Accessibility statement

By Rohit Gaur · Last updated October 30, 2026 · Report a mistake

The target is WCAG 2.2 level AA, and every test that can be automated runs on every change.

What is checked automatically

Each build runs an accessibility scan (axe-core) over the calculator in four states — as it loads, with the cost panel open, with a field showing an error, and with several rooms — and over every written page. The build fails if any serious or critical issue appears.

Alongside that, the build checks that:

• every control can be reached and used from the keyboard, with a visible focus ring;
• every field has a real label, and no field uses a placeholder attribute instead of one;
• every image and drawing has an accessible name, or is explicitly hidden from assistive technology;
• colour contrast meets the AA threshold in both the light and the dark theme.

Decisions worth knowing about

• The drawings are described, not decorative. Each one carries a name that includes its measurements, and the same numbers appear as text beside it, so nothing is available only as a picture.
• Results are announced. Totals live in a status region, so a screen reader hears the new number when it changes rather than only on request.
• Little motion, and none if you ask. The menu on a phone fades in over 0.15 seconds, and the acreage map animates its zooms. When your device asks for reduced motion, the fade does not play and the map moves straight to where it is going.
• The menu on a phone is the browser’s own popover: Escape or a tap outside closes it, focus goes back to the Menu button, and it opens without JavaScript.
• The theme follows your system unless you pick Light or Dark with the switch in the header (in the menu, on a phone), and both themes are tested for contrast.

What has not been tested yet

Automated tools catch perhaps half of what matters. Still outstanding:

• a manual pass with NVDA on Windows and VoiceOver on iOS;
• testing on real phones rather than emulated ones;
• testing at 400% browser zoom and with a screen magnifier.

The site went live on 21 September 2026 before these were done, and as of 30 October 2026 they are still outstanding. This page will give the date each one is done.

If something does not work

Write to contact@sqftmath.com with the page, the browser and the assistive technology you use. Accessibility bugs are treated as bugs, not as feature requests.