Accessibility
This site targets WCAG 2.2 Level AAA. Where a criterion is not met, it is named below rather than omitted.
What is in place
- Text contrast of at least seven to one against its background, in all four reading themes.
- Line length capped below eighty characters, with line and paragraph spacing set for readability.
- Four selectable reading themes, including a high-contrast option.
- A summary in plain language at the top of every substantive page, in a labelled box.
- Every interactive target at least forty-four by forty-four pixels.
- Link text that describes its destination without relying on surrounding words.
- Nothing that moves, auto-advances, or interrupts. No pop-ups and no time limits.
- The contact form shows you exactly what will be sent and asks you to confirm before sending.
- Full keyboard operation, with a visible focus indicator that is never obscured.
- A glossary, linked from technical terms on first use.
Known exceptions
The W3C does not recommend Level AAA as a blanket policy for entire sites, because some criteria cannot be met for some content. These are the places this site falls short, and why.
- 3.1.5 Reading Level
- The doctrine documents are written for a professional audience and exceed lower secondary reading level. The plain-language summary at the top of each page is the supplementary version this criterion allows, but it summarises rather than replaces the argument.
- 1.2.6 Sign Language and 1.2.8 Media Alternative
- Archived talks link to third-party video hosted elsewhere. Captions are not under this site’s control, and no sign language interpretation is provided. A written summary accompanies each.
- 1.4.9 Images of Text
- Documents linked from external sources may contain images of text. Those documents are not authored here.
Reporting a barrier
If any part of this site prevents you from doing something, please write and say what happened and what you were using. Contact details are here. A reply should be expected within five working days.
How this was assessed
Automated checks run against every deployment and block it if they fail. Automated testing catches perhaps a third of real barriers, so manual keyboard and screen reader testing is done as well. This statement is reviewed whenever the site changes materially.