Legal
Accessibility
Our conformance target, how we test, and how to report a barrier.
Our target
This website is designed and built to meet WCAG 2.2 level AA. Accessibility is treated as an acceptance criterion, not a post-launch task.
How we test
Automated checks (contrast, semantics, form labelling) run on every route, followed by keyboard-only passes and screen-reader spot checks on the main journeys: navigation, filters, the brief form and article reading.
What works today
All interactive elements are reachable and operable by keyboard. Focus is always visible. Forms label every field and announce errors. Motion respects the reduced-motion setting. Colour pairings ship with measured contrast ratios.
Known limitations
Decorative photography carries descriptive alt text but no long descriptions; where a caption is needed, it is written into the page. The style guide page is an internal review tool and is not linked from navigation.
How to report a barrier
If something on this site blocks you, send a brief through the project form marked “Accessibility”. We reply within two business days and treat the report as a defect, not a favour.
How fixes ship
Barrier reports are triaged with the next release. If a fix needs more than two weeks, we say so, explain why, and offer an alternative way to get the information.
Standards we reference
WCAG 2.2 AA for web content, ISO 9241 for interaction principles, and EN 301 549 where clients operate in regulated markets.
Review cadence
This statement is reviewed every six months and after any significant change to the site or the brief form.
Questions
If something here is unclear.
Use the project form and mark your message “Legal question” or “Accessibility”; it routes to the person who maintains this page.
Next step
Start a project
Tell us what you are planning. Three steps, about two minutes.