1. Home
  2. Accessibility

Verifiable quality

Digital accessibility

Accessibility that is measured, not merely claimed.

Edikka treats accessibility as a production-quality discipline: HTML structure, keyboard navigation, contrast, text alternatives, forms, reduced motion and compatibility with assistive technologies.

  • RGAA 4.1.2
  • Partially conformant
  • 96% of applicable criteria
  • 3 published gaps
Read the audit report

Key indicators for Edikka's accessibility approach

96%

Partially conformant

June 25, 2026 internal RGAA 4.1.2 audit: 76 conformant criteria, 3 non-conformities and 27 non-applicable criteria.

76

URLs checked

The full accessibility crawl reported no failure and no issue across the public sitemap.

84

Expert checks

Keyboard, 320/390 px reflow, ARIA, accessible names, images and accessibility tree: 0 failure on the controlled sample.

8 x 100

Lighthouse accessibility

Priority templates, including the AI-agent readiness test after correction, reached 100 for Lighthouse accessibility.

1. Commitment

Edikka is committed to making its website accessible to as many people as possible, with attention to keyboard navigation, document structure, contrast, text alternatives, forms and reduced-motion preferences.

The goal is not only to remove issues detected by automated tools. The goal is to maintain verifiable quality for people using a keyboard, a screen reader, enlarged display settings or constrained browsing conditions.

2. Conformance status

This statement applies to the edikka.com website. It is published voluntarily and aligned with the expected French RGAA accessibility statement format.

Following the June 25, 2026 internal criterion-by-criterion audit, edikka.com is declared partially conformant with RGAA 4.1.2. The published rate is 96% of applicable criteria met, based on 76 conformant criteria out of 79 applicable criteria.

Published official result: partial RGAA 4.1.2 conformance, 96% of applicable criteria met, 3 non-conformities and 27 non-applicable criteria. The remaining issues are published to avoid overstating the status as total conformance.

3. Testing method

The internal audit combines the complete RGAA 4.1.2 grid with a representative sample of the website’s pages and user journeys.

  • Homepage, expertise pages, project, insights, FAQ, contact, accessibility statement, audit report, English version, AI-agent readiness test, legal pages and 404 page.
  • Complete RGAA 4.1.2 grid: 13 topics, 106 criteria, with each criterion marked conformant, non-conformant or not applicable.
  • Automated tests: WAVE, axe or equivalent, Lighthouse and HTML validation where relevant.
  • Browser tests: keyboard, focus order, 320/390 px reflow, Chrome accessibility tree, contrast, text alternatives, forms and multimedia content.
  • Verification of user preferences, including reduced-motion behavior.

4. Test results

The checks performed between June 22 and June 25, 2026 show a very favourable technical base, with three remaining issues deliberately kept in the published rate.

  • Global accessibility crawl: 76 content URLs audited, 0 skipped URL, 0 fetch failure, 0 issue.
  • Expert Chrome/Playwright checks: 84 checks, 0 failure.
  • Keyboard navigation: skip link, mobile menu, Escape closing and focus restoration validated.
  • Real screen-reader testing: VoiceOver with Safari was used on the homepage, contact, accessibility statement and audit report, with no blocking issue reported.
  • Reflow: no user-facing horizontal scroll on priority pages at 320 px and 390 px.
  • Lighthouse accessibility: priority templates reached 100, including the AI-agent readiness test after contrast correction.
  • Contrast: 0 Lighthouse color-contrast error on the verified FAQ pages after correction.
  • W3C Nu validation: 0 message on the verified pages.
  • June 25, 2026 AI-agent readiness test check: 1 H1, 1 main region, 24 radio inputs described by aria-describedby, no broken ARIA reference and no new-tab link without an announcement.

Criterion-level statuses, controls and reservations are published in the detailed accessibility audit report.

5. Non-accessible content

Three non-conformities remain in the published rate. They do not block access to the main checked pages, but they prevent Edikka from claiming total conformance.

Declared non-conformities

  • Criterion 4.1: editorial audio versions must be linked to a transcript or equivalent text alternative for each published media item.
  • Criterion 10.12: strengthened text-spacing checks must be replayed across the full public scope before reclassification.
  • Criterion 13.3: public downloadable documents, including PDFs, must be audited or paired with an equivalent accessible HTML alternative.

Derogations and exemptions

  • No disproportionate burden derogation is invoked.
  • No exempt content has been identified as of June 25, 2026.

6. Statement preparation

This statement was prepared on June 22, 2026 and last updated on June 25, 2026.

Technologies used

  • HTML5, CSS, JavaScript and TypeScript.
  • PHP for server-side templates.
  • Inline SVG, decorative or named depending on their role.
  • WAI-ARIA where needed for interactive components.
  • JSON-LD schema.org structured data.

Test environment and tools

  • Google Chrome, Chrome DevTools Accessibility Tree and Playwright checks.
  • Lighthouse, WAVE, W3C Nu Validator and internal accessibility crawl.
  • User preference prefers-reduced-motion tested in browser context.
  • VoiceOver Safari documented on key pages; NVDA Firefox remains recommended if available.

7. Verified pages

8. Detailed report

The public report brings together the tested sample, complete RGAA grid, Lighthouse and W3C results, full-site crawl, FAQ contrast checks, 84 expert checks with no failure, the June 25, 2026 supplementary check and the remaining non-conformities.

Read the detailed accessibility audit report. For editorial analysis and future measurement waves, see the French-language Observatoire accessibilité Edikka.

Recommended reading path

9. Already in place

  • A skip link allows keyboard users to reach the main content directly.
  • Menus use ARIA states to communicate opening and closing behavior.
  • Main forms use labels associated with their fields.
  • Zoom is not blocked by the viewport.
  • Animations are disabled when the user requests reduced motion.
  • Public quality checks, including WAVE, are available from the “Verifiable quality” section.

10. Maintenance and next steps

  • Maintain automated and human checks when major changes are made to the website.
  • Complete an NVDA Firefox pass if a Windows environment is available.
  • Correct the 3 remaining non-conformities to aim for total conformance.
  • Commission third-party review if a contractual, legal or certification need requires it.
  • Maintain the crawl and Lighthouse checks when major changes are made.

11. Accessibility contact

If you have difficulty accessing content or a feature on the website, you can contact Edikka to request a correction or an accessible alternative.

12. Remedies

If you report an accessibility issue that prevents access to content or a feature and do not receive a satisfactory response, you may contact the French Defender of Rights.

13. Follow-up and updates

This page will be updated after each major step: blocking issue correction, new audit, possible publication of a conformance score update or evolution of the reference standard.

  • June 22, 2026: accessibility statement, detailed report and technical evidence published.
  • June 22, 2026: the French-language Accessibility Observatory opened to document the method and future measurement waves.
  • June 23, 2026: previous interim status recorded as administratively non-conformant, with targeted checks passed and limits published.
  • June 25, 2026: internal criterion-by-criterion audit published, status changed to partially conformant, with 96% of applicable criteria met.
  • Afterwards: regular checks when major changes are made to the website.