Accessibility

Tools designed for keyboard, screen and assistive technology use

We aim for WCAG 2.2 AA and treat calculator errors, focus behavior and result announcements as core functionality.

What we test

Pages use semantic headings, visible labels, keyboard-operable controls, strong focus indicators, sufficient contrast, responsive layouts and live result messaging that does not steal focus. Motion respects reduced-motion preferences, and print views preserve the calculation record.

Known limitations

Automated checks cannot prove full accessibility. We also inspect representative pages with keyboard navigation, zoom, narrow viewports and screen-reader-friendly markup before release.

Reporting a problem

If a calculator is difficult to use, record the page, control, device and assistive technology involved. A public contact channel will be added before production launch; until then, accessibility is a release-blocking review item rather than an unsupported promise of conformance.