Legal

Accessibility

This site is built to WCAG 2.2 AA. People read it under stress, often on a phone, often in a second language — accessibility and plain writing are the same project here, not separate ones.

Last verified 12 September 2026 · 1 day ago · checked by spec-import Every figure on this page was checked against its source on this date.

What we have done

• Semantic landmarks, a skip link, and headings in a real hierarchy on every page.
• Full keyboard operability. Source panels on figures open with the keyboard, not on hover — hover-only would fail both WCAG and every touch device.
• Visible focus outlines that are not removed.
• Tap targets of at least 44px on every interactive control.
• No horizontal page scroll at 360px. Tables scroll inside their own container with a sticky first column.
• Every comparative table is preceded by a plain-language sentence, so information is never conveyed by table structure alone.
• Colour is never the only signal. Pass and fail states carry text and symbols as well.
• Ranges are written "550 to 750" rather than with a hyphen, which a screen reader announces as "minus".
• Dark mode follows your system setting, and a high-contrast preference flattens the palette further.
• Reduced-motion preferences are respected.
• Every calculator degrades to a static table when JavaScript is unavailable.

Known gaps

We have not yet run a full audit with assistive technology users, and automated checks are not the same as someone actually using the site. The calculators are the most likely place for problems, because live-updating results are easy to get wrong for screen reader users even when the markup looks correct.

Fonts are currently a system stack rather than the self-hosted faces specified for the design. That is a fidelity gap rather than an accessibility one, and it means the site loads faster than specified in the meantime.

Reporting a problem

If something here is hard or impossible to use, tell us and describe what happened and what you were using. Accessibility reports are treated like factual corrections: they go to the top of the queue ahead of new writing.