This site aims at WCAG 2.2 level AAA. Every claim below was measured in a browser against the colours and sizes actually rendered, not read off a palette, and the places it falls short are named rather than left out.
What it meets
- Contrast, enhanced (1.4.6). Every piece of text the site draws clears 7:1 against the background behind it, measured against the darker ground and the lighter panels separately, because the lighter one is the harder case and it is what the reading column sits on.
- Target size, enhanced (2.5.5). Every control is at least 44 by 44 pixels. The numbered markers on the model stay small because enlarging them would change the drawing, so the target grew and the dot did not.
- Visual presentation (1.4.8). Line spacing is 1.62, paragraph spacing more than 1.5 times that, no text is justified, and no line exceeds about 74 characters.
- Keyboard, no exception (2.1.3). Everything is reachable and operable from the keyboard, including the model: arrow keys move the camera in free roam. Focus is visible on every control.
- Motion. A Reduce motion control sits in the menu, and the site also honours the reduced-motion setting in your operating system without being asked. Nothing flashes.
- Structure. One h1 a page, headings in order, landmarks on every region, and a skip link to the text.
Where it does not reach AAA
- The accessibility toolbar's own controls. The toolbar is a third-party widget, and several of its buttons and its language picker do not meet 7:1. We cannot change its internals without forking it. Everything the site itself draws does meet it.
- Reading level (3.1.5). AAA asks for text a lower secondary reader can follow. Parts of this site quote planning language, listing descriptions and Local Plan policy, and those sentences carry length the measure punishes and the argument needs. The questions and answers page is the plain-language version of the whole case.
- The model. The 3D model is decorative and marked as such, so a screen reader skips it. Everything it shows is also written out in the text beside it, which is the version that carries the meaning.
If something here does not work for you
Tell us and it gets fixed. The contact button on the site goes to Jamie and nowhere else, or write to [email protected]. Saying what you were trying to do and what happened instead is more useful than naming a standard.