The commitment and how it is checked
This site targets WCAG 2.2 AA practices. Pages are built from semantic HTML with a single H1, a logical heading order, real landmark elements, descriptive link text, and visible focus indicators. Content renders server-side, so it does not depend on client-side scripting to be readable.
That is checked in two ways: an automated accessibility scan runs against representative pages as part of the test suite, and keyboard navigation through the primary flows is exercised directly. Both are part of the release gate rather than a periodic audit.
What is implemented
The specific measures in place across the site:
- Skip link to main content as the first focusable element
- Keyboard operability throughout, with no keyboard traps and visible focus styling
- Form fields with associated labels, and validation messages announced to assistive technology
- Colour contrast targeted at AA thresholds for body and interface text
- Meaningful alternative text on informative images; empty alt on decorative ones
- Reduced-motion preferences respected, with animation suppressed when requested
- Accordion and disclosure content built on native elements that expose their state
Where automated testing is not enough
Automated scanning reliably catches contrast failures, missing labels, and structural problems. It cannot judge whether alternative text is actually useful, whether a heading order makes sense to someone navigating by headings, or whether an interaction is comprehensible with a screen reader. Those need human review, and that review has not yet been performed by someone using assistive technology daily.
That is stated here rather than implied, because an accessibility statement claiming more testing than has been done is its own accessibility problem.
Reporting a barrier
If part of this site is difficult or impossible to use, that is worth reporting, and specifics help most: the page, the assistive technology and browser, and what you were trying to do. A public contact route for accessibility reports is on the owner-confirmation list and will be published once supplied.
Frequently asked questions
Is this site fully WCAG 2.2 AA conformant?
It is built to those practices and automated testing passes on representative pages, but full conformance is a claim that requires manual evaluation across every page and interaction — including testing with assistive technology by someone who uses it regularly. That has not been completed, so the claim is not made.
Does the site work without JavaScript?
Content pages render on the server, so text, headings, links, and structure are present without client-side scripting. Interactive elements use native HTML controls where possible, which is why disclosure and accordion content remains operable.
