Accessibility Statement
Draft — pending counsel review
Accessibility is an engineering discipline. It is testable, measurable, and it fails in observable ways. It belongs in the same operating posture as observability, security, and governance: designed in, instrumented continuously, and regressed against rather than retrofitted when someone notices.
The site you are on aims to meet WCAG 2.2 Level AA. This is the same posture the firm takes on enterprise AI systems it builds for clients: declared, evidenced, and surveyed against. Where the site falls short of the standard, the gap is named below rather than concealed. Accessibility consciousness on a site that hides its known issues is theatrical, not engineering.
Standards declared
Standards we target. This site targets WCAG 2.2 Level AA, the current Web Content Accessibility Guidelines standard maintained by the W3C Web Accessibility Initiative. The standard covers perceivability (text alternatives, time-based media, adaptable presentation, distinguishable content), operability (keyboard accessibility, sufficient time, no seizure-inducing content, navigability, input modalities), understandability (readability, predictability, input assistance), and robustness (compatibility with current and future user agents and assistive technologies).
WCAG 2.2 Level AA is also the conformance level expected by the UK Public Sector Bodies Accessibility Regulations 2018, the EU Web Accessibility Directive (where it applies to public-sector bodies), and the EU Accessibility Act (where it applies to private-sector services).
Testing methodology
How we test. Automated testing runs against axe-core and Lighthouse on every deployment. Automated tests catch a meaningful but limited fraction of WCAG criteria: broken alt-text, low contrast ratios, missing form labels, invalid ARIA. They do not catch the criteria that depend on context: heading semantics, focus order, descriptive link text, the appropriateness of an image's alternative text given the page's argument.
Manual testing covers the criteria automation cannot. The site is audited with a screen reader (NVDA on Windows, VoiceOver on macOS), with keyboard-only navigation, and at 200 percent zoom. The cadence is per release for major templates, and quarterly for a full-site review.
External testing is engaged annually with a third-party accessibility auditor.
Known limitations
Where we fall short, currently. The following gaps to WCAG 2.2 Level AA are presently known and tracked. Each is recorded with a target resolution date and assigned to an accountable engineer.
If the list above is empty at the time of your visit, the site is presently believed to meet WCAG 2.2 Level AA in full. New gaps may be identified in subsequent audits; this list is updated as they are.
Reporting an issue
Found something we should fix? If you encounter an accessibility issue on this site, a barrier you experienced personally or a gap you observed, please tell us through the contact form, choosing "Something else", with: a description of the issue, the page URL, the assistive technology you were using (screen reader, switch device, voice control, etc.), and the device and browser. We review every accessibility report we receive and reply with what we plan to do about it.
If our response does not resolve the issue or you are dissatisfied with how it was handled, you can escalate via the regulatory mechanism that applies to your jurisdiction:
In the United Kingdom: the Equality and Human Rights Commission (EHRC) for matters under the Equality Act 2010, or the Equality Commission for Northern Ireland for Northern Irish matters.
In the European Union: the national accessibility enforcement body in your member state (the European Commission maintains a list of national contact points).
Elsewhere: the equivalent accessibility regulator in your jurisdiction.
Last reviewed
This Accessibility Statement was last reviewed on [TODO: last reviewed date — owner/counsel]. The next scheduled review is [TODO: next review date — owner/counsel].