--- title: "Accessibility Statement: Myrmid" description: "WCAG 2.2 AA conformance target, automated and manual test layers, known limitations, and how to report a barrier." canonical: https://www.myrmid.ai/en/accessibility/ --- Accessibility # Accessibility statement Last updated: 2026-05-10 Myrmid is committed to making this site accessible to as many visitors as possible. This statement reports the current accessibility status of the site, the standard we conform to, and how to reach us if you encounter a barrier. ## Conformance target This site targets **WCAG 2.2 Level AA** as its accessibility conformance standard. Where French regulation references RGAA (_Référentiel général d'amélioration de l'accessibilité_), we treat WCAG 2.2 AA conformance as substantively meeting the equivalent RGAA criteria; an explicit RGAA self-assessment lands when the company crosses the obligation thresholds (public-sector contract, €250M turnover, or other RGAA Art. 47 trigger). ## Conformance state **Substantially conformant.** The site is built against WCAG 2.2 AA and gated by automated and manual accessibility checks at every release. Specifically, every public surface passes: - **axe-core 100/100** (zero violations across `wcag2a`, `wcag2aa`, `wcag21aa`, `wcag22aa` rule sets) on every locale × every colour mode. - **Heading-hierarchy clean:** exactly one `<h1>` per page; no skipped levels. - **Reduced-motion respected:** every animation, transition, and Stigmergy motion exception (the Hero scroll-cue ant + the cursor trail) is gated by `prefers-reduced-motion: reduce` and resolves to zero motion when the visitor's system signals that preference. - **Theme + locale switching** is FOUC-free and announced to assistive technology when locale changes. ## Known limitations Certain French and German content is currently flagged as draft pending native-speaker review; while the underlying structure is conformant, native-language idiomatic accuracy follows the H2 sign-off. This is content-quality, not accessibility-of-structure. The Lucie chat widget (when enabled) is built to the same accessibility standard as the page chrome, but its conformance is asserted by the widget's own accessibility tests; consult the widget repository for that conformance statement. ## How we test We combine four layers: 1. **Automated checks in CI:** axe-core, heading-hierarchy, FOUC, and reduced-motion gates run on every pull request before merge. 2. **Per-locale Lighthouse audits** at every release. 3. **Manual NVDA + VoiceOver passes** at every major release (Story 2.5 NFR-A3 baseline) on Windows + macOS/iOS, with results logged in the repository. 4. **Real-user CWV measurement** via the `web-vitals` library, sampled on every page view, so we know the in-the-wild experience matches the lab. ## Reporting an accessibility barrier If you encounter a barrier on this site (anything from a missing label to a contrast issue to a keyboard trap), please tell us: [accessibility@myrmid.ai](mailto:accessibility@myrmid.ai) We respond within 5 business days with an acknowledgement and a target fix date. Where the fix takes longer than the response window, we tell you the route to the information you needed in the meantime. ## Mediation pathway If you raise a barrier and we do not respond within a reasonable time, you may refer the matter to the Défenseur des droits, the independent French ombudsman. Contact details and the procedure are at [www.defenseurdesdroits.fr](https://www.defenseurdesdroits.fr/). ## Statement maintenance This statement is updated when our conformance state materially changes (new automated gates land, new manual-test results, new known limitations). The "last updated" date at the top reflects the most recent change.