Accessibility statement
Calculators are only useful if everyone can use them. Here's what we do and where to report problems.
Last updated August 2026
Our target
We aim for conformance with WCAG 2.2 Level AA. Accessibility is treated as a requirement for every new calculator, not a retrofit.
What that means in practice
The whole site is built and tested against these behaviors:
- Every input has a visible label and, where helpful, inline guidance — no placeholder-only labeling.
- All tools are fully operable by keyboard, with a visible focus indicator and a skip-to-content link.
- Results are announced to screen readers using live regions; errors are reported as alerts next to the form.
- Pages use semantic structure (headings, landmarks, lists) so navigation works with assistive technology.
- Text meets contrast requirements, and information is never conveyed by color alone.
Known limitations
Some long pages (calculators with extensive supporting content) are dense by nature; we use clear heading structure and breadcrumbs to keep them navigable. If you find a specific barrier, we want to hear about it.
Feedback
If you hit an accessibility barrier — a control you can't reach, text you can't read, a result that isn't announced — please report it through the contact page. Accessibility reports are treated as bugs, not suggestions.