Accessibility statement
Last updated : September 10, 2026
We want this site to be usable by everyone, including with a screen reader, keyboard only, or heavy magnification. This page states what has been verified, how, and what has not.
01Where we stand
**We do not declare this site compliant.** Declaring conformance with WCAG 2.1 AA requires a full manual audit, criterion by criterion. That audit has not yet taken place.
What has been done is an **automated** check, run across ten pages representative of a visitor's path, in both themes and at two screen widths — forty scans in total. It currently reports no violations.
That distinction is not a stylistic hedge. Automated tooling detects roughly a third of accessibility criteria: contrast, attributes, heading structure, accessible names. It does not judge whether an alternative text is meaningful, how the tab order actually feels, or what someone navigating by ear really hears.
Claiming conformance on that basis alone would be false, and would turn against you the day a user found otherwise.
02What is checked on every release
The automated check is part of the delivery pipeline: it runs before every release, and a regression blocks deployment exactly as a failing test does.
It covers text contrast in both themes, accessible names for links, buttons and fields, heading structure, ARIA roles and their naming, keyboard access to scrollable regions, and the presence of alternative text on images.
Fixes already made as a result: the logo's accessible name in dark theme, turquoise contrast on tinted backgrounds, naming of the quote form's progress bar, and keyboard access to the availability chart.
03What we do not yet know
No testing has been carried out with an actual screen reader (NVDA, JAWS, VoiceOver), nor with the people concerned.
Tab order, focus handling when dialogs open and close, and the relevance of alternative texts on article illustrations have not been manually reviewed.
PDF documents you may receive in your client area are not checked: their accessibility depends on the tool that produced them.
04Reporting a problem
If a page resists you, write to us: we treat such reports as defects, not suggestions.
Where possible, describe the page and how you navigate — keyboard, screen reader, magnification. It saves us from looking in the wrong place.
We undertake to acknowledge receipt within two working days and to give a target date for a fix.

