Accessibility of the akiani.fr website

Partially compliant with RGAA 4.1.2, by voluntary alignment. The site is not subject to the legal obligation (Article 47 of Law No. 2005-102, which targets organizations with more than €250 million in turnover). We publish this statement and the multi-year scheme below anyway, because we design digital products for organizations that are subject to it. Practicing what we preach is sturdier than defending it in a sales deck.

Method

Internal audit using axe-core 4.11, WCAG 2.1 level AA ruleset, across 186 pages as of 27 May 2026. The site now has 474 pages as of 14 August 2026, 237 of them in French: the automated audit needs to be re-run on that scope, and it is listed in the action plan below. We also ran a dedicated audit of tab order and visible focus (RGAA 10.7, 12.7, 12.8, 12.9) on 10 representative desktop page templates. Manual criterion-by-criterion verification has not been carried out across the whole site, and there is no third-party audit.

Results

182 pages out of 186 with no violation detected by the tool. axe-core covers about a third of the RGAA, namely the automatable rules. Within this scope and excluding third-party iframes, the site reports no violation.

Non-compliant content. No WCAG 2.1 AA violation detected by the automated audit outside third-party iframes. Any gaps the manual audit reveals will be listed here, criterion by criterion.

Exempt content. Four pages carry violations located inside an iframe supplied by a third party: Spline 3D, INA Fresques, a Facebook embed and the TED player. This is code sent by those providers, which we don't control. If the content of one of these iframes is not accessible to you, write to us and we will send it to you in another form.

Disproportionate burden exemptions. None to date.

Fixes applied during this campaign

Contrast token on the breadcrumb of the case studies (61 pages).
title attribute on the YouTube iframe of the Weezdays article, so that it carries an accessible name.
title attribute added to 5 non-YouTube third-party iframes.
aria-hidden replaced with inert on the scroll-driven CTA of the about page.
Defensive aria-label and skipping of empty sections in JavaScript-built article tables of contents.
Three empty links removed on old WordPress articles (two links containing only a <br>, one link wrapping a decorative image).
Keyboard audit on 10 desktop page templates: skip link first in the tab order, no trap, no positive tabindex, visible focus on every interactive element.

How this statement was drawn up

Statement drawn up on 27 May 2026, updated on 14 August 2026.

Technologies used on the site: HTML, CSS, JavaScript and SVG.

Evaluation tools: axe-core 4.11 with the WCAG 2.1 level AA ruleset, run in headless Chrome against the production build, plus a manual keyboard audit on 10 desktop page templates. Screen-reader testing has not taken place yet: it is in the 2026 action plan, not here.

Pages tested for the keyboard audit: the home page, about, what we do, our values, our team, the blog index, the article "3 UX lessons from ransomware", the glossary entry "arborescence", the Lab study "UXDevil", and this page.

One caveat about the template we follow: it provides for remedies before the Défenseur des droits, which exist for organisations under the legal obligation. We are not one of them, so that remedy does not apply to us. It changes nothing about the commitment in the Contact section: a reported gap gets an answer.

Limitations

Manual criterion-by-criterion verification and screen-reader testing across the whole site remain to be done, as does an audit by an independent third party. The keyboard audit currently covers desktop only. The mobile menu and focus behaviour in opened states (modals, expanded filters) remain to be checked.

We follow the DINUM framework used by organisations subject to Article 47, for two reasons. First, it makes things simpler when our clients (who are subject to it) speak that same language. Second, a multi-year scheme forces you to write down what you'll do in three years, and therefore to do it. The scheme covers both akiani.fr and our internal practices (project method, training, client deliverables).

Accessibility policy

akiani.fr targets WCAG 2.1 AA conformance. On client projects, we embed accessibility from the design phase, to the extent of what is commissioned. It isn't always spelled out in the quote, but it's always in the method.

Resources allocated

The in-house team carries the work (UX research, UX/UI design, integration). We don't have a dedicated accessibility consultant, but we have lined up a third-party audit in 2027 to test our work against an outside view.

Organisation

Accessibility is tooled inside the site's repository. We have a design guide that goes through seven user perspectives (from visually impaired users to people with cognitive disorders), an axe-core audit that re-runs on the production build, and around twenty integration guardrails documented from mistakes we've already made. Sébastien Klifa is the digital accessibility lead. He coordinates audits, team training and the handling of reports, and carries the topic into client projects.

Accessibility in projects

On akiani.fr, any new interactive component (modal, dropdown, carousel) goes through an accessibility framing before being written, then an automated audit afterwards. On client projects, we progressively embed accessibility into the phases we handle: a brief that asks the question, UX research that includes people with disabilities when the topic calls for it, wireframes that think about screen readers, and acceptance that checks it.

Team training

We keep building skills on RGAA, ARIA patterns, and screen-reader testing. We aim for one team-wide session per year, tracked in the annual review.

External expertise

The independent third-party audit is scheduled for 2027. We bring in outside skills ad hoc when the topic requires it: a test session with a user who has a rare impairment, expertise on a sector-specific standard we don't master.

User tests

We include people with disabilities in the UX research of client projects whenever the product is meant for them or the topic calls for it. On akiani.fr, a screen-reader test (VoiceOver, NVDA) is scheduled on the critical paths in 2026.

Audit calendar

axe-core audit, at each significant release.
Manual criterion-by-criterion audit, on critical paths in 2026 then on the whole site in 2027.
Independent third-party audit in 2027.

Order of fixes

Fixes follow audience: key journeys first (home, what we do, case studies, contact), then the most visited pages, then the rest. A gap that prevents use comes first, whatever the audience of the page.

Enhanced accessibility

We do not plan either sign-language translation or an easy-read version on akiani.fr. It is a presentation website, and that effort is worth more on the public services we design for our clients than on our own pages. On request, we will send any content in another form.

User feedback handling

If you report a gap to hello@akiani.fr, we reply within 5 working days saying what we will do and when. Gaps that block use go first, the others join the current plan.

Full axe-core audit across the 186 pages published as of 27 May 2026 (done). To be re-run across the 474 pages of the site (to come).
Fix all WCAG AA violations detected outside third-party iframes (done).
Internal tooling: accessibility guide by user perspectives + automated audit agent (done).
Manual criterion-by-criterion audit on critical paths (home, expertise, case studies, contact) (in progress), keyboard and focus part (RGAA 10.7, 12.7, 12.8, 12.9) covered on 10 desktop page templates.
Screen-reader test (VoiceOver, NVDA) on 10 representative pages (to come).
Internal practice sheet "accessibility in Akiani projects" (to come).
First team accessibility training session (to come).

2027 action plan (forecast)

Independent third-party RGAA 4.1.2 conformance audit.
Manual criterion-by-criterion audit extended to the entire site.
Systematic accessibility scope included in project quotes.
Client deliverables (presentations, reports) produced in accessible format by default.
Year-one public review published on this page.