Accessibility
What has been done to make this usable, and how to tell us where it fails.
How this site is built
- Every page is ordinary HTML that works without JavaScript for reading; the calculators need it, the tables do not.
- One
h1per page and headings in order, so a screen reader’s outline matches the visible one. - Data tables use real
thheaders with scopes and a caption, rather than styleddivelements. - Wide tables scroll inside their own region, which is focusable and labelled, so the page body never scrolls sideways.
- Visible focus outlines on every interactive element, and no focus trap anywhere.
- Colour is never the only carrier of meaning; text contrast targets WCAG 2.2 AA.
- Text reflows to 320px and can be zoomed to 200% without loss of content.
Known limits
The full pay-scale and take-home tables are large. They are marked up correctly and are navigable, but reading a 31-row, seven-column table with a screen reader is slow regardless — the per-band pages exist partly for that reason, since each carries the same figures in smaller pieces.
Telling us where it fails
Accessibility problems are defects. A contact route will be published alongside the site’s public launch, and reports of specific failures — the page, what you were using, and what happened — are the most useful thing anyone can send.