Our accessibility goal
We target the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA as a practical, ongoing goal, not a one-time checklist. Accessibility is treated as part of building a calculator, not a separate pass done at the end.
Keyboard use
Every interactive control — inputs, toggles, tabs, buttons, and menus — is reachable and operable using a keyboard alone, with a visible focus outline so you can always see where keyboard focus currently is.
Labels and semantic structure
Calculator inputs are named for assistive technology rather than relying on placeholder text: by a visible label tied to the field or, on compact unit, mode and table-cell controls, by an aria-label. Headings, lists, tables, and form fields use semantic HTML so they are announced correctly by assistive technology, and results are exposed as real text content, not just a styled number.
Colour contrast
Text and interactive colours are designed to meet WCAG AA contrast ratios in both light and dark themes, rather than relying on colour alone to convey meaning.
Screen-reader considerations
On some calculators the result region is a live region, so a screen reader announces the new figure as the calculation updates; on the rest you move to the result to hear it. Most decorative icons are hidden from assistive technology so they do not add noise to what is read aloud.
Zoom, responsive layout, and reduced motion
Layouts are responsive down to small mobile widths and remain usable at increased browser zoom. Pages follow your system light/dark preference, and respect a reduced-motion preference where animation is used. Display advertising is currently disabled, so no ad placement can shift the layout or reflow inputs.
Charts and tables
Wherever a chart appears, the same figures are also available as result cards or a data table, so a chart is never the only way to read a result.
Known limitations
We consider the site partially conformant: complex charts, dense comparison tables, and some interactive scenario tools still need broader assistive-technology testing beyond what has been checked so far. Four gaps are known: most calculators do not yet announce result updates automatically; some small icons beside headings and breadcrumb links are still read out; the mode selector on the GPA calculator has no accessible name; and contrast is designed for WCAG AA but not yet checked automatically on every page. This is stated plainly rather than claiming full conformance we haven't verified.
Reporting an accessibility problem
If you hit a barrier, tell us the page, your device or browser, and the assistive technology you use, through our contact page. Accessibility reports are treated as a priority, alongside content and formula corrections covered in our Corrections Policy. For more on how the site is built and reviewed, see About.
Accessibility FAQ
Do the calculators work with a screen reader?
Inputs are named for screen readers, results are real text in semantic HTML (announced as they update on some calculators), and interactive controls are reachable with a keyboard. Complex charts and dense tables still need broader assistive-technology testing, which is why the site is described as partially, not fully, conformant.
Can I use a calculator with only a keyboard?
Yes — every interactive control (inputs, toggles, buttons, tabs) is reachable and operable by keyboard, with a visible focus outline so you can see where you are.
Does the site support dark mode and reduced motion?
Yes. Layouts follow your system light/dark preference and respect a reduced-motion preference where animation is used.
What should I do if I hit an accessibility barrier?
Tell us the page, your device or browser, and the assistive technology you use, through the contact page. Accessibility reports are treated as a priority.
