Accessibility
We want CalculatorLib to be usable with a keyboard, a screen reader, at any zoom level and in any colour scheme. This page says how far we have got, what we already know is wrong, and how to tell us about the rest.
Last reviewed: 3 de septiembre de 2026.
Where we stand
CalculatorLib is partially conformant with WCAG 2.2 level AA. Partially conformant means most of the site meets the standard but some parts do not, and the parts we know about are listed below. We have not commissioned an independent audit; this statement is based on our own testing.
What is in place
Every page begins with a "skip to content" link that takes a keyboard user straight past the header and navigation. Interactive controls show a visible focus ring. Animation is switched off for anybody whose system asks for reduced motion. Pages carry a language attribute so a screen reader pronounces them correctly, and wide tables are scrollable regions a keyboard can reach and their screen reader can announce.
What we know does not work yet
- Calculator input forms are generated from the definition of each calculator, and older definitions do not all pair every field with a proper label or explain their units to a screen reader. We are correcting these as the calculators are revised.
- Formulas are rendered with KaTeX. It produces a readable image of the formula for sighted users and a text version underneath for screen readers, but complex expressions are still announced awkwardly, and there is no spoken step-by-step alternative yet.
- A few tools draw a chart of the result. The numbers behind the chart are always shown in the result text as well, but the chart itself carries no description.
- Calculators embedded on other people's websites inherit that site's page structure, so how they behave for assistive technology partly depends on the host page.
Tell us when something blocks you
If any part of this site stops you doing something, tell us — it is the fastest way for it to get fixed, and we would rather hear about it than not. Say which page you were on and what you were using; we reply to every report.
Report an accessibility problem