Accessibility statement

Translation provided for information only; only the French version is legally binding. View the French version

1. KAYZEN’s commitment

KAYZEN is committed to making its website accessible to everyone, whatever their disability, in accordance with the RGAA 4.1 (Référentiel Général d’Amélioration de l’Accessibilité, the French accessibility standard), the Web Content Accessibility Guidelines (WCAG 2.1 level AA) and the European Accessibility Act (EAA — Directive (EU) 2019/882).

Digital accessibility is at the heart of what we do: we help businesses achieve EAA compliance with our Konforme tool and our accessibility audit and compliance services. Our own website has to set the example: it is continuously improved, and this page keeps an honest account of where it stands.

This accessibility statement applies to the website https://www.kayzen-lyon.com.

2. Compliance status

The website www.kayzen-lyon.com is non-compliant with RGAA 4.1: no full audit has yet been carried out. The known non-conformities are listed below.

This finding is based on an internal evaluation carried out on 3 September 2026: automated audits (Lighthouse, axe-core) of representative pages, manual keyboard and screen reader checks, and contrast measurements. A full RGAA audit covering all 106 criteria, carried out by a third party, has not yet been conducted; the compliance rate is therefore not published.

The following have been verified as compliant to date: page structure (a single main landmark, named landmarks, skip link), heading hierarchy, text alternatives for images, the contact form (labels, error messages linked to their fields, focus moved to the first error), support for the “reduce motion” preference by CSS animations and our in-house components, and the contrast of body text (14.7:1) and secondary text (6:1).

3. Non-accessible content — known non-conformities

The following issues have been identified and are being fixed. They are listed by RGAA criterion, with the corresponding WCAG criterion.

  • RGAA 3.3 — contrast of user interface components (WCAG 1.4.11). The borders of form fields (contact form, quote configurator, 404 page search, cookie banner) have a contrast ratio of 2.3:1 in the light theme, below the 3:1 threshold. In “OLED” mode, the fields are almost invisible.
  • RGAA 3.2 — text contrast (WCAG 1.4.3). In the dark theme, the white text of some action buttons has a ratio of 3.2:1, below the 4.5:1 threshold. Some secondary text on the contact card and the on-screen quote is also below the threshold.
  • RGAA 7.1 and 12.x — dialog component (WCAG 2.4.3, 4.1.2). The digital contact card opens as a modal window without moving focus on opening, without a focus trap and without returning focus on closing; its tabs do not declare their panels and cannot be navigated with the arrow keys. The theme button combines a “pressed” state with a changing label, which produces a contradictory announcement.
  • RGAA 13.8 — motion and animation (WCAG 2.2.2). CSS animations and our reveal components respect the system’s “reduce motion” preference, but sections animated with the framer-motion library (portfolio, pricing, service pages) do not yet do so.
  • RGAA 13.2 — opening a new window (WCAG 3.2.5). Some links open a new tab without warning (Grants and Stack pages, quote configurator, assistant). The legal pages and the footer were fixed on 3 September 2026.
  • RGAA 11.10 and 11.11 — input validation (WCAG 3.3.1, 3.3.3). In the quote configurator, error messages are not linked to the fields concerned and focus is not moved to the first error. The contact form, by contrast, is compliant on these points.
  • RGAA 10.7 — focus visibility (WCAG 2.4.7). On input fields, the focus indicator is limited to a one-pixel border change, which is barely perceptible.
  • RGAA 12.11 — keyboard navigation in menus (WCAG 2.1.1). The mega menu opens on focus but does not close when focus leaves it; in the quiz, the radio buttons cannot be navigated with the arrow keys and focus is lost at each question.
  • Target size (WCAG 2.5.8, level AA since WCAG 2.2). Several controls measure less than 44 pixels: the assistant’s launcher and close button, the contact card button, the carousel arrows and dots, and the configurator options.
  • “Dyslexia-friendly font” option. The option offered in the accessibility settings does not yet have an embedded font and does not apply to headings: it has no real effect. It will either be given a font that is actually loaded or be removed.

4. Technologies used

  • HTML5 / ARIA
  • CSS (Tailwind CSS)
  • JavaScript / TypeScript (React)

5. Evaluation methodology and tools

Accessibility is checked using:

  • Automated Google Lighthouse and axe-core audits of representative pages of the site;
  • Manual checks: full keyboard navigation (Tab, Enter, Space, Esc), contrast ratio checks (WCAG 2.1 — 1.4.3 and 1.4.11), heading hierarchy, text alternatives, link and button labels, screen reader output;
  • Our in-house tool Konforme, dedicated to EAA/RGAA accessibility auditing;
  • Respect for user preferences: dark theme, reduced motion (prefers-reduced-motion), adjustable text size;
  • Test environment: spot checks carried out with recent versions of the Chrome, Firefox and Safari browsers, and with the NVDA and VoiceOver screen readers.

6. Third-party content and exemptions

The following content comes from third-party services or is generated on demand; its accessibility does not depend entirely on us, and an alternative is offered for each item:

  • The Google Maps map in the footer, loaded only when you choose to; the postal address is provided as text nearby;
  • The appointment booking module, which relies on Calendly; a phone and email alternative is offered on the same page;
  • The conversational assistant, based on Google’s Gemini model: its responses are generated automatically and are not audited; a member of the team remains reachable by email, by telephone or via the Contact page;
  • The PDF quote produced by the quote configurator, which is not yet tagged for assistive technologies; its content can be obtained in an accessible format on request from the address given in section 8;
  • Some decorative mock-ups (website previews) are shown for illustration purposes.

7. Preparation of this statement

This statement was drawn up on 4 July 2026 and updated on 30 September 2026, on the basis of the internal evaluation of 3 September 2026. It will be updated each time one of the issues listed in section 3 is fixed, and reviewed at least once a year.

8. Feedback and contact

If you encounter an accessibility issue that prevents you from accessing content or a feature of the site, please let us know: we undertake to reply and to fix the problem as quickly as possible.

9. Remedies

If you have noticed an accessibility issue, reported it to us and not received a satisfactory response, you are entitled to: