Accessibility

A legal explainer that cannot be read is worthless. These are the choices made so this site works for as many people as possible, and how to tell us when one of them fails.

What is built in

• Contrast. Body text sits at roughly 14:1 against the page and no interface text falls below 4.5:1. The accent gold is used as a shape and background color; where gold appears as text it uses a darker value that clears the threshold.
• Text size. Body text is 19px on a desktop and 17.5px on a phone, with a line height near 1.7 and a measure capped at about 75 characters. Nothing breaks if you scale text to 200% in your browser.
• Keyboard. Every control is reachable by keyboard, in a sensible order. The search box is a proper combobox: arrow keys move through results, Enter opens one, Escape closes the list. A skip link is the first focusable element on every page.
• Focus. The focus ring is a solid 2.5px outline, deliberately heavier than any hairline on the page so it cannot be mistaken for a border.
• Motion. The only movement on the site is a slight image scale on hover and a fade when a menu opens. All of it is disabled when your system asks for reduced motion, including smooth scrolling.
• Images. Every photograph has alt text describing what is actually in the frame, and dimensions are set so the page does not jump while images load.
• Structure. One H1 per page, headings in order, real landmarks, and lists and tables marked up as lists and tables rather than drawn with characters.
• No JavaScript required. Every report, desk and policy page is plain HTML. Only search needs scripting, and the search page says so and offers the archive instead.

Known limits

Wide comparison tables scroll horizontally inside their own container on a narrow screen. We use tables only where the comparison genuinely needs rows and columns, and the surrounding text always states the point the table makes, so nothing is lost by skipping it.

Telling us about a barrier

Write to [email protected] with the page address and what happened — the assistive technology, the browser, and what you expected instead. Accessibility defects are treated as bugs, not as feature requests.