Accessibility
Accessibility Statement
The site is designed to target WCAG 2.2 AA where practical for the MVP launch. Last reviewed on 16 June 2026 against keyboard navigation, form usability, visible focus, reduced-motion expectations, and automated accessibility scanning.
Commitment
The target for this MVP is WCAG 2.2 AA.
Accessibility is treated as a launch-quality requirement rather than post-launch polish. The site is reviewed as a static export served by the same C++ origin runtime used for production delivery behind the managed edge.
Last reviewed
This statement was last reviewed on 16 June 2026.
Accessibility work included so far
- Semantic headings and labelled form controls.
- Keyboard-reachable navigation and mobile menu controls.
- Visible focus states and skip-to-content support.
- Reduced-motion support for visitors who request it.
- Browser-based verification of the core marketing and form flows.
- Automated accessibility scanning across the required launch page set using Playwright and axe.
Known limitations
As of 16 June 2026, no severe automated accessibility blockers are intended to remain open at launch. This is an internal launch evidence pass, not a formal certification or exhaustive third-party audit. If an issue is discovered, it should be triaged visibly rather than hidden inside implementation notes.
How to report an issue
Please report accessibility problems through [email protected] and include the page URL, the device or browser used, and a short description of what was difficult to access.
Review cadence
Accessibility should be reviewed before launch, after significant UI changes, and at least quarterly while the site is active.
Next step
Want to review the main interaction path?
The fit-call and audit-request forms are part of the accessibility review because they are core launch journeys, not optional extras.