Accessibility Statement

What we do

These measures are built into the site and into the process that ships it:

• An automated axe-core check (WCAG 2.2 AA rules) runs in continuous integration on every change and fails the build on any serious or critical violation. It covers seven representative pages: the home page in two languages, the calculator index, a category page, two calculators and the unit converter.
• A visible focus outline on every link, button, field and menu, applied site-wide from the stylesheet rather than component by component.
• A “skip to main content” link as the first item in the tab order.
• Landmarks (header, main, footer, navigation) and headings in order, so a screen reader can jump around the page.
• Animations and smooth scrolling are switched off when the operating system asks for reduced motion.
• Layouts are built mobile-first, and a second automated check fails the build if any element spills outside a 375 px-wide screen.
• Form fields have real labels, and errors are announced to assistive technology.

Compatibility

The site is built to work with:

• Current versions of Chrome, Firefox, Safari and Edge.
• Keyboard-only navigation.
• Browser zoom to 200% and text-only resizing.
• Screen readers that support HTML landmarks and ARIA.

We verify keyboard operation and the automated checks ourselves. We have not run a systematic test pass with JAWS, NVDA or VoiceOver, so we cannot promise a flawless experience with a specific screen reader.

Known limitations

We would rather list these than pretend they are not there:

• The automated check runs on representative page templates, not on every individual URL. A page that uses an unusual component may carry a defect the gate never sees.
• Kalcufy has not been audited by an independent accessibility specialist.
• Advertising and analytics loaded from third parties are outside our control and may introduce problems we cannot fix directly.
• Charts and complex visualisations inside some calculators offer limited alternatives for screen reader users; the underlying numbers are always available as text.
• PDF exports are not tagged and are not guaranteed to be accessible.
• A few interface strings outside the calculators (such as the skip link) are only available in English.

How this was assessed

This statement is based on a self-evaluation carried out with:

• Automated axe-core testing against WCAG 2.0/2.1/2.2 A and AA rules, run in continuous integration.
• Manual keyboard walkthroughs of the interactive pieces we build ourselves: the sign-in dialog, the account pages and the widget generator.
• Review of colour contrast against the 4.5:1 requirement for body text and 3:1 for large text and interface components.

No external audit has been commissioned yet. When one is, this page will say so.