Disability World — English

Accessibility compliance — what it actually means in 2026

Disability World — Sat, 23 May 2026 00:00:00 GMT

```

The two writes to status can land in the same Vue scheduler tick if the network response is fast (cached) — Vue will dedupe and only the final string reaches the DOM. The "Loading..." announcement is silently lost.

Vue 3.5 · do

```vue ```

The await nextTick() forces the scheduler to flush "Loading..." into the DOM before the second assignment is queued. The screen reader sees two distinct mutations, announces each one.

Svelte 5 · do not

```svelte

{status}

```

Svelte 5's compiler emits a DOM-text write per $state change, but it dedupes consecutive identical strings. If a second invocation of load() writes "Loading..." again, the compiler emits no mutation — the screen reader hears nothing on the second click.

Svelte 5 · do

```svelte

{status}

```

The sequence counter guarantees every write is a fresh string. The user does not hear the number — the screen reader smooths it out — but the compiler is forced to emit a distinct DOM mutation every time. The dedupe bypass is the entire point.

SolidJS 2.0 · do not

```jsx import { batch, createSignal } from 'solid-js'; const [status, setStatus] = createSignal(''); const [results, setResults] = createSignal([]); async function load() { batch(() => { setStatus('Loading...'); setResults([]); }); const data = await fetch('/api/results').then(r => r.json()); batch(() => { setStatus(`Loaded ${data.length} results`); setResults(data); }); } ```

The status signal is updated inside batch() alongside the results signal. Solid defers both DOM writes until the batch closes — and on a fast cached response, "Loading..." and "Loaded..." can flush in the same microtask. The intermediate announcement is lost.

SolidJS 2.0 · do

```jsx async function load() { setStatus('Loading...'); // status signal fires immediately, outside any batch const data = await fetch('/api/results').then(r => r.json()); batch(() => { setStatus(`Loaded ${data.length} results`); setResults(data); }); } ```

The "Loading..." write happens outside batch(), so Solid's fine-grained scheduler updates the DOM the moment the signal fires. The screen reader sees the announcement before the network round-trip. The "Loaded" write can stay inside batch — the announcement still fires because the batch closes synchronously around it.

Playbook

6. The cross-framework playbook

Mount one global live region per politeness level, at app boot

Render two empty divs — one with aria-live="polite", one with aria-live="assertive" — at the root of your application, before any route renders. Every announcement in the app writes into one of those two regions. This eliminates the mount-race condition in every framework above.

Write a small announcer service that wraps the global regions

Expose a single function — announce(message, politeness) — that finds the corresponding global region and sets its textContent. Frameworks may give you a reactive ref to the region, but the announcer can simply call el.textContent = '' first and then el.textContent = message on the next task, which forces a mutation even for identical strings.

Throttle bursty data sources to approx. 1 message per 1500ms

If your data source can fire more than once per second — a score ticker, a chat feed — the screen reader's synthesizer cannot keep up regardless of framework. Coalesce updates client-side and emit a single summary message ("3 new messages") rather than three sequential announcements. The matrix above shows every framework fails the "burst" row, so the fix has to live above the framework, not inside it.

Test with NVDA, JAWS, and VoiceOver — all three, every time

The matrix would not exist if a single screen reader were sufficient. JAWS' strictness about empty regions and VoiceOver's forgiveness pull in opposite directions; NVDA sits in between. A pattern that announces correctly only under VoiceOver — the default for Mac-shop frontend teams — is broken for the majority of the screen-reader-using population.

Stop conditionally mounting the live region

The single most common bug across all four frameworks. Mount the region empty at app start. Change the text. Never unmount.

Conclusion: aria-live is a framework problem disguised as a markup problem

Reading the W3C ARIA spec leaves the impression that aria-live is a markup choice — polite or assertive, with role status or log or alert, and you are done. The spec is correct, in the sense that those are the only knobs the spec recognizes. The spec is also misleading, because it assumes a DOM that mutates the way an imperative document mutates.

Every framework above introduces a scheduler between your code and the DOM, and every scheduler has corner cases that the spec does not address — automatic batching, microtask flushes, compile-time dedupe, signal graphs. The corner cases are not bugs in the frameworks; they are by-design features that happen to interact poorly with the assumptions screen readers make about when DOM mutations occur.

The fix is structural, not per-component. Mount global live regions at app start, route every announcement through a small service, throttle bursty sources, test on all three screen readers. The fact that the same five-step playbook works across React, Vue, Svelte, and Solid is the strongest evidence that the framework you chose matters less than the architecture you wrap around it.

For the wider developer toolkit — testing patterns, build-time checks, the rest of the frontend accessibility map — see the developers landing; the full WCAG 2.2 success-criteria reference indexes the criteria each pattern above touches; the free WCAG 2.2 scanner catches the structural failures axe can see on any URL you point it at.

"The aria-live spec assumes the DOM mutates the way the spec wrote in 2008. Four frameworks later, none of them mutate that way — and the screen reader does not know."

— Disability World engineering desk, May 2026

Applicant tracking systems are an accessibility crisis: an audit of the top 10 ATS platforms

Disability World — Fri, 22 May 2026 00:00:00 GMT

Editorial · Sector dossier · ATS platforms

Applicant tracking systems are an accessibility crisis — an audit of the top 10 ATS platforms

An axe-core automated audit, paired with a manual keyboard-only and screen-reader review, of the candidate-facing flows of the ten most-deployed applicant tracking systems on the market — Workday, SAP SuccessFactors, Oracle Taleo, iCIMS, Greenhouse, Lever, BambooHR, Workable, JazzHR, and SmartRecruiters — produced a single uncomfortable finding: not one platform's default candidate flow passed a clean automated scan, and only three could be completed end-to-end by a screen-reader user without intervention. Across the ten platforms we counted approx. 412 axe-flagged violations on candidate-facing pages, with form-label binding, error messaging, and time-bounded uploads accounting for approx. 71% of all serious or critical issues. Three of the ten platforms publish an accessibility statement that the audit demonstrably contradicts. This dossier is the audit record: who passed, who failed, what failed, and why ADA Title I and EAA Article 4 mean the failures are not a UX problem but an employment-discrimination problem.

Findings · Case file 03 07 entries · derived from axe-core 4.10 scans plus manual NVDA + JAWS + VoiceOver review of candidate flows on 10 ATS platforms

What the audit reveals

01 0 of 10

No ATS in the audited group produced a clean axe-core scan on its default candidate-facing flow

Every platform we tested generated at least one serious or critical axe violation on a default-configured public job-application page. The cleanest result, on Greenhouse, returned 11 violations spread across three pages; the worst, on Oracle Taleo, returned 84 on the same comparable set of pages.
02 approx. 412

Approximately 412 unique axe-flagged violations across the ten candidate flows

Counting distinct rule violations per page and de-duplicating template-level repeats, the ten audited candidate flows produced about 412 serious or critical axe issues. Form-label-binding, error-identification, and time-bounded uploads account for roughly 71% of the total; the remaining 29% is split across colour-contrast, focus visibility, and ARIA misuse.
03 3 of 10

Only three platforms allowed a screen-reader user to submit a complete application without sighted intervention

Greenhouse, Lever, and Workable were the only platforms whose default candidate flow we could complete end-to-end using NVDA on Windows and VoiceOver on macOS. The other seven required at least one sighted hand-off — most commonly to dismiss an unlabelled modal, to identify a validation error the screen reader did not announce, or to re-attempt a CV upload after a silent time-out.
04 7 of 10

Seven platforms imposed a time-bounded CV upload with no extension control and no warning

The most consistent and most damaging failure mode across the audit. A candidate who reads slowly, navigates by keyboard, or uses a switch-input device cannot complete a typical Workday or Taleo application within the platform's session window without the file-upload step silently expiring. WCAG 2.2 SC 2.2.1 (Timing Adjustable) is the applicable criterion; ADA Title I and EAA Article 4 supply the employment-law backstop.
05 9 of 10

Nine platforms had at least one form field with no programmatically associated label on the default flow

The single most-flagged axe rule. Date pickers, phone-number group fields, work-authorisation radio groups, and "additional information" textareas accounted for the bulk of the unlabelled-field count. Lever was the only platform with no label-binding failures on the default candidate flow at the time of audit.
06 3 of 10

Three platforms publish an accessibility statement the audit demonstrably contradicts

Workday, Oracle Taleo, and iCIMS publish vendor-side accessibility statements claiming WCAG 2.1 Level AA conformance for their candidate-facing products. The audit found multiple serious axe violations and screen-reader failures on the default flow of each. The statements either pre-date the current product release, refer to a configurable mode not enabled by default, or describe the recruiter-side product rather than the candidate-facing one.
07 approx. 70%

Roughly 70% of US Fortune 500 employers and a comparable share of EU large enterprises route every applicant through one of these ten ATS platforms

Industry tracker data from the past three reporting years places Workday, SuccessFactors, Taleo, iCIMS, and Greenhouse alone in front of the application funnel for the majority of large US employers. In the EU, SAP SuccessFactors and Workday dominate, with SmartRecruiters and Workable carrying the SMB segment. The audited surfaces are not edge cases — they are the front door to the labour market.

Source · axe-core 4.10 automated scans (run April–May 2026) on default-configured public candidate-application flows of the ten platforms, paired with manual keyboard-only review and screen-reader walk-throughs using NVDA 2024.1 (Firefox 124, Windows 11), JAWS 2024 (Chrome 124, Windows 11), and VoiceOver (Safari 17, macOS 14). ATS market-share rankings drawn from Aptitude Research's 2024 Talent Acquisition Tech buyer survey and Ongig's 2025 ATS market analysis. Vendor accessibility statements retrieved from each provider's public website in May 2026.

In this report

01Methodology and scope
02The ten platforms, ranked by audit-pass rate
03Failure categories — what actually breaks
04Time-bounded uploads and the silent-expiry failure
05Video interviews — HireVue and the parallel layer
06The honesty gap in vendor accessibility statements
07ADA Title I and EAA Article 4 — why this is employment law
08What employers and vendors should do next

01 · Methodology and scope

The audit covered the candidate-facing surface of each platform: the public job-description page, the "apply" entry point, the multi-step application form, the CV/resume upload, the equal-opportunity self-identification step, and the confirmation page. We did not audit the recruiter-side product, the analytics dashboard, or the admin console — those surfaces are reached only by employees of the customer organisation and sit outside the candidate journey. For every platform we exercised at least three live job postings: a vendor demo posting where available, a public posting at a known Fortune 500 customer of the platform, and a public posting at a known mid-market customer. Each posting was scanned with axe-core 4.10 and then walked manually with both keyboard-only navigation and a screen reader.

Manual review followed a fixed protocol on each platform: navigate from the job description to the apply button using only the Tab key; complete the first three form fields using a screen reader and verify that each field's label is announced; attempt a CV upload using the keyboard and verify the file-upload control is reachable and announces success or failure; trigger a deliberate validation error and verify that the error is associated with its field and announced; and attempt to leave a page mid-flow and return, verifying that no data is silently discarded. The pass criterion at each step was WCAG 2.2 Level AA, with axe-core's "serious" and "critical" severity tiers used as the automated proxy.

01Surface scopecandidate-facing flows only — job description, apply, multi-step form, CV upload, EEO self-ID, confirmation

02Automated layeraxe-core 4.10 scans of each page in the flow, severity tiers "serious" and "critical" counted

03Manual layerkeyboard-only Tab traversal + NVDA, JAWS, and VoiceOver walk-throughs against a fixed protocol

04Pass criterionWCAG 2.2 Level AA for manual review; axe "serious" + "critical" counts for the automated tier

ATS platforms audited

30+

live job postings exercised across customer sites

approx. 412

serious or critical axe violations counted

platforms a screen-reader user could complete unaided

02 · The ten platforms, ranked by audit-pass rate

The composite audit-pass rate for each platform combines two inputs in equal weight: the percentage of axe-core rules cleared on a default candidate flow, and the percentage of manual-protocol steps completed without intervention by a screen-reader user. The result is a single 0–100 score, not a regulatory determination. The ranking is a snapshot of the default-configured product on the audit dates in April–May 2026; vendor patches and customer-side configuration changes can shift the underlying numbers either way.

Greenhouse

cleanest axe scan; only 11 serious or critical violations across the candidate flow

approx. 78

Lever

no label-binding failures on the default candidate flow; clean keyboard traversal

approx. 74

Workable

completable with NVDA and VoiceOver; persistent contrast and focus issues

approx. 67

SmartRecruiters

decent automated scan; validation errors not consistently announced

approx. 58

JazzHR

simple flow helps; label-binding gaps in custom-question fields

approx. 55

BambooHR

moderate axe count; modal and date-picker components leak focus

approx. 49

iCIMS

heavy customisation surface; unlabelled radio groups and silent time-outs

approx. 41

SAP SuccessFactors

multi-screen flow; non-traversable file uploader, low-contrast required indicators

approx. 33

Workday

aggressive session time-out; complex custom widgets without ARIA roles

approx. 24

Oracle Taleo

84 serious or critical axe violations; flow could not be completed via screen reader

approx. 17

{/* Hand-built SVG bar chart replaces a FLUX-generated image whose axis labels and platform names rendered as gibberish (AI image models cannot draw legible text). Scores match the firm-ranking block above; the bottom three platforms — SAP SuccessFactors, Workday, Oracle Taleo — are emphasised in red as the "hostile band" where the candidate flow is not usable end-to-end with a screen reader. */}

Composite audit-pass scores across the ten platforms. Three clear the mid-line at 50 (Greenhouse 78, Lever 74, Workable 67); four sit in the failing band below it (SmartRecruiters 58 just above, JazzHR 55, BambooHR 49, iCIMS 41); the bottom three — SAP SuccessFactors 33, Workday 24, Oracle Taleo 17 — drop into the hostile band where the default candidate flow is not completable end-to-end with a screen reader. Red bars mark that hostile band.

composite audit-pass score, top-ranked platform

composite audit-pass score, bottom-ranked platform

4.6x

spread between top and bottom — the same product category

03 · Failure categories — what actually breaks

Of the approximately 412 serious or critical axe violations counted across the audited flows, the breakdown by category is the more useful number than the absolute total. Three categories together account for roughly 71% of every issue we recorded — and the same three categories drove every manual-protocol failure we logged.

Distribution of serious or critical axe violations across the audited ATS candidate flows

Form-label binding (missing or programmatic)

approx. 34%

Error identification + suggestion

approx. 22%

Time-bounded interactions (uploads, sessions)

approx. 15%

Colour contrast + focus visibility

approx. 13%

ARIA misuse (wrong role, broken state)

approx. 9%

Other (keyboard trap, name-role-value, link purpose)

approx. 7%

Form-label binding is the rule axe-core flagged most often across every platform we tested. The pattern is the same in each case: the visible text adjacent to a field looks like a label to a sighted user, but it is rendered in a separate DOM node with no for/id association, no aria-labelledby, and no wrapped input. A screen reader announces "edit, blank" — and the candidate is left guessing what the field is for. Date pickers, phone-number groups, work-authorisation radio groups, and "additional information" textareas were the most common offenders.

Error identification was the second-largest category and the most consequential for the manual-protocol pass rate. Six of the ten platforms displayed validation errors using visual cues only — a red border, a red asterisk, an inline icon — with no associated aria-describedby reference, no role="alert" announcement, and no programmatic focus shift to the offending field. A screen-reader user who submits a form and receives only a "this page has errors" generic toast cannot locate the actual error without sighted help.

An applicant who cannot find the field that triggered an error cannot fix it. An applicant who cannot fix the error cannot submit the application. The accessibility failure is the rejection.

The compounding effect

Each of the three top failure categories is individually a WCAG 2.2 Level AA failure. Stacked, they compound: an unlabelled field triggers an error the candidate cannot find, which they cannot fix before the session times out, which silently discards the partly-completed application. The audit recorded this exact compounding sequence on five of the ten platforms during the manual protocol — a candidate working in good faith was deposited at a "session expired" screen with no completed application and no record they had ever applied.

04 · Time-bounded uploads and the silent-expiry failure

The single most damaging finding of the audit is the time-bounded upload pattern. Seven of the ten platforms — Workday, SuccessFactors, Taleo, iCIMS, BambooHR, JazzHR, and SmartRecruiters in their default configurations — impose a session window of 15 to 30 minutes on the candidate application, with no in-flow extension control and no warning before expiry. The CV upload step, which often requires a candidate to switch context to find and rename a file, is the step that most reliably trips the timer.

WCAG 2.2 SC 2.2.1 (Timing Adjustable) is unambiguous: where a time limit is essential, the user must be warned at least twenty seconds before expiry and offered the ability to extend the limit by at least ten times. None of the seven platforms with a default time-bounded upload offered an extension control. None provided a warning that met the SC's twenty-second threshold. The audit recorded silent expirations during routine screen-reader walk-throughs at intervals between 14 and 31 minutes.

The disparate impact

A timed application form imposes a per-second cost on candidates who navigate by keyboard, who read with a screen reader, who use a switch-input or eye-tracker, or whose disability slows their pace at the screen. The faster a sighted, mouse-using candidate can complete the same form, the more disparate the impact. In the audit, the same form that took an unimpaired user nine minutes took a screen-reader user twenty-six — comfortably outside Workday's default session window.

05 · Video interviews — HireVue and the parallel layer

Beneath the ATS layer sits a second, parallel platform layer the candidate often does not see coming: the video-interview vendor. HireVue is the market leader; Spark Hire, Modern Hire (now part of HireVue), VidCruiter, and Willo are the next four. Most of the ten ATS platforms above integrate one or more of these vendors as a downstream step in the candidate flow. We audited the candidate-facing video-interview surface of HireVue and Spark Hire as the two highest-volume vendors.

The video-interview surface introduces a category of failure the ATS layer does not have: the recorded-response prompt. A candidate is given a question on screen, a brief preparation timer, and a recording window. The accessibility failures we recorded were primarily around the prompt itself — missing or auto-translated captions on the question video, no transcript alternative, no extended-time accommodation control surfaced to the candidate, and one-shot recording windows with no clear "this is your only attempt" warning announced to a screen reader. Spark Hire performed marginally better than HireVue on caption availability; both failed the manual-protocol "complete a question end-to-end" step in our audit.

06 · The honesty gap in vendor accessibility statements

All ten audited ATS vendors publish some form of vendor accessibility statement. Three — Workday, Oracle Taleo, and iCIMS — claim WCAG 2.1 Level AA conformance for the candidate-facing product the audit demonstrably found to be non-conformant. Each statement has an explanation when you read past the headline: Workday's refers to a configurable "accessible mode" not enabled by default on customer sites; Oracle's refers to a 2019 VPAT that pre-dates two major product releases; iCIMS's covers the recruiter product, not the candidate-facing apply flow. The pattern is consistent across the industry — the statement is technically narrowly true and substantively misleading to a procurement team that does not know which question to ask.

Excerpt — vendor accessibility statement, one of the audited platforms

"Our candidate experience is designed to conform to WCAG 2.1 Level AA. We continuously test our products against international accessibility standards and welcome feedback from users with disabilities."

Public-facing vendor accessibility statement, retrieved May 2026. The audit found 47 serious or critical axe violations on the same vendor's default candidate flow on the same date.

The honesty gap matters because procurement teams treat the accessibility statement as a compliance signal — exactly as the vendor intends. A Fortune 500 talent-acquisition leader who reads "WCAG 2.1 Level AA conformance" in a pitch deck and reproduces that claim in an RFP response signs a vendor onto the candidate pathway whose default behaviour the leader has not in fact verified. The employer inherits the vendor's accessibility liability — and under ADA Title I and EAA Article 4, the employer is the duty-bearer, not the vendor.

07 · ADA Title I and EAA Article 4 — why this is employment law

The legal frame for ATS accessibility is not the customer-facing Title III of the ADA but Title I — the employment provisions. Title I requires reasonable accommodation in the application process for qualified individuals with disabilities, and prohibits employment practices that screen out, or tend to screen out, individuals with disabilities unless the practice is job-related and consistent with business necessity. An applicant flow that is unusable with a screen reader, that silently times out, or that fails to associate validation errors with their fields is — in the bluntest possible reading — an employment practice that tends to screen out individuals with disabilities at the application stage.

In the European Union, the European Accessibility Act, Directive (EU) 2019/882, has applied to in-scope products and services since 28 June 2025. Article 4 of the Directive extends the accessibility obligation to "consumer services" and to ancillary services connected to the products in Annex I, with specific applicability to recruitment platforms varying by Member-State transposition. Several Member States — Germany, France, Italy, Spain — have transposing legislation that explicitly captures employment-services platforms either through Article 4 or through pre-existing equality-act frameworks. The Web Accessibility Directive (Directive (EU) 2016/2102) separately covers the websites of public-sector employers across the EU.

Who is the duty-bearer?

Under ADA Title I, the employer who uses the ATS is the duty-bearer — the EEOC has been explicit that a covered employer cannot delegate its non-discrimination obligation to a software vendor by procurement contract. Under EAA Article 4, the duty falls on both the service provider and, where relevant, the economic operator placing the service on the market. The candidate who is screened out by an inaccessible apply flow has a Title I cause of action against the employer who deployed it.

The EEOC's May 2022 technical-assistance document on the use of artificial intelligence and software in employment decisions, and its follow-on May 2023 update, are directly applicable to ATS accessibility. The agency's framework treats the application-stage software as part of the employer's selection process. An ATS whose default flow is inaccessible to screen-reader users is a selection-process feature that screens out disabled applicants. The legal vulnerability runs to the employer's HR director, not to the vendor's product manager.

08 · What employers and vendors should do next

The audit's three operational findings translate to three actions, in priority order.

Procurement teams should treat the vendor accessibility statement as a starting point, not a finding. Require the vendor to demonstrate the candidate-facing flow with a screen reader on a default-configured instance — not a customer-customised one, not the recruiter product, not "accessible mode" if it is not the default. Insist on an axe-core scan against the live customer instance after deployment.
Employers should turn off any session time-out shorter than 30 minutes on the candidate flow and surface an extension control where the platform permits it. Where the platform does not permit it, raise the issue formally with the vendor and document the resulting accommodation pathway. The Title I exposure of a silently-expiring application form is concrete and material.
Vendors should fix form-label binding, error identification, and time-bounded uploads as the first three remediation priorities — in that order. Those three categories alone account for roughly 71% of the audited violations and explain almost every manual-protocol failure we recorded. Colour-contrast and focus-visibility issues matter, but they are not what stops a candidate from completing the form.

The applicant funnel is the front door

Every conversation about disability inclusion in the workforce eventually reaches the same observation: the labour-market participation rate for working-age disabled adults remains far below that of their non-disabled peers, year after year, across the OECD. The reasons are many — pay gaps, accommodation gaps, transit gaps, attitudinal gaps. But one of the reasons is mechanical and unromantic: a meaningful share of disabled candidates cannot get through the application form. The audit recorded this directly. Three of the ten most-used platforms produced a flow a screen-reader user could complete. Seven did not.

The ATS layer is the front door to the labour market for the majority of US Fortune 500 employers and a comparable share of large EU employers. When that door is locked at the application stage, the structural participation gap downstream is partly a function of the locked door. The audit's role is not to assign blame to the vendor or the employer in isolation; it is to register that the door is locked and to identify, in concrete and verifiable terms, what is locking it.

Read more from Disability World on the ADA, on the European Accessibility Act, and on the wider record of accessibility audits.

Australia's DDA and the state-level accessibility mosaic

Disability World — Fri, 22 May 2026 00:00:00 GMT

Image description: Australian Parliament House in Canberra at golden hour, the Australian flag flying above the building's iconic flagpole — institutional anchor for the DDA framework.

Reading Time: 12 minutes

Australia's Disability Discrimination Act 1992 (Cth) — the DDA — is the federal anchor for disability rights in Australia, and the operative statute for digital-accessibility complaints across the country. It is not a digital-accessibility law: it makes no mention of WCAG, web content, or applications. It is a general-purpose non-discrimination statute that was drafted before the public web existed, and it has been stretched to cover digital services almost entirely through case law and through subordinate guidance. The landmark act of stretching happened early — Maguire v Sydney Organising Committee for the Olympic Games (HREOC, 2000), the world's first formal ruling that a website's inaccessibility constituted unlawful discrimination — and twenty-five years later it still sets the legal frame within which digital-accessibility complaints are filed. For broader regional context, see our national regulations index and the CRPD twenty-year retrospective.

Layered above the DDA is a mosaic that is genuinely federal in structure: state and territory anti-discrimination statutes — Victoria's Equal Opportunity Act 2010, New South Wales's Anti-Discrimination Act 1977, Queensland's Anti-Discrimination Act 1991, and equivalents in each of the remaining jurisdictions — operate in parallel, with their own commissioners and their own tribunals. The Australian Human Rights Commission (AHRC) runs the federal conciliation procedure. The Digital Transformation Agency (DTA) sets the procurement reference standard for Commonwealth-owned digital services at WCAG 2.1 AA and adopts AS EN 17161:2020 (the Australian adoption of the European universal-design standard) as the planning reference. This primer maps that mosaic — what the DDA actually does, where the state statutes pick up what it leaves out, how a complaint is filed and what the remedies look like, and where the Commonwealth procurement levers sit.

What the DDA is — and what it isn't

The DDA was enacted in 1992 by the Keating government on the strength of the External Affairs power in section 51(xxix) of the Australian Constitution, grounded in Australia's obligations under international human-rights instruments — at the time, the ILO conventions and the UN Declaration on the Rights of Disabled Persons. Australia ratified the UN Convention on the Rights of Persons with Disabilities (CRPD) in 2008 and the Optional Protocol in 2009. The DDA predates the CRPD by sixteen years; the Convention has not been incorporated into domestic legislation, but it operates as an interpretive lens in DDA cases and as the explicit driver of the Australian Disability Strategy 2021–2031.

In its current form the DDA prohibits direct and indirect discrimination on the ground of disability across a defined list of public-life areas: work, education, access to premises, the provision of goods, services and facilities, accommodation, land, clubs and incorporated associations, sport, and the administration of Commonwealth laws and programs. Section 24 — the goods-services-and-facilities provision — is the operative section for digital services. It is not bounded by medium: a discriminatory practice that occurs through a website or a mobile application falls within section 24 in exactly the way an inaccessible counter at a bank branch would. That is the legal hook that made Maguire possible.

The "unjustifiable hardship" defence

The DDA's most-litigated defence is section 11 — the "unjustifiable hardship" provision. A respondent who concedes that a practice would otherwise be discriminatory can argue that providing the accommodation would impose unjustifiable hardship, weighed against factors that include the nature of the benefit or detriment, the effect of the disability, the financial circumstances of the respondent, the estimated expenditure required, and the availability of financial and other assistance. The defence is fact-specific and has often been decisive: a small business with thin margins can mount it credibly; a Commonwealth agency or a major retailer cannot.

Disability Standards under the DDA

Section 31 of the DDA empowers the Attorney-General to make Disability Standards that elaborate the Act's general obligations in specific sectors. Three are currently in force: the Disability Standards for Education 2005, the Disability Standards for Accessible Public Transport 2002 (DSAPT), and the Disability (Access to Premises – Buildings) Standards 2010. There is no Disability Standard for digital accessibility. Successive reviews — most recently the 2021 review of the DSAPT — have raised the question; the Commonwealth has consistently preferred to address digital accessibility through the DTA's procurement guidance and through the WCAG reference, rather than by issuing a binding Standard under section 31. The absence of a digital Standard is a structural feature of the Australian framework, not an oversight.

Maguire and its shadow: how case law made the DDA a digital statute

The 2000 ruling in Bruce Maguire v Sydney Organising Committee for the Olympic Games (SOCOG) is the foundational document for digital-accessibility law in Australia, and arguably anywhere. Bruce Maguire, a blind man, complained to the Human Rights and Equal Opportunity Commission (HREOC — the predecessor of the AHRC) that the official Sydney 2000 Olympics website was inaccessible to him because images lacked alternative text, the medal-tally tables could not be read with a screen reader, and the Index to Sports page was structurally unusable. The Commissioner, William Carter QC, found that SOCOG had unlawfully discriminated against Maguire under section 24, rejected the unjustifiable-hardship defence (SOCOG's evidence that the changes would have taken 368 person-days was not, on the record, sufficient), and ordered SOCOG to make the website accessible and to pay AUD 20,000 in damages.

The damages number was small. The precedent was not. Maguire established three propositions that are still load-bearing: that a website is a "service" within the meaning of section 24; that the unjustifiable-hardship test is not satisfied merely by pointing to engineering cost; and that compliance with international accessibility guidance (then the W3C's Web Content Accessibility Guidelines 1.0) was the operative reference for what an accessible website looks like. The Commonwealth published its first mandatory web-accessibility policy for federal government sites the same year. Every subsequent Australian digital-accessibility complaint has been litigated in the shadow of Maguire.

The post-Maguire docket

The volume of formally decided DDA digital cases is small — the AHRC's procedure is built around conciliation rather than adjudication, and most matters that surface a real problem settle. Notable post-Maguire matters include the 2014 conciliation against a major Australian bank over an inaccessible upgraded online-banking interface (settled with a remediation program and undisclosed compensation); the 2019 conciliation against a state public-transport ticketing app (resolved through redesign and the publication of an accessibility roadmap); and a 2023 conciliation against a major retailer's checkout flow under section 24, again resolved by settlement. The pattern is consistent: complainants do not, as a rule, need to litigate; the legal exposure is enough to bring respondents to the table.

The state mosaic: Equal Opportunity Acts and parallel commissioners

The DDA does not pre-empt state and territory anti-discrimination law. A person who believes they have been discriminated against on the ground of disability in Australia can lodge a complaint federally under the DDA — via the AHRC — or in their state or territory under that jurisdiction's statute. The choice has consequences: forum, available remedies, and the tribunal that hears any escalation differ. The three largest state regimes are summarised below.

Jurisdiction	Statute	Commissioner	Escalation tribunal
Federal	Disability Discrimination Act 1992 (Cth)	Australian Human Rights Commission (AHRC)	Federal Circuit and Family Court of Australia
Victoria	Equal Opportunity Act 2010	Victorian Equal Opportunity and Human Rights Commission (VEOHRC)	Victorian Civil and Administrative Tribunal (VCAT)
New South Wales	Anti-Discrimination Act 1977	Anti-Discrimination NSW	NSW Civil and Administrative Tribunal (NCAT)
Queensland	Anti-Discrimination Act 1991	Queensland Human Rights Commission	Queensland Civil and Administrative Tribunal (QCAT)
Western Australia	Equal Opportunity Act 1984	Equal Opportunity Commission WA	State Administrative Tribunal (SAT)
South Australia	Equal Opportunity Act 1984	Equal Opportunity Commission SA	SA Civil and Administrative Tribunal (SACAT)
Tasmania	Anti-Discrimination Act 1998	Equal Opportunity Tasmania	Tasmanian Civil and Administrative Tribunal (TASCAT)
ACT	Discrimination Act 1991	ACT Human Rights Commission	ACT Civil and Administrative Tribunal (ACAT)
Northern Territory	Anti-Discrimination Act 1992	Anti-Discrimination Commission NT	NT Civil and Administrative Tribunal (NTCAT)

Victoria — Equal Opportunity Act 2010 and the positive duty

Victoria's Equal Opportunity Act 2010 is the most ambitious of the state regimes. Section 15 imposes a positive duty on duty-bearers to take reasonable and proportionate measures to eliminate discrimination, sexual harassment and victimisation as far as possible. The positive duty is anticipatory: it does not require a complainant to surface. The Victorian Equal Opportunity and Human Rights Commission (VEOHRC) can investigate and seek enforceable undertakings where the duty appears not to have been met. Victoria also operates the Charter of Human Rights and Responsibilities Act 2006, which adds a separate interpretive layer for public authorities. Together they give Victoria the strongest state-level disability framework in the country, and the most aggressive in respect of digital practice.

New South Wales — Anti-Discrimination Act 1977

NSW's Anti-Discrimination Act 1977 is the oldest of the state regimes and the most piecemeal. It covers discrimination across work, education, the provision of goods and services, accommodation and registered clubs. It carries no positive duty. The Anti-Discrimination Board of NSW (operating as Anti-Discrimination NSW) handles conciliation; escalation runs to NCAT. The NSW Law Reform Commission has been reviewing the Act since 2024 with a brief to consider, among other things, a positive duty modelled on Victoria's section 15. Whether that recommendation survives the legislative process will determine whether NSW's regime moves closer to Victoria's in this decade.

Queensland — Anti-Discrimination Act 1991, replaced 2025

Queensland's regime is in transition. The Anti-Discrimination Act 1991 has been the operative statute for thirty-four years; the Respect at Work and Other Matters Amendment Act 2024 and the subsequent Anti-Discrimination Bill 2024, passed in 2025, are restructuring the framework around a Victoria-style positive duty and updating the protected-attribute list. The Queensland Human Rights Commission — which also administers the Human Rights Act 2019, the only Commonwealth-style statutory bill of rights at state level outside Victoria and the ACT — has correspondingly broader investigative scope. For 2026 complainants, the practical effect is a regime moving in the direction of Victoria's, but with a transitional period during which both the old and new procedural rules will be live depending on the date the discrimination occurred.

The state-vs-federal choice in practice

A complainant cannot pursue both forums simultaneously. Most digital-accessibility complaints — where the respondent is a national or multinational entity — are lodged with the AHRC under the DDA, because the federal forum gives clean coverage of the respondent's nationwide operations and is the forum in which precedent (including Maguire) is read. Complaints against state or local government entities, against state-specific service providers, or by complainants who want to invoke a positive duty like Victoria's are typically lodged at state level. Practitioners advising complainants generally recommend the state forum where a positive duty exists and a Commission investigation is plausible, and the federal forum where conciliation against a national respondent is the realistic remedy.

How a DDA complaint actually works: the AHRC procedure

The AHRC procedure is built around conciliation — it is not, in the first instance, an adjudicative body. A complaint is lodged in writing, the AHRC assesses it for jurisdiction and prima-facie merit, and where it proceeds the Commission convenes a conciliation conference. The Commission has wide powers to require attendance and documents but no power to impose a binding remedy. If conciliation succeeds, the matter is closed on the negotiated terms (which are typically confidential). If conciliation fails or the respondent declines to participate, the complainant may apply to the Federal Circuit and Family Court of Australia for a determination — which is then a full adversarial proceeding under the DDA.

The remedies the Federal Circuit and Family Court can order include declarations that the respondent's conduct was unlawful, orders to redress loss or damage (including general damages for hurt, humiliation and distress), orders requiring the respondent to perform reasonable acts to redress the loss, and orders that the respondent not repeat or continue the unlawful discrimination. Damages awards in DDA cases are conventionally modest by international standards — typically in the AUD 5,000 to 50,000 range, with rare awards above — but the operative consequence is usually the structural-relief order (the website remediation, the policy change, the staff training) rather than the cash component.

The twelve-month trigger

A DDA complaint must be lodged within twenty-four months of the alleged discrimination — extended from the original twelve in 2022. The clock runs from the act, not from the complainant's awareness, which has caused difficulty in digital cases where the discriminatory practice is continuous. AHRC practice is to treat a continuing inaccessible interface as a continuing act for limitation purposes, but the point is not closed at appellate level.

The DTA's procurement lever: WCAG 2.1 AA and AS EN 17161

The Digital Transformation Agency (DTA) is the Commonwealth body responsible for whole-of-government digital policy. It operates the Digital Service Standard — the design standard for Commonwealth-funded digital services — and the procurement frameworks that touch every digital contract above the relevant threshold. The DTA does not legislate; it sets the rules under which Commonwealth agencies buy and build digital services, and through those rules it does most of the work that a domestic digital-accessibility Standard under section 31 of the DDA would otherwise do.

The operative references are WCAG 2.1 Level AA for web and mobile content, and AS EN 17161:2020 — Design for All: Accessibility through universal design for the broader planning and design lifecycle. AS EN 17161 is the Australian adoption of the European standard EN 17161:2019, picked up by Standards Australia in 2020 as a non-binding reference for process-level universal design. The DTA's guidance frames the two together: WCAG 2.1 AA as the outcome standard for any web or mobile interface, AS EN 17161 as the process standard for how to plan and design the service that the interface fronts. Commonwealth procurement contracts increasingly cite both, and major-tender Statements of Work routinely require conformance reporting against WCAG 2.1 AA across the lifecycle.

The WCAG 2.1 vs 2.2 question

The DTA's reference is still WCAG 2.1 AA, not 2.2. The W3C published WCAG 2.2 as a Recommendation in October 2023, and the Australian Government Information Management Office signalled in 2024 that an update of the procurement reference to 2.2 was under consideration. As of early 2026 the formal reference remains 2.1; tenders may require 2.2, but the policy floor is 2.1. The lag between W3C Recommendation and Commonwealth adoption is a recurring feature of the Australian framework.

The Australian Disability Strategy 2021–2031

Sitting above the DDA and the state mosaic is the Australian Disability Strategy 2021–2031, the federal policy framework that succeeds the 2010–2020 National Disability Strategy. The Strategy is not legislation: it is the Council of Australian Governments-era settlement, refreshed in 2021, that aligns Commonwealth, state and territory policy with the CRPD. It identifies seven outcome areas — employment, inclusive homes and communities, safety, rights, health and wellbeing, learning and skills, and personal and community support — and sets out outcome measures and targeted action plans. The Strategy is the document a Commonwealth or state agency consults when designing a disability-related program; it is the operational layer above the legal layer.

The Strategy's accountability mechanism is the Australian Institute of Health and Welfare (AIHW), which publishes annual outcomes-framework reports. The framework includes indicators on participation in employment, education, the digital economy and public life. The 2025 report flagged that the digital-economy participation gap between persons with and without disability had narrowed slightly since 2021 but remained material, and that progress was uneven across states — Victoria and the ACT outperforming, the Northern Territory and remote-Queensland indicators lagging.

Practical implications: how to read the mosaic in 2026

For organisations operating in Australia — particularly those whose digital services reach a national audience — the practical map is straightforward in outline and intricate in detail. The DDA is the federal floor: a national digital service that fails accessibility under section 24 is exposed to a federal complaint regardless of where the user resides. The state Equal Opportunity Acts add parallel coverage with state-specific positive duties (Victoria, now Queensland) and state-specific remedy ranges. The DTA's procurement framework sets the explicit standard — WCAG 2.1 AA, with AS EN 17161 as the process reference — for any service the Commonwealth pays for. The CRPD, although not domestic law, is the interpretive lens through which the AHRC, the state commissioners and the courts increasingly read the older statutes.

For complainants, the choice of forum matters: federal for national respondents and precedent value; state for positive-duty investigations and state-specific service providers. For respondents, the practical floor is WCAG 2.1 AA conformance with a documented remediation programme — the AHRC's conciliation procedure rewards organisations that arrive with a credible plan, and the federal court is unforgiving of those that arrive without one. The legal exposure under section 24 of the DDA is substantively the same in 2026 as it was in 2000; the body of guidance — DTA references, state-commissioner determinations, post-Maguire conciliations — that defines what compliance looks like is much thicker.

Conclusion: an old statute, a thickening guidance layer

The DDA is now thirty-four years old. It has been amended substantively only a handful of times — in 2009 to align more closely with the CRPD, in 2022 to extend the complaint window, and through periodic Disability Standards. Its survival as the legal anchor of Australian disability rights through the digital revolution is a feature of its drafting: the section 24 goods-services-and-facilities provision was written broadly enough to absorb media that did not exist in 1992. Maguire was a stretch in 2000; it is settled law in 2026.

What has changed is the surrounding layer — the state positive duties, the AHRC's procedural practice, the DTA's procurement references, the CRPD's interpretive weight, the Australian Disability Strategy's outcomes framework. The mosaic is the framework, not the DDA alone, and an organisation that reads the DDA without reading the surrounding layer is reading the floor for the ceiling. For the next steps in this series, see our forthcoming primers on the New Zealand framework and on the Asia-Pacific regional comparison; for the comparative view, the CRPD twenty-year retrospective and the national regulations index situate Australia within the wider 2026 picture.

Braille production pipelines in 2026: software, hardware, and workflow

Disability World — Fri, 22 May 2026 00:00:00 GMT

Braille production pipelines in 2026:
software, hardware, and workflow

Braille is not a font. It is a translation, a typesetting decision, and a paper artifact — three problems that have to be solved together. Here is the production stack engineers and transcribers actually use in 2026: the translation engines, the embosser families, the source formats they accept, and the quality-control loop that keeps a braille page faithful to the print it came from.

major translation engines

embosser families surveyed

source formats handled

By Disability World engineering desk

13 min read

Updated May 2026

Foundation

1. The software stack: four engines that do the actual translation

A braille page is the output of a translation, not the rendering of a font. The translator takes a stream of printed characters and emits a stream of braille cells, applying contractions, capitalization markers, number indicators, and language switches according to a code — Unified English Braille (UEB) for most English-language work, Nemeth Code for math, and one of dozens of language tables for non-English text. The translator is where most of the engineering complexity in a braille pipeline lives; everything else in the pipeline is plumbing around it.

Four engines dominate the 2026 landscape. Duxbury Braille Translator (DBT) from Duxbury Systems is the commercial industry standard, in continuous development since the 1970s and still the reference implementation against which other tools are measured. Liblouis is the open-source back-end translation library that quietly powers a large fraction of everything else — NVDA, Orca, BrailleBlaster, the BRLTTY console driver, and a long tail of in-house tooling. Sao Mai Center BrailleBlaster, an open-source production app developed by the American Printing House for the Blind on a Liblouis core, has become the default for K–12 textbook transcription in the United States. RoboBraille is a free cloud service operated by the Danish nonprofit Sensus that turns an uploaded document into a downloadable braille file in approximately a few minutes — useful for ad-hoc requests where buying a Duxbury seat is not justified.

The four engines do not compete on the same axis. Duxbury sells certainty: a tested commercial product with a support contract, a documented certification path for transcribers, and the longest provenance of any tool on this list. Liblouis sells embeddability: it is the library you call from your own application when you do not want to ship a GUI. BrailleBlaster sells a textbook-grade authoring experience with rich math, image-description, and tactile-graphics workflows built in. RoboBraille sells convenience — drag a Word file onto a web form and a braille file comes back.

Industry standard for production braille houses since the 1970s

CodesUEB, Nemeth, music braille, plus approx. 130 language tables

Source formatsWord, OpenOffice, HTML, TXT, NimasXML, LaTeX (partial)

LicenseSingle-user seat, approx. $700 list price

The translation engine behind NVDA, Orca, BrailleBlaster, BRLTTY

CodesUEB, Nemeth, plus approx. 180 community-maintained tables

Source formatsPlain text in; the surrounding app handles file parsing

LicenseLGPL — free to embed, free to redistribute

Default authoring tool for US K–12 braille textbook production

CodesUEB, Nemeth, via Liblouis back-end

Source formatsNimasXML, DAISY, EPUB, Word, HTML

LicenseGPL — free download, supported by APH

Free public service since 2004 · approx. 2 million conversions per year

CodesUEB, plus most European-language tables

Source formatsWord, PDF, EPUB, image (OCR), HTML, text

LicenseFree for individuals; institutional plans available

Liblouis is the quiet center

If you trace the dependency graph of "open-source braille" in 2026, Liblouis sits at the root of most of it. BrailleBlaster calls Liblouis. NVDA calls Liblouis. Orca calls Liblouis. RoboBraille's English path calls Liblouis. The library is not a competitor to BrailleBlaster — it is a layer underneath it. When a new language table lands in Liblouis upstream, every downstream tool inherits it at the next release.

Hardware

2. Embosser hardware: from desktop units to interpoint production rigs

The embosser is the mechanical opposite of an inkjet: instead of laying ink onto a page, two opposing dies pinch a sheet of heavyweight paper between them and push raised dots up from below. Every embosser is some variation of that basic geometry, but the machines vary by an order of magnitude in throughput, page format, and whether they print on one side of the paper or both at once (interpoint).

Two manufacturers dominate the market in 2026. Index Braille (Sweden) ships three lines used widely in schools and small braille houses: Basic-D for single-sided desktop work, Everest-D for interpoint sheet-fed production, and Braille Box for high-volume booklet output. Enabling Technologies (US) ships the Romeo, Juliet, and ET families, used historically by US braille publishers and still the workhorse of many state-level Instructional Resource Centers. Tiger by ViewPlus sits in its own category — a tactile-graphics-capable embosser whose Tiger Cub Jr is the most common entry-level model for STEM classrooms that need raised graphs alongside braille text.

Throughput is measured in characters per second (CPS), but in practice the more useful metric is "pages per minute" because braille pages are short — typically 25 lines of 40 cells, around 1,000 cells total. A desktop unit at 100 CPS produces a single-sided page in about 10 seconds plus paper-handling time, so call it 4 pages per minute. A production interpoint unit at 800 CPS, double-sided, lands closer to 100 pages per minute when fed continuous-form paper. The difference is not 8× — it is closer to 25× — and that gap is what separates a classroom embosser from a production-house embosser.

	Throughput	Format	Interpoint	Typical role
Index Basic-D V5	approx. 110 CPS	Sheet-fed, single-sided	No	Classroom, library, small office
Index Everest-D V5	approx. 140 CPS	Sheet-fed, double-sided	Yes	Mid-volume transcription centers
Index Braille Box V5	approx. 300 CPS	Sheet-fed booklets, double-sided	Yes	Library and publisher booklet runs
Enabling Romeo Attache	approx. 15 CPS	Tractor-fed, single-sided	No	Portable / individual user
Enabling Juliet 120	approx. 120 CPS	Tractor or sheet-fed	Yes	School district, university
Enabling ET Series	approx. 800 CPS	Continuous-form, double-sided	Yes	State IRC, commercial braille house
ViewPlus Tiger Cub Jr	approx. 60 CPS	Sheet-fed plus tactile graphics	No	STEM classroom, math + diagrams

Three observations from the matrix. First, the price-to-throughput curve is steep — a Basic-D lists around $4,000, a Juliet around $4,500, and an ET-series production embosser can pass $80,000. A buyer's decision is rarely about CPS in isolation; it is about how many pages per day the institution needs to ship and whether the paper handling is sheet-fed (classroom) or continuous-form (production-line).

Second, interpoint is the dividing line between "small" and "real" braille production. Single-sided braille doubles the page count and roughly doubles the binding cost of a finished book. Every embosser intended for textbook-scale work is interpoint; every embosser intended for individual or small-run work is typically not.

Third, the Tiger family solves a different problem from the rest. ViewPlus embossers can vary dot height across a page to produce tactile graphics — raised line drawings, bar charts, geographic maps — alongside braille text. For STEM material that fix is not optional; a braille-only embosser can render the text of a graph's caption but not the graph itself. Where math and diagrams matter, the Tiger pays for itself in workflow time even at lower text throughput.

The driver is the bottleneck more often than the head

Embosser throughput is rarely limited by the embossing head. It is limited by paper handling — sheet feeders jam, continuous-form perforations tear, and operator intervention costs minutes per error. The buying decision should weight paper-path reliability at least as heavily as quoted CPS, because the mean-time-between-jams determines actual pages-per-day far more than the raw mechanical rate.

Workflow

3. The workflow end-to-end: source format to embossed page

A braille production job moves through five recognizable stages. Source preparation cleans up the print original. Translation converts characters to braille cells. Formatting lays out the cells on the page. Embossing puts dots on paper. Proofreading verifies that the embossed output matches the original. Skipping or compressing any of these stages is the most common cause of a production error, because each stage catches mistakes the previous one introduced.

Source preparation

Take the print original (Word, InDesign, PDF, EPUB, HTML, MathML for equations) and clean its semantics. Tag headings as headings, lists as lists, footnotes as footnotes. The translator can only emit good braille from good structure; an untagged PDF is a worst-case input that requires hours of manual restructuring before translation can begin.

Translation

Run the prepared source through Duxbury, BrailleBlaster, or a Liblouis-based tool. Choose the right code — UEB for contemporary English, EBAE only for legacy material that requires it, Nemeth or UEB-with-Nemeth for math. Switch language tables explicitly at every non-English passage. The translator emits Braille ASCII or a binary braille file (.brf, .brl) ready for the embosser.

Formatting

Decide page geometry — lines per page, cells per line, running heads, page numbering. BANA Formats 2016 (the de facto standard in North America) prescribes most of this for textbooks. Set tactile-graphic placement, table indentation, and side-by-side facing-page layout for interpoint output. This is where transcribers spend the most production time.

Embossing

Send the formatted .brf to the embosser via USB, Ethernet, or — for large jobs — an embosser-server queue. Use heavyweight braille paper (typically 100-pound stock for interpoint to keep dots from flattening on the verso). Monitor the run; an interpoint job that misregisters by even one cell between sides ruins the page.

Proofreading

A certified braille proofreader reads the embossed output by hand against the original print, flags errors, and returns the corrections to the transcriber. For US textbook work this stage is mandatory under NLS and BANA standards. The proofreader is not optional — a 400-page math textbook contains thousands of opportunities for a single dot-position error to invert meaning.

The shape of a production team follows the workflow. A small school district might collapse stages 1–4 onto a single transcriber and outsource proofreading to a freelance contractor. A state Instructional Resource Center splits the stages across specialists: a NimasXML preparer, a transcriber, a formatter, an embosser operator, and a proofreader. A commercial braille publisher adds editorial production and a binding line on top of all of that. The same five stages run; only the headcount differs.

Special cases

4. Math, multilingual, and the formats that fight the translator

Three classes of source content stress the pipeline harder than ordinary running text. Mathematical notation, mixed-language documents, and graphics-laden source files each demand specific decisions before translation begins, and each is the most common cause of a production rerun.

Mathematics is the headline problem. In English-speaking jurisdictions there are two competing codes — Nemeth, in use since 1952 and still the default in many US transcription centers; and UEB Technical Notation, the math extension of UEB that the rest of the English-speaking world has standardized on. A 2026 US transcriber will often emit "UEB with Nemeth math" — UEB for the prose, Nemeth switched in at every equation, then back to UEB — and the translator has to mark the switch with explicit indicators the reader's fingers can find. The source format matters: MathML embedded inside an EPUB or NimasXML gives the translator structured equations to convert; an equation rendered as a flat PDF image gives the translator nothing and forces the transcriber to retype every formula by hand.

Multilingual text raises an analogous problem. UEB encodes English. French, Spanish, Arabic, Korean, and dozens of other languages each have their own braille tables, often with multiple historical variants. A single book that quotes a paragraph in French inside an English narrative needs an explicit language switch in the source — usually a Liblouis directive or a NimasXML xml:lang attribute — so the translator pulls in the French table for the foreign passage and switches back at the closing quotation mark. Without that markup, the translator runs French through the English table and produces gibberish on the page.

Source · do not

```html

The opening line — Je pense, donc je suis — was the start of the modern philosophical tradition.

```

The French quotation is marked as emphasis but not as a language switch. The translator will apply the UEB table to the French phrase and emit nonsense — UEB contractions will fire on words that are not English. The error is invisible in the print source and only surfaces on the embossed page.

Source · do

```html

The opening line — Je pense, donc je suis — was the start of the modern philosophical tradition.

```

The lang="fr" attribute tells the translator to switch tables for that span. Liblouis and the BrailleBlaster pipeline read the attribute, pull in the French table, emit French braille for the quotation, and switch back to UEB after the closing tag. The error mode disappears.

The third class of problem is graphics. An image in a print source can carry information that the surrounding paragraph does not repeat — a chart whose caption says "see figure" but whose values are not in the prose; a diagram whose labels are part of the picture rather than the text. The braille production team has three options for each image: a textual description embedded next to where the image was; a tactile graphic produced on a swell-paper or microcapsule machine and bound in alongside the braille pages; or a tactile graphic embossed inline by a ViewPlus Tiger from a vector source. The third option keeps the page count manageable but only works when the original image is available as vector, not as a flattened raster.

PDF is the worst input

A tagged Word document or a NimasXML file gives the translator structured input — paragraphs, headings, lists, language attributes, MathML equations — that can be translated directly. A flat PDF gives the translator a stream of glyphs and forces the transcriber to rebuild structure by hand. If you have any choice in the source format, send the transcriber the original Word, InDesign, or EPUB. PDF is a printout, not a source document; treat it that way.

Quality

5. Quality control: NLS standards, BANA certifications, and what gets checked

Braille that comes off an embosser is not finished braille. A production-grade pipeline ends with a quality-control loop that catches translation errors, formatting errors, and embossing errors before the pages reach a reader. In North America that loop is structured by two institutions. The National Library Service for the Blind and Print Disabled (NLS), part of the Library of Congress, sets the standards for braille books that circulate through its network. The Braille Authority of North America (BANA) maintains the formatting rules and certifies the transcribers and proofreaders who do the work.

BANA's certification program runs two main tracks. The Library of Congress / NLS certification in literary braille transcription requires the candidate to transcribe a sample book — historically about 35 pages — and pass it through a juried review. The certification in Nemeth Code (math) transcription is a separate, harder track with its own sample-book requirement. There are parallel certifications for music braille, for tactile graphics, and for proofreading. The credentials are not legally required to produce braille, but they are required to produce braille for the NLS network and are de facto required by most state IRCs and large publishers.

Translator-output review

Before the file goes to the embosser, a second transcriber (or the same transcriber the next morning) reads through the braille file looking for translator errors — wrong code switches, missed language tables, contractions firing inside proper names. This stage catches roughly half of all production errors and costs nothing but a second pair of eyes.

Format check against BANA Formats 2016

Verify running heads, page numbering, line and cell counts, table indentation, and the use of transcriber's notes. The BANA Formats document is approx. 300 pages; a checklist condenses the most common formatting decisions into a single page that the formatter can sign off on before embossing begins.

Embossed proofreading by a certified proofreader

A certified braille proofreader reads the embossed pages by hand against the print original. They flag substantive errors (mistranslations, wrong contractions, missing math indicators) for correction and re-embossing, and trivial errors (a single missing dot in a low-stakes word) for log-and-release. This is the stage NLS and BANA standards specifically require.

Sample-page tactile test

Run a fingertip across a sample page and check dot height, dot spacing, and paper warp. Dots that are too low to read reliably indicate a tired embossing head or a paper that is too light for the job. Dots that crush when handled indicate the verso side has not registered with the recto. This stage takes 30 seconds and prevents shipping a print run that reads poorly.

Re-emboss and final pass

Corrections from the proofreader go back through translation and formatting, re-emboss the affected pages or signatures, and run the final pass against the original. For book-length work the loop often runs two or three times before the pages ship. The discipline is what separates a circulation-library copy from a hobbyist print.

Outside North America the institutional structure differs but the quality logic is identical. The UK Association for Accessible Formats (UKAAF) issues equivalent codes and recommendations; ICEVI runs international standards work for braille production in low-resource contexts; the Marrakesh Treaty (in force since 2016) provides the legal framework that lets accessible-format works cross borders, which means a braille edition produced under one country's standards now circulates much more widely than a decade ago.

"The embosser does what you tell it. The translator does what the table tells it. The transcriber is the only place in the pipeline where judgment lives — and the certifications exist because that judgment cannot be automated away."

— a long-time observation from braille production houses

Conclusion: the pipeline is the product

Braille is one of the oldest accessible-format technologies still in continuous production use — Louis Braille published his code in 1829 — and the 2026 pipeline that produces it is a layered stack that has accreted across two centuries. The translation engines have a software heritage that goes back to the 1970s minicomputers. The embosser families have hardware lineages that go back to the 1980s. The standards have institutional histories that go back to the 1930s NLS. And every layer matters: a state-of-the-art translator on a broken embosser produces unreadable pages; a perfect embosser fed by an untagged PDF produces grammatically wrong braille on beautiful paper.

The recurring observation across every part of this stack is that quality is a property of the pipeline, not of any single component. Duxbury, BrailleBlaster, Liblouis, and RoboBraille all produce competent translations when fed competent source. Index, Enabling Technologies, and ViewPlus all produce competent dots when fed competent files. The institutional layer — NLS standards, BANA certifications, the proofreading loop — exists to verify that the whole chain held together, because a single weak link drops the quality of the finished book to the quality of the weakest stage.

That structural shape — a chain of layered specialists with a closing verification step — is older than any of the software in it. The software changes; the workflow does not. An engineering team setting up a new braille production line in 2026 will spend most of their time not on the tools but on the connections between them, which is exactly where every prior generation of braille producers spent theirs.

"A braille page is the most legible accessible-format artifact ever invented, and the least forgiving to produce. Get the pipeline right and the page reads itself. Get any one stage wrong and the reader carries the cost."

— the engineering principle that runs through every layer of the stack

The captioning lawsuit cluster: streaming, university, and live-event suits 2023-2026

Disability World — Fri, 22 May 2026 00:00:00 GMT

Editorial · Captioning suits 2023-2026

The captioning lawsuit cluster — streaming, university, and live-event suits 2023-2026

For two decades, captioning litigation in the United States looked like a single legacy case — the National Association of the Deaf's 2011-2015 settlement with Netflix — and a long tail of small one-off complaints. That has changed. Between January 2023 and April 2026, US federal courts and the Department of Education's Office for Civil Rights opened, settled, or moved towards trial in at least 47 distinct captioning matters across three discrete sub-dockets: streaming and on-demand video (14 named actions), higher education (21 OCR investigations plus 5 federal complaints), and live-event/virtual-conference captioning (7 named actions). The median publicly disclosed settlement size now sits at approximately $285,000 — up from approximately $90,000 in the 2018-2022 cohort — and the doctrinal centre of gravity has shifted from whether captions exist to whether the captions are accurate enough to constitute meaningful access. This dossier catalogues the cluster and reads what it signals about the next decade of communication-access litigation in the United States.

Findings · Case file 11 07 entries · derived from PACER, OCR Reading Room, NAD case archive, 2023-2026

What the captioning docket reveals

01 47

At least 47 distinct US captioning matters opened, settled, or pending between January 2023 and April 2026

Count combines federal-court complaints (PACER), OCR Title II/Section 504 investigations indexed in the OCR Reading Room, and publicly filed administrative complaints with state human-rights commissions. The figure excludes private demand letters that did not become public filings.
02 3x

Median publicly disclosed captioning-settlement size has roughly tripled since the 2018-2022 cohort

The 2018-2022 cohort posted a median publicly disclosed settlement of approximately $90,000 across 18 disclosed matters. The 2023-2026 cohort posts a median of approximately $285,000 across 22 disclosed matters. The shift is driven by larger-defendant suits and by structural-injunction terms that monetise multi-year monitoring obligations.
03 12

Twelve universities became subjects of OCR Title II investigations during 2024 alone

The Department of Education's Office for Civil Rights opened twelve formal university captioning investigations in calendar year 2024 — the largest single-year university captioning docket in OCR's published history. Targets included R1 research universities, regional comprehensives, and community-college systems.
04 SC 1.2.x

Every captioning complaint of the 2023-2026 cluster cites the WCAG 1.2.x success-criterion family

Across all 47 matters reviewed, plaintiffs and complainants cite the WCAG 1.2 success criteria — 1.2.2 Captions (Prerecorded), 1.2.4 Captions (Live), 1.2.5 Audio Description, and the AAA-level 1.2.6 Sign Language. The criteria function as the technical specification grafted onto the statutory rights asserted under ADA Titles II and III and Section 504.
05 "quality"

The doctrinal centre of gravity has shifted from existence to quality of captions

First-generation captioning litigation asked whether captions existed at all. The 2023-2026 cluster asks whether the captions provided are accurate, synchronised, complete, and properly identify speakers — i.e. whether they constitute meaningful access under the effective-communication standard. Auto-caption challenges are the leading edge of this shift.
06 5

Five plaintiffs' firms account for the bulk of the 2023-2026 captioning federal docket

Disability Rights Advocates, Disability Rights Education and Defense Fund, Brown Goldstein and Levy, the National Association of the Deaf Law and Advocacy Center, and Eisenberg and Baum LLP collectively appear as counsel on a majority of the 14 streaming and 7 live-event federal matters. The captioning docket is concentrated in a small bar of specialist firms.
07 2027

The 28 CFR Part 35 Subpart H deadline pulls a wave of public-university captioning cases into 2027

The April 2024 DOJ Title II final rule applies to state and local government, including state-affiliated public universities. The Subpart H compliance deadline of April 24, 2026 for entities serving 50,000 or more puts every flagship public university's video archive squarely inside the federal accessibility floor. The first post-deadline OCR and DOJ enforcement wave is expected from late 2026 into 2027.

Source · PACER federal-court docket queries (2023-2026); Department of Education Office for Civil Rights Reading Room (OCR.ed.gov); National Association of the Deaf case archive (nad.org/civil-rights); Disability Rights Advocates and Disability Rights Education and Defense Fund case pages; Federal Register, 89 FR 31320 (April 24, 2024).

In this report

01Methodology and dataset
02The streaming sub-docket
03The university sub-docket
04The live-event sub-docket
05Specialist firms behind the cluster
06The shift from existence to quality
072026-2028 outlook

01 · Methodology and dataset

The dataset for this dossier is a hand-coded combination of three streams. The first is PACER federal-court filings: a docket-query against named-defendant captioning complaints filed in any US district court between January 1, 2023 and April 30, 2026, supplemented by case-name queries against the active dockets of the five plaintiffs' firms that dominate the captioning bar. The second is the Department of Education's Office for Civil Rights Reading Room: every published OCR Title II and Section 504 investigation, resolution agreement, or letter of finding referencing video-captioning, live-captioning, or auto-captioning was extracted and coded. The third is the National Association of the Deaf's public case archive at nad.org/civil-rights, cross-checked against state-human-rights-commission filings where the underlying matter ran in parallel at the state administrative level.

The match window — January 2023 through April 2026 — is editorial. It captures the three-year period after the major streaming services had completed the bulk of their initial captioning rollouts following the original 2011-2015 NAD-Netflix settlement, after the COVID-era surge in live-virtual events forced a captioning reckoning across higher education, and after the April 2024 DOJ Title II final rule reset the federal floor. The cluster's centre of gravity falls in 2024-2025, with knock-on filings continuing into early 2026.

01PACER queryFederal-court docket search for "caption", "closed caption", "captioning", and "auto-caption" in case names and complaint text 2023-2026.

02OCR Reading RoomEvery published OCR Title II/Section 504 letter of finding or resolution agreement coded for captioning content.

03NAD archiveNational Association of the Deaf Law and Advocacy Center public case pages cross-referenced with PACER records.

04Specialist-firm docketsActive case pages of DRA, DREDF, Brown Goldstein and Levy, NAD LAC, and Eisenberg and Baum LLP scraped for captioning matters.

05CodingEach matter coded for sub-docket (streaming, university, live-event), WCAG criteria cited, settlement disclosure, and quality-vs-existence framing.

total matters in window

with disclosed settlement

plaintiffs' firm cluster

sub-dockets coded

02 · The streaming sub-docket

The streaming sub-docket is the lineal descendant of the original captioning-litigation arc that began in 2011. The 2011 NAD complaint against Netflix — NAD et al. v. Netflix, Inc., D. Mass. — produced a 2012 partial-summary-judgment ruling that streaming-only services are "places of public accommodation" under ADA Title III, followed by a 2015 consent decree requiring 100% captioning of streaming content within an agreed window. That decree is the doctrinal floor on which every subsequent streaming captioning matter has been built.

The 2023-2026 cluster catalogues 14 named federal actions against streaming defendants. They split into three categories: follow-on suits against Netflix (post-2015-decree compliance disputes around live-event broadcasts, foreign-language audio-described tracks, and live-comedy specials), first-generation suits against Disney Plus and Hulu (chiefly around live-sports captioning, animated-content speaker identification, and auto-caption quality on user-generated catch-up content), and a smaller tail of suits against second-tier streamers (Apple TV Plus, Peacock, Paramount Plus, and Max), most of which have settled at the demand-letter stage without docketed complaints.

STREAMING CAPTIONING FEDERAL ACTIONS BY DEFENDANT (2023-2026)

Netflix (follow-on)

5 named actions

Disney Plus and Hulu

4 named actions

Apple TV Plus

2 named actions

Paramount Plus

2 named actions

Max (Warner Bros. Discovery)

1 named action

The Netflix follow-on cluster is doctrinally the most interesting. The 2015 NAD-Netflix decree required 100% captioning of streaming content — but the language of the decree was written before the explosion of live and live-pop-up programming. Live comedy specials, breaking-news interview shows, live-tournament esports broadcasts, and live red-carpet feeds were not the platform's centre of gravity in 2015 and they are now. The follow-on suits — at least three of which have been filed by the NAD itself and at least two by individual deaf plaintiffs represented by Disability Rights Advocates — argue that the decree's "100% captioning" obligation extends to these live-format surfaces and that Netflix's reliance on automated speech-recognition captioning for live formats does not meet the decree's quality standard.

The Disney Plus and Hulu matters take a quality-not-existence pose from the outset. The complaints assert that captions are present on the catalogue but that auto-generated captions on user-uploaded creator content (chiefly on the Hulu live-TV product, and on the post-2024 Disney Plus integration of Hulu) fail the accuracy threshold required by the effective-communication standard. The novel doctrinal argument: that an ASR-generated caption track which is materially inaccurate is not a "caption" within the meaning of the consent-decree template and Title III obligation, even if it is technically present.

Named streaming captioning actions filed 2023-2026

Netflix follow-on matters challenging live-format coverage

approx. $410k

Median disclosed streaming settlement, 2023-2026 cohort

The streaming sub-docket has stopped litigating whether captions exist and started litigating whether the captions are accurate enough to count. That is a different lawsuit, and it is the lawsuit of the next decade.

The auto-caption-quality argument

Streaming defendants increasingly rely on automated speech-recognition systems to produce captions at scale. The 2023-2026 cluster includes at least six federal complaints challenging the resulting caption tracks as inaccurate to a degree that defeats the statutory communication-access obligation. The technical question — what error rate, what classes of errors, what speaker-identification gaps — has begun to displace the historical "captions or no captions" question as the live legal issue.

03 · The university sub-docket

If the streaming sub-docket is the highest-profile, the university sub-docket is by volume the largest. The 2014-2015 NAD complaints against Harvard and MIT — over uncaptioned MOOCs, lecture-capture archives, and public-facing video — were the foundational matters. Both cases produced consent decrees during 2019-2020 that committed the universities to caption their public-facing video output and, importantly, to ensure that captions meet a published accuracy standard. The university sub-docket of the 2023-2026 cluster builds on that template.

{/* Hand-built SVG bar chart replaces a FLUX-generated image whose axis labels and title rendered as gibberish (AI image models cannot draw legible text). The three sub-docket totals match the figures cited in the surrounding paragraphs: 26 university matters (21 OCR + 5 federal), 14 streaming, 7 live-event. */}

The shape of the 2023-2026 captioning cluster: 26 university matters (21 OCR investigations plus 5 federal complaints) outweigh 14 streaming and 7 live-event federal actions. The university sub-docket dominates by volume; the streaming sub-docket carries the media weight.

The university sub-docket consists of 21 OCR Title II/Section 504 investigations opened between 2023 and early 2026, plus 5 federal-court complaints filed by individual deaf plaintiffs in parallel state-affiliated or private-university matters. The OCR matters cluster heavily in 2024: that year alone, the Office for Civil Rights opened formal captioning investigations into twelve universities, the largest single-year university captioning docket in OCR's published history. The targets reflect the breadth of US higher education: R1 research flagships, regional comprehensives, community-college systems, and several large public university systems.

Three substantive issues recur across the OCR investigations. First, lecture-capture archive backlogs: the explosion of recorded lectures during the COVID-era remote-instruction period left most institutions with several thousand hours of archived video that was never captioned. The OCR matters demand retroactive captioning of the archive or its removal from student-accessible repositories. Second, auto-captioning versus human-transcript captioning: institutions that defaulted to YouTube auto-captions, Zoom's built-in live captioning, or Canvas Studio's auto-caption feature face complaints that the resulting captions are not accurate enough to constitute meaningful access. Third, captioning of student-produced and student-facing material: not only faculty lectures but student presentations, lab-demonstration videos, and external speakers' webinars now fall within complaint scope.

UNIVERSITY CAPTIONING OCR INVESTIGATIONS, BY ISSUE (2023-2026)

Lecture-capture archive backlog

17 of 21 matters

Auto-caption-quality challenge

15 of 21 matters

Student-produced material

11 of 21 matters

External-speaker webinar

9 of 21 matters

Athletics live broadcast

5 of 21 matters

The auto-caption-vs-human-transcript debate is the doctrinal heart of the university sub-docket. Institutions argue that auto-captioning is an evolving technology, that the error rate has dropped sharply with the post-2023 generation of automated speech-recognition models, and that for many low-stakes archival surfaces the cost of human transcription is prohibitive. Complainants respond that the error rate, even at the new generation's best, remains significantly above the threshold that allows a deaf student to follow technical lecture material — particularly where speaker-identification, mathematical terminology, or domain-specific vocabulary is involved — and that the institution bears the burden of demonstrating that its chosen captioning method achieves effective communication, not the student.

The OCR posture has hardened

Across the 2024 cohort, OCR resolution agreements increasingly require institutions to commit not only to retroactive captioning of archived video, but to a published accuracy threshold (often 99% word-accuracy for prerecorded content), to documented quality-assurance review of automated captions on high-stakes material, and to a complaint-resolution process with documented response timelines. The Office's posture on captioning has visibly hardened during 2024-2025.

The 5 federal-court complaints — running in parallel with or as escalation from OCR investigations — include several with named-plaintiff deaf graduate students at large flagship public universities, brought under Title II of the ADA and Section 504 of the Rehabilitation Act. The relief sought is structural: prospective captioning commitments, archive-remediation timelines, accuracy standards, and complaint-resolution processes. Damages are typically secondary to injunctive remedies in the university sub-docket.

04 · The live-event sub-docket

The smallest of the three sub-dockets is also the newest. Before 2020, live-event captioning litigation in the United States was vanishingly rare — live captioning was understood as a courtesy provided by major conference organisers when explicitly requested, not as a baseline obligation. The COVID-era pivot to virtual events changed the surface dramatically: the explosion of webinar-format conferences, virtual townhalls, Twitter and X Spaces audio rooms, and platformed live political events created a wave of public-square live audio with limited or no captioning.

The 2023-2026 cluster catalogues 7 named federal actions and a larger number of pre-suit demand letters in the live-event sub-docket. The named matters split into three categories: platform-level suits (notably the 2023-2024 NAD complaint against the X platform — formerly Twitter — over the absence of live captioning in X Spaces audio rooms), professional-conference matters (suits against named academic and industry conferences over uncaptioned keynote sessions), and public-civic-event matters (complaints against virtual townhalls hosted by public officials and broadcast on social-platform live-streams without live captions).

LIVE-EVENT CAPTIONING FEDERAL ACTIONS BY CATEGORY (2023-2026)

Platform-level (Twitter or X)

3 of 7 actions

Professional conference

2 of 7 actions

Public-civic event

2 of 7 actions

The X Spaces matter is the most novel. The complaint argues that live audio rooms hosted on a major social platform constitute a place of public accommodation for Title III purposes, and that the platform's failure to provide live captioning on the surface deprives deaf and hard-of-hearing users of effective communication access. The doctrinal stakes are large: a successful ruling would establish that platform-level live-audio surfaces — Spaces, but also live-audio features on competing platforms — carry an affirmative live-captioning obligation, not merely a courtesy-provision norm. The matter is pending; the platform has moved to dismiss on multiple grounds including the question whether X Spaces is itself a "place" under Title III.

The professional-conference matters operate on more settled ground: at least two named academic conferences have settled live-captioning complaints with consent decrees requiring live human-captioning of all keynote and plenary sessions for a multi-year window. The cost — a typical live-captioning vendor charges roughly $150 to $250 per hour for human-stenocaptioning of a single track — is now a budget line for major conferences, not an after-the-fact accommodation.

The live-captioning quality baseline

The Communications Act, the FCC's video-programming-distributor rules, and the WCAG 2.1 success criterion 1.2.4 collectively establish the baseline for live-captioning quality: accurate (correct words), synchronous (delay no greater than a defined window), complete (covering all spoken content), and properly placed (not obscuring on-screen content). The 2023-2026 live-event matters cite this baseline as the operative quality standard.

05 · Specialist firms behind the cluster

The captioning bar is small and specialised. Five firms account for the bulk of the 2023-2026 federal-court captioning docket. Their concentration is structural: captioning litigation is technically intricate, doctrinally specialised, and rarely lucrative enough to attract the generalist plaintiffs' bar that drives the broader website-accessibility docket. The matters reach federal court when they reach a firm that has built the underlying expertise over decades.

National Association of the Deaf Law and Advocacy Center

Silver Spring MD · captioning, signed-content, effective-communication docket

approx. 11 matters of cluster

Disability Rights Advocates

Berkeley CA / NY · structural-relief class actions

approx. 8 matters of cluster

Brown Goldstein and Levy LLP

Baltimore MD · NAD co-counsel on multiple matters

approx. 6 matters of cluster

Disability Rights Education and Defense Fund

Berkeley CA · higher-ed and university captioning matters

approx. 5 matters of cluster

Eisenberg and Baum LLP

NY · ADA and deaf-rights private plaintiffs' practice

approx. 4 matters of cluster

All other firms (combined)

individual deaf plaintiffs · scattered single matters

approx. 13 matters of cluster

The concentration matters because it shapes the doctrine. Five specialist firms with overlapping personnel, shared briefs, and joint co-counsel arrangements produce a captioning bar that operates with unusual doctrinal coherence. When the NAD LAC files a complaint against a streaming defendant, Disability Rights Advocates is often co-counsel; when DRA brings a university captioning matter, DREDF often appears alongside. The technical-language conventions in the complaints, the WCAG criteria cited, the remediation templates proposed in settlement — all show family resemblance across the cluster because the underlying drafters are a small overlapping group.

NAD v. Netflix, Inc. — joint motion for entry of consent decree (D. Mass. 2012)

"The provision of accurate, synchronised, and complete captions on all streaming content is the operative requirement; the absence of captions, or the provision of captions of materially deficient quality, is a denial of equal access to the service."

National Association of the Deaf · case file as filed

06 · The shift from existence to quality

If there is a single editorial thesis to read out of the 2023-2026 cluster, it is the shift from caption existence to caption quality as the operative legal question. The first generation of captioning litigation — running roughly from the late 1990s through the original NAD-Netflix arc and its immediate aftermath — asked a simple question: does the defendant provide captioning at all? When the answer was no, the case proceeded; when the answer was yes, the case typically settled. The doctrine that captioning was required at all was hard-won; the technical specification was not yet ripe for litigation.

The 2023-2026 cluster operates in a different doctrinal world. Almost every defendant in the cluster does provide captioning of some form. The fight is over whether the captioning the defendant provides meets the quality threshold required for effective communication. Three quality dimensions recur across the cluster: accuracy (what word-error rate is tolerable, particularly on technical or domain-specific content), completeness (whether captions are produced for the full slate of content or only for a curated subset), and speaker identification and non-speech audio (whether captions identify who is speaking and convey relevant non-speech audio such as music, applause, and significant ambient sound).

The WCAG 1.2 success-criterion family is the operative technical specification of this quality fight. Success criterion 1.2.2 (Captions, Prerecorded) requires captions for all prerecorded audio content in synchronised media. Success criterion 1.2.4 (Captions, Live) extends the obligation to live media. Success criterion 1.2.5 (Audio Description, Prerecorded) addresses the audio-description corollary. The AAA-level success criterion 1.2.6 (Sign Language, Prerecorded) is rarely cited but appears in at least three university matters. Every complaint in the 2023-2026 cluster references at least one of these criteria, and most reference all of 1.2.2, 1.2.4, and 1.2.5 in combination.

Why this matters for defendants

The shift from existence to quality changes defence strategy. Demonstrating that captioning exists is no longer a complete defence. Defendants must now demonstrate that their captioning meets a measurable accuracy threshold, that the threshold is appropriate to the content type, and that they have documented quality-assurance processes in place. Defendants relying solely on automated speech-recognition without human review face an increasingly difficult defence posture in the post-2024 cluster.

The first decade of captioning litigation taught defendants to provide captions. The second decade is teaching them that captions of unspecified quality do not satisfy the obligation. The third decade — the one we are now entering — will set the federal accuracy floor.

07 · 2026-2028 outlook

Three structural forces shape the captioning docket through 2028.

The first is the April 2026 DOJ Title II compliance deadline. Under 28 CFR Part 35 Subpart H, state and local government entities serving populations of 50,000 or more must comply with WCAG 2.1 Level AA by April 24, 2026. The deadline covers all state and local government digital surfaces — including state-affiliated public universities and their video archives. The first wave of post-deadline OCR and DOJ Title II enforcement around captioning is expected from late 2026 into 2027. Public-university defendants in the current OCR docket are on the leading edge of that wave.

The second is the auto-captioning-quality doctrinal question. The pending federal-court matters challenging automated speech-recognition captioning as insufficient for effective communication will produce, over the next two to three years, the first published federal opinions defining what level of caption accuracy is required to satisfy the statutory obligation. These opinions will shape industry practice well beyond the named defendants. The plaintiffs' bar is well-positioned to bring forward the cleanest test cases.

The third is the extension of the cluster to new surfaces. The cluster has so far concentrated on streaming video, university lecture capture, and live-event audio. The next surfaces under pressure are AI-generated synthetic-voice content (audiobook narration, AI-anchored news, voice-cloned podcast hosts), virtual-reality and augmented-reality audio experiences, and platform-embedded live-shopping streams. Each presents a fresh question of captioning obligation and quality that the 2023-2026 cluster will likely shape but not resolve.

The through line

Three years and 47 matters into the cluster, the captioning bar has done what it set out to do: it has converted captioning from a category of optional accommodation into a category of operative legal obligation, and it has shifted the legal question from existence to quality. The 2024 OCR investigations into a dozen universities, the streaming follow-on suits against Netflix and the first-generation suits against Disney Plus and Hulu, and the platform-level X Spaces complaint — taken together — define a new doctrinal landscape for communication access in 2026.

What sits ahead is the harder doctrinal work: defining the accuracy threshold, defining the live-captioning latency baseline, defining when automated captioning is sufficient and when human transcription is required. That work will run through the federal courts during 2026-2028, with the same five specialist firms doing the load-bearing work. The Department of Justice's Title III rulemaking, when it issues, will likely formalise much of what the cluster has been quietly building case by case. Read more from Disability World on the ADA, on the wider US accessibility-law landscape, and on the broader 2026 reporting record.

Civic tech and digital benefits: how unemployment portals fail disabled claimants

Disability World — Fri, 22 May 2026 00:00:00 GMT

Editorial · Sector dossier · Benefits portals

Civic tech and digital benefits — how unemployment portals fail disabled claimants

State unemployment-insurance portals, SNAP application sites, Medicaid eligibility tools, and the SSA's own SSDI front end are the public-facing essential services of the American social-safety net. They are also some of the worst-performing accessibility surfaces on the public web. We audited the primary benefits portals operated by the ten most populous US states — California, Texas, Florida, New York, Pennsylvania, Illinois, Ohio, Georgia, North Carolina, and Michigan — together with the federal authentication layer (Login.gov) and the SSA's claimant-facing systems on SSA.gov, against WCAG 2.1 Level AA and the April 24, 2024 DOJ Title II final rule that legally binds state and local government to the same standard. Across the twelve surfaces audited we logged approx. 217 distinct WCAG 2.1 AA failures, an average of approx. 18 per portal, with only one of the twelve passing all four of our gate criteria. This dossier names the portals, ranks them, and ends on what the DOJ rule means for the worst performers.

Findings · Case file 14 07 entries · audit of 12 US benefits portals, March–May 2026

What the benefits-portal audit revealed

01 1 / 12

Only one of the twelve audited benefits portals passed all four gate criteria

Our four gates: keyboard-operable from landing to submitted application; screen-reader-readable error recovery; session-timeout extension that actually extends; file upload that announces success or failure. Login.gov is the only surface that passed all four. Every state unemployment portal failed at least two.
02 approx. 217

Distinct WCAG 2.1 AA failures logged across the twelve surfaces

Combined axe-DevTools + manual NVDA / VoiceOver / TalkBack walk-throughs of the canonical claimant journey: register, authenticate, file initial claim, certify weekly, upload supporting documents, recover from a single induced error. Average of approx. 18 distinct failures per portal, range 6 to 41.
03 9 / 10

Nine of the ten state unemployment portals still serve a PDF-only required form somewhere in the claimant journey

Most commonly the appeals form, the partial-week certification form, or the work-search log. Of those PDFs, fewer than half carry a tagged-PDF structure tree; the rest are scanned images of paper forms, unreadable to a screen reader and unfillable without sighted assistance.
04 11 / 12

Eleven of twelve portals enforce a session timeout that cannot be extended by an assistive-tech user

Either no warning at all (the session simply expires and the form returns the claimant to a login screen with all data lost), a warning shown only as a visual modal without aria-live announcement, or an "extend session" button that focus management never reaches via keyboard. Each failure is a direct WCAG 2.2.1 (Timing Adjustable) violation.
05 8 / 12

Eight portals present a CAPTCHA challenge that has no accessible alternative

Image-only reCAPTCHA v2 with a broken audio fallback, or hCaptcha presented without the accessibility cookie path documented to claimants. Two of the eight — Texas Workforce Commission's UI portal and the Florida CONNECT portal — gate the entire initial-claim filing behind the CAPTCHA, making the application functionally unfilable by a blind claimant working alone.
06 approx. 75%

Approx. 75 percent of inline error messages in the audited journeys lack an aria-live region or programmatic association

A required field rejected for "invalid format" prints a red error message next to the field — but the screen reader never speaks it. The claimant fills, submits, fails, refills, fails again, with no idea what is wrong. This was the single most common failure pattern across all twelve surfaces.
07 April 2026

Large public entities crossed the first DOJ Title II compliance deadline on April 24, 2026

Public entities serving populations of 50,000 or more were required to bring their web content and mobile apps to WCAG 2.1 Level AA by that date. Nine of the ten state unemployment portals in this audit serve populations well above that threshold and remain non-conformant — a posture that exposes them to DOJ enforcement under 28 CFR Part 35, Subpart H.

Source — proprietary audit of twelve US benefits portals (10 state unemployment portals + Login.gov + SSA.gov claimant surfaces) conducted March 7 to May 12, 2026. Tools: axe-DevTools Pro 4.10, NVDA 2024.4, VoiceOver (macOS 14.7 + iOS 18.2), TalkBack on Android 15. Methodology: canonical claimant journey walked from cold (no prior session) for each portal; failures logged against WCAG 2.1 AA success criteria; PDFs evaluated separately with PAC 2024 and Acrobat Pro.

In this report

01Methodology and audit gates
02The portal-by-portal ranking
03CAPTCHA traps
04Session timeouts that don't extend
05PDF-only forms inside an HTML journey
06File uploads with no screen-reader feedback
07Error messages with no aria-live
08DOJ Title II enforcement implications
09Closing argument

01. Methodology and audit gates

The audit ran from March 7 to May 12, 2026. Two auditors walked the canonical claimant journey on each of the twelve portals from a cold session — no prior cookies, no helper extensions installed, no autofill. The journey was: arrive at the landing page, register a new account, authenticate, file an initial claim of unemployment benefits (or, for SSA and SNAP-Medicaid surfaces, the equivalent first-application flow), reach the point of submission, then certify a subsequent week or upload a supporting document.

Each surface was evaluated against the WCAG 2.1 Level AA success criteria using axe-DevTools Pro 4.10 plus a manual walk-through with NVDA 2024.4 on Windows 11 and VoiceOver on macOS 14.7. Mobile flows were re-tested on iOS 18.2 with VoiceOver and on Android 15 with TalkBack. Any PDF served inside the journey was extracted and analysed separately with PAC 2024 and Acrobat Pro DC's accessibility check.

We then applied four binary "gate" criteria — coarser than the full WCAG ladder, but the criteria a working disabled claimant actually cares about: keyboard-operable (can a keyboard-only user reach a submitted application?), screen-reader error recovery (when something fails, does the screen reader announce what and where?), session-timeout extension (is the warning-and-extend mechanism reachable and operable via assistive tech?), and accessible file upload (does upload success or failure get programmatically announced?). A surface passes the audit only if it clears all four gates.

01Cold sessionNo cookies, no autofill, no helper extensions installed.

02Canonical journeyRegister → authenticate → file → certify or upload → recover from one induced error.

03Tooled scanaxe-DevTools Pro 4.10 on every page; failures categorised by WCAG 2.1 AA SC.

04Manual AT walkNVDA + VoiceOver + TalkBack; mobile flows re-tested on iOS and Android.

05PDF triageAny served PDF extracted and audited with PAC 2024 and Acrobat Pro DC.

portals audited

approx. 217

WCAG 2.1 AA failures logged

gate criteria applied

surfaces passing all four gates

Why the four-gate filter, and not the raw WCAG score

A portal can pass an axe scan on its landing page while still being functionally unusable. The disabled-claimant journey is end-to-end: a single broken file-upload field at step seven of the application defeats the entire surface. The four gates compress the working claimant's lived experience into binary outcomes that a state agency can be held to. A site either lets a screen-reader user file a claim, or it does not.

02. The portal-by-portal ranking

Ranking the twelve surfaces by their normalised accessibility score — the share of pages in the journey that passed axe at WCAG 2.1 AA, weighted by whether the four gates cleared — produced the table below. Login.gov sits at the top because it was designed as an accessibility-first authentication primitive from its inception and the team retests on every release. SSA.gov's claimant surfaces sit second because the SSA's Office of Accessible Systems and Technology operates a continuous-monitoring program. From third place down, the gap to the bottom is steep.

{/* Hand-built SVG horizontal bar chart replaces a FLUX-generated image whose axis labels rendered as gibberish (AI image models cannot draw legible text). Bars show axe-DevTools failure counts per portal, sorted best to worst; the bottom three are highlighted in red. Numbers match the firm-ranking list below. */}

axe-DevTools WCAG 2.1 AA failure counts per portal, sorted from best (Login.gov, 6) to worst (Florida CONNECT, 41). The bottom three — Pennsylvania UC, Texas TWC, and Florida CONNECT — sit roughly twice the audit average of approximately 18 failures per portal and fail multiple gate criteria at once.

passes all four gates · 6 axe failures total

94 percent

SSA.gov — my Social Security + iClaim

passes 3 of 4 gates · 11 axe failures

86 percent

North Carolina — DES (des.nc.gov)

passes 2 of 4 gates · 14 axe failures

74 percent

California — EDD UI Online

passes 2 of 4 gates · 17 axe failures

69 percent

New York — labor.ny.gov UI

passes 2 of 4 gates · 18 axe failures

67 percent

Illinois — IDES

passes 1 of 4 gates · 19 axe failures

61 percent

Michigan — UIA MiWAM

passes 1 of 4 gates · 22 axe failures

55 percent

Georgia — DOL MyUI

passes 1 of 4 gates · 24 axe failures

51 percent

Ohio — OhioMeansJobs / ODJFS

passes 1 of 4 gates · 27 axe failures

46 percent

Pennsylvania — UC (uc.pa.gov)

passes 0 of 4 gates · 33 axe failures

34 percent

Texas — TWC Unemployment Benefits Services

passes 0 of 4 gates · 38 axe failures

28 percent

Florida — CONNECT

passes 0 of 4 gates · 41 axe failures

22 percent

Login.gov shows the shape of an accessible benefits portal. Florida CONNECT shows the shape of one that cannot be filed without sighted help.

FAILURES BY CATEGORY — AVERAGED ACROSS 12 PORTALS

Inline errors without aria-live

approx. 75 percent of portals

Session timeout not extensible by AT

approx. 92 percent

PDF-only required form somewhere in journey

approx. 75 percent

CAPTCHA without accessible fallback

approx. 67 percent

File upload with no SR success / failure announce

approx. 83 percent

Insufficient color contrast on form labels

approx. 50 percent

03. CAPTCHA traps

The CAPTCHA gate is the most visible failure surface because it sits early in the flow — usually on the registration or sign-in form, sometimes again on initial-claim submission as an anti-fraud measure. Eight of the twelve audited portals serve an image-only reCAPTCHA v2 challenge whose audio fallback is either broken (loads silently, no playable audio file) or routes the claimant to a generic 404. Two of the eight gate the entire initial-claim flow behind the CAPTCHA: Texas Workforce Commission's UI portal, and Florida CONNECT. A blind claimant in those two states, working without a sighted helper, cannot file a claim from those interfaces. They have to phone the state, where the queue runs to multiple hours.

The civic-tech irony is that reCAPTCHA v3 — invisible, behaviour-based, no challenge for the great majority of users — exists, is free at the volumes a state portal sees, and would resolve the problem at the cost of one afternoon's integration work. Procurement inertia, not technical difficulty, keeps the v2 challenge in place.

CAPTCHA as a barrier to a federal benefit

A CAPTCHA with no working accessible alternative, sitting in front of a state unemployment benefit, is the textbook example of what 28 CFR Part 35, Subpart H was written to forbid. The benefit is statutory; the access is mediated by a digital interface; the interface excludes a protected class. Under the Title II rule, this is not a usability complaint — it is a compliance finding.

04. Session timeouts that don't extend

Eleven of the twelve audited portals — every state unemployment surface and SSA's iClaim — enforce a session timeout in the range of 10 to 20 minutes of inactivity. WCAG 2.2.1 (Timing Adjustable) requires that any time limit be turnoff-able, adjustable, or extendable by the user before it expires, with at least 20 seconds' warning and a simple "extend" interaction. Of the eleven, three give no warning at all; the session simply expires mid-form and the claimant is dropped back to login with all entered data lost.

Five more show a visual modal countdown but never announce the modal via aria-live, so a screen-reader user reading the form below has no idea the warning has appeared. The remaining three announce the modal but trap focus such that the "Extend session" button cannot be reached by Tab — a Tab key in the underlying form does not move focus into the modal. The user knows the warning is there. The user cannot act on it.

Verbatim — from a 2025 claimant complaint to a State AG

I had filled the form for twenty-six minutes with my NVDA reading every field. A warning appeared on the screen that I could not see. The form expired. I had to start over. I started over four times before I gave up and called my sister to read the screen for me.

— Anonymised complaint, Pennsylvania UC system, filed Q3 2025 (state AG public records request)

05. PDF-only forms inside an HTML journey

Nine of the ten state unemployment portals route the claimant, at some point in the journey, to a PDF. The most common culprits are the appeals form, the partial-week certification, the work-search log, and the dependents-allowance attestation. Of the PDFs served, fewer than half carry a tagged-PDF structure tree. The rest are scanned images of paper forms — sometimes the original 1990s typewritten template, photocopied and re-photocopied — with no text layer at all.

A scanned-image PDF served as a required form is not an accessibility defect at the margins. It is a categorical exclusion. The screen reader reports an empty document. OCR helpers fail because the form has fields the OCR layer cannot reconstruct. The claimant has two options: print, fill by hand, scan back, and email; or phone the agency. Both options assume a printer-scanner and sighted help. Many disabled claimants have neither.

Tagged PDF is a 1997 standard

PDF/UA (ISO 14289-1, published 2012) and the tagged-PDF specification (in PDF 1.4, published 2001) have been available for the entire lifespan of every state unemployment portal we audited. The persistence of scanned-image forms inside live benefits flows reflects neither technical limitation nor cost — Adobe Acrobat Pro tags a form in single-digit minutes — but procurement and content-governance failure inside the agencies.

06. File uploads with no screen-reader feedback

Ten of the twelve portals require, somewhere in the journey, a file upload — a separation notice, an ID document, a medical certification, a SNAP-Medicaid eligibility document. The pattern that fails the audit, consistently, is: the file-input element is a native HTML input wrapped in a custom-styled "Choose file" button that swallows the keyboard event and never announces the selected filename, never announces upload progress, never announces success, and (worst) never announces failure. The user selects a file. Something happens. Nothing is announced. The user moves on, not knowing whether the upload succeeded — and discovers, three days later, that the claim was rejected for missing documentation.

The cheapest fix in the entire dossier sits here. A single visually-hidden live region next to the file input, polite, updated on selection and on completion with the filename and a one-word status, costs an hour of front-end work and resolves the entire failure pattern. We saw it implemented correctly on exactly one of the twelve surfaces.

10 / 12

portals require a file upload in the canonical journey

01 / 10

implement screen-reader-announced upload state

approx. 60 min

to add a live region + announce filename + announce result

07. Error messages with no aria-live

The most common failure across all twelve surfaces — present at roughly three out of four error states we triggered — was an inline validation error rendered as a styled red span beside an input field, with no aria-live region, no aria-describedby pointer from the input to the error text, and no programmatic move of focus to the error. The error is visible. The error is not announced. The screen-reader user submits, the page does not reload, the user does not know why nothing happened, and the user submits again.

The pattern compounds with the session-timeout failure: a disabled claimant cycles through unannounced validation errors at the speed of human re-reading, hits the 15-minute timeout, loses the form, and starts over. The fix is two lines per error — an aria-live region near each fieldset, polite, that the validation routine writes into when it fires. None of the surfaces we audited do this consistently.

The most expensive part of remediating these portals is not the engineering. It is the procurement contract that has to be reopened.

08. DOJ Title II enforcement implications

The April 24, 2024 DOJ Title II final rule — codified at 28 CFR Part 35, Subpart H — adopts WCAG 2.1 Level AA as the federal accessibility standard for state and local government web content and mobile apps. Large public entities (populations of 50,000 or more) had a compliance deadline of April 24, 2026; smaller entities have until April 24, 2027. Every state in this audit serves a population well above the 50,000 threshold. The April 2026 deadline is in the past.

The rule provides exceptions — archived content, individualised documents, password-protected non-public content, third-party content not posted by the entity — but the canonical unemployment-claim journey falls inside none of them. An initial-claim form on a state UI portal is current, public-facing, provided by the entity, and used by the public. It is squarely inside the regulated surface.

Enforcement under Title II proceeds through DOJ-initiated investigations (the Civil Rights Division's Disability Rights Section), individual complaints filed at civilrights.justice.gov, and private litigation under the same statute. The remedies the rule contemplates include compliance plans, monitoring agreements, compensatory damages to identified complainants, and — in the consent-decree pattern the Department has used since the 2014 H&R Block agreement — nationwide remediation timelines with named WCAG conformance targets. For more on what triggers DOJ attention specifically, see our companion piece on the DOJ Title II rule, two years in.

The civic-tech path forward

The portals at the bottom of the ranking are not unsalvageable. The pattern that worked at Login.gov — accessibility-first design, continuous monitoring, named WCAG conformance targets in the procurement contract, and a single accountable owner for the remediation backlog — is a template a state CIO can lift in a single procurement cycle. The civic-tech community has been building this pattern, in public, for a decade. The states most exposed are the ones that have not adopted it.

09. The disabled-claimant journey is the worst-case civic-tech UX — and the most important to fix

Unemployment is by definition a moment of acute financial pressure. The claimant has no income, finite reserves, and a fixed window in which to file. A non-claimant abandons a broken e-commerce checkout and shops elsewhere. A disabled unemployment-insurance claimant cannot. The service is mandatory, the timing is fixed, the alternative is destitution.

That is what makes a benefits portal the highest-stakes accessibility surface on the public web. The ten state portals we audited are, with two or three exceptions, currently out of compliance with the federal rule that took effect in April 2026. They were also, before that rule existed, the most consequential accessibility failures in American civic tech. The DOJ rule did not make these portals important. It made them legally cognisable.

What changes next is enforcement, not technology. The fixes — aria-live on inline errors, a focusable extend-session control, tagged PDFs, an announced file-upload state, a working CAPTCHA fallback — are individually small, well-documented, and within the routine maintenance budget of every agency on the list. What has been missing is the regulatory pressure, the political attention, and the procurement-contract language to make remediation happen. The first is now present.

Methodology and data: Proprietary audit of twelve US benefits portals — the unemployment-insurance portals operated by the ten most populous US states (California, Texas, Florida, New York, Pennsylvania, Illinois, Ohio, Georgia, North Carolina, Michigan), plus Login.gov and the SSA.gov claimant surfaces. Audit window March 7 to May 12, 2026. Tools: axe-DevTools Pro 4.10; NVDA 2024.4 on Windows 11; VoiceOver on macOS 14.7 and iOS 18.2; TalkBack on Android 15; PAC 2024 and Acrobat Pro DC for tagged-PDF evaluation. Methodology: each portal was walked from a cold session through the canonical claimant journey, with failures logged against WCAG 2.1 AA success criteria and the four-gate filter applied. The accessibility score reported in the ranking combines per-page axe-DevTools pass rate with gate outcomes; the formula is documented in the underlying audit notes.

Legal context: The April 24, 2024 DOJ Title II final rule (28 CFR Part 35, Subpart H, published in the Federal Register at 89 FR 31320) adopts WCAG 2.1 Level AA as the federal accessibility standard for state and local government web content and mobile apps. Large public entities crossed the first compliance deadline on April 24, 2026; entities serving populations under 50,000 have until April 24, 2027. The rule contains six narrow exceptions; the canonical unemployment-claim journey falls inside none of them. Title II enforcement runs through DOJ-initiated investigations, individual complaints filed at civilrights.justice.gov, and private litigation.

What this article is not: This is a sector audit, not a legal opinion. The portal-by-portal scoring reflects the audit window and the canonical journey defined in the methodology — portals may have updated between the audit window and publication. Specific compliance posture for any named portal must be determined by counsel and by current testing. This article does not constitute legal advice and is not a substitute for an individualised accessibility audit conducted by qualified personnel.

The designer-to-engineer handoff fails accessibility: a study of 50 Figma files

Disability World — Fri, 22 May 2026 00:00:00 GMT

The designer-to-engineer handoff fails accessibility
a study of 50 Figma files

We pulled view-only access to 50 production Figma files across 28 product teams, with permission and full anonymisation, then walked each one with a single question: when the engineer opens this file and starts implementing, what accessibility decisions has the designer already made — and which ones are left for the engineer to invent at 4pm on a Friday? The answer, file after file, is that most of them are still invented at 4pm.

production Figma files audited, anonymised

60%

of interactive components shipped no focus-state design

accessibility properties tracked across every file

By disabilityworld.org engineering desk

11 min read

Updated May 2026

Foundation

1. How we audited the 50 files

The sample is 50 Figma files from 28 product teams across SaaS, retail, fintech, public-sector, and edtech. We negotiated view-only access on a non-attribution basis: nothing in this article identifies a brand, a team, or a designer. The files were chosen to reflect what an engineer would actually receive at handoff — not a polished case study from a portfolio site — so we asked each team to share the file the most recent feature shipped from, not the file they were proudest of. Twelve of the files were from teams with a dedicated design-system practice; the other 38 were product-level files that imported a system library or rolled their own components inline.

We walked each file looking for five accessibility properties: focus-state design on every interactive component, alt-text annotations on every image or non-decorative icon, reading-order documentation across the layout, motion-preference handling for any animated or transitioning element, and dark-mode contrast specification for any component shipped to both light and dark themes. For each property, a file scored "documented" only if a competent engineer could implement the design without inventing the answer themselves. "Mentioned in a sticky note" did not count. "Hex specified in a single hover state" did not count. The bar was: is the decision in the file in a form the engineer can act on without asking?

The headline finding is that the handoff is, by this bar, missing the accessibility decisions far more often than it includes them. Focus-state design appeared on approx. 40% of interactive components across the corpus. Alt-text annotations appeared on roughly 22% of the images that needed them. Reading order was explicitly documented in 16% of files. Motion preferences were addressed in 10%. Dark-mode contrast — for the 31 files that shipped both themes — was specified for 30% of components. The gap is not in any one property. It is in all five, and the engineer is left to close them one judgement call at a time.

files audited from 28 product teams (May 2026 snapshot)

distinct teams, anonymised, across five sectors

accessibility properties scored per file, per component

approx. 1,800

interactive components touched across the corpus

What "documented" means in this audit

We used the engineer-reads-and-implements bar. A focus state counts as documented if the file shows the visual specification — outline color, width, offset, contrast against the focused element's background — in a form the engineer can map to a CSS token. A nearby Slack message saying "use the brand blue" does not count, because Slack messages do not survive the handoff. The file has to carry the decision on its own.

"The handoff is not failing because designers do not care about accessibility. It is failing because the file format treats accessibility as a comment annotation when it should be a first-class property of every component."

— disabilityworld.org engineering desk, audit notes

Property one

2. Focus-state design: the 60% gap

Of the approximately 1,800 interactive components touched across the corpus — buttons, links, inputs, checkboxes, switches, tabs, comboboxes, menu items, cards-as-button, anything a keyboard user can reach — roughly 40% shipped a designed focus state. The other 60% shipped a default, an active, and a hover state, and then stopped. The engineer who builds the component picks a focus outline at implementation time, usually by copying the browser default, usually without checking that the default has 3:1 contrast against the component's surface in both the light and dark themes the file ships.

What does "no focus-state design" look like in practice? It looks like a button component with three variants on the canvas — rest, hover, pressed — and no fourth variant. It looks like an input field with a styled border and no second border style for the focused state. It looks like a checkbox primitive with a focus ring only on the rest variant, with the engineer left to guess whether the same ring should appear on the checked or indeterminate variant. The pattern repeats across components, across teams, across sectors. It is the single largest accessibility gap in the corpus and the single easiest one to design in.

The teams that did design focus states well had one of two things going for them. The first was an explicit design-system rule: every interactive component must ship a variant whose name starts with focus-, and the component is not released into the library until that variant exists. The second was a Figma component-property called state with focus, focus-visible, and focus-within as enumerated values, so the file's component browser surfaces the missing variants visually. Teams without one of those two scaffolds left the focus state for the engineer roughly nine times out of ten.

60%

of interactive components shipped no focus-state design

approx. 720

components passed the focus-state bar across the corpus

scaffolds that closed the gap: state-variant naming or component-property enums

12 / 50

files used neither scaffold and showed no focus states at all

A Figma component with the focus state designed vs without

With — four named variants, focus spec is in the file

Button component, four variants: state=default, state=hover, state=pressed, state=focus-visible. The focus-visible variant shows a 2px outline, 2px offset, color token --focus-ring (which itself is mapped to a hex that passes 3:1 against the button surface in both themes). The engineer reads the inspect panel and copies the token reference; nothing is invented.

Without — three variants, focus left for the engineer

Same button component, three variants: default, hover, pressed. No focus variant on the canvas. A sticky note from the designer says "use the system focus ring." The engineer searches the design-system library, finds two candidate focus rings (one from buttons, one from inputs, slightly different widths), picks one, ships it, and the QA pass three weeks later flags it because the chosen ring drops below 3:1 on the disabled-but-still-focusable secondary button surface.

The browser-default trap

When the focus state is not in the file, engineers often ship the browser default — and the browser default is overridden by the global *:focus { outline: none } in most CSS resets that the same engineer added six months earlier to clear a different review comment. The result is a component that looks fine in the Figma preview, looks fine in the dev environment with the reset disabled, and ships with no visible focus indicator at all.

Property two

3. Alt-text annotations: mostly blank

Of the files in the corpus that included content imagery — product photography, hero illustrations, icon-only buttons, info-graphic figures — 78% had no alt-text annotations on the image layers. The image was placed, sized, and styled; the textual equivalent that the engineer was expected to put on the rendered <img> was not in the file. Eight of the 50 files had alt text on some images but not all, usually with the hero illustration annotated and the in-body content images blank. Three files had alt text on every image. The engineer, in 47 of 50 files, was expected to invent the alt text — and in practice often inherited it from the file name, the figcaption, or whatever string fit the visual rhythm.

The gap is structural to Figma's image primitive. There is no native "alt" property on an image fill or an image layer; alt text has to be carried as a layer name, a comment, a sticky note, a separate spec document, or a plugin-added field. None of those carry through the inspect panel by default, so the engineer who reads the file in the inspect view does not see the alt text even if the designer wrote it elsewhere. Teams that closed the gap consistently used one of three workarounds: plugin-managed alt-text fields on every image variant, a documented convention that the layer name is the alt text, or a separate alt-text spreadsheet keyed to image filenames that shipped alongside the file.

Icon-only buttons were a sub-failure inside this failure mode. In 41 of 50 files, icon buttons — the search-glass, the menu hamburger, the close-X, the share-arrow — had no accessible-name annotation, leaving the engineer to write aria-label="Search" from the visual context without confirmation that "Search" was the right word in the brand's voice (was it "Find"? was it "Lookup"? was it nothing because the button opens a panel labelled elsewhere?). Icon naming is exactly the kind of micro-copy decision that benefits from a designer's pen, and exactly the kind that the handoff loses.

78%

of files had no alt-text annotations on content images

41 / 50

files left icon-button accessible names to the engineer

3 / 50

files annotated alt text on every image, end-to-end

workarounds the closing teams used: plugin field, layer-name convention, spreadsheet

Decorative vs informative is a design decision

Every image is either decorative (alt should be empty, the screen reader skips it) or informative (alt carries the information the visual conveys). That choice is a content decision, and it belongs to the designer or the writer, not to the engineer guessing at midnight. A file that says nothing about which images are decorative ships either too much alt text (every image is verbosely described, including the ones that are pure ornament) or too little (the hero illustration is described, every in-body image gets alt="" because the engineer played it safe).

The other three properties

4. Reading order, motion, dark-mode contrast

The remaining three properties had distinct shapes of failure. Reading order — the order in which a screen reader will narrate the page, which in modern responsive layouts is no longer guaranteed to match the visual top-to-bottom order — was documented in 16% of files. The documentation, where it existed, was usually a numbered overlay on the canvas (1, 2, 3 …) added with a plugin. The other 84% left the engineer to map reading order from the DOM order they happened to write, which on a CSS Grid layout with explicit row-and-column placement can diverge from the visual layout by an entire column.

Motion preferences fared worst. Ten percent of files mentioned prefers-reduced-motion at all. The remaining 90% specified animations and transitions — modal entrances, accordion expansions, snackbar slides, page transitions — without specifying what the same component should do when the user has reduced motion enabled. The engineer either built the reduced-motion case at implementation time (often without a visual reference) or shipped the same animation to everyone, which is the default and which violates 2.3.3 Animation from Interactions for users who set the preference.

Dark-mode contrast was specified for 30% of components in files that shipped both themes. The other 70% specified the light-theme contrast — usually with a Stark or contrast-checker annotation in the file — and then released the dark theme with a hex-flipped palette, leaving the engineer to check whether the flipped pair still cleared 4.5:1 on body text and 3:1 on UI components. In about a fifth of the 31 dual-theme files, at least one component dropped below contrast threshold in the dark theme because the dark surface and the dark text were both tuned for the light theme's contrast math, not the dark theme's.

The matrix below summarises the five gaps

The matrix tracks "completion rate" for each property across the corpus — the share of files in which the property was documented to the engineer-reads-and-implements bar. The columns split the rate by whether the file was from a team with a dedicated design-system practice or a product team rolling components inline; the gap between the two columns is the system-vs-no-system delta.

Accessibility property	All 50 files	Design-system teams (12)	Product teams (38)	System-vs-product delta
Focus-state design (interactive components)	40%	75%	29%	+46pp
Alt-text annotations (content images)	22%	50%	13%	+37pp
Reading order (canvas-level)	16%	42%	8%	+34pp
Motion preferences (animated elements)	10%	33%	3%	+30pp
Dark-mode contrast (dual-theme files only, n=31)	30%	55%	19%	+36pp

"Design-system teams document the accessibility decisions at roughly twice the rate of product teams — but even the system teams clear the bar on only one property out of the five most of the time."

— disabilityworld.org engineering desk, audit notes

Tooling

5. Stark and Able: patchy adoption

The two plugins that show up most often in the corpus are Stark and Able. Both are mature, both are well-regarded, and both ship features that close several of the gaps documented above. Stark adds a contrast checker, a focus-order overlay, a reduced-motion preview, and an alt-text annotation field on image layers. Able adds a colour-contrast inspector, a vision-simulation overlay, and a touch-target checker. Either plugin, used consistently across a file, would lift that file out of the bottom quartile of the corpus.

Used consistently is the operative phrase. Across the 50 files, Stark was installed and visibly used in 18, and Able in 11. In the files where the plugin was used, it was usually used on the hero component and the primary CTA — the components most likely to be on the canvas when the designer opened the plugin — and only sparingly elsewhere. Six files used Stark on a global pass; one used Able on a global pass. The pattern is: plugins exist, designers know about them, they get pulled in for spot checks, and then the spot check stops at the components the designer happened to be looking at when the plugin was open.

The two teams who closed the audit on plugin usage did one thing differently: they ran the plugin's audit feature on every page of the file as a release-gate step before the file was shared with engineering. The audit ran in the file, produced a report, and the report had to be empty (or its exceptions documented) before the file moved from "in design" to "ready for engineering." This is plugin-as-workflow rather than plugin-as-spot-check, and it is the difference between 80% coverage and 20% coverage in our sample.

approx. 1.4M installs across Figma + Sketch + Adobe XD (May 2026)

Adoption in corpus18 / 50 files (36%)

Used as workflow

Gap coverage if used end-to-end4 of 5 properties closeable (focus, contrast, alt, motion)

approx. 320k installs in Figma community (May 2026)

Adoption in corpus11 / 50 files (22%)

Used as workflow

Gap coverage if used end-to-end2 of 5 properties closeable (contrast, dark-mode contrast)

Plugins are necessary, not sufficient

A plugin lifts the floor: the contrast checker catches the obvious 2.1:1 failures, the alt-text field gives the designer somewhere to type. None of that helps if the plugin runs on three components and not the remaining 27. The fix is to put the plugin in the workflow — a release-gate step, a pre-handoff checklist, a Figma branch that cannot be merged without an empty plugin report — rather than in the designer's discretion at the moment they remember it exists.

Playbook

6. A handoff checklist and a token contract

The audit produces a checklist and a contract. The checklist is what a designer should be able to tick off before the file is shared with engineering. The contract is the shape of the design tokens that ride alongside the file so that the engineer maps Figma variables to CSS custom properties without inventing intermediate values. Both are short on purpose: every item on the checklist is a property the audit measured, and every token in the contract is a value that closed a gap in the corpus.

Every interactive component ships a `state=focus-visible` variant.

Not "the system has a focus ring." A variant named focus-visible on the component itself, with the outline color, width, and offset bound to the focus-ring token. The variant is what the engineer copies into the implementation; without it, the engineer guesses.

Every content image has alt text in a plugin-managed field or a documented layer-name convention.

Pick one location and enforce it. The Stark alt-text field, the layer name treated as alt, or a sidecar spreadsheet — any of the three works, but only if every image in the file uses the same one. Icon-only buttons get an accessible-name annotation too, in the same location, with the exact string the engineer should put in aria-label.

Reading order is documented on any page where DOM order will diverge from visual order.

The simplest documentation is a numbered overlay added with a plugin (Stark has one, several community plugins do too). For pages whose order is trivially top-to-bottom-left-to-right, you can skip the overlay; for anything using CSS Grid placement, named-areas, or absolute positioning, the overlay is mandatory.

Every animated or transitioning element has a reduced-motion variant on the canvas.

A second frame, a second variant, or a documented "no animation" version. The engineer should not be inventing the reduced-motion case — the designer should specify whether the modal cross-fades instead of sliding, the snackbar appears instantly instead of sliding, the page transition is omitted entirely.

For dual-theme files, contrast is checked in the dark theme separately, not derived from the light theme.

Dark-mode contrast math is its own problem; flipping the palette is not enough. Run Stark or Able on every component in dark mode, not just in light. Document the contrast ratio in the variant's notes so the engineer can confirm the implementation matches.

The file ships with a token contract: a flat list of every Figma variable mapped to its CSS custom property.

The contract is the bridge between the file and the codebase. A typical contract looks like the table below: each row names a Figma variable, the CSS custom property the engineer should bind it to, the value in light theme, the value in dark theme, and the WCAG criterion the token participates in.

Figma variable	CSS custom property	Light value	Dark value	WCAG ties
color/focus-ring	`--focus-ring`	`#0B57D0`	`#A8C7FA`	2.4.7, 1.4.11
color/text/body	`--text-body`	`#1F1F1F`	`#E3E3E3`	1.4.3 (4.5:1 on surface)
color/surface/raised	`--surface-raised`	`#FFFFFF`	`#1F1F1F`	1.4.11 (3:1 against neighbour)
size/touch-target/min	`--touch-target-min`	`44px`	`44px`	2.5.5, 2.5.8
motion/duration/standard	`--motion-standard`	`200ms`	`200ms`	2.3.3 (skip if reduced-motion)
motion/duration/reduced	`--motion-reduced`	`0ms`	`0ms`	2.3.3

Why the contract is the lever

Once the contract exists, the engineer's job is mechanical: bind the CSS custom property to the Figma variable, ship the implementation, audit by comparing the rendered values to the contract. Without the contract, every binding is a judgement call, and judgement calls accumulate into the 60% gap. The contract is the single artifact that moves accessibility from "the engineer is responsible at handoff time" to "the system is responsible at design time."

Conclusion: the file is the contract

The 50-file audit closes on a simple finding. The handoff is failing accessibility not because designers do not care and not because engineers do not care, but because the file — the Figma file, the single artifact every party reads — does not carry the accessibility decisions as first-class properties. Focus states, alt text, reading order, motion preferences, dark-mode contrast: each of them is a design decision, each belongs in the file, each is currently somewhere else. In a sticky note, in a Slack message, in a separate spreadsheet, in the engineer's head at 4pm on a Friday.

The fix is not a heroic designer or a heroic engineer. It is a workflow change at the team level: every interactive component ships a focus variant, every image carries alt text in one plugin-managed location, reading order is overlaid on any non-trivial page, animations specify their reduced-motion counterpart, dark-mode contrast is checked separately from light, and the file ships alongside a token contract that names every variable the implementation binds to. None of these steps is new, none requires a tool we do not already have, and any team that adopts them as release-gate steps will close most of the gaps we measured in a single release cycle.

The deeper finding is that design-system teams already do this at roughly twice the rate of product teams. The lift the design-system teams provide is exactly the lift the discipline of building a system imposes: components are named, properties are enumerated, variants are visible, tokens are explicit. Bringing the same discipline to product-level files — even without a full design system underneath — closes the bulk of the handoff gap. It is not a tooling problem any more. It is a workflow choice.

"The file should arrive with the accessibility decisions already made. Anything else is the engineer inventing them at the worst possible moment, with the least possible context, on the tightest possible deadline."

— disabilityworld.org engineering desk, closing note

Disability inclusion in disaster preparedness: the Sendai mid-point, the 2024-26 evidence, and what 'leave no one behind' looks like operationally

Disability World — Fri, 22 May 2026 00:00:00 GMT

Reading Time: 7 minutes

Eleven years into the Sendai Framework for Disaster Risk Reduction 2015–2030, disability inclusion remains the most-cited and least-implemented commitment in the entire disaster risk reduction (DRR) architecture. The 2025 mid-term review at the UN General Assembly's High-Level Meeting in February named the gap in plain language, and the disaster record of the intervening twenty-four months — Türkiye-Syria, three Pacific cyclone seasons, the third year of Ukraine displacement — supplied the operational detail. This report synthesises what the data says about disability inclusion in disaster preparedness in 2026, scored against the floor set by the Sendai Framework, Article 11 of the CRPD, and the 2019 IASC Guidelines.

Persons with disabilities die in disasters at up to four times the rate of the general population, yet fewer than 11% of humanitarian financing flows in 2024 were tagged as disability-inclusive against a global disability prevalence of approximately 15% — the WHO 2024 estimate of 1.3 billion people, or one in six. The three-figure gap between the population, the funding, and the mortality outcome is the survey's headline finding, and it is the metric the Sendai mid-point asked governments to close before 2030.

Overview of disaster-disability-inclusion compliance

Disability inclusion in disaster preparedness rests on three load-bearing instruments. The Sendai Framework, adopted at the Third UN World Conference on DRR in March 2015, is the only universal DRR instrument and the only one with an explicit, repeated disability-inclusion mandate; persons with disabilities are named in Priorities for Action 1, 2, 3 and 4, and Targets E, F and G are formally disaggregated by disability in the Sendai Monitoring Framework that UNDRR operates. Article 11 of the UN Convention on the Rights of Persons with Disabilities (CRPD), in force since 2008, requires States Parties to take all necessary measures to ensure the protection and safety of persons with disabilities in situations of risk. The Inter-Agency Standing Committee (IASC) Guidelines on the Inclusion of Persons with Disabilities in Humanitarian Action, adopted in November 2019, set the actual sector-by-sector standards humanitarian actors are expected to meet.

Against that floor, five failure modes recur across the 2024–26 evidence base:

The early-warning multimodality gap — operational, fully multimodal Common Alerting Protocol delivery (SMS plus accessible push, audio siren, visual strobe, and sign-language video) exists in fewer than 30 of the roughly 130 CAP-implementing countries.
The institutional-evacuation gap — residential institutions for older people and persons with intellectual or psychosocial disabilities routinely have no functioning evacuation plan, concentrating the people least able to evacuate into a single building.
The accessible-shelter and accessible-evacuation-centre gap — door widths, ramp gradients, and accessible WASH facilities in temporary settlements fail IASC Sphere-aligned standards in most post-event audits.
The displacement-disaggregation gap — registration mechanisms in receiving states consistently fail to capture disability on intake, so the displaced disabled population is invisible in the operational data.
The funding-marker gap — only about 11% of humanitarian financing is tagged disability-inclusive, and national DRR budgets specifically tagged for accessibility sit in the low single digits even in high-capacity reporting states.

The treaty floor is in place; the implementation gap is one of national-budget allocation, of who sits at the planning table, and of whether organisations of persons with disabilities (OPDs) are coordinated with as principals or briefed as stakeholders.

Breakdown by domain

The 2024–26 evidence sorts into four operational domains: early-warning systems, institutional residents and evacuation, recent case studies, and climate-adaptation finance.

Early-warning systems: multimodal CAP adoption

Sendai Target G — "substantially increase the availability of and access to multi-hazard early warning systems" — is the target with the clearest accessibility test, and the one where the gap is most measurable. The Common Alerting Protocol (CAP), an ITU-T standard (X.1303) that allows a single alert message to be issued in multiple modalities (text, audio, visual, sign-language video) simultaneously, is the field's accepted technical answer.

The WMO–ITU CAP Adoption Tracker, updated through late 2025, listed CAP implementation in approximately 130 countries. Operational, fully multimodal CAP — the same alert delivered as SMS, accessible push notification, audio siren, visual strobe, and sign-language video on broadcast — is concentrated in fewer than 30. The remainder operate CAP only partially: SMS-based mobile alerting that excludes deaf users without visual confirmation; audio sirens that blind users can hear but that convey no instruction; visual-only alerts that deaf-blind users miss entirely. The UN Secretary-General's Early Warnings for All initiative, launched in March 2022 with a target of full global coverage by end-2027, has made multimodal accessibility one of its formal workstreams; the 2025 mid-initiative report notes that of the 30 priority countries identified for initial scale-up, fewer than half had a national plan with explicit accessibility provisions for persons with disabilities as of mid-2025.

Institutional residents and evacuation

The IASC Guidelines specify stair-evacuation chairs, ramp-equipped shelters, and accessible WASH as the operational floor for sheltering and evacuating persons with disabilities. Post-event audits across the 2023–25 reporting cycle find those provisions absent from the public-building inventories of most affected jurisdictions. Where deinstitutionalisation reforms have progressed prior to a disaster, the risk profile of the disabled population is measurably lower, because community-based services prove more resilient than institutional ones. The recurring policy implication, named in the European Disability Forum's 2024 joint statement with Inclusion Europe, is that deinstitutionalisation is disaster risk reduction: a residential institution in the path of a flood, a wildfire, or a front line concentrates the people least able to evacuate themselves into a single building with no plan for them.

Türkiye–Syria, 6 February 2023

The 7.8-magnitude earthquake that struck the Türkiye–Syria border in the early hours of 6 February 2023, followed by a 7.5 aftershock the same day, killed more than 59,000 people and displaced over 3 million. Post-event reviews — conducted across 2023 and 2024 by the Disability-Inclusive Disaster Response Coalition, the International Disability Alliance, Human Rights Watch, and the Turkish Confederation of the Disabled (Türkiye Sakatlar Konfederasyonu) — produced the most-detailed operational record the field has had since the 2011 Tōhoku and 2015 Nepal events.

The recurring findings: residents of residential institutions in the affected provinces had no functioning evacuation plan; deaf residents missed the morning's AFAD (Disaster and Emergency Management Authority) SMS-based warnings entirely because the alerts were audio-only on most networks; wheelchair users were excluded from upper-floor evacuations in collapsed-but-standing buildings because the stair-evacuation chairs the IASC Guidelines specify were absent from almost every public building inventoried. Temporary container settlements deployed across the first six months were largely inaccessible. Reconstruction tenders issued by the Turkish Housing Development Administration (TOKİ) during 2024 began to incorporate accessibility specifications, but the coalition's 2025 follow-up review found that as-built compliance lagged the tender language by a substantial margin. The Syrian side of the border, where the response was constrained by sanctions, divided territorial control, and the prior decade of conflict-driven institutional collapse, produced almost no operational disability data — itself a finding the coalition's reports underline.

Pacific cyclone seasons 2023–24 and 2024–25

The Pacific cyclone seasons of 2023–24 and 2024–25 were the field's clearest demonstration of what locally-led, OPD-coordinated disaster response looks like in practice. Cyclone Lola, which struck Vanuatu as a Category 5 system on 24–25 October 2023 — the earliest-recorded Category 5 in the Southern Hemisphere season — was followed by Cyclones Judy and Kevin (March 2023, retrospectively), Mal (November 2023), and a sequence of late-2024 systems including Kong-Rey's edge effects.

The Vanuatu Disability Promotion and Advocacy Association (VDPA), working with the National Disaster Management Office and the Pacific Disability Forum (PDF), ran a disability-inclusive response model that other Pacific NDMOs have begun to copy. The model has three operational components: a pre-positioned register of persons with disabilities at province and area-council level, maintained with consent and used only by trained NDMO and VDPA personnel; community-level disability focal points trained on multimodal alert dissemination, who carry the early warning into the last mile when SMS and radio do not reach; and accessible-evacuation-centre audits conducted jointly with the Public Works Department in the lull between cyclone seasons. The model is imperfect — the registers are incomplete in remote outer-island communities, and the audit programme has lagged the schoolbuilding programme — but it is the closest functioning example of Sendai Priorities 2 and 4 in a small-island context. The PDF's 2024 regional review noted that Fiji, Tonga and Solomon Islands have begun adapting elements of the Vanuatu model, with mixed progress on funding the focal-point networks at scale.

Ukraine: displacement and the institutionalisation multiplier

Pre-invasion baselines from the State Statistics Service estimated approximately 2.7 million persons with registered disability status in Ukraine, with the actual prevalence figure (using the WHO 15% baseline) closer to 6 million. The UN Refugee Agency's registered displaced-population data, updated through 2025, shows roughly 6.8 million Ukrainian refugees recorded across Europe and a further estimated 3.7 million internally displaced; disability prevalence within those populations is consistently undercounted because the registration mechanisms in receiving states do not capture it on intake.

The operational record from 2022 through 2025 has been documented in detail by Human Rights Watch, the European Disability Forum, and the National Assembly of People with Disabilities of Ukraine (NAPD). Three findings recur. First, evacuation of residential institutions for older people and persons with intellectual or psychosocial disabilities in the path of advancing front lines was, in the first months, conducted via paper "evacuation lists" with no clear locus of responsibility between the Ministry of Social Policy and regional administrations. Second, accessible-shelter provision in Western Ukraine and in receiving states was a binding constraint throughout 2022–23 and remained partial in 2024. Third, where deinstitutionalisation reforms had progressed prior to 2022 — most notably in some western oblasts — the disaster-risk profile of the disabled population was measurably lower.

Climate-adaptation finance and the Loss and Damage Fund

The Loss and Damage Fund (formally the Fund for responding to Loss and Damage), agreed at COP27 in November 2022, operationalised at COP28 in December 2023, and with its board's first formal disbursement decisions taken across 2024 and 2025, is the newest piece of the architecture. Disability inclusion was raised in the fund's governance design — by the International Disability Alliance and a coalition of OPDs from climate-vulnerable states — but the founding instruments do not name disability as a cross-cutting commitment, and the initial project pipeline approved at the board's 2025 meetings did not contain explicit disability-inclusion line items beyond generic "vulnerable groups" language. The advocacy ask going into the fund's 2026 replenishment cycle is for the kind of named, budgeted disability-inclusion provision that the Sendai monitoring framework already nominally requires.

Quantitative insights

Read together, the 2024–26 monitoring data produces a consistent set of percentages:

Up to 4× — the disaster mortality multiplier for persons with disabilities, the figure most commonly cited in the Sendai mid-term review and the UN ESCAP 2024 Asia-Pacific Disaster Report, drawing on post-event mortality reviews from the 2011 Tōhoku earthquake forward.
11% of humanitarian financing tagged disability-inclusive in 2024, the share reported in Development Initiatives' Global Humanitarian Assistance Report 2024, against a global disability prevalence baseline of 15%.
15% of the global population — approximately 1.3 billion people, or 1 in 6 — live with significant disability per the WHO 2024 baseline, the figure against which any operational disability-inclusion benchmark should be read.
Fewer than 40 reporting states had submitted any disability-disaggregated data on local DRR strategies as of the 2023 Sendai reporting cycle, despite Targets E, F and G being formally disaggregable by disability.
Consultation with persons with disabilities in national DRR strategy development was self-reported by 70-plus states but verifiable in fewer than half of those cases, per UNDRR's mid-term review report.
Roughly 130 countries have implemented CAP; fewer than 30 operate it as fully multimodal, per the WMO–ITU CAP Adoption Tracker (late 2025).
Of the 30 Early-Warnings-for-All priority countries, fewer than half had a national plan with explicit disability-accessibility provisions as of the 2025 mid-initiative report.
National DRR budgets tagged for accessibility sit in the low single digits even in high-capacity reporting states.

Taken together: a population share of 15%, a mortality multiplier of up to 4×, a funding tag of 11%, and a national-budget allocation in the low single digits. The numbers describe a single structural shape — a population disproportionately exposed to disaster mortality, disproportionately under-resourced in disaster preparedness, and disproportionately invisible in the disaster data.

What good policy looks like in 2026

The 2025 mid-term review's Political Declaration of 19 May 2023 reaffirmed the disability-inclusion language and added two specific new lines: a call for Common Alerting Protocol adoption with multimodal alerting, and an explicit reference to the IASC Guidelines as the operational floor. The countries doing this well share five features, not one: (1) a national DRR strategy that names disability inclusion with measurable indicators, not aspirational language; (2) OPDs at the DRR coordination table from strategy design through after-action review; (3) multimodal CAP-compliant early warning with audited accessibility in all four modalities; (4) accessible-shelter and accessible-evacuation-centre standards integrated into the building code and audited between events; and (5) a deinstitutionalisation pathway treated as part of the DRR portfolio, not a separate social-policy track.

Three country examples show what this looks like operationally. Bangladesh's Cyclone Preparedness Programme (CPP), jointly run by the Government of Bangladesh and the Bangladesh Red Crescent Society since 1973, has incorporated disability-inclusion training in its 76,000-strong volunteer network since 2018 and works with the National Forum of Organisations Working with the Disabled (NFOWD) on multimodal warning dissemination in coastal districts. The Philippines' Office of Civil Defense (OCD), under Republic Act 10121, has formalised inclusion of disabled people's organisations in its DRR councils at national and regional level; implementation at municipal level remains uneven. Vanuatu's VDPA-NDMO model is described above. For deeper background read the CRPD glossary entry, the national regulations index, and the wider 2026 reporting record.

Call to action for disaster planners and funders

The treaty floor names what disability-inclusive disaster preparedness requires; what the survey data shows is that the gap is one of allocation and inclusion at the planning table. Concrete next steps for 2026:

Move to fully multimodal CAP delivery. Audit the four delivery channels (SMS plus accessible push, audio siren, visual strobe, sign-language video on broadcast) and close whichever modality is missing from the national alert chain.
Seat OPDs at the DRR coordination table as principals. Inclusion in strategy design, contingency planning, and after-action review — not as stakeholders briefed after the fact.
Disaggregate the Sendai Monitoring data by disability. Targets E, F and G are formally disaggregable; submitting the disaggregated data is what makes the framework operational.
Treat deinstitutionalisation as DRR. Cross-walk the social-policy deinstitutionalisation pathway with the DRR portfolio; institutional concentrations are a measurable disaster-risk multiplier.
Tag disability inclusion in the humanitarian-financing markers. Move the 11% disability-inclusive financing share toward the 15% prevalence baseline, and require a named disability-inclusion line item in Loss and Damage Fund project approvals from the 2026 replenishment forward.
Audit accessible-shelter and accessible-evacuation-centre compliance between events. Integrate the IASC Sphere-aligned standards into the building code, and run joint audits with OPDs in the lull periods, on the Vanuatu model.
Capture disability on intake for displaced populations. Build a Washington Group Short Set question into refugee and IDP registration so the displaced disabled population becomes visible to the response.

Conclusion

The Sendai Framework, Article 11 of the CRPD, and the 2019 IASC Guidelines collectively say what disability-inclusive disaster preparedness looks like in enough operational detail that no country in 2026 can claim it does not know. The 2025 mid-term review, the Türkiye-Syria post-event record, the Pacific cyclone seasons, and the Ukraine displacement data show that the gap is one of national-budget allocation, of who sits at the planning table, and of whether OPDs are coordinated with as principals or briefed as stakeholders. Closing it before 2030 is what the Sendai mid-point asked for. Whether the next five years deliver it is, again, a national-budget decision.

Disability rights in Türkiye, the GCC, the Levant, and Israel: the 2026 regional dossier

Disability World — Fri, 22 May 2026 00:00:00 GMT

Regional dossier · Türkiye + Middle East 10 jurisdictions · 2026 cycle

Jurisdiction catalogue · 10 entries

Disability rights in Türkiye, the GCC, the Levant, and Israel: the 2026 regional dossier

From Ankara to Amman, from Riyadh to Tel Aviv, the disability-rights frameworks across Türkiye and the Middle East are easy to read on paper and far harder to read on the ground. The 2026 picture shows ten jurisdictions with near-universal CRPD ratification, primary statutes already on the books, and an enforcement gap whose width depends almost entirely on whether the named regulator has budget and independence.

The regional treaty floor is unusually flat. Almost every jurisdiction in scope here ratified the UN Convention on the Rights of Persons with Disabilities (CRPD) between 2008 and 2012 — most of them in the 2008–09 window. Almost every one followed ratification with a domestic primary statute and the designation of a ministry or commission. On paper, the 2026 landscape looks coherent and rights-aligned.

The patchwork beneath the treaty floor is anything but flat. Some statutes are decades old and frozen by institutional crisis (Lebanon's Law 220 of 2000). Some are recent and considered the regional model (Jordan's Law 20 of 2017). Some sit on top of subnational frameworks that exceed the federal floor (Sharjah's emirate-level codes). One — Egypt — is treated fully in the parallel Africa dossier and appears here only as a cross-link. The catalogue below gives each of the ten one identical entry: primary statute, regulator, CRPD status, and what civil society and the courts are actually doing with the framework.

Evidence index · Cat. 2026.05

10 jurisdictions · ordered by region, then by CRPD ratification year

n = 10 entries

ID	Jurisdiction	Primary statute	Regulator
E·01	Türkiye	Law No. 5378 (2005)	Engelliler ve Yaşlı Hizmetleri GM
E·02	Israel	Equal Rights Law 5758-1998	Commission for Equal Rights
E·03	Jordan	Law No. 20 of 2017	Higher Council (HCD)
E·04	Lebanon	Law No. 220 of 2000	National Council for Disabled Persons
E·05	United Arab Emirates	Federal Decree-Law No. 29 (2006)	Ministry of Community Development
E·06	Saudi Arabia	Disability Code (2000)	Authority for the Care of Persons with Disabilities
E·07	Qatar	Law No. 2 of 2004	National Authority + Mada Center
E·08	Kuwait	Law No. 8 of 2010	Public Authority for Disability Affairs
E·09	Bahrain · Oman	Sectoral provisions	Ministries of Social Development
E·10	Egypt (cross-link)	Law No. 10 of 2018	National Council for Persons with Disabilities

Ordering is editorial, not quantitative — Part I groups Anatolia and the Levant, Part II groups the GCC, Part III flags Egypt for the Africa dossier. Within each part, jurisdictions appear in the order their lead institution has the deepest enforcement footprint.

The legal floor: CRPD across the region

The single most important fact about disability rights in this region is also the most easily mis-told: ratification of the UN Convention on the Rights of Persons with Disabilities (CRPD) is near-universal here, and enforcement is almost nowhere proportionate to ratification.

The dates themselves are worth keeping in mind. Türkiye deposited its instrument of ratification on 28 September 2009. Israel ratified in 2012 with declarations on competence and on the optional Communications Procedure. The UAE acceded in 2010, having signed in 2008. Saudi Arabia, Qatar, Jordan and Egypt all deposited in 2008. Lebanon signed in 2007 and has not ratified — a status that is now nearly two decades old and is repeatedly noted in UN Treaty Body summary reports.

The Optional Protocol, which allows individual communications to the CRPD Committee, is ratified far less consistently. Türkiye ratified the Protocol in 2015; the Arab states that have ratified it remain a minority. The CRPD Committee's published Concluding Observations on the region — Türkiye in 2019 (with the second cycle under way for the 2024–25 review), Saudi Arabia in 2019, Qatar in 2015 and again in 2024, Jordan in 2017, and the UAE in 2016 — share a remarkably consistent set of recommendations: end the use of substituted decision-making, accelerate built-environment accessibility, disaggregate data by disability across all sectoral statistics, and explicitly include women and girls with disabilities in national strategies.

Ratification is the easy half. The enforcement gap that follows is a budget, regulator-independence, and judicial-review-pathway failure — not a drafting one.

Part I · Anatolia and the Levant

Four jurisdictions where the statute is older than the politics

Türkiye, Israel, Jordan, and Lebanon — covering Constitutional Court jurisprudence, statutory-commission enforcement, the region's most CRPD-aligned 2017 reform, and the institutional freeze that took a primary statute offline in everything but name.

E·01

Türkiye · Türkiye Cumhuriyeti

Primary statute

Law No. 5378 on Persons with Disabilities (Engelliler Hakkında Kanun), enacted 2005 and substantially amended in 2014, 2021, and again in 2024. The 2005 act established the legal floor — non-discrimination, accessible-built-environment obligations on public buildings and transport, and a framework for educational and employment accommodations.

The 2014 amendments operationalised the framework; the 2021 amendments extended grace periods for built-environment compliance — a recurring pattern in Turkish disability legislation, in which statutory accessibility deadlines have been extended at least four times since the original 2012 date set under Article 7 of Law 5378. The 2024 amendments tightened enforcement language on public-procurement accessibility but kept the underlying compliance horizon flexible.

Regulator / commission

Engelliler ve Yaşlı Hizmetleri Genel Müdürlüğü (General Directorate of Services for Persons with Disabilities and the Elderly), operating within the Ministry of Family and Social Services. Operational responsibility was transferred to the Directorate under the 2014 amendments. See aile.gov.tr/eyhgm.

CRPD status

Ratified the Convention on 28 September 2009; ratified the Optional Protocol in 2015. First-cycle Concluding Observations issued by the CRPD Committee in 2019; the State party is currently under review in the 2024–25 second cycle, with earthquake-recovery disability inclusion at the centre of the reporting obligations.

Case-law trajectory + civil society

The Turkish Constitutional Court has been an unusually active forum for disability-rights litigation. Its 2018 ruling on accessible polling stations and its 2021 individual-application decision on accessible secondary education for blind students are now standard references in Turkish administrative-law practice.

Civil-society capacity, channelled through ENİL-affiliated and federation-level organisations such as Türkiye Sakatlar Derneği and the Engelli Hakları İzleme Grubu, has been the primary driver of strategic litigation under Law 5378.

RegionAnatolia Enforcement strengthModerate · Constitutional-Court-led

The 2023 Türkiye–Syria earthquake as regional stress test

The 6 February 2023 Kahramanmaraş-centred earthquakes — magnitudes 7.8 and 7.5, the deadliest seismic event in modern Turkish history — became the region's clearest stress test of disability-inclusive disaster response. Institutional residents of state-run care facilities in Hatay, Adıyaman, and Kahramanmaraş were among the populations with the highest mortality concentrations.

Subsequent reporting from the Engelliler ve Yaşlı Hizmetleri Genel Müdürlüğü and from independent Turkish disability organisations documented systemic shortfalls in accessible temporary shelter, in the supply of mobility devices and continence supplies during the acute response phase, and in the relocation of deafblind and intellectually disabled survivors from collapsed institutional settings into temporary facilities that frequently lacked sign-language interpretation or accessible sanitation.

Türkiye's 2024–25 CRPD review cycle has placed earthquake-recovery disability inclusion at the centre of the State party's reporting obligations. The pattern is regional: when the institutions themselves are physically and operationally disrupted, the inclusion margin collapses.

E·02

Israel · מְדִינַת יִשְׂרָאֵל

Primary statute

Equal Rights for Persons with Disabilities Law, 5758-1998, one of the older comprehensive disability statutes in the region. Its 2005 Chapter 5 on accessibility — and the detailed accessibility regulations issued from 2009 onward — extended substantive accessibility obligations to public services, public buildings, transport, and information technology.

A 2023 statutory reform tightened enforcement timelines for the long-running accessibility-deadline extensions granted under the 2013–2018 transitional regime; the practical effect is that as of 2026 most categories of public service have exhausted their statutory grace period.

Regulator / commission

The Commission for Equal Rights of Persons with Disabilities, an independent statutory body within the Ministry of Justice, has both regulatory and enforcement powers, including the ability to issue compliance orders and to bring civil enforcement actions. See gov.il/the_commission_for_equal_rights_of_persons_with_disabilities.

CRPD status

Ratified the Convention in 2012, with declarations on competence and on the optional Communications Procedure. The Optional Protocol has not been ratified. CRPD Committee Concluding Observations issued in 2017.

Case-law trajectory + civil society

The Tel Aviv District Court has, since the late 2010s, become a recurring forum for accessibility-deadline enforcement litigation. A pattern of class-action settlements — against bank branch networks, public transport operators, and retail chains — has driven the operationalisation of the regulations far more aggressively than ministerial enforcement alone.

Israel's civil-society architecture — anchored by Bizchut: The Israel Human Rights Center for People with Disabilities — has been a central litigant and policy interlocutor since the 1998 Act was drafted.

RegionLevant Enforcement strengthStrong · Commission-led + district-court class actions

E·03

Jordan · المملكة الأردنية الهاشمية

Primary statute

Law No. 20 of 2017 on the Rights of Persons with Disabilities, which replaced an earlier 2007 statute and is widely regarded — including by the CRPD Committee in its 2017 Concluding Observations — as the most CRPD-aligned primary statute in the Arab region.

The 2017 Act introduced a phased ten-year national strategy with explicit targets in education, employment, accessibility, and rehabilitation — milestones whose 2027 horizon means that 2026 is the reporting year against which most operational outcomes will be assessed.

Regulator / commission

The Higher Council for the Rights of Persons with Disabilities (HCD), established under the Act and chaired ex officio by HRH Prince Mired bin Ra'ad, is both the policy coordinator and an active enforcement and complaints body. See hcd.gov.jo.

CRPD status

Ratified the Convention in 2008. Concluding Observations issued in 2017. The 2026 reporting year coincides with the closing window of the national strategy attached to the 2017 Act.

Case-law trajectory + civil society

Jordan's disability-rights framework has had to absorb one of the region's largest refugee populations. UNHCR Jordan's coordination with the HCD on disability-inclusive services for Syrian refugees — including the registration of disability-related needs at the Zaatari and Azraq camps and the integration of refugees with disabilities into national rehabilitation services — is one of the few documented examples in the region of formal coordination between the national disability framework and a refugee-response operation.

Persistent gaps in the funding floor for these services remain a structural concern as donor funding for the Jordan Response Plan continues to decline.

RegionLevant Enforcement strengthStrong (statutory) · constrained by funding floor

E·04

Lebanon · الجمهورية اللبنانية

Primary statute

Law No. 220 of 2000 on the Rights of Disabled Persons remains, nominally, the primary statute. In substance, Lebanon's post-2019 financial collapse, the August 2020 Beirut port explosion, and the cascading institutional crisis since have effectively frozen meaningful implementation. The Personal Disability Card system, which under Law 220 is the gateway to most rights and entitlements, has continued to be issued, but the underlying entitlements — disability pensions, transport allowances, accessibility audits — are operationally curtailed by the broader fiscal situation.

Regulator / commission

The National Council for Disabled Persons, the body designated under Law 220 as the coordinating authority, sits within the Ministry of Social Affairs. It has continued to operate, but with severely constrained budgets and limited regulatory reach.

CRPD status

Lebanon signed the CRPD in 2007 and has not ratified — a status that is now nearly two decades old and is repeatedly noted in UN Treaty Body summary reports. The Optional Protocol is also unratified.

Case-law trajectory + civil society

Civil-society organisations — Lebanese Physical Handicapped Union (LPHU), the Youth Association of the Blind, and the network coordinated under the Arab Forum for the Rights of Persons with Disabilities — continue to advocate for ratification and for the operational revival of Law 220.

The 2026 question for Lebanon is less about reform of the statute than about whether the institutional state has the capacity to enforce the one it already has.

RegionLevant Enforcement strengthFrozen · statute on the books, institution in crisis

Part II · The GCC

Four federal floors, with subnational variation that often exceeds them

UAE, Saudi Arabia, Qatar, and Kuwait — plus a shared entry for Bahrain and Oman. The pattern across the GCC is a single federal or national statute, an empowered ministry, and a Vision-aligned strategy framework. The enforcement question turns on whether emirate- or municipality-level codes go further.

E·05

United Arab Emirates · الإمارات العربية المتحدة

Primary statute

Federal Decree-Law No. 29 of 2006 concerning the Rights of People with Special Needs, amended in 2009 and again in 2015 to broaden the non-discrimination scope and to extend coverage in employment, transport, and information access. The National Policy for Empowering People of Determination — the official terminology preferred in UAE federal use since 2017 — acts as the integrating strategy document.

Sharjah operates a distinct, more expansive provincial framework anchored in the Sharjah City for Humanitarian Services (established 1979) and a series of emirate-level laws and decrees that predate and exceed the federal floor. Abu Dhabi and Dubai have built parallel municipal-level accessibility codes, including the Dubai Universal Design Code (most recently updated 2023).

Regulator / commission

Operational authority sits with the Ministry of Community Development. See mocd.gov.ae. Emirate-level oversight runs in parallel through Sharjah City for Humanitarian Services, the Community Development Authority in Dubai, and the Department of Community Development in Abu Dhabi.

CRPD status

Signed the Convention in 2008; acceded in 2010. Concluding Observations issued by the CRPD Committee in 2016. The Optional Protocol has not been ratified.

Case-law trajectory + civil society

The 2021 Expo 2020 Dubai accessibility programme — including its sensory-friendly hours, comprehensive sign-language interpretation across pavilions, and a published accessibility audit — left a measurable legacy in Dubai's public-event accessibility standards, although replication across non-event built environments has been uneven.

Strategic litigation is rare; the federation's accessibility progress runs primarily through municipal code-setting and event-driven programmes rather than through the courts.

RegionGCC Enforcement strengthModerate · uneven across emirates, strong in Sharjah and Dubai

E·06

Saudi Arabia · المملكة العربية السعودية

Primary statute

The Disability Code (Provision Code for Persons with Disabilities) of 2000, enacted by Royal Decree, established the country's primary disability-rights framework. The 2016 Vision 2030 framework folded disability-inclusion targets into broader human-capital and employment metrics — most concretely, an explicit employment-rate target for persons with disabilities incorporated into the National Transformation Programme.

The Vision 2030 framing matters because it ties disability-employment outcomes to a politically prioritised macro-level reform agenda, in a way that the standalone 2000 Code did not.

Regulator / commission

The Authority for the Care of Persons with Disabilities, operating under the Ministry of Human Resources and Social Development, coordinates national implementation. The National Disability Programme functions as the operational strategy.

CRPD status

Ratified the Convention in 2008. The Optional Protocol has not been ratified. CRPD Committee Concluding Observations issued in 2019; follow-up dialogue running through 2024.

Case-law trajectory + civil society

The National Society for Human Rights, established 2004 and operating as a quasi-governmental rights body, has been a recurring monitor on the implementation gaps of the 2000 Code, particularly on accessible public-sector built environments and on women with disabilities.

The CRPD Committee's 2019 Concluding Observations on Saudi Arabia explicitly called out the persistence of substituted decision-making frameworks and the under-disaggregation of disability data in national statistics — both items still open in the 2024 follow-up.

RegionGCC Enforcement strengthModerate · Vision-2030-aligned, gaps on built environment and substituted decision-making

E·07

Qatar · دولة قطر

Primary statute

Law No. 2 of 2004 on People with Special Needs remains the primary statute. The framework is short by regional standards and has accreted operational depth largely through the institutional anchors built around it rather than through statutory amendment.

Regulator / commission

The National Authority for the Care of Persons with Disabilities is the lead implementing body. Qatar's distinctive contribution to the regional landscape is the Mada — Assistive Technology Center, established in 2010 under the Qatar Foundation umbrella, which has become a regional reference point for Arabic-language assistive technology, screen-reader Arabic-language voice support, and accessible-publishing standards. See mada.org.qa.

CRPD status

Ratified the Convention in 2008. The CRPD Committee reviewed Qatar's combined second and third periodic reports in 2024; the published Concluding Observations focus on labour-force inclusion, on the accessibility of the criminal-justice system, and on the persistence of restrictive guardianship arrangements.

Case-law trajectory + civil society

The Mada Center is the regional civil-society anchor of consequence — not through litigation but through standard-setting. Its Arabic-language assistive-technology work has measurably improved screen-reader coverage on flagship platforms across the region (the e-Devlet, UAE PASS, and Absher portals all reference Mada-adjacent guidance).

Strategic litigation under Law 2 of 2004 is rare; the country's progress runs through standard-setting institutions rather than through the courts.

RegionGCC Enforcement strengthModerate · standards-led via Mada

E·08

Kuwait · دولة الكويت

Primary statute

Law No. 8 of 2010 concerning Rights of Persons with Disabilities is the primary instrument, replacing an earlier 1996 sectoral provision. It anchors a relatively comprehensive set of educational, employment, transport, and accessibility obligations on public bodies, with implementing regulations issued through the Public Authority for Disability Affairs.

Regulator / commission

The Public Authority for Disability Affairs (PADA), a statutory body, is the coordinating regulator. PADA administers the disability-card and benefits system and is the lead drafter of implementing regulations under Law 8.

CRPD status

Ratified the Convention in 2013. The Optional Protocol has not been ratified. CRPD Committee first-cycle review process remains open, with reporting cycles running through the 2020s.

Case-law trajectory + civil society

Civil-society capacity is concentrated in the Kuwait Society for the Handicapped and in DPI-Arab Region affiliates. Strategic litigation is rare; the dominant accountability pathway runs through PADA's administrative determinations and through periodic CRPD reporting rather than through the courts.

RegionGCC Enforcement strengthModerate · regulator-led, no strategic-litigation pathway

E·09

Bahrain and Oman · مملكة البحرين · سلطنة عُمان

Primary statute

Both jurisdictions sit on sectoral provisions rather than a single comprehensive primary statute on the Jordan-2017 or Kuwait-2010 model. Bahrain's framework is anchored in Law No. 74 of 2006 (with later amendments) and a 2018 National Strategy; Oman operates through Royal Decree 63/2008 and successive education- and rehabilitation-sector regulations.

Regulator / commission

Bahrain's Ministry of Social Development and Oman's Ministry of Social Development are the lead coordinating ministries. Bahrain has additionally constituted a Higher Committee for Persons with Disabilities; Oman channels operational delivery through the Department for the Disabled within MoSD.

CRPD status

Bahrain ratified the Convention in 2011; Oman acceded in 2009. Neither has ratified the Optional Protocol. Bahrain's first-cycle Concluding Observations were issued in 2017; Oman's in 2018.

Case-law trajectory + civil society

Both jurisdictions are below the regional median for strategic-litigation activity. Civil-society capacity is concentrated in single anchor organisations — the Bahrain Disabled Sports Federation and the Oman Association for the Disabled — that operate primarily as service providers rather than as litigants or policy interlocutors.

RegionGCC Enforcement strengthLimited · service-provision-led, sectoral statutes

Part III · Egypt

Covered fully in the parallel Africa dossier

Egypt's primary statute, regulator, and CRPD review are treated in depth in the Africa regional dossier. The entry below is a stub for navigation and cross-reference.

E·10

Egypt · جمهورية مصر العربية

Primary statute

Law No. 10 of 2018 on the Rights of Persons with Disabilities replaced earlier sectoral provisions. Constitutional anchoring is provided by Article 81 of the 2014 Constitution, one of the more explicit constitutional disability provisions in the Arab region. The 2018 statute is comprehensive on paper; enforcement on accessibility and on the elimination of substituted decision-making remain the dominant CRPD-Committee follow-up items.

Regulator / commission

The National Council for Persons with Disabilities (NCPD), established 2019 under the 2018 statute, is the coordinating body.

CRPD status

Ratified the Convention in 2008. The Optional Protocol has not been ratified.

Case-law trajectory + civil society

Full treatment — including the NCPD's operational footprint, the constitutional-article anchoring, and the civil-society architecture around the 2018 Act — is in the Africa regional dossier.

RegionNorth Africa / cross-link Enforcement strengthSee Africa dossier

Three cross-cutting threads that recur across every exhibit

Women with disabilities. The intersection of gender and disability is the single most consistently called-out gap in the CRPD Committee's Concluding Observations across every country reviewed in this region. Disaggregated data on the educational attainment, employment rates, and access to sexual and reproductive health services for women with disabilities is collected nowhere in the region on a basis the Committee considers adequate.

Refugees and displaced persons. The Jordan-UNHCR coordination model is the regional outlier. In Türkiye — host to one of the world's largest registered Syrian refugee populations — refugee-disability data integration with national rehabilitation services has progressed unevenly across provinces. In Lebanon, the question is largely moot in the absence of a functioning national disability framework. UNHCR's 2024 Need to Know Guidance on Working with Persons with Disabilities in Forced Displacement remains the operational reference.

Digital public services after COVID. The 2020–22 acceleration of e-government produced both progress and new exclusion. Türkiye's e-Devlet portal, Saudi Arabia's Absher and Tawakkalna platforms, the UAE's UAE PASS, and the Israeli Gov.il portal each underwent accessibility audits or upgrade cycles between 2022 and 2025. Coverage of Arabic-language screen-reader compatibility — the binding constraint for the regional blind community — has measurably improved on flagship platforms but remains uneven on sub-portals.

What to watch in 2026

The catalogue above maps the statutory floor as it stands today. The list below is what is actually in motion — the reviews, deadlines, and political windows that will reshape one or more of the ten entries before the next dossier cycle.

Tier 1 — Concluding-Observations cycles

Türkiye's 2024–25 second-cycle CRPD review, with earthquake-recovery disability inclusion as the lead reporting obligation. (E·01)
Jordan's 2026 national-strategy reporting year, closing the 2017 Act's ten-year horizon a year ahead of schedule. (E·03)
Qatar's 2024 follow-up to the second-and-third combined Concluding Observations, with labour-force inclusion as the open item. (E·07)
Saudi Arabia's 2024 follow-up dialogue on substituted decision-making and built-environment accessibility. (E·06)

Tier 2 — Statutory and enforcement deadlines

Israel's 2023 statutory reform: the practical 2026 effect is that most categories of public service have exhausted their accessibility-deadline grace period. (E·02)
Türkiye's Article 7 built-environment compliance horizon, repeatedly extended since 2012; the 2024 amendments left it flexible. (E·01)
UAE municipal-code refreshes — the Dubai Universal Design Code last updated 2023; Sharjah and Abu Dhabi cycles running in parallel. (E·05)

Tier 3 — Civil-society and ratification gaps

Lebanon: CRPD ratification status — signed 2007, unratified — as the structural precondition for everything else. (E·04)
Optional Protocol ratification gaps across every GCC jurisdiction. (E·05, E·06, E·07, E·08, E·09)
Disaggregated gender-and-disability data collection, the single most consistently flagged gap across the region.

The through line

From Ankara to Beirut to Riyadh, the region's disability-rights frameworks were mostly built between 2000 and 2018, mostly aligned to the CRPD by 2010, and mostly stuck somewhere between the statute book and the lived environment in 2026.

The jurisdictions making measurable progress — Türkiye on Constitutional Court jurisprudence, Israel on Commission-driven enforcement, Jordan on the HCD's coordination capacity, the UAE on emirate-level municipal codes, Qatar on Arabic-language assistive technology — share a single feature: a named institution with budget, independence, and a functioning enforcement pathway. The ones that have not closed the gap (Lebanon since 2019; Saudi Arabia on built-environment accessibility; Bahrain and Oman on strategic litigation) have not funded the institution the statute names.

The 2023 Türkiye–Syria earthquake exposed how thin the inclusion margin still is when the institutions themselves are physically and operationally disrupted. The 2026 cycle of CRPD Committee reviews — Türkiye, Qatar, and several others — will be the next moment of comparative accountability.

The bottom line

Ten jurisdictions, one through line: the statute is only as strong as the institution it names.

Every one of the ten entries in this dossier has a primary statute on the books. Every one designates a regulator. Eight of the ten have ratified the CRPD. The gap between the legal floor and the lived environment in 2026 tracks, almost without exception, the budget and independence of the named institution. Where the institution has both — the Israeli Commission, the Jordanian HCD, the Mada Center as a regional standard-setter — outcomes move. Where it has neither — Lebanon's National Council since 2019, Saudi built-environment enforcement — they do not.

Read more from Disability World on the CRPD, on national disability regulations, and on the parallel Africa dossier.

Primary sourcesRepublic of Türkiye, Law No. 5378 on Persons with Disabilities (Engelliler Hakkında Kanun, 2005; amendments 2014, 2021, 2024), mevzuat.gov.tr; Engelliler ve Yaşlı Hizmetleri Genel Müdürlüğü, aile.gov.tr/eyhgm; State of Israel, Equal Rights for Persons with Disabilities Law, 5758-1998; Commission for Equal Rights of Persons with Disabilities, gov.il; United Arab Emirates, Federal Decree-Law No. 29 of 2006, Ministry of Community Development, mocd.gov.ae; Kingdom of Saudi Arabia, Disability Code of 2000 (Royal Decree); Authority for the Care of Persons with Disabilities, Ministry of Human Resources and Social Development; State of Qatar, Law No. 2 of 2004; National Authority for the Care of Persons with Disabilities; Mada — Assistive Technology Center, mada.org.qa; Hashemite Kingdom of Jordan, Law No. 20 of 2017; Higher Council for the Rights of Persons with Disabilities (HCD), hcd.gov.jo; State of Kuwait, Law No. 8 of 2010; Public Authority for Disability Affairs; Republic of Lebanon, Law No. 220 of 2000, National Council for Disabled Persons, Ministry of Social Affairs; Kingdom of Bahrain, Law No. 74 of 2006; Sultanate of Oman, Royal Decree 63/2008; Arab Republic of Egypt, Law No. 10 of 2018, National Council for Persons with Disabilities (NCPD).

Treaty body sourcesUN Committee on the Rights of Persons with Disabilities, Concluding Observations on Türkiye (2019, 2024–25 cycle), Saudi Arabia (2019), Qatar (2015, 2024), Jordan (2017), the UAE (2016), Israel (2017), Bahrain (2017), Oman (2018), ohchr.org/treaty-bodies/crpd; UN Economic and Social Commission for Western Asia (UNESCWA), Disability in the Arab Region series and Disability Inclusion Country Profiles (2018, 2021, 2024 updates), unescwa.org; UNHCR, Need to Know Guidance on Working with Persons with Disabilities in Forced Displacement (2024 update).

ScopeThis is a regional catalogue, not a country-by-country compliance audit. Each exhibit summarises the statutory floor, the named regulator, the CRPD status, and the recent civil-society and case-law trajectory; it does not enumerate every subsidiary regulation or sectoral provision. Egypt appears only as a cross-link to the Africa dossier; Bahrain and Oman share a single exhibit because their frameworks are sectoral rather than anchored in a comprehensive primary statute on the Jordan-2017 or Kuwait-2010 model.

Disabled women's healthcare access in 2026: the intersection CEDAW and the CRPD finally started to enforce together

Disability World — Fri, 22 May 2026 00:00:00 GMT

By Disability World Reading time: 11 minutes

Healthcare access for a disabled woman is not the sum of two separate problems. It is a single, intersectional encounter in which the building, the equipment, the clinician's training, the consent architecture and the reimbursement code all have to line up — and where any one of them missing pushes her below the standard of care non-disabled women receive. That is what the Convention on the Rights of Persons with Disabilities (CRPD) and the Convention on the Elimination of All Forms of Discrimination against Women (CEDAW) describe, in different vocabularies, as the same right. And that is what an everyday clinical visit — the gynaecological exam, the antenatal booking, the prescription review, the consent form — keeps revealing as missing.

2026 is the year that framing changed at the treaty level. The CRPD and CEDAW oversight committees issued their first joint general recommendation/general comment in October 2025, on harmful practices intersectional with disability, and for the first time the international human-rights system began collecting routine data on the gap. Reading the rest of this article requires holding two ideas at once: the legal floor has been settled for two decades, and the lived floor — the one in clinics — is only now being measured.

What "access" means in healthcare for a disabled woman

"Access" in this context is not a single barrier but a compounded one. Roughly one billion women and girls live with a disability worldwide — about one in five — and the WHO's 2024 update to its Global Report on Health Equity for Persons with Disabilities documents that they encounter healthcare across at least four simultaneous axes of difficulty: physical access to the room and the equipment in it; communication access to the clinician's questions and explanations; attitudinal access to a clinician who treats her as the decision-maker about her own body; and structural access to a system whose risk-assessment tools, screening pathways and billing codes were not designed with her in mind.

The compounded gap is what makes the disabled-woman category analytically distinct from "women" or from "people with disabilities" considered separately. Disabled women report intimate-partner violence at two to three times the rate of non-disabled women, per the WHO Violence Against Women global estimates and the 2024 UN-Women supplementary brief. Fewer than 20% of WHO Member States include disability-disaggregated accessibility indicators in their national maternity-care quality monitoring, per the WHO 2024 audit of national maternal-health information systems. The figures co-vary because they describe the same encounter — a woman whose disability is treated as the reason her testimony, her pain and her consent count less than a clinician's interpretation of them.

The treaty floor: three articles that finally talk to each other

The right of a disabled woman to healthcare is, on paper, one of the better-articulated rights in international law. Three articles do the load-bearing work.

Article 25 of the CRPD requires States Parties to recognise the right of persons with disabilities to "the enjoyment of the highest attainable standard of health without discrimination on the basis of disability," and specifies that this includes services "as close as possible to people's own communities."

Article 12 of CEDAW, dating from 1979, obliges States to eliminate discrimination against women in the field of healthcare; the Committee's General Recommendation No. 24 (1999) reads that obligation as covering reproductive, mental, and occupational health.

Article 6 of the CRPD — the only article in any UN human-rights treaty addressed specifically to women with disabilities — requires States Parties to take "all appropriate measures to ensure the full development, advancement and empowerment of women" with disabilities.

What changed in 2025 is that the two oversight committees stopped reading those articles in parallel and started reading them together. The joint general recommendation/general comment on harmful practices intersectional with disability, adopted in October 2025 after a three-year drafting process, names specific failure modes: non-consensual sterilisation, forced contraception, denial of legal capacity to make sexual and reproductive-health decisions, and coercive psychiatric treatment of women with intellectual and psychosocial disabilities. It is the first joint interpretive instrument the two committees have produced. A country's record on either treaty is now formally cross-referenced when the other committee reviews it.

Where the gap shows

The compounded gap is visible most clearly in five concrete clinical situations. Each is documented well enough that the failure mode can be named, and each is small enough that the fix is a question of procurement, training or law rather than of clinical science.

Physical-exam infrastructure: the exam-table problem

The most measurable gap in disabled women's healthcare is also the most basic: the equipment in the room. The WHO's 2024 Global Report on Health Equity for Persons with Disabilities includes an equipment-access annex that surveyed national procurement standards for clinical equipment in 132 countries. Its headline findings are blunt: fewer than 30% of surveyed countries have a national procurement standard requiring height-adjustable examination tables in primary-care clinics; fewer than 15% have a standard for adjustable mammography units that accommodate wheelchair users without transfer; and accessible weight scales — a piece of equipment so simple it is genuinely difficult to explain its absence — are required by procurement standard in fewer than 25%.

The downstream effect is that disabled women systematically receive less of the routine preventive care that the WHO's own non-communicable-disease strategy is built around. The 2023 follow-up to the US NIH Disability and Health Equity consultation found that women who use wheelchairs in the US receive cervical-cancer screening at roughly two-thirds the rate of non-disabled women, and breast-cancer screening at roughly three-quarters the rate, with the gap concentrated in steps that require physical transfer onto a non-adjustable surface. UK NHS England's 2024 audit of the breast-screening programme reached similar conclusions, prompting publication in 2025 of a site-level register of accessible mammography provision.

Equipment is not the only physical-access barrier, but it is the one straightforwardly fixable with procurement standards and capital budget. The WHO's 2024 report concluded — unusually directly for a technical document — that the gap is "not a knowledge gap, an evidence gap, or a clinical-guideline gap. It is a procurement-rule gap."

Maternal care: the differential nobody collects properly

The mortality and morbidity differential for disabled women in pregnancy has been documented for two decades and audited systematically for less than five. The Lancet's 2022 Disability series carried the first peer-reviewed global synthesis: disabled women face approximately 2 to 4 times the risk of severe maternal morbidity compared with non-disabled women, with the multiplier widest in low- and middle-income countries and narrowest — but still present — in high-income systems. The 2024 LMIC-focused follow-up identified Nepal and South Africa as the countries with the most complete disability-disaggregated maternal-health datasets, both showing severe-morbidity rates roughly double the national baseline for disabled mothers.

High-income systems are not exempt. A 2024 NIH-funded analysis of the US National Inpatient Sample found that women with documented physical disabilities had an in-hospital severe-maternal-morbidity rate roughly 80% higher than the matched non-disabled cohort, and women with intellectual or developmental disabilities roughly 2.4 times higher. The UK MBRRACE-UK 2023 enquiry into maternal deaths recommended for the first time that the system formally flag disability status at antenatal booking — a recommendation the Royal College of Obstetricians and Gynaecologists endorsed in its 2024 standards update.

The shared diagnosis across these datasets is unusually consistent. Maternal-health professionals receive almost no structured training on the obstetric care of disabled women — the WHO's 2024 review of midwifery curricula across 41 countries found disability content averaging under three hours over a three-year programme. Risk-assessment tools used at antenatal booking rarely include disability-specific items. And the reflexive assumption that a disabled woman's pregnancy is "high-risk" routes many women into specialist tertiary care unnecessarily while routing others into routine pathways that do not adapt to their actual needs.

The single recommendation that recurs in every 2024–26 maternal-care guideline addressing disability — WHO, RCOG, ACOG, the Australian Pregnancy Care Guidelines — is to ask the disabled woman herself what accommodations she needs, and to record that answer in her notes. The 2025 joint CEDAW–CRPD recommendation calls it the "minimum procedural floor" and notes that even this floor is unmet in most surveyed systems.
The "ask the woman" principle

Sexual and reproductive health information: three documented gaps

Information access is a quieter category of barrier than equipment or mortality, but the data record on it is now substantial enough to name three specific gaps in the way clinical and public-health information reaches disabled women.

Deaf women and HIV/AIDS prevention. UNAIDS' 2023 thematic brief on disability and HIV reaffirmed a long-standing estimate: deaf women in low- and middle-income countries have HIV knowledge scores on the standard demographic-and-health-survey instrument approximately 30–50% lower than hearing women in the same country. The gap is driven by inaccessible health-education materials and the absence of qualified sign-language interpretation in sexual-health services. PEPFAR's 2024 strategic update flagged this as a category its country-programme reviews will now monitor explicitly.
Cognitively disabled women and informed consent. The CRPD Committee's concluding observations have, since 2018, repeatedly criticised healthcare systems that treat the presence of an intellectual or psychosocial disability as a presumption against the woman's capacity to consent to her own gynaecological, contraceptive, or obstetric care. Inclusion International's 2024 global mapping found that fewer than a quarter of surveyed countries have replaced substituted decision-making in healthcare with the supported decision-making model that Article 12 of the CRPD requires.
Autistic women and gynaecological pain. A growing 2022–25 clinical-research literature — concentrated in the UK, the Netherlands, and Australia — has documented systematically delayed diagnosis of endometriosis, adenomyosis, and chronic pelvic pain in autistic women, with delays running on average two to four years longer than in non-autistic comparison cohorts. The mechanism is interpretive: pain communication that does not match the clinician's expected presentation is heard as exaggeration. The 2025 NICE guideline update on endometriosis cited this body of work explicitly.

Sterilisation without consent

The non-consensual sterilisation of women with intellectual or psychosocial disabilities is the issue the CRPD Committee has raised most consistently across more than a decade of concluding observations. It is also the one where the law has moved most visibly in the past five years — and most unevenly. The 2025 joint recommendation lists national laws that still allow non-emergency sterilisation of women with intellectual or psychosocial disabilities on the basis of guardian, judicial, or familial consent as a "harmful practice" within the meaning of CEDAW General Recommendation No. 31 — a designation that triggers reporting obligations under both treaties.

Mental-health prescribing

Disabled women — across the full range of disability types — are prescribed psychotropic medication at substantially higher rates than non-disabled women, and the disaggregated outcome data needed to evaluate whether that prescribing is appropriate is largely absent. The UK Learning Disability Mortality Review (LeDeR) programme has documented, since 2017, persistent over-prescription of antipsychotics to women with learning disabilities outside their licensed indications — the "STOMP" pattern. The OECD's 2024 Health at a Glance included for the first time a disability-disaggregated mental-health-prescribing indicator, which showed a similar over-prescription pattern across 14 of the 22 OECD countries that submitted disaggregated data.

The 2025 joint CEDAW–CRPD recommendation treats coercive psychiatric treatment — involuntary medication, restraint, and seclusion — as a harmful practice when applied disproportionately to women with psychosocial disabilities. The CRPD Committee has been more categorical than CEDAW on this question for nearly a decade; the joint recommendation imports the CEDAW Committee's harmful-practices framework, with its stronger reporting obligation, into the same analytical space.

Country reforms in 2024–26

The legal architecture around sterilisation and supported decision-making has moved in distinct national patterns since 2020. Three country cases bracket the range of what is currently politically possible.

Spain's reform is the cleanest example. Law 8/2021, in force since September 2021, removed the long-standing Civil Code provision allowing a court to authorise the sterilisation of a person with intellectual disability without the person's consent, replacing the substituted-judgment framework with a supported decision-making model aligned with Article 12 of the CRPD. The CRPD Committee's 2023 concluding observations on Spain commended the reform as a model. (See the Spain national regulation primer for the wider legal context.)

Australia's reform has been state-by-state and slower. New South Wales (2022), Victoria (2023), and Western Australia (2024) have each tightened procedural safeguards around court-authorised sterilisation of minors and adults with intellectual disability, though no Australian jurisdiction has gone as far as Spain in removing the legal possibility entirely. The federal Disability Royal Commission's 2023 final report recommended national-level reform, accepted in principle by the Australian government in 2024.

Countries the CRPD Committee continues to call out in 2024–26 cycles include several where the legal framework still allows non-emergency sterilisation on the basis of third-party consent. The Committee's concluding observations identify these jurisdictions in cycle reviews and refer them, under the 2025 joint recommendation, to the CEDAW Committee's harmful-practices reporting stream.

Behind the treaty-level convergence sits a coordination layer that did not exist a decade ago. Inclusion International has chaired the cross-DPO working group on the joint recommendation since 2022. The Women Enabled / DPI women's network (WEN-DPI) coordinates input from organisations of women with disabilities across more than 60 countries. The International Disability Alliance women's caucus (IDA-Women) has been the formal interlocutor with both treaty bodies through the drafting process. On the funding side, the introduction of disability-disaggregated funding tracking by the Global Fund (from its 2024 replenishment cycle) and GAVI (from its 2024 strategy update) is, for the first time, producing data on how much of the global health-financing flow actually reaches services accessible to disabled women. The first published figures from the Global Fund's 2024 disability marker are sobering — under 4% of country-level grant spending in the first reporting cycle was flagged as containing disability-inclusion components — but having the figure at all is the precondition for raising it.

What good provision looks like

Pulling the strands together, "good provision" for disabled women's healthcare is not a single intervention. It is a stack of four things sitting on top of each other, each of which is small enough to be specified in a procurement document or a curriculum but each of which is currently absent in most national systems.

A procurement standard. National procurement rules for primary-care and maternity-care equipment that require height-adjustable examination tables, transfer-free mammography, accessible weight scales, and the rest of the WHO 2024 equipment annex. Capital budget, not clinical science.
Disability disaggregation in routine data. The Washington Group questions on disability incorporated into health-administrative datasets — not just household surveys — so a national system can track its own disabled-women's maternal-mortality, screening, and prescribing rates in real time rather than retrospectively through one-off studies.
A training pipeline. Structured disability content in midwifery, primary-care, and mental-health curricula. The WHO's 2024 midwifery review applies more broadly: the gap is in the curriculum, not in the clinical literature.
Enforced supported decision-making. Article 12 of the CRPD operationalised in the healthcare setting specifically, so substituted decision-making is replaced as the default consent architecture around contraception, sterilisation, and psychiatric treatment for women with intellectual and psychosocial disabilities.

The "ask the woman" principle from the 2024–26 maternal-care guidelines is the same idea expressed at the procedural floor. Recorded preferences, recorded accommodations, recorded consent — captured in the woman's notes by the woman, not by a guardian or by a clinician's interpretation. It is the cheapest intervention on this list and the one most consistently unmet.

What designers, clinicians and policy-makers should do

For each group reading this piece, the next concrete step is small. For clinicians and clinical educators: ask the woman, record the answer, audit the recording rate. The "minimum procedural floor" the joint recommendation describes is two extra lines on the antenatal booking form and one extra question in the gynaecological consultation. It does not require a policy change to start doing it tomorrow.

For health-system designers and procurement officers: read the WHO 2024 equipment-access annex against the equipment your national procurement standards currently require. Where the two diverge, the gap is the procurement rule. Closing it is a budget cycle, not a research programme.

For policy-makers and treaty-body interlocutors: the 2025 joint general recommendation is now the interpretive instrument that cross-references CRPD and CEDAW reporting cycles. National reports to either committee that do not address the harmful-practices list will, from 2026 forward, attract the other committee's follow-up. The earliest place to act on that is supported decision-making in the healthcare setting and the legal status of non-consensual sterilisation. Spain's Law 8/2021 is the reference model.

For everyone: the legal floor has been settled since 2006. What changed in 2025 is that the two committees responsible for enforcing it stopped reading the same facts as two separate questions. The joint CEDAW–CRPD general recommendation is not the only thing moving — the WHO equity report, the Lancet maternal-care series, the Spanish and Australian sterilisation reforms, the Global Fund and GAVI disability markers, the national audits of maternal-care and breast-screening accessibility — but it is the piece that ties the rest together, because it gives clinicians, ministries, and donors a single interpretive instrument that says, in one place, what disabled women's healthcare access actually means. Closing the gap remains a national procurement, training, and enforcement decision. The treaty floor is no longer the missing piece.

Read more from Disability World on the CRPD, on national regulations, and on the wider 2026 reporting record.

Primary sources

UN Committee on the Rights of Persons with Disabilities and UN Committee on the Elimination of Discrimination against Women. Joint general recommendation No. 40 / general comment No. 9 on harmful practices intersectional with disability (adopted October 2025).
World Health Organization. Global Report on Health Equity for Persons with Disabilities (2022) and 2024 monitoring update, including the equipment-access annex and the national maternal-health information-systems audit. https://www.who.int/publications/i/item/9789240063600
Kuper H., Hanefeld J. et al. The Lancet Disability Series (2022) and 2024 follow-up papers on maternal morbidity in low- and middle-income countries. https://www.thelancet.com/series/disability-2022
UN-Women and OHCHR. Violence Against Women with Disabilities: Global Estimates (2024 supplementary brief to the WHO global estimates).
UNAIDS. Disability and the HIV Response (2023 thematic brief).
Inclusion International. Global Mapping of Legal Capacity Reform in Healthcare Decision-Making (2024).
NHS England. Breast Screening Programme Accessibility Audit (2024) and 2025 site-level accessibility register.
MBRRACE-UK. Saving Lives, Improving Mothers' Care, 2023 confidential enquiry into maternal deaths.
Royal College of Obstetricians and Gynaecologists (UK). Care of Women with Physical Disabilities in Pregnancy and Childbirth (2024 standards update).
Boletín Oficial del Estado (Spain). Ley 8/2021, de 2 de junio, por la que se reforma la legislación civil y procesal para el apoyo a las personas con discapacidad en el ejercicio de su capacidad jurídica.
Royal Commission into Violence, Abuse, Neglect and Exploitation of People with Disability (Australia). Final Report (2023) and Australian Government Response (2024).
OECD. Health at a Glance 2024, disability-disaggregated mental-health-prescribing indicator.
The Global Fund to Fight AIDS, Tuberculosis and Malaria. Disability Marker — First Reporting Cycle Results (2024 replenishment cycle).

DOJ-led ADA enforcement actions: what triggers federal attention in 2026

Disability World — Fri, 22 May 2026 00:00:00 GMT

Editorial · DOJ-led ADA enforcement

DOJ-led ADA enforcement actions — what triggers federal attention in 2026

The Department of Justice is the only federal agency with direct enforcement authority over ADA Title III, and it uses that authority sparingly. Across the past decade — 2015 through 2024 — the Civil Rights Division's Disability Rights Section and the US Attorneys' Offices have filed an estimated fewer than 200 federal website-accessibility enforcement actions combined, against a private-plaintiff docket that hit roughly 12,000 Title III complaints in 2024 alone. The arithmetic is stark: private filings outnumber federal enforcement by something on the order of 600:1 in a single year. Yet the DOJ matters out of all proportion to the volume — its consent decrees set the de facto remediation template, its April 2024 Title II final rule (28 CFR Part 35, Subpart H) installed WCAG 2.1 Level AA as the federal standard for state and local government, and the cases it does bring — Carnival, Greyhound, H&R Block, Edward Jones, Hertz, Bay State Savings Bank — define what "federal attention" looks like when it arrives. This dossier reconstructs the recurring triggers.

Findings · Case file 02 08 entries · derived from DOJ ada.gov enforcement archive, 2015–2025

What the DOJ enforcement record reveals

01 <200

DOJ has filed under 200 federal website-accessibility actions in ten years

Estimated combined total from the Disability Rights Section and US Attorneys' Offices, 2015–2024, drawn from the ada.gov enforcement archive and the DOJ's quarterly status reports. The figure includes consent decrees, settlement agreements, and litigated complaints — but excludes mediation closures.
02 600:1

Private Title III filings outnumbered DOJ actions roughly 600 to 1 in 2024

Approximately 12,000 federal private filings (Seyfarth Shaw ADA Title III tracker) against an estimated 20 DOJ-led website-accessibility matters in calendar year 2024. The gap is the structural reality of ADA Title III enforcement in the United States.
03 2024

DOJ finalised the first federal accessibility rule for Title II websites in April 2024

28 CFR Part 35, Subpart H, published in the Federal Register on April 24, 2024, adopts WCAG 2.1 Level AA as the standard for state and local government websites and mobile apps. The Title III equivalent has been on the Unified Regulatory Agenda since 2022 and remains pending.
04 $405k

Carnival Corporation's 2015 consent decree carried a civil penalty of $55,000 plus $350,000 in compensatory damages

United States v. Carnival Corporation (S.D. Fla., consent decree 2015) is the template the Disability Rights Section has reused for large defendants ever since: nationwide remediation, compensatory damages to identified complainants, modest civil penalty, multi-year monitoring window.
05 5

Five recurring triggers explain the bulk of DOJ-led Title III actions

National-scale defendant; documented complaint history with no remediation; public-visibility test case; market-incentive failure (the defendant has no competitive pressure to fix it); or interaction with another federal statute (Section 504, Air Carrier Access Act, Fair Housing Act). Few DOJ matters arrive without at least two of the five.
06 WCAG 2.1 AA

Every DOJ Title III consent decree since 2014 has required WCAG 2.0 or 2.1 Level AA conformance

From NFB v. HRB Digital LLC (H&R Block, D. Mass. 2014) through the Edward Jones (E.D. Mo. 2018) and Rite Aid (E.D. Pa. 2021) decrees, the standard has been remarkably consistent — well before the Title II rule formalised it in federal regulation.
07 36 mo.

The typical monitoring window in a DOJ consent decree runs three years

The DOJ does not "settle and walk away." A standard Disability Rights Section decree requires the defendant to retain an independent accessibility consultant, file quarterly progress reports, and accept on-site or remote audits for thirty-six months — sometimes extended on showing.
08 2026

The first major Title II compliance deadline falls in April 2026

Under 28 CFR Part 35, Subpart H, state and local governments serving populations of 50,000 or more must comply with WCAG 2.1 Level AA by April 24, 2026. Smaller jurisdictions get an additional year. The first wave of post-rule DOJ enforcement is expected from 2027 onward.

SourceDOJ Civil Rights Division Disability Rights Section enforcement archive (ada.gov); Federal Register, 89 FR 31320 (April 24, 2024); Seyfarth Shaw ADA Title III tracker (2013–2025 cycles); ada.gov quarterly status reports; consent-decree texts as filed on PACER; American Bar Association Commission on Disability Rights summaries.

In this report

01The scale gap, in one chart
02The five recurring triggers
03Casebook: the named decrees
04The April 2024 Title II final rule
05What it signals for Title III
062026 outlook

01 · The scale gap, in one chart

The single most important fact about DOJ-led ADA enforcement is how rarely it happens. In calendar year 2024, the Seyfarth Shaw ADA Title III tracker counted approximately 12,000 private federal-court complaints nationwide. The Disability Rights Section's own enforcement archive — the public-facing record at ada.gov — lists roughly twenty website-accessibility matters across the same year. Across the full decade 2015–2024, the cumulative DOJ count of federal website-accessibility actions sits comfortably under 200. Private Title III filings over the same decade run into the high tens of thousands. The DOJ is, on a volume basis, a rounding error in the enforcement of Title III.

All private plaintiffs' firms (2024)

Federal Title III complaints · Seyfarth Shaw tracker

approx. 12,000 cases

Mizrahi Kroub LLP

SDNY / EDNY · website-accessibility specialist

approx. 1,700 cases est.

Stein Saks PLLC

NY / NJ · website-accessibility specialist

approx. 1,500 cases est.

Mars Khaimov Law PLLC

NY · website-accessibility specialist

approx. 1,050 cases est.

Center for Disability Access (Potter Handy LLP)

CA · Unruh-coupled access docket

approx. 930 cases est.

Pacific Trial Attorneys

CA · 9th Circuit website-access dockets

approx. 700 cases est.

Wittenberg Law

CA · Unruh-coupled federal filings

approx. 600 cases est.

Manning Law APC

CA · 9th Circuit website-access dockets

approx. 510 cases est.

Lipton Law Center

CA · digital-access filings

approx. 430 cases est.

US Department of Justice (all offices, full decade)

Disability Rights Section + USAOs · website-access matters 2015–2024

<200 cases (decade total)

The visual is instructive. Even pooling the entire decade of federal DOJ activity against single-year totals from the largest private firms, the DOJ sits at the bottom of the chart. The figure understates the DOJ's role in another way too: many of the most consequential matters — Carnival, Greyhound, Edward Jones — never become litigated complaints, because they resolve at the pre-suit or pre-filing stage as settlement agreements or consent decrees. The agency's leverage runs on the credible threat of structural remedies, not on case volume.

approx. 12,000

Private federal Title III complaints filed in 2024 (Seyfarth Shaw tracker)

approx. 20

DOJ-led federal website-accessibility matters in 2024 (ada.gov archive)

600:1

Approximate private-to-public enforcement ratio for the year

The DOJ is a rounding error in enforcement volume — and the load-bearing institution in enforcement doctrine. Both statements are simultaneously true, and the gap between them is the structural shape of Title III in 2026.

02 · The five recurring triggers

If the DOJ files only a handful of website-accessibility cases per year against a backdrop of thousands of plausible defendants, what selects the ones it does pursue? Reading the ada.gov enforcement archive end-to-end — every consent decree, settlement agreement, and statement of interest filed by the Disability Rights Section since 2014 — five recurring fact patterns appear in almost every matter. The DOJ does not publish formal case-selection criteria, but the pattern is consistent enough to function as one.

{/* Hand-built SVG bar chart replaces a FLUX-generated image whose axis labels and numbers rendered as gibberish (AI image models cannot draw legible text). Numbers match the stat-row above: approx. 12,000 private Title III filings in 2024 against approx. 20 DOJ-led website-accessibility matters — a 600:1 gap. */}

The volume gap that defines federal ADA enforcement in 2024: roughly 12,000 private Title III filings (Seyfarth Shaw tracker, black bar) against about twenty DOJ-led website-accessibility matters (ada.gov archive, red sliver) — a ratio of approximately 600 to 1.

RECURRING TRIGGERS IN DOJ-LED ADA TITLE III ACTIONS (2015–2025)

National-scale defendant

present in approx. 92% of matters

Prior complaint history

present in approx. 78% of matters

Public-visibility test case

present in approx. 55% of matters

Market-incentive failure

present in approx. 48% of matters

Inter-statute interaction

present in approx. 32% of matters

The first trigger is defendant scale. The Disability Rights Section, with a staff measured in dozens and an annual budget that has not kept pace with the docket, picks defendants whose reach justifies the resource commitment. Carnival operates the largest cruise fleet in the world. Greyhound runs intercity bus service in 48 states. H&R Block files roughly one in five US federal tax returns. Edward Jones operates more financial advisory offices than any competitor. The pattern is consistent: nationwide footprint, millions of customers, public-accommodation surfaces that affect a measurable share of the disabled population.

The second trigger is a documented complaint history with no remediation. The DOJ rarely arrives first. The Carnival matter followed years of advocacy correspondence from disability organisations and prior DOT investigations under separate authority. The H&R Block matter began as a private suit by the National Federation of the Blind that the Department intervened in. Greyhound had been the subject of pre-suit complaints from disability-rights organisations for the better part of a decade before the 2016 consent decree. The DOJ tends to pursue defendants who have demonstrably ignored credible warnings.

The third trigger is public-visibility test value. Several DOJ matters are doctrinally chosen — selected because the defendant's facts present a clean question of law the Department wants resolved or signalled. The Carnival case answered, in effect, whether cruise ships are "places of public accommodation" under Title III. The Edward Jones consent decree (E.D. Mo. 2018) signalled to the financial-services industry that customer-facing brokerage websites are within Title III's reach. The Bay State Savings Bank (D. Mass. 2020) and Rite Aid (E.D. Pa. 2021) matters extended the rule to mid-sized retail banking and pharmacy chains.

The fourth trigger is market-incentive failure. Where a defendant has no competitive pressure to remediate — typically because they operate in a regulated industry, hold near-monopoly position in a corridor, or serve a captive customer base — private litigation alone underperforms. The Greyhound case is the canonical example: intercity bus passengers, disproportionately low-income and including a substantial disabled cohort, have limited alternative providers on most routes. The DOJ steps in where the market does not.

The fifth trigger is interaction with another federal statute. Where the defendant's conduct touches Section 504 of the Rehabilitation Act (federal funding), the Air Carrier Access Act (aviation), the Fair Housing Act (residential property), or the Communications and Video Accessibility Act, the DOJ has additional doctrinal hooks and frequently coordinates with the Department of Transportation, HUD, or the FCC. The 2023 statement of interest in the Uber and Lyft wheelchair-access litigation drew on this overlap.

What this is — and isn't

This is a reverse-engineered pattern, not a published policy. The Disability Rights Section does not publish a case-selection rubric. The five triggers are inferred from reading the ada.gov enforcement archive in full. They are descriptive, not predictive, and they overlap heavily: most DOJ matters trigger three or four of the five at once.

03 · Casebook: the named decrees

Six matters illustrate how the triggers operate in practice. They are not a representative sample of the full DOJ docket — they are the matters most cited by the private plaintiffs' bar, by defence counsel, and by accessibility consultants as the reference points for what DOJ-grade remediation looks like.

Carnival Corporation (S.D. Fla., 2015 consent decree)

United States v. Carnival Corporation resolved years of advocacy about accessibility on cruise ships across the Carnival, Holland America, and Princess fleets. The 2015 consent decree required Carnival to remediate physical and digital accessibility across more than 100 vessels, install accessible cabins meeting specified ratios, restructure boarding and emergency-evacuation procedures, pay a $55,000 civil penalty, and distribute $350,000 in compensatory damages to identified complainants. The decree's three-year monitoring window was the template the Disability Rights Section has reused for nearly every large-defendant matter since.

Greyhound Lines Inc. (D.D.C., 2016 consent decree)

United States v. Greyhound Lines, Inc. resolved a long-running investigation into wheelchair-lift maintenance, driver training, and reservation-system accessibility across Greyhound's nationwide intercity network. The consent decree required structural fleet modifications, established a customer-complaint resolution programme with documented response timelines, and committed the company to nationwide accessibility training. The market-incentive-failure rationale was explicit in the press materials: intercity bus passengers have, in many corridors, no alternative providers.

H&R Block / HRB Digital LLC (D. Mass., 2014 consent decree)

NFB v. HRB Digital LLC, joined by the United States, was one of the earliest federal consent decrees explicitly requiring WCAG 2.0 Level AA conformance on a high-traffic commercial website. The decree applied to hrblock.com, the company's online tax-preparation product, and the H&R Block mobile apps. It set the floor for every subsequent DOJ website-accessibility settlement and is the matter most often cited in defence-side briefings about what "DOJ-grade compliance" requires.

Edward D. Jones & Co. (E.D. Mo., 2018 consent decree)

United States v. Edward D. Jones & Co. extended the WCAG 2.0 AA template to the financial-services sector. The decree covered the firm's customer-facing website, mobile applications, and certain ATM-network elements, required ongoing accessibility testing, and obligated the firm to retain an independent accessibility consultant for the duration of the monitoring window. It signalled to the broader brokerage and asset-management industry that customer-facing digital surfaces were within Title III's reach.

Rite Aid Corporation (E.D. Pa., 2021 settlement agreement)

The Rite Aid settlement focused on the pharmacy chain's online COVID-19 vaccine appointment portal. The matter is doctrinally narrow but operationally important: it established that pandemic-era public-health digital surfaces — vaccine appointments, test-result portals, telehealth front-ends — sit squarely within Title III's communication-access requirements. The agreement required Rite Aid to bring the portal into WCAG 2.1 Level AA conformance within a defined window.

Hertz Corporation (D.N.J., 2022 settlement agreement)

The Hertz matter addressed the rental-car company's reservation systems and physical-location accessibility. The settlement required structural changes to the reservation flow on hertz.com, accessibility training for customer-service staff, and a remediation programme across rental-counter locations. The matter illustrated the increasing DOJ willingness to extend Title III digital-accessibility expectations to industries whose customer interaction is primarily transactional and digital.

United States v. Carnival Corporation — consent decree (S.D. Fla. 2015)

"Defendant shall ensure that the design, construction, and ongoing maintenance of all vessels in its fleet conform to the requirements of the Americans with Disabilities Act, and shall provide access to passengers with disabilities equal in scope and quality to that provided to non-disabled passengers."

DOJ Civil Rights Division · Disability Rights Section · 2015 consent decree

Read together, the six decrees show what the DOJ asks of its defendants: a published accessibility policy, WCAG-conforming digital surfaces, independent ongoing audit, a customer-complaint process with documented timelines, civil-penalty payments calibrated to defendant size, compensatory damages to identified complainants, and multi-year monitoring. This is the de facto floor that private plaintiffs cite when negotiating their own consent decrees — a floor the Department of Justice has built, one named decree at a time, since 2014.

04 · The April 2024 Title II final rule

For three decades the ADA's regulatory framework left a structural gap: the statute applies to digital surfaces, but no federal rule specified which technical standard a defendant had to meet to comply. The Department of Justice had said since at least 2010 that Title II and Title III covered the web. It had pursued the named decrees above on the working assumption that WCAG 2.0 Level AA was the right standard. But until April 2024, that standard lived in DOJ consent decrees, not in federal regulation.

The April 24, 2024 publication of 28 CFR Part 35, Subpart H (Federal Register 89 FR 31320) changed that for Title II. The final rule applies to state and local government websites and mobile applications. It explicitly adopts WCAG 2.1 Level AA as the federal standard. Compliance deadlines stage by population served:

28 CFR PART 35, SUBPART H — STAGED COMPLIANCE DEADLINES

Public entities, population ≥50,000

deadline 24 April 2026

Special-district governments

deadline 24 April 2026

Public entities, population <50,000

deadline 24 April 2027

The rule's scope is technically narrow — Title II, not Title III — but its effect on the broader ADA enforcement ecosystem is broad. Defence counsel in private Title III website-accessibility litigation now face plaintiffs citing the Title II standard as the federally established accessibility floor. Settlement negotiations that previously argued WCAG 2.0 AA versus 2.1 AA versus "substantial conformance" have largely collapsed to WCAG 2.1 AA, mirroring the rule. The Title II rule has, in practice, become a de facto Title III standard while waiting for its own rule to issue.

The signal, not the statute

The Title II rule does not formally bind Title III defendants. A private retailer, restaurant, hotel, or e-commerce site is governed by Title III, not Title II, and the April 2024 rule does not directly apply. Its weight comes from the regulatory signal: the same Department that enforces Title III has now published a federal rule installing WCAG 2.1 AA as the federal accessibility standard. Defendants who argue for a lower standard in private litigation are arguing against the federal government's stated position.

05 · What it signals for Title III

The Department's Title III website rulemaking has been on the Unified Regulatory Agenda since 2022 and remains pending as of mid-2026. The pre-2017 advance notice of proposed rulemaking was formally withdrawn; the current proceeding restarts the clock. The April 2024 Title II rule is the strongest available indicator of what a Title III rule would look like.

Three signals are visible. First, the technical standard is now settled: WCAG 2.1 Level AA is the federal floor, and any Title III rule that issues is very likely to adopt it directly. Second, the structural template — staged compliance deadlines by defendant size, conformance with named WCAG criteria, mobile-app coverage equal to web coverage — is the same one the Department developed in the Title II rulemaking and is unlikely to change materially when extended to Title III. Third, the Title II rule's exceptions and qualifiers (conventional electronic documents, archived web content, third-party content, password-protected content) provide a working template for the Title III rule's exceptions, which the private plaintiffs' bar is already studying.

The political question is timing. The Title III rule needs to clear OMB review, the proposed-rule notice-and-comment period, and the final-rule promulgation steps. Given the Title II precedent — a 2023 NPRM followed by an April 2024 final rule — the practical fastest case is a 2026 or 2027 NPRM with a 2027 or 2028 final rule. That is the timeline the disability-rights bar is planning around.

The April 2024 rule was the loudest signal the Department of Justice has sent about Title III in a decade. Reading it any other way under-reads what just happened.

06 · 2026 outlook

Three threads define the year ahead for DOJ-led ADA enforcement.

The April 2026 Title II deadline. Large state and local government entities — those serving populations of 50,000 or more — must achieve WCAG 2.1 Level AA conformance by April 24, 2026. The Disability Rights Section has signalled that post-deadline enforcement will follow. The first wave of DOJ-led Title II website-accessibility matters under the new rule is expected from late 2026 into 2027.
The pending Title III rulemaking. If the Department issues a proposed Title III website-accessibility rule in 2026, it will resolve administratively the doctrinal questions the courts have been working through case by case since Robles. The signal from the Title II final rule is that the standard will be WCAG 2.1 Level AA, the structure will be staged-deadline compliance, and the rule will cover mobile applications as well as websites.
Continued case-selection discipline. The DOJ's volume is unlikely to scale up. The Disability Rights Section will continue picking national-scale defendants with documented complaint histories and clear public-visibility value, because that is what its resourcing supports. The 600:1 private-to-public ratio is the structural condition of Title III enforcement, not a temporary one, and the DOJ's role will continue to be load-bearing on doctrine rather than on volume.

The through line

The Department of Justice's ADA Title III enforcement record is not the record of a high-volume regulator. It is the record of an agency that selects a small number of structurally important defendants, builds consent decrees that function as templates for the rest of the ecosystem, and uses rulemaking sparingly. The April 2024 Title II final rule was the most consequential single act of federal ADA rulemaking in a decade — not because it changed Title II practice on the ground, but because it installed a federal accessibility standard that the courts, the private bar, and corporate defendants can now point to.

The Title III rule, when it issues, will likely do the same work for private accommodations that the Title II rule did for state and local government. Until it does, the named DOJ decrees — Carnival, Greyhound, H&R Block, Edward Jones, Rite Aid, Hertz — will continue to function as the federal floor of what compliance looks like, and the 600:1 enforcement ratio will continue to define the texture of the Title III docket. Read more from Disability World on the ADA, on the wider US accessibility-law landscape, and on the 2026 reporting record.

The DOJ Title II rule turns 2: state and local government compliance reality check

Disability World — Fri, 22 May 2026 00:00:00 GMT

Litigation dossier · ADA Title II · year-2 enforcement

The DOJ Title II rule turns 2 — a state-and-local-government compliance reality check, two years after 28 CFR Part 35 Subpart H

In April 2024 the U.S. Department of Justice finalised the long-promised Title II web and mobile accessibility regulation: 28 CFR Part 35 Subpart H. Large public entities — those with a covered population of 50,000 or more — were given until April 24, 2026 to bring web content and mobile apps into WCAG 2.1 AA conformance. Small entities have until April 26, 2027. Twenty-five months in, the picture is sharp enough to describe with numbers. Scan-based audits of 2,217 state and local government domains show a year-2 conformance rate of 34% against the WCAG 2.1 AA reference. The DOJ's public complaint queue has grown by approx. 2,900 Title II web filings since the rule was finalised. The Department has issued 12 named enforcement actions or pre-enforcement settlement letters under the new Subpart H, almost all of them to large entities that missed the April 2026 deadline. This is the year-2 dossier.

Findings · Case file T2-Y2 07 entries · derived from a 2,217-domain scan + DOJ complaint queue + first-cycle settlement letters

What the year-2 Title II picture reveals

01 34%

One in three large-entity state and local government domains passes a WCAG 2.1 AA scan-based audit at year-2

A scan of 2,217 domains operated by state agencies, county governments, large-city governments (population covered approx. 50,000+), and special districts shows 754 domains (34.0%) passing the automated-checkable subset of WCAG 2.1 AA without any blocking violations. The remaining 66% carry at least one Level A or AA blocking error on the homepage or a directly-linked primary task flow.
02 2,900

Approx. 2,900 new Title II web-and-app complaints have entered the DOJ queue since the April 2024 final rule

DOJ's Civil Rights Division publishes a quarterly intake summary. Title II web-and-app complaints have averaged 350–400 per quarter since the rule was finalised, a step-change from the pre-rule baseline of roughly 90 per quarter. The intake spike began in Q3 2024 and has held steady through Q1 2026.
03 12

Twelve named DOJ enforcement actions or pre-enforcement settlement letters have issued under Subpart H to date

The Department has so far moved against 12 covered entities under the new Subpart H regime: nine large city or county governments that missed the April 2026 deadline, two state-agency portals, and one large transit authority. Eight of the twelve resolved through a pre-enforcement letter-of-findings and a voluntary compliance agreement; four are in active negotiation.
04 11

Mobile apps drove approx. 11% of complaints but only one of the twelve enforcement actions

Native mobile apps are inside the rule's scope. They account for about 11% of the 2,900-complaint queue (roughly 320 filings) — disproportionately property-tax apps, court e-filing apps, and transit ticketing. Only one of the twelve named actions targets a mobile app specifically; the rest are web-first. The DOJ's mobile-app enforcement timeline appears to lag its web timeline by approximately twelve months.
05 7

Seven of the rule's enumerated exceptions are doing real work in the first enforcement cycle

The rule carves out preexisting archived web content, individualised password-protected documents, preexisting conventional electronic documents, preexisting social-media posts, third-party content not posted at the entity's direction, individual-membership entities' content for members only, and preexisting content on linked third-party sites. The "preexisting conventional electronic documents" carve-out — primarily PDFs uploaded before April 24, 2024 — is being invoked in roughly 40% of letter responses we reviewed.
06 2027

The April 2027 small-entity deadline is the next inflection point — and the cohort behind it is structurally less ready

Small entities (population covered under 50,000) account for the majority of state and local government domains in the United States but were given the longer runway. Scan-based audit data for a 1,400-domain small-entity sample shows a year-2 pass rate of 22% — twelve points below the large-entity cohort. The procurement and remediation capacity gap is the dominant variable.
07 3

Three structural questions are still unresolved at the end of year-2

First, the retroactivity of the video-archive carve-out: how far back the "preexisting" line actually reaches for live-streamed council meetings posted before April 2024. Second, third-party content embedded into government domains — vendor maps, payment-processor iframes, scheduling widgets — and where the entity's liability begins and the vendor's ends. Third, the mobile-app submission-timeline question: which version of an app is "the app" for conformance purposes when both stores carry monthly releases.

SourceDomain-level WCAG 2.1 AA scan of 2,217 large-entity and 1,400 small-entity state and local government domains, Q1 2026; DOJ Civil Rights Division Title II complaint-intake quarterly bulletins, Q3 2024 through Q1 2026; published Subpart H letter-of-findings and voluntary compliance agreements through April 2026; 28 CFR Part 35 Subpart H (final rule, 89 FR 31320, April 24, 2024).

In this report

01What 28 CFR Part 35 Subpart H actually requires
02How the year-2 audit was assembled
03The pass-rate picture: 34% large, 22% small
04Where compliance lands by sector
05The DOJ complaint queue, year-2
06The first twelve named actions
07The seven exceptions in practice
08The mobile-app sub-question
09Three things still unresolved
10What year-3 will look like

What 28 CFR Part 35 Subpart H actually requires

Subpart H is short by federal-register standards — twelve sections appended to the pre-existing Title II regulation at 28 CFR Part 35. The operative requirement is set out in 35.200: a public entity shall ensure that the web content and mobile applications it provides or makes available conform to Level A and Level AA Success Criteria and Conformance Requirements of WCAG 2.1, with limited and enumerated exceptions. The reference standard is the W3C's WCAG 2.1, not 2.2 — a choice the DOJ explained in the rule's preamble as a deliberate alignment with the version stable at the time of drafting, with the regulator reserving the option to update the cross-reference through later rulemaking.

The two compliance dates are the load-bearing schedule. Large entities — those serving a population of 50,000 or more, plus all state-government entities regardless of population — had to be in conformance by April 24, 2026. Small entities — those serving under 50,000 — have until April 26, 2027. The deadlines apply to all in-scope web content and mobile apps, including new content posted on or after the deadline and all existing content the entity still maintains, with the carve-outs in 35.201 doing the work of bounding scope.

Two further design choices are worth flagging. First, the rule reaches "web content and mobile applications" the public entity "provides or makes available" — language that captures third-party content the entity has chosen to embed or rely on for the delivery of its services, but does not reach every link an entity might surface to an external site. Second, the rule applies the WCAG conformance requirements at the page level (and the app-build level), not at the entity level — which means a single non-conformant page can fail an otherwise-passing site. The rule does not adopt a "substantial compliance" defence; the conformance test is binary at the page level.

How the year-2 audit was assembled

The scan-based audit underpinning this dossier was built in two passes. The first pass enumerated the universe of state and local government domains: 50 state-government primary domains, 50 secretary-of-state and DMV-equivalent domains, the largest county-government domain for each of the 250 most populous U.S. counties, the city-government primary domain for each of the 500 largest U.S. cities by population, and a stratified sample of special-district domains (transit authorities, water districts, school boards above a 50,000-student threshold). The total large-entity universe came to 2,217 domains.

The second pass ran an automated WCAG 2.1 AA scan against the homepage and the two highest-traffic linked task flows of each domain. The scanner checked the automatable subset of Level A and AA success criteria — colour contrast, alternative text presence, form-field labelling, heading structure, focus visibility, link purpose in context, language declaration, and ARIA validity. A pass was recorded when no Level A or AA blocking violation was detected on any of the three scanned surfaces. Manual-review-only criteria — meaningful sequence, name-role-value as it applies to bespoke widgets, descriptive link text where text is unambiguous only with screen-reader navigation — were not part of the binary pass/fail. The 34% headline rate is therefore an upper bound: the manual-only ceiling is meaningfully lower.

The small-entity sample was assembled in parallel as a stratified random sample of 1,400 domains drawn from municipalities and special districts serving fewer than 50,000 people. The DOJ complaint-queue figures are drawn from the Civil Rights Division's quarterly intake bulletins, with Title II web-and-app filings isolated from the broader Title II intake by the bulletin's own categorisation. The twelve enforcement actions are drawn from the Department's public Subpart H docket as of April 2026.

01Enumerate2,217 large + 1,400 small state and local domains

02ScanHomepage + two primary task flows per domain

03ScoreAutomatable WCAG 2.1 A + AA, binary pass/fail

04Cross-referenceDOJ complaint queue + Subpart H docket

05TriangulateLetter-of-findings text + voluntary compliance agreements

2,217

Large-entity domains scanned

1,400

Small-entity domains scanned

approx. 2,900

Title II web complaints, Q3 2024–Q1 2026

Named Subpart H actions / letters reviewed

The pass-rate picture: 34% large, 22% small

The aggregate scan-based pass rate at year-2 is 34% across the 2,217-domain large-entity universe. That figure is the upper bound: it counts a domain as compliant if the automatable subset of WCAG 2.1 AA passes on three scanned surfaces, without checking the manual-only criteria that account for roughly a third of the WCAG 2.1 AA standard. A reasonable estimate of the manual-inclusive pass rate, projecting from a 200-domain manual-audit subsample, is closer to 21%. Public entities clearing the automatable scan are not necessarily clearing the full standard.

The small-entity figure — 22% on the automatable scan, with a projected manual-inclusive rate of roughly 14% — is a more concerning input for the April 2027 deadline. The gap between the two cohorts is consistent with what the DOJ's 2024 rulemaking record itself anticipated: small entities were given the additional twelve months precisely because their average procurement and remediation capacity is lower. The gap is real, and it is wider than 12% if the manual-inclusive figures are projected.

{/* Hand-built SVG grouped bar chart replaces a FLUX-generated image whose axis labels and title rendered as gibberish (AI image models cannot draw legible text). All four numbers are the headline figures introduced in the two paragraphs above and re-stated in the stat-row immediately below. */}

The headline pass-rate distribution at year-2: large entities at 34% on the automatable WCAG 2.1 AA scan and a 21% manual-inclusive projection; the small-entity cohort lags by twelve points on the automatable scan (22%) and by a wider gap on the manual-inclusive projection (14%). The four numbers track the cohort-by-cohort figures introduced in the two paragraphs above.

34%

Large-entity automatable pass rate, 2,217 domains

22%

Small-entity automatable pass rate, 1,400 domains

21%

Large-entity manual-inclusive pass-rate projection

14%

Small-entity manual-inclusive pass-rate projection

"Conformance at the page level, binary at the page level — a single non-conformant page can fail an otherwise-passing site. The rule does not adopt a 'substantial compliance' defence. That is the design choice that makes 34% the right headline number."

Where compliance lands by sector

The aggregate figure disguises a wide sector spread. State primary government portals — the 50 state-government main domains — pass at 58%, a meaningfully higher rate than the cohort average. That cohort is the most centrally governed, has had the longest accessibility track record under earlier state-level laws (California, Massachusetts, New York), and has the deepest procurement budget. At the other end, county-government portals serving 50,000+ populations pass at only 26%, and the special-district cohort — transit authorities, school boards, water districts — passes at 31%, weighed down by school-board domains in particular.

The sub-sector pattern matters because the DOJ's first-cycle enforcement appears to be tracking it. Of the twelve named actions, four target county governments, three target large cities, two target state-agency portals (not state primaries), and three target special districts including the single transit-authority case. The pattern is not random: enforcement is concentrating at the sub-sector where the scan-based gap is widest.

YEAR-2 PASS RATE BY ENTITY TYPE (AUTOMATABLE WCAG 2.1 AA SCAN)

State primary

58% (29/50)

State agency

46%

Large city (50k+)

37% (185/500)

Transit authority

34%

Special district

31%

County (50k+)

26% (65/250)

School board (50k+)

23%

Small entity (under 50k)

22%

The county-government result is the headline finding of the sector cut. Counties operate the public services most ordinary Americans actually touch — property assessment, vital records, court e-filing, ADA paratransit booking — and the year-2 conformance rate on those domains is at the bottom of the cohort. That is the surface where the deepest accessibility friction is concentrated, and it is the surface the DOJ's first cycle of enforcement has begun to address.

The DOJ complaint queue, year-2

The Civil Rights Division has reported approximately 2,900 Title II web-and-app complaints since the April 2024 final rule, against a pre-rule baseline that averaged roughly 90 per quarter. The post-rule run-rate has stabilised at 350–400 complaints per quarter. The composition of the queue has shifted as well: pre-rule, the modal complaint was a county property-records portal; post-rule, the modal complaint is a court e-filing system or a city online-payment portal. The shift reflects what the public is now expecting public entities to deliver online — and what the new rule has put inside the federal accessibility envelope.

Geographically, the queue concentrates. Five states — California, Texas, Florida, New York, and Pennsylvania — account for approximately 48% of the post-rule Title II web complaints, broadly proportional to population but with California somewhat over-indexing and the Mountain West somewhat under-indexing. Within those states, individual complainants account for a disproportionate share of the volume: roughly 14% of the queue comes from a single set of 40 repeat filers, mostly individuals with documented disabilities filing against multiple covered entities serving their region.

The repeat-filer dynamic is structurally different from Title III

In private-sector Title III litigation, the "serial-plaintiff" pattern has long been part of the enforcement landscape — high-volume filers pursuing damages claims under state laws that allow them. Title II under Subpart H is administrative, not private: the complaint goes to the DOJ, the DOJ decides whether to investigate, and the resolution is a voluntary compliance agreement or, in the rare contested case, federal litigation by the United States. A repeat filer in the Title II queue is therefore expanding administrative capacity to flag entities, not extracting damages. The dynamic is qualitatively different from the Title III plaintiff economy.

That said, the cumulative effect of repeat-filer volume — about one complaint in every seven across the queue — is meaningful for which entities the DOJ chooses to investigate. The Department's intake is reactive: a high-volume queue against a single entity is part of what triggers a first cycle of investigation.

The first twelve named actions

The twelve named Subpart H actions issued through April 2026 cluster in a recognisable pattern. Nine are large city or county governments that missed the April 2026 deadline; two are state-agency portals (a tax-collection agency and an unemployment-insurance portal); one is a transit authority. Eight resolved through a pre-enforcement letter-of-findings and a voluntary compliance agreement (VCA), with a typical remediation window of 12–18 months and a structured progress-report cadence to the Department. Four are still in active negotiation as of April 2026.

The VCAs themselves follow a consistent template. The covered entity commits to a remediation plan against the named non-conforming surfaces, an internal accessibility-training requirement, the appointment of a designated accessibility coordinator, an external audit at the 12-month mark, and a written report to the Department at 6, 12, and 18 months. The Department reserves the right to escalate to formal enforcement if the milestones are missed. None of the eight settled VCAs in year-2 has yet triggered an escalation clause — the cycle is still inside its first 18 months.

Large city governments

3 named actions · VCA range $0 monetary, multi-year remediation plan

03 actions

County governments

4 named actions · Concentrated in property-tax + court e-filing portals

04 actions

Special districts

3 named actions · 1 transit authority + 2 school boards

03 actions

State agencies (non-primary)

2 named actions · Tax-collection + unemployment-insurance portals

02 actions

What is conspicuously absent from the twelve-action list is the state-primary government portal cohort. None of the 50 state primaries has been the subject of a named Subpart H action — consistent with that cohort's 58% pass rate. Where the DOJ is moving, it is moving against entities at the bottom of the sector pass-rate distribution and against entities where a high-volume complaint queue has built up over twelve months or more.

The seven exceptions in practice

Subpart H's 35.201 enumerates seven categories of content that fall outside the rule's general conformance requirement. They are: preexisting conventional electronic documents (primarily PDFs uploaded before April 24, 2024 that are not currently being used); preexisting web content that is archived; preexisting social-media posts; preexisting linked third-party content (where the third party has not posted at the entity's direction); content provided through a third party that the entity has not chosen to use; password-protected individualised content; and content created by or for an individual entity member for that member's personal use. Each of the seven is doing some work in the year-2 enforcement record — but they are not doing equal work.

The "preexisting conventional electronic documents" carve-out is the one most aggressively invoked. In approximately 40% of letter responses we reviewed, the responding entity asserted the PDF carve-out as a basis for excluding some portion of its document inventory from the year-2 conformance scope. The DOJ's position, as reflected in the early VCAs, is that the carve-out applies narrowly: only to PDFs that were uploaded before April 24, 2024 and are not currently being used by the entity. A pre-2024 PDF that is still linked from the entity's homepage or is regularly accessed by the public is, in the Department's view, not "preexisting" within the meaning of the carve-out.

The third-party-content carve-out is the second-most-invoked. Embedded vendor maps, payment-processor iframes, and scheduling widgets are the typical fact pattern. The Department has signalled — through the language of the early VCAs, not yet through a formal interpretive memo — that the carve-out reaches third-party content the entity has not chosen to use, but does not reach a vendor widget the entity has affirmatively integrated into its service-delivery flow. That distinction will be where the contested cases in year-3 sit.

What "preexisting" actually means is the next contested question

The rule defines preexisting by reference to April 24, 2024 — the publication date of the final rule. But "preexisting" intersects with "currently used" in ways the regulation does not fully resolve. A council-meeting video posted in 2019 that is no longer linked from the homepage and has not been accessed in three years is plainly within the carve-out. A 2019 council-meeting video that the public still reaches through the meeting-archive search is plainly inside the scope. Between those two cases is a substantial grey zone the Department has not yet addressed through a formal interpretive document. The year-3 enforcement record is likely to develop the line.

The mobile-app sub-question

Native mobile applications are inside the rule's scope on the same timeline as web content. The DOJ's drafting treats web and mobile as parallel obligations, with conformance to WCAG 2.1 AA the reference standard for both. The practical implementation of that obligation is meaningfully harder for mobile than for web, for two reasons: WCAG 2.1 was drafted with web as the primary target, and many of the criteria translate to native mobile only by reference rather than directly; and mobile apps ship monthly or more frequently, raising the question of which version is "the app" for conformance purposes.

The year-2 complaint data reflects the difficulty. Approximately 11% of the post-rule queue — roughly 320 of the 2,900 complaints — concern native mobile apps. The disproportion is striking: property-tax apps, court e-filing apps, and transit-ticketing apps account for more than two-thirds of the mobile-app complaint volume. These are the three categories where a public-service interaction has migrated most fully from web to native mobile, and where the year-2 scan-based audit has limited reach (automated scanners are far less mature on native iOS and Android than on the web).

Only one of the twelve named year-2 enforcement actions targets a mobile app specifically — a transit-authority ticketing app whose VCA includes both a remediation plan against the named non-conforming surfaces and an explicit "release-cycle conformance" clause requiring conformance testing as part of the entity's app-submission process. That clause, if generalised across future VCAs, is the most likely answer to the "which version" question: the rule will be operationalised at the build level, with conformance testing required before each store submission.

Three things still unresolved at the end of year-2

Three structural questions are still unresolved at the end of year-2, and the year-3 enforcement record is likely to develop each.

The video-archive retroactivity question. How far back the "preexisting" line actually reaches for live-streamed council meetings posted before April 2024 is the single most-asked question across the year-2 letter-response record. Council-meeting video is high-volume, frequently navigated, often the only public record of a deliberative process, and overwhelmingly non-captioned in the pre-2024 archive. The "preexisting" carve-out plainly reaches some of this archive; just as plainly does not reach all of it. The Department has not yet issued an interpretive document drawing the line.

The third-party-content question. Where the entity's liability begins and the vendor's ends for embedded third-party content is the second open question. The early VCAs gesture at the distinction between content the entity has chosen to use (inside scope) and content the entity has not chosen to use (outside scope), but the practical line is harder. A vendor payment-processor iframe the entity integrates as part of its tax-collection flow is plainly inside scope. A vendor map widget the entity has dropped into its parks-department page is closer to the line. The carve-out's language will need either an interpretive memo or a contested case to harden.

The mobile-app submission-timeline question. Which version of an app is "the app" for conformance purposes when both stores carry monthly releases is the third open question. The single VCA addressing the question to date adopts a build-level test — conformance at submission, ongoing testing as part of release-cycle quality assurance. That answer is workable, but is not yet generalised. The DOJ has not yet announced whether the build-level test will be its general position or whether a different cadence (annual third-party audit, for example) will apply to apps with lower release frequency.

U.S. Department of Justice, Civil Rights Division, Subpart H VCA standard language

"The Public Entity shall ensure that all web content and mobile applications it provides or makes available conform to the Web Content Accessibility Guidelines (WCAG) Version 2.1, Level A and AA, with the limited exceptions set forth in 28 CFR 35.201. The Public Entity shall designate an accessibility coordinator, conduct an annual third-party audit, and submit a written compliance report to the Department at six, twelve, and eighteen months from the effective date of this Agreement."

— DOJ Civil Rights Division, standard Subpart H VCA template, in force April 2026

What year-3 will look like

The year-2 picture is, in one sentence, a regulator pacing itself. The DOJ moved against the entities most plainly outside the rule's conformance envelope and most plainly outside the carve-outs, using the lowest-friction tool — the pre-enforcement letter-of-findings and the voluntary compliance agreement — to convert non-conformance into a structured remediation plan. The Department has not yet escalated any of the eight settled VCAs. The twelve named actions are a tiny fraction of the 66% of large entities that did not pass the year-2 scan. The implication is that the first cycle of Subpart H enforcement is triage, not prosecution.

Year-3 is the year that triage logic will be tested. By April 2027, the small-entity cohort joins the conformance envelope at a starting pass rate that is twelve points below the large entities. The five-state geographic concentration of the complaint queue is unlikely to dissipate; if anything, it is likely to sharpen as repeat-filer cohorts expand into the small-entity universe. The first interpretive memo on the video-archive carve-out, on third-party content, or on mobile-app submission cadence is overdue and likely to issue in the next four quarters. And the first contested escalation under the eight settled VCAs — the first case where a covered entity misses an 18-month milestone and the Department invokes the escalation clause — is the moment year-3's qualitative posture starts to look different from year-2's.

The structural point is that 28 CFR Part 35 Subpart H is the first federal regulation in two decades to put state and local government web and mobile content inside a binding accessibility envelope. The year-2 numbers — 34% pass, 2,900 complaints, 12 actions — describe a regulator and a regulated community both in the first cycle of learning the new system. The numbers will move in year-3. The seven exceptions will harden. The mobile-app sub-question will be answered. And the carve-out question that is doing the most quiet work — what "preexisting" actually means — will be the one that defines whether the rule's reach is, in practice, the rule's text.

Methodology and data: Scan-based audit covers 2,217 large-entity and 1,400 small-entity state and local government domains, scanned Q1 2026 against WCAG 2.1 AA (Level A and AA, automatable subset). The "pass" rate reflects no Level A or AA blocking violation across the homepage and two primary linked task flows. Complaint-queue data is drawn from the DOJ Civil Rights Division quarterly intake bulletins, Q3 2024 through Q1 2026. Enforcement-action data is drawn from the Department's published Subpart H docket through April 2026. The 21% / 14% manual-inclusive projections are extrapolated from a 200-domain manual-audit subsample.

Legal context: 28 CFR Part 35 Subpart H, "Accessibility of Web Content and Mobile Applications Provided by State and Local Government Entities," final rule published 89 FR 31320 (April 24, 2024). The rule cross-references WCAG 2.1 (W3C, June 2018) at Level A and AA. The two compliance dates are April 24, 2026 (entities with a population of 50,000 or more, plus all state-government entities) and April 26, 2027 (entities with a population under 50,000). Subpart H amends the pre-existing Title II implementing regulation at 28 CFR Part 35; the underlying statutory authority is Title II of the Americans with Disabilities Act (42 U.S.C. § 12132).

What this article is not: Not legal advice. The scan-based pass rates are point-in-time scan results and are not a substitute for a full WCAG conformance audit. The DOJ's interpretive position on the seven carve-outs is in development; the Department has not issued a formal interpretive memorandum as of April 2026, and the descriptions above reflect language drawn from early voluntary compliance agreements rather than from a regulatory pronouncement. State and local government entities reading this dossier should treat it as a year-2 status report, not as a compliance plan.

EAA Article 13: fine ranges by Member State, mid-2026

Disability World — Fri, 22 May 2026 00:00:00 GMT

Editorial · EU regulatory enforcement · Article 13

EAA Article 13: fine ranges by Member State, mid-2026 — a two-orders-of-magnitude spread inside a Single Market

Article 13 of Directive (EU) 2019/882 is one sentence long in substance: penalties for non-compliance must be "effective, proportionate and dissuasive." The Directive's drafters then left the actual numbers to 27 national legislatures. Twelve months into enforcement, the result is visible. The lowest top-of-band per-violation ceiling sits at €5,000 (Estonia, Slovenia). The highest fixed ceiling sits at €1,000,000 in Spain under Ley 11/2023. Italy ties its top tier to a percentage — up to 5% of annual turnover — which, applied to the largest covered operators, eclipses every fixed ceiling on the continent. This is the first comprehensive Member-State-by-Member-State survey of Article 13 caps as they stand at mid-2026.

Findings · Case file EAA-A13 07 entries · derived from 27 national transposition acts + first-year enforcement bulletins

What the 27-state Article 13 picture reveals

01 200×

The top-of-band per-violation ceiling differs by a factor of two hundred between the lowest and highest fixed-cap Member States

Estonia and Slovenia cap a single violation at €5,000–€10,000. Spain caps a single very-serious infringement at €1,000,000. That ratio — 200× — is the headline measure of how widely Member States have interpreted the "effective, proportionate and dissuasive" instruction in Article 13.
02 5%

Italy is the only Member State to scale its top tier to annual turnover

D.lgs. 82/2022, building on the Stanca Law framework, applies a turnover-percentage tier up to 5% of annual turnover for the most serious infringements. For a covered operator with €1 billion in EU turnover, this implies a theoretical maximum of €50 million per very-serious violation — eclipsing every fixed-ceiling regime.
03 3

Three Member States have issued first-year sanctioning resolutions under their Article 13 schedules

Germany (BAFA, under the BFSG), Spain (Ministerio de Asuntos Económicos, under Ley 11/2023), and France (DGCCRF and ARCOM, under the 2023 RGAA-implementing decrees) issued the first publicly-reported penalties during the 2025–26 enforcement window. No other Member State has yet published an Article 13 sanction.
04 €50K

The modal first-year penalty has landed an order of magnitude below the statutory ceiling

Actually-issued first-year fines in Germany, Spain, and France have clustered in the €15,000–€100,000 band — well below the €1M Spanish ceiling and the €100K German ceiling. The gap between statutory ceiling and modal penalty is itself a data point: surveillance authorities are pacing themselves through a first cycle of triage.
05 7

Seven Member States operate a per-day continuing-violation penalty in addition to a per-violation cap

Germany, France, Spain, Italy, Netherlands, Portugal, and Belgium each layer a daily penalty (typically €500–€10,000 per day) on top of the headline per-violation ceiling for as long as the violation persists after a formal notice. This is the practical multiplier that turns a five-figure headline cap into a six- or seven-figure exposure.
06 2030

The Commission's first scheduled review of the Article 13 spread is the 2030 consolidated implementation review

Article 33 of the Directive requires the Commission to report on application by 28 June 2030 and to consider, among other items, the penalty regime. The 2026 implementation note has already flagged the Article 13 spread as a candidate for the substantive review — but no formal proposal to harmonise the ceilings has yet been tabled.
07 EUR

All 27 Member States denominate their Article 13 ceilings in euro — including those outside the eurozone

Sweden, Denmark, Poland, Czechia, Hungary, Romania, and Bulgaria each publish their Article 13 ceilings in euro alongside the local-currency figure, reflecting a Commission-encouraged convention. The local-currency figure is the legally binding amount; the euro figure is the reference. This is a soft form of single-market convergence the Directive itself does not require.

SourceTwenty-seven Member-State transposition acts as in force at mid-2026; European Commission DG JUST implementation note (March 2026); national market-surveillance authority bulletins; first-year sanctioning resolutions published in Germany, Spain, and France.

In this report

01What Article 13 actually says
02How the 27-state survey was assembled
03The 27 Member States, ranked by penalty cap
04The floor: €5,000 in Estonia and Slovenia
05The mid-band: France, Germany, Netherlands
06The ceiling: Spain's €1M and Italy's 5%
07The per-day continuing-violation multiplier
08Is the range converging or diverging?
09What this means for compliance teams
10Sources

What Article 13 actually says

Article 13 of Directive (EU) 2019/882 — the European Accessibility Act — runs to three short paragraphs. The operative sentence is the one repeated across every horizontal Single Market instrument adopted since the late 1990s: "Member States shall lay down the rules on penalties applicable to infringements of the national provisions adopted pursuant to this Directive and shall take all measures necessary to ensure that they are implemented. The penalties provided for shall be effective, proportionate and dissuasive." The Article also requires Member States to notify the Commission of those rules and any subsequent amendment.

The phrase "effective, proportionate and dissuasive" is not bespoke to the EAA. It appears in essentially every consumer-protection, data-protection, and product-safety directive the Union has adopted in the last quarter-century. The Court of Justice has interpreted the phrase to require Member States to set penalties that, at a minimum, deprive the infringer of any economic advantage gained by the infringement and impose a deterrent margin above that. The Court has consistently refused to read the phrase as imposing a Union-wide floor or ceiling — that is the legislator's job, and in the EAA the legislator declined to set one.

What the Directive does require is that the penalty regime "take into account the extent of non-compliance, including its seriousness, and the number of units of non-complying products or services concerned, as well as the number of persons affected." That is a proportionality instruction, not a number. The proportionality instruction is what most Member States have used to graduate their penalty schedules into tiers — minor, serious, very serious — with separate ceilings for each tier and explicit factors (recidivism, intent, duration) that move a given infringement up or down the scale.

How the 27-state survey was assembled

This survey is built from the text of each Member State's EAA transposition act as in force at mid-2026, supplemented by enforcement bulletins from the designated market-surveillance authority where one has been published. The transposition acts vary in form: in some Member States the EAA was transposed by amending a pre-existing horizontal accessibility statute (Germany's BFSG, France's loi 2005-102, Italy's Stanca Law); in others by a dedicated transposition act (Spain's Ley 11/2023, Estonia's Toodete ja teenuste ligipääsetavuse seadus, Slovenia's Zakon o dostopnosti); and in a third group by a chapter inserted into a general consumer-protection code.

For each Member State we recorded four data points: the top-of-band ceiling for a single very-serious infringement; the ceiling for a serious infringement; the existence and rate of any per-day continuing-violation penalty; and the designated market-surveillance authority. The figures below are headline maxima. The actually-imposed penalty in any given case will be a fraction of the headline maximum, scaled by the factors set out in the national act — typically the operator's turnover, the duration of the infringement, the number of affected users, and any aggravating or mitigating circumstances. The headline maximum is what determines the upper limit of exposure; the modal penalty is determined by the surveillance authority's practice.

One technical caveat applies throughout. Several Member States set their headline ceiling in local currency; for non-eurozone Member States we converted at the European Central Bank reference rate for 1 May 2026 and rounded to the nearest €1,000 to allow comparability. The legally binding figure remains the local-currency one.

The 27 Member States, ranked by per-violation penalty ceiling

The table below ranks each of the 27 EU Member States by the top-of-band per-violation ceiling for the most serious category of infringement, as set out in the transposition act in force at mid-2026. Italy's turnover-percentage tier is shown separately — the implied maximum depends entirely on the size of the covered operator, and at the level of a major multinational e-commerce platform the implied maximum would be the highest in the Union. For the rest of the cohort the ranking is straightforward.

{/* Hand-built SVG horizontal bar chart replaces a FLUX-generated image whose member-state labels and euro values rendered as gibberish (AI image models cannot draw legible text). All values match the ranked table below; Italy is excluded from the bar comparison because its ceiling is a percentage of turnover, not a fixed-euro figure — it is noted in the caption instead. Spain's €1M outlier is highlighted in red. */}

Top ten EU Member States by EAA Article 13 per-violation ceiling, mid-2026. Spain's €1,000,000 fixed cap (highlighted) is four times the next-highest fixed ceiling (Portugal, €250,000) and twenty times the cohort floor shown here (Sweden, €50,000). Italy is excluded from the bar comparison because its ceiling is set as up to 5% of annual turnover rather than a fixed-euro figure — applied to a covered operator with €1bn EU turnover, the implied maximum is €50,000,000.

EU Member States ranked by per-violation Article 13 penalty ceiling under the European Accessibility Act, mid-2026.
Rank	Member State	Top per-violation ceiling	Continuing daily penalty	Market-surveillance authority
01	Italy	up to 5% of annual turnover	up to €10,000/day	AgID
02	Spain	€1,000,000	up to €6,000/day	Ministerio de Asuntos Económicos
03	Portugal	€250,000	up to €2,000/day	INR / ANACOM
04	Belgium	€200,000	up to €1,500/day	SPF Économie
05	Ireland	€150,000	—	CCPC / NDA
06	Germany	€100,000	up to €5,000/day	BAFA / Länder authorities
07	Greece	€100,000	—	EETT / EEEP
08	Netherlands	€87,000	up to €1,000/day	Agentschap Telecom (RDI)
09	France	€75,000	up to €1,500/day	ARCOM / DGCCRF
10	Austria	€60,000	—	Sozialministeriumservice
11	Sweden	€50,000	—	MFD / PTS
12	Denmark	€50,000	—	Digitaliseringsstyrelsen
13	Finland	€50,000	—	Etelä-Suomen AVI
14	Czechia	€40,000	—	Ministerstvo průmyslu a obchodu
15	Poland	€40,000	—	UOKiK / PFRON
16	Slovakia	€40,000	—	Ministerstvo dopravy
17	Hungary	€35,000	—	Fogyasztóvédelmi Hatóság
18	Slovenia	€10,000–€40,000	—	Tržni inšpektorat
19	Estonia	€5,000–€32,000	—	Tarbijakaitseamet (TTJA)
20	Romania	€30,000	—	ANPC
21	Croatia	€30,000	—	Državni inspektorat
22	Bulgaria	€25,000	—	КЗП (Consumer Protection)
23	Lithuania	€25,000	—	VVTAT
24	Latvia	€20,000	—	PTAC
25	Luxembourg	€20,000	—	ILR
26	Cyprus	€15,000	—	Consumer Protection Service
27	Malta	€10,000	—	MCCAA

Where two figures are shown for the same Member State (Estonia, Slovenia), the lower figure is the maximum for serious infringements and the upper figure the maximum for very serious infringements; the upper figure is the relevant comparator for the ranking. All figures are headline maxima per single violation. The continuing-daily penalty column shows the per-day surcharge that applies, where the national act provides for one, for each day the violation persists after a formal notice. Authorities listed are the lead market-surveillance authority for digital services; in several Member States (Germany, Spain, Belgium, Italy) sector-specific competences are split across additional sectoral regulators (banking supervisors, telecom regulators, audio-visual regulators).

The floor: Estonia, Slovenia, Malta, Cyprus

At the bottom of the table sit four Member States with headline ceilings in the €5,000–€15,000 band: Estonia, Slovenia, Malta, and Cyprus. Each has explained the choice in similar terms. In Estonia, the Toodete ja teenuste ligipääsetavuse seadus calibrated its EAA penalty schedule to the rest of the country's consumer-protection penalty regime, in which a five-figure ceiling is the norm for individual administrative infringements. The Tarbijakaitseamet (Consumer Protection and Technical Regulatory Authority) — the designated lead — has indicated that the ceiling is, in its view, sufficient for the size of the Estonian market and the typical turnover of operators it expects to sanction. Slovenia followed similar reasoning under its Zakon o dostopnosti proizvodov in storitev.

The structural objection to a five-figure ceiling is the one the Commission's 2026 implementation note flagged: where a non-Estonian operator with EU-wide turnover sells into the Estonian market through a single-domain storefront, the headline ceiling is at the absolute floor of what Article 13's "dissuasive" instruction can plausibly accommodate. The counter-argument from the smaller Member States is that the headline ceiling is not the full deterrent picture: continuing-violation penalties, removal-from-market powers, and reputational-publication regimes all add to the operator's exposure beyond the fixed cap. The substantive review will be the place where this argument is tested.

Why the floor matters more than the ceiling

For a multinational e-commerce platform deciding how to allocate accessibility-remediation budget across the Single Market, the floor matters more than the ceiling. The decision is not "where could we be fined €1M?" — it is "where is the marginal cost of non-compliance lowest, and does that produce a perverse incentive to deprioritise those markets?" The Commission's 2026 note records exactly this concern: the spread is wide enough that the Internal Market's accessibility floor is at risk of being defined, in practice, by the slowest-moving and lowest-cap jurisdiction.

The counterweight is the continuing-violation mechanism. A €5,000 headline cap that triggers a daily penalty for every additional day of non-compliance after a formal notice converts, within months, into a six-figure exposure. The four lowest-cap Member States do not all carry that mechanism, however — and that is where the deterrence gap is real.

The mid-band: France, Germany, Netherlands, Belgium

The mid-band of the ranking — €75,000 in France, €87,000 in the Netherlands, €100,000 in Germany, €200,000 in Belgium — represents the cohort of Member States with mature pre-EAA digital-accessibility enforcement frameworks. Each calibrated its EAA penalty schedule against the ceiling of its existing horizontal accessibility regime, which had been operational for years before the EAA was adopted: the RGAA framework in France, the BFSG's earlier iterations and the BITV regime in Germany, the Implementatiewet that predated the 2022 EAA-specific amendments in the Netherlands. The mid-band is also where the first-year enforcement actions have clustered.

What is visible in the mid-band is a deliberate trade-off between two regulatory cultures. The Member States that opted for fixed five-to-six-figure ceilings tend to be those with a long track record of administrative-penalty enforcement, where the surveillance authority issues a high volume of moderate-sized fines rather than a small number of headline-grabbing ones. The Member States that opted for higher ceilings (Spain, Ireland, Portugal) tend to be those that consciously imported the data-protection regulator's logic: a smaller number of large fines, often after extensive investigation, with the deterrent effect amplified by publication.

BAFA's first publicly-reported BFSG penalty in Q1 2026 — issued against a mid-sized fashion e-commerce operator, in the upper-five-figure range — is paradigmatic of the mid-band approach. The penalty was below the €100,000 ceiling, well above what a small operator would treat as a cost of doing business, and accompanied by a remediation order with a continuing-penalty clause. The pattern is consistent with how the German market-surveillance system has handled product-safety and consumer-protection enforcement for two decades. The French DGCCRF's first formal-notice tranche in early 2026 followed a similar shape.

SELECTED MEMBER STATES · PER-VIOLATION CEILING (€000s)

Spain

€1,000,000

Portugal

€250,000

Belgium

€200,000

Ireland

€150,000

Germany

€100,000

Netherlands

€87,000

France

€75,000

Slovenia

€40,000

Estonia

€32,000

Malta

€10,000

The ceiling: Spain's €1M and Italy's 5% of turnover

Two Member States sit alone at the top of the table. Spain's Ley 11/2023 sets a fixed €1,000,000 cap for very-serious infringements — the highest fixed ceiling in the Union and an order of magnitude above the mid-band cohort. Italy's D.lgs. 82/2022, building on the Stanca Law framework, sets a turnover-percentage tier of up to 5% of annual turnover for the most serious category of infringement, with no fixed-euro absolute cap. Applied to a covered operator with, say, €1 billion in EU turnover, the Italian regime implies a theoretical maximum of €50,000,000 per very-serious violation. Applied to a small operator, it implies a maximum well below the Spanish cap. The Italian regime scales with size; the Spanish one does not.

The choice of design is not accidental. Spain calibrated its EAA ceiling against the upper limit of the existing administrative-penalty regime under the LGCA (general telecommunications law) and the LSSI (information-society services law), both of which already operated million-euro ceilings for consumer-protection breaches. The Spanish regulatory tradition, particularly in the digital-services space, has consistently favoured high fixed ceilings — partly because of the deterrent visibility, partly because Spanish administrative law makes graduated administrative tiering more transparent than turnover-percentage tiers do. Italy went the other way, importing the turnover-percentage logic from the GDPR-cousin AgCom telecommunications-penalty schedule and the AGCM competition-penalty schedule. The 5% rate is identical to the GDPR's 4% upper tier in feel — and, in the case of the largest operators, materially exceeds it.

The first sanctioning resolutions under Ley 11/2023 — published in late 2025 against operators of self-service kiosks at regional transport hubs — landed at €50,000–€150,000, well below the ceiling. The Italian regime has not yet produced a published turnover-percentage fine; AgID's first-year enforcement activity has been concentrated on formal notice and remediation orders rather than on sanctioning resolutions. The first time an Italian regulator issues a turnover-percentage fine against a major covered operator, it will set a precedent the Spanish €1M ceiling cannot match in absolute terms.

"Effective, proportionate, dissuasive — three words. Twenty-seven legislatures. Two orders of magnitude between the floor and the ceiling. The question for 2030 is whether Article 13 is a Single Market provision or a Single Market problem."

The per-day continuing-violation multiplier

Headline ceilings are only half of the Article 13 picture. Seven Member States — Germany, France, Spain, Italy, Netherlands, Portugal, and Belgium — operate a per-day continuing-violation penalty in addition to the per-violation cap, typically at €500–€10,000 per day for as long as the violation persists after the operator has been formally notified. This is the practical mechanism that turns a five- or six-figure headline cap into a six- or seven-figure exposure in a contested case.

The rates are not uniform. Germany's BFSG provides for a per-day surcharge of up to €5,000 per day under the supervisory-order mechanism; Italy's regime, applied through AgID, can reach €10,000 per day in the most serious category. France's per-day rate under the DGCCRF schedule is more modest — up to €1,500 per day — but applies more reliably across enforcement actions. Spain's regime under Ley 11/2023 sets a per-day surcharge of up to €6,000 per day, scaled to the size of the operator.

For compliance teams, the continuing-violation mechanism is the part of Article 13 that most directly affects remediation planning. A formal notice with a 30-day cure period — common across the seven Member States with per-day mechanisms — translates, at the highest applicable rate (Italy, €10,000/day), into €300,000 of exposure on top of the headline per-violation cap. At French rates, the same 30-day window is €45,000. Member States without a per-day mechanism — most of the Central and Eastern Europe cohort, plus the Nordics — rely on the headline cap alone for their deterrent.

Is the range converging or diverging?

The honest answer at mid-2026 is that the range is neither obviously converging nor obviously diverging. No Member State has revised its Article 13 ceiling upward in the first year of enforcement. No Member State has revised it downward. The bottom-end cohort (Estonia, Slovenia, Malta, Cyprus) has not signalled an intention to raise its ceilings. The top-end cohort (Spain, Italy) has not signalled an intention to lower them. The mid-band cohort (France, Germany, Netherlands, Belgium) is operating its existing ceilings as designed and producing first-year enforcement at modal levels well below those ceilings.

What is happening is a soft form of operational convergence that does not require statutory change. Surveillance authorities across the Union are sharing methodology — the BAFA, DGCCRF, AEPD, and AgID have published broadly compatible enforcement triage criteria during the first year — and the modal penalty in actually-issued cases is clustering in the €15,000–€100,000 band even where the headline ceiling is much higher. That is the part of the convergence story the Article 13 spread does not capture: in practice, the first-year fines are not exploiting the spread.

The Commission's 2026 implementation note describes the spread as "an area for monitoring rather than for immediate intervention." The 2030 substantive review is the first scheduled moment at which legislative harmonisation could be tabled. Between now and then, the Commission's tools are softer: shared methodology, cross-border cooperation under Regulation (EU) 2019/1020, and (eventually) the first cross-border enforcement action under the joint-surveillance framework, which will materially test how a single covered operator is exposed under multiple national Article 13 schedules at once.

Cross-link · the broader first-year picture

This piece is the deep-dive on Article 13 specifically. For the broader first-year status of the European Accessibility Act — transposition completeness across all 27 Member States, first-named enforcement actions, scan-pass rates by sector, and the open standards question (EN 301 549 V3 versus V4, WCAG 2.1 versus 2.2) — see our companion report, EAA first year: enforcement, penalties, and the compliance-rate trajectory across the EU 27.

European Commission, DG JUST, EAA implementation note

"The range of penalty levels currently in force across Member States reflects the Directive's deliberate choice to leave the specific calibration to national legislatures, within the 'effective, proportionate and dissuasive' constraint. The Commission will monitor the spread and report on its consistency with the Single Market in the 2030 application review."

— DG JUST Unit D.3, EAA first-year implementation note, March 2026

What this means for compliance teams

For a covered operator running compliance across the Single Market, the first-year Article 13 picture has three practical implications.

First, the headline ceiling is not the right planning input. The modal first-year fine is clustering at €15,000–€100,000 across the Member States with active enforcement, and that band is more useful for budgeting than the €1M Spanish ceiling. The headline ceiling matters for the worst-case tail risk — a recidivist failure across a flagship checkout flow on a multinational platform — but most actually-issued fines will sit well below it.

Second, the per-day continuing-violation mechanism is the part of Article 13 that should drive remediation timelines. A 30-day cure period at Italian rates is €300,000 of additional exposure; at French rates it is €45,000. Remediation programmes should be calibrated to clear formal notices within the cure window, not to optimise against the headline cap.

Third, the range itself is a single-market planning consideration. Allocating remediation budget by ceiling alone would underweight low-cap markets with active surveillance authorities (the Baltic and Visegrád cohort, where per-day mechanisms are rare but operational enforcement is rising) and overweight high-cap markets with cautious first-year enforcement practice. The right input is a blended exposure measure that combines ceiling, per-day mechanism, surveillance-authority activity level, and reputational publication regime — not the headline cap alone.

The most likely 2026–27 development on the Article 13 front is the first cross-border enforcement action under the Regulation (EU) 2019/1020 framework — at which point a single covered operator will, for the first time, face Article 13 schedules from multiple Member States simultaneously. That case will tell us, more clearly than any of the first-year domestic actions have, how the spread actually behaves under stress.

Read more from Disability World on the EAA, on the broader first-year enforcement picture, and on national accessibility regulations.

EAA first year: enforcement, penalties, and the compliance-rate trajectory across the EU 27

Disability World — Fri, 22 May 2026 00:00:00 GMT

Editorial · EU regulatory enforcement

EAA first year: enforcement, penalties, and the compliance-rate trajectory across the EU 27

The European Accessibility Act — Directive (EU) 2019/882 — became enforceable across the Union on 28 June 2025, six years after adoption and three years after the Member-State transposition deadline. Twelve months in, the first wave of fines has landed, the Commission has named the laggards behind on transposition, and automated scan data has produced the first comparable compliance picture for EU-facing e-commerce. The headline: penalty ceilings now range from €5,000 in Estonia to roughly €1 million in Spain, transposition is formally complete in all 27/27 Member States but operationally uneven, and fewer than half of large EU e-commerce properties pass an automated WCAG 2.1 AA scan at the level the EAA implicitly requires. This is the first-year status report.

Findings · Case file EAA-Y1 06 entries · derived from Commission, national authorities, and scan data, mid-2026

What the first year of EAA enforcement shows

01 27/27

All 27 Member States have formally transposed Directive (EU) 2019/882 by mid-2026

Formal adoption is complete. Operational readiness — designated market-surveillance authority, published complaint mechanism, penalty schedule in force — lags formal adoption in seven Member States.
02 €5K–€1M

Top per-violation penalty ceilings span two orders of magnitude across the Single Market

€5,000 floors in Estonia and Slovenia, approx. €75,000–€100,000 ceilings in France, Germany, and the Netherlands, up to €1 million in Spain (Ley 11/2023), and turnover-percentage tiers up to 5% of annual turnover in Italy.
03 3

Three Member States produced the first publicly-reported EAA enforcement actions

Germany (BAFA), Spain (Ministerio de Asuntos Económicos), and France (ARCOM and DGCCRF) issued the first sanctioning resolutions and formal-notice tranches during the 2025–26 window — concentrated on e-commerce checkout flows and self-service kiosks.
04 < 50%

Fewer than half of major EU e-commerce properties pass an automated WCAG 2.1 AA scan at mid-2026

The same rolling sample sat at 30–40% before the 28 June 2025 deadline. National coverage now ranges from roughly 30% in late-transposing Member States to 70% in the consumer-banking and regulated-transport segments.
05 < 10 / €2M

The microenterprise carve-out exempts services-side undertakings under 10 staff or €2M turnover

Article 4(5) services-side exemption does not extend to products. Article 14's disproportionate-burden defence carries the burden of proof and a five-year documentation requirement — and has not yet succeeded at the level of a whole-platform exemption.
06 V3 → V4

EN 301 549 V3.2.1 is the referenced harmonised standard; V4 (with WCAG 2.2) is in late-stage drafting

V3.2.1 incorporates WCAG 2.1 Level AA. V4 — incorporating WCAG 2.2 — is expected to be referenced by the Commission within 18 months, with a transition period. French and German authorities are already treating WCAG 2.2 conformance as good-faith evidence.

SourceEuropean Commission DG JUST implementation note (March 2026); national market-surveillance authority bulletins (BAFA, AEPD, ARCOM, AgID, Tarbijakaitseamet); ETSI EN 301 549 drafting status; consolidated automated-scan dataset across approximately 4,000 EU-domain e-commerce properties, mid-2026.

In this report

01What came into force, and when
02Transposition status across the EU 27
03First named enforcement actions
04The microenterprise carve-out
05What the scan data shows
06The open standards question
07What 2026–27 will resolve
08Sources

What came into force, and when

The European Accessibility Act sets a harmonised minimum accessibility standard for a defined list of products and services placed on the EU market. Adopted on 17 April 2019 and published in the Official Journal as Directive (EU) 2019/882, it required Member States to transpose its provisions into national law by 28 June 2022, and required covered economic operators to comply with the substantive requirements from 28 June 2025. The five-year run-up was intentional: the Directive's drafters knew it touched product lines (e-readers, smartphones, ATMs, self-service terminals) with multi-year hardware refresh cycles, and service categories (banking, e-commerce, e-ticketing, audio-visual media, electronic communications) where existing accessibility regimes varied widely.

The legal architecture is a directive, not a regulation: it sets the outcome each Member State must achieve and leaves the implementing mechanism — designated authorities, penalty schedules, complaint pathways, exemption procedures — to national legislatures. This is the source of most of the unevenness now visible at one year. The substantive requirements are common; the enforcement apparatus is not.

The covered scope is broad. On the products side: computers and operating systems, smartphones, smart-TV equipment, self-service terminals (ATMs, ticketing machines, check-in kiosks), e-readers, and consumer banking terminals. On the services side: consumer banking services, electronic communications, e-commerce, e-books and dedicated software, audio-visual media access components, transport e-ticketing and information services, and emergency communications via the European single emergency number 112. The Annex I functional requirements map closely — though not identically — to [WCAG 2.1 Level AA](/toolkit/standards/wcag/) for digital services, with the harmonised technical specification provided by EN 301 549 V3.x, which the European Commission referenced as the presumptive standard during 2024–25.

Transposition status: formally 27/27, operationally uneven

{/* Hand-built SVG horizontal-bar chart replaces a FLUX-generated image whose axis labels rendered as gibberish (AI image models cannot draw legible text). Values match the transposition table below; a log scale is used because the ceilings span two orders of magnitude (€32K to €1M). Italy is shown separately because its ceiling is set in turnover percentage, not absolute euros. */}

Top per-violation penalty ceilings under the European Accessibility Act span two orders of magnitude across the Single Market — from a €32,000 ceiling in Estonia and €40,000 in Slovenia, through approximately €75,000–€100,000 in France, the Netherlands, and Germany, up to €1 million in Spain. Italy's ceiling is set as a percentage of annual turnover (up to 5%) and is not directly comparable on a euro scale.

By the 28 June 2022 deadline, only a minority of Member States had transposing legislation in force. The Commission opened infringement proceedings against the laggard cohort during 2023 and issued reasoned opinions during the second half of 2024 against the Member States still missing the deadline. By mid-2025, the cohort had shrunk; by mid-2026, all 27 Member States have a transposition act on the books. The picture below is the formal status — what is enforceable on paper.

Selected EU Member-State transposition acts and penalty ceilings under the European Accessibility Act, mid-2026.
Member State	Transposition act	Top per-violation penalty	Market-surveillance authority
Germany	Barrierefreiheitsstärkungsgesetz (BFSG, 2021)	€100,000	BAFA / Länder authorities
France	Loi n° 2005-102, RGAA implementing decrees (2023 update)	approx. €75,000	ARCOM / DGCCRF
Spain	Ley 11/2023 (de trasposición)	up to €1,000,000	Ministerio de Asuntos Económicos
Italy	D.lgs. n. 82/2022 (Stanca Law extension)	up to 5% of turnover	AgID
Netherlands	Implementatiewet toegankelijkheidsvoorschriften (2022)	approx. €87,000	Agentschap Telecom (RDI)
Estonia	Toodete ja teenuste ligipääsetavuse seadus (2022)	€5,000–€32,000	Tarbijakaitseamet (TTJA)
Slovenia	Zakon o dostopnosti proizvodov in storitev (2022)	€10,000–€40,000	Tržni inšpektorat

The transposition gap: formal versus operational readiness

The Estonia–Spain ceiling spread is two orders of magnitude. That is not a drafting accident: the Directive's Article 30 requires penalties to be "effective, proportionate and dissuasive," and leaves the absolute level to national legislatures. In smaller Member States, a five-figure ceiling is consistent with the rest of the consumer-protection penalty schedule; in Spain and Italy, the ceiling is consistent with general data-protection or competition-law ceilings, where the deterrent calculus is set against the turnover of the largest covered firms.

France and Germany sit between — high enough to matter to a national retailer, low enough that a multinational e-commerce platform would treat it as a cost of business if it appeared in isolation. The Commission's own 2026 implementation report has signalled that the spread will be reviewed in the next consolidated review of the Directive, scheduled for 2030.

The first named enforcement actions

The penalty regimes mattered most in jurisdictions where the surveillance authority had a budget, a designated team, and a pre-existing accessibility enforcement track record. Three Member States produced the first publicly-reported fines during the 2025–26 enforcement window.

Germany — BAFA opens proceedings under the BFSG

The Federal Office of Economics and Export Control (BAFA), acting as the federal coordinating market-surveillance authority for the BFSG, opened a tranche of formal proceedings during the autumn of 2025 against e-commerce operators whose checkout flows failed the Annex I functional requirements on a programmatic check. The first publicly-reported penalty under the BFSG was issued in Q1 2026 against a mid-sized fashion e-commerce operator and sat in the upper-five-figure range. BAFA's own communication noted that the Bundesländer authorities — which retain residual enforcement competence in several covered service categories — were running parallel investigations.

BAFA enforcement bulletin, Q1 2026

"Effective, proportionate, dissuasive — the Directive's three words for penalties. After one year, the proportionality and effectiveness are visible. The dissuasion test is what 2027 will answer."

— European Commission, Directorate-General for Justice and Consumers, EAA implementation note, March 2026

Spain — Ley 11/2023 produces the first published resolutions

The Spanish transposition act, Ley 11/2023, gave the Ministerio de Asuntos Económicos y Transformación Digital the lead surveillance role for digital services, with sector-specific competences retained by the Banco de España (banking interfaces) and the CNMC (electronic communications). The first sanctioning resolutions under Ley 11/2023 were published in late 2025 against operators of self-service kiosks at regional transport hubs. The penalty levels in the published resolutions were well below the €1 million ceiling — closer to the €50,000–€150,000 range typical of Spanish first-instance accessibility sanctions — but the public-resolution practice is itself novel: the published-decision regime gives the Spanish enforcement pipeline a deterrent visibility that, e.g., the German Länder-level proceedings do not have.

France — ARCOM and DGCCRF run on RGAA experience

ARCOM and the DGCCRF have shared competence under the French transposition, with ARCOM taking on audio-visual media services and electronic communications, and DGCCRF taking on e-commerce and consumer banking. The first DGCCRF formal-notice tranche under the EAA-implementing decrees landed in early 2026, with penalty proposals concentrated in the €15,000–€60,000 band. France's pre-existing RGAA framework (Référentiel général d'amélioration de l'accessibilité) had given French enforcement authorities a decade of operational experience with which to triage EAA referrals — visible in the speed of the first-year action.

The microenterprise carve-out and the disproportionate-burden defence

Two structural exemptions in the Directive shape the enforcement landscape more than any of the penalty schedules. The first is the microenterprise exemption for service providers (Article 4(5)): undertakings with fewer than 10 staff and an annual turnover or balance-sheet total not exceeding €2 million are exempt from the services-side requirements. The carve-out does not apply to the products-side of the Directive, where a small-volume manufacturer faces the same conformity-assessment requirements as a multinational. The asymmetry is intentional — products bear the conformity-assessment burden once per model, services bear it per platform — but it has been challenged by small-business federations across multiple Member States during the transposition rounds, and the Commission's 2030 review will revisit it.

Article 4(5) and Article 14 — the two structural exemptions

The microenterprise exemption (Article 4(5)) applies only to the services side of the Directive: a service provider with fewer than 10 staff and turnover or balance-sheet total under €2 million is exempt. A small-volume hardware manufacturer is not — it faces the same conformity-assessment regime as a multinational. The asymmetry is a deliberate trade-off between cost of compliance and conformity overhead.

The disproportionate-burden defence (Article 14) may be invoked by any covered operator. The burden of proof is on the operator and the supporting documentation must be retained for inspection for five years. In the first year of enforcement, the defence has succeeded for specific features (legacy product catalogues being grandfathered out until a planned platform migration) but not for headline service categories.

The second is the disproportionate-burden defence (Article 14): an economic operator may, under defined conditions, claim that a specific accessibility requirement would impose a disproportionate burden, with the burden of proof on the operator and a documentation requirement that the operator must keep available for five years for inspection. In the first year of enforcement, several Member States — Germany, Netherlands, France — have published guidance on how the disproportionate-burden assessment should be documented, including the cost–benefit calculation methodology and the threshold above which the defence is plausibly arguable. The early enforcement record suggests that the defence is rarely successful at the level of a whole-platform exemption: it has succeeded for specific features (e.g., legacy product catalogues being grandfathered out of the requirements until a planned platform migration) but not for headline service categories. The DGCCRF in particular has indicated that a disproportionate-burden claim covering a checkout flow on a major e-commerce platform would not be accepted absent unusual circumstances.

What the scan data shows

The hardest piece of the first-year picture has been measuring compliance. The Directive does not require any centralised reporting from covered firms; it requires Member States to provide market-surveillance authorities with the powers to inspect, request documentation, and apply penalties, and to publish summary enforcement data. The result is that the most comparable EU-wide compliance data comes not from regulators but from automated accessibility scans of public-facing URLs, run by a handful of academic groups and accessibility-tool vendors who have been publishing methodologically-similar samples since 2018.

The picture across those samples is consistent. In the months immediately before the 28 June 2025 deadline, programmatic scan-pass rates for major EU-domain e-commerce home pages and primary checkout flows hovered around 30–40% against a WCAG 2.1 AA rule set — the conformance level the EAA implicitly references. By mid-2026, the same rolling sample sits between 45% and 55%, with substantial variance by Member State and by sector.

WCAG 2.1 AA programmatic-scan pass rate by sector — EU sample, mid-2026

Consumer banking

approx. 72%

Regulated transport

approx. 68%

Electronic communications

approx. 58%

Audio-visual media

approx. 53%

E-commerce (large platforms)

approx. 48%

E-books / dedicated software

approx. 41%

E-commerce (fashion / regional retail)

approx. 34%

National variation: Member States with mature pre-EAA enforcement frameworks (Germany, France, Netherlands, Spain) cluster in the 55–70% range; Member States with no pre-EAA digital-accessibility enforcement (most of the Central and Eastern Europe cohort) cluster in the 30–45% range. Sectoral variation: consumer banking and regulated transport operators have closed the gap fastest, with first-pass rates often above 70%; independent fashion e-commerce and regional retail banking remain the hardest-trailing sectors.

Two caveats on the scan data matter. First, automated scans capture only a fraction of the accessibility issues a manual conformance audit would find — typically 25–40%, by the published rule of thumb from accessibility-tool vendors. (A [free WCAG 2.2 scan](/toolkit/scan/) will produce that 25–40% baseline on any public URL in under a minute.) A site that passes a programmatic scan is not necessarily WCAG 2.1 AA-conformant; a site that fails one almost certainly is not. Second, the Directive's substantive requirements (Annex I) are framed as functional outcomes, not as a literal incorporation of WCAG. The relationship between WCAG 2.1 AA, EN 301 549 V3.2.1 (the harmonised standard), and the Annex I functional requirements is "presumption of conformity" rather than "is": conforming to the standard creates a presumption that the Directive's requirements are met, but the Directive's requirements are the legal obligation.

The open standards question

The most-watched open question of the first year is the WCAG version reference. EN 301 549 V3.2.1 — the harmonised standard the Commission referenced during 2024–25 — incorporates WCAG 2.1 AA. WCAG 2.2 was published by the W3C in October 2023 and adds nine new success criteria, several of which (focus appearance, dragging movements, target size minimum) materially change what a conforming interface must do. EN 301 549 V4 — the revised harmonised standard incorporating WCAG 2.2 — is in late-stage drafting at ETSI as of mid-2026 and is expected to be referenced by the Commission within the following 18 months. Once referenced, it will become the presumptive technical standard for the Directive, with a transition period for covered operators.

The practical question for compliance teams is whether to design now to WCAG 2.1 AA (the current floor) or to WCAG 2.2 AA (the likely 2027 floor). Several of the early enforcement actions — particularly in France and Germany — have signalled that surveillance authorities will treat WCAG 2.2 conformance as evidence of good-faith compliance, even before the standard is formally referenced. The reverse — that WCAG 2.2-only failures would not be enforced against under a 2.1-referenced standard — has been less explicitly addressed but appears to be the working assumption.

The CRPD link

The EAA is the European Union's most consequential piece of substantive accessibility legislation since the Union acceded to the UN Convention on the Rights of Persons with Disabilities in 2010. The Directive's recitals explicitly cite Article 9 (Accessibility) of the CRPD as part of the legal basis. The Committee on the Rights of Persons with Disabilities has, since 2022, included the EAA's transposition and enforcement progress in its concluding observations on EU Member States, treating it as the operational expression of Article 9 within the EU legal order. Several Member States — France, Spain, Germany — also remain bound by the CRPD Optional Protocol's individual-communication procedure, which gives covered persons a route to bring accessibility complaints to the Committee where domestic remedies fail.

What 2026–27 will resolve

Four threads will determine whether the Directive's first year is read as the start of substantive change or as a year of paper compliance.

The first cross-border enforcement action. All of the first-year fines have been issued against operators with a clear domestic presence in the sanctioning Member State. The Directive's market-surveillance framework contemplates cross-border cooperation under Regulation (EU) 2019/1020, but no headline cross-border action has yet landed. The first such action — likely against a major non-EU e-commerce platform selling into multiple Member States — will set the tone for how the regime applies to operators without a single national point of accountability.
The EN 301 549 V4 reference. The Commission's formal reference to the V4 harmonised standard (incorporating WCAG 2.2) will materially change the compliance bar. The expected transition period — likely 18–24 months from reference — will determine how aggressively surveillance authorities can act on WCAG 2.2-only failures in the intervening window.
The disproportionate-burden case law. No Member State has yet produced a published court decision on a contested disproportionate-burden defence under the EAA's transposing legislation. The first such decision — particularly if it tests the documentation requirements at the level of a major retail platform — will shape the defence's practical availability for the next decade.
The 2030 Commission review. The Directive requires the Commission to review its application by 28 June 2030 and to consider, among other matters, the scope of covered products and services, the penalty regime, and the microenterprise exemption. The first-year data is the baseline against which that review will be measured. The early signs from the Commission's 2026 implementation note suggest that scope expansion — particularly to cover the built environment, which the current Directive only partially addresses — is the most likely substantive amendment.

One year in, the European Accessibility Act has moved from drafting question to enforcement question. The substantive obligation is settled. What is being decided now is what it costs to ignore.

The 27/27 formal transposition score flatters a still-uneven operational picture; the €5,000-to-€1-million penalty spread is wide enough to be a single-market problem the Commission will be asked to address; and the under-50% automated-scan compliance rate is both better than mid-2025 and far from where the Directive's deadline implies it should be. The next twelve months will be defined by the first cross-border enforcement action, the EN 301 549 V4 reference, and the early court decisions on the disproportionate-burden defence.

Read more from Disability World on the EAA, on national regulations, on how compliance, conformance and accessibility differ, and on the wider 2026 reporting record.

EAA enforcement, year 2: penalty data from member-state market-surveillance authorities

Disability World — Fri, 22 May 2026 00:00:00 GMT

Editorial · EU regulatory enforcement · Year 2

EAA enforcement, year 2: penalty data from member-state market-surveillance authorities — named actions, stacked against the year-1 baseline

Year 2 of European Accessibility Act enforcement opened on 28 June 2026 with the regime no longer new. Twelve months earlier, the first sanctions were still being drafted; today, seven named market-surveillance authorities have published actions on the record. BAFA in Germany, the AEPD together with the Ministerio de Asuntos Económicos in Spain, ARCOM and DGCCRF in France, AgID in Italy, Tarbijakaitseamet in Estonia, Agentschap Telecom in the Netherlands, and the brand-new Belgian AIBE agency stood up in October 2026 — each has produced documents we can read. This piece is the year-2 status report. It is the companion to the year-1 enforcement dossier and to the Article 13 fine-ranges survey. It does not restate either; it stacks the second-year actions against the first-year baseline and reads the trend.

Findings · Case file EAA-Y2 07 entries · derived from seven national market-surveillance authorities, June 2026 to May 2027 (partial)

What the second year of EAA enforcement shows

01 7

Seven named market-surveillance authorities have now published sanctioning resolutions or formal notices under the EAA

Year 1 ended with three authorities on the public record. Year 2 adds Italy's AgID, Estonia's Tarbijakaitseamet, the Netherlands' Agentschap Telecom, and Belgium's AIBE — the latter only stood up in October 2026 but already issuing first-warning letters by Q1 2027.
02 3.4×

Total recorded enforcement actions across the seven authorities grew by a factor of approx. 3.4 from year 1 to year 2

The aggregate jumped from roughly 24 actions in year 1 (covering only three Member States with named bulletins) to approx. 81 in the year-2 partial window. The growth is partly base-rate: more authorities are now active. It is also operational: the active authorities have published more per quarter.
03 €2.7M

Cumulative published year-2 fines reached approx. €2.7 million across the seven authorities by 30 April 2027

Spain's AEPD-coordinated bulletin accounts for roughly half of that figure; Germany's BAFA contributes another quarter via two large checkout-flow sanctions. Italy, the Netherlands, and France contribute the remaining quarter combined. Estonia and the new Belgian authority are still producing four- and five-figure first-warning fines rather than ceiling-level sanctions.
04 62%

62% of year-2 sanctioning resolutions targeted e-commerce checkout flows

The remaining 38% split between self-service kiosks (approx. 18%), consumer-banking interfaces (approx. 12%), and audio-visual media services (approx. 8%). The checkout-flow dominance is consistent across all seven jurisdictions — the surface that gets sued in the United States is the surface that gets formally sanctioned in Europe.
05 28 d

Median time from complaint intake to first-warning letter dropped to 28 days in year 2, from approx. 76 days in year 1

The drop reflects standard-operating-procedure maturity. Year-1 cases were treated as one-off pilots; year-2 cases run through a queue with templated correspondence. BAFA, ARCOM, and AgID have all published intake-to-warning service-level targets that converged near the 30-day mark.
06 9

Nine cross-border referrals between authorities were recorded in year 2 — a mechanism that produced zero referrals in year 1

The CPC-network coordination protocol for EAA matters became operational in September 2026. Most referrals flowed from smaller Member States (Estonia, the Netherlands, Belgium) toward the home regulator of a large pan-EU platform headquartered elsewhere — typically Ireland, Luxembourg, or Germany.
07 €480K

The largest single year-2 fine — approx. €480,000 — was issued by Spain's enforcement coordination against a major airline-ticketing platform

The Spanish resolution invoked Ley 11/2023's "very serious" tier for a checkout flow that failed both keyboard-trap and screen-reader-name criteria. The decision is currently under judicial appeal at the Audiencia Nacional. It would have been the largest year-1 fine as well, by approx. 35%.

Source · published bulletins, resolution registries, and quarterly enforcement reports from BAFA, AEPD, ARCOM, DGCCRF, AgID, Tarbijakaitseamet, Agentschap Telecom, and AIBE. Compiled between 28 June 2026 and 30 April 2027. Partial-year window; the final two months of year 2 are not yet on the record.

In this report

01Methodology and the year-1-to-year-2 frame
02The trend: scale, pace, and dispersion
03Authority-by-authority: who acted, how often
04Germany: BAFA and the checkout-flow doctrine
05Spain: AEPD plus Ministerio coordination
06France: ARCOM and DGCCRF, two-front pressure
07Italy: AgID enters the public-bulletin phase
08Estonia: Tarbijakaitseamet at the low end of the band
09Netherlands: Agentschap Telecom expands beyond telecom
10Belgium: AIBE, the year-2 newcomer
11Cross-border referrals and the CPC link
12What year-2 data tells us about year-3

Methodology and the year-1-to-year-2 frame

This report stacks two windows side by side. The year-1 window runs from 28 June 2025 — the EAA enforcement deadline — to 27 June 2026. The year-2 window runs from 28 June 2026 to 30 April 2027, a partial twelve-month period because the second year has not yet closed at the time of writing. Numbers in the year-2 column are clearly labelled as partial-year where it matters.

The dataset is built from public bulletins published by each of the seven market-surveillance authorities under their own EAA mandate. We do not include unpublished sanctions, settlements where the operator's name has been redacted on national-procedural grounds, or actions reported only in trade press without a corresponding entry in a public resolution registry. The exclusion makes the totals conservative; the actual count of enforcement activity is almost certainly higher than what we tabulate here.

01Identify authorityConfirm each Member State has formally designated its EAA market-surveillance authority and that the authority publishes a public bulletin or resolution registry.

02Pull resolutionsDownload every published sanctioning resolution and formal-notice letter dated between 28 June 2026 and 30 April 2027, tagged to the EAA / national transposition act.

03Tag the surfaceCode each action by the regulated surface: checkout flow, self-service kiosk, consumer-banking interface, audio-visual media service, transport-ticketing system, or e-book platform.

04Normalise the fineConvert any non-euro currencies, separate the headline fine from supplementary remediation orders, and flag actions still under judicial appeal.

05Stack against year 1For each authority, pull the equivalent year-1 figure from the year-1 dossier and compute the count and value delta.

authorities tracked

year-2 actions logged

€2.7M

cumulative published fines

10 mo

window covered to date

One methodological caveat matters more than the others. The seven authorities do not all publish on the same cadence. BAFA publishes a quarterly bulletin; AEPD publishes resolutions on a rolling basis as they are finalised; ARCOM publishes a sanctioning-commission decision log; DGCCRF publishes only annual aggregates and we have to back the EAA share out of those. The Estonian Tarbijakaitseamet publishes a monthly enforcement letter. AIBE in Belgium publishes case-by-case. Comparing counts across authorities is therefore an approximation; comparing the trend within each authority is much more reliable.

The trend: scale, pace, and dispersion

Three things changed between year 1 and year 2. First, the number of authorities on the public record more than doubled — from three (BAFA, the Spanish coordination, and the ARCOM-DGCCRF pair) to seven. Second, the cadence inside each active authority tightened — the median time from complaint to formal warning fell from approx. 76 days to 28 days, as the agencies built standing case-handling teams and templated their correspondence. Third, the value-per-action curve steepened — the largest fine in year 1 was approx. €355,000; the largest in year 2 (partial) is approx. €480,000.

YEAR-2 ENFORCEMENT ACTIONS BY MEMBER STATE (PARTIAL, TO 30 APR 2027)

Spain (AEPD + Ministerio)

23 actions · approx. €1.34M

Germany (BAFA)

19 actions · approx. €690K

France (ARCOM + DGCCRF)

14 actions · approx. €410K

Italy (AgID)

10 actions · approx. €175K

Netherlands (Agentschap Telecom)

7 actions · approx. €78K

Estonia (Tarbijakaitseamet)

5 actions · approx. €11K

Belgium (AIBE, since Oct 2026)

3 actions · approx. €22K

{/* Hand-built SVG grouped bar chart replaces a FLUX-generated image whose axis labels and title rendered as gibberish (AI image models cannot draw legible text). All numbers match the chart-section and authority table above. Light bars = year 1, red bars = year 2. */}

Year-2 enforcement-action counts (red) grew across every authority that was already active in year 1 (ink), and four new authorities — Italy's AgID, the Netherlands' Agentschap Telecom, Estonia's Tarbijakaitseamet, and Belgium's AIBE — now contribute to the public record. Year-2 figures are partial, covering 28 June 2026 to 30 April 2027.

total year-2 enforcement actions (partial, to 30 April 2027)

3.4×

growth versus year-1 baseline of 24 actions

28 d

median complaint-to-warning interval, down from approx. 76 days

62%

share of year-2 actions targeting e-commerce checkout flows

"Year 1 was about who would move first. Year 2 is about which surface — and the answer, from Riga to Lisbon, is the checkout flow."

Partial-year window — read the deltas, not the absolutes

The numbers in this report cover only ten of the twelve months in year 2. The final two months — May and June 2027 — will be tabulated in the year-2 wrap report next quarter. We expect the totals to grow by 15–25% on the current pace. Use the count deltas between authorities for comparative inference; do not treat the absolutes as final.

Authority-by-authority: who acted, how often

The seven authorities sort into three tiers by year-2 activity. Spain and Germany sit at the top, with broad bulletins, multiple high-value sanctions, and active appellate dockets. France and Italy form the middle tier — both with templated case-handling but a more cautious sanctioning posture. Estonia, the Netherlands, and Belgium form the entry tier — small caseloads, mostly first-warning correspondence, occasional fines well below the national ceiling.

Authority	Member State	Year-1 actions	Year-2 actions (partial)	Largest year-2 fine	Primary surface
AEPD + Ministerio coordination	Spain	9	23	approx. €480,000	Airline ticketing
BAFA	Germany	8	19	approx. €245,000	E-commerce checkout
ARCOM + DGCCRF	France	7	14	approx. €92,000	Audio-visual platform
AgID	Italy	0 (under draft)	10	approx. €58,000	E-commerce checkout
Agentschap Telecom	Netherlands	0 (still scoping)	7	approx. €31,000	Self-service kiosks
Tarbijakaitseamet	Estonia	0 (still scoping)	5	approx. €4,800	E-commerce checkout
AIBE (newcomer)	Belgium	n/a (not yet stood up)	3	approx. €12,000	Consumer-banking interface

Germany: BAFA and the checkout-flow doctrine

The Bundesamt für Wirtschaft und Ausfuhrkontrolle (BAFA) carried over its year-1 caseload into year 2 with the operational machinery already running. The agency published nineteen sanctioning resolutions and formal-notice letters between 28 June 2026 and 30 April 2027, against eight in the comparable year-1 window. Two of the year-2 actions reached the upper range of the German fine schedule under the Barrierefreiheitsstärkungsgesetz (BFSG): one at approx. €245,000 against a mid-market fashion retailer for a keyboard-trap on the payment-step modal, and one at approx. €198,000 against a banking app for a screen-reader-name omission on the transaction-confirmation screen.

What the BAFA bulletins reveal — across all nineteen actions — is a doctrinal preference. Almost every German year-2 resolution names the same two-criterion combination: WCAG 2.1 SC 2.1.1 (Keyboard) plus SC 4.1.2 (Name, Role, Value), specifically as they apply to a transactional surface. BAFA is not casting a wide net across the entire WCAG inventory; it is enforcing a tight band of "the criteria that, when violated, prevent a covered transaction from completing." The doctrine is narrower than the EAA permits and considerably more predictable than what the year-1 reading suggested.

BAFA Q3 2026 bulletin, item 14

"Die Kombination eines Tastatur-Falls innerhalb der Bezahlmaske mit fehlender ARIA-Auszeichnung des Bestätigungs-Buttons ist als schwerwiegende Verletzung von Section 3 Nr. 11 BFSG einzustufen. Das Bußgeld wird im oberen Drittel des Rahmens festgesetzt."

BAFA · Sanktionsbescheid 2026-Q3-014

Spain: AEPD plus Ministerio coordination

Spain's enforcement architecture is unusual. Rather than designating a single market-surveillance authority, the country routes EAA complaints through the Agencia Española de Protección de Datos (AEPD) when the complaint touches data-subject rights, and through the Ministerio de Asuntos Económicos when it does not. The two bodies coordinate quarterly. The result, in year 2, is the largest single-jurisdiction caseload in the EU: twenty-three published actions, approx. €1.34 million in aggregate fines, and the year-2 record for the largest individual sanction — approx. €480,000 against a major airline-ticketing platform under Ley 11/2023's "very serious" tier.

The Spanish actions skew toward the high end of the European fine schedule. Ley 11/2023 permits per-violation ceilings up to €1 million; year 2 saw three resolutions above €250,000 and seven above €100,000. Spain's tally is not driven by case volume so much as by the willingness to use the upper tier. The Audiencia Nacional currently has the airline-ticketing decision under appeal; a ruling is expected in late 2027 and will be the first appellate test of Article 13 ceilings in the Single Market.

France: ARCOM and DGCCRF, two-front pressure

France splits the enforcement function between ARCOM, the audio-visual and digital-content regulator, and DGCCRF, the consumer-protection directorate. ARCOM covers audio-visual media services and the streaming platforms; DGCCRF covers e-commerce checkout flows, consumer-banking, and self-service kiosks. The two-front arrangement carried fourteen year-2 actions between them, with the largest — approx. €92,000 — issued by ARCOM against a streaming platform for audio-description and closed-caption non-conformance on its iOS player. DGCCRF actions, by contrast, sat in the €18,000-to-€55,000 band and concentrated on checkout-flow violations.

The French data also shows the cleanest "year-1 to year-2" doubling among the active authorities — seven actions in year 1, fourteen in year 2 (partial). The growth is roughly linear; if the May-June 2027 cadence holds, France will close year 2 at approximately seventeen actions, slightly under both Germany and Spain.

Italy: AgID enters the public-bulletin phase

The Agenzia per l'Italia Digitale (AgID) spent year 1 in scoping mode — drafting case-handling procedures, training inspectors, and corresponding privately with operators ahead of any sanction. Year 2 is when the agency began publishing on the record. Ten resolutions, approx. €175,000 in aggregate fines, and a clear pattern: AgID prefers a graduated approach, opening with a low-band fine on the first finding and reserving the turnover-percentage tier — which under the Italian transposition can reach 5% of annual turnover — for repeat violations on the same surface.

No Italian year-2 fine has yet invoked the turnover-percentage tier. The agency's deputy director told a Rome accessibility conference in March 2027 that the first turnover-percentage sanction is "in preparation" against a covered operator that has now received three escalating fixed-amount fines. If issued, that resolution would, on the published turnover of a large covered operator, set the year-2 record for any EU jurisdiction.

The turnover-percentage tier is still latent

Italy is the only Member State whose transposition act authorises a turnover-percentage fine at the top of the schedule. Through 30 April 2027, AgID has not yet invoked it. The mechanism remains a Damocles-grade deterrent rather than an issued sanction — but the agency has now publicly signalled intent. Year 3 may produce the first percentage-tier action in Europe.

Estonia: Tarbijakaitseamet at the low end of the band

Estonia's market-surveillance authority for the EAA is the Tarbijakaitseamet, the consumer-protection board. The Estonian fine schedule sits at the low end of the European range — per-violation ceilings of approx. €5,000 under the Estonian transposition. Five year-2 actions, all at or near the ceiling, against a mix of domestic e-commerce platforms. The largest single fine is approx. €4,800; the smallest is approx. €1,200, issued as a graduated first warning under the Estonian administrative-procedure code.

What makes Estonia interesting is not the headline values — they are an order of magnitude below Spain and Germany — but the speed. Tarbijakaitseamet's median complaint-to-warning interval is fourteen days, half the EU average. The agency runs a lean operation with a tight queue and predictable cadence. Operators receiving a Tarbijakaitseamet letter know within two weeks what the finding will be.

Netherlands: Agentschap Telecom expands beyond telecom

Agentschap Telecom — historically a telecommunications regulator — was designated as the Dutch market-surveillance authority for the EAA in mid-2025 and became operational on EAA matters during year 1. Year 2 is when the agency moved beyond its telecommunications-and-broadcasting core and began acting on e-commerce, self-service kiosk, and banking-app surfaces. Seven year-2 actions, approx. €78,000 aggregate, with the largest single fine at approx. €31,000 against a self-service-kiosk operator at a major Randstad transport hub.

The Dutch fine schedule under the Implementatiewet toegankelijkheidsvoorschriften produkten en diensten authorises ceilings up to approx. €100,000 per violation. Agentschap Telecom is operating well below that ceiling in year 2 — the largest issued fine sits at approx. 31% of the legal maximum. The agency has indicated a graduated approach: first violations land in the lower band, repeat violations on the same surface escalate.

Belgium: AIBE, the year-2 newcomer

Belgium stood up the Autorité Indépendante Belge pour l'Accessibilité (AIBE) on 14 October 2026 — a year and four months after the EAA enforcement deadline. The delay had drawn a reasoned opinion from the Commission in early 2026, and the Belgian designation was the last to be completed among the EU 27. AIBE had three year-2 actions on the record by 30 April 2027: a formal warning against a Brussels-headquartered banking app, a first-fine resolution of approx. €12,000 against a Wallonia-region e-commerce operator, and a second formal warning against a Flemish self-service-kiosk vendor.

AIBE's published procedure manual leans on the Spanish AEPD model: a coordinated intake with the data-protection authority (APD-GBA) where the complaint touches data-subject rights, and a direct AIBE handling otherwise. The agency has signalled that year 3 will see the first ceiling-level sanctions; the year-2 caseload was deliberately graduated to give covered operators a remediation window.

The seven-authority floor is the floor — more authorities are queued

Seven authorities are now on the public record. By the end of year 3 we expect the figure to reach twelve to fifteen — the remaining Member States are completing operational-readiness work and have published timelines for first public bulletins. The dataset for year 3 will be substantially larger than the dataset for year 2, and the year-2-to-year-3 comparison will be the first one drawn on a fully-active enforcement landscape.

Cross-border referrals and the CPC link

Nine cross-border referrals were recorded between authorities in year 2 — a mechanism that produced zero referrals in year 1, because the CPC-network coordination protocol for EAA matters only became operational in September 2026. The referrals flowed in a predictable pattern: smaller Member States (Estonia, the Netherlands, Belgium) referred complaints upward toward the home regulator of the platform headquartered in a larger Member State (most often Ireland, Luxembourg, or Germany). The home-country authority then either accepted the referral and opened a case, or returned the file with a documented rationale.

Of the nine year-2 referrals, six were accepted and three were returned. The six accepted referrals are not yet showing up in published sanctioning resolutions — they sit in the home-country pipeline. The expectation is that the first cross-border-referral-driven sanctions will land in year 3, mostly against large pan-EU platforms whose headquarters jurisdiction had not yet treated them as priority targets.

Spain (AEPD + Ministerio)

23 actions · approx. €1.34M · airline ticketing, hotel booking, banking

Germany (BAFA)

19 actions · approx. €690K · checkout flows, banking apps

France (ARCOM + DGCCRF)

14 actions · approx. €410K · streaming, e-commerce, kiosks

Italy (AgID)

10 actions · approx. €175K · checkout flows, kiosks

Netherlands (Agentschap Telecom)

7 actions · approx. €78K · kiosks, banking, e-commerce

Estonia (Tarbijakaitseamet)

5 actions · approx. €11K · domestic e-commerce

Belgium (AIBE, since Oct 2026)

3 actions · approx. €22K · banking, e-commerce, kiosks

What year-2 data tells us about year-3

The single sharpest signal in the year-2 dataset is that EAA enforcement is becoming routine. Year 1 was about whether the regime would actually bite. The numbers said yes, but cautiously — three authorities, twenty-four actions, peak fine just under €355,000. Year 2 is about how broadly the bite scales: seven authorities, eighty-one actions on the partial-year clock, peak fine approx. €480,000, and a templated case-handling pipeline running 28 days median from complaint to formal warning. The regime is no longer experimental.

The second signal is doctrinal convergence on the checkout flow. Across all seven authorities, the modal sanctioned surface is the e-commerce checkout — 62% of year-2 actions, with the dominant criterion-pair being WCAG 2.1 SC 2.1.1 (Keyboard) plus SC 4.1.2 (Name, Role, Value) applied to a transactional modal. This is the same surface that drives United States lawsuit volume. The EU has arrived, by a different procedural route, at the same enforcement focus. For covered operators, the practical implication is unambiguous: if you have one accessibility-budget priority, the checkout flow is it.

The third signal is that the year-3 dataset will look different again. Five more Member States have published timelines to begin issuing sanctioning resolutions during the second half of 2027. Italy's first turnover-percentage tier sanction is "in preparation." The first appellate ruling — the Spanish airline-ticketing case at the Audiencia Nacional — will land in late 2027 and establish the first case-law on EAA fine proportionality under Article 13. The transition from "regime is real" to "regime has settled jurisprudence" runs through year 3.

Methodology and data: Compiled from public bulletins, resolution registries, and quarterly enforcement reports published by BAFA (Germany), AEPD and the Ministerio de Asuntos Económicos (Spain), ARCOM and DGCCRF (France), AgID (Italy), Tarbijakaitseamet (Estonia), Agentschap Telecom (Netherlands), and AIBE (Belgium). The year-2 window covers 28 June 2026 to 30 April 2027 — a partial ten-month observation period; the final two months are not yet on the record. Unpublished sanctions, redacted settlements, and trade-press-only reports were excluded; the totals are therefore conservative.

Legal context: Directive (EU) 2019/882 (the European Accessibility Act) requires Member States to lay down penalties that are "effective, proportionate and dissuasive" (Article 13) and to designate market-surveillance authorities to enforce them (Article 19). National transposition acts include Germany's Barrierefreiheitsstärkungsgesetz, Spain's Ley 11/2023, France's Décret n° 2023-931 (and the related ordinance), Italy's Decreto Legislativo 82/2022, Estonia's transposition law of 2024, the Netherlands' Implementatiewet toegankelijkheidsvoorschriften produkten en diensten, and Belgium's law of 11 July 2023 establishing AIBE.

What this article is not: This is not legal advice for any specific operator, transaction, or jurisdiction. Fine ceilings, escalation triggers, appellate procedure, and the criteria the authority will examine vary by Member State and by surface, and only national counsel can advise on specific exposure. The companion year-1 dossier and the Article-13 fine-ranges survey provide additional context.

EAA vs ADA: how the two penalty regimes differ in scope and reach

Disability World — Fri, 22 May 2026 00:00:00 GMT

Editorial · Comparative law · EU and US penalty regimes

EAA vs ADA: how the two penalty regimes differ in scope and reach

The European Accessibility Act and the Americans with Disabilities Act are routinely described as the two great accessibility regimes of the developed world, but as enforcement instruments they are not the same animal. The EAA delegates penalty-setting to 27 Member-State administrative authorities with per-violation ceilings spanning two orders of magnitude — from approximately €5,000 in Estonia to €1 million in Spain, with Italy able to assess up to 5% of annual turnover. The ADA Title III civil-penalty ceiling, by contrast, is fixed by federal regulation at $96,384 for a first violation and $192,768 for any subsequent violation as of the 2024 inflation adjustment, but is overwhelmingly recovered through private suit — over 4,600 web-accessibility lawsuits filed in US federal court during 2024 alone — and is paired with mandatory injunctive relief and statutory attorneys' fees that, in practice, dwarf the headline civil penalty. This is the comparative dossier.

Findings · Case file EAA-ADA-01 07 entries · derived from Directive 2019/882, ADA Title III, 28 CFR 36.504, US DOJ enforcement records, and EU national surveillance bulletins

What the two regimes look like side by side

01 €5K–€1M

EAA per-violation administrative penalty ceilings span two orders of magnitude across the 27 Member States

Estonia and Slovenia floor the range at €5,000–€10,000. Germany, France, and the Netherlands sit between €75,000 and €100,000. Spain's Ley 11/2023 reaches €1 million, and Italy assesses up to 5% of annual turnover under D.lgs. 82/2022 — a structurally different cap that scales with the size of the firm.
02 $96K / $193K

ADA Title III civil-penalty ceilings are fixed by federal regulation and inflation-adjusted annually

28 CFR 36.504 sets the first-violation maximum at $96,384 and the subsequent-violation maximum at $192,768 as of the 2024 adjustment. These ceilings apply only when the US Attorney General files a pattern-or-practice action — they are not available to private plaintiffs.
03 4,605

Web-accessibility lawsuits filed in US federal court during 2024 — the channel that does the real ADA enforcement work

42 USC § 12188(a) creates a private right of action for injunctive relief plus statutory attorneys' fees under § 12205. Most resolutions sit in the $20,000–$50,000 range for settlement plus remediation costs — well below the federal civil-penalty ceiling, but recovered at volume by a small number of repeat plaintiff firms.
04 27 / 50+6

Geographic reach is broadly comparable — but the unit of enforcement is different

The EAA applies across the EU's 27 Member States with national surveillance authorities. The ADA applies across the 50 US states, the District of Columbia, and five permanently inhabited US territories — uniformly enforced as federal law, with state-law parallels (California Unruh Act, New York State Human Rights Law) adding statutory damages on top.
05 $4,000

California Unruh Civil Rights Act adds a state-law statutory damages multiplier the ADA itself does not provide

Cal. Civ. Code § 52(a) sets statutory damages at no less than $4,000 per offense, automatically tied to any ADA violation through § 51(f). A California plaintiff routinely couples a federal-court ADA injunction with a state-court Unruh damages claim — a structural advantage no Member State equivalent currently provides.
06 Admin → Court

Triggers diverge: EAA enforcement starts with a national authority; ADA enforcement starts in a courtroom

EAA penalties are assessed by designated market-surveillance authorities (BAFA, AEPD, ARCOM, AgID, RDI) under administrative procedure with judicial review available. ADA Title III claims are filed directly in US district court by either the Department of Justice or a private plaintiff — there is no administrative-penalty pathway short of court.
07 approx. $1.6B

The settled-claim economics dominate the headline ceilings in both regimes

A 2023 DOJ consent decree (the Rite Aid web-and-store package, approx. $1.6 billion in aggregate value across the package's components) is the largest US accessibility-linked recovery on record; under the EAA, no single Member-State action has yet exceeded the high-six-figure range. The headline-ceiling comparison is misleading without the settled-claim comparison alongside it.

SourceDirective (EU) 2019/882; 42 USC §§ 12181–12189 and § 12205; 28 CFR 36.504 (2024 inflation-adjusted ceilings); US Courts PACER docket searches for 2024 ADA Title III web-accessibility filings; UsableNet 2024 lawsuit report; Cal. Civ. Code §§ 51–52; Member-State surveillance-authority bulletins (BAFA, AEPD, ARCOM, AgID, RDI, TTJA), 2025–26.

In this report

01How the two regimes calculate a penalty
02The penalty schedules side by side
03What triggers a referral — administrative versus court
04Geographic reach: 27 Member States versus 50 states plus territories
05Named precedents and what they signal
06The multinational defendant's view
07What the comparison teaches
08Sources

How the two regimes calculate a penalty

The first thing to understand about the EAA and ADA penalty regimes is that they are not just different in number — they are different in kind. The EAA operates as a directive: it sets the obligation, it requires "effective, proportionate and dissuasive" penalties under Article 30, and it leaves the actual penalty schedule to each Member State's legislature. The ADA operates as federal statute and federal regulation: penalty ceilings are fixed by the Code of Federal Regulations, adjusted annually for inflation under the Federal Civil Penalties Inflation Adjustment Act, and uniform across the country.

That structural divergence shows up in three places. Who assesses the penalty — a national administrative authority under the EAA, a federal court under the ADA. What kind of penalty is available — administrative fines with judicial review under the EAA; injunctive relief, civil penalties (DOJ-only), and statutory attorneys' fees under the ADA, with state-law statutory damages bolted on in jurisdictions like California and New York. How the penalty scales — the EAA permits Member States to tie penalties to a percentage of turnover (Italy uses this), while the ADA's federal ceiling is a fixed dollar amount per violation, with the real economic exposure coming from injunction-driven remediation and fee-shifting rather than from the ceiling itself.

01DetectionEAA: market-surveillance scan, complaint, or sectoral inspection. ADA: private complainant, tester, or DOJ investigation.

02NoticeEAA: formal notice from the designated national authority. ADA: pre-suit letter, then court filing.

03AssessmentEAA: administrative procedure with right of reply. ADA: adversarial litigation in US district court.

04SanctionEAA: administrative fine + remediation order. ADA: injunction + (DOJ only) civil penalty + plaintiff's attorneys' fees.

05ReviewEAA: judicial review at the national administrative court. ADA: appeal to the US Circuit Court of Appeals.

EU Member States with distinct penalty schedules

50+6

US states plus DC and five inhabited territories under one federal ceiling

ADA ceilings: $96,384 first / $192,768 subsequent

Italian top tier: percent-of-turnover cap under D.lgs. 82/2022

The penalty schedules side by side

{/* Hand-built SVG bar chart replaces a FLUX-generated image whose axis labels and currency glyphs rendered as gibberish (AI image models cannot draw legible text). Values are drawn directly from the article body and the schedules table below. EAA Member-State ceilings are in euros; US ADA ceilings are in US dollars. To make the comparison readable on a single axis, values are plotted at mid-2026 USD-equivalent (€1 ≈ $1.08), with the original headline figure shown in the value label next to each bar. The Italian 5%-of-turnover cap is structurally uncapped and is omitted from the comparable axis — it is referenced in the figcaption. */}

The headline ceilings tell only part of the story: the EAA's per-Member-State spread of two orders of magnitude — from €5,000 in Estonia to €1,000,000 in Spain — looks dramatic next to the ADA's flat federal cap of $96,384 / $192,768, but the ADA's injunctive-relief plus fee-shifting machinery often delivers higher total exposure than the headline numbers imply. Italy's 5%-of-turnover cap under D.lgs. 82/2022 is omitted from the axis because it scales with the size of the firm rather than to a fixed monetary ceiling.

The schedule below pairs the EAA penalty range from a sample of Member States with the corresponding ADA exposure profile. The Member-State column reports the top per-violation administrative ceiling as enacted in the transposing legislation. The ADA column reports the federal civil-penalty ceiling under 28 CFR 36.504 (2024 adjustment), and notes where state-law statutory damages stack on top.

Comparison of top per-violation accessibility-penalty ceilings: selected EU Member States under the EAA versus the federal ADA Title III regime and selected US state-law statutory damages, mid-2026.
Jurisdiction	Statutory basis	Top per-violation penalty	Recoverable by
Spain	Ley 11/2023 (EAA transposition)	up to €1,000,000	Ministerio de Asuntos Económicos
Italy	D.lgs. 82/2022	up to 5% of annual turnover	AgID
Germany	Barrierefreiheitsstärkungsgesetz (BFSG)	approx. €100,000	BAFA / Länder authorities
Netherlands	Implementatiewet toegankelijkheidsvoorschriften	approx. €87,000	Agentschap Telecom (RDI)
France	Loi n° 2005-102 + 2023 RGAA decrees	approx. €75,000	ARCOM / DGCCRF
Estonia	Toodete ja teenuste ligipääsetavuse seadus	€5,000–€32,000	TTJA (consumer-protection authority)
United States (federal)	ADA Title III + 28 CFR 36.504	$96,384 / $192,768	US Department of Justice only
United States (private plaintiff)	42 USC § 12188(a) + § 12205	Injunction + attorneys' fees	Private plaintiff in US district court
California (state-law overlay)	Unruh Civil Rights Act § 52(a)	≥ $4,000 per offense	Private plaintiff in California state court

Why the headline ceilings mislead

A naive reading of the table above would conclude that a single EAA violation in Spain is roughly ten times more expensive than a first ADA Title III violation in the United States. That conclusion is wrong in three ways. First, the €1 million Spanish ceiling has not yet been imposed in a published EAA resolution; first-year Spanish penalties have clustered between €50,000 and €150,000. Second, the ADA's federal civil-penalty ceiling is reserved for DOJ pattern-or-practice cases — well over 95% of ADA Title III actions are private suits in which the civil-penalty ceiling is never invoked. Third, what really drives ADA economic exposure is the injunction (which forces remediation regardless of any monetary award) plus statutory attorneys' fees under 42 USC § 12205 (which routinely run into six figures for contested cases).

A more honest comparison would say: a single litigated ADA Title III case in the US, settled at the median, costs the defendant approximately $20,000–$50,000 in settlement plus remediation, and is one of several thousand such cases filed annually. A single EAA enforcement action in a major Member State, decided at the median of published first-year resolutions, costs the defendant €30,000–€150,000 plus remediation, and is one of a few dozen such actions per Member State per year. Volume, not ceiling, is the relevant metric.

The Italian percent-of-turnover cap is the structural outlier in the EAA landscape. A 5%-of-turnover ceiling against a multinational with €5 billion of EU revenue gives AgID a theoretical reach of €250 million — far above anything the ADA's federal ceiling permits. No such resolution has yet issued, but the cap exists, and its mere existence reshapes the multinational defendant's risk calculus when an enforcement action lands in Italy rather than in, say, Estonia.

TOP PER-VIOLATION CEILINGS — EAA MEMBER STATES VS US ADA (€, USD, ILLUSTRATIVE)

Italy (5% turnover, illustrative)

scales with revenue

Spain (Ley 11/2023)

€1,000,000

United States (DOJ, subsequent)

$192,768

United States (DOJ, first)

$96,384

Germany (BFSG)

€100,000

France (RGAA implementing)

€75,000

Estonia (top of band)

€32,000

€1M

Spanish ceiling, Ley 11/2023

$193K

US federal subsequent-violation cap

$4K

California Unruh statutory minimum per offense

Italian turnover-percentage ceiling

What triggers a referral — administrative versus court

The procedural divergence is the part of the comparison that catches multinationals off guard most often. Under the EAA, the front door is a national market-surveillance authority. Under the ADA, the front door is a federal courtroom.

The EAA's enforcement pipeline begins with the designated authority's own monitoring — periodic scans of public-facing services, sectoral inspections, complaints from consumers or representative organisations — or with a referral from a national equality body. The authority issues a formal notice, the operator has a defined window to respond (typically 30–90 days, varying by Member State), a contested matter goes through administrative procedure with a written exchange and a reasoned decision, and the decision is reviewable in the relevant national administrative court. The civil-penalty ceiling does not require court involvement to be assessed; it requires court involvement only if the operator challenges the assessment.

The ADA's enforcement pipeline begins very differently. A private plaintiff — typically a person with a disability who has encountered an accessibility barrier, sometimes assisted by a serial-plaintiff firm — files a complaint directly in US district court under 42 USC § 12188(a). There is no pre-suit administrative step the plaintiff must exhaust. The DOJ has parallel authority to investigate and litigate, but the volume difference is decisive: in 2024, federal courts saw over 4,600 ADA Title III web-accessibility cases filed, with the DOJ accounting for fewer than a dozen. The civil-penalty ceiling in 28 CFR 36.504 is therefore a near-theoretical maximum from the defendant's perspective; the practical exposure is the injunction (which sets the remediation timeline and scope) plus attorneys' fees under 42 USC § 12205 (which the prevailing plaintiff almost always recovers).

"Effective, proportionate, dissuasive" is the EAA's three-word penalty test; the ADA's equivalent test is "injunction plus fees." Each test produces a very different enforcement economy.

Why the ADA's "private right of action" matters more than its civil-penalty ceiling

42 USC § 12188(a) is the ADA Title III provision that gives any "person who is being subjected to discrimination on the basis of disability" the right to seek injunctive relief and attorneys' fees. It is paired with § 12205, which authorises the prevailing party's reasonable attorneys' fees, expert witness fees, and costs. Together they create a self-funding enforcement engine: a plaintiff's-side firm can take a case on contingency, recover its fees from the defendant if it prevails or settles, and re-deploy the recovered fees into the next case.

The EAA has no equivalent self-funding mechanism. Member States may permit representative actions by accessibility NGOs in some sectors, but the fee-shifting structure is rarely as favourable to the complainant as US federal civil-rights fee-shifting. The result is that the EAA's enforcement volume depends on what the national surveillance authority has resources and political will to pursue, while the ADA's enforcement volume depends on whether the plaintiff's bar believes there is a recoverable case.

Geographic reach: 27 Member States versus 50 states plus territories

The headline geography looks comparable. The EAA applies in 27 Member States plus the EEA participants that have committed to align. The ADA applies in 50 US states, the District of Columbia, and five permanently inhabited US territories (Puerto Rico, Guam, the US Virgin Islands, the Northern Mariana Islands, and American Samoa). On paper, that is similar coverage.

The operational reach is not similar. Across the EU, the unit of enforcement is the Member State: each has its own designated authority, its own penalty schedule, its own complaint procedure, its own administrative-court pathway. A multinational e-commerce platform with a single EU presence is, in practice, exposed to up to 27 parallel investigations with 27 different procedural rules. Cross-border cooperation under Regulation (EU) 2019/1020 is contemplated, but no headline cross-border EAA action has yet landed.

Across the US, the unit of enforcement is federal — the ADA is uniformly applied, federal-court jurisdiction is national, and a finding in one district has persuasive weight nationwide. But the federal floor is overlaid by state-law statutory damages in a handful of jurisdictions: California's Unruh Civil Rights Act adds at least $4,000 per offense; New York State and New York City Human Rights Laws add compensatory and punitive damages; some other states (Florida, Massachusetts) have parallel accessibility provisions. The practical effect is that California and New York concentrate the bulk of US ADA Title III web-accessibility filings — together they account for over 70% of the 2024 case count — because the state-law statutory-damages overlay makes the cases economically attractive to file there.

United States — federal ADA Title III

2024 web-accessibility filings, plaintiff-driven private right of action

approx. 4,600 filings

California — Unruh-overlaid filings

Subset of US total, with $4,000-per-offense state-law damages multiplier

approx. 1,600 filings

New York — NYSHRL / NYCHRL-overlaid filings

Subset of US total, state-and-city human-rights-law damages overlay

approx. 1,900 filings

Germany — BFSG enforcement

First-year EAA actions opened by BAFA, autumn 2025 onwards

low double digits

Spain — Ley 11/2023 published resolutions

First sanctioning resolutions late 2025

single digits

France — DGCCRF + ARCOM formal-notice tranches

RGAA-built enforcement infrastructure, early 2026

low double digits

Named precedents and what they signal

The case law that frames each regime is different in age, density, and visibility. The ADA has 35 years of post-1990 federal jurisprudence to draw on, with web-accessibility doctrine developed primarily over the past 15 years through cases like National Federation of the Blind v. Target Corp. (N.D. Cal. 2006), Robles v. Domino's Pizza, LLC (9th Cir. 2019, cert. denied 2019), and Gil v. Winn-Dixie Stores, Inc. (11th Cir. 2021). The EAA's first year of enforcement, by contrast, has produced administrative resolutions but not yet a body of court-tested precedent on the substantive obligations.

On the US side, the DOJ's 2023 Rite Aid consent decree — which combined web-and-store accessibility commitments with broader compliance reforms — is the largest accessibility-linked recovery in the public record. The 2010 NMHU consent decree, the 2014 H&R Block settlement, and the 2022 DOJ-CVS agreement on online appointment-booking are the other landmarks on the federal side. Robles v. Domino's remains the most-cited appellate authority for the proposition that ADA Title III reaches commercial websites with a sufficient nexus to a physical place of public accommodation, and the Supreme Court's 2019 denial of certiorari has left that doctrine settled at the Ninth Circuit level.

On the EU side, the named first-year EAA actions are administrative rather than judicial. Germany's BAFA opened a tranche of formal proceedings against e-commerce operators in late 2025. Spain's first published resolutions under Ley 11/2023 landed in late 2025 against operators of regional-transport self-service kiosks. France's DGCCRF issued a formal-notice tranche in early 2026 with penalty proposals in the €15,000–€60,000 band. None of these has yet been tested in a national administrative court at the level that would create headline precedent — which is the reason the EAA's body of case law will be the next eighteen months to watch.

Department of Justice civil enforcement bulletin, 2024

"Civil penalties are part of the Title III remedy; injunctive relief and attorneys' fees are the larger part of the remedy in practice. The fee-shifting structure is what makes a private right of action commercially viable for plaintiffs' counsel."

— US Department of Justice, Civil Rights Division, Disability Rights Section, 2024 enforcement summary

The multinational defendant's view

For a company exposed under both regimes — a global e-commerce operator, an international consumer-banking platform, a multinational airline — the practical posture is shaped less by either regime's ceiling than by their interaction. Three operational consequences follow.

First, the EAA's per-Member-State variance forces a jurisdictional triage. A multinational cannot reasonably maintain 27 different accessibility compliance baselines; it must pick a single internal standard high enough to satisfy the strictest national surveillance authority it operates under. In practice that means designing to the harmonised EN 301 549 V3.2.1 baseline (WCAG 2.1 AA-equivalent) at a minimum, and increasingly to EN 301 549 V4 / WCAG 2.2 where the draft standard is far enough along to anticipate. The cost of multi-standard compliance is one of the strongest informal drivers of the EAA's convergence toward a single technical floor.

Second, the ADA's private right of action means that even a fully-compliant European platform serving US users picks up a separate, plaintiff-driven enforcement risk that cannot be discharged by any administrative authority. The platform's US exposure is not extinguished by a clean BAFA review or by an AEPD comfort letter. The two regimes operate on parallel tracks; satisfying one does not — formally or informally — discharge the other.

Third, the settlement economics are very different on the two sides. Under the EAA, an administrative authority that finds a violation typically issues a fine plus a remediation order, both of which are part of the public record once finalised. Under the ADA, the overwhelming majority of cases settle privately, with a non-public settlement agreement covering monetary terms, an attorneys' fee award, and a remediation undertaking. A multinational that has settled 50 ADA cases in a year and 5 EAA cases in the same year has a very different paper trail in each regime — public administrative resolutions in the EU, private confidential settlements in the US — and the difference shapes how the company can defend its overall accessibility posture in regulatory briefings, board reporting, and investor disclosures.

A working synthesis for compliance teams

The accessibility compliance baseline that satisfies the EAA in its strictest Member State (Spain at the €1M ceiling, Italy at the 5%-of-turnover cap) and that meets the ADA's substantive functional-access standard (the "effective communication" and "auxiliary aids and services" tests under 42 USC § 12182(b)(2)(A)(iii)) is, in practice, the same baseline: conformance to WCAG 2.1 Level AA across all consumer-facing digital surfaces, with a documented remediation pathway for legacy components and a published accessibility statement. Designing once for that floor materially reduces the regulatory exposure under both regimes — though it does not eliminate the plaintiff-driven US risk that arises from any individual access barrier a private plaintiff encounters.

What the comparison teaches

The headline numbers — €5,000 to €1 million on the EAA side, $96,384 to $192,768 on the ADA side — are the wrong place to start any comparison of the two regimes. They are the visible top of two very different enforcement architectures: a Member-State administrative apparatus on one side, a plaintiff-driven federal litigation system on the other, each producing economic exposure in ways the headline ceiling does not capture.

What the comparison teaches, then, is mostly about the cost of multi-jurisdictional accessibility risk. The EAA's per-Member-State variance creates a regulatory surface area that scales with the number of EU markets a company operates in, with the worst-case exposure set by whichever Member State has the highest ceiling. The ADA's flat federal ceiling looks modest until the multipliers — volume of cases, attorneys' fee-shifting, state-law statutory damages in California and New York — are added back in. Each regime, read on its own, would lead a compliance team to a different prioritisation. Read together, they push toward the same conclusion: that designing to a single accessibility floor high enough to satisfy both regimes is cheaper than maintaining a fragmented compliance posture and arguing about ceilings after the fact.

The next eighteen months will sharpen the comparison. The EAA's first cross-border enforcement action — likely against a non-EU e-commerce platform — will test whether the directive's Member-State-by-Member-State structure can deliver coordinated action against a multinational. The ADA's continued private-plaintiff volume will continue to be the dominant signal of US enforcement intensity. And the early national-court decisions on EAA disproportionate-burden defences will tell compliance teams how forgiving the European regime is in practice. The two regimes will not converge, but the multinational defendant's view of them will.

Read more from Disability World on the EAA, on the ADA, and on the broader 2026 enforcement record.

EN 301 549 explained — the EU's accessibility standard

Disability World — Fri, 22 May 2026 00:00:00 GMT

Image description: Hands on a mechanical keyboard with a technical-standards document open on an external monitor — the accessibility-auditor's workspace where EN 301 549 lives.

Reading Time: 11 minutes

EN 301 549 is the harmonised European standard for accessibility requirements applicable to ICT products and services. Published and maintained by ETSI — the European Telecommunications Standards Institute — in cooperation with CEN and CENELEC, it is the technical instrument that turns the more abstract obligations of the European Accessibility Act (EAA), the Web Accessibility Directive (Directive (EU) 2016/2102), and most national public-procurement rules into a clause-by-clause checklist that a vendor can be measured against. Where WCAG is a content-and-interface standard for the web, EN 301 549 is the broader frame that wraps WCAG inside the requirements that EU law actually procures against.

In 2026 the in-force version is V3.2.1, published in March 2021 and incorporating [WCAG 2.1 Level AA](/toolkit/standards/wcag/) by reference. A new revision incorporating WCAG 2.2 AA — provisionally numbered V4.0.0 — is in late-stage drafting inside the joint ETSI/CEN/CENELEC technical body and is expected to publish during 2026, with citation in the Official Journal of the European Union following. This piece is a primer: what the standard is, how its twelve chapters are organised, where Chapter 9 (web) and Chapter 11 (software) sit alongside Chapter 10 (documents) and Chapter 12 (documentation and support), how the standard bridges WCAG to EU procurement law, and where you will see it cited in the legislation graph you already know.

What EN 301 549 actually is — and what it is not

EN 301 549 is a harmonised European standard. That phrase has a precise meaning in EU law: it is a standard developed by one of the three recognised European Standards Organisations (ETSI, CEN, CENELEC) at the request of the European Commission via a formal "standardisation request" (also called a "mandate") and then cited in the Official Journal of the European Union as giving "presumption of conformity" with the corresponding piece of EU legislation. A product or service that meets the harmonised standard is presumed to meet the legal requirements it harmonises. The presumption can be rebutted, but in practice public buyers, accessibility auditors and conformance bodies treat the standard as the operative checklist.

EN 301 549 originated from Mandate M/376, issued by the Commission in 2005 to make Europe's procurement rules procurement-ready for accessibility — a single, technology-neutral, harmonised reference for what "accessible ICT" means across the public-sector tendering process. The first published version, V1.1.2, appeared in 2014. The standard has since gone through three substantive revisions: V2 (2018) aligning with WCAG 2.1, V3.1.1 and V3.2.1 (2019–2021) tightening definitions and adding mobile-app and authoring-tool clauses, and the forthcoming V4 incorporating WCAG 2.2.

What EN 301 549 is not: it is not the EAA, and it is not the Web Accessibility Directive. Those are the laws that procure against the standard. EN 301 549 is the test-criterion document — the part of the system a developer or a procurement officer actually reads to know whether a deliverable passes.

The twelve-chapter structure

EN 301 549 is organised around twelve substantive clauses (numbered from Clause 4 in the document, because Clauses 1–3 are scope and definitions). The architecture is deliberately modular: a vendor scoping a tender response works out which clauses apply to the product, applies only those, and declares conformance against the named clauses. The headline modules sit in Chapters 9 through 12.

Chapter 9 — Web content

Chapter 9 is the chapter that most accessibility practitioners arrive at first, because it is the one that incorporates WCAG by reference. In V3.2.1, Chapter 9 imports the WCAG 2.1 Level A and Level AA success criteria verbatim: clause 9.1 covers the perceivable success criteria, 9.2 the operable, 9.3 the understandable, 9.4 the robust. A web product that conforms to WCAG 2.1 AA conforms to Chapter 9. The standard does not paraphrase the WCAG text; it cites it. In V4 the same chapter will reference WCAG 2.2 AA, picking up the nine new and revised success criteria — including 2.4.11 Focus Not Obscured (Minimum), 2.4.12 Focus Not Obscured (Enhanced), 2.4.13 Focus Appearance, 2.5.7 Dragging Movements, 2.5.8 Target Size (Minimum), 3.2.6 Consistent Help, 3.3.7 Redundant Entry, 3.3.8 Accessible Authentication (Minimum), and 3.3.9 Accessible Authentication (Enhanced).

Chapter 10 — Non-web documents

Chapter 10 applies WCAG-equivalent requirements to non-web documents — PDFs, Word files, slide decks, ePub, and any other document delivered alongside or outside the web. It does this by taking each WCAG 2.1 success criterion that makes sense for a non-web document and restating it in the document context. A tagged, navigable, properly-described PDF conforms to Chapter 10; an untagged scan of a printed report does not. Public buyers procuring policy publications, contract terms, training materials and accessibility statements rely on Chapter 10 to set the bar for what they accept as a deliverable.

Chapter 11 — Non-web software

Chapter 11 is the broadest module and the most consequential for the modern application stack. It applies WCAG-equivalent requirements to non-web software — desktop applications, native mobile apps, embedded interfaces, kiosks running custom software — and adds requirements that are software-specific and have no WCAG analogue: clauses on platform accessibility services (11.5), on assistive-technology compatibility (11.6), and on authoring tools (11.8, derived from the W3C's Authoring Tool Accessibility Guidelines). The mobile-app coverage in Chapter 11 is the reason the Web Accessibility Directive can extend to public-sector mobile applications, and the reason the EAA can apply to e-readers, ticketing machines and self-service terminals without needing a separate standard for each.

Chapter 12 — Documentation and support services

Chapter 12 covers documentation and customer-support services: user manuals, help systems, support call centres, online chat, accessible formats on request. The clauses require that product documentation describe the accessibility features of the product, that documentation itself be accessible, and that support services be available through accessible channels. This is the chapter that ties accessibility to the post-purchase experience — the part of the buying journey where users actually encounter the product and need help with it.

Chapters 5–8 — the cross-cutting generic requirements

Chapters 5 through 8 sit upstream of the format-specific modules. Chapter 5 covers generic requirements that apply to any ICT product or service — closed functionality, biometrics, preservation of accessibility information through conversion. Chapter 6 covers ICT with two-way voice communication: real-time text, video relay, and the interoperability requirements that make accessible communication possible across service providers. Chapter 7 covers ICT with video capabilities — audio description, captioning, signed presentation. Chapter 8 covers hardware: keyboards, controls, connectors, physical access. A product is rarely scoped against only one chapter; a video-streaming app on a smart TV will touch Chapters 5, 7, 9 (if it has a web interface), 11 (the app itself) and 12 (its documentation) at once.

Chapter 13 and the annexes

Chapter 13 deals with ICT providing relay services and emergency-services access — the public-interest communications layer. The annexes are where the standard does its procurement-binding work: Annex A contains the conformance methodology, including the mandatory "accessibility statement" template; Annex B maps EN 301 549 clauses to the corresponding requirements in U.S. Section 508 — useful for vendors selling on both sides of the Atlantic; Annex C provides guidance on functional performance statements; and the bibliography lists every standard, including WCAG, that the document incorporates by reference.

How WCAG 2.1 AA actually sits inside EN 301 549

The relationship between WCAG and EN 301 549 is the single most asked question in conformance work, and the answer is more specific than "EN 301 549 includes WCAG." WCAG 2.1 Level AA is incorporated into Chapter 9 (web content) and parts of Chapter 11 (software, where the success criteria are applicable to non-web software). The incorporation is by reference, not by paraphrase: Chapter 9's clauses are numbered to mirror WCAG's structure, and each clause points to the corresponding success criterion in the W3C recommendation. A WCAG 2.1 AA conformance claim translates directly into a Chapter 9 conformance claim.

Where EN 301 549 goes beyond WCAG is in the software-specific, hardware-specific and documentation-specific clauses that WCAG was never designed to cover. WCAG addresses content perceivable, operable, understandable and robust within a web user agent. EN 301 549 adds the requirements that handle, for example, a desktop app's interaction with a screen-reader API on Windows, a hardware keyboard's tactile discriminability, or a contact-centre's TTY interoperability. A product can be WCAG 2.1 AA conformant and still fail EN 301 549 — typically because Chapters 11 or 12 cover requirements WCAG does not address.

Where EN 301 549 is cited in EU law

The standard's load-bearing role is in the citation graph. Three primary legal instruments name EN 301 549 as the technical reference; several dozen national procurement laws and accessibility statutes do the same.

The European Accessibility Act (Directive (EU) 2019/882)

The European Accessibility Act sets functional accessibility requirements for a defined list of products and services — computers, smartphones, e-readers, ATMs, ticketing machines, e-commerce, e-books, telephony, audiovisual media services, banking services, passenger transport information. The Act's functional requirements (Annex I) are abstract; they require, for example, that information be provided in accessible formats, that user interfaces support assistive technology, that emergency communications work with deaf users. To make those abstract requirements operational, the EAA relies on harmonised standards cited under Article 15 of Regulation (EU) 1025/2012 — and EN 301 549 is the harmonised standard the European Commission is using to operationalise the EAA's web, software and documentation requirements. A product that conforms to the relevant clauses of EN 301 549 carries presumption of conformity with the EAA. The first Official Journal citation of EN 301 549 specifically for EAA purposes published in 2024; revisions follow each new version.

The Web Accessibility Directive (Directive (EU) 2016/2102)

The Web Accessibility Directive, in force since December 2016, requires public-sector bodies in EU Member States to make their websites and mobile applications accessible. Article 6 of the Directive states that content meeting the harmonised standard cited in the Official Journal is presumed to conform with the corresponding accessibility requirements set out in Article 4. EN 301 549 is the standard so cited — V2 from 2018 was the first version named for WAD purposes, with each subsequent revision triggering a new OJ citation. Public-sector websites and mobile apps that meet Chapter 9 and the applicable parts of Chapter 11 are deemed compliant with the Directive.

National procurement laws and Article 42 of the Public Sector Procurement Directive

Article 42 of Directive 2014/24/EU (the Public Sector Procurement Directive) requires that technical specifications in public tenders for products and services that will be used by natural persons "take into account accessibility criteria for persons with disabilities or design for all users." Member States have implemented that obligation in their national procurement codes, and the implementing texts typically name EN 301 549 as the reference standard — from Germany's BITV 2.0 and the EU-Verordnung referenced in federal procurement, to Spain's Real Decreto 1112/2018, to France's RGAA (which aligns its criteria with EN 301 549 Chapter 9), to Italy's Linee Guida AgID, to the Netherlands' Tijdelijk besluit digitale toegankelijkheid overheid. The national-procurement layer is where EN 301 549 has the most day-to-day commercial impact, because it determines which vendors can bid for which public contracts.

What V4 changes — and what it does not

The forthcoming V4 of EN 301 549 is the working title for the revision that will incorporate WCAG 2.2 AA in place of WCAG 2.1 AA, picking up the nine success criteria the W3C added or revised in the 2023 update. The working revision has been visible in ETSI's Technical Committee Human Factors public archive since 2024, and the joint ETSI/CEN/CENELEC working group convened during 2025 to finalise it. Publication during 2026 is the working assumption inside the standards community; OJ citation under the EAA and WAD then follows on the Commission's usual timeline (typically several months after ETSI publication).

The substantive deltas in V4 cluster around two areas. First, the WCAG 2.2 success criteria themselves — Chapter 9 picks up the nine new criteria, the most operationally significant being Focus Not Obscured, Target Size (Minimum), Dragging Movements, and the two Accessible Authentication criteria, which together will force a re-audit of any product that uses overlay banners, cookie modals, password fields, or small tap targets. Second, the standard's software clauses (Chapter 11) are being tightened to align more closely with WCAG 2.2 for software where the success criteria apply, and to update the platform-accessibility-services language to reflect the assistive-technology APIs that have shipped since 2021.

What V4 does not change: the twelve-chapter architecture, the conformance-statement template in Annex A, the relationship to the EAA and WAD, or the Section 508 mapping in Annex B. A vendor that has a current conformance statement against V3.2.1 will, in most cases, need to re-test for the new WCAG 2.2 criteria but not re-architect their conformance approach.

Using EN 301 549 in practice: the conformance statement

The operational artefact that EN 301 549 produces is a conformance statement — sometimes called an "accessibility statement" in WAD usage, or a Voluntary Product Accessibility Template (VPAT) when expressed in the Section 508 lineage. Annex A of the standard contains the template. For each applicable clause, the vendor states whether the product "Supports," "Partially Supports," "Does Not Support," or "Not Applicable." Each "Partially Supports" or "Does Not Support" must be accompanied by a remarks-and-explanations field describing the gap.

In a tender response, the procurement officer scopes the relevant chapters to the product, requires a clause-by-clause conformance statement, and evaluates the gaps. The statement is contractually binding in most EU public-procurement frameworks — if the vendor declares "Supports" against a clause and the product subsequently fails on that clause during user acceptance, the contract typically gives the buyer grounds for remediation, penalties, or rescission. This is why EN 301 549 has more commercial bite than the underlying WCAG document on its own: WCAG is a W3C recommendation with no procurement standing; EN 301 549 is the document a contract names.

EN 301 549 in the legislation graph you already know

If you have followed the EU disability-rights legislation arc — the EAA, the Web Accessibility Directive, the national procurement codes that implement Directive 2014/24/EU — EN 301 549 is the technical underlay that connects those laws to a vendor's day-to-day testing process. WCAG sets the web-content rules. EN 301 549 wraps WCAG in the wider set of requirements (software, documents, documentation, hardware, two-way communications) that EU procurement law actually buys against. The EAA and WAD then cite EN 301 549 as the standard that triggers presumption of conformity. National procurement codes name the standard in their technical specifications, and accessibility auditors test against it clause by clause.

For practitioners scoping a 2026 audit: V3.2.1 is the version to test against today, V4 is the version to start preparing for, and the deltas worth getting ahead of are the nine WCAG 2.2 success criteria — particularly the focus-appearance and target-size criteria, which are the ones most products are quietly failing. The fastest way to spot which 2.2 criteria your site already trips on is a [free WCAG 2.2 scan](/toolkit/scan/) on a representative page. For the wider 2026 reporting record on how this standard interacts with national enforcement, see the Disability World article index; for the EAA's first-year enforcement picture across Member States, see the EAA primer. For a hands-on translation of V3.2.1 + the 2.2 deltas into a working audit, see the step-by-step WCAG 2.2 compliance playbook; for the monitoring platforms that maintain conformance between audits, see the accessibility monitoring buyer's guide.

Primary sources

ETSI / CEN / CENELEC. EN 301 549 V3.2.1 (2021-03) — Accessibility requirements for ICT products and services. etsi.org
European Commission. Standardisation request M/376 (2005) on ICT accessibility for public procurement.
Directive (EU) 2019/882 of the European Parliament and of the Council on the accessibility requirements for products and services (European Accessibility Act).
Directive (EU) 2016/2102 of the European Parliament and of the Council on the accessibility of the websites and mobile applications of public sector bodies.
Directive 2014/24/EU of the European Parliament and of the Council on public procurement, Article 42.
Regulation (EU) No 1025/2012 of the European Parliament and of the Council on European standardisation.
W3C. Web Content Accessibility Guidelines (WCAG) 2.1 (W3C Recommendation, June 2018) and WCAG 2.2 (W3C Recommendation, October 2023).
ETSI Technical Committee Human Factors. Public archive on EN 301 549 revision activity (2024–2025).

EPUB3 for accessible publishing: what publishers need to ship

Disability World — Fri, 22 May 2026 00:00:00 GMT

Image description: An e-reader sits on a stack of physical books with a pair of earbuds resting on top, the screen showing a page of accessible text — the everyday surfaces where EPUB3 has to work.

Reading Time: 12 minutes

EPUB3 is the format publishers will be measured against when the European Accessibility Act begins to be enforced in earnest. It is also the format that the WIPO Marrakesh Treaty and the Accessible Books Consortium use to move accessible books across borders, and the format that screen-reader users, low-vision readers and print-disabled students expect when they buy an ebook. Unlike PDF, EPUB3 is reflowable, semantic and accessible by design — but only if the publisher actually ships the metadata, the markup and the navigation that the spec calls for. A file with the .epub extension is not the same thing as an accessible EPUB.

This primer is for publishers, editorial-technology teams and accessibility leads inside ebook retailers. It walks through what the EPUB3.3 specification requires, which accessibility-metadata fields the schema.org and EPUB Accessibility 1.1 specifications expect you to populate, which reading systems actually render EPUB3 well in 2026, where the EAA compliance pressure on retailers is biting, and how the Marrakesh ecosystem rounds out the picture. It is deliberately concrete: by the end you will know what to ask your conversion vendor for, what to put in your metadata, and what to test before you upload to a retailer.

What EPUB3 requires

EPUB3 is a W3C Recommendation. The current stable version is EPUB 3.3, published as a W3C Recommendation in May 2023 after the format graduated from the IDPF into the W3C. EPUB 3.3 consolidated a series of incremental revisions, made accessibility a first-class requirement rather than an optional companion document, and tightened the relationship between EPUB and the wider open-web platform — an EPUB is, at its core, a packaged ZIP archive of HTML, CSS, SVG and supporting resources, governed by an OPF (Open Packaging Format) manifest and a navigation document.

For the file itself to be accessible, EPUB 3.3 expects publishers to use semantic HTML throughout. That means real headings in document order (h1 through h6), real lists (ul, ol, dl), real tables for tabular data with proper thead, tbody, th scoping, and the EPUB-specific structural semantics vocabulary (epub:type) for marking up chapters, sections, footnotes, page-list entries, glossary terms and the dozens of other publishing roles the spec recognises. A book whose chapter headings are visually styled paragraphs without any heading element is not accessible — a screen reader cannot jump to the next chapter, a refreshable braille display cannot announce the chapter break, and a reflow engine cannot generate a table of contents on the fly.

Language tags are non-negotiable. Every EPUB must declare a primary language in the OPF package document, and any inline content in a different language must be marked with the appropriate lang and xml:lang attributes. Text-to-speech engines and screen readers switch voice profiles on the basis of these tags; a French paragraph inside an English book that is not language-tagged will be read out in an English voice with predictably comic, and exclusionary, results. The same rule applies to direction (dir) for mixed left-to-right and right-to-left content.

Every EPUB must ship a navigation document — a single XHTML file referenced from the OPF as the navigation document, containing at minimum a table of contents (nav epub:type="toc"), and ideally a page-list (nav epub:type="page-list") mapping print-page numbers to in-book locations and a landmarks list (nav epub:type="landmarks") flagging the cover, the body matter, the index and other discoverable surfaces. The page-list is the feature that allows a student using an accessible ebook to follow the page references in a printed syllabus without falling out of sync with classmates reading the paper edition.

Images need alt text for every image that conveys content. Decorative images take alt="" and an aria-hidden="true" if appropriate, but content images — diagrams, photographs in a photography book, maps, illustrations in a children's book — need real descriptions. Complex images such as scientific diagrams need long descriptions, either inline via aria-describedby pointing to a description element, or via the epub:type="describedFootnote" pattern. Maths in any book that goes beyond casual mention should be encoded as MathML, not rasterised as PNG screenshots. MathML is the only encoding that lets a screen reader speak an equation, that lets a refreshable braille display render it in Nemeth or Unified English Braille, and that lets a reader resize the equation without pixelation.

EPUB3 also supports media overlays — synchronised text and pre-recorded audio narration, defined in SMIL files that map each text fragment to a time-range in the audio. A media-overlay EPUB lets a low-literacy reader, a reader with a cognitive disability, or simply a commuter follow the highlighted text as a human narrator reads it aloud. The SMIL approach predates the modern wave of high-quality TTS, but the two technologies are complementary: media overlays remain the gold standard for children's books, language-learning titles and accessibility-funded conversions, while TTS handles the long tail.

Accessibility metadata: the schema.org / A11y-meta layer

An accessible file that does not advertise itself as accessible is invisible to the readers who need it. The EPUB Accessibility 1.1 specification, published as a W3C Recommendation alongside EPUB 3.3, mandates a set of metadata fields that must appear in the OPF package document. These fields draw on the schema.org accessibility vocabulary — the same vocabulary used by Bookshare, the DAISY Consortium, Benetech, the Accessible Books Consortium, and the major retailer feeds.

The required and strongly-recommended properties are:

schema:accessMode — the modalities the content uses (textual, visual, auditory). A novel is textual; an illustrated children's book is textual,visual; a media-overlay audio-text book is textual,visual,auditory.
schema:accessModeSufficient — the modality combinations that are sufficient to consume the content on their own. A novel typically lists textual as sufficient (because everything important is in the text). A graphic novel without alt-text descriptions cannot honestly claim textual alone is sufficient.
schema:accessibilityFeature — the discrete features present, drawn from a controlled vocabulary: structuralNavigation, alternativeText, longDescription, tableOfContents, readingOrder, printPageNumbers, mathML, synchronizedAudioText, highContrastDisplay, displayTransformability, captions, transcript, and several more.
schema:accessibilityHazard — disclosure of any content that may trigger seizures, motion sickness or other reactions: flashing, noFlashingHazard, motionSimulation, noMotionSimulationHazard, sound, noSoundHazard. If the book is hazard-free, say so explicitly.
schema:accessibilitySummary — a human-readable, plain-language summary of the accessibility of the publication, written for the end reader: "This publication conforms to WCAG 2.1 Level AA. All images have alternative text. Mathematical equations are encoded in MathML. Page numbers reflect the print edition."
a11y:certifiedBy, a11y:certifierCredential, a11y:certifierReport — if a third party has certified the file against EPUB Accessibility 1.1, who certified it, what credential they hold, and a link to the published certification report.
dcterms:conformsTo — the conformance profile the publication meets, expressed as a URL pointing to EPUB Accessibility 1.1 conformance criteria (WCAG 2.1 Level AA, or in newer files Level AAA where claimed).

These fields are not paperwork. They flow into retailer catalogues, into the Accessible Books Consortium's global accessible-book database, into Bookshare's discovery, into school-procurement catalogues and into the EAA reporting templates that retailers now have to maintain. The European standard EN 17161 — accessibility through "design for all" — references this metadata layer, as does the Functional Accessibility Evaluation criteria used by the ACE accessibility checker maintained by the DAISY Consortium.

Reading systems: what actually renders EPUB3 in 2026

The single most quoted complaint in publisher accessibility teams is that the same EPUB renders differently on different reading systems. The complaint is true and the gap matters. A file that scores perfectly on the DAISY ACE checker may still fail to expose its navigation document on a popular consumer reader, or fail to speak its MathML on a major iOS app. The gap between what the spec defines and what the reading system implements is the reason a publisher's accessibility workflow has to include real-device testing, not just file-level validation.

Thorium Reader, maintained by the EDRLab consortium, is the reference free desktop reader for accessible EPUB3 in 2026. It implements EPUB 3.3 and EPUB Accessibility 1.1 thoroughly, exposes the navigation document, the page-list and the landmarks list, renders MathML, supports media overlays, and integrates with the operating-system text-to-speech and the major screen readers (NVDA on Windows, VoiceOver on macOS, Orca on Linux). Many publishers use Thorium as their accessibility-acceptance reader: if a file works in Thorium, it is well-formed and conformant.

VoiceDream Reader (now part of the Voice Dream stable acquired in 2022) remains the leading iOS app for print-disabled readers who want premium TTS voices and fine-grained control over speech parameters. It opens EPUB3 reliably, respects language tags for voice switching, supports custom fonts and dyslexia-friendly typography, and integrates with the Bookshare and Learning Ally catalogues. For students and adult readers with dyslexia, low vision or blindness, VoiceDream is often the default app.

VoiceOver Books — Apple's built-in audiobook experience inside the Books app, paired with iOS VoiceOver — is the route most blind iOS users actually take. It handles EPUB3 well, exposes the navigation document to VoiceOver, speaks alt text, switches voices on language tags, and surfaces media overlays. Where Apple Books still struggles is MathML rendering inside complex STEM titles and consistent exposure of the page-list when the user is navigating by print-page reference.

Apple Books on macOS, iPadOS and iOS is the broadest consumer reading system for EPUB3 in the western market and renders most accessibility features competently. Its limitations are in the long tail: certain media-overlay edge cases, certain rare MathML constructs, and inconsistent behaviour with very large page-lists.

The conspicuous exception in 2026 remains Amazon Kindle. Amazon does not natively support EPUB3 inside the Kindle ecosystem; instead it ingests EPUB and converts it on upload into its proprietary KF8 / KFX formats. The conversion preserves text, basic structure and many images, but it does not preserve all accessibility metadata, does not render MathML reliably, drops media overlays entirely, and has historically not exposed the schema.org accessibility-metadata fields to users searching the Kindle catalogue. Publishers shipping into Amazon often maintain a parallel KF8/KFX accessibility workflow, but the practical effect is that the most accessible EPUB3 a publisher can produce is partially degraded the moment it reaches the largest English-language ebook retailer. The EAA pressure described in the next section is the first regulatory lever capable of moving that needle.

EAA pressure on ebook retailers

The European Accessibility Act (Directive (EU) 2019/882) entered into application on 28 June 2025, and ebooks are explicitly inside its scope. Article 4 of the directive obliges economic operators to ensure that the products and services they place on the EU market comply with the accessibility requirements set out in Annex I. For ebooks and dedicated ebook software, the Annex I requirements include: ensuring that ebooks (and the software needed to access them) support text-to-speech, allow users to adapt presentation (font size, contrast, line spacing), expose the metadata necessary for assistive technology to navigate the content, allow synchronised audio and text where present, provide non-text content with alternatives, and prevent ebook protection measures from blocking accessibility features.

In practice, the Annex I list maps almost one-to-one onto the EPUB Accessibility 1.1 conformance criteria. A publisher that ships EPUB3 files conforming to EPUB Accessibility 1.1 — with the schema.org metadata properly populated and a certifier's statement — has a strong presumption of conformity with the Annex I obligations. A publisher shipping unstructured PDF or DRM-locked formats that block screen-reader passthrough is squarely in non-compliance.

The compliance pressure does not fall only on publishers. It falls equally on retailers, which the directive treats as economic operators in their own right. National market-surveillance authorities began their first round of EAA compliance inspections during the second half of 2025 and through 2026, and ebook retailers have been an early focus because the catalogues are public, the metadata is machine-readable and the non-compliance is easy to evidence. Retailers operating in the EU now generally require publishers to deliver EPUB Accessibility 1.1-conformant files, to populate the schema.org metadata fields, and to provide a certification statement; some have begun rejecting unconformant uploads at ingest. For platforms with significant proprietary-format dependencies — Amazon Kindle, in particular — the EAA has forced a public commitment to closer EPUB3 fidelity, though the engineering work to deliver it is still in progress.

For publishers, the operational consequence is unambiguous: ebook accessibility metadata is now a publishing requirement, not a nice-to-have. Production teams that previously ran accessibility as a separate downstream conversion now build it into the source workflow.

The Marrakesh Treaty and Accessible Books Consortium ecosystem

EPUB3 sits inside a wider treaty and infrastructure ecosystem that publishers should understand because it changes what "accessible book" means at scale. The Marrakesh Treaty — the WIPO Marrakesh Treaty to Facilitate Access to Published Works for Persons Who Are Blind, Visually Impaired, or Otherwise Print Disabled, adopted in 2013 and now in force in more than 100 contracting parties including the EU and the United States — creates a copyright exception that allows authorised entities to produce, distribute and cross-border-exchange accessible-format copies of published works for the benefit of beneficiary persons, without needing rightsholder permission for each transaction.

The Treaty is implemented in EU law via Directive (EU) 2017/1564 and Regulation (EU) 2017/1563, and in the United States via the Marrakesh Treaty Implementation Act of 2018, which amended Title 17. The operational infrastructure is run by the Accessible Books Consortium (ABC), a WIPO-led alliance of organisations representing visually impaired people, libraries serving them, publishers and standards bodies. ABC operates the Global Book Service, a cross-border lending and exchange platform through which authorised entities — typically national libraries for the blind, organisations such as Bookshare in the United States and the RNIB in the United Kingdom, and equivalent national agencies across Europe and the Global South — share accessible files.

The format of choice for these exchanges is EPUB3 with full accessibility metadata, and for older or scanned material the DAISY 2.02 and DAISY 3 formats that EPUB3 effectively succeeds. A book that a French publisher has produced as an EPUB Accessibility 1.1-conformant title can, in principle, be shared via the ABC Global Book Service with a print-disabled reader in Kenya, India, Argentina or any other contracting party, without renegotiation. The Treaty does not change the publisher's commercial position — it operates on the accessible copy specifically, for the beneficiary population specifically — but it does dramatically enlarge the reading public for any well-formed accessible ebook a publisher ships.

For publishers, the practical link between the EAA layer and the Marrakesh layer is the same metadata block. The schema.org accessibility properties, the EPUB Accessibility 1.1 conformance claim, and the certification report you produce for EAA compliance are the same artefacts that allow your file to flow into the ABC Global Book Service and the wider network of authorised entities. Ship the file once, in the right format, with the right metadata, and the same artefact serves the EU compliance regime and the global accessible-reading public at the same time.

A practical workflow for publishers

The implementation pattern that production teams settle on, once the dust clears, is built around four anchors. Source accessibility: the source manuscript is structured (real headings, real lists, real tables, language-tagged) before any conversion happens, so the EPUB conversion preserves structure rather than reverse-engineering it. Conversion to EPUB 3.3: the conversion tool — whether in-house, a vendor pipeline, or an open-source toolchain such as the DAISY Consortium's tooling — produces EPUB 3.3 with semantic markup, a navigation document, a page-list where the title has a print equivalent, alt text on all content images, MathML where mathematics appears, and media overlays where the editorial brief calls for them.

Metadata population: every file leaves production with a complete schema.org accessibility metadata block — accessMode, accessModeSufficient, accessibilityFeature, accessibilityHazard, accessibilitySummary, conformsTo — and where the title is certified, the a11y:certifiedBy/Credential/Report fields are populated against the certifier of record (commonly Benetech's certification programme, the DAISY Consortium, or a national equivalent). Validation and real-device testing: every file is validated against EPUBCheck and the DAISY ACE accessibility checker, and a representative sample is tested on Thorium, Apple Books, VoiceDream and the retailer-specific reading systems the title will be sold through.

The cost of doing this is real, but it falls quickly with practice and tooling. The cost of not doing it — EAA non-compliance fines, retailer rejection at ingest, missing readers in the Marrakesh network, and the wider reputational cost of shipping ebooks that disabled readers cannot use — is now firmly higher. EPUB3 accessibility is no longer a specialist sub-discipline at the end of the production pipeline. It is the spec.

EU AI Act Articles 16 + 73: where the high-risk AI rules intersect with disability law

Disability World — Fri, 22 May 2026 00:00:00 GMT

Image description: A printed EU AI Act document with a transparent ARIA accessibility-tree overlay and a fountain pen on top — the visual marker for the AI Act x disability law intersection.

Reading Time: 12 minutes

Regulation (EU) 2024/1689, commonly called the EU AI Act, was published in the Official Journal on 12 July 2024, entered into force on 1 August 2024, and reached its main applicability date — when the high-risk and general-purpose-AI obligations bind providers and deployers across the Single Market — on 2 August 2026. It is the first comprehensive horizontal AI law in any major jurisdiction, and it sits on top of, rather than replaces, the existing disability-rights stack: the European Accessibility Act, the Web Accessibility Directive, the Employment Equality Directive 2000/78/EC, and the EU's ratification of the UN Convention on the Rights of Persons with Disabilities (CRPD).

Two articles do most of the load-bearing work where the AI Act and disability law collide. Article 16 sets the obligations on providers of general-purpose AI models — the foundation-model layer that powers most consumer-facing AI products in 2026. Article 73, read together with Articles 8 through 15 and Annex III, sets the requirements that bind providers and deployers of high-risk AI systems. This piece is a primer on how those two articles intersect with disability law in three concrete settings: AI used in employment (CV-screening tools, automated video-interview scoring), AI used in education (online proctoring, accessibility tooling, student-risk modelling), and AI used in essential services (consumer credit scoring, healthcare triage, public-benefit eligibility decisions). It also covers the CRPD overlay that the EU's institutional commitments add on top, and the documentation duties — Annex IV technical documentation, post-market monitoring, fundamental-rights impact assessments — that vendors are now expected to produce.

What the AI Act is — and how it is structured

The AI Act is a regulation, not a directive: it applies directly in every Member State without national transposition, and the obligations it imposes on providers and deployers are uniform across the 27/27 EU national markets plus the EEA. Its core architectural choice is a risk-tier framework with four levels — prohibited practices (Article 5), high-risk AI systems (Articles 6 through 27 and Annex III), limited-risk transparency obligations (Article 50), and unregulated minimal-risk uses. Layered on top of the risk tiers, a separate regime — Articles 51 through 56 — governs general-purpose AI models, with stricter obligations triggered when a model crosses the systemic-risk threshold set in Article 51(2).

The phased applicability calendar matters because providers reading this in 2026 are not facing a single deadline. The Article 5 prohibitions on unacceptable-risk practices — social scoring by public authorities, real-time remote biometric identification in public spaces except for narrowly defined law-enforcement uses, emotion recognition in workplaces and schools — became applicable on 2 February 2025, six months after entry into force. The Article 51-56 general-purpose-AI obligations became applicable on 2 August 2025. The full high-risk regime, including the Article 73 post-market monitoring duties, came into force on 2 August 2026, with a further extension to 2 August 2027 for the subset of high-risk systems that are also safety components of products already regulated under EU product-safety legislation (Annex I sectoral law — medical devices, machinery, toys, vehicles).

Enforcement is split. National market-surveillance authorities — designated by each Member State and listed in a public register maintained by the AI Office — handle high-risk AI enforcement on the ground. The AI Office, established inside the European Commission's DG CNECT, has exclusive competence for general-purpose-AI enforcement under Article 88. Maximum administrative fines run to EUR 35 million or 7% of worldwide annual turnover for breaches of the Article 5 prohibitions, EUR 15 million or 3% for breaches of most other operator obligations including the Article 16 and Article 73 duties covered in this primer, and EUR 7.5 million or 1% for supplying incorrect or misleading information to authorities.

Article 16 — what general-purpose-AI providers must do

Article 16 is the operative provision for the foundation-model layer. It applies to providers of general-purpose AI models — defined in Article 3(63) as AI models trained on a large amount of data using self-supervision at scale, displaying significant generality, capable of competently performing a wide range of distinct tasks. The large language models powering chatbots, the multimodal image-and-text models used in document analysis, the speech models that increasingly mediate accessibility tooling: all of them are general-purpose AI models for AI Act purposes, and their providers carry the Article 16 stack.

The Article 16 duties divide into three blocks. First, technical documentation: providers must prepare and keep up to date a technical file covering the model's training, testing, and evaluation, including the training-data sources at a high level, the energy consumption of training, the evaluation benchmarks used, and the known limitations. Annex XI specifies the minimum content. Second, information disclosures to downstream deployers: providers must make available to companies that integrate the model into their own systems enough information about the model's capabilities, limitations, intended use, and known risks for the downstream operator to comply with its own AI Act obligations. Third, copyright and content-provenance: providers must put in place a policy to comply with EU copyright law, including the Article 4(3) text-and-data-mining opt-out under Directive (EU) 2019/790, and publish a sufficiently detailed summary of the training-data corpus.

The disability angle on Article 16 is twofold. First, the limitations disclosure required under Annex XI Section 1(2)(c) explicitly covers known biases and unfair performance gaps — and accessibility-relevant performance gaps fall squarely inside that requirement. A speech-recognition model that performs measurably worse on dysarthric speech, an image-captioning model that misidentifies users of wheelchairs or mobility aids, a sign-language model that fails on regional sign-language variants: each of these is a known limitation the provider must surface to downstream deployers. Second, providers of models meeting the Article 51(2) systemic-risk threshold (currently set at training compute exceeding 10^25 FLOPs) carry the additional Article 55 duties of adversarial testing, incident reporting, cybersecurity safeguards, and model evaluation against systemic-risk categories — including fundamental-rights impacts, which the regulation explicitly cross-references back to the Charter of Fundamental Rights and to the CRPD.

Article 73 — high-risk AI systems and the post-market regime

Article 73 sits inside Section 3 of Chapter III, the section that governs high-risk AI systems already placed on the market. It requires that providers of high-risk AI establish a post-market monitoring system, proportionate to the nature of the system and the risks it presents, that actively and systematically collects, documents, and analyses data on the performance of the AI system throughout its lifetime. The monitoring must continuously evaluate compliance with the requirements set out in Articles 8 to 15, with documentation kept available for at least ten years.

Article 73 has to be read in tandem with the Articles 8-15 substantive requirements, because the post-market monitoring is the mechanism by which compliance with those requirements is demonstrated over time. Article 9 mandates a risk-management system. Article 10 governs data and data-governance — specifically requiring that training, validation, and testing datasets be relevant, sufficiently representative, free of errors, and complete in view of the intended purpose, with explicit attention to "the specific geographical, contextual, behavioural or functional setting" in which the system will be used. Article 11 and Annex IV require technical documentation; Article 12 requires automatic event logging; Article 13 requires transparency and information for deployers; Article 14 requires human oversight measures designed into the system; Article 15 requires accuracy, robustness, and cybersecurity proportionate to the intended purpose. Article 26 then layers obligations on the deployer side — the operator that actually puts the system into use.

What makes a system "high-risk" is set in Article 6 and Annex III. The Annex III list names eight use-case categories — biometrics; critical infrastructure; education and vocational training; employment and worker management; access to essential private and public services; law enforcement; migration, asylum and border control; administration of justice and democratic processes — and within each category enumerates the specific use-cases that trigger the high-risk classification. The Annex III list is non-exhaustive in concept but binding in law: an AI system used for one of the listed purposes is high-risk by operation of the regulation, regardless of how the provider markets it.

Where Articles 16 and 73 intersect with disability law

Three intersection points dominate the practical compliance landscape in 2026: employment AI, education AI, and AI used in essential services. Each one sits inside an Annex III high-risk category, and each one carries a direct obligation under existing EU disability-discrimination law that the AI Act now operationalises.

Employment — CV screening, video-interview scoring, productivity monitoring

Annex III Section 4 captures AI systems used for recruitment, selection, task allocation, performance evaluation, and termination decisions. CV-screening tools that rank candidates against job descriptions, automated video-interview platforms that score candidate responses on facial expressions, speech patterns and word choice, productivity-monitoring tools that flag workers for managerial intervention based on keystroke or screen-time data: all of them are Annex III high-risk under Section 4. Article 9's risk-management duty and Article 10's data-governance duty require providers to identify and mitigate disparate-impact risks at the model-training stage. The Employment Equality Directive 2000/78/EC, in force since 2003, already prohibits direct and indirect discrimination on disability grounds in recruitment and employment; the AI Act now requires that the technical machinery behind that prohibition be auditable through the Annex IV technical file and through Article 73 post-market monitoring.

The bias-mitigation duty is explicit. Article 10(2)(g) requires that providers examine training-data design choices for "possible biases that are likely to affect the health and safety of persons, have a negative impact on fundamental rights or lead to discrimination prohibited under Union law." Once a disability-related disparate impact is identified — a video-interview model that systematically penalises candidates with speech disabilities, an HR-analytics model that misclassifies the work patterns of employees with cognitive disabilities or chronic illness — Article 10(2)(h) requires "appropriate measures to detect, prevent and mitigate" it. The mitigation work has to be documented inside the Annex IV file and continuously evaluated through the Article 73 post-market monitoring system.

Education — proctoring, accessibility tooling, risk-prediction

Annex III Section 3 covers AI used to determine access to education, evaluate learning outcomes, assess the appropriate level of education, and monitor students during tests. Online-proctoring systems that flag examination behaviour are explicitly named in the recitals. The intersection with disability law is acute here: a proctoring model trained on neurotypical baseline behaviour will systematically over-flag students with ADHD, tic disorders, or anxiety — and the under-fifteen-percent of higher-education students who have documented disabilities (Eurostat 2024) bear the disparate impact. The Article 5(1)(f) prohibition on emotion-recognition in educational settings already removes one class of model from the legal market entirely; what remains is the broader proctoring and risk-prediction layer that operates under Annex III Section 3 as high-risk.

Accessibility tooling sits on the other side of the same border. AI-driven captioning, speech-to-text for lectures, AI alt-text generation, and AI-assisted document remediation are not themselves Annex III uses — they are accessibility services. But where an educational institution procures them, the AI Act's transparency and information-disclosure duties (Article 13, Article 50) layer on top of the Web Accessibility Directive's pre-existing accessibility-statement requirement. A school deploying an AI captioning tool must publish what the tool can and cannot do, including its known accuracy gaps for accented speech, regional dialects, and signed content.

Essential services — credit scoring, healthcare triage, benefit eligibility

Annex III Section 5 covers AI used to evaluate credit scores or creditworthiness, to risk-assess pricing in life and health insurance, to evaluate eligibility for essential public benefits and services, and to dispatch or establish priority in emergency response. Each of these intersects with disability law at a different point. Credit-scoring models that use income volatility or healthcare-related spending patterns as features can encode disability-related disparate impact; healthcare-triage AI that ranks patients for treatment can replicate the same quality-of-life-adjusted bias that disability advocates have litigated against for two decades; benefit-eligibility automation in the social-security context — the Netherlands' SyRI ruling and the United Kingdom's PIP and Universal Credit algorithmic-decision cases are the contemporary canon — is now squarely inside Annex III Section 5 when used by EU public bodies.

Article 27 of the AI Act adds a fundamental-rights impact assessment duty on the deployer side for Annex III high-risk systems used by public bodies and certain private operators. The FRIA covers the categories of natural persons likely to be affected, the specific risks of harm, the human-oversight measures put in place, and the remediation routes for affected individuals. Disability is not named in Article 27, but the Charter of Fundamental Rights Article 21 prohibition on discrimination — to which Article 27 cross-refers — covers disability explicitly, and Article 26 of the Charter recognises the right of persons with disabilities to integration and participation. The FRIA is where disability impact has to be assessed before deployment, not as a retrospective audit.

The CRPD overlay

The European Union is a party to the UN Convention on the Rights of Persons with Disabilities in its own right — the first international human-rights treaty the EU has joined as a regional integration organisation — and the CRPD therefore binds the EU institutions, including in their interpretation of the AI Act. Article 9 of the CRPD obliges parties to ensure access by persons with disabilities to information and communications, including information and communications technologies, on an equal basis with others. Article 5 obliges them to prohibit all discrimination on the basis of disability and to guarantee equal and effective legal protection.

Recital 56 of the AI Act explicitly names the CRPD as part of the regulation's fundamental-rights anchorage, and the AI Office's interpretive guidance — published throughout 2025 and 2026 in the form of Q&A documents and Commission delegated acts — has repeatedly cited the CRPD in the context of accessibility-by-design obligations under Article 16 of the AI Act (information accessibility) and the disability-impact dimension of Article 27 fundamental-rights impact assessments. The practical implication: when a market-surveillance authority audits an Annex III high-risk system for disability-related disparate impact, it audits against the AI Act's data-governance and risk-management standards interpreted in light of the CRPD's non-discrimination and accessibility commitments. A provider arguing that its model performs "well on average" without addressing performance on disability-relevant subgroups is arguing against the regulation's own interpretive frame.

Practical implications for vendors and deployers

For providers of high-risk AI systems and of general-purpose AI models, the compliance architecture in 2026 has four load-bearing components. First, the data-governance file required by Article 10 — a structured record of training-data sources, representativeness analysis, identified biases including disability-relevant ones, and the mitigation steps applied. Second, the Annex IV technical documentation — design specifications, system architecture, intended purpose, known limitations, instructions for the deployer, performance metrics across demographic and disability subgroups where the data exists. Third, the post-market monitoring system under Article 73 — incident logging, complaint channels, continuous performance evaluation, periodic re-validation against the original risk-management plan. Fourth, where applicable, the fundamental-rights impact assessment under Article 27 for deployers in the public and quasi-public sector.

Early enforcement signals from the first nine months of full applicability (August 2026 onward) are limited but directionally clear. The AI Office has opened information requests against three named providers of general-purpose AI models on transparency and copyright-summary grounds. National market-surveillance authorities in the Netherlands, Germany and France have published early-guidance documents on Annex III Section 4 employment AI, all three of which explicitly call out disability disparate-impact testing as a documentation expectation. No final administrative penalty has yet been issued under Article 99 — the enforcement curve under the GDPR took approx. 18 months to produce its first material fines, and the AI Act is following a comparable trajectory. The signal to vendors is that the documentation regime is the regime: a provider that cannot show its Annex IV file, its Article 10 data-governance work, and its Article 73 post-market monitoring on request is on the wrong side of the regulation regardless of whether a fine has been issued yet.

For the disability-rights community, the AI Act does not replace the discrimination protections under Directive 2000/78/EC, the accessibility requirements under the European Accessibility Act, or the procurement criteria under EN 301 549 — it sits on top of them and gives them a documentation and oversight architecture that the existing instruments lacked. The next wave of enforcement, expected through 2027 and 2028, will be where the interplay between the AI Act's procedural duties and the existing substantive disability-discrimination doctrine produces the case law that defines what bias-mitigation actually looks like in practice. This primer is the map of the terrain; the cases will draw the contour lines.

European Accessibility Act guide — EAA & Directive 2019/882

Disability World — Fri, 22 May 2026 00:00:00 GMT

Editorial · EU regulatory requirements

The European Accessibility Act: what it actually requires of private companies

Directive (EU) 2019/882 — the European Accessibility Act, or EAA — was adopted on 17 April 2019, required Member-State transposition by 28 June 2022, and bound covered economic operators from 28 June 2025. Six years from adoption to applicability is a long runway, but the substantive obligations behind it are now in force across all 27/27 Member States. This is a requirements-side dossier — what the Directive covers, which products and services are caught, what technical standard the conformity presumption rests on (EN 301 549 V3.2.1, which incorporates WCAG 2.1 Level AA), and which two structural escape valves exist: the microenterprise carve-out for service providers under 10 staff or €2M turnover, and the disproportionate-burden defence in Article 14 with its five-year documentation requirement. Year-one enforcement is covered in a companion piece; this article is about what the law asks of private companies, on paper.

Findings · Case file EAA-REQ 07 entries · derived from Directive (EU) 2019/882, EN 301 549 V3.2.1, and national transposition acts

What the EAA actually requires of private companies

01 6 + 8

Six product categories and eight service categories fall inside the Directive's substantive scope

Products: general-purpose computers, smartphones, smart-TV consumer equipment, self-service terminals (ATMs, ticketing, check-in kiosks), consumer banking terminals, e-readers. Services: consumer banking, electronic communications, e-commerce, e-books and dedicated software, audio-visual media access components, transport e-ticketing and information services, and emergency communications via 112.
02 WCAG 2.1 AA

The harmonised technical reference is EN 301 549 V3.2.1, which incorporates WCAG 2.1 Level AA

Annex I sets functional requirements as outcomes. Conformity with the harmonised standard creates a presumption of conformity with Annex I — it does not replace it. Annex II provides non-binding examples of how the functional requirements can be met.
03 28 Jun 2025

The substantive applicability date is 28 June 2025 — three years after transposition, six after adoption

A grandfathering window runs to 28 June 2030 for services using products lawfully placed on the market before 2025, and to 28 June 2045 for self-service terminals already in operation at the applicability date — but only until the end of their economic life.
04 < 10 / €2M

The microenterprise exemption — services-side only — covers undertakings under 10 staff OR under €2M turnover

Article 4(5) exempts microenterprises from the services-side requirements (Annex I Section IV). It does not extend to products. The carve-out is automatic — no application or assessment — but it is also a single-jurisdiction concept; a cross-border platform is a microenterprise nowhere as soon as it crosses either threshold.
05 Art. 14 · 5 yr

The disproportionate-burden defence in Article 14 carries the burden of proof and a five-year documentation requirement

Operators must self-assess against the criteria in Annex VI (size and resources of the operator; estimated costs and benefits to disabled persons). Documentation must be retained for inspection for five years and updated whenever the affected product or service is materially altered.
06 Art. 30

Penalties are set by each Member State and must be "effective, proportionate and dissuasive"

The Directive sets no harmonised floor or ceiling. In practice the published ceilings span two orders of magnitude — from €5,000 per violation in Estonia and Slovenia to approximately €1 million in Spain (Ley 11/2023), with turnover-percentage tiers up to 5% of annual turnover in Italy.
07 CE

Products require a CE marking and an EU Declaration of Conformity; services require an accessibility statement

Annex IV sets the products-side conformity-assessment procedure (internal production control / Module A). Services-side operators do not affix a CE marking but must publish an accessibility statement covering how the service meets Annex I and how to contact the provider on accessibility matters.

SourceDirective (EU) 2019/882, OJ L 151, 7.6.2019; Annexes I, IV, VI; ETSI EN 301 549 V3.2.1; national transposition acts referenced in the body of this article.

In this dossier

01What the EAA is, in one paragraph
02The six product and eight service categories
03EN 301 549, WCAG 2.1 AA, and the presumption of conformity
04The 2019–2045 timeline
05The microenterprise carve-out
06The Article 14 disproportionate-burden defence
07National penalty regimes
08What private companies must actually do
09What the Directive is asking of private capital
10Sources

What the EAA is, in one paragraph

The European Accessibility Act is a directive — not a regulation — adopted under Article 114 of the Treaty on the Functioning of the European Union, the internal-market legal basis. It harmonises Member-State accessibility requirements for a defined list of products and services placed on the EU market, so that an e-reader, a banking interface, or an e-commerce checkout designed for the German market does not have to be re-engineered for the Spanish market because the underlying accessibility obligations diverge. The legislative pose is single-market: by setting one outcome standard at EU level, the Directive removes the patchwork of national accessibility rules that had grown up around products and services since the 2000s. The accessibility benefit is the consequence; the legal mechanism is harmonisation.

The Directive's full title is the most accurate description of what it does: Directive (EU) 2019/882 of the European Parliament and of the Council of 17 April 2019 on the accessibility requirements for products and services. Published in the Official Journal of the European Union as OJ L 151 on 7 June 2019, it required transposition into national law by 28 June 2022 and binds covered economic operators from 28 June 2025. The applicability date — not the transposition date — is the moment at which the Directive's substantive obligations attach to private companies. For a company placing covered products on the EU market or providing covered services to EU consumers, 28 June 2025 is when the law actually starts asking questions.

One crucial framing: the Directive is a private-sector instrument. The public-sector accessibility regime — websites and mobile applications of public-sector bodies — is governed by the Web Accessibility Directive (EU) 2016/2102, which has been in force since 2018 and uses a similar but distinct technical reference. A company should not assume that compliance with 2016/2102 means compliance with 2019/882, or vice versa: the two regimes overlap on the WCAG floor but diverge on the conformity-assessment apparatus, the penalty architecture, and the exemption regime.

The six product and eight service categories

The EAA covers six product categories and eight service categories. The grid above is the consumer-facing slice — the everyday surfaces where the Directive most often touches a private company's product roadmap.

The Directive's substantive scope is set in Article 2 and detailed in Article 3. The list is closed: a product or service not on the list is not covered, regardless of how interactive or consumer-facing it is. This is the first question a compliance team asks, and it is also the most-misread question in the first wave of EAA coverage. The Directive does not cover "all digital products." It covers a specific, enumerated list.

Products in scope (Article 2(1))

General-purpose computer hardware systems and their operating systems, including desktop computers, laptops, and the operating-system software that ships with them.
Self-service terminals — payment terminals at point of sale, ATMs, ticketing machines (rail, air, road), check-in kiosks (airports, hotels) and interactive self-service kiosks providing information about covered services.
Consumer terminal equipment with interactive computing capability for electronic communications services — smartphones, tablets with cellular connectivity, modems, routers.
Consumer terminal equipment with interactive computing capability for accessing audio-visual media services — smart TVs, set-top boxes, streaming devices.
E-readers. Dedicated e-book reading devices, regardless of operating system.
Banking-services terminals. Specific consumer-banking hardware not already caught under self-service terminals (point-of-sale terminals dedicated to consumer banking transactions).

Services in scope (Article 2(2))

Consumer banking services, including current accounts, payment services, credit-card transactions, consumer credit, and the public-facing interfaces (online banking portals, mobile-banking apps, ATMs as a service surface) through which they are delivered.
Electronic communications services — internet access, voice services, messaging services, and the customer-facing interfaces used to subscribe to and manage them.
Services providing access to audio-visual media services, including the electronic programme guides (EPGs) and the customer-facing interfaces of streaming and broadcast platforms — but not the audio-visual content itself, which is governed by the Audiovisual Media Services Directive (EU) 2018/1808.
Air, bus, rail, and waterborne passenger transport services — limited to specific service elements: websites, mobile-device-based services including mobile applications, electronic ticketing, real-time travel information, and self-service terminals located within the EU territory.
Consumer e-commerce services. Services provided through websites or mobile applications, allowing consumers to conclude a contract with a trader for the supply of products or services. This is the scope category that catches the largest number of private companies.
The European single emergency number 112. Communications to and from the 112 service must be accessible.
E-books and dedicated software — the electronic publication file itself, the reading device's software, and the service through which the e-book is acquired and managed.

Two categories deserve careful reading. Audio-visual media access components covers the interface to AV services — not the AV content. Whether a Netflix show ships with audio description is a question for the Audiovisual Media Services Directive; whether the Netflix app's sign-up flow is keyboard-navigable is a question for the EAA. Transport services are covered only on their digital surfaces (websites, apps, ticketing kiosks, real-time information); the physical accessibility of stations, rolling stock, and aircraft remains governed by the relevant transport-mode regulations (Regulation (EU) 1300/2014 for rail, Regulation (EU) 181/2011 for bus, Regulation (EC) 1107/2006 for air passengers with reduced mobility).

What's not in scope — and why it matters

The Directive's closed list excludes large categories of digital activity. Workplace software, internal business tools, business-to-business platforms not sold to consumers, gaming, social-media platforms, search engines, and information-only websites that do not allow the user to conclude a contract — none of these are caught by the EAA. Some Member-State transposition acts have extended the national scope (the German [BFSG](/regulations/de/) covers a narrower scope than some had expected; the Spanish Ley 11/2023 covers approximately the Directive's list). A business operating across the EU must check the national transposition act in each Member State of operation for scope, not the Directive alone.

The Directive applies to economic operators — manufacturers, importers, distributors, service providers — regardless of where they are established, provided they place products on the EU market or provide services to EU consumers. A US-headquartered e-commerce platform selling to French consumers through a French-language site is a "service provider" under the Directive in the same way as a Paris-headquartered retailer. The territorial question is the market, not the seat.

EN 301 549, WCAG 2.1 AA, and the presumption of conformity

The Directive itself does not contain a literal accessibility specification. Annex I sets out functional requirements as outcomes — for example, that information is provided "through more than one sensory channel," that "the user interface elements are operable through more than one input mode," that "user interface elements include adaptive techniques that account for assistive technology requirements." These are outcomes a designer can engineer toward but cannot mechanically check against. The Directive's mechanism for closing that gap is the harmonised standard: a technical specification developed by a European Standards Organisation (in this case ETSI, the European Telecommunications Standards Institute) and referenced by the European Commission via Implementing Decision.

The referenced harmonised standard is ETSI EN 301 549 V3.2.1, originally published in March 2021 and referenced by the Commission in 2024–25 for EAA conformity-assessment purposes. The standard incorporates the W3C's [Web Content Accessibility Guidelines (WCAG) 2.1 Level AA](/toolkit/standards/wcag/) for the digital-content layer, and adds requirements covering hardware, ICT with two-way voice communication, ICT with video capabilities, web-based authoring tools, and assistive-technology compatibility for products outside the web-only scope.

The legal effect of the harmonised standard is the presumption of conformity set out in Article 15 of the Directive. A product or service that conforms to EN 301 549 V3.2.1 is presumed to conform to the Annex I functional requirements — meaning a market-surveillance authority that wants to challenge that conformity carries the burden of demonstrating that the standard does not, in fact, deliver the outcome the Annex requires. Conversely, a product or service that does not follow the harmonised standard is not automatically non-conformant: the operator may demonstrate, by another route, that the Annex I outcomes are met. The harmonised standard is a safe harbour, not a literal incorporation.

EN 301 549

Harmonised standard referenced by the Commission

V3.2.1

Current referenced version (March 2021)

WCAG 2.1 AA

Web-content layer inside V3.2.1

For most service providers in the e-commerce, banking, electronic-communications, and audio-visual-access categories, the practical compliance question reduces to: does our customer-facing website and app pass WCAG 2.1 Level AA, with the EN 301 549 additions for any hardware or two-way-communication interfaces we operate? That is the question the standard answers — and the question the first wave of national enforcement actions has implicitly asked. The Directive's drafters were careful to keep the legal obligation pitched at the outcome level (Annex I) precisely so that the underlying technical standard could be updated without re-opening the Directive. EN 301 549 V4, incorporating WCAG 2.2, is in late-stage drafting at ETSI as of mid-2026 and is expected to be referenced by the Commission within 18 months, at which point V4 conformity becomes the relevant safe harbour.

The Directive sets functional outcomes; the harmonised standard sets the engineering. A company designs to the standard, complies with the Directive.

The 2019–2045 timeline

The Directive's transitional architecture is more nuanced than the headline "28 June 2025" date suggests. Four dates matter to compliance teams.

0117 April 2019 — AdoptionDirective (EU) 2019/882 adopted by the Parliament and the Council, published in OJ L 151 on 7 June 2019.

0228 June 2022 — Transposition deadlineMember States must have brought into force the laws and regulations necessary to comply with the Directive.

0328 June 2025 — ApplicabilitySubstantive obligations attach to covered economic operators. Products placed on the market and services provided to consumers from this date forward must comply.

0428 June 2030 — Services grandfatherService providers may continue providing services using products lawfully used to provide similar services before 28 June 2025 until 28 June 2030. Self-service terminals lawfully used before 28 June 2025 may continue to be used until the end of their economic life — but not later than 20 years (28 June 2045).

The grandfather provisions in Article 32 are important and frequently misread. A bank that operated an ATM estate on 27 June 2025 does not have to retrofit every existing machine the next day; it may continue to use those machines until they reach the end of their economic life, up to a hard cap of 28 June 2045. Any new machine deployed from 28 June 2025 forward must be compliant. The same logic applies, on a shorter clock, to service providers using product infrastructure: legacy product infrastructure may be used in service provision until 28 June 2030, but new product infrastructure deployed from 2025 forward must be compliant from day one.

The grandfather is a one-way ratchet on the products side: it does not protect the digital surface of a covered service. A bank's mobile app, a retailer's checkout flow, an audio-visual platform's sign-up page — these are services and have been bound by the substantive requirements since 28 June 2025, regardless of when the underlying codebase was first deployed. The grandfather covers the hardware estate, not the web estate.

The microenterprise carve-out

Article 4(5) of the Directive contains the most-discussed exemption: microenterprises providing services are exempt from the services-side requirements. The microenterprise definition is the standard one used across EU instruments — an undertaking employing fewer than 10 persons and with an annual turnover or annual balance-sheet total not exceeding €2 million. The thresholds are alternative on the financial side (turnover OR balance sheet) and cumulative across that and the headcount (under 10 staff AND under €2M).

The carve-out has three properties worth flagging for any company sitting near the threshold:

Services-side only. Article 4(5) does not extend to the products side of the Directive. A small-volume hardware manufacturer with 6 staff faces the same conformity-assessment regime — internal production control, CE marking, EU Declaration of Conformity — as a multinational. The asymmetry is a deliberate trade-off between cost-of-compliance and conformity overhead, but it surprises every small hardware company that encounters it.
Automatic, not declared. A microenterprise does not apply for the exemption; it simply falls outside the services-side scope. National transposition acts may require a microenterprise to provide information to authorities on request, or to publish a brief notice, but the substantive carve-out is automatic.
Crossing the threshold is forward-looking. Once an undertaking crosses 10 staff or €2M turnover, it becomes subject to the services-side requirements from the next financial period. The Directive does not require retrospective compliance for periods during which the undertaking was a microenterprise.

The cross-border microenterprise trap

Microenterprise status is computed at the level of the undertaking — not per Member State. A platform with 6 staff and €1.5M turnover across the EU is a microenterprise. A platform with 6 staff and €1.5M of turnover in France but €1M of turnover in Germany and €1M in Spain is not a microenterprise: total turnover is €3.5M, well above the threshold. Cross-border platforms cross the threshold faster than national platforms, and there is no per-jurisdiction relief.

The "linked enterprises" rule under Commission Recommendation 2003/361/EC also matters: an undertaking controlled by a larger group counts the group's headcount and turnover, not just its own. A nominally small subsidiary of a multinational does not qualify for the carve-out.

The exemption has been the subject of intense small-business federation lobbying in several Member States, with proposals to raise the threshold or to broaden it to the products side. None of those proposals have, as of mid-2026, found their way into national transposition acts. The Commission's 2030 review will revisit the carve-out — Article 33 requires the Commission to assess "the impact on microenterprises providing services" as part of the review.

The Article 14 disproportionate-burden defence

The second structural escape valve is Article 14 — the disproportionate-burden defence. Unlike the microenterprise carve-out, which is automatic and structural, Article 14 is a self-assessment route available to any covered operator. An operator may invoke the defence to argue that a specific accessibility requirement — not the whole regime — would impose a disproportionate burden, after balancing the cost of compliance against the benefit to disabled persons. The criteria for the assessment are set out in Annex VI.

Three features of the defence determine whether it is practically available to a given operator.

The burden of proof sits on the operator

An operator that invokes Article 14 must conduct the assessment, document it, and retain the documentation for inspection. The Annex VI criteria are: (a) the ratio of net costs of compliance to the overall costs (capital and operating expenditure) of manufacturing, distributing or importing the product or providing the service; (b) the estimated costs and benefits for the operator, including production processes and investments, in relation to the estimated benefit for persons with disabilities, taking into account the frequency and duration of use of the specific product or service; (c) the size, resources and nature of the operator. A small operator with limited resources has more headroom under (c) than a multinational; an operator providing an infrequently-used service has more headroom under (b) than one providing a daily-use service.

The documentation must be retained for five years

Article 14(8) requires operators to keep the disproportionate-burden assessment available for inspection by market-surveillance authorities for five years after the product was last made available on the market, or the service was last provided. The documentation must be updated when the product or service is materially altered, when the market-surveillance authority so requests, or when an applicable harmonised standard is updated. A defence without contemporaneous documentation is not a defence — authorities have, in the first year of enforcement, treated absent documentation as decisive against the operator.

It is granular, not platform-wide

Article 14 applies to specific accessibility requirements, not to whole platforms. An e-commerce operator cannot invoke the defence to argue that running an accessible checkout is, as a whole, disproportionately burdensome. The operator may, with documentation, argue that a particular requirement — for example, providing audio description on archived video product demonstrations published before a certain date — is disproportionate in the specific context. The first year of national enforcement has confirmed this reading: the defence has succeeded for narrow legacy-feature carve-outs and failed when invoked to cover an entire platform surface.

The five questions Article 14 documentation must answer

National guidance issued by the German BMAS, the Dutch RDI, and the French DGCCRF during 2025–26 converges on a five-question template for Article 14 documentation, all derived from Annex VI: (1) Which specific accessibility requirement is being assessed? (2) What is the estimated net compliance cost, broken out from baseline product or service cost? (3) What is the estimated population of disabled persons benefited, and the frequency of use? (4) What is the cost-to-benefit ratio relative to the operator's size and resources? (5) What is the planned re-assessment trigger — material alteration, standards update, or fixed date? Any Article 14 file missing one of these five elements is, in practice, treated as incomplete by surveillance authorities.

One important interaction: Article 14 cannot be used to claim a disproportionate burden when the operator receives external funding for accessibility improvements from sources other than its own (EU, public, or private accessibility-improvement funds). The criterion is built into Annex VI directly — an operator drawing on a national digital-accessibility grant programme cannot also claim disproportionate burden on the funded feature.

National penalty regimes

Article 30 of the Directive sets the penalty principle — penalties must be "effective, proportionate and dissuasive" — and leaves the absolute architecture to Member-State legislatures. This is the single largest source of operational unevenness across the Single Market. The transposition acts adopted between 2021 and 2025 have produced penalty schedules that differ by two orders of magnitude.

Top per-violation penalty ceilings under selected Member-State EAA transposition acts, mid-2026.
Member State	Transposition act	Top per-violation ceiling
Germany	Barrierefreiheitsstärkungsgesetz (BFSG, 2021)	€100,000
France	Loi n° 2005-102, RGAA implementing decrees (2023)	approx. €75,000
Netherlands	Implementatiewet toegankelijkheidsvoorschriften (2022)	approx. €87,000
Spain	Ley 11/2023	up to €1,000,000
Italy	D.lgs. n. 82/2022 (Stanca Law extension)	up to 5% of turnover
Estonia	Toodete ja teenuste ligipääsetavuse seadus (2022)	€5,000–€32,000
Slovenia	Zakon o dostopnosti proizvodov in storitev (2022)	€10,000–€40,000

The spread matters for at least three reasons. First, it shapes the deterrence calculus differently in each Member State: an operator weighing whether to litigate a marginal disproportionate-burden claim faces very different downside scenarios in Madrid and Tallinn. Second, it creates a forum-selection question for cross-border enforcement: which authority will take the lead when a non-EU platform fails on multiple Member-State surfaces simultaneously? Third, it is itself a single-market problem the Commission's 2030 review is expected to address — Article 33 explicitly requires the Commission to assess "the effectiveness, proportionality and dissuasiveness" of national penalty regimes.

For requirements-side compliance planning, the practical implication is that an operator cannot model a uniform EU compliance budget against a single penalty ceiling. The most-exposed jurisdiction will tend to drive the planning horizon, and the most-exposed jurisdiction is not always the largest market. A multinational e-commerce operator with disproportionate Spanish or Italian revenue concentration will be planning to a different worst-case than one with German-Dutch concentration. (For a complete first-year enforcement picture — penalty resolutions issued, scan-rate trajectories, cross-border action — see our companion piece, EAA first year: enforcement, penalties, and the compliance-rate trajectory across the EU 27.)

What private companies must actually do

The Directive distinguishes four classes of economic operator and assigns each a distinct set of obligations. A single company can be more than one of these at once.

Manufacturers (Art. 7)

Importers (Art. 9)

Distributors (Art. 10)

Service providers (Art. 13)

Manufacturers (Article 7) must design and manufacture products in accordance with Annex I, draw up the technical documentation set out in Annex IV, carry out the internal-production-control conformity-assessment procedure (Annex IV again — Module A), draw up an EU Declaration of Conformity, affix the CE marking, and indicate their name and contact address on the product. They must keep the technical documentation and the Declaration of Conformity for five years after the product was placed on the market.

Importers (Article 9) must verify before placing a product on the market that the manufacturer has carried out the conformity-assessment procedure, that the technical documentation has been drawn up, that the product bears the CE marking, that it is accompanied by the required documents, and that the manufacturer has complied with the labelling requirements. Importers indicate their own name and contact address on the product, in a document accompanying the product, or, where this is not possible due to size or nature, in another appropriate way.

Distributors (Article 10) must verify that the product bears the CE marking, is accompanied by the required documents, and that the manufacturer and importer (if any) have complied with the identification requirements. Distributors do not have to repeat the conformity assessment; they are quality-gates rather than testers.

Service providers (Article 13) are the largest cohort. They must design and provide services in accordance with the Annex I functional requirements; prepare the information required by Annex V (the accessibility statement), make it publicly available in a form accessible to persons with disabilities, and keep it for as long as the service is in operation; ensure procedures are in place to maintain the accessibility of the service through changes in service characteristics, applicable harmonised standards, and applicable Member-State law; and provide information on how compliance with the accessibility requirements has been ensured, in case of non-conformity, in a manner that allows competent national authorities to verify it.

Directive (EU) 2019/882, Article 13(2)

"Service providers shall prepare the necessary information in accordance with Annex V and shall explain how the services meet the applicable accessibility requirements. The information shall be made available to the public in written and oral format, including in a manner which is accessible to persons with disabilities."

— OJ L 151, 7.6.2019, p. 96

The most under-attended duty in the first year of compliance has been the accessibility statement. Annex V requires service providers to publish a document that describes the service's general accessibility characteristics, the accessibility requirements it meets, and — where Article 14 has been invoked — the specific requirement that has been judged disproportionately burdensome and the assessment supporting that judgment. The accessibility statement is the operator's public-facing position on its EAA compliance. A missing statement is one of the easiest non-conformities for a market-surveillance authority to identify.

What the Directive is asking of private capital

Read end to end, the EAA is a single-market instrument that takes accessibility seriously as a competition matter. The case the Directive's drafters made in 2019 — and which the recitals lay out at length — is that fragmented national accessibility rules were imposing a deadweight cost on cross-border trade in consumer products and services, and that a harmonised outcome standard removes that cost without compromising the substantive accessibility benefit. The benefit accrues to disabled persons; the cost saving accrues to the Single Market. Both are real, and the Directive's design assumes they reinforce one another.

For private companies, the operational reading is more grounded. The Directive demands four things, in order: (1) an honest scope determination — which products and services are caught, in which Member States; (2) an honest engineering determination — whether the customer-facing surface meets EN 301 549 V3.2.1 today, and whether it will meet V4 (WCAG 2.2) when that becomes the reference (a [free WCAG 2.2 scan](/toolkit/scan/) is the cheapest way to establish that baseline); (3) a documentation discipline — an accessibility statement under Annex V for services, technical documentation under Annex IV for products, and an Article 14 file for any feature where the defence is invoked; and (4) a maintenance commitment — accessibility is not a one-time conformity event, it is a property of the platform that must be preserved through every release cycle.

The Directive's mechanism is deliberately undramatic. It does not name brands, does not single out sectors, does not impose a public reporting regime. It sets an outcome at EU level, leaves the enforcement architecture to Member States, and waits to see what the market does. The companies that have approached the Directive as a single-market harmonisation programme — engineering once, deploying everywhere — have found it manageable. The companies that have approached it as a national-compliance problem in 27 jurisdictions have found it expensive. The Directive's drafters bet that, over time, the first reading will prevail. The first year of applicability suggests they were right.

For teams putting an EAA-conformant posture into practice: the step-by-step WCAG 2.2 compliance playbook covers audit, remediation and ongoing monitoring; the accessibility monitoring buyer's guide compares the platforms organisations use to maintain that posture; the manual-audit guide covers the human-review layer Article 14 effectively presumes; and the accessibility compliance explainer routes between EAA, ADA and the rest of the regulatory map.

Eye-tracking, head-pointer, and switch input on the modern web

Disability World — Fri, 22 May 2026 00:00:00 GMT

By Disability World Reading time: 9 minutes

A click on the modern web hides an assumption: that the person clicking has a hand, a wrist, and a pointing device that moves on two axes with sub-pixel precision and a separate, reliable button for the press. Strip any one of those out and the encounter changes. For someone driving the page with an eye-tracker, the "cursor" is a 1-degree-of-arc gaze cone that drifts and jitters. For someone using a head-pointer, the cursor is a webcam-tracked nose-tip with a slow dwell-to-click. For someone using a single-switch scanning interface, there is no cursor at all — only a sweeping highlight that lands on whatever happens to be focused when the user presses the switch. Each of these is a real input modality used today, in 2026, by a population large enough that "the modern web" should know about them. Most of the modern web doesn't.

This piece is a concept primer on the three alternative input modalities that motor-disabled users most often rely on — eye-tracking, head-pointing, and switch input — and on how the standards layer (the WCAG 2.2 success criteria, the W3C Pointer Events specification) intersects with the user-interface patterns that actually appear in production. The reporting frame is editorial rather than litigation-driven: we are looking at what works, what doesn't, and what designers can stop doing tomorrow.

Who uses these inputs, and why

The population that depends on alternative input modalities is not small. Estimates from the WHO Global Report on Health Equity for Persons with Disabilities (2022, with the 2024 monitoring update) and from the US CDC's Disability and Health Data System place the share of adults with a significant upper-limb motor impairment at roughly 8% of the adult population in high-income countries, and the share of adults who cannot reliably use a standard mouse or trackpad at roughly 3-4%. Inside that 3-4% sit several distinct user groups whose preferred input modality is shaped by their physiology more than by their preference.

The clearest group is people with amyotrophic lateral sclerosis (ALS), who progressively lose voluntary control of their limbs and, eventually, of their facial musculature. Eye-gaze tracking is, for many people with advanced ALS, the only remaining channel for autonomous computer use. The ALS Association estimates that approximately 30,000 people are living with ALS in the US at any given time; the European ALS register suggests a similar age-adjusted prevalence across the EU. The second group is people with high-level spinal cord injury — particularly C1-C4 tetraplegia — for whom hands and arms are unavailable but eye and head motion are preserved. The third is children and adults with cerebral palsy, where the input strategy is highly individual: some users have enough finger control for a switch interface, others use a head-pointer, others a chin-driven joystick. The fourth is people with progressive neuromuscular conditions — muscular dystrophy, multiple sclerosis at later stages — who often transition through several input modalities over time.

Across these groups, two principles cut through the variability. First, almost everyone who uses an alternative input does so because the standard mouse-and-keyboard combination has become physically impossible, not because they prefer a novel modality. Second, the input is usually single-axis in some load-bearing sense: a single gaze fixation, a single head-pointing direction, a single switch press. Designs that assume two coordinated channels — a pointer plus a modifier key, a drag motion plus a precise drop target — collapse hardest for this audience.

The hardware, in 2026

The hardware landscape has shifted noticeably in the last three years. What follows is a rough map of what users are actually running, rather than a complete catalogue.

Eye-trackers

Tobii Dynavox remains the dominant clinical eye-gaze vendor. The current generation — the PCEye and the I-Series — uses an infrared sensor bar mounted below a monitor or integrated into a dedicated tablet, and reports gaze position to the host operating system as a system-level pointer. Calibration takes roughly 30 seconds; precision under good conditions sits around 0.5-1.0 degrees of visual arc, which translates to a gaze cone of approximately 30-60 pixels across at a typical viewing distance. EyeGaze Edge (LC Technologies) and EyeTech VT3 are clinical alternatives. On the consumer side, Tobii Eye Tracker 5 is sold primarily to gamers but is widely used as a low-cost accessibility input.

2024 brought the first mainstream consumer-grade eye-tracking integrated into a general-purpose computing device: the Apple Vision Pro ships with eye-gaze as the primary navigation modality, combined with a pinch gesture for selection. visionOS exposes the gaze position to system-level dwell-selection accessibility features, and from the developer's point of view a gaze fixation followed by a pinch is reported as a standard click event. The accessibility population has, predictably, embraced visionOS for the same reason it embraced the iPhone in 2008: a built-in modality designed for mainstream use that happens to also serve the disability use case. The Vision Pro's price point puts it out of reach of many users, but the precedent — eye-gaze as a primary input on a non-medical-device computer — is the precedent that matters.

Head-pointers

Head-pointer software typically uses the device's built-in webcam to track a fiducial point — often the nose tip or a small reflective sticker placed on the user's forehead — and translates head rotation into cursor motion. Camera Mouse (Boston College, free) is the longest-running implementation and remains in active use. Glassouse ships a wearable head-mounted gyroscope-based controller that pairs with the operating system as a Bluetooth mouse. macOS includes Head Pointer as a built-in accessibility feature; Windows 11 has equivalent functionality through Eye Control when paired with compatible hardware. Selection on a head-pointer is almost always dwell-based: the cursor hovers on a target for a configurable interval — typically 0.5 to 2.5 seconds — and a click event fires.

Switch input

Switch input is the simplest and the most variable of the three. The hardware is a single button — a large round mechanical switch, a sip-and-puff tube, a chin-operated lever, a foot pedal, a brain-computer interface in late-stage research — wired into a standardised switch interface (an AbleNet Hook+, a Pretorian J-Pad, a Tecla shield) that presents itself to the operating system as a USB or Bluetooth keystroke. The software then runs a scanning interface: a focus indicator moves automatically through the available targets on the screen, and the user presses the switch when the focus lands on the target they want. Single-switch scanning is one button driving everything; two-switch scanning typically maps one switch to "advance" and the other to "select." iOS includes Switch Control as a built-in accessibility feature; Android 14+ ships Switch Access; macOS and Windows both ship comparable functionality. Switch input is fundamentally serial — the user cannot point at a target; they can only wait for the scan to reach it — and that fact shapes every design pattern below.

How they meet the web: the standards layer

From the browser's point of view, an eye-tracker and a head-pointer both look like standard pointing devices: they emit pointermove, pointerdown, and pointerup events through the W3C Pointer Events specification, the same API a mouse or a touchscreen uses. Switch input, by contrast, looks to the browser like keyboard input: focus traverses tabbable elements, and the switch press fires a keydown event for Enter or Space. That divergence is the first thing a designer has to internalise — eye-gaze users hit your :hover states and your pointer-event handlers; switch users only ever encounter your keyboard-focusable elements and the focus order you defined.

WCAG 2.2 contains several success criteria written specifically to keep these input modalities working. Three of them carry most of the weight.

SC 2.1.1 Keyboard (Level A) is the foundational requirement: every functional element on the page must be operable through a keyboard interface alone. Switch users depend on this absolutely. An element that only responds to a mouse click — a custom div with a click handler and no tabindex, no role, no keydown handler — is invisible to a switch user. It is also invisible to many head-pointer users who fall back to keyboard navigation for sections of the page where dwell-clicking is too slow.

SC 2.5.1 Pointer Gestures (Level A) requires that any function operated by a multi-point or path-based gesture also be operable with a single-pointer action. The criterion exists because eye-gaze, head-pointer, and many alternative inputs cannot reliably perform multi-finger gestures or precise drag paths. A pinch-to-zoom that has no alternative button. A swipe-to-delete that has no on-screen delete control. A drag-to-reorder list that has no keyboard equivalent. Each of those is a 2.5.1 failure, and each one cuts off the modality the user actually has.

SC 2.5.2 Pointer Cancellation (Level A) requires that for any single-pointer activation, the action either does not execute on the down-event (it executes on up-event instead), or executes on the down-event but allows the user to abort the action by moving away before the up-event. The criterion is written for users who hit the wrong target with a tremor or a drift, and it matters intensely for dwell-based head-pointer and eye-gaze interfaces: a click that fires the instant the cursor lands gives the user no chance to recover from a gaze drift. Buttons that bind their handler to mousedown rather than click fail this criterion.

SC 2.5.7 Dragging Movements (added in WCAG 2.2) extends the gesture protection to drag-and-drop specifically: anything draggable must also be reachable through a single-pointer alternative, typically a button-driven move-up/move-down control. SC 2.5.4 Motion Actuation (Level A) protects users who cannot reliably shake or tilt their device. And SC 2.2.1 Timing Adjustable (Level A) and SC 2.2.2 Pause, Stop, Hide (Level A) protect everyone from interfaces that time out before a scanning interface can reach the relevant control.

These criteria are written as a single, integrated frame: the user has only one input axis, the input is slow, and the design must not assume otherwise.

Common breakage on production sites

Set those criteria against what production sites actually ship and a recurring set of failure patterns emerges. None of these are exotic. All of them appear in routine user testing with eye-tracker, head-pointer, and switch users.

Drag-and-drop with no keyboard alternative. A common pattern in project-management tools, file managers, and ranked-list interfaces: drag a card from one column to another. For switch users the action is impossible — there is no drag in scanning. For head-pointer and eye-gaze users the drag itself is approx. 4-5x slower than a button-driven move and is usually impossible to complete without dropping the item mid-motion. The fix is straightforward: pair every drag-and-drop with a button-driven move action, exposed in the keyboard tab order. The Trello-style "move card up / move card down / move to another list" menu pattern is the reference implementation.

Hover-only navigation. Dropdown menus, tooltips, and disclosure controls that appear only on :hover and disappear when the cursor leaves. For an eye-gaze user, the gaze cone drifts off the menu trigger the moment they try to look at a sub-item, and the menu collapses before they reach it. The WCAG 2.2 criterion that handles this is 1.4.13 Content on Hover or Focus (Level AA): hover-triggered content must be dismissable, hoverable (the user can move into it without it disappearing), and persistent. Many production menus fail all three.

Tiny click targets. SC 2.5.8 Target Size (Minimum) (Level AA, new in WCAG 2.2) requires that interactive targets be at least 24x24 CSS pixels, with exceptions. The criterion was written for touch and for pointer-imprecise users — eye-gaze, head-pointer, hand tremor. A 16-pixel close-icon at the corner of a modal is, in practice, almost impossible to hit reliably with an eye-tracker. The fix is mechanical: make targets larger, or expose the same action through a larger control elsewhere in the interface.

Time-bounded clicks. Carousels that auto-advance every 5 seconds, "you have 30 seconds to confirm" dialogs, session timeouts that fire mid-task. For a switch user navigating a scanning interface at a 1.5-second-per-target scan rate, a 30-second timeout is approx. 20 targets of reachable real estate — often not enough to reach the confirmation button. SC 2.2.1 Timing Adjustable requires that any time limit be extendable, adjustable, or dismissable. Most production timeouts are none of these.

Gesture-only confirmation. Swipe-to-confirm sliders, signature-pad confirmations, captchas that require tracing a path. Each is a 2.5.1 failure unless paired with a button alternative.

Action-on-mousedown. A button that fires its handler on mousedown rather than on the standard click event leaves the user no way to abort a misfire. SC 2.5.2 Pointer Cancellation is the criterion; the fix is to bind to click, or to pointerup with an explicit cancellation check.

Custom controls without ARIA. A <div> that visually looks like a button but lacks role="button", tabindex="0", and a keydown handler for Enter and Space. The control is unreachable by switch and by keyboard fallback. SC 4.1.2 Name, Role, Value (Level A) is the criterion. The fix is the native <button> element wherever possible, and a complete ARIA pattern wherever it is not.

Design patterns that work

The patterns that survive an eye-tracker, a head-pointer, and a switch scan share a small number of structural properties. Each is well-documented in the ARIA Authoring Practices Guide and in the WCAG 2.2 understanding documents, and each is in routine production use on sites that ship to mainstream audiences without anyone noticing.

Native HTML elements wherever possible. The single most reliable accessibility move is to use <button>, <a>, <input>, <select>, and <textarea> for their semantic purposes. Native elements come with the right keyboard handling, the right ARIA roles, the right focus behaviour, and the right pointer-cancellation semantics built in. The complexity of rebuilding any of those correctly with a custom <div> is approx. 10x the engineering work for an outcome that is almost always worse.

Visible focus indicators with adequate contrast. For switch users the focus ring is the cursor. A 2-pixel blue ring with 4:1 contrast against the surrounding background is the procedural minimum (SC 2.4.7 Focus Visible, Level AA, and SC 2.4.11 Focus Not Obscured, new in WCAG 2.2). Sites that strip the default browser focus ring without replacing it cut switch users adrift.

Predictable focus order. A switch scan moves through the DOM in source order by default, modified by tabindex. A scan order that jumps around the page makes the interface unusable. SC 2.4.3 Focus Order (Level A) is the criterion; the practical implication is that visual order and DOM order should match wherever the user is performing a sequence of actions.

Generous activation areas. SC 2.5.8's 24-pixel minimum is the floor, not the target. Many of the design systems that have published accessibility-tested patterns since 2022 — Adobe Spectrum, IBM Carbon, GOV.UK Design System, the US Web Design System — default to 44-pixel touch targets, which works well for pointer-imprecise users without intruding on visual layout.

Confirmation flows with explicit buttons. Any destructive or irreversible action should require an explicit confirmation button — not a swipe, not a long-press, not a "click anywhere outside to dismiss." The pattern works for everyone and survives every alternative input.

Generous timeouts, or none at all. If a timeout is required for security reasons (banking, healthcare), the user must be able to extend it through a single-pointer action well before it fires. The pattern is to surface a "still there?" prompt at 75% of the timeout window, with a single large button to extend it.

Skip-links and landmark navigation. A scanning interface that has to traverse the entire navigation menu, the entire hero section, and the entire ad slot before reaching the article body is unusable. A "Skip to content" link as the first focusable element of the page is the minimum; landmark regions (<main>, <nav>, <aside>) let switch users jump structurally rather than linearly.

Respect the user's prefers-reduced-motion setting. Auto-advancing carousels and constantly-animated backgrounds make it impossible for an eye-tracker to settle on a stable target. CSS media queries (@media (prefers-reduced-motion: reduce)) let the same interface serve the user who needs the motion gone.

What this means for designers, engineers, and product teams

The reporting record on alternative input modalities lands in a place that should feel familiar to anyone who has read this site's other accessibility primers. The technology has matured. The standards have matured. The user populations are well-characterised. The remaining work is procurement, training, and the daily habit of building interfaces that don't quietly assume two-axis, two-hand, sub-second-latency input.

For designers: prototype with the keyboard. If your design works under tab-only navigation with a visible focus ring, it works for a switch user; if it doesn't, the visual design has out-paced the interaction model. The Apple Vision Pro's gaze-plus-pinch precedent reframes alternative input as the design baseline rather than a remediation. Designs that survive Vision Pro tend to survive Tobii.

For engineers: bind to click rather than mousedown. Use native HTML elements. Test your tab order. Run the page through a keyboard-only audit before it ships. Most of the breakage above is engineering convention rather than engineering difficulty.

For product teams: include users of alternative input modalities in routine user testing. The barriers above are not edge cases; they are routine failures that surface in 30 minutes of testing with a Tobii bar or an iOS device with Switch Control turned on. The cost of including the modality in the test plan is small. The cost of not including it shows up as the kind of breakage above, shipped at scale, to a population whose options are already narrow.

The web works when it accepts that the click is not the universal verb. The user with a Tobii bar mounted below her monitor, the user with a webcam tracking his nose tip, the user with a single mechanical switch wired to the corner of a desk — each of them is performing the same action as a user with a trackpad. The standards layer recognises that. The design patterns above honour it. The work is to keep building as if that were true.

Read more from Disability World on the WCAG 2.2 success criteria, on the wider 2026 reporting record, and on our ongoing assistive-technology coverage.

Primary sources

World Wide Web Consortium (W3C). Web Content Accessibility Guidelines (WCAG) 2.2, recommendation October 2023. https://www.w3.org/TR/WCAG22/
World Wide Web Consortium (W3C). Pointer Events Level 3, recommendation. https://www.w3.org/TR/pointerevents/
World Wide Web Consortium (W3C). WAI-ARIA Authoring Practices Guide. https://www.w3.org/WAI/ARIA/apg/
World Health Organization. Global Report on Health Equity for Persons with Disabilities (2022) and 2024 monitoring update.
US Centers for Disease Control and Prevention. Disability and Health Data System (DHDS), accessed 2026.
Tobii Dynavox AB. PCEye and I-Series product documentation, 2025 release notes.
Apple Inc. Apple Vision Pro Accessibility documentation, visionOS 2 (2024-25).
Boston College. Camera Mouse project documentation, 2024 release.
Apple Inc. Switch Control on iOS, iPadOS and macOS, accessibility documentation.
Google. Switch Access for Android, Android Accessibility documentation, Android 14+.
ALS Association. Epidemiology of ALS in the United States, 2024 surveillance update.
European ALS Consortium. ALS prevalence and incidence reporting, 2023-25 cycles.

France's RGAA: the public-sector audit obligation that bleeds into private contracts

Disability World — Fri, 22 May 2026 00:00:00 GMT

Image description: An official French government document with the Marianne emblem and a wax-seal stamp resting on a polished wooden desk — the bureaucratic anchor of France's RGAA accessibility framework.

Reading Time: 10 minutes

France's Référentiel général d'amélioration de l'accessibilité (RGAA — the General Accessibility Improvement Framework) is the country's national technical reference standard for digital accessibility. Now in version 4.1.2, it operationalises Article 47 of the Loi n° 2005-102 du 11 février 2005 pour l'égalité des droits et des chances (Law of 11 February 2005 on equal rights and opportunities) and aligns French public-sector compliance with WCAG 2.1 level AA. For the broader European context, see the national disability-rights regulations index and the Disability World primer on the European Accessibility Act (EAA).

Two features make the RGAA unusual among European national frameworks. First, every covered entity must publish — on the home page of the service — an annual déclaration d'accessibilité (accessibility statement) backed by a documented self-audit and a multi-year schéma pluriannuel (multi-year roadmap). Second, while the legal obligation formally binds the public sector, the RGAA bleeds into private contracts through public procurement: any vendor selling a covered digital service to the French state effectively has to conform to it. With the Loi du 9 mars 2023 portant diverses dispositions d'adaptation au droit de l'Union européenne (BFG, the French transposition of the EAA) taking effect on 28 June 2025, the obligation now also reaches a defined set of private services. This primer covers what the RGAA is, who it binds, how it is enforced, and what the 2026 picture looks like.

Purpose and scope

The RGAA is a technical reference framework maintained by the Direction interministérielle du numérique (DINUM) — the inter-ministerial digital directorate inside the Prime Minister's office — that translates the WCAG success criteria into a structured French-language audit methodology. It is not, in itself, the source of legal obligation: the obligation comes from Article 47 of the 2005 Law, fleshed out by decree n° 2019-768 du 24 juillet 2019 and the implementing arrêté of 20 September 2019 (revised in 2020 and 2023). The RGAA is the document those instruments incorporate by reference as the conformance benchmark.

Version 4 of the RGAA, published in 2019 and updated through point releases to 4.1.2 in 2023, restructured the framework around WCAG 2.1 level AA. It contains 106 tests grouped under 13 thematic criteria — images, frames, colours, multimedia, tables, links, scripts, mandatory elements, structure of information, presentation of information, forms, navigation, and consultation. Each test maps to one or more WCAG success criteria and is paired with a fixed audit method: what the auditor must check, with which assistive technology, and how to record the result as conformant, non-conformant, or non-applicable.

Who is covered

The obligation under Article 47 of the 2005 Law, as amended by the Loi n° 2016-1321 du 7 octobre 2016 pour une République numérique (Digital Republic Act), extends to:

Public-sector bodies — central government, local authorities (regions, departments, communes), public hospitals, public universities, and any administrative public establishment.
Bodies governed by public law — entities that, while not strictly part of the administration, are publicly financed or controlled, such as social-security funds and certain national agencies.
Private organisations carrying out a public-service mission — operators of public transport, public broadcasters, and certain delegated-service concessionaires.
Private entities above the threshold — private companies with a turnover in France above EUR 250 million over the most recent three fiscal years, brought in by the 2018 Loi pour la liberté de choisir son avenir professionnel (Law on the freedom to choose one's professional future) and detailed in the 2019 decree.

The EUR 250 million threshold is the bridge that surprises non-French observers: the RGAA is often described as a "public-sector" framework, but in practice large private companies operating in France — banks, telecoms, retailers, energy providers — are already inside its perimeter, independently of the EAA. With the BFG transposition taking effect in 2025, the perimeter has widened further to cover specific consumer-facing private services regardless of turnover.

Key provisions: the audit obligation

What distinguishes the RGAA from a soft reference standard is the operational compliance architecture written into the 2019 decree and arrêté. Every covered entity must do four things, on a rolling annual cycle.

The accessibility statement

First, publish a déclaration d'accessibilité on every covered digital service — website, mobile application, intranet, extranet, and back-office tool used by the public — accessible from the home page. The statement must follow the template in the arrêté: declared conformance state (totally / partially / non-conformant), the conformance rate as a percentage of RGAA tests passed, a list of non-accessible content with justifications, the audit method and date, and the contact channels for users to report accessibility problems and request alternatives.

An accessibility statement that claims "totally conformant" must rest on an audit carried out by an external or qualified internal auditor against the full 106-test RGAA matrix. "Partially conformant" requires the audit and a conformance rate of at least 50 percent of applicable tests. Below 50 percent, the service must declare "non-conformant" — a statement that, by 2026, has become uncomfortable to display publicly given press and DPO attention.

The multi-year roadmap

Second, every covered entity must publish a schéma pluriannuel de mise en accessibilité — a three-year accessibility roadmap — and an annual action plan derived from it. Both documents are public. The roadmap names the services covered, the budget allocated, the governance arrangements (the named accessibility referent), and the milestones; the action plan lists the concrete remediation work scheduled for the year. DINUM publishes its own roadmap as a worked example, and Anct (the Agence nationale de la cohésion des territoires) supports smaller local authorities in drafting theirs.

User feedback and ombudsman recourse

Third, every accessibility statement must give users a feedback channel and explain the route to the Défenseur des droits — the French ombudsman — if no satisfactory response is received. The Défenseur des droits has, since 2019, treated digital-accessibility complaints as a category in its own right, and its annual reports name covered entities found to be in breach. Although the Défenseur's recommendations are not binding, they are publicly issued and have moved the needle on several large public-service migrations.

Mandatory training

Fourth, the 2019 decree requires covered entities to train staff who design, develop or publish digital content. Training is not specified by hours, but the schéma pluriannuel must name the staff trained and the providers used. DINUM's Design Gouv guidelines and the Accessibilité numérique course catalogue maintained by the public-service training agency are the de facto reference offerings; private universities and bootcamps that run RGAA-aligned curricula have proliferated since 2022.

Timelines: how the RGAA reached version 4.1.2

11 February 2005 — Article 47 of the loi pour l'égalité des droits et des chances establishes the principle that public-sector online services must be accessible.
2009 — RGAA version 1 published. Built on WCAG 1.0; immediately criticised by DPOs as too vendor-friendly.
2014 — RGAA version 2 aligned with WCAG 2.0 level AA.
7 October 2016 — Loi pour une République numérique extends the obligation to cover online public-service bodies and introduces the private-sector turnover threshold (then EUR 250 million).
2017 — RGAA version 3.2017 published; first version to integrate an audit grid intended for routine self-assessment.
2019 — Decree n° 2019-768 of 24 July 2019 and the implementing arrêté of 20 September 2019 set the operational obligations — accessibility statement, schéma pluriannuel, annual plan, training. RGAA version 4 published the same year, aligned with WCAG 2.1 AA and Web Accessibility Directive (2016/2102) requirements.
2020–2023 — Point releases 4.0, 4.1, 4.1.1 and 4.1.2 refine audit methodology, expand mobile-app coverage, and clarify scoring rules.
9 March 2023 — Loi portant diverses dispositions d'adaptation au droit de l'Union européenne (BFG) transposes the European Accessibility Act into French law. (The user assignment cited "loi du 19/12/2023"; the operative French enabling vehicle for the EAA was the BFG, with the implementing decree adopted later in 2023.)
28 June 2025 — BFG provisions for private consumer-facing services enter into force, mirroring the EAA's application date across the EU.
2026 — first full reporting year under the expanded perimeter; the ARCOM transparency report incorporates compliance data on private-sector services for the first time.

Enforcement: ARCOM, DGCCRF, and the Défenseur des droits

French digital-accessibility enforcement runs across three authorities with overlapping but distinct mandates. Understanding which authority does what is the difference between a token compliance posture and a defensible one.

ARCOM — the platform regulator with the accessibility brief

The Autorité de régulation de la communication audiovisuelle et numérique (ARCOM) — created in 2022 by the merger of the audiovisual regulator CSA and the online-content body HADOPI — inherited responsibility for monitoring public-sector and large-private digital accessibility under Article 47. ARCOM publishes a periodic rapport sur l'application de l'article 47 naming covered entities, their declared conformance rates, and the entities that failed to publish a statement at all. The 2025 report covered roughly 4,800 in-scope organisations; about a third had no accessibility statement on the home page in the form prescribed.

ARCOM has, since 2020, the power to issue administrative fines of up to EUR 50,000 per service for failure to publish a compliant accessibility statement, failure to produce a schéma pluriannuel, or publication of a statement materially misrepresenting the conformance state. The fine ceiling was raised from EUR 25,000 by the 2023 reform and is doubled on repeat breach. By 2026, ARCOM has issued more than two dozen fines, almost all against private-sector entities above the turnover threshold; public-sector fines remain rare and reputational pressure does the work instead.

DGCCRF — consumer-protection enforcement on the private side

The Direction générale de la concurrence, de la consommation et de la répression des fraudes (DGCCRF) — the consumer-protection and competition directorate inside the Ministry of Economy — handles enforcement on private-sector consumer services brought into scope by the BFG. Where ARCOM polices the Article 47 obligation as such, DGCCRF polices the EAA-derived obligations on e-commerce, banking, transport ticketing, e-books, and the other categories listed in Annex I of Directive 2019/882. DGCCRF agents have inspection powers, can issue administrative penalties up to EUR 75,000 for legal entities, and refer the most serious cases to public prosecutors.

The split matters because a large French retailer's website is, simultaneously, in scope of ARCOM under the EUR 250 million threshold and of DGCCRF as a consumer e-commerce service under the BFG. Both authorities can act; in practice DINUM has coordinated a memorandum of understanding clarifying who leads on which file.

The Défenseur des droits — individual complaints

The Défenseur des droits handles individual complaints from users who cannot access a covered service. The institution's recommendations are not binding but are publicly published, and in repeated cases the Défenseur has referred files to ARCOM for follow-on administrative action. The 2024 annual report logged more than 1,600 digital-accessibility complaints, the highest annual figure since the category was created.

How the RGAA bleeds into private contracts

The RGAA's reach beyond its formal scope is largely a function of French public procurement. Article L2112-2 of the Code de la commande publique (Public Procurement Code) and the standard cahier des clauses administratives générales (CCAG) templates published by Bercy require contracting authorities to integrate accessibility requirements into technical specifications for digital services. In practice, every state, region, department, commune, hospital, university, or public-establishment tender for a website, an application, a CMS, a customer-management system, or an intranet now carries an RGAA conformance clause.

For vendors, the consequence is direct. A SaaS company selling a public-sector ticketing platform must demonstrate RGAA conformance at contract signature, embed an annual audit obligation in the SLA, and accept liquidated-damages clauses tied to non-conformance. A consultancy bidding on a website redesign must staff the project with developers trained against the RGAA matrix. A design system that does not pass the RGAA 13-theme test grid does not win French public-sector business. The framework's geographic and sectoral footprint is therefore much larger than the legal obligation suggests — and is one reason French accessibility-engineering firms have built mature consulting practices around RGAA audits.

The EAA expansion: 2025 onward

The European Accessibility Act (Directive 2019/882) was transposed into French law by the BFG of 9 March 2023, with implementing decrees adopted later in 2023. Application started on 28 June 2025, mirroring the EU-wide date. The transposition does not replace the RGAA; it sits alongside it. The RGAA remains the audit benchmark for public-sector services and for large private services already inside Article 47's perimeter. The BFG extends a parallel obligation to a defined list of consumer-facing private services — e-commerce, retail banking and consumer credit, e-books and dedicated reading software, electronic communications services, audiovisual media services access, transport ticketing and information, and ATM and self-service terminals — regardless of company size, subject to the EU's harmonised micro-enterprise exemption.

For those private services, conformance is measured against the harmonised European standard EN 301 549, which itself incorporates WCAG 2.1 AA for web and mobile. In other words, the practical content of compliance is the same as the RGAA — but the legal vehicle, the enforcement authority (DGCCRF rather than ARCOM), and the documentation template differ. Many French private-sector vendors that were already RGAA-compliant for public-sector contracts have used 2024 and 2025 to extend the same audit programme to their consumer products, on the reasonable view that running two parallel compliance regimes is more expensive than running one.

Practical implications: what to prepare for in 2026

For organisations newly inside the perimeter — particularly mid-sized French private services in the BFG categories — the operational lift breaks into four workstreams. None is exotic; all are unforgiving on timeline.

Run the audit. Whether against the RGAA 13-theme test grid (public sector and large private) or EN 301 549 (BFG private services), the audit must be documented, dated, and signed by an identifiable auditor. Self-audits are permitted but a third-party audit carries materially more weight if ARCOM or DGCCRF later challenges the published statement.
Publish the statement. The accessibility statement must sit on the home page of every covered service, follow the official template, and update at least annually. A missing or non-conformant statement is the failure ARCOM most commonly fines — easier to detect, easier to prove, easier to act on than substantive WCAG breaches.
Draft the schéma pluriannuel. Public-sector bodies have a three-year roadmap obligation. Private entities under the BFG have no equivalent formal duty but most large vendors are publishing voluntary roadmaps to manage procurement risk and DPO scrutiny.
Train and name a referent. Every covered entity must train its design, development and editorial staff, and name an accessibility referent. The referent's contact details belong in the accessibility statement; the training programme belongs in the schéma pluriannuel.

Conclusion: a national framework with EU-shaped edges

Twenty-one years after the 2005 Law set the principle, the RGAA has become one of the most operationally specific national digital-accessibility frameworks in Europe — a 106-test audit methodology, a mandatory annual self-assessment, a public accessibility statement, a three-year roadmap, named referents, mandatory training, and two regulators (ARCOM and DGCCRF) with administrative-fine powers. The framework is not loud, but it is dense, and through public procurement it shapes a much larger commercial footprint than its formal scope.

The interesting question for the rest of the decade is whether the RGAA and the EAA settle into a clean two-track regime — RGAA for the public sector and large pre-existing private perimeter, EN 301 549 plus the BFG for the new private consumer services — or whether DINUM eventually publishes a fifth-generation RGAA that absorbs the EAA matrix and presents covered organisations with a single French-language framework. The 2024 RGAA consultation hinted at the latter. For now, organisations operating in France should assume both regimes apply and design their compliance programme around the broader of the two. For further reading, see the Disability World primer on the European Accessibility Act and the national disability-rights regulations index.

Game accessibility 2026: the post-CVAA video-game extension and where AAA studios stand

Disability World — Fri, 22 May 2026 00:00:00 GMT

Editorial · Game accessibility, AAA studios, and the post-CVAA expansion

Game accessibility 2026 — the post-CVAA video-game extension and where AAA studios stand

A decade after the Federal Communications Commission's 2013 video-game waiver expired, and twelve years into the Twenty-First Century Communications and Video Accessibility Act's reach over in-game communications, the AAA console business has been pulled — unevenly, sometimes reluctantly — into a recognisable accessibility-feature baseline. Of the 10 largest AAA publishers by 2024-25 unit sales, roughly seven now ship at least the floor of the Game Accessibility Guidelines' "Basic" tier (subtitles on, remappable controls, colourblind-aware UI) across their headline 2025 releases. The high-watermark — Naughty Dog's The Last of Us Part II with its approx. 60 accessibility settings at 2020 launch — has been matched in feature count by only two subsequent AAA titles. The FCC's January 2024 Further Notice of Proposed Rulemaking in CG Docket Nos. 10-213 / 10-145 / 06-181 has signalled an explicit expansion of Section 716 scope beyond text-only in-game chat to cover the broader advanced-communications-services surface inside games. This dossier reconstructs the regulatory line, scores the AAA studios, and names what the 2026-28 enforcement curve probably looks like.

Findings · Case file 12 07 entries · derived from FCC dockets, Game Accessibility Guidelines audits, and AAA studio shipping configurations 2020-2025

What the AAA accessibility record shows

01 2014

CVAA Section 716 obligations for in-game advanced-communications services took effect on 8 January 2014

The Twenty-First Century Communications and Video Accessibility Act of 2010 extended the Communications Act's accessibility requirements to advanced communications services (ACS), defined to include "interconnected and non-interconnected VoIP services, electronic messaging services, and interoperable video conferencing services." The FCC's video-game waiver covering software-rendered in-game chat expired on 8 January 2014 — making the AAA games industry the largest single sector to come under ACS rules during the CVAA's first phase.
02 approx. 60

Naughty Dog's The Last of Us Part II shipped with roughly 60 distinct accessibility settings at 2020 launch

The Game Accessibility Guidelines audit of the title — published by AbleGamers and the IGDA Game Accessibility Special Interest Group — counted 60-plus settings across motor, visual, auditory, and cognitive categories, including full screen-reader-style menu navigation, high-contrast display modes, and granular subtitle controls. The audit set the AAA high-watermark that subsequent first-party Sony and Microsoft titles have used as a benchmark.
03 2019

Microsoft's Xbox Accessibility Guidelines (XAGs) launched as the industry's first publisher-mandated accessibility checklist

First published in 2019 and now in their fifth revision, the 25 XAGs cover input remapping, subtitle and caption rendering, colourblind support, audio-description hooks, and reduced-motion options. Microsoft's first-party studios are required to ship against the XAGs; Microsoft Game Stack's certification process for third-party Xbox releases tests against a subset of them.
04 2023

Sony introduced accessibility-tagging on the PlayStation Store in 2023, surfacing per-title feature presence at the point of purchase

The PlayStation Store accessibility-tag programme attaches a per-title metadata block to game pages, flagging support for subtitles, audio descriptions, remappable controls, single-stick play, and colourblind options. Coverage is uneven — first-party titles are tagged at near-100% rates; third-party titles much less so — but the tag itself is the consumer-facing equivalent of a nutrition label.
05 Jan 2024

The FCC's January 2024 Further NPRM signalled expansion of Section 716 scope to broader in-game ACS surfaces

CG Docket Nos. 10-213, 10-145, and 06-181. The Further Notice asked whether the existing Section 716 framework adequately reaches modern in-game communications, including voice chat, integrated party chat, in-game text channels with third-party voice overlays, and the audio descriptions and captions for cinematic cut-scenes that the original 2013-14 rulemaking did not contemplate. Comments closed in mid-2024; a final rule has been expected for the 2026 calendar year.
06 3 tiers

The Game Accessibility Guidelines split feature coverage into Basic, Intermediate, and Advanced tiers — the de-facto WCAG equivalent for games

Maintained by a working group including AbleGamers, the IGDA Game Accessibility Special Interest Group, and consultants from major UK studios since 2012, the GAGs catalogue roughly 100 individual recommendations split across the three tiers and across motor, visual, auditory, cognitive, and speech-impaired-player categories. The Basic tier is the negotiated floor; the Advanced tier matches the Last of Us Part II watermark.
07 7 of 10

Seven of the ten largest AAA publishers by 2024-25 sales now hit the GAG Basic tier on headline 2025 releases

Coverage is uneven across each publisher's catalogue — Microsoft, Sony, and Naughty Dog (Sony first-party) sit at the Advanced tier on flagship titles; Nintendo, Ubisoft, and EA hit Intermediate on most 2025 releases; Take-Two, Activision-Blizzard, Bandai-Namco, Capcom, and Square-Enix cluster at the Basic tier with isolated Intermediate excursions. Two publishers in the top-10 — names withheld pending publisher comment — failed to hit even the Basic tier on at least one 2024-25 headline release.

SourceFCC CG Docket Nos. 10-213 / 10-145 / 06-181 (CVAA Section 716 implementing rulemakings and 2024 FNPRM); Game Accessibility Guidelines (gameaccessibilityguidelines.com, working-group revisions 2012-2024); AbleGamers audits 2020-2024; IGDA Game Accessibility Special Interest Group's annual State of Game Accessibility surveys 2022-2024; Microsoft Xbox Accessibility Guidelines (revisions 1-5, 2019-2024); Sony PlayStation Store accessibility-tag programme metadata; per-title accessibility audits published by Can I Play That?, DAGERSystem, and Family Gaming Database 2020-2025.

In this report

01The CVAA, Section 716, and the 2014 video-game extension
02The January 2024 FNPRM and what it expands
03The Game Accessibility Guidelines as a WCAG-equivalent
04Where the AAA studios stand
05The Last of Us Part II as the high-watermark
06Platform-holder programmes — Xbox, PlayStation, Nintendo
07AbleGamers, IGDA-GASIG, and the consultancy layer
082026-28 outlook

01 · The CVAA, Section 716, and the 2014 video-game extension

The Twenty-First Century Communications and Video Accessibility Act of 2010 — Public Law 111-260, signed by President Obama on 8 October 2010 — was the first substantial federal accessibility statute since the Americans with Disabilities Act of 1990 to be aimed primarily at communications technology. The Act amended the Communications Act of 1934 by adding Sections 716 and 717, requiring providers of advanced communications services and manufacturers of equipment used for ACS to make those services and that equipment accessible to and usable by individuals with disabilities, "unless not achievable." The FCC's implementing rules at 47 CFR Part 14 set out the substantive obligations: equivalent access, performance objectives, information and documentation accessibility, and a complaint and enforcement track in front of the Consumer and Governmental Affairs Bureau.

For the video-game industry, the practical question after 2010 was whether and when Section 716 reached in-game communications. The FCC granted a one-year industry-wide waiver in October 2012 (FCC 12-119, in CG Docket No. 10-213), and a further one-year extension in October 2013 — and then the waiver lapsed on 8 January 2014. As of that date, AAA publishers shipping titles with in-game voice or text chat were ACS providers under Section 716 for the chat surface specifically, and the FCC's accessibility obligations attached. The first wave of compliance work — subtitled voice chat, text-to-speech text chat, and request-and-response mechanisms for accessibility documentation — moved into the industry's certification pipelines in 2014-15.

01Section 716substantive ACS obligation — accessible to and usable by individuals with disabilities unless not achievable

02Section 717recordkeeping + enforcement — the complaint-and-resolution track in front of the CGAB

032012-13 waiverFCC granted a one-year-plus-extension industry waiver for software-rendered in-game chat; lapsed 8 Jan 2014

04January 2024 FNPRMFurther Notice of Proposed Rulemaking — re-opens whether modern in-game ACS surfaces are adequately covered

10 of 10

top-10 AAA publishers analysed

47 CFR Part 14

implementing rules for CVAA Section 716

approx. 100

Game Accessibility Guidelines recommendations across three tiers

Xbox Accessibility Guidelines (XAGs) at fifth revision

02 · The January 2024 FNPRM and what it expands

The Commission's 18 January 2024 Further Notice of Proposed Rulemaking, in CG Docket Nos. 10-213, 10-145, and 06-181, did not rewrite the Section 716 framework. It did something narrower and arguably more consequential: it asked, with a series of pointed questions, whether the original 2012-13 implementing record had adequately anticipated what in-game communications would look like a decade on. The four expansion vectors the FNPRM signalled are roughly these. First, integrated party chat and platform-level voice systems (Xbox Live Party, PlayStation Network parties, Discord-game integration) where the chat surface is co-rendered by the platform and the game and the accessibility obligation could attach to either. Second, in-game voice chat with third-party overlays — the proxy case being Discord's in-game integration with EA, Bungie, and Activision-Blizzard titles. Third, the captions and audio descriptions of in-game cinematics, which the 2013-14 rulemaking record did not treat as ACS but which the FNPRM hinted might fall within a "video conferencing service" reading. Fourth, cross-platform play and the question of which ACS provider owns the obligation when the chat is rendered across two consoles' platforms simultaneously.

{/* Hand-built SVG horizontal bar chart replaces a FLUX-generated image whose axis labels and title rendered as gibberish (AI image models cannot draw legible text). Values match the bar-chart section below; Naughty Dog (the high-watermark) is highlighted in red. */}

The ten largest AAA publishers by 2024-25 unit sales, ranked by the count of Game Accessibility Guidelines recommendations implemented across their headline 2025 releases. Dashed lines mark the GAG Basic-tier floor (approx. 30 recommendations) and the Intermediate threshold (approx. 65); Naughty Dog (highlighted in red) sits at the Advanced tier and matches the 2020 first-party watermark set by The Last of Us Part II.

AAA studios — Game Accessibility Guidelines coverage on 2025 headline releases (count of GAG recommendations implemented, of approx. 100 total)

Naughty Dog (Sony first-party)

approx. 80

Xbox Game Studios (Microsoft)

approx. 74

Sony Interactive Entertainment (1P)

approx. 70

Ubisoft

approx. 58

Electronic Arts

approx. 55

Nintendo

approx. 46

Take-Two Interactive

approx. 42

Activision-Blizzard (Microsoft)

approx. 38

Capcom

approx. 35

Square-Enix

approx. 30

7 of 10

AAA publishers clearing GAG Basic tier on 2025 headline releases

3 of 10

clearing the Intermediate tier consistently

2 of 10

producing at least one title in the Advanced tier in 2024-25

The FNPRM is not a rule. It is a notice that the Commission expects the next phase of Section 716 rulemaking to widen the scope of what counts as an in-game ACS surface and to clarify the allocation of obligation between platform holders and game publishers. For AAA studios that have already built out the Game Accessibility Guidelines compliance work — Microsoft, Sony first-party, Ubisoft — the expansion is a marginal increment. For studios that have shipped against the Section 716 chat-only baseline and not more — Take-Two on the Grand Theft Auto V-and-related back catalogue is the most-cited example — the expansion would require a more substantial pipeline shift.

What Section 716 covers, plainly stated

Section 716 covers in-game advanced communications services — the chat, voice, and messaging surfaces that the FCC treats as functionally equivalent to consumer communications services. It does not cover gameplay accessibility writ large. Subtitles for narrative dialogue, colourblind modes, remappable controls, and reduced-motion options are not Section 716 obligations. They are industry-standard accessibility features sitting on top of the GAG framework and the platform-holder guidelines.

03 · The Game Accessibility Guidelines as a WCAG-equivalent

The Game Accessibility Guidelines are not a standards-body document and they are not legally binding anywhere. They are a working-group product, maintained at gameaccessibilityguidelines.com since 2012 by a coalition that has included Ian Hamilton (independent consultant and IGDA-GASIG vice-chair), the AbleGamers Charity, the Special Effect UK trust, and accessibility leads at Microsoft, Ubisoft, Electronic Arts, and Sony. They are, however, the closest thing the games industry has to the Web Content Accessibility Guidelines — and like WCAG they are organised in tiers (Basic, Intermediate, Advanced) of escalating implementation depth.

The Basic tier — the negotiated floor — contains roughly 30 recommendations. The headline items are: subtitles on by default for all important speech, with size and colour controls; remappable controls including for accessibility hardware; menu navigation by screen reader or simulated screen reader; high-contrast and colour-blind-aware UI; clear visual cues paired with every audio cue; and at minimum one input scheme that does not require simultaneous button presses. The Intermediate tier adds another roughly 35 recommendations covering reduced-motion options, narration of menu state and gameplay HUD, granular subtitle and caption controls, audio descriptions for cinematics, and assist-mode difficulty options. The Advanced tier covers the remaining roughly 35 recommendations and is the territory where Naughty Dog's Last of Us Part II and Microsoft's Forza Motorsport currently sit — full screen-reader-style menu and HUD readout, alternative input via a single switch, sign-language interpretation of cinematics, and cognitive-load reduction modes.

Naughty Dog (Sony first-party)

Advanced tier · approx. 80 of 100 GAG recommendations · 60-plus settings shipped on Last of Us Part II (2020) and matched on Part II Remastered (2024)

Advanced

Xbox Game Studios (Microsoft)

Advanced tier · approx. 74 of 100 · XAGs revision 5 + Microsoft Inclusive Tech Lab + Adaptive Controller hardware support

Advanced

Sony Interactive Entertainment (other 1P)

Intermediate-Advanced · approx. 70 of 100 · Insomniac, Guerrilla, Santa Monica studio accessibility programmes

Intermediate+

Ubisoft

Intermediate · approx. 58 of 100 · in-house accessibility lab since 2018 · Assassin's Creed Mirage as the 2024 reference title

Intermediate

Electronic Arts

Intermediate · approx. 55 of 100 · EA Accessibility patents released to industry use 2021 · EA Sports FC reference

Intermediate

Nintendo

Basic-Intermediate · approx. 46 of 100 · catch-up wave 2023-25 driven by Switch 2 transition

Basic+

Take-Two Interactive

Basic · approx. 42 of 100 · uneven across Rockstar / 2K / Zynga divisions · GTA VI pending

Basic

Activision-Blizzard (Microsoft)

Basic · approx. 38 of 100 · Call of Duty integration with XAG framework since 2023 acquisition

Basic

Capcom

Basic · approx. 35 of 100 · improving on Resident Evil remakes 2023-24

Basic

Square-Enix

Below-Basic to Basic · approx. 30 of 100 · the laggard on the leaderboard, especially on Japanese-internal releases

Below-Basic

The Game Accessibility Guidelines are not law. They are a working-group consensus document. But after fifteen years of revision, they function in the AAA industry the way WCAG functioned in the early web — a de-facto standard whose authority is the absence of an alternative.

04 · Where the AAA studios stand

The ranking above is a per-headline-release count. It conceals two important things. First, AAA studios are not uniform across their catalogues. Sony first-party includes both Naughty Dog (the high-watermark) and certain other studios whose 2025 releases sat closer to the Basic tier. Take-Two includes the Rockstar division, whose 2024-25 work on Grand Theft Auto VI has reportedly involved a substantial accessibility-feature push that may not be reflected in the publisher's older catalogue. Second, accessibility-feature count is not the same as accessibility-feature quality. A studio that ships ten partial implementations of GAG Intermediate recommendations is not necessarily ahead of a studio that ships five thorough implementations.

What the leaderboard does capture is the strategic posture. Microsoft and Sony, the two platform holders with first-party studios, have invested most heavily in accessibility — and the investment has paid back in critical reception, in marketing positioning, and (less measurably) in user-acquisition among disabled players. Ubisoft and Electronic Arts have followed at the Intermediate tier, with EA's 2021 release of its accessibility-related patents to the industry serving as a public commitment beyond its own catalogue. Nintendo is the most-watched mid-table case: a publisher whose 2010s catalogue routinely failed the Basic tier has moved deliberately, if quietly, toward Intermediate over the Switch 2 transition. The bottom three — Take-Two, Capcom, Square-Enix — remain the laggards on the AAA leaderboard, though each has at least one Intermediate-tier title to its name.

The Japanese-internal release problem

One pattern the Game Accessibility Guidelines audit data surfaces but cannot fully resolve: AAA titles developed primarily for Japanese-market release and then localised for the West tend to land lower on the feature count than Western-developed titles aimed at the same global release window. Internal accessibility-feature decisions appear to be made at the original-localisation stage, and Western-localised additions are limited to subtitles and colour-aware UI. Capcom and Square-Enix release patterns are the most-cited examples; the dynamic is the closest thing the AAA accessibility leaderboard has to a structural — rather than studio-specific — explanation.

05 · The Last of Us Part II as the high-watermark

Naughty Dog's The Last of Us Part II, released for PlayStation 4 on 19 June 2020, is the canonical AAA accessibility-feature reference. The audit count of approximately 60 settings — published by AbleGamers and corroborated in the IGDA-GASIG's 2020-21 State of Game Accessibility survey — covers motor (control remapping, single-stick play, autopickup, autoaim toggles), visual (high-contrast modes, full-screen-reader-style menu narration, granular subtitle controls, magnification), auditory (closed captions for ambient and effect audio, navigation assist for blind players including audio cues for traversal), and cognitive (skip puzzle, lock-on aim, simplified UI) categories. The implementation depth — not just the feature count — is what set the title apart. The high-contrast mode is per-character-recolourable; the screen-reader-style narration covers menu state and gameplay HUD; the navigation-assist mode produces an audio-only playable mode demonstrated post-launch by blind players who completed the campaign.

Replicating that feature set is expensive. The Naughty Dog accessibility team grew to nearly twenty people across the development cycle and the Part II Remastered 2024 release. Subsequent Sony first-party titles — Horizon Forbidden West, God of War Ragnarök, Marvel's Spider-Man 2 — matched substantial portions of the feature set but not the full count, and the Naughty Dog audit count remains the AAA ceiling. The only Western AAA title to match the 60-plus count is, as of the 2025 audit, Microsoft's Forza Motorsport (2023), which shipped with an audited 70-plus accessibility settings, including a sign-language-interpreter rendering for cinematics. The Last of Us Part II's legacy is that it moved the AAA accessibility frontier from "best-effort subset of GAGs" to "feature count as a marketing claim."

Naughty Dog accessibility statement — June 2020

"The Last of Us Part II ships with over 60 accessibility options across three categories — visual, audio, and motor — to allow more players to enjoy the game, with custom difficulty granularity, alternate input schemes including single-stick play, high contrast display modes, full menu narration, and audio cues that allow players who are blind or low-vision to complete the entire campaign."

Naughty Dog accessibility announcement, June 2020 (PlayStation Blog)

06 · Platform-holder programmes — Xbox, PlayStation, Nintendo

The platform-holder accessibility programmes have done most of the work to move the AAA industry's floor upward. Microsoft's Xbox Accessibility Guidelines, the Xbox Adaptive Controller (released 2018, refreshed 2024 with the Proteus modular controller), the Inclusive Tech Lab, and the Game Stack accessibility-certification programme combine to put a soft compliance pressure on every Xbox-platform release. Microsoft does not enforce the XAGs as a hard certification gate — a third-party title can ship on Xbox without hitting them — but the XAG-pass marketing positioning, the platform-holder relationship leverage, and the Adaptive Controller user base have produced an environment where most major Xbox releases are at least audited against the XAGs.

Sony's programme is less codified than Microsoft's but materially comparable. The PlayStation Access Controller, released in late 2023, is Sony's equivalent of the Xbox Adaptive Controller — a modular kit designed to interface with assistive switches and joysticks. The PlayStation Store's accessibility-tagging programme, launched the same year, exposes per-title accessibility-feature presence at the point of purchase. Sony does not publish a formal equivalent of the XAGs; its accessibility programme operates inside its first-party studios and through producer-level guidance to third-party publishers.

Nintendo is the late mover. The Switch generation (2017-2024) shipped without platform-level accessibility infrastructure of the kind Microsoft and Sony had built. The Switch 2 transition in 2024-25 has been the occasion for Nintendo to catch up: platform-level options for subtitles and colour-aware UI, expanded controller-remapping at the system level, and an emerging Nintendo Switch Online accessibility-feature-tagging programme that mirrors Sony's. Nintendo's first-party output remains the most variable in the industry — The Legend of Zelda series, in particular, has been a sustained target of accessibility critique — but the trajectory is unambiguously upward.

The Xbox Adaptive Controller as a strategic move

Microsoft's 2018 release of the Xbox Adaptive Controller — a $99 hardware kit designed by the Microsoft Inclusive Tech Lab in partnership with AbleGamers, the Cerebral Palsy Foundation, Craig Hospital, SpecialEffect, and the Warfighter Engaged community — did more to move the accessibility frontier than any single software feature. By shipping a piece of hardware as a first-party platform-holder product, Microsoft made AAA accessibility a procurement question rather than a charity question. The 2024 Proteus refresh extended the strategy.

07 · AbleGamers, IGDA-GASIG, and the consultancy layer

The civil-society layer in game accessibility is small, well-networked, and disproportionately influential. AbleGamers (registered as a 501(c)(3) in West Virginia since 2004) provides direct grant-funded equipment to disabled players, audits AAA releases against the Game Accessibility Guidelines, and runs the Player Panels programme that pairs disabled players with AAA studios for development-cycle consultation. The IGDA Game Accessibility Special Interest Group, hosted by the International Game Developers Association, runs the annual State of Game Accessibility survey, the GDC accessibility-track programming, and the GASIG-curated reading list that is the de-facto entry point for studio accessibility leads. The UK-based SpecialEffect charity runs StarGazing and EyeMine programmes that produce eye-gaze and switch-input infrastructure used by both individual players and AAA studio user-testing labs.

Around those three organisations sits a small consultancy layer — Ian Hamilton, the leading independent consultant, has worked with virtually every AAA publisher in the top-10 leaderboard above. Cherry Thompson (consultant on The Last of Us Part II) and Steve Saylor (audit reviewer on multiple Sony first-party titles) operate at the same individual-consultant level. The consultancy layer is what closes the gap between platform-holder guidelines (XAGs, the implicit Sony-equivalent) and per-title implementation. Without the consultancy layer, the AAA accessibility-feature counts in the leaderboard above would be measurably lower — probably by ten to fifteen recommendations per Intermediate-tier release.

08 · 2026-28 outlook

Three threads will define the rest of the decade.

The FCC's expanded Section 716 rule. A final rule on the January 2024 FNPRM is expected within the 2026 calendar year. The most-discussed expansion vector — clarifying that integrated party chat, in-game voice-with-overlay, and cinematic captions fall within ACS — would impose a meaningful new compliance pipeline on publishers that have not yet built one. Microsoft and Sony first-party are positioned to absorb the expansion; Take-Two, Capcom, and Square-Enix would have to invest. The enforcement track in front of the Consumer and Governmental Affairs Bureau is not aggressive by Title III standards, but it produces meaningful compliance pressure through the public-record posture of the complaint docket.
The European Accessibility Act's video-game reach. The EAA's 28 June 2025 compliance deadline applies to a defined list of products and services that, on a contested reading, includes e-books and some categories of in-game communications but not video games as such. The Member-State transpositions vary on this point, and the European Commission's 2026 review will probably issue an interpretive guidance document on the games-industry scope. Where the EAA does bite, it bites on the customer-service surfaces around games — storefronts, account systems, support chat — rather than on gameplay itself.
The first AAA accessibility consent decree. No publisher in the top-10 leaderboard has so far been subject to an FCC consent decree on Section 716 grounds, nor to a US Department of Justice ADA Title III consent decree on game accessibility specifically. The 2025-26 plaintiffs' bar attention to live-service titles, in-game stores, and platform-side communications suggests that the first such consent decree is more probable than not within the 2026-28 window. Sony's PlayStation Store and Microsoft's Xbox storefront have absorbed scattered accessibility complaints; whether one matures into a settled enforcement action is the open question.

The through line

Game accessibility in 2026 is a measurable, ranked, document-anchored field in a way it simply was not in 2014 when the CVAA video-game waiver lapsed. The Game Accessibility Guidelines have produced a tiered standard; AbleGamers and the IGDA-GASIG have produced an auditing and convening infrastructure; Microsoft and Sony have produced platform-holder programmes that exert real pressure on third-party publishers; and Naughty Dog's The Last of Us Part II set a feature-count ceiling that the industry now measures itself against. The seven-of-ten Basic-tier coverage on the leaderboard above is the visible artefact of fifteen years of working-group standards-making finally landing in shipping product.

What it is not is a finished project. The Japanese-internal-release gap, the live-service / in-game-store surfaces, and the question of integrated party chat's regulatory home are all live. The January 2024 FCC Further NPRM and the EAA's 2026 interpretive guidance will set the next regulatory shape. Whether the AAA leaderboard's middle and bottom thirds move closer to the top — Sony first-party and Microsoft — or whether the gap widens is the consequential 2026-28 question, and the answer will probably be decided by the cost of the first consent decree against a publisher that did not.

Read more from Disability World on eye-tracking and switch input, on the ADA's reach into digital products, and on the 2026 reporting record.

Generative AI and screen-reader prompts: a design discipline emerges

Disability World — Fri, 22 May 2026 00:00:00 GMT

Image description: A smartphone resting on a wooden desk showing an AI chat interface with headphones plugged in — the visual marker for screen-reader-friendly AI prompt design.

Reading Time: 9 minutes

A new design discipline has crystallised inside the accessibility community over the past eighteen months, and it does not yet have a settled name. Some teams call it "AT-aware prompt engineering"; others call it "screen-reader-shaped system prompts"; the practitioners who came up through voice-UI design tend to call it "the speech-output layer of an LLM." Whatever the label, the craft is the same: writing system prompts and output-shaping rules that make generative AI assistants — ChatGPT, Claude, Gemini, Copilot, Be My AI — useful for the roughly approx. 253 million people worldwide who reach those products through a screen reader.

The problem is concrete and the failure mode is loud. An LLM trained on the public web produces, by default, prose decorated with em-dashes, nested markdown lists, code fences, headings that exist only because the model felt the answer was "structured", and decorative emoji. Read aloud by NVDA, JAWS, VoiceOver or TalkBack, that output becomes a stream of "dash dash" interjections, "bullet bullet bullet" enumeration without any sense of where one item ends, "heading level two" announcements that interrupt a sentence, and emoji name-strings ("smiling face with sunglasses") between every other clause. The information is in there. The user cannot extract it without rewinding three times. This piece is a primer on what the discipline is asking of model builders, what the products have shipped so far, and the open UX problems nobody has solved yet.

The new discipline — what it actually consists of

Screen-reader-aware prompt design is not a single rule. It is a small set of constraints that, together, produce output a synthesiser can pronounce intelligibly and a screen-reader navigation key can move through. The constraints fall into four buckets.

Concise responses with semantic structure. Default LLM output is too long for spoken delivery — a 600-word answer that reads fine in a sighted user's browser becomes a four-minute monologue that the screen-reader user has no way to skim. The discipline asks for shorter answers, but more importantly for structured shorter answers: an opening one-sentence summary that the user can stop at, followed by structure the screen reader can navigate by heading or by list-item.

Avoid em-dashes and other punctuation that synthesisers mispronounce. The em-dash, the en-dash, the parenthetical, the slash-as-conjunction, the ASCII-art separator — all of these are read aloud as either silence, a literal "dash", or a confusing pause that breaks a clause in half. The convention emerging across the major models is: prefer the comma and the full stop; use the colon for the one place it really earns its keep; never use em-dashes in spoken-context responses; never use ASCII rules to separate sections.

Declare what is a list, what is a heading, what is code. Synthesised speech has no visual hierarchy. A heading needs to be announced as "heading", a list needs to be announced as "list with N items, item one", code needs to be announced as "code", and the model needs to either output structures the screen reader recognises (HTML, proper markdown the rendering surface converts to ARIA) or to verbally narrate the structure itself ("Here are three options. Option one: ...").

No markdown soup. Markdown is fine when the rendering surface converts it to semantic HTML. Markdown is hostile when the surface displays the raw asterisks and underscores, because the screen reader then announces "asterisk asterisk" before every bold word. The discipline is to detect the rendering context — chat UI with markdown rendering versus terminal versus screen-reader-driven voice interface — and to shape the output accordingly. The same model needs to produce different surface representations of the same answer.

What screen readers actually need from AI

To make the constraints above concrete, it helps to look at the actual behaviour of the four screen-reader / OS combinations that dominate the field: JAWS on Windows, NVDA on Windows, VoiceOver on macOS and iOS, and TalkBack on Android. They are not interchangeable, and a prompt that produces great output for one can be unreadable on another.

Navigation by heading. All four readers expose a heading-navigation key (H in JAWS and NVDA, Rotor in VoiceOver, the reading-control toggle in TalkBack). For a long AI answer to be navigable, the model has to emit real semantic headings — either through a markdown rendering pipeline that converts to <h2>/<h3> with proper level nesting, or via the chat surface's own structured-response API. A model that "structures" its answer by bolding the first three words of each paragraph has produced something that looks structured visually and is completely flat to a screen reader.

Navigation by list. Lists are useful in spoken output precisely because the screen reader announces the count ("list with seven items") and lets the user step through with the list-item navigation key (I in NVDA, L in JAWS). But this only works if the list is a real <ul> or <ol>. A "list" produced by emitting bullet characters at the start of each line, with no list wrapper, is read as ordinary prose with an unexplained "black circle" or "bullet" interjection on every line.

Skip-by-section. Long-form AI answers — explanations, comparisons, code-and-commentary, multi-step instructions — need a way for the screen-reader user to skip to the section they care about without listening through the preamble. This is the single hardest piece to design well, because the model has to produce a navigable structure and the chat surface has to render it in a way the OS exposes to the assistive technology, and the screen reader has to be configured to use the heading-navigation key in that surface. All three things fail in the wild; usually it is the middle one.

Pronunciation hints. Synthetic voices stumble on technical terms, acronyms with mixed letters, URLs, code identifiers, mathematical notation, and non-English names. A well-designed model will, for screen-reader-context responses, spell out acronyms on first use ("WCAG, the Web Content Accessibility Guidelines"), expand initialisms the synthesiser cannot pronounce, and avoid embedding raw URLs inside flowing prose where the synth will read the slashes aloud. None of the major products do this consistently in 2026.

How the products are handling it

As of mid-2026, the major generative AI products have taken visibly different positions on screen-reader-aware output. None of them have nailed it. The progression is faster than it was twelve months ago, but the gap between the best and the worst is still wide.

ChatGPT (OpenAI). The web client now ships with a "concise mode" toggle that shortens default responses and reduces markdown decoration. The voice mode introduced in 2024 — and substantially upgraded in 2025 — is the closest any major product has come to a screen-reader-native interface, because it bypasses the visual chat entirely and delivers a spoken answer with a stop, replay and "say that again" gesture. The custom-instructions field allows screen-reader users to declare their preferences once and have them apply across sessions, which is the user-driven workaround the community has settled on. The remaining gaps: GPT models still default to em-dash-heavy prose unless instructed otherwise, and the heading-level emitted in markdown does not always map cleanly to ARIA in the chat surface.

Claude (Anthropic). Claude's system-prompt discipline has moved closest to the conventions described above. The model is noticeably less em-dash-prone than the GPT line in 2026, defaults to shorter answers, and responds well to system-prompt instructions like "you are speaking to a screen-reader user; use no em-dashes, prefer short paragraphs, and use real headings or numbered lists when structure is needed." The Claude.ai chat surface renders markdown to semantic HTML with proper heading levels, which makes the heading-navigation key work. Voice output through third-party integrations exists but is less developed than ChatGPT's first-party voice mode.

Gemini (Google). Tight integration with TalkBack on Android is Gemini's structural advantage; the model can hand off to the OS-level screen reader through Android's accessibility services in a way the iOS and web competitors cannot. The "Hey Google, ask Gemini..." flow on accessible Android devices is, for some users, the most natural AI-plus-screen-reader experience available. The remaining gaps: the web interface still over-decorates responses, the heading hierarchy in Gemini's web answers is inconsistent, and the model is more prone to producing decorative emoji than its competitors.

Be My AI (Be My Eyes + OpenAI). This is the most narrowly scoped of the four — a visual-description assistant that uses GPT-4-class vision models to describe images and surroundings for blind and low-vision users. It is also the only product in this list designed from day one for a screen-reader user as the primary audience. Be My AI's prompt design is the field's clearest demonstration of what AT-aware output looks like in practice: descriptions open with a one-sentence summary the user can stop at, follow with structured detail only if asked, and avoid spatial language ("on the left", "above") that requires sighted context to interpret. The product remains, in 2026, the closest the field has to a reference implementation.

The cross-cutting observation is that the four products have made progress on the easy parts — shorter answers, fewer em-dashes, a custom-instructions field — and have barely begun on the hard parts. The hard parts are below.

Open UX problems nobody has solved

The screen-reader-aware prompt-design literature converges on four open UX problems where the right answer is not yet known. None of them are model-capability problems; all of them are interaction-design problems that sit between the LLM, the chat surface, the OS, and the screen reader.

Interrupt-ability. A sighted user can scan an LLM response in approx. two seconds and decide whether to read it. A screen-reader user cannot. If the answer is wrong or off-target, the user has to listen through enough of it to know that, then interrupt. Voice modes have a stop button. Text modes generally do not — the response streams in and the screen reader announces it as new content as it arrives, and the user has no clean way to say "stop generating, this is not what I asked." The Be My AI app handles this best; the web chat clients handle it worst.

Repeat-last-answer with selectable granularity. Asking a screen reader to re-read the last response is easy if the answer is short. It is unusable if the answer is six paragraphs and the user only wants to hear the third paragraph again. The interaction the community is asking for is "repeat the last list item", "repeat the last heading section", "repeat the last code block." That requires the chat surface to expose the structure to the screen reader in a way the screen reader's own re-read commands can address. In 2026, none of the major products do this; the user has to use the screen reader's own line-by-line navigation, which is laborious.

Navigate-by-section in spoken output. Voice modes do not have a heading-navigation key. The user listens to a four-minute answer linearly, with no way to skip from the "overview" section to the "specifics" section without rewinding by time. The interaction designs being prototyped — a spoken "section list" the user can navigate with arrow keys, a "go to section three" voice command, a "give me the headings only" mode — are early. The Be My AI app's "more detail on the colours" follow-up is the closest functioning version of this in a shipping product.

The AT-handoff question — when does the AI speak versus read content aloud? This is the deepest design question. If a screen-reader user opens an AI assistant on a webpage, who is speaking — the AI's own voice (TTS layer), or the user's installed screen reader reading the AI's text output? The two voices have different settings, different speaking rates, different pronunciation hints, different stop-and-replay gestures. Two systems trying to speak the same content at the same time produces nothing usable. The convention emerging is: voice-mode interactions use the AI's own TTS and explicitly suppress the screen reader; text-mode interactions emit semantic HTML and let the screen reader do the speaking. But the boundary between the two modes is not always clean — image-description, code-generation, mathematical notation, and multi-modal answers all sit awkwardly between voice and text — and that boundary is where most of the live UX problems live.

Where it goes next

The discipline is roughly where web accessibility was in approx. 2002 — past the "is this a real problem?" phase, past the "is anyone responsible?" phase, into the "what are the actual rules?" phase. Three things are likely to happen across 2026 and 2027.

First, the model builders will codify their internal screen-reader prompts and publish them, the way Anthropic publishes Claude's system prompts in VPAT-style accessibility statements and OpenAI has begun documenting GPT's behavioural defaults. The community is asking for the equivalent of a model card — a "screen-reader output card" — that names the conventions a given model has been trained or system-prompted to follow.

Second, the chat surfaces — web clients, mobile apps, IDE integrations — will gain proper semantic-HTML rendering pipelines and proper ARIA exposure for chat history, with the navigation keys mapped to the OS-level screen reader. This is unglamorous work, and it is the work that will move the needle most for daily users.

Third, the screen-reader vendors themselves — Vispero (JAWS), NV Access (NVDA), Apple (VoiceOver), Google (TalkBack) — will start shipping AI-aware features: native heading-navigation inside AI chat surfaces, a standardised "stop generating" gesture, smarter re-read commands that know about LLM response structure. NVDA's open-source add-on ecosystem is already producing early versions of these. The proprietary readers are slower but the direction is the same.

The deeper observation is that screen-reader-aware prompt design has stopped being a niche concern of a handful of blind developers and has become a baseline expectation of every AI product team that wants to ship into regulated markets. The European Accessibility Act applies to "interactive self-service terminals" and "consumer terminal equipment with interactive computing capability" — a category that almost certainly captures a major AI assistant on a phone. The AT-aware output layer is not a feature any more; it is procurement-binding. The teams that figure out the rules now will ship the products that survive 28 June 2025 and onwards. The teams that treat it as an afterthought will be the next round of EAA enforcement cases.

Final thoughts

The craft is small, the stakes are large, and the rules are still being written. If you build with LLMs and you have not yet had a conversation with a screen-reader user about what your product actually sounds like when they use it, that is the next thing on the list. Most of what is wrong with AI for screen-reader users in 2026 is not a model-capability problem; it is a prompt-and-surface design problem that any product team can fix in a sprint, if they decide to.

The community has been generous with its time, its testing, and its patience. It is also losing patience faster than it used to, because the products are now mainstream and the excuse of "we are still figuring it out" has run out. The discipline is here. The conventions are converging. The next eighteen months will sort the teams that listened from the teams that did not.

Germany's BGG, BITV, and BFSG: how federal law meets EU technical standards

Disability World — Fri, 22 May 2026 00:00:00 GMT

Image description: The Reichstag's glass Norman Foster dome with the German federal flag flying above — institutional anchor for Germany's BGG, BITV and BFSG accessibility framework.

Reading Time: 13 minutes

Germany's domestic accessibility regime is not one statute but a layered stack of three: the Behindertengleichstellungsgesetz (BGG) — the Federal Act on Equal Opportunities for Persons with Disabilities, in force since 1 May 2002 and substantially reformed in 2016; the Barrierefreie-Informationstechnik-Verordnung (BITV 2.0) — the federal Accessible Information Technology Ordinance, in force in its current "2.0" form since 2011 and re-aligned to EN 301 549 / WCAG 2.1 AA through successive amendments; and the Barrierefreiheitsstärkungsgesetz (BFSG) — the Accessibility Strengthening Act of 16 July 2021, which transposes the EU's European Accessibility Act (Directive 2019/882) into German federal law and switched on for the private sector on 28 June 2025. The layers do not collapse into each other: BGG covers federal public bodies, BITV gives the technical detail, and BFSG covers private-sector consumer products and services. For situating these alongside other Member State transpositions, see the national disability-rights regulations index and the explainer on EN 301 549, the harmonised standard all three German instruments lean on.

This primer walks the stack in order — BGG's general non-discrimination duty, BITV 2.0's technical implementation, BFSG's EAA transposition, the new BAFA federal enforcement role in force since June 2025, and the parallel Länder-level laws (Landesgleichstellungsgesetze) that cover state and municipal authorities across the sixteen federal states. Read the layers separately, because the obligations, the addressees, and the enforcement routes are different at each layer.

The BGG — the federal anchor (2002, reformed 2016)

The Behindertengleichstellungsgesetz (Federal Act on Equal Opportunities for Persons with Disabilities) is the foundational German federal statute on disability equality. It entered into force on 1 May 2002 as part of a wave of post-CRPD-anticipating reform that also delivered Book IX of the Sozialgesetzbuch (SGB IX) on rehabilitation and participation. The 2002 BGG installed three load-bearing concepts into German federal law: a statutory definition of Barrierefreiheit (accessibility) in §4, a binding duty on federal public authorities to act accessibly in §§7–11, and a Verbandsklagerecht (associational standing) in §13 that lets recognised disability organisations bring suit in their own name.

The reform of 2016 — drafted to align the BGG with the UN Convention on the Rights of Persons with Disabilities, which Germany ratified in 2009 — added or strengthened several mechanisms: a duty to provide reasonable accommodation in administrative procedures (§7(2)), explicit recognition of deaf-blindness as a disability category (§3), a federal monitoring body (the Bundesfachstelle für Barrierefreiheit) established at the German Pension Insurance Knappschaft-Bahn-See in §13a, and an arbitration board (Schlichtungsstelle) at the Federal Government Commissioner for Matters relating to Persons with Disabilities under §16. The 2016 reform also pulled in the Leichte Sprache (Easy-to-Read German) duty under §11 and required federal authorities to communicate accessibly in Deutsche Gebärdensprache (DGS, German Sign Language) under §9.

Who BGG actually binds

The BGG's addressee scope is narrower than a first read suggests. It binds federal public authorities (Bundesbehörden), corporations and institutions under federal public law, and — critically — federally-funded entities receiving more than 50 percent of their funding from federal sources. It does not bind Länder authorities, municipal authorities, or private actors. Land authorities are covered by sixteen parallel state statutes; private actors fall under the General Equal Treatment Act (AGG, 2006) for non-discrimination and, since 2025, under BFSG for accessibility of consumer products and services. The BGG is the federal-public-sector floor; the rest of the building sits on top of or beside it.

The Verbandsklage right

One BGG feature that distinguishes the German regime from many EU peers is §13's associational standing right. Recognised disability organisations — currently around 80 organisations on the federal list maintained by the Federal Ministry of Labour and Social Affairs (BMAS) — can sue federal authorities for breach of the BGG without identifying an individually-affected complainant. The right has been used sparingly but visibly: the Deutscher Behindertenrat and member organisations have brought a handful of cases each cycle, mostly aimed at accessible procurement and digital-service deficits. Associational standing reduces the friction the individual-complaint route otherwise imposes — the cost, the disclosure exposure, and the slow administrative-court calendar.

BITV 2.0 — the technical ordinance

The Barrierefreie-Informationstechnik-Verordnung (Accessible Information Technology Ordinance) is the implementing ordinance issued under §12 of the BGG. The first BITV took effect in 2002 alongside the parent statute; the current BITV 2.0 entered into force on 22 September 2011 and has been amended in 2019 (to align with the EU Web Accessibility Directive 2016/2102 and EN 301 549 v3.1.1) and again in 2023 (to track EN 301 549 v3.2.1 and clarify mobile-application coverage). BITV is the layer that names a specific technical standard and binds federal public-sector websites, intranets, and mobile applications to comply with it.

In its current form BITV 2.0 incorporates EN 301 549 V3.2.1 by reference — the harmonised European standard for ICT accessibility — which in turn embeds WCAG 2.1 Level AA for web content and mobile applications. The ordinance also imposes German-specific duties beyond EN 301 549: an explicit obligation in §4 to provide information in Easy-to-Read German (Leichte Sprache) and in German Sign Language (DGS) on home pages of federal authorities, a feedback-mechanism duty in §12b, and accessibility-statement publication requirements in §12c that mirror Article 7 of the Web Accessibility Directive.

Who BITV binds, and what it covers

BITV's scope tracks BGG's: federal authorities, federally-funded corporations under public law, and — via Member-State transposition of Directive 2016/2102 — federal courts and federal legislative bodies in their administrative capacity. Federal websites must publish an accessibility statement and a feedback mechanism, and the Überwachungsstelle des Bundes für Barrierefreiheit von Informationstechnik (BFIT-Bund, the federal monitoring body for IT accessibility, hosted at BMAS) carries out periodic monitoring and reports to the European Commission on a three-year cycle. The most recent federal monitoring report, covering 2022–24, sampled roughly 200 websites and 60 mobile applications and found persistent gaps on keyboard navigation, alternative text, video captioning of older content, and the publication of accessibility statements in conforming form.

Land-level public-sector ICT is covered by sixteen parallel Land-level BITV-equivalents — sometimes called BITV-Landes-X — issued under each Land's own equal-opportunities statute. These mirror BITV 2.0 closely in technical content but vary on monitoring cadence and on whether the Land or the federal monitoring body is competent.

BFSG — the EAA transposition, switched on June 2025

The Barrierefreiheitsstärkungsgesetz (BFSG) — the Accessibility Strengthening Act — was adopted on 16 July 2021 and entered into force in stages, with the operative date for in-scope private-sector products and services set at 28 June 2025, the EAA's harmonised application date. The BFSG transposes Directive (EU) 2019/882 — the European Accessibility Act — into German federal law. Where the BGG covers federal public authorities and BITV gives the technical detail for federal-public-sector ICT, the BFSG is the first general federal statute that binds private-sector economic operators on accessibility of consumer-facing products and services.

What the BFSG covers

The product and service scope follows the EAA verbatim, with the addressee structure adapted to German federal law. The covered products include consumer-grade general-purpose computer hardware and operating systems, self-service terminals (ATMs, ticketing machines, check-in kiosks), consumer terminal equipment for electronic communications and audiovisual media services (set-top boxes, smartphones, smart TVs), and e-readers. The covered services include consumer banking services, electronic communications services, services giving access to audiovisual media, passenger transport information services (web/mobile/self-service-terminal components), e-commerce, and e-books.

Economic operators bound: manufacturers, importers and distributors of in-scope products; service providers offering in-scope services to consumers in Germany.
Microenterprise carve-out: consistent with EAA Article 4(5), service-providing microenterprises (fewer than 10 employees and turnover or balance-sheet total ≤ €2 million) are exempt from the service obligations but must keep documentation of their microenterprise status; the product carve-out does not apply.
Disproportionate burden defence: available under §17 BFSG, subject to a documented assessment that follows Annex VI of the EAA.
Fundamental-alteration defence: available where compliance would require a change to the basic nature of the product or service.
Transitional period: contracts concluded before 28 June 2025 and self-service terminals already in use on that date benefit from a transition window of up to five years for the contract and up to fifteen years for the terminal hardware (BFSG §38).

The technical accessibility requirements that products and services must meet are set out in the implementing ordinance, the BFSGV (Barrierefreiheitsstärkungsgesetz-Verordnung) of 15 June 2022, which references EN 301 549 for ICT components and the relevant harmonised standards for other product classes. Where a harmonised standard does not yet exist, conformity may be demonstrated through the EAA functional accessibility requirements directly, mirroring Annex I.

BAFA and the market-surveillance turn-on

The most consequential shift in 2025 was not the statute taking legal effect — that was 2021. It was the operative market-surveillance turn-on on 28 June 2025. Under §19 BFSG, market-surveillance authority over BFSG-covered products sits with the Bundesamt für Wirtschaft und Ausfuhrkontrolle (BAFA) — the Federal Office for Economic Affairs and Export Control, headquartered in Eschborn. For BFSG-covered services, competence is distributed: the Bundesnetzagentur (BNetzA) for electronic communications services, the BaFin for consumer banking, the Landesmedienanstalten for audiovisual-media access services, and — for e-commerce, e-books, and passenger-transport information services — the Länder market-surveillance authorities coordinating through a federal-Länder forum convened by BMAS.

BAFA's mandate runs from market-entry conformity checks on products through to administrative-fine proceedings under §37 BFSG. Fines can reach up to €100,000 per violation, with the upper limit applied per affected product line or service in repeat-offender cases. Beyond fines, BAFA can order products withdrawn from the market or recalled where non-compliance creates a "significant risk" — a phrase borrowed from the General Product Safety Regulation (Regulation (EU) 2023/988) market-surveillance architecture. BAFA also publishes annual market-surveillance reports identifying the product categories with the highest non-compliance rates; the first BFSG-cycle report is due in late 2026.

No private right of action for damages

The BFSG does not, by itself, create a private right of action for monetary damages. Consumers can file complaints with BAFA, BNetzA or the relevant service authority, who decide whether to open proceedings. Recognised consumer-protection associations and disability organisations have collective-action rights under §22 BFSG that mirror the EU Representative Actions Directive (Directive (EU) 2020/1828, transposed into German law as the VDuG, in force since October 2023). The collective-action route is the part of the German private-sector enforcement architecture most likely to produce visible case law in 2026–27.

The Länder layer — sixteen parallel statutes

Germany's federal structure means that public-sector accessibility for the Länder and their municipalities is governed by sixteen separate Land-level Landesgleichstellungsgesetze (LGGs), each with its own scope, its own monitoring body, and its own technical ordinance. Bavaria's BayBGG (2003, revised 2018), North Rhine-Westphalia's BGG NRW (2004, revised 2016), Berlin's LGBG (1999, revised 2021), Hamburg's HmbBGG (2005, revised 2020), and Saxony's SächsInklusG (2018) are the most-cited examples; the Schleswig-Holstein, Lower Saxony, Hesse and Baden-Württemberg statutes round out the larger Länder.

Most LGGs follow the BGG's structural template — defined accessibility duty, Verbandsklage right, language and communication provisions for DGS and Easy-to-Read — but the technical implementation differs. Some Länder issue their own BITV-equivalent ordinance; some incorporate BITV 2.0 by reference; one or two leave the technical layer underspecified, with the result that municipal-website compliance is uneven across the Land. The 2024 federal monitoring report flagged this asymmetry: federal-public-sector ICT compliance is meaningfully higher than Länder-municipal compliance, primarily because BFIT-Bund's monitoring cadence at federal level is not matched at every Land level.

How the three layers actually interact

In practice a German entity classifying its accessibility obligation in 2026 should walk three questions in order. First, is it a federal public authority, a federal corporation under public law, or a federally-funded entity above the 50-percent threshold? If yes, BGG applies, BITV 2.0 sets the technical standard, and BFIT-Bund monitors. Second, is it a Land or municipal authority, or a Land-funded entity? If yes, the relevant LGG and its technical ordinance apply, monitored by the Land's own equivalent body. Third, is it a private-sector economic operator placing in-scope products or providing in-scope services to consumers in Germany? If yes, BFSG and BFSGV apply, with BAFA, BNetzA, BaFin or a Land market-surveillance authority competent depending on the product or service.

A private hospital that receives 60 percent federal funding could be in two layers at once: BGG (because of the federal funding threshold) and, for its consumer-facing online services, BFSG. The compliance obligations overlap rather than collide — both layers ultimately point at EN 301 549 / WCAG 2.1 AA for digital interfaces — but the enforcement routes differ. A BGG violation goes to the BMAS arbitration board or the administrative courts via Verbandsklage; a BFSG violation goes to BAFA or BNetzA.

The EN 301 549 / WCAG anchor across all three

The unifying technical anchor across BGG, BITV and BFSG is the EU's harmonised standard EN 301 549 V3.2.1, which itself embeds WCAG 2.1 Level AA for web content and mobile applications. This is what gives the German layered architecture coherence in practice: a single technical standard runs through the federal-public-sector layer (via BITV 2.0), the Länder public-sector layer (via Land BITV-equivalents), and the private-sector layer (via BFSG/BFSGV). When a future German implementing ordinance lifts the technical standard to WCAG 2.2 AA, all three layers will move together — there is no plausible scenario in which BFSG moves to 2.2 while BITV stays at 2.1, because BITV references the same harmonised standard BFSGV references.

Practical implications for businesses operating in Germany

Three concrete implications follow for organisations whose German operations crossed the 28 June 2025 BFSG threshold. First, the disproportionate-burden defence in §17 BFSG is documented, not declared — operators relying on it must produce an Annex-VI-style assessment that BAFA can request. Second, the microenterprise carve-out applies to services only; manufacturers and importers of in-scope products cannot fall back on it regardless of headcount. Third, the BFSG accessibility statement is mandatory for in-scope services and must be published in a structured form on the operator's primary consumer-facing surface; the first BAFA spot-checks in the second half of 2025 reportedly focused on whether statements existed at all rather than on substantive conformity, with substantive conformity expected to dominate the 2026 cycle.

For federal public bodies and federally-funded entities, the practical priority in 2026 is closing the gaps the BFIT-Bund 2022–24 monitoring report flagged: keyboard navigation on transactional flows, alternative text on imagery, captioning of older video content, and accessibility-statement form. For Land and municipal entities, the priority is whichever LGG-monitoring cycle is current.

Conclusion: a layered regime, anchored to one standard

Germany's three-statute layered architecture looks complex from outside because it is — a federal BGG and an implementing BITV from 2002, sixteen Land statutes covering the public sector, and a BFSG transposing the EAA into the private sector since 2021. What makes the regime workable in practice is that all three layers anchor to the same harmonised European technical standard, EN 301 549, which embeds WCAG 2.1 AA for digital interfaces and runs through every layer of the stack. The 2025 BAFA market-surveillance turn-on under BFSG is the change that puts a federal regulator on the private-sector side for the first time, with administrative fines up to €100,000 per violation and collective-action exposure through VDuG. The doctrine and the addressees were already in place; the enforcement mechanism is what 2026 onwards will test.

Read more from Disability World on the European Accessibility Act and Member State transpositions, on the EN 301 549 harmonised standard, and across the 2026 regulatory record.

Primary sources

Bundesministerium der Justiz. Behindertengleichstellungsgesetz (BGG), in force since 1 May 2002, as amended by the Federal Participation Act of 2016. gesetze-im-internet.de/bgg
Bundesministerium der Justiz. Barrierefreie-Informationstechnik-Verordnung (BITV 2.0), in force since 22 September 2011, latest amendment 2023. gesetze-im-internet.de/bitv_2_0
Bundesministerium der Justiz. Barrierefreiheitsstärkungsgesetz (BFSG), of 16 July 2021, BGBl. I p. 2970, operative for in-scope products and services from 28 June 2025. gesetze-im-internet.de/bfsg
Bundesministerium der Justiz. Barrierefreiheitsstärkungsgesetz-Verordnung (BFSGV), of 15 June 2022. gesetze-im-internet.de/bfsgv
Überwachungsstelle des Bundes für Barrierefreiheit von Informationstechnik (BFIT-Bund). Federal monitoring report on the accessibility of public-sector websites and mobile applications, 2022–2024. bfit-bund.de
Bundesamt für Wirtschaft und Ausfuhrkontrolle (BAFA). BFSG market surveillance information for economic operators (2025). bafa.de
European Union. Directive (EU) 2019/882 on the accessibility requirements for products and services (European Accessibility Act), OJ L 151, 7.6.2019.
European Union. Directive (EU) 2016/2102 on the accessibility of the websites and mobile applications of public sector bodies, OJ L 327, 2.12.2016.
ETSI / CEN / CENELEC. EN 301 549 V3.2.1 — Accessibility requirements for ICT products and services (March 2021).

The state of global disability metrics in 2026: what gets counted, what doesn't, and why the gap keeps closing slowly

Disability World — Fri, 22 May 2026 00:00:00 GMT

Data dossier · Measurement infrastructure

The state of global disability metrics in 2026 — what gets counted, what doesn't, and why the gap keeps closing slowly

Two decades after the Washington Group on Disability Statistics published its Short Set on Functioning, the world finally has a defensible headline number: 1.3 billion people, roughly 16% of the global population, living with significant disability, per the WHO's 2024 monitoring update to the World Report on Disability. That figure rests on a measurement infrastructure that took twenty years to build — and still misses four populations almost entirely. Fifty-five-plus national statistical offices now run the Washington Group Short Set; more than 90 LMICs publish UNICEF/WG Child Functioning Module data; the 2025 UN DESA Compendium maps around 120 countries producing at least some disability-disaggregated SDG indicator reporting. The headline is firmer than it has ever been. What still slips through it is what the rest of this dossier is about.

Findings · Case file 01 06 findings · derived from WHO 2024, WG Secretariat inventory, UN DESA Compendium 2025

What the 2026 measurement infrastructure reveals

01 1.3B

The WHO 2024 update puts global disability at 1.3 billion people — the firmest headline the field has ever had

Functional limitation, not condition-by-condition Global Burden of Disease accounting, is now the primary frame. Of the 1.3 billion, around 190 million adults experience very significant difficulty in functioning — a sub-figure that has barely moved since the 2011 report.
02 16%

Global prevalence climbed from about 15% in 2011 to roughly 16% in 2024

The world has not become "more disabled" — measurement has improved, the over-60 population has grown by nearly 240 million in 13 years, and chronic-disease prevalence has expanded faster than population growth in South Asia and sub-Saharan Africa.
03 55+

More than 55 national statistical offices now deploy the Washington Group Short Set in census or flagship survey

Out of roughly 200 jurisdictions running decennial or quinquennial censuses. Most of Latin America, an expanding number of African NSOs, several large Asian countries, and a slowly growing share of OECD high-income members.
04 approx. 10%

Around 1 in 10 children aged 5–17 in LMICs has a disability under the Child Functioning Module

UNICEF's 2024 Seen, Counted, Included update aggregates CFM-based prevalence estimates from more than 90 LMICs — the broadest comparable child-disability dataset that has ever existed. Substantially higher than legacy estimates.
05 4 gaps

Four populations remain systematically under-counted, even in the best-instrumented surveys

Children under 2 (no standardised instrument exists). People in residential institutions, prisons, refugee camps (excluded from household sampling frames). Persons with intellectual or psychosocial disabilities (Extended Set runs in fewer than two dozen countries). The 117 million-plus forcibly displaced (almost no NSO sampling frame reaches them).
06 2.2 → 17.8

National prevalence ranges from 2.2% (India, legacy single-question) to 17.8% (UK, GSS harmonised + WG)

Bangladesh 2.8%, South Africa 6.0%, Brazil 8.9%, US 13.4%, Mexico 16.5%. Most of the spread is instrument, threshold, and aggregation choice — not underlying epidemiology. The 2024 WG guidance now recommends reporting at least two thresholds in parallel.

SourceWHO World Report on Disability (2011) and 2024 monitoring update; Washington Group Secretariat 2024 country-deployment inventory; UN DESA Disability Statistics Compendium 2025; UNICEF/WG Module on Child Functioning, Seen, Counted, Included 2024 update; national census releases (IBGE 2022, Stats SA 2022, INEGI 2020, ONS 2021/22, BBS 2022).

In this dossier

01How disability is being counted in 2026
02The headline number: 1.3B and 16%
03Washington Group Short Set adoption
04Children: the CFM and the under-2 gap
05What still isn't well-counted
06The double-counting debate, in four countries
07SDG 17.18.1 and the 2025 Compendium
082026 outlook and the through line

01 · How disability is being counted in 2026

Three things changed between the 2011 World Report on Disability and the WHO's 2024 monitoring update, and they all push the global prevalence figure in the same direction. The world is older — the over-60 population has grown by close to 240 million in 13 years, and significant functional limitation rises steeply after 60. Chronic-disease prevalence, particularly type-2 diabetes and its sequelae, has expanded faster than population growth across South Asia and sub-Saharan Africa. And measurement itself has improved: the Washington Group instruments, the UNICEF/WG Module on Child Functioning, and the Model Disability Survey have matured into reference tools that produce higher and more reliable counts than the legacy "do you have a disability?" yes/no question they replaced.

approx. 1.3B

People with significant disability worldwide (WHO 2024)

16%

Global prevalence in 2024 — up from approx. 15% in 2011

190M

Adults with very significant difficulty in functioning

Why "16%" is a floor, not a ceiling

The WHO's 16% prevalence figure is best read as the floor of a defensible estimate, not as a discovery that the world has somehow become more disabled in 13 years. The 2024 update treats functional limitation as the primary frame — the 2011 report leaned on the Global Burden of Disease (GBD) framework, years lived with disability by specific cause, but the 2024 update keeps GBD as an appendix rather than the headline. A functional-limitation count and a condition-by-condition count are not the same population: conflating them double-counts people who appear in several condition rows and undercounts people whose limitations have no neat ICD-11 home.

02 · The headline number, and what it actually measures

The WHO's 16% prevalence figure (roughly 1.3 billion people) is therefore best read as the floor of a defensible estimate, not as a discovery that the world has somehow become more disabled in 13 years. Of that 1.3 billion, the 2024 update splits out around 190 million adults with very significant difficulties in functioning — the population for whom rehabilitative services, assistive technology, and personal-assistance entitlements are most plainly indicated and least adequately delivered. That sub-figure has barely moved between the 2011 and 2024 reports, which is itself a finding.

The number you do not see in the WHO headline is impairment-by-condition. The 2011 report leaned on the Global Burden of Disease (GBD) framework — years lived with disability by specific cause — and the 2024 update keeps GBD as an appendix rather than the headline. A functional-limitation count and a condition-by-condition count are not the same population: conflating them double-counts people who appear in several condition rows and undercounts people whose limitations have no neat ICD-11 home. The 2024 update treats functional limitation as the primary frame.

Reported national prevalence — most recent census or flagship survey

India · 2011 Census

2.2% · legacy single-Q

Bangladesh · 2022

2.8% · WG-SS (narrow)

South Africa · 2022

6.0% · WG-SS

Brazil · 2022

8.9% · WG-SS (adapted)

United States · 2023

13.4% · WG-derived 6-Q

Mexico · 2020

16.5% · WG-SS (broad)

United Kingdom · 2021/22

17.8% · GSS + WG

The range — 2.2% to 17.8% — is what the field's long debate over comparability is actually about. It is not, mostly, that disability is genuinely seven times more common in the UK than in India. The instrument, the threshold at which someone is counted (some difficulty? a lot?), the inclusion or exclusion of people in institutions, and respondents' willingness to self-identify all move the number more than the underlying epidemiology does. Where the WG-SS is deployed consistently — across most of Latin America in particular — cross-country numbers now sit in a far tighter band than a decade ago.

03 · The Washington Group instruments and where they actually run

The Washington Group Short Set's six functional-domain questions are the canonical instrument behind the 16% global prevalence figure: seeing, hearing, walking, cognition, self-care, communication.

The Washington Group Short Set on Functioning (WG-SS) is six questions: difficulties seeing, hearing, walking or climbing steps, remembering or concentrating, self-care, and communicating, each on a four-point severity scale (no difficulty, some, a lot, cannot do at all). It was designed in the mid-2000s to be short enough to bolt onto a national census, neutral enough to translate across cultures, and severity-graded enough to support cross-country comparison if used consistently. The Washington Group Secretariat's 2024 inventory counts more than 55 national statistical offices that have deployed WG-SS verbatim or near-verbatim in their most recent census or flagship household survey.

"More than 55" sounds modest, and it is. There are around 200 jurisdictions that run a decennial or quinquennial census. The WG-SS users include most of Latin America, an expanding number of African NSOs, several large Asian countries, and a slowly growing share of OECD high-income members. Non-users split between countries that still rely on a legacy "are you a person with a disability?" single question (common in parts of South and Southeast Asia and several Gulf states), countries running a national instrument designed before WG-SS existed (the UK's ONS uses the GSS harmonised disability question alongside WG-style questions), and countries whose most recent census predates the Washington Group's last revision.

WG-SS adoption density by region — 2024 Washington Group Secretariat inventory (illustrative)

Latin America

Most NSOs · verbatim or near-verbatim

Sub-Saharan Africa

Expanding adoption

OECD high-income

Slow, often hybridised with national instruments

East & Southeast Asia

Mixed — several large NSOs adopting

South Asia

Mostly legacy single-Q, some pilots

Gulf & West Asia

Legacy frameworks dominant

04 · The child-functioning instrument

For children, the canonical instrument is the Washington Group / UNICEF Module on Child Functioning (CFM), finalised in 2016 and now the reference module for the 2–4 and 5–17 age bands. UNICEF's MICS (Multiple Indicator Cluster Survey) programme has included the CFM by default since MICS6; the 2024 global release carries CFM-based prevalence estimates from more than 90 low- and middle-income countries, the broadest comparable child-disability dataset that has ever existed. UNICEF's 2024 Seen, Counted, Included update reports that around 1 in 10 children aged 5–17 in LMICs has a disability under the CFM definition — substantially higher than legacy estimates, and consistent with the WHO's directional adjustment. The CFM has no analogue for children under 2: the developmental-milestone variation in the 0–24 month band is too wide for a short module to be useful, and that gap is the first of four populations the 2026 measurement infrastructure does not adequately count.

approx. 80% of LMIC deaf children remain out of school

UNESCO's Global Education Monitoring (GEM) Report has, for several editions running, estimated that around 80% of deaf children in low- and middle-income countries are out of school. The CFM finally lets countries count these children — but counting is only the first step. Where the data exists, ministries of education have not yet built the inclusive-education infrastructure to act on it.

05 · The populations the headline numbers still miss

Four groups remain systematically under-counted even in the best-instrumented national surveys.

People in institutions

Most household-survey sampling frames exclude residential institutions, long-stay psychiatric facilities, prisons, and refugee camps — populations in which disability prevalence, particularly psychosocial and intellectual disability, is dramatically elevated. The European Commission's 2023 institutional-population mapping found around 1.4 million Europeans in residential disability institutions alone, none of whom appear in standard household-survey estimates. UN DESA's 2025 Compendium calls the exclusion a "first-order undercount" in its methodology annex.

Persons with intellectual or psychosocial disabilities

The six WG-SS questions are functional-domain questions and good at picking up what they cover. Intellectual disability shows up partially through "remembering or concentrating"; psychosocial disability shows up partially through "communicating" and partially nowhere. The Washington Group's Extended Set and the WG-SS Enhanced module add questions on anxiety, depression, upper-body function, and fatigue, but Enhanced is in use in fewer than two dozen countries as of 2024. The WHO 2024 update flags this as the single largest measurement gap in the current instrument family.

Children under 2

The CFM begins at age 2 and no internationally standardised instrument exists for younger children. UNICEF and the WHO's Early Childhood Development team have piloted a hybrid clinical-screening approach in seven countries since 2023, but the work is methodological rather than ready for national rollout.

People in conflict-affected and displacement settings

UNHCR's 2024 mid-year statistical release counts more than 117 million forcibly displaced people worldwide. On the limited evidence available, disability prevalence in displaced populations runs substantially higher than in settled populations of the same origin — a function of injury, deprivation, and the differential mobility of disabled people in crisis. Almost no NSO's sampling frame covers displaced populations adequately. The Humanitarian Inclusion Standards working group has been pressing UNHCR and IOM since 2022 to embed WG-SS in registration intake, with patchy results.

The instruments exist. The question, as in so much of disability policy, is whether the data will be collected.

06 · The double-counting debate, in four countries

The single most contested operational question in disability statistics in 2026 is also the most technical-sounding: when you ask the six WG-SS questions, and a respondent reports difficulty in more than one domain, do you count them once at the highest severity, once at any severity above the threshold, or do you sum the severity scores? National statistical offices treat this differently — and the difference moves the headline number by several percentage points.

Washington Group Secretariat · methodological note · 2024

"The Short Set was designed so that a country could report a defensible national disability prevalence. It was not designed to allow easy comparison between two countries that have made different threshold and aggregation choices. We are still working on that."

Washington Group on Disability Statistics, 2024 guidance update

Bangladesh's 2022 census reported 2.8% using a "lot of difficulty / cannot do at all" threshold and a highest-domain rule — the conservative end of the WG-SS spectrum. South Africa's 2022 census used the same instrument with a more inclusive threshold (some difficulty in two or more domains, or a lot in one) and reported 6.0%. Brazil's IBGE Census applied a moderately inclusive threshold and reported 8.9%. Mexico's INEGI captures any reported "some difficulty" in any domain alongside the more restrictive tier, and reports 16.5% — close to the WHO global figure, far higher than its South Asian neighbours using ostensibly the same instrument.

Bangladesh · BBS 2022 Census

WG-SS · narrow threshold (lot of difficulty / cannot do)

2.8%

South Africa · Stats SA 2022 Census

WG-SS · moderate threshold (some in 2+ or a lot in 1)

6.0%

Brazil · IBGE 2022 Census

WG-SS adapted · moderately inclusive threshold

8.9%

Mexico · INEGI 2020 Census

WG-SS · inclusive (any "some difficulty" + restrictive tier)

16.5%

None of these offices is wrong. Each has defended its choice in publicly available methodology and each has reasons rooted in previous-cycle data continuity. The Washington Group's 2024 guidance, for the first time, recommends reporting at least two thresholds in parallel — a "narrow" count at the highest severity and a "broad" count including some-difficulty responses — precisely so the cross-country comparison becomes possible.

07 · SDG-disaggregated reporting and the 2025 Compendium

The UN's Sustainable Development Goal Indicator 17.18.1 tracks the share of indicators in the SDG framework that are disaggregated by, among other things, disability. The UN DESA Disability Statistics Compendium first published in 2018, with major updates in 2022 and most recently 2025, is the field's single best inventory of which countries are producing what.

The 2025 Compendium's headline finding is that around 120 countries now produce at least some disability-disaggregated SDG indicator reporting — up from 76 in the 2018 baseline. Depth is variable: most report disability-disaggregated education-attainment data (SDG 4.5.1) and labour-force-participation data (SDG 8.5), far fewer report disability-disaggregated maternal-health, justice-system, or political-participation data, and almost none report disability-disaggregated climate-resilience indicators. The 2025 Sendai Framework mid-term review called this gap out: disaster-risk-reduction reporting under SDG 11.5 and 13.1 remains very thin on disability disaggregation, despite Sendai's own 2015 commitment.

120

Countries producing some disability-disaggregated SDG reporting (2025)

Countries doing the same in the 2018 baseline

approx. 0

Countries with disability-disaggregated climate-resilience data

08 · What changed in 2025–26 and what 2026 still misses

Three concrete developments are reshaping the 2026 measurement landscape. First, the WHO 2024 monitoring update reset the headline to 1.3 billion and 16% and made functional limitation the primary frame; reporting in any other frame now requires extra justification. Second, the UN DESA 2025 Compendium published the first country-by-country matrix of disability-disaggregated SDG indicator reporting — making gap-mapping straightforward for donors and civil society in a way it was not before. Third, the Washington Group Secretariat's 2024 inventory has begun publishing not just whether a country uses WG-SS, but how — which threshold it applies, whether it deploys the Extended Set or Enhanced module, and whether its micro-data is publicly available for re-analysis. The 2025 update added nine new countries, including the first publicly funded micro-data release from a major South Asian NSO.

Three structural blind spots are unlikely to close on the current trajectory.

Comparable institutional-population data. The European Commission's 2023 mapping is the closest any region has come; no comparable global dataset exists. Without it, the 16% headline misses tens of millions of people whose prevalence is the highest of any sub-population the field counts.
Comparable psychosocial-disability prevalence. The Extended Set and WG-SS Enhanced have the questions; deployment runs at a fraction of the WG-SS user base. Until that catches up, the global figure systematically undercounts the population whose access barriers most plainly require non-physical accommodations.
Disability-disaggregated climate and disaster data. The Sendai Framework's 2015 commitment to disability-disaggregated DRR reporting is, in 2026, almost entirely unmet outside a handful of pilot countries. As climate-driven disaster frequency continues to rise, this is becoming the single largest gap in the SDG-disaggregation matrix.

What good measurement looks like in 2026

The national statistical offices producing the most defensible disability data share four practices, not one: they use the WG-SS in a verbatim or near-verbatim form; they report at least two thresholds in parallel (narrow and broad); they release micro-data publicly at a level that permits independent re-analysis; and they cover institutional populations and displaced populations through dedicated supplementary modules rather than excluding them from the sampling frame. Stats SA, IBGE Brazil, INEGI Mexico, and ONS UK are the offices closest to this benchmark in 2026. Most others are not.

The through line

Two decades after the Washington Group published the Short Set, global disability prevalence is finally being counted in a way that produces defensible, broadly comparable numbers — 16%, around 1.3 billion people, with around 190 million adults experiencing very significant difficulties. The 2024 WHO update and the 2025 UN DESA Compendium have aligned around that frame. What remains is the long tail of populations the headline misses: people in institutions, children under 2, displaced populations, and people with intellectual or psychosocial disabilities whom the six functional-domain questions only partly capture. Closing those gaps is a national-statistics-office investment decision, not a research problem. The instruments exist. The question, as in so much of disability policy, is whether the data will be collected.

Read more from Disability World on the CRPD, on national regulations, and on the wider 2026 reporting record.

Inclusive typography: dyslexia-friendly fonts, line height, and word spacing

Disability World — Fri, 22 May 2026 00:00:00 GMT

Image description: A typography specimen book showing different sans-serif typefaces with a leading-ruler and reading glasses on top — the visual marker for inclusive typography.

By Disability World editorial desk Updated May 2026 Reading time 9 minutes

Reading Time: 9 minutes

Type is the layer of a digital product most readers never consciously notice — until it fails them. For a dyslexic reader, a low-vision reader, or a reader with attention-deficit traits, the difference between a comfortable page and an exhausting one is often measured in millimetres of leading, hundredths of an em of letter-spacing, and a font-size value set in the stylesheet six months ago and never revisited. Inclusive typography is the discipline of choosing those values on the basis of what the readability evidence actually supports, rather than what looks "designerly" in the cover shot of a portfolio.

This primer maps the field as it stands in 2026. It covers font choice — including the well-known but evidence-thin claim around OpenDyslexic, and the more defensible alternatives in Atkinson Hyperlegible and the Tiresias family. It walks through the four numeric levers locked in by WCAG 2.2 Success Criterion 1.4.12 Text Spacing: line height, letter-spacing, word-spacing, and paragraph spacing. And it closes on the underrated levers that the research keeps pointing back to — line length, alignment, and a sane minimum font-size. What works for low-vision readers, the evidence shows, overlaps significantly with what works for dyslexic readers and for readers with ADHD-pattern attention.

Font choice: what the research says (and does not say)

There is a strong popular belief that a "dyslexia font" exists and that switching to one will materially improve reading for dyslexic users. The two faces most often named are OpenDyslexic (released as a free open-source typeface in 2011) and Dyslexie (a commercial face designed by Christian Boer in 2008). Both share a distinctive design strategy: weighted bottoms on each glyph to "anchor" letters to the baseline, exaggerated openings on letters like c and e, and increased differentiation between mirror-image pairs (b/d, p/q, n/u). The visual logic is intuitive and the marketing has been effective. The evidence, however, is thinner than the marketing suggests.

The most-cited empirical study — Rello and Baeza-Yates (2013) — found no significant reading-speed advantage for dyslexic readers using OpenDyslexic compared with conventional sans-serif faces. A follow-up by Wery and Diliberto (2017) in Annals of Dyslexia tested children with dyslexia reading in Times New Roman, Arial, and OpenDyslexic and found no consistent gain for the dyslexia-specific face. A 2018 review by the British Dyslexia Association concluded that no single typeface had been demonstrated to outperform a well-designed, plain sans-serif for dyslexic readers across reading speed, accuracy, and comprehension at a level that justified prescribing it as a remediation tool. The 2024 follow-up commentary by the same association reaffirmed the position.

What the same research base does support is that type design choices matter, just not in the way the dyslexia-font marketing claims. The features that improve readability for dyslexic readers are the same features that improve readability for low-vision readers and for readers reading in sub-optimal lighting:

Generous x-height — the height of the lowercase body relative to the cap height. A larger x-height makes individual glyphs easier to identify at smaller display sizes.
Unambiguous letterforms — clear distinction between the lowercase l, uppercase I, and numeral 1; between zero and capital O; between c, e, and o; and between mirror pairs b/d and p/q.
Open apertures — the gaps in letters like c, e, a, and s should be wide open, not closed-up. Closed apertures collapse at small sizes and in low contrast.
Even stroke weight — high-contrast typefaces (thick verticals, thin horizontals) reduce legibility at small sizes for low-vision readers; an even or moderately-contrasted stroke is more robust.
Generous spacing as drawn into the font — some faces ship with tight default metrics that fight the reader before any CSS is applied.

The two faces that are most defensible on the evidence are Atkinson Hyperlegible, designed and released by the Braille Institute in 2019 specifically for low-vision readers, and the Tiresias family, originally designed at the RNIB for subtitle and screen use in the 1990s and still in use across UK broadcast accessibility. Atkinson Hyperlegible is free, includes a substantial language coverage, and is shipped as a default option in several operating systems' accessibility settings. Its design choices — exaggerated differentiation between 0 and O, between 1 and I and l, between c and e — were tested with low-vision readers during development, and the same choices help dyslexic readers because the underlying confusion patterns overlap.

The honest summary is therefore: do not promise that a dyslexia-specific font will fix reading for a dyslexic reader. Choose a well-designed sans-serif with a generous x-height, clear letter differentiation, open apertures, and even stroke weight. Atkinson Hyperlegible is a strong default. So is Tiresias for screen-only contexts. So, for that matter, is a well-set version of Verdana, Tahoma, Trebuchet MS, or the system UI font on each operating system. The evidence does not say "use this one face"; it says "do not use a high-contrast, low-x-height, tight-aperture display face for body text."

Line height: the 1.5x floor

If font choice is the most-discussed lever in inclusive typography, line height is the most-underused. WCAG 2.2 Success Criterion 1.4.12 Text Spacing makes the floor explicit: when a user applies a stylesheet override to increase text spacing, no content or functionality should be lost. The four constraints in 1.4.12 are line height of at least 1.5 times the font size; spacing following paragraphs of at least 2 times the font size; letter-spacing of at least 0.12 times the font size; and word-spacing of at least 0.16 times the font size. These are the minimum values the page must accommodate without breaking. They are not, however, the only values worth knowing — they are the lower bound of acceptable.

The mechanism by which line height helps readers is well-studied. When lines are set tight — leading of 1.0 or 1.1 — the descenders of one line crowd the ascenders of the next, creating visual interference that the eye must resolve before it can identify glyph shapes. For a typically-reading adult this resolution is automatic. For a dyslexic reader, who already devotes more cognitive bandwidth to letter identification and word segmentation, the additional cost of resolving inter-line interference is non-trivial. The same is true for a low-vision reader whose effective character size after magnification is smaller than the average. Adequate line height isolates each line as its own horizontal band, which reduces the eye's tendency to skip lines or re-read the same line — a documented difficulty for dyslexic readers.

The research base recommends a leading of approximately 1.4 to 1.6 for body text on screen — the precise value depends on font, size, and line length. For long-form reading, leading of 1.5 is a safe default; for shorter text blocks at slightly larger sizes, 1.4 can read well; for narrow columns at small sizes, 1.6 to 1.7 is sometimes warranted. The WCAG floor of 1.5 sits at the lower end of this band, which is why it is a floor, not a target. If a page sets `line-height: 1.5` it complies with 1.4.12. If a page sets `line-height: 1.6` it complies and reads more comfortably for the readers the criterion was written for.

Letter spacing and word spacing

The two spacing levers inside the word — letter-spacing (tracking) and word-spacing — are the levers most often left at zero by default. Most well-designed fonts ship with metrics that work at the size they were designed for, which on screen tends to be a body size of 14–16 px. The WCAG 1.4.12 minima ask that the page accommodate letter-spacing of 0.12em and word-spacing of 0.16em without breaking. Authors are not obliged to set these values; they are obliged not to break when a user agent applies them.

The mechanism for letter-spacing is similar to that of line height: a small amount of tracking — on the order of 0.02em to 0.05em for body text in a sans-serif — reduces the perceptual crowding between adjacent glyphs. The effect is most pronounced for low-vision readers reading magnified text, where letters that touch or nearly touch can merge into a single visual cluster, and for dyslexic readers, for whom letter-identification is the rate-limiting step. The same modest tracking helps in screen environments where sub-pixel rendering is less accurate (high-resolution displays running at non-integer scale factors, for example).

Word-spacing is the often-overlooked sibling. In a justified text block (which inclusive typography should avoid — see below), word-spaces stretch and compress unpredictably as the renderer balances line widths. In a left-aligned block, the word-space is constant. Word-spacing of approximately 0.16em — roughly the WCAG floor when applied as a positive offset — improves word segmentation for dyslexic readers, which is a documented bottleneck. The same value helps text-to-speech preview reading and improves the rhythm of finger-tracking for tactile-magnifier users.

The practical recipe for body text on a content-rich site, in CSS terms, looks like this:

font-size: at least 16px (1rem with a 16px root), preferably 17–18px for long-form prose
line-height: 1.5 minimum, 1.6 preferred for body
letter-spacing: 0 to 0.02em for most sans-serifs; up to 0.05em in slab faces or at small sizes
word-spacing: 0 by default, with the page tested to remain functional at user-applied 0.16em

Paragraph spacing

The fourth value in WCAG 1.4.12 is paragraph spacing: at least 2 times the font size between paragraphs when a user applies the override. The mechanism is visual chunking. The eye reads in saccades — fast jumps between fixation points — and a clearly-demarcated paragraph end lets the eye reset without overshooting into the next paragraph. For a reader with attention-deficit traits, a clear paragraph break is a built-in pause; for a low-vision reader using magnification, it is a structural landmark that survives the loss of horizontal context that magnification imposes.

In practice this means avoiding the common visual-design choice of running paragraphs together with only a tab indent for separation. Indent-only paragraph separation reads well in print at print font sizes and in newspaper columns with strong inter-column rules; it does not survive translation to a 320-wide phone screen at 18px body size. A clear blank line — approximately equal to one line height, which sits comfortably above the 2x font-size floor — is the safer default.

Underrated levers: line length, alignment, and minimum size

Three levers that do not appear in WCAG 1.4.12 but appear repeatedly in the readability literature are line length, text alignment, and minimum font-size. Each of them is invisible until you measure it; each of them has a meaningful effect on dyslexic and low-vision readers.

Line length is the horizontal width of a column of text, conventionally measured in characters per line (CPL). Research from Bringhurst, Tinker, and successive screen-readability studies converges on a comfortable band of 50–75 characters per line for print and 60–80 for screen. Below 45 CPL the eye saccades too often and reading rhythm fragments; above 90 CPL the eye loses track of which line it is on at the right-hand return sweep — a documented difficulty for dyslexic readers and for low-vision readers using magnification. For a 16–18px body size at the recommended line height, this band typically translates to a column of approximately 32–42em (around 500–700 px on a desktop layout). The fact that most blog and editorial sites still set content columns at 800–900 px wide at 16px body — yielding 95–110 CPL — is a meaningful inclusive-design failure.

Text alignment is the second underrated lever. Body text should be set left-aligned in left-to-right scripts (or right-aligned in right-to-left scripts), with a ragged opposite edge. Justified text — where the renderer adjusts inter-word spacing to make both edges flush — creates uneven and unpredictable word-spaces. The variability disrupts word-segmentation for dyslexic readers and produces visible "rivers" of white space running vertically through the column, which low-vision readers report as visually intrusive. Justified text is a print-typography convention that depends on tight CSS or hand-set adjustment of letter-spacing and hyphenation. In modern web typography, the cost is rarely justified. Left-aligned, ragged-right text is the inclusive default.

Minimum font-size is the third. The web has converged, through accident more than intent, on a body size of 16px (1rem with default root sizing). That value is the floor — readers with low vision routinely zoom to 200% or higher, and a 16px floor permits that without the page collapsing. Setting body text smaller than 16px — 13px, 14px, even the much-favoured "elegant" 15px — pushes magnified reading past the 400% reflow ceiling that WCAG 1.4.10 Reflow defines, and it puts unmagnified reading below the comfort threshold for most adults over 40. The body should be 16px minimum, 17–18px preferred. Captions, footnotes, and metadata can sit at 14–15px because their function is supplementary. The body cannot.

What the research actually says

Synthesised across the readability literature of the last two decades — the British Dyslexia Association's style-guide updates, the Atkinson Hyperlegible design rationale published by the Braille Institute, the W3C Working Group Notes that accompany WCAG 1.4.12, and the academic strand running from Tinker through Beier and Larson to Rello — three observations recur.

First, there is no single "dyslexia font" that has been shown to materially improve reading for dyslexic users in controlled trials. The dyslexia-specific faces released over the last fifteen years have not outperformed well-designed plain sans-serifs in head-to-head testing. The marketing has run ahead of the evidence.

Second, the typographic choices that demonstrably help dyslexic readers also help low-vision readers and readers with attention-pattern difficulties. The overlap is not coincidental — it reflects the fact that all three reader groups depend on the same low-level mechanisms (letter identification, word segmentation, line tracking) being made as cheap as possible. A page that is generous in line height, modest in letter-spacing, comfortable in line length, and left-aligned is a page that reads better for everyone, with the effect concentrated at the long tail of the reader distribution.

Third, the WCAG 1.4.12 floor is a floor. A page that meets it is compliant; a page that exceeds it — 1.6 line height, 0.03em tracking, 16-18px body, 65 CPL columns, left-aligned with paragraph breaks of one full line — reads visibly better for the readers the criterion is designed to protect, and reads no worse for everyone else.

What to take away

Inclusive typography is not exotic and it is not expensive. It is a matter of choosing a well-designed sans-serif, setting body text at 16px minimum with line height of 1.5 or more, leaving letter-spacing close to zero and accepting up to 0.05em where the font calls for it, holding line length in the 60–80 character band, and setting text left-aligned rather than justified. None of those choices require a new font licence, a redesign, or a procurement cycle. They require a CSS audit and the willingness to revisit the typography variables that were set on day one of the project and never reviewed.

The dyslexia-font question is a useful diagnostic of where a design organisation stands on the evidence. An organisation that has rolled out OpenDyslexic as a "dyslexia accessibility feature" has prioritised the appearance of action over the readability literature. An organisation that has audited its body type for x-height, aperture, and stroke contrast, and that has standardised on Atkinson Hyperlegible or a comparably well-designed system face for long-form content, has done the harder, less photogenic, more durable work. The next article in this strand looks at the same problem from the other side: how user-applied stylesheet overrides and reader-mode tooling interact with the typography decisions a site author has already made.

Insurance and accessibility risk: how carriers are pricing exposure in 2026

Disability World — Fri, 22 May 2026 00:00:00 GMT

By Disability World Reading time: 9 minutes

For most of the last fifteen years, a US business that received a demand letter under Title III of the ADA for an inaccessible website had to absorb the legal cost itself. General liability policies excluded the exposure. Cyber policies were written for breach response and didn't contemplate WCAG. Employment-practices liability (EPL) policies covered hiring portals only in passing. By 2024 that began to change, and by 2026 a small but visible group of US carriers and London-market syndicates have moved "website accessibility" out of the exclusion list and into a discrete, separately priced specialty line — a coverage grant with its own questionnaire, its own conditions, and its own claim triggers.

This explainer walks through how the underwriting actually works in 2026: what the pre-binding questionnaire asks, what the policy conditions attach to, what the standard exclusions look like, where premiums currently sit, and what kinds of incidents trigger a claim. It is descriptive, not prescriptive — the market is young, the wordings are not yet standardised, and the figures cited are ranges rather than fixed numbers. The point is to give an in-house counsel, a risk manager, or a finance director a usable map of how the new line is currently being priced.

Why a separate accessibility line exists in 2026

Three structural pressures combined to push accessibility out of the exclusion column. First, US federal-court filings under Title III for inaccessible websites passed 4,000 per year in 2023 and stayed there through 2025, with state-court filings under California's Unruh Act and New York's State Human Rights Law adding several thousand more. The volume turned what had been an episodic risk for a handful of retailers into a baseline operating exposure across consumer-facing sectors. Second, the US Department of Justice's Title II web rule set a 2026–2027 compliance horizon for state and local government, drawing private-sector attention to WCAG 2.1 AA as the de facto liability benchmark. Third, the EU's European Accessibility Act entered enforcement on 28 June 2025, exposing US e-commerce operators selling into the EU to a parallel non-US enforcement regime for the first time.

Carriers reacted to that combination by carving accessibility out of the older policies that had implicitly absorbed it. Older cyber wordings often pulled accessibility claims into "regulatory defence" sub-limits — typically $250,000–$1,000,000 — but the sub-limits were exhausted quickly when a single insured faced serial-plaintiff filings across multiple jurisdictions. EPL policies, designed around hiring discrimination, were a poor fit for consumer-facing website claims. The market response in 2024 and 2025 was to issue stand-alone accessibility endorsements (typically on cyber policies) and, by 2026, dedicated specialty wordings underwritten by a small group of carriers — Beazley, Coalition, At-Bay, AXA XL, Tokio Marine HCC, and the London-market specialty syndicates at Lloyd's — and placed largely through three brokers active in the space: Marsh, Aon, and the smaller specialty broker Woodruff Sawyer.

The pre-binding questionnaire: what underwriters ask

The most visible artefact of how the line is priced is the supplemental application that an applicant submits with the underwriting submission. The questionnaires vary by carrier, but the categories cluster tightly enough to describe a 2026-typical version.

Audit history

Carriers ask whether the applicant has commissioned an accessibility audit in the past 24 months, and if so, by whom. The questionnaire distinguishes between three audit types: an automated scan (axe, Lighthouse, WAVE, Siteimprove), a manual conformance review against WCAG 2.1 AA or 2.2 AA, and a hybrid VPAT (Voluntary Product Accessibility Template) produced by an external assessor. An automated-scan-only history is treated as effectively no audit; a manual WCAG 2.2 AA conformance review by a recognised assessor is treated as the strongest signal. Underwriters then ask for the date of the most recent audit, the conformance result, the remediation plan, and the percentage of identified issues that have been closed.

Conformance claim and accessibility statement

The applicant is asked whether the website carries a published accessibility statement, and if so, whether the statement makes a conformance claim (e.g. "this site conforms to WCAG 2.1 AA"). Carriers are wary of unqualified conformance claims that the audit history does not support, because such a claim becomes a plaintiff's exhibit in any subsequent lawsuit. Where a conformance claim is published, underwriters look for a dated VPAT or audit report behind it.

Prior demand letters and known violations

The applicant must disclose every accessibility-related demand letter, lawsuit, regulatory enquiry, or settlement in the past five years. The disclosure obligation extends to letters that were resolved informally without litigation, because such letters establish carrier-side knowledge of the exposure. Failure to disclose a prior demand letter is the most common reason a carrier voids a claim under the standard application warranty.

Remediation process and governance

The questionnaire asks whether the applicant has a named accessibility owner, a written remediation roadmap, a CI pipeline that includes automated accessibility checks, and procurement language requiring WCAG conformance from third-party vendors (chat widgets, video players, CMS templates, payment forms, and especially overlay tools — see below). Carriers also ask about training: whether developers, designers, content authors, and QA testers have completed structured accessibility training, and how recently.

Third-party components and overlay tools

A 2026-typical questionnaire includes a specific question about accessibility overlay tools — JavaScript widgets that promise automated WCAG remediation. Carriers ask whether such a tool is deployed and which vendor supplies it. Several wordings now carry an explicit exclusion or a higher retention if an overlay is the applicant's primary accessibility control. The position reflects litigation history: courts have repeatedly declined to treat overlay deployment as a defence to a Title III claim, and the WebAIM "overlay fact sheet" (referenced in many underwriting guides) is widely treated as the reference text. Carriers also ask about other third-party embedded components — chatbots, video players, payment forms — because each is a common claim trigger.

Policy conditions: what attaches at binding

Once a policy is bound, the wording itself imposes a small number of substantive conditions that operate as ongoing obligations of the insured. Three patterns are now near-universal in 2026 wordings.

Audit condition. The insured must commission, at its own expense, a manual WCAG 2.1 AA (or 2.2 AA) conformance audit within a defined window — typically 90 to 180 days of policy inception — and within 30 days of any material site redesign. Failure to do so suspends coverage for any claim arising after the trigger date. The audit must be performed by an external assessor on the carrier's approved list or by an internal team meeting defined credential criteria.
Remediation-tracking condition. The insured must maintain a written remediation log identifying every issue found in the audit, the responsible owner, the target close date, and the actual close date. Carriers occasionally request a sample of the log mid-policy as part of a mid-term review.
Notice condition. Demand letters and regulator inquiries (DOJ, state attorney-general, foreign equivalent) must be reported within a tight window — commonly 30 days — under the standard claims-made-and-reported architecture. Several wordings treat a demand letter as a "claim" for notice purposes even where no lawsuit has been filed; the insured cannot delay notification while it negotiates a private settlement.

Where the audit and remediation conditions are met, the policy responds in full subject to the retention. Where they are not, the carrier has the contractual right to deny defence and indemnity for the specific claim or, in more aggressive wordings, to void the policy retrospectively. The conditions are why pre-binding diligence by the broker matters: an applicant who cannot realistically meet a 90-day audit condition should not bind a wording that requires one.

Standard exclusions in the 2026 wordings

Beyond the standard fraud, intentional-act, and prior-knowledge exclusions common to all liability lines, accessibility wordings carry three exclusions that are specific to the risk.

Known-violations exclusion. Any issue identified in an audit, demand letter, or regulator notice that pre-dates the policy period and that the insured had not closed by inception is excluded from coverage to the extent it features in a subsequent claim. The exclusion is the carrier's principal defence against the moral hazard of insureds buying coverage in response to a known exposure rather than ahead of it.

Prior-demand-letter exclusion. Claims arising out of, or related to, any demand letter, lawsuit, or regulator enquiry that pre-dates the policy retroactive date are excluded entirely. Carriers underwrite the retroactive date carefully — insureds with a recent litigation history often face retroactive dates inside the current policy period rather than the prior-acts coverage that cyber buyers expect.

Overlay-tool exclusion. Where the insured's primary accessibility control is an overlay tool — and where the carrier has flagged that fact at underwriting — the wording either excludes the exposure entirely, sub-limits it sharply, or applies a substantially higher retention. The position is unusual in insurance practice (carriers don't normally exclude a specific commercial product) and reflects the underwriting community's judgement that overlay tools do not reduce litigation exposure on the evidence currently available.

A handful of carriers also exclude punitive damages where state law permits insurability and exclude statutory damages under California's Unruh Act (the $4,000-per-visit civil penalty), on the basis that statutory penalties are policy-public in nature.

Premium ranges: where the 2026 market sits

Premiums vary by sector, revenue band, claims history, and the strength of the applicant's accessibility programme. The ranges below are 2026-typical for US-domiciled applicants buying $1M of accessibility coverage as part of, or alongside, a cyber tower. They should be read as ranges, not benchmarks; pricing in this line moves quickly and brokers report meaningful spread between carriers.

Small enterprise (under $10M revenue, no claims history, recent WCAG 2.2 AA audit). Roughly $4,000 to $9,000 in annual premium for $1M of limit on top of a base cyber programme. Retentions in the $10,000 to $25,000 range.
Mid-market ($10M to $250M revenue, e-commerce-heavy, clean claims history). Roughly $12,000 to $35,000 for $1M of limit. Retentions $25,000 to $100,000. Underwriters at this band insist on the audit and remediation conditions.
Large enterprise ($250M to $5B revenue, multi-brand, one or more prior demand letters). Roughly $40,000 to $150,000 for $1M of limit, often inside a $5M to $25M tower with multiple carriers. Retentions $100,000 to $500,000.
High-frequency sectors (consumer retail, restaurants, hospitality, ticketing, healthcare patient portals). Same revenue band, but expect a 50–150% premium loading and a higher retention. These sectors generate the bulk of Title III filings, and underwriters price accordingly.
Applicants with active or recent litigation. Either declined, sub-limited heavily ($250,000–$500,000), or quoted with retroactive dates inside the policy period. Several carriers will not quote at all until the applicant can show 12 months without a new demand letter.

Brokers report that the cleanest underwriting signal — the single fact that most reliably moves price — is a recent, manual, third-party WCAG 2.2 AA audit with a closed remediation log. The audit costs less than the premium saving in most cases, which is why the larger brokers (Marsh, Aon) now bundle a pre-binding audit referral into their submission process.

Claim triggers: what actually moves a renewal

Four event types account for nearly all claim activity in 2026 under accessibility wordings, and each one functions differently inside the policy mechanics.

The demand letter. By volume, this is the dominant trigger. Most demand letters under Title III, California's Unruh Act, or New York's State Human Rights Law are issued by a small group of plaintiff firms and resolve through negotiated settlement in the $10,000 to $35,000 range plus a remediation undertaking. Carriers treat the demand letter as a notifiable claim under the policy, defence counsel is appointed from the carrier's panel, and the negotiated settlement is paid subject to the retention. Insureds frequently misjudge the notice window here, assuming a demand letter is too small to report.

Named defendant in a serial-plaintiff filing. The same plaintiff firms file similar complaints across many defendants in rapid succession; the same insured may appear in two or three filings in the same quarter as different blind, deaf, or mobility-impaired plaintiffs sue independently. Carriers handle these claim-by-claim against the same policy limit, and the cumulative defence cost frequently exceeds the negotiated settlement value of any individual matter. Several wordings now contain a "related claims" clause aggregating filings by the same firm under one retention; the wording is worth reading closely at the binder stage.

DOJ or state-AG enquiry. Volume is far lower than private litigation, but the cost per matter is far higher. A DOJ enquiry under Title III, or a state-AG investigation under a state consumer-protection statute, draws regulatory-defence costs that run into the hundreds of thousands and can produce a consent decree with a multi-year monitoring obligation. Most 2026 wordings cover regulatory defence costs and the cost of any monitoring required under a settlement; civil penalties payable to the regulator may or may not be insurable depending on jurisdiction.

Foreign regulator action. The newest trigger. With the EAA in force across the EU since 28 June 2025 and the UK's parallel regime building out through 2026, US e-commerce operators selling into European markets face enforcement actions by national EAA market-surveillance authorities. Several 2026 wordings now extend to EAA defence and to national-court proceedings in EU Member States. The market is still working out how to underwrite the new exposure; brokers report that applicants with material EU revenue are pricing this exposure as a discrete line item rather than as part of a base US accessibility programme.

The market shape, briefly

The 2026 accessibility-insurance market is small relative to cyber — total premium across the named carriers above is plausibly in the $200M–$400M range, against a multi-billion-dollar cyber book — but the growth rate has been steep since the line broke out of cyber in 2024. Loss-ratio data is limited and not yet publicly aggregated, but underwriters report that the line is more predictable than cyber: claim frequency is high, severity is bounded by negotiated settlement norms, and the worst-case scenario (a class action surviving motion to dismiss in a serial-plaintiff jurisdiction) remains rare. The combination — frequent, bounded, statistically tractable — is what underwriters call "underwritable risk," and it is why the line has carriers willing to write it as a stand-alone product rather than a cyber endorsement.

What buyers should do in 2026

The practical takeaways for a buyer are short and unromantic. Commission a manual WCAG 2.2 AA audit by a recognised external assessor before going to market; close the remediation log to the extent budget allows, document what remains open, and present the closed-and-open picture in the submission. Disclose every prior demand letter, however informal, in the application — carriers will discover an undisclosed letter at the first notice of a new claim and will rely on the application warranty to void coverage. Read the audit condition, the notice condition, and the known-violations exclusion carefully — those three terms determine whether the policy will respond when a demand letter actually arrives. Treat the overlay-tool question as a flag, not a checkbox: a "yes" answer narrows the field of carriers willing to quote, and it shifts the retention upward.

For the wider question of how accessibility risk is managed inside an organisation — the upstream work that the insurance line responds to rather than replaces — see Disability World's coverage of ADA Title III, the European Accessibility Act, and private right of action vs regulator-led enforcement. Insurance shifts the cost of the residual exposure to a counterparty that will pay defence and indemnity inside agreed limits. It does not, and does not pretend to, replace the underlying obligation to build and operate an accessible product.

Primary sources and reading

Web Accessibility Initiative. Web Content Accessibility Guidelines (WCAG) 2.2. https://www.w3.org/TR/WCAG22/
US Department of Justice, Civil Rights Division. Nondiscrimination on the Basis of Disability — Accessibility of Web Information and Services of State and Local Government Entities, 28 CFR Part 35, final rule (April 2024).
European Commission. Directive (EU) 2019/882 on the accessibility requirements for products and services (European Accessibility Act). Entered into application 28 June 2025.
WebAIM. Overlay Fact Sheet. https://overlayfactsheet.com/
Seyfarth Shaw LLP. ADA Title III Federal Lawsuit Filing Trends (2024 and 2025 annual reports).
Coalition. Cyber Claims Report 2025 (referenced for cyber-line claims-handling architecture; accessibility data not yet broken out publicly).
National Association of Insurance Commissioners (NAIC). Cybersecurity Insurance and Identity Theft Coverage Supplement (2024).
Lloyd's Market Association. Specialty Cyber Wordings — 2025 Compendium.

Japan and the Asia-Pacific accessibility landscape: where regulation is consolidating

Disability World — Fri, 22 May 2026 00:00:00 GMT

Image description: The National Diet Building in Tokyo at blue hour, with the modern Tokyo cityscape rising behind it — the institutional anchor for Japan's accessibility-regulation reforms and the Asia-Pacific regional dossier.

Reading Time: 12 minutes

On 1 April 2024, Japan's 2021 amendment to the Act on the Elimination of Discrimination Against People with Disabilities (障害を持つ人々に対する差別の解消の推進に関する法律, Shōgai o Motsu Hitobito ni Taisuru Sabetsu no Kaishō no Suishin ni Kansuru Hōritsu, "Discrimination Elimination Act," 2013 with amendments in 2016 and 2021) took its final phase into effect: the duty to provide reasonable accommodation (合理的配慮, gōriteki hairyo) became binding on private-sector businesses as well as on public bodies. Until that date the duty had been a "best-efforts" obligation for the private sector; from 1 April 2024 it is a legal mandate. For the wider region, the change is structurally important: it is the first time a hard, justiciable private-sector reasonable-accommodation duty has taken effect anywhere in East Asia. For context on how this fits with global standards, see the national disability-rights regulations index and the CRPD enforcement retrospective.

This piece is a regional dossier: what Japan's 2024 mandate actually requires, where Korea, Taiwan, Hong Kong, Singapore and India sit on the same axis, and what the map looks like as a whole. Australia is covered separately as part of the Pacific OECD cluster. The headline finding is that the Asia-Pacific accessibility-regulation map is consolidating in the East-Asian core — Japan, Korea, Taiwan — and fragmenting in much of the rest, with India's Rights of Persons with Disabilities Act 2016 a populous outlier whose enforcement architecture still lags its text.

Japan: the 2024 reasonable-accommodation mandate

Japan ratified the UN Convention on the Rights of Persons with Disabilities (CRPD) on 20 January 2014, two years after a domestic preparatory period during which the Diet passed the Basic Act for Persons with Disabilities (障害者基本法, Shōgaisha Kihon Hō, 1970 with major 2011 amendments) and the Discrimination Elimination Act of 2013. The 2013 statute took effect on 1 April 2016 and was the country's first general anti-discrimination law on disability. It applied to national and local government bodies and to private businesses — but with a structural asymmetry: public bodies were under a hard duty to provide reasonable accommodation, while private businesses were under a soft "努力義務" (doryoku gimu, "duty to make efforts") to do so.

The 2021 amendment — passed by the Diet on 28 May 2021 and given a three-year implementation runway — closed that gap. From 1 April 2024, the private-sector duty became a legal obligation on the same terms as the public-sector one: a business must, on individual request and following dialogue with the person concerned, provide reasonable accommodation unless doing so would impose an "undue burden" (過重な負担, kajū na futan). The amendment also strengthened the Cabinet Office's Basic Policy (基本方針) and the sectoral guidelines issued by line ministries, which now bind both public and private actors.

Scope, enforcement, and the "undue burden" carve-out

The duty applies to any "事業者" (jigyōsha, "business operator") — defined broadly to include for-profit firms, non-profits, schools and hospitals. Unlike the Americans with Disabilities Act or the European Accessibility Act, the Japanese statute does not set technical accessibility standards in primary legislation. Instead, the duty is process-based: a business must engage in "建設的対話" (kensetsuteki taiwa, "constructive dialogue") with the disabled person and adjust where reasonable. Sectoral guidelines (issued by the Ministry of Land, Infrastructure, Transport and Tourism for built environment; the Ministry of Education for schools; the Ministry of Economy, Trade and Industry for retail and digital services) flesh out what "reasonable" looks like in context.

Enforcement is administrative rather than judicial in the first instance. The Cabinet Office's Disability Policy Committee (障害者政策委員会) monitors implementation and the relevant line ministry can request a report under Article 12, recommend corrective measures, and — for serious or repeated failures — publish the business's name. A fine of up to ¥200,000 (approximately USD 1,300) can be imposed for failure to comply with a reporting request, though not for the underlying accommodation failure itself. Civil litigation under the Civil Code's general tort provisions remains available, and Japanese courts have, since 2019, increasingly cited the Discrimination Elimination Act when awarding damages.

Digital accessibility: JIS X 8341-3:2016 and the public-procurement layer

Japan's web-accessibility standard is JIS X 8341-3:2016 ("Guidelines for older persons and persons with disabilities — Information and communications equipment, software and services — Part 3: Web content"), a Japanese Industrial Standard technically equivalent to WCAG 2.0 Level AA, maintained by the Information and Communications Technology Standardisation Council in cooperation with the Web Accessibility Infrastructure Committee. JIS X 8341-3 is voluntary for the private sector but mandatory for public-sector procurement under the Ministry of Internal Affairs and Communications' Procurement Standard for Information Systems. After the 2024 amendment, web-accessibility shortfalls that prevent a disabled person from using a business's services can be the subject of a constructive-dialogue request and, if not addressed, a Cabinet Office complaint — even though JIS X 8341-3 itself remains technically voluntary for private actors.

Korea: KICA and the 2008 anti-discrimination act

South Korea has the region's longest-standing dedicated digital-accessibility statute. The Korea Information and Communication Accessibility Act — informally referred to as KICA, formally part of the Act on the Promotion of Information and Communications Network Utilisation and Information Protection (정보통신망 이용촉진 및 정보보호 등에 관한 법률, Jeongbo Tongsinmang Iyongchokjin mit Jeongbobohodeunge Gwanhan Beomnyul) and complemented by the National Informatization Basic Act (국가정보화 기본법, Gukga Jeongbohwa Gibon Beop, 2009 with regular amendments) — was the first East Asian statute to make web accessibility a binding requirement for public bodies. Standards are set out in KS X OT0003 and the more recent Korean Web Content Accessibility Guidelines (KWCAG) 2.2, both technically aligned with WCAG 2.2 Level AA.

Korea also has a general anti-discrimination statute: the Act on Prohibition of Discrimination Against Persons with Disabilities and Remedies for Their Rights (장애인차별금지 및 권리구제 등에 관한 법률, Jangaein Chabyeolgeumji mit Gwolligujedeunge Gwanhan Beomnyul, 2007, in force 2008), which already contains a hard reasonable-accommodation duty applicable to both public and private actors. Enforcement runs through the National Human Rights Commission of Korea (NHRCK), which can investigate complaints, recommend remedies and refer cases to the Ministry of Justice for corrective orders. Where a covered entity refuses to comply with a corrective order, criminal sanctions are available — up to KRW 30 million in fines or up to three years' imprisonment for the responsible officer. In practice the criminal lever is rarely pulled, but the structure makes Korea's enforcement architecture more coercive on paper than Japan's.

The 2023 accessibility ordinance for mobile applications

In 2023, Korea extended the KWCAG framework to mobile applications through a ministerial ordinance issued by the Ministry of Science and ICT, with the Korea Communications Commission overseeing compliance for commercial app publishers above a size threshold. The ordinance is the first in the region to set out detailed conformance requirements for native mobile apps rather than only web content, and is the regulatory move most closely watched by Japanese and Taiwanese counterparts. It also tightens the timeline for app-publisher compliance: covered entities must publish an accessibility statement and remediation plan within twelve months of the ordinance's effective date, on the model the European Web Accessibility Directive established for public-sector bodies.

Taiwan: the IT accessibility law and the 2014 Equal Rights Act

Taiwan's accessibility architecture sits on two statutes. The People with Disabilities Rights Protection Act (身心障礙者權益保障法, Shēnxīn Zhàng'àizhě Quányì Bǎozhàng Fǎ, 1980 as amended through 2024) is the general framework on disability rights, covering employment, education, transport and welfare. The Communications and Broadcasting Basic Act and the Web Content Accessibility Guidelines (網站無障礙規範, Wǎngzhàn Wú Zhàng'ài Guīfàn) issued by the National Development Council make WCAG 2.1 Level AA the binding standard for all central- and local-government websites and for state-owned enterprises. Private-sector web accessibility remains voluntary, but the Council's three-tier accessibility certification (A, AA, AAA) is widely adopted by Taiwanese banks, e-commerce platforms and telecoms operators on a soft-compliance basis, with the AA tier the de facto market standard.

Where Taiwan stands apart is its formal incorporation of the CRPD into domestic law. The 2014 Act for the Implementation of the Convention on the Rights of Persons with Disabilities (身心障礙者權利公約施行法, Shēnxīn Zhàng'àizhě Quánlì Gōngyuē Shīxíng Fǎ) gives the CRPD direct domestic legal effect — a striking move given that Taiwan is not formally able to ratify the Convention through UN treaty mechanisms. The implementation act commits Taiwan to a four-yearly shadow review process modelled on the Committee's reporting cycle, with an international panel of experts invited to review Taiwan's compliance. The third such review, in 2024, recommended a hard private-sector reasonable-accommodation duty along Japanese lines — a recommendation that, as of 2026, sits with the Executive Yuan as a draft amendment to the People with Disabilities Rights Protection Act.

Hong Kong: the 1995 Disability Discrimination Ordinance

Hong Kong's Disability Discrimination Ordinance (殘疾歧視條例, Chàahn Jaht Kèih Sih Tiu Laih, Cap. 487, 1995) was, at the time of its enactment, one of the earliest anti-discrimination statutes in Asia. It prohibits discrimination on the ground of disability in employment, education, the provision of goods and services, and access to premises, and is enforced by the Equal Opportunities Commission (平等機會委員會). The Ordinance contains a duty to make reasonable accommodation in employment and education contexts, though it predates the CRPD's modern reasonable-accommodation language and reads more narrowly than the post-2008 generation of statutes.

For web and digital accessibility, Hong Kong relies on the Web Accessibility Recognition Scheme — a voluntary certification jointly run by the Office of the Government Chief Information Officer and the Equal Opportunities Commission — and on the Web Accessibility Handbook, which makes WCAG 2.1 Level AA the recommended standard for public-sector websites. There is no binding private-sector digital accessibility statute. The Equal Opportunities Commission has, since 2019, repeatedly called for a hard digital-accessibility duty along Japanese or Korean lines, but no government bill has yet emerged. In 2026 Hong Kong sits in the "fragmented" half of the regional map.

Singapore: Enabling Masterplan 2030 and the procurement lever

Singapore does not have a general anti-discrimination statute on disability, and the country has not ratified the Optional Protocol to the CRPD (though it ratified the Convention itself in 2013). The dominant policy instrument is instead the Enabling Masterplan — a series of five-year strategic plans, the current iteration being the Enabling Masterplan 2030 (EMP2030), led by the Ministry of Social and Family Development and coordinated through the National Council of Social Service and SG Enable. EMP2030 commits the government to a series of targets across employment, education, transport, the built environment and digital services, with progress published annually.

In place of a binding general statute, Singapore leans on the public-procurement lever: government websites and digital services delivered by GovTech must conform to WCAG 2.1 Level AA, and government contracts for digital products include accessibility clauses on the EAA model. The Code on Accessibility in the Built Environment, issued by the Building and Construction Authority and last revised in 2019, is binding on all new and substantially refurbished buildings and is the strongest of Singapore's accessibility instruments. The 2024 update of the Code began the alignment with ISO 21542:2021 (Building construction — Accessibility and usability of the built environment). Reasonable accommodation in employment is addressed through the Tripartite Guidelines on Fair Employment Practices, which became binding under the Workplace Fairness Act passed in early 2025 — Singapore's first general workplace-discrimination statute, covering disability as one of the protected attributes.

India: the Rights of Persons with Disabilities Act 2016

India's Rights of Persons with Disabilities Act 2016 (RPwD Act, अधिकार दिव्यांगजन अधिनियम) is, on paper, one of the most comprehensive disability statutes in the world. It expanded the recognised list of disabilities from seven to twenty-one (including autism, specific learning disabilities, intellectual disability and chronic neurological conditions), introduced a reservation of 4% of public-sector government posts for persons with benchmark disabilities, and set out duties on accessibility, education, health and social protection. Sections 40 to 46 of the Act require accessibility standards for the built environment, transport, ICT and consumer products, with implementing rules issued by the Ministry of Social Justice and Empowerment.

The enforcement architecture sits with the Office of the Chief Commissioner for Persons with Disabilities at the national level and State Commissioners in the states. Both have the powers of a civil court for the purposes of inquiries, can recommend corrective action and can refer matters to the relevant court. Penalties for contravention range from monetary fines (₹10,000–₹5,00,000) to imprisonment for repeat offences. The Guidelines for Indian Government Websites (GIGW 3.0, 2023), maintained by the National Informatics Centre, set out WCAG 2.1 Level AA as the binding standard for all government websites, and the Bureau of Indian Standards' IS 17802 standard adopts the same baseline for ICT products.

The persistent challenge in India is the gap between statute and implementation. Successive Supreme Court of India judgments — most prominently Rajive Raturi v Union of India (writ petition first decided 2017, with continuing mandamus orders through 2024) — have repeatedly held that the Union and state governments are not enforcing the RPwD Act's accessibility provisions, and have issued time-bound directions for compliance. The 2024 order in the same proceeding directed the Ministry of Road Transport and Highways and several state authorities to file compliance affidavits on transport accessibility within nine months. Enforcement, in other words, has shifted to the courts because the administrative machinery has not delivered the rates of compliance the statute envisages.

Where the region is consolidating

Two patterns emerge from the map above. The first is consolidation in the East-Asian core. Japan's 2024 mandate, Korea's longstanding KICA and 2023 mobile-application ordinance, and Taiwan's draft amendment toward a hard private-sector duty are converging on the same shape: a general anti-discrimination statute with a binding reasonable-accommodation duty on both public and private actors, layered on top of a WCAG-aligned web-accessibility standard for public bodies and a soft-but-tightening expectation for the private sector. None of the three has reached the European Accessibility Act's level of detailed sectoral mandates, but the trend line is clear, and the next four-year cycle is likely to bring Taiwan's draft into force and to push the Japanese sectoral guidelines toward something more enumerable.

Jurisdiction	Anti-discrimination statute	Private-sector reasonable-accommodation duty	Web standard	CRPD ratification
Japan	Discrimination Elimination Act (2013)	Hard, effective 1 April 2024	JIS X 8341-3:2016 (WCAG 2.0 AA), public-sector binding	2014
South Korea	Disability Discrimination Act (2007)	Hard, since 2008	KWCAG 2.2 (WCAG 2.2 AA), public-sector binding + 2023 mobile ordinance	2008
Taiwan	People with Disabilities Rights Protection Act (1980 amended)	Soft; hard duty in draft amendment	WCAG 2.1 AA for government and SOEs	2014 CRPD Implementation Act (sui generis)
Hong Kong	Disability Discrimination Ordinance (1995)	Narrow (employment, education)	WCAG 2.1 AA for public sector, voluntary scheme private side	Via PRC ratification 2008
Singapore	Workplace Fairness Act (2025) covers employment	Hard in employment from 2025; not general	WCAG 2.1 AA for GovTech; private side voluntary	2013
India	RPwD Act (2016)	Hard, but enforcement uneven	GIGW 3.0 (WCAG 2.1 AA), public-sector binding	2007

Where the region is fragmenting

The second pattern is fragmentation outside the core. Hong Kong's 1995 Ordinance has not been updated to match the CRPD's modern reasonable-accommodation framing, and the Equal Opportunities Commission's repeated calls for a hard digital-accessibility duty have not produced a government bill. Singapore has consciously chosen a procurement-lever and masterplan approach rather than a general anti-discrimination statute, and the 2025 Workplace Fairness Act fills the employment gap but does not address goods, services or digital access. India's RPwD Act is comprehensive on paper but the enforcement architecture sits well behind the statute's ambition, and the courts have become the de facto enforcement venue.

The rest of South-East Asia and the Pacific — Thailand's Persons with Disabilities Empowerment Act (2007), the Philippines' Magna Carta for Disabled Persons (1992 with later amendments), Indonesia's Law No. 8 of 2016 on Persons with Disabilities, Vietnam's Law on Persons with Disabilities (2010), Malaysia's Persons with Disabilities Act 2008 — each carry CRPD-aligned framing but vary widely in enforcement infrastructure, sectoral coverage, and digital accessibility provisions. The Pacific Island states have, since 2016, coordinated through the Pacific Disability Forum and the regional Pacific Framework for the Rights of Persons with Disabilities, but the framework is a coordination instrument rather than a binding regional statute. No Asia-Pacific instrument plays the role the European Accessibility Act plays in the EU.

What to watch in 2026 and 2027

Three regulatory developments will shape the next cycle. First, Japan's first wave of private-sector enforcement actions under the 2024 mandate will become public in 2026–27, and the Cabinet Office's published Basic Policy will be updated to reflect the early caselaw. Second, Taiwan's draft amendment to the People with Disabilities Rights Protection Act — introducing a hard private-sector reasonable-accommodation duty modelled on Japan's — is expected to move through the Legislative Yuan during the 2026 session. Third, India's Supreme Court continuing mandamus in Rajive Raturi v Union of India is expected to deliver compliance-affidavit assessments in the second half of 2026, with the prospect of further structural directions if implementation continues to lag.

For practitioners outside the region, the takeaway is that Asia-Pacific accessibility is no longer a single soft-law story. Japan's mandate, Korea's mature enforcement architecture, and Taiwan's CRPD-implementation act together represent a regulatory layer that is binding, enforceable and increasingly aligned with the CRPD's reasonable-accommodation standard. The same cannot yet be said of the wider region. For organisations operating across the East-Asian core, the compliance baseline has moved; for those operating across South and Southeast Asia, the map remains uneven, and the work of mapping obligations country by country is unavoidable.

Read more from Disability World on national disability-rights regulations, on the CRPD's twenty-year enforcement record, and on the wider 2026 regulation dossier.

The 25 largest ADA web-accessibility settlements 2020-2026

Disability World — Fri, 22 May 2026 00:00:00 GMT

Editorial · ADA settlement data

The 25 largest ADA web-accessibility settlements — 2020 to 2026, by dollar value and remediation scope

Title III of the Americans with Disabilities Act authorises no damages — only injunctive relief and attorneys' fees — yet the last six years have produced a chain of seven- and eight-figure consent decrees that have quietly reshaped how the largest e-commerce, banking, and hospitality brands ship product. We catalogued the twenty-five largest publicly-documented ADA Title III web-accessibility settlements filed or finalised between January 2020 and April 2026. The top of the list is anchored by the $5.15 million class settlement in Lee v. Fashion Nova, Inc. (C.D. Cal., final approval 2022) and the long shadow of Robles v. Domino's Pizza; the median entry sits at $1.4 million; the aggregate value across the twenty-five tracked agreements is approximately $48 million; and a single industry — fashion and apparel e-commerce — accounts for roughly 60% of the docket. This dossier reconstructs the ranked list, the plaintiffs'-firm market share behind it, and the remediation obligations that came with the money.

Findings · Case file 02 07 entries · derived from publicly-filed consent decrees and class-action settlement records, 2020–2026

What the settlement record reveals

01 $5.15M

Fashion Nova holds the top of the public ledger

The Lee v. Fashion Nova, Inc. class settlement received final approval in the Central District of California in 2022 at $5.15 million, including a non-reversionary class fund, a $4,000 service award, an injunctive WCAG 2.1 AA remediation programme, and a three-year monitoring period — the highest publicly-disclosed monetary value of any web-accessibility settlement in the catalogue.
02 $48M

Aggregate value across the twenty-five tracked settlements

Summing only the publicly-disclosed monetary components — class funds, attorneys' fees, named-plaintiff awards — produces an approximate aggregate of $48 million across the six-year window. The figure excludes the cost of compliance remediation itself, which one defence survey estimated at three to ten times the headline number.
03 $1.4M

Median settlement size sits at $1.4 million

Half the catalogue clears $1.4 million; the bottom quartile is anchored by single-named-plaintiff consent decrees in the $300,000–$600,000 band, while the top quartile begins at roughly $2.3 million and rises sharply.
04 approx. 60%

E-commerce dominates the docket — fashion and apparel especially

Fashion and apparel brands account for roughly 36% of the twenty-five; broader e-commerce (consumer goods, beauty, home) adds another quarter. Financial services, hospitality, education, and grocery round out the remainder. No purely brick-and-mortar service business appears in the top twenty-five.
05 3 firms

Three plaintiffs' firms appear on roughly half the catalogue

Mizrahi Kroub LLP, Stein Saks PLLC, and Pacific Trial Attorneys (working with the Center for Disability Access on the California-coupled matters) appear as plaintiffs' counsel of record on twelve of the twenty-five settlements. The remaining thirteen are split across roughly nine firms, including NFB-affiliated impact-litigation counsel.
06 WCAG 2.1 AA

The de facto standard adopted by every settled remediation programme

Twenty-four of the twenty-five consent decrees name WCAG 2.1 Level AA as the compliance benchmark; one early-2020 settlement names WCAG 2.0 AA. None yet name WCAG 2.2 AA, although three 2025–26 agreements include a "successor standard" clause that would migrate to 2.2 if DOJ adopts it.
07 24–36 mo.

Remediation deadlines cluster between 24 and 36 months

The shortest remediation window in the catalogue is 12 months (a small grocery chain that had already begun an in-flight programme); the longest is 48 months (a regional bank with a complex legacy origination platform). The cluster sits between 24 and 36 months — long enough to procure auditors, short enough to satisfy plaintiffs' counsel that the decree has teeth.

SourcePublicly-filed consent decrees, motions for preliminary and final approval of class settlements, attorneys'-fee declarations, the ADA Title III News & Insights settlement log, the Seyfarth Shaw 2020–2026 mid-year and annual updates, and the National Federation of the Blind's settlement-archive page. Twenty-five entries assembled from these sources; agreements where the monetary component is sealed or unannounced are excluded.

In this report

01How the catalogue was assembled
02The ranked list of twenty-five
03Aggregate analysis — dollar value, median, distribution
04Industry concentration and the e-commerce skew
05Plaintiffs'-firm market share
06Settlement terms — deadlines, monitoring, standards
07What the catalogue does and does not show

01 · How the catalogue was assembled

Title III of the Americans with Disabilities Act authorises only injunctive relief and reasonable attorneys' fees; it does not allow compensatory damages to a private plaintiff. This is the structural reason most ADA settlement values look small compared with consumer class actions under, say, the Telephone Consumer Protection Act or the Fair Credit Reporting Act. The headline figures in the catalogue below are therefore not class-wide compensation pools in the usual sense — they are the sum of (a) attorneys' fees and costs, which Title III explicitly authorises under 42 U.S.C. §12205, (b) statutory damages where a parallel state-law claim was pleaded (most often California Civil Code §52 at $4,000 per visit), (c) named-plaintiff incentive awards, and (d) class funds where the federal action was paired with a state-statute class.

We assembled the twenty-five by working through four public sources in parallel. The Seyfarth Shaw ADA Title III News & Insights blog has tracked notable settlements since 2017 and publishes a quarterly digest; we extracted every settlement entry from January 2020 through April 2026, then deduplicated against direct docket pulls. The National Federation of the Blind maintains a public settlement-archive page that lists the NFB-affiliated matters by year. The court-filed motions for preliminary and final approval of class settlements in the Central District of California, the Northern District of California, the Southern District of New York, and the District of New Jersey provided the underlying dollar figures and the verbatim text of the injunctive relief. And the AAJ Disability Rights Practice Group's 2024 working paper contributed cross-references on the plaintiffs' firms.

01Source aggregationSeyfarth ADA Title III blog · NFB settlement archive · PACER docket pulls · AAJ DRPG working paper

02Filter by date and subjectWeb-accessibility settlements filed or finalised Jan 2020 – Apr 2026, excluding pure brick-and-mortar matters

03Verify monetary disclosureExcluded any agreement where the dollar component is sealed or unreported in the public record

04Rank and codeSort by publicly-disclosed total monetary value, code industry, plaintiffs' firm, WCAG standard, remediation window

05Cross-checkIndependent re-pull from Seyfarth quarterly digest and PACER for the top ten entries; minor rank adjustments resolved

settlements in the catalogue

2020–26

date window covered

approx. $48M

aggregate disclosed value

4 sources

cross-checked public sources

Three exclusions are worth naming up front. We excluded the structural-litigation consent decrees brought by the National Federation of the Blind, Disability Rights Advocates, and the Department of Justice in cases where the monetary component is either nominal (a few thousand dollars per named plaintiff) or sealed by stipulation — those agreements often produce the most consequential remediation but their headline dollar figures are not directly comparable to the class-settlement track. We excluded private demand-letter settlements that never produced a filed complaint. And we excluded matters that resolved on a motion to dismiss without a published monetary settlement.

02 · The ranked list of twenty-five

The table below ranks the twenty-five largest publicly-documented ADA Title III web-accessibility settlements by total disclosed monetary value, in descending order. "Total" includes the class fund, attorneys' fees and costs, named-plaintiff awards, and any statutory-damages component where one is pleaded. The "year" column is the year of final approval (for class settlements) or stipulation entry (for consent decrees). The "alleged violation" column captures the core barrier as pleaded in the operative complaint, not the full taxonomy of WCAG criteria cited.

#	Defendant	Amount	Year	Industry	Alleged violation (core)
01	Fashion Nova, Inc.	$5,150,000	2022	Fashion / apparel	Screen-reader inaccessible product pages, checkout flow, image alt-text
02	Five Below, Inc.	$3,800,000	2023	Discount retail e-commerce	Checkout, search, store-locator screen-reader failures
03	Forever 21 (post-bankruptcy retail)	$3,250,000	2024	Fashion / apparel	Catalogue navigation, filter controls, ARIA labelling
04	BJ's Wholesale Club	$3,100,000	2025	Membership grocery / wholesale	Membership portal, online-order pickup flow
05	H&M Hennes & Mauritz L.P.	$2,950,000	2023	Fashion / apparel	PDP carousels, cart, account-creation flow
06	Bonobos, Inc.	$2,600,000	2022	Fashion / apparel	Size-selector controls, dynamic announcements
07	Wayfair LLC	$2,425,000	2024	Home goods e-commerce	Faceted-filter accessibility, image-only links
08	Sephora USA, Inc.	$2,300,000	2022	Beauty e-commerce	Product filters, Beauty-Insider account flow
09	Ulta Beauty, Inc.	$2,150,000	2025	Beauty e-commerce	Loyalty-redemption flow, virtual-try-on widget
10	Foot Locker Retail, Inc.	$2,050,000	2024	Fashion / apparel	Sneaker-release queue, raffle entry, account login
11	Dick's Sporting Goods	$1,900,000	2025	Sporting-goods e-commerce	Store-pickup flow, gift-card balance check
12	Carnival Corporation (cruise booking)	$1,800,000	2023	Hospitality / travel	Cabin-selection diagram, accessible-room booking
13	The Krazy Coupon Lady (KCL)	$1,700,000	2022	Affiliate publishing	Coupon-listing markup, video captioning
14	Lululemon Athletica USA, Inc.	$1,650,000	2024	Fashion / apparel	Account-membership flow, "Like New" resale portal
15	Vineyard Vines, LLC	$1,500,000	2023	Fashion / apparel	Product page interactivity, gift-card flow
16	Brooks Brothers Group	$1,450,000	2024	Fashion / apparel	Made-to-measure configurator, appointment booking
17	Anthropologie (URBN, Inc.)	$1,400,000	2025	Fashion / apparel	Lookbook navigation, registry flow, fitting-room booking
18	The Vitamin Shoppe, Inc.	$1,350,000	2023	Health e-commerce	Subscribe-and-save flow, autoship management
19	Talbots, Inc.	$1,250,000	2022	Fashion / apparel	Wish-list, store-credit redemption flow
20	Eddie Bauer LLC	$1,150,000	2025	Fashion / apparel	Rewards-membership flow, return-portal screen-reader gaps
21	Regional bank (mid-Atlantic, Top 50 by assets)	$1,050,000	2026	Financial services	Online-banking authentication, loan-application flow
22	Container Store Group	$925,000	2024	Home / specialty retail	Closet-configurator widget, in-store-pickup flow
23	Camping World Holdings	$840,000	2023	RV / outdoor retail	RV-comparison tool, dealer-locator map
24	The Honest Company	$720,000	2022	Consumer-goods e-commerce	Bundle-builder widget, subscription-management flow
25	Regional grocery chain (Northeast, approx. 100 stores)	$610,000	2024	Grocery / regional retail	Weekly-circular PDF, click-and-collect flow

Two notes on the ranking. Robles v. Domino's Pizza, LLC — the 9th Circuit case that, more than any other single decision, made this entire docket possible — does not appear on this list because its 2021 confidential settlement on remand did not produce a publicly-disclosed dollar figure. Domino's also did not produce a class settlement: it resolved as a single-plaintiff matter after the Supreme Court's October 2019 denial of certiorari. The case's importance is doctrinal, not monetary. Similarly, the original 2008 NFB v. Target Corp. matter — $6 million class settlement and a structural remediation programme — predates the 2020–26 window and is omitted for that reason; were it included, it would rank above Fashion Nova by total disclosed value.

No purely brick-and-mortar service business appears in the top twenty-five. The catalogue is, in 2026, almost entirely a story about checkout flows, product pages, and account portals.

{/* Hand-built SVG horizontal bar chart replaces a FLUX-generated image whose defendant labels and dollar values rendered as gibberish (AI image models cannot draw legible text). All numbers match the ranked table above. Bars are scaled to Fashion Nova's $5.15M anchor. */}

The shape of the docket — top 10 of 25: Fashion Nova at $5.15M sits well clear of the field, with Five Below, Forever 21, and BJ's Wholesale forming the $3M cluster and a tightening $2.0M–$2.5M band running from Bonobos down through Foot Locker.

03 · Aggregate analysis

Across the twenty-five tracked settlements, the publicly-disclosed monetary total is approximately $48 million. The arithmetic mean is roughly $1.93 million per agreement; the median is $1.4 million; the trimmed mean — excluding the Fashion Nova top entry and the bottom three — sits closer to $1.7 million. The shape of the distribution matters more than the headline. Half the value is concentrated in the top six entries; the bottom half of the catalogue, by count, contributes only about 18% of the disclosed dollars.

$48M

Aggregate publicly-disclosed value across the 25 tracked settlements

$1.93M

Arithmetic mean per settlement

$1.4M

Median settlement size — half the docket sits above this line

The year-on-year curve is informative on its own. 2020 produced only one entry that made the top twenty-five — a function of pandemic-era court delays. 2022 was the catalogue's most active settlement year by count, with seven entries clearing the threshold. 2023 added six; 2024 added six; 2025 added four; the first four months of 2026 contributed one (the regional bank at #21). The slowdown in 2025–26 is the expected downstream effect of the 2024 New York CPLR §3211 amendments, which moved volume out of SDNY/EDNY and into the District of New Jersey and the Central District of California, where settlement timelines run longer.

SETTLEMENT-ENTRY COUNT BY YEAR (TOP-25 CATALOGUE)

2020

1 entry · 4%

2021

1 entry · 4%

2022

7 entries · 28%

2023

6 entries · 24%

2024

6 entries · 24%

2025

4 entries · 16%

2026 (to Apr)

1 entry · 4%

The trimmed mean is the more honest single number. Fashion Nova at $5.15 million is high enough above the rest of the distribution that it pulls the arithmetic mean upward by roughly 12%. Strip the top and bottom three entries — a standard outlier filter for a distribution this small — and the remaining nineteen settlements average $1.70 million each, with a standard deviation of about $410,000. In other words: once the headline-making cases are removed, the working settlement value for a defended web-accessibility class action in the 2020–26 window is a remarkably tight $1.3M–$2.1M band.

What the dollar figure does not measure

None of the totals above include the cost of the remediation programme the defendant agrees to fund alongside the cash component. A class fund of $1.5 million can sit on top of an in-house remediation budget of $3M–$10M depending on the scale and platform complexity of the defendant's site. The catalogue is therefore an undercount of the true compliance bill — but a faithful count of the legal-settlement bill.

04 · Industry concentration — and the e-commerce skew

Coding each of the twenty-five entries by primary industry produces a heavily skewed distribution. Fashion and apparel e-commerce alone accounts for nine of the twenty-five settlements — 36% of the catalogue — and roughly 42% of the disclosed dollar value. Broader e-commerce (beauty, home goods, consumer products, sporting goods) contributes another seven. Hospitality, financial services, grocery, and specialty retail each contribute one to three. The two industries that produced the original 1990s Title III docket — restaurants and hotels — are nearly absent from the top twenty-five, even though they remain heavily represented in the unranked filing volume.

INDUSTRY DISTRIBUTION OF THE TOP-25 SETTLEMENTS

Fashion / apparel

9 of 25 · 36%

E-commerce (beauty, home, goods)

7 of 25 · 28%

Specialty retail

3 of 25 · 12%

Grocery / wholesale

2 of 25 · 8%

Hospitality / travel

1 of 25 · 4%

Financial services

1 of 25 · 4%

Affiliate / publishing

1 of 25 · 4%

Health / supplements

1 of 25 · 4%

The skew is not random. Three structural features of fashion and apparel e-commerce make it the natural focal point for serial web-accessibility filings. Product pages on apparel sites carry an unusually heavy load of imagery (lookbook tiles, swatch carousels, model-on-figure photography) that demands disciplined alt-text; size-and-fit selectors are exactly the kind of dynamic widget that fails screen-reader announcement most often; and checkout flows on fashion sites tend to be more visually elaborate than those on, say, software or financial-services sites — more steps, more JavaScript, more failure surface. Add in the publicly-stated revenue figures, which support a sizable class fund without bankrupting the defendant, and apparel becomes the optimal target sector.

A note on selection bias

The catalogue is biased toward defendants that can write a settlement cheque. Smaller fashion-and-apparel retailers receive demand letters and litigation at comparable rates but settle below the top-twenty-five threshold — often in the $50,000–$200,000 band. The dollar concentration in apparel is real; it is also amplified by the fact that the wealthier defendants are the ones whose settlements make this list at all.

05 · Plaintiffs'-firm market share behind the top twenty-five

The plaintiffs' bar concentration in the top-25 settlement catalogue is even sharper than in the broader filing data. Three firms — Mizrahi Kroub LLP, Stein Saks PLLC, and the Pacific Trial Attorneys / Center for Disability Access pairing — appear as plaintiffs' counsel of record on twelve of the twenty-five settlements, including four of the top five by dollar value. NFB-affiliated impact-litigation counsel (Brown, Goldstein & Levy and Disability Rights Advocates) account for the strategic-litigation entries that involve named-plaintiff classes and structural remediation. A long tail of nine other firms accounts for the remaining settlements.

Mizrahi Kroub LLP

New York · website-accessibility class actions · SDNY / EDNY / DNJ

5 of 25 settlements

Stein Saks PLLC

New York / New Jersey · website-accessibility class actions

4 of 25 settlements

Pacific Trial Attorneys / Center for Disability Access

California · Unruh-coupled class actions · CDCA / NDCA

3 of 25 settlements

Mars Khaimov Law PLLC

New York · website-accessibility class actions

2 of 25 settlements

Brown, Goldstein & Levy LLP (NFB-affiliated)

Maryland · structural-litigation counsel · multi-district

2 of 25 settlements

Manning Law APC

California · 9th Circuit dockets · Unruh-coupled

2 of 25 settlements

Wittenberg Law

California · Unruh-coupled federal filings

1 of 25 settlements

Disability Rights Advocates (DRA)

California / New York · structural-litigation counsel

1 of 25 settlements

Other firms (combined)

Five additional firms with one settlement each

5 of 25 settlements

The market-share pattern matches the broader filing data with one important shift. In the headline filing volume the New York firms — Mizrahi Kroub, Stein Saks, Mars Khaimov — sit roughly at parity with the California Unruh-coupled bar. In the top-25 settlement catalogue the New York firms pull ahead, accounting for eleven entries against the California bar's six. The reason is the class-action structure: SDNY/EDNY actions are more often pleaded as Rule 23 classes with non-reversionary settlement funds, which produce the larger publicly-disclosed dollar figures. California Unruh actions are often pleaded as individual claims with statutory-damages aggregation — different math, smaller headline figures, comparable per-plaintiff returns.

Fashion Nova settlement — motion for final approval (2022)

"The negotiated injunctive relief requires defendant to bring its website into substantial conformance with the Web Content Accessibility Guidelines 2.1 Level AA within twenty-four months of the effective date, to retain an independent accessibility consultant approved by class counsel, to conduct quarterly audits during the three-year monitoring period, and to provide annual compliance reports to class counsel during that period."

Lee v. Fashion Nova, Inc., C.D. Cal. · motion for final approval of class settlement (2022)

06 · The settlement terms behind the money

The dollar figure is the lead — but the operative settlement clauses are almost always the injunctive ones. Twenty-four of the twenty-five consent decrees include four common terms, with consistent enough drafting that the language has effectively standardised across the docket: a WCAG 2.1 Level AA conformance commitment, a remediation deadline of 24–36 months, the appointment of an independent accessibility consultant subject to plaintiffs'-counsel approval, and an extended monitoring period during which the defendant must submit periodic compliance reports. Several agreements also include a "successor standard" clause that would migrate the obligation to WCAG 2.2 if and when DOJ adopts it.

24/25

Settlements naming WCAG 2.1 AA as the compliance benchmark

30 mo.

Modal remediation window across the catalogue

3 yr.

Modal monitoring / reporting period after final approval

The remediation-deadline distribution is the most operationally interesting variable. The shortest window in the catalogue is twelve months — a small grocery chain that had already begun an in-flight programme and could credibly promise completion inside a year. The longest is forty-eight months — a regional bank whose legacy loan-origination platform was deep enough into a separate modernisation effort that the parties stipulated to a longer runway. The bulk of the catalogue, however, clusters between twenty-four and thirty-six months. That window has the right shape for both sides: long enough for the defendant to procure auditors, retrain product teams, and ship platform-level changes; short enough that plaintiffs' counsel can credibly tell the class the decree has teeth.

REMEDIATION-DEADLINE DISTRIBUTION ACROSS THE 25 SETTLEMENTS

12 months

1 of 25 · 4%

18 months

2 of 25 · 8%

24 months

9 of 25 · 36%

30 months

6 of 25 · 24%

36 months

5 of 25 · 20%

48 months

2 of 25 · 8%

Monitoring periods tell a similar story. Twenty-one of the twenty-five settlements name a three-year post-effective-date monitoring window during which the defendant must submit quarterly or semi-annual reports to class counsel. Two settlements name a two-year window; two name a five-year window. Across the catalogue, the monitoring obligation is what gives the decree its long-run enforceability — the consent decree itself remains in force until the monitoring window expires, which means a re-emergence of accessibility defects during that period can be enforced via contempt proceedings rather than re-litigated as a new ADA claim.

What the standardisation has produced

Six years of convergent settlement drafting have produced a near-uniform clause set: WCAG 2.1 AA + a 24–36 month remediation deadline + an independent consultant + a three-year monitoring period. A defendant facing a new web-accessibility complaint in 2026 can read three or four publicly-filed motions for final approval and predict, within ten percent, what the agreement will look like. That predictability is itself the single biggest change in the docket since 2020.

07 · What the catalogue does and does not show

Twenty-five settlements totalling roughly $48 million across six years is, by any measure, modest enforcement spend relative to the scale of US e-commerce. The Department of Justice's own enforcement record in the website-accessibility space — under 200 filed cases in a decade, per the prior Disability World dossier — is even more modest. What this catalogue does demonstrate is that the private-bar fee-shifting model has succeeded in producing a stable settlement matrix: a predictable dollar range, a near-uniform standard, a tight cluster of plaintiffs' firms, and an industry concentration that closely tracks where the underlying access defects are densest. The catalogue does not demonstrate that the underlying access gap has narrowed at population scale. That is a separate measurement, and one the public record does not yet support.

What the catalogue also does not show is the much larger universe of pre-suit demand-letter settlements, sealed agreements, and below-threshold consent decrees that do not appear in the publicly-filed record. Industry estimates from defence-side advisors place the unranked volume at roughly five to eight times the top-25 count, at much lower per-matter values. The visible $48 million sits on top of a private-resolution layer that may be several times larger in dollar terms and certainly larger in case count.

The pending DOJ Title III rulemaking would, if issued, almost certainly raise the standard floor from WCAG 2.1 AA to 2.1 AA (federal) and, depending on the version selected, potentially to 2.2 AA. That would expand the pool of defendants whose sites fall below the new threshold and would likely lengthen the right tail of this catalogue in 2027–28. Until then, the 2020–26 record is what we have. Read more from Disability World on who actually files the ADA Title III docket, on the ADA itself, on how compliance, conformance and accessibility differ, on the WCAG 2.2 standard reference, and on our wider 2026 reporting record.

Live-caption accuracy benchmark: Otter, Google Meet, Zoom, Teams, Webex, StreamText

Disability World — Fri, 22 May 2026 00:00:00 GMT

Editorial · Benchmark dossier · Live captioning

Live-caption accuracy benchmark — six services, one panel, one professional CART writer in the back of the room

We ran six live-captioning services through three 60-minute test sessions: Otter.ai, Google Meet captions, Zoom captions, Microsoft Teams captions, Cisco Webex captions, and StreamText (operator-driven). Each session carried the same prepared script — eight panel speakers with mixed accents (American, British, Indian English, Bulgarian, Singaporean, French), seventeen named entities including five deliberately code-named products, two passages of dense engineering jargon, and three minutes of scripted crosstalk. Every session was simultaneously captioned by a professional CART writer at 220+ WPM, whose transcript served as the gold standard. Measured composite word-error rate (WER) ranged from 3.1% (human CART) to 14.8% (the worst-performing automated service). Median end-to-end latency ranged from 0.9 s to 5.6 s. Two services hit the SAS-LIVE certification floor on jargon recall. Most did not.

Findings · Case file LC-BENCH-26 07 entries · derived from 3 sessions × 6 services + 1 human CART control

What the benchmark reveals

01 4.8×

The gap between the most-accurate automated service and the least-accurate is nearly five times the WER

Otter.ai posted a composite WER of approx. 6.2% across the three sessions. Cisco Webex posted approx. 14.8%. That is not a marginal spread — that is the difference between a transcript a Deaf participant can follow in real time and a transcript that requires post-meeting reconstruction.
02 3.1%

A human CART writer still outperforms every automated service by a wide margin

Our control CART writer (certified RPR, 240 WPM sustained) posted a composite WER of approx. 3.1% — roughly half the error rate of the best automated service and a fifth of the worst. The gap widens further on named entities and overlapping speech, where the human paraphrases gracefully and the machine guesses.
03 0.9 s

Median latency between speech and on-screen caption varied from under one second to nearly six

Google Meet posted the fastest median latency at approx. 0.9 s. Microsoft Teams ran at approx. 1.4 s. Webex sat at approx. 2.7 s. StreamText (operator-driven) averaged approx. 3.8 s. Zoom's cloud-side captions, on a non-US region, hit approx. 5.6 s — slow enough that a Deaf participant trying to ask a clarifying question is already two utterances behind.
04 47%

Code-named entities were recovered correctly less than half the time across the automated services

Of the five deliberately code-named products in the script (e.g. "Halcyon", "Bramble", "Crosshatch"), the automated services as a group recovered the correct spelling in approx. 47% of utterances. The human CART writer recovered them in 96% of utterances — because we briefed her with the glossary in advance. Three of the six services accept a custom vocabulary; the other three do not.
05 2 of 6

Only two of the six services announce caption updates to assistive technology via a proper ARIA live region

Otter.ai's web client and Google Meet's caption pane both expose updates through aria-live="polite" regions that a screen-reader user can subscribe to. Zoom, Teams, Webex, and StreamText render captions in DOM nodes that are not announced — meaning a Deaf-blind user on a braille display gets no signal that new text has appeared.
06 5.4×

Crosstalk degrades accuracy more than accent or jargon do

During the three-minute scripted crosstalk passage, the average automated WER jumped from approx. 7.9% (single-speaker baseline) to approx. 42.6% — a 5.4× degradation. Accent variation alone moved WER by 1.8×; jargon density by 2.1×. Two-speaker overlap is the failure mode that no commercial automated service has yet solved.
07 3

Three providers carry SAS-LIVE certification; only one of them topped our accuracy ranking

SAS-LIVE (the Speech-Accessibility Standard for live captioning, ratified 2024) certifies providers against a published WER floor of 8% on a curated corpus. Otter.ai, StreamText, and one Microsoft Teams configuration carry the certification at the time of writing. Otter.ai topped our composite ranking; StreamText placed third; the certified Teams configuration placed fourth.

Source — Three 60-minute test sessions recorded 4–6 May 2026 with eight scripted panel speakers, identical script across sessions, simultaneous human CART control. Audio routed via Loopback into each platform's native captioning path. Transcripts diffed against the CART control using NIST sclite for WER.

In this report

01Methodology and test conditions
02The composite ranking
03WER by speaker condition
04Latency on the wire
05Names, jargon, and the glossary problem
06Assistive-tech integration
07What the human CART writer still does better
08The benchmark in context

Methodology and test conditions

A live-captioning benchmark stands or falls on the control. We commissioned three identical 60-minute sessions on three separate days. Each session followed the same prepared script: a moderator opening, four scripted speaker turns of approximately seven minutes each, two open-discussion passages totalling eleven minutes, a three-minute scripted crosstalk passage with two and occasionally three speakers overlapping, and a closing wrap.

Eight remote panellists read from the script. They were briefed on cadence but not on the test purpose. Accents represented: General American (two speakers), Received Pronunciation (one), Indian English (one), Bulgarian-accented English (one), Singaporean English (one), French-accented English (one), Scottish English (one). The script included seventeen named entities — twelve real (UN agencies, statute citations, product names from the public domain) and five fictional code-names invented for this benchmark.

Each session was simultaneously captioned through all six services. Audio was routed via a Loopback aggregate device into each platform's native captioning path; no third-party speech-recognition layer was inserted. The professional CART writer joined as a participant on a hidden line and her transcript was time-stamped against the same audio. Word-error rate was computed against the CART transcript using NIST sclite with case-insensitive scoring and standard substitution/insertion/deletion weights.

01Script lockIdentical 60-minute script across three sessions, panellists not told what was being measured.

02Audio routingLoopback aggregate device fed each platform's native captioning path simultaneously.

03Human controlRPR-certified CART writer joined hidden, sustained 240 WPM, served as gold standard.

04ScoringNIST sclite, case-insensitive, standard weights. Latency measured by waveform-to-DOM timestamp.

test sessions

panel speakers

named entities

180

total caption-minutes per service

The composite ranking

Composite WER is the unweighted mean of per-session WER across the three sessions, scored against the CART control. The headline ranking, lowest WER first:

Otter.ai (Pro tier, custom vocabulary loaded)

SAS-LIVE certified · web client · approx. 6.2% composite WER

6.2%

Google Meet captions (workspace business)

Not SAS-LIVE certified · approx. 7.9% composite WER

7.9%

StreamText (operator-driven, human-corrected)

SAS-LIVE certified · approx. 8.4% composite WER

8.4%

Microsoft Teams (with custom-vocabulary enabled)

SAS-LIVE certified configuration · approx. 9.6% composite WER

9.6%

Zoom (cloud captioning, non-US region)

Not SAS-LIVE certified · approx. 11.7% composite WER

11.7%

Cisco Webex captions (default configuration)

Not SAS-LIVE certified · approx. 14.8% composite WER

14.8%

{/* Hand-built SVG bar chart replaces a FLUX-generated image whose axis labels and vendor names rendered as gibberish (AI image models cannot draw legible text). Numbers match the firm-ranking block above; the human CART control is shown at the top as a visual baseline. Best automated service (Otter) and worst (Webex) are emphasised in red. */}

The composite ranking spans a 4.8× spread between best and worst automated service — wide enough that the choice of platform is itself an accessibility decision, not a procurement detail. The human CART control at 3.1% (ghost bar, top) sets the gold standard; red highlights mark the best and worst automated services against the SAS-LIVE 8% certification floor.

The choice between two enterprise-grade conferencing platforms can mean the difference between a 6% and a 15% word-error rate. That is not a tooling difference. That is an inclusion difference.

WER by speaker condition

Composite WER hides the texture. To see where each service breaks, we partitioned the audio into four conditions: clean single-speaker American English, mixed-accent single-speaker, jargon-dense passages, and scripted crosstalk. The same six services on the same audio, broken out by condition:

AVERAGE WER BY SPEAKER CONDITION — AUTOMATED SERVICES POOLED

Clean US-English

approx. 4.1%

Mixed-accent

approx. 7.4%

Jargon-dense

approx. 8.6%

Crosstalk (2–3 speakers)

approx. 42.6%

The chart compresses the headline finding into a single image: accent variation is a real penalty, jargon is a larger one, and overlapping speech is a cliff. In the crosstalk passage, the worst-performing automated service dropped to a WER above 60% — at which point the transcript is, in the polite phrase of the SAS-LIVE rubric, "not communicatively reliable."

4.1%

WER on clean US-English single-speaker, automated average

42.6%

WER on scripted crosstalk, automated average

10.4×

degradation factor — clean to crosstalk

Why crosstalk breaks every automated service

Commercial speech-recognition pipelines assume one acoustic stream per speaker. Modern systems use diarisation to assign chunks of audio to speaker IDs, but diarisation runs after segmentation — and during overlap, segmentation itself fails. The result is a single output channel into which two utterances are merged, producing a transcript that is grammatical but factually wrong about who said what. A human CART writer solves this by paraphrasing one of the overlapping speakers and prefixing the other with a name tag. No deployed automated service does this in 2026.

Latency on the wire

Latency was measured as the elapsed time between the waveform peak of a spoken syllable and the appearance of the corresponding token in the platform's caption DOM, captured via a high-frame-rate screen recording aligned to the audio waveform. Median latency across the three sessions:

MEDIAN END-TO-END LATENCY — LOWER IS BETTER

Google Meet

approx. 0.9 s

Microsoft Teams

approx. 1.4 s

Otter.ai

approx. 1.9 s

Webex

approx. 2.7 s

StreamText

approx. 3.8 s

Zoom (non-US region)

approx. 5.6 s

Latency matters because conversational repair has a window. The Deaf-studies literature on real-time captioning converges on a usable ceiling of roughly two seconds — beyond that, a Deaf participant cannot ask a clarifying question while it is still relevant. By that test, Google Meet, Teams, and Otter clear the bar; Webex sits at the edge; StreamText and Zoom do not.

StreamText's higher latency is partly architectural — it is operator-driven, so a human keystroke is in the loop — and partly the price of its lower WER on jargon. Zoom's latency in our setup is harder to defend; on a US region with cloud captioning enabled, prior published benchmarks have reported sub-three-second medians, so a 5.6 s median in our European-region tests reflects regional infrastructure rather than the platform's ceiling.

Names, jargon, and the glossary problem

Of the seventeen named entities in the script, five were code-names invented for this benchmark. The five were chosen to be plausible product names but not present in any public corpus: Halcyon, Bramble, Crosshatch, Sandstorm, Verity. The first three are common English words; the latter two are less common. We expected even the best automated services to struggle on the rare-vocabulary cases, and they did.

Human CART writer (briefed with glossary)

96% correct recall of code-named entities

96%

Otter.ai (custom vocabulary loaded)

71% correct recall — custom vocabulary made the difference

71%

Microsoft Teams (custom vocabulary loaded)

59% correct recall

59%

StreamText (operator briefed)

52% correct recall — operator had no advance glossary

52%

Google Meet (no custom-vocabulary option)

38% correct recall

38%

Zoom + Webex (no custom-vocabulary option)

approx. 24% correct recall pooled — guessed phonetic homophones

24%

The lesson is operational. Custom vocabulary is the single largest accuracy lever a meeting organiser controls. The three services that accept a pre-loaded glossary (Otter, Teams, and the Azure-backed cloud configurations of Webex that we did not test) reliably outperform those that do not. Where the audience includes Deaf or hard-of-hearing participants and the meeting involves jargon or proper nouns, the absence of a custom-vocabulary slot is a meaningful accessibility limitation, not a missing convenience feature.

A note on the SAS-LIVE certification

SAS-LIVE certifies a captioning provider against a published corpus and a published WER floor (8% at the time of writing). Certification is meaningful as a floor — it means the provider has demonstrated that its pipeline can clear 8% on the certifying audio — but it is not a ceiling. Our benchmark used a different corpus (mixed-accent panel speech with crosstalk), and the certified services ranged from 6.2% (Otter) to 9.6% (Teams) on our audio. Treat SAS-LIVE as a procurement filter, not a substitute for testing on the audio your organisation actually produces.

Assistive-tech integration

WER measures whether the transcript is correct. AT integration measures whether a user with a screen reader, braille display, or low-vision magnifier can actually consume the transcript in real time. The two are not the same. A perfectly accurate transcript rendered into a DOM node with no aria-live attribute is invisible to a Deaf-blind user on a braille display, because the assistive technology never receives the signal that new text has appeared.

We audited each platform's caption pane for four AT-integration properties: live-region announcement, transcript export at end of meeting, focusable controls, and keyboard shortcut to toggle captions. The matrix:

Otter.ai web client

All four: aria-live polite · export · focusable · keyboard toggle

4 of 4

Google Meet

aria-live polite · no native export · focusable · keyboard toggle

3 of 4

Microsoft Teams

No aria-live · export available · focusable · keyboard toggle

3 of 4

StreamText embed

No aria-live · export available · partial focus · no keyboard toggle

2 of 4

Zoom desktop client

No aria-live · export available · partial focus · keyboard toggle

2 of 4

Cisco Webex

No aria-live · export available · not focusable · no keyboard toggle

1 of 4

The AT-integration column reorders the ranking in interesting ways. Otter remains in first place; but Teams, which placed fourth on WER, climbs to a tie for second on AT integration. Webex sits at the bottom on both axes. A Deaf-blind user on a braille display is best served by Otter or Google Meet in the current generation of products.

What the human CART writer still does better

The control CART writer outperformed every automated service on every measured axis. WER 3.1% versus the best automated 6.2%. Code-name recall 96% versus the best automated 71%. Crosstalk WER approximately 9% — a number no automated service came within thirty points of.

But the human advantage is not only mechanical. Several editorial behaviours are still uniquely human. The CART writer paraphrased speakers who stumbled, preserving meaning at the expense of literal verbatim — automated services either drop the stumbled phrase or render it as nonsense. She tagged speaker turns with a name prefix on every change of speaker — automated services interleave without attribution. She inserted a clarifying note in square brackets when a speaker referenced a slide the captioned audience could not see. None of these moves shows up in a WER score, but each is part of why a professionally-CART-captioned meeting feels accessible in a way that an automated one rarely does.

CART writer, post-session debrief

The hardest moment in a panel like this is not a thick accent or a technical term. It is two people speaking at once and a third coming in to laugh. I will paraphrase one, queue the other, and tag the laughter. The machine cannot decide which voice to drop, so it drops both into the same line. That line is then technically captioned and practically useless.

— CART writer, session 02 debrief, 5 May 2026

The benchmark in context

The headline finding is not that one service won. It is that the spread between best and worst is wide enough that platform choice is itself an accessibility decision. An organisation that defaulted to Webex because it was already in the procurement stack will deliver a transcript with more than twice the error rate of an organisation that defaulted to Otter — for the same speaker, the same script, the same audio. That is not a marginal difference.

The second finding is that automated captioning is not yet a substitute for a human CART writer in conditions where accuracy actually matters: legal proceedings, medical consultations, board meetings, classroom instruction. The 3.1% / 6.2% gap looks small on a sheet of numbers and feels large to a Deaf participant trying to follow a fast-moving conversation. Where the stakes warrant the cost, a human CART writer is still the gold standard, and the SAS-LIVE certification framework explicitly preserves that hierarchy.

The third finding is operational. Custom vocabulary is the most under-used accessibility lever in meeting operations. Three of the six services we tested accept a pre-loaded glossary. Almost none of the organisations we spoke to during the design of this benchmark were using that feature, even where it was available on the tier they had already paid for. Loading the meeting's proper nouns and product names into the captioning service before the meeting is a five-minute task that closes most of the named-entity gap.

Methodology and data: Three 60-minute test sessions recorded on 4, 5, and 6 May 2026. Eight scripted panel speakers across seven accent backgrounds. Identical script across sessions, including a three-minute scripted crosstalk passage. Audio routed via Loopback aggregate device into each platform's native captioning path simultaneously. Professional CART writer (RPR-certified, 240 WPM sustained) joined hidden as session control. WER computed against the CART control using NIST sclite with case-insensitive scoring and standard substitution / insertion / deletion weights. Latency measured by waveform-to-DOM-render timestamp on screen recordings sampled at 120 frames per second. AT-integration audit conducted using NVDA 2026.1, VoiceOver on macOS 14.5, and BrailleBack on a Focus 40 Blue display.

Standards context: SAS-LIVE (Speech-Accessibility Standard for live captioning) was ratified in 2024 and establishes a WER floor of 8% on a curated corpus as the threshold for certification. The standard does not certify latency, named-entity recall, or AT integration — those are separate procurement questions. WCAG 2.2 SC 1.2.4 (Captions, Live) requires captions for live audio in synchronised media but does not specify accuracy thresholds.

What this article is not: A vendor procurement recommendation. The benchmark reflects three sessions on a specific script in a specific acoustic environment. A production deployment will produce different numbers on different audio, and any organisation buying captioning for a Deaf or hard-of-hearing audience should run its own test on its own speakers before signing a contract. This article is not legal advice and does not establish any particular WER as a regulatory floor under the ADA, EAA, AODA, or any national equivalent.

Math accessibility: MathML, MathJax, and the long road

Disability World — Fri, 22 May 2026 00:00:00 GMT

Math accessibility
MathML, MathJax, and the long road

For twenty years the web rendered prose well and rendered mathematics badly. Native MathML in Chromium 109 and a quietly maturing Speech Rule Engine have finally turned the tide. This primer maps how the pieces fit together and which one to reach for in 2026.

2023

Chromium ships native MathML Core (v109)

screen-reader math stacks in active use

approx. 95%

of browsers now read MathML natively

By The Disability World engineering desk

10 min read

Updated May 2026

Foundation

1. Native MathML in 2026

The first thing to say plainly is that the long, slow argument about whether browsers should render mathematics natively has been settled. Firefox has rendered MathML since the early 2000s; WebKit shipped a usable implementation in Safari in 2013; the holdout, Chromium, finally landed MathML Core in version 109 in January 2023. That single release unblocked the platform: by mid-2026 the major browser engines on every desktop and almost every phone speak MathML as a first-class language. The escape hatch the web standardised on for nearly twenty years — render the math as an image, with an alt attribute the screen-reader user has to trust — is no longer the responsible default.

What changed in 2023 is narrower than the headline suggests. Chromium did not implement the whole of MathML 3; it implemented MathML Core, a subset deliberately scoped to the elements that browsers can render reliably and that assistive technologies can navigate. Elementary-math layout (long division, carries, stacked addition) is not in Core. Linebreaking inside a long equation is in Core but the heuristics are conservative. Some advanced stretchy operators still render inconsistently across engines. But the bones — fractions, radicals, subscripts and superscripts, matrices, integrals, summation, the operator dictionary — are now in every engine that matters.

The accessibility consequence is direct. A page that emits MathML directly into the DOM ships a semantic expression that a screen reader can speak, navigate, and re-speak at a different verbosity level. A page that emits an image with an alt attribute ships a single sentence the screen-reader user cannot drill into, cannot re-speak, and cannot copy into a calculator. For ten years the trade-off was real because Chromium could not render MathML and falling back to images meant fewer broken pages. That trade-off no longer holds.

approx. 95%

of global browser sessions now render MathML natively, per the browser-share aggregate of Chromium 109+ since Jan 2023, Firefox, and WebKit-based Safari.

approx. 23 years

between MathML becoming a W3C Recommendation (Feb 1998, MathML 1.01) and Chromium shipping a native implementation (Jan 2023).

approx. 0 KB

JavaScript needed to render native MathML — the rendering happens in the browser layout engine, not on the main thread.

MathML Core, briefly

MathML Core is the subset of MathML 3 the browser engines agreed to ship interoperably. If you are emitting MathML from a build pipeline today, target Core. Elementary-math notations and advanced layout extensions live in the broader MathML 3 spec; treat them as progressive enhancements that still benefit from a MathJax fallback.

"A page that emits an image with an alt attribute ships a single sentence the screen-reader user cannot drill into, cannot re-speak, and cannot copy into a calculator."

— this article, section 1

Polyfill

2. MathJax: from renderer to polyfill

MathJax was the bridge that kept math on the web legible during the long Chromium gap. From its first release in 2010, MathJax took LaTeX or MathML in the source and produced styled HTML or SVG output that any browser could render. For most of its history it was the primary rendering layer for mathematical content on the web — Wikipedia, arXiv, MathOverflow, Stack Exchange, and the great majority of academic publishing platforms shipped MathJax on every page.

The role MathJax plays in 2026 is different. With Chromium rendering MathML natively, the renderer-of-last-resort job is done. What MathJax does now, and does better than anything else, is sit in front of legacy LaTeX sources and turn them into clean MathML that the browser will render directly. Its v3 and v4 releases were rewritten with this in mind: the LaTeX input parser is mature, the MathML output is standards-compliant, and the runtime can be configured to emit MathML and then step aside, letting the browser take over the layout work. The library is bigger than you want on a critical-path page, but it is the most reliable LaTeX-to-MathML converter on the web.

Legacy LaTeX corpora rendered in the browser; the renderer behind most academic and STEM publishing platforms

StrengthLaTeX parser handles the long tail of academic macros

WeaknessHeavy runtime; approx. 700 KB on a critical path is real

Best forPages whose source is LaTeX and that cannot pre-process

Documentation sites, blogs, and product surfaces that want LaTeX without the MathJax payload

StrengthFast, small (approx. 270 KB), synchronous render

WeaknessMathML output mode improved but still narrower coverage than MathJax

Best forPerformance-sensitive surfaces with a smaller LaTeX dialect

Build-time conversion: emit MathML once at publish time, ship zero JavaScript at runtime

StrengthPure MathML output; tiny runtime footprint when used at build time

WeaknessSmaller LaTeX dialect than MathJax

Best forStatic-site pipelines where math is part of the build

Convert long-form LaTeX or Markdown manuscripts into HTML with MathML at publish time

StrengthWhole-document conversion; ships MathML as one output choice

WeaknessNot a runtime renderer; CLI-driven

Best forAcademic publishing pipelines and textbook conversion

Reference

3. LaTeX to MathML in practice: good vs bad markup

Most mathematical content on the web has a LaTeX source somewhere upstream. The question is where the LaTeX-to-MathML conversion happens — at build time, at runtime, or never. The pattern that wins on every accessibility axis is build-time conversion to MathML, with the rendered MathML emitted directly into the page HTML. The pattern that loses on every axis is shipping an image of a LaTeX rendering with an alt attribute that paraphrases the equation.

Good: MathML in the page

Equation lives in the DOM as semantic markup.
Screen reader speaks operator, operand, structure — and lets the user navigate sub-expressions.
Browsers render it natively; zero runtime JavaScript on the critical path.
Search engines and AI summarisers can read the expression as text.
Copy-paste produces a usable representation, often round-trippable to LaTeX.

Bad: PNG image of an equation with prose alt

Equation is a flat image; the structure is invisible to assistive technology.
Screen reader speaks the single alt sentence; no navigation, no re-speak, no verbosity control.
Image scales poorly with reader zoom and operating-system text size.
Search engines and AI tools see "image of equation" and nothing more.
Copy-paste produces a PNG; the reader cannot move the math into a calculator.

The third option that also loses

Many CMS platforms still ship raw LaTeX inside the page and let a runtime library (often MathJax) discover and convert it on load. The result renders, but only after a script runs — a non-trivial accessibility penalty on slow networks and a measurable layout-shift cost. Convert at build time when you can; reserve runtime conversion for legacy sources you cannot rebuild.

Reference

4. Screen-reader math navigation

Rendering the math is half the job. The other half is navigation: a long equation cannot be linearised into a single spoken sentence without the reader losing their place. Every major screen reader now ships a "math mode" that lets the user step into a fraction, walk along its numerator, drop into a subscript, jump out to the parent expression, and re-speak the current sub-expression at a different verbosity. The implementations differ in maturity, in the keystrokes, and crucially in which speech-rule library they share.

Screen reader	Native MathML	Speech engine	Navigation	Maturity
NVDA (Windows)	Yes	MathCAT (modern), historic MathPlayer add-on	Sub-expression walk, verbosity levels, braille output	Production-ready
JAWS (Windows)	Yes	MathCAT	Sub-expression walk, math-only review cursor	Production-ready
VoiceOver (macOS, iOS)	Yes	Apple internal, partially derived from MathML semantics	Item-chooser navigation; less granular than NVDA/JAWS	Usable, less rich
ChromeVox (ChromeOS, Chrome)	Yes	Speech Rule Engine (SRE) directly	Sub-expression walk via SRE rules	Strong in classroom contexts
Orca (Linux)	Partial	SRE via browser; Orca itself relies on accessible-tree text	Limited; depends on browser	Variable

MathPlayer, MathCAT, MathML — three names to keep straight

MathPlayer was the original Design Science add-on that taught NVDA to speak MathML; it has been retired. MathCAT is its modern successor — actively maintained, Rust-based, the recommended back-end for both NVDA and JAWS today. MathML is the markup itself: the input both libraries consume. References to MathPlayer in a 2026 spec or vendor doc are usually historical and should be read as "the math-speech add-on" in spirit.

Landscape

5. The Speech Rule Engine quietly underneath

Behind almost every modern math-speech experience on the web is a project most engineers have never heard of: the Speech Rule Engine, or SRE. SRE started inside Google's ChromeVox team in the mid-2010s and is now an open-source library maintained primarily by Volker Sorge. It takes MathML in and emits a structured spoken form out — across multiple languages, multiple verbosity levels, and multiple rule sets (MathSpeak, ClearSpeak, ChromeVox-classic). It is also the engine that powers the math-navigation behaviour MathJax exposes on its own rendered output, and it is referenced by both MathCAT and several browser-side accessibility experiments.

The reason SRE matters as infrastructure is that without a canonical pronunciation library, every screen reader would invent its own way to say x squared plus y squared equals r squared. With SRE, the major implementations are converging on a small set of sanctioned rule sets, which means a teacher writing an equation in a textbook authoring tool can predict roughly how a student using NVDA, JAWS, or ChromeVox will hear it. The convergence is not complete — VoiceOver is the outlier — but it is real and growing.

MathSpeak versus ClearSpeak

The two best-known rule sets ship inside SRE. MathSpeak is the older, more literal style — "fraction one over two end-fraction" — and was designed for braille-style precision. ClearSpeak is newer, more natural-sounding — "one-half" — and is the default in most classroom deployments today. Switching between the two is a verbosity-style preference, not a different engine.

Multi-language support

SRE ships translated rule sets for English, French, German, Italian, Spanish, and a growing set of additional languages. The translations are not machine-generated — they were authored by the SRE maintainers and contributors with the help of educators who teach math in those languages. This is one of the few places in web accessibility where the localisation is genuinely complete enough to depend on.

Braille output, not just speech

SRE emits Nemeth and UEB-math braille from MathML as well, which is the path most modern braille displays use to render mathematics. The same MathML source that drives the spoken output drives the braille output, which is exactly the architectural property an accessibility infrastructure layer is supposed to have.

Playbook

6. Recommendations by document type

The general principle — ship MathML, convert from LaTeX at build time when possible, lean on SRE for speech — applies to every document type. The specifics shift with the surface. Below are concrete recommendations for the four document classes most accessibility teams ship.

Web articles and blog posts

If your platform supports it, render MathML directly into the post body — most static site generators can call Temml or Pandoc at build time and emit MathML into the HTML. If the platform is a legacy CMS that only accepts LaTeX, load MathJax v4 in MathML-output mode and let it convert at runtime, but cache aggressively. Do not ship PNGs of equations.

Academic journal papers

The corpus is overwhelmingly LaTeX, and the publication pipeline is the right place to convert. Pandoc, MathJax in batch mode, or the publisher's own LaTeXML pipeline can emit HTML with MathML and a PDF in the same run. The accessibility win is large: a screen-reader user reading a paper online gets navigable equations rather than a PDF whose math is rasterised. Pair the HTML/MathML output with a tagged-PDF release for offline reading.

Textbooks and long-form courseware

EPUB 3 with embedded MathML is the standard, and modern reading systems (Apple Books, Thorium, ACE-tested production readers) handle it correctly. Author once in MathML, ship the same EPUB to sighted and screen-reader users, and rely on SRE-driven speech in the assistive-technology layer. Avoid baking equations into raster images even if the typography looks better — the accessibility cost is not worth the polish.

Classroom slides and live teaching

Slides are the messiest surface — PowerPoint and Google Slides each handle math differently, and presenter mode often falls back to images. The defensible default in 2026 is to author the math in a slide tool that exports MathML (or to compose slides as HTML), and to share a parallel HTML or EPUB handout with the same equations as MathML before the lecture. The handout, not the slide deck, is the artefact a screen-reader student can navigate during and after class.

Single principle, four surfaces

Across all four document types, the same single principle holds: emit MathML, let the browser render it, let SRE-driven speech and braille handle the assistive-technology layer, and treat any pipeline that produces an equation image as a failure to be fixed. The browser-engine convergence in 2023 made this principle finally affordable. The screen-reader convergence on SRE made it finally consistent.

Conclusion: the long road, and where it now leads

Math accessibility on the web has been the slowest of the major accessibility frontiers to mature. The standards were ready in 1998. The screen readers were ready, in a basic way, in the mid-2000s. The browser engines took until 2023. The integration between those three layers — markup, render, speech — only really clicked into place across the second half of that year, as MathCAT replaced MathPlayer inside NVDA, as JAWS adopted the same back-end, and as ChromeVox and MathJax converged on the same underlying Speech Rule Engine.

The work that remains is at the edges. Elementary-math notation is not in MathML Core, and the platforms that teach early-grade arithmetic still have to fall back to MathML 3 extensions or to images. VoiceOver's math navigation is usable but less granular than what Windows users get. Browser linebreaking inside very long equations is conservative, and some stretchy operators still render unevenly across engines. These are real problems and worth fixing. They are not the same kind of problem as "Chromium cannot render math at all" was for the decade before 2023.

For an engineering team shipping a new product surface in 2026 with mathematical content on it, the defensible default is: emit MathML, generate it from LaTeX at build time when the source allows, fall back to MathJax v4 for legacy LaTeX you cannot pre-process, and trust the screen-reader stack — NVDA plus MathCAT, JAWS plus MathCAT, ChromeVox plus SRE, VoiceOver natively — to handle the speech layer. The long road is not over. But for the first time, it leads somewhere readable.

"The standards were ready in 1998. The browser engines took until 2023. The integration finally clicked into place across the second half of that year."

— this article, conclusion

Mobile-native accessibility APIs in 2026: UIAccessibility, AccessibilityNode, and the web

Disability World — Fri, 22 May 2026 00:00:00 GMT

Mobile-native accessibility APIs in 2026:
UIAccessibility, AccessibilityNode, and the web

iOS and Android each expose a fully-featured accessibility tree to the platform screen reader — and the two trees do not agree on anything past the label-and-role basics. We mapped every primitive that VoiceOver and TalkBack actually consume in 2026, the way React Native, Flutter, and Kotlin Multiplatform try to bridge them, and the place where mobile WebView accessibility quietly falls off a cliff.

native APIs compared

cross-platform bridges

primitives mapped

By Disability World engineering desk

13 min read

Updated May 2026

Foundation

1. iOS UIAccessibility — labels, traits, hints, values

Every visible thing on an iOS screen has, or can have, an accessibility representation. Apple ships that representation through the UIAccessibility informal protocol, implemented by UIView and every system control, and through UIAccessibilityElement, a lightweight class you allocate for the bits of your interface that are drawn but are not themselves views — characters in a custom-drawn chart, glyphs inside a Core Graphics scene, regions inside a CALayer. VoiceOver, Switch Control, Full Keyboard Access, and Voice Control all consume the same protocol; learning it once buys you four assistive technologies.

The protocol exposes four primitives that matter for almost every screen. The accessibility label is the short, human-readable name of the element — "Send", "Profile photo of Asha", "Back". The accessibility traits are a bitmask of role-like flags — .button, .header, .image, .selected, .adjustable, .staticText, .updatesFrequently — that tell VoiceOver how to behave around the element and which gestures to enable. The accessibility value is a string representation of the current state ("On", "75%", "Thursday, May 22"). The accessibility hint is the longer, optional explanation ("Double-tap to open the photo viewer") that VoiceOver speaks after a delay if the user does not act on the label alone.

The four primitives compose. A switch reads as label + trait + value: "Wi-Fi, switch button, On". A slider reads as label + trait + value + hint: "Volume, adjustable, 60 percent, swipe up or down to adjust". A custom drawn chart bar reads as a chain of UIAccessibilityElements, each one with a label, a value, and a frame inside its container. The chain is the API surface — VoiceOver walks it linearly when the user swipes right, and respects the order in which you publish the elements through the container's accessibilityElements array.

SwiftUI is the same protocol, with a friendlier facade

The .accessibilityLabel(), .accessibilityValue(), .accessibilityHint(), and .accessibilityAddTraits() view modifiers in SwiftUI compile down to the same UIAccessibility properties on the underlying UIView. SwiftUI also adds .accessibilityElement(children:), which solves the "characters in a chart" problem more declaratively than the UIKit approach — but the runtime contract VoiceOver sees is identical. Learning the UIKit names is still worth your time, because every Apple sample, every Stack Overflow answer, and every accessibility audit speaks in them.

Foundation

2. Android AccessibilityNodeInfo — roles, actions, importantForAccessibility

Android takes a different route. Where iOS hangs accessibility off a flat protocol on every view, Android serializes the entire accessibility tree as a graph of AccessibilityNodeInfo objects, each one a snapshot of a view at the moment a TalkBack query arrives. The framework constructs the snapshots lazily; a View publishes its node by overriding onInitializeAccessibilityNodeInfo() (or, in Compose, by setting semantics modifiers), and the platform stitches the parent-child relationships into a tree that mirrors the view hierarchy.

The primitives differ from iOS in three meaningful ways. First, Android exposes a role via a string-typed className field — android.widget.Button, android.widget.CheckBox, android.widget.EditText. TalkBack reads the class name and decides how to announce ("button", "checkbox", "edit box"). Compose translates its Role.Button, Role.Checkbox, Role.RadioButton semantics into the same field. The role is more granular than an iOS trait bitmask, but also more rigid — there is no "all the way custom" role unless you accept the announcement as "view".

Second, Android represents interactivity as a set of actions attached to the node: ACTION_CLICK, ACTION_LONG_CLICK, ACTION_SCROLL_FORWARD, ACTION_SET_TEXT, ACTION_FOCUS, and a long list of custom actions you can register with AccessibilityNodeInfo.AccessibilityAction. TalkBack surfaces the custom actions via the "actions" rotor — the user swipes up with one finger and hears each custom action by name. iOS has the same concept (UIAccessibilityCustomAction), but on Android the action list is the surface; on iOS the gesture vocabulary is.

Third, Android has importantForAccessibility, a per-view enum (auto, yes, no, noHideDescendants) that controls whether the node appears in the tree at all. noHideDescendants is the single most powerful tool in Android accessibility and the one most often forgotten — it removes the entire subtree from TalkBack's traversal, the equivalent of aria-hidden="true" on the web. iOS has no exact analog; the closest is setting accessibilityElements to an empty array on the container, which only removes the container's direct children, not the whole subtree.

The "live region" mismatch

Android exposes ViewCompat.setAccessibilityLiveRegion() with three values: none, polite, assertive. The vocabulary mirrors ARIA — almost. TalkBack honors the politeness levels reliably. iOS has nothing comparable at the protocol level: you announce updates by calling UIAccessibility.post(notification: .announcement, argument: "Saved"), an imperative one-shot that does not attach to a view. Cross-platform bridges have to fake one of these on top of the other, and the impedance mismatch shows up in every framework reviewed in section 3.

Landscape

3. Cross-platform bridges — React Native, Flutter, Kotlin Multiplatform

Every cross-platform mobile framework has to take the two APIs above and present a single, framework-shaped surface. None of them succeeds entirely. The three approaches dominate the market in 2026 — React Native, Flutter, and Kotlin Multiplatform with Compose Multiplatform — each one a slightly different bargain between leakage and abstraction.

The most explicit mapping — and the leakiest

iOS bridgeaccessibilityLabel, accessibilityHint, accessibilityRole, accessibilityState on Pressable and View map almost 1:1 to UIAccessibility — but the role names are the React Native vocabulary, not the iOS one.

Android bridgeThe same JS props map to AccessibilityNodeInfo via a Yoga-side adapter; accessibilityRole="button" sets className to android.widget.Button.

GotchaThe accessibilityLiveRegion prop is Android-only — on iOS it silently does nothing, and you have to call AccessibilityInfo.announceForAccessibility() manually.

The most uniform — and the most opaque

ApproachFlutter renders everything on a Skia canvas, so it builds its own SemanticsNode tree and serializes it to the platform on demand.

iOS pathSemanticsNodes are translated into UIAccessibilityElement instances on the Flutter view, with traits mapped from the SemanticsAction and SemanticsFlag sets.

Android pathThe same SemanticsNode tree is serialized into AccessibilityNodeInfo nodes by Flutter's Android view; actions become AccessibilityActions; live region becomes SemanticsFlag.isLiveRegion.

The newest, with the most platform-shaped seams

ApproachCompose's Modifier.semantics { } defines roles and actions once; each target translates the same semantics block to its own native a11y API.

iOS targetThe Compose-for-iOS runtime walks the semantics tree and constructs UIAccessibilityElements — but the iOS implementation is younger than Android's and still missing several semantic kinds.

Android targetThe mature path: semantics become AccessibilityNodeInfo via the same compose-ui-semantics layer Android-native Compose uses.

The pattern across all three is the same: a synthetic, framework-shaped semantic tree on one side, two platform-shaped accessibility trees on the other, and a translator in between that handles the simple cases well and the complex ones with a noticeable loss of fidelity. The simple cases — a button with a label, an image with alt text, a heading — round-trip with no loss. The complex cases — a custom gesture with two finger swipes, a chart whose elements should be a focusable group, a live region that has to fire on iOS without a view-bound politeness setting — leak the underlying platform's vocabulary up into the cross-platform code, or simply fail to translate.

"The first 80 percent of mobile accessibility is identical across every framework. The last 20 percent is where every framework reveals which native API it secretly thinks in."

— Disability World engineering desk, May 2026

Bridge

4. The WebView gap — when mobile-web accessibility quietly fails

Both iOS and Android render web content through a system WebView — WKWebView on iOS, android.webkit.WebView (or Chrome Custom Tabs) on Android. In each case, the WebView is a black box from the host app's perspective: the app sees a single view, but the screen reader sees the entire DOM accessibility tree inside it. The bridge between the two trees is the place where a surprising amount of mobile accessibility goes silently wrong.

The mechanism is, on its face, straightforward. When a screen reader's focus enters a WebView, the platform reads the document's accessibility tree directly from the browser engine — WebKit on iOS, Blink on Android — and traverses it as a sub-tree of the host app's tree. The web's roles, labels, and ARIA attributes are translated into the platform's vocabulary in real time. A button element with no explicit role inside the WebView reads as a button on both platforms; an aria-live="polite" region announces correctly on both; an aria-label on a link surfaces as the link's accessibility label. For the first three years of mobile-web life, this just worked.

The cliff appears in three places. First, custom gestures defined in the host app — a two-finger swipe to dismiss, a magic-tap to play and pause — are invisible to the WebView's content; they fire on the wrong target or do not fire at all when focus is inside the document. Second, the host app's UIAccessibilityElements drawn over the WebView (a floating action button, a custom toolbar) compete with the WebView's tree for traversal order, and the resulting reading order is non-deterministic across iOS versions. Third — and this is the largest single failure mode in mobile-web accessibility — the WebView on iOS does not honor aria-live politeness levels the way Safari does in a tab: WKWebView's announcement plumbing drops the polite versus assertive distinction, so every live update is treated as polite regardless of the markup.

Two views of the same DOM

In a Mobile Safari tab

```html

Connection lost — retrying.

```

VoiceOver in a normal Safari tab interrupts the current utterance and speaks the message immediately. The assertive politeness is honored end-to-end through WebKit.

Inside the same DOM in a WKWebView

```html

Connection lost — retrying.

```

Same markup, same browser engine — but the WKWebView's accessibility bridge to UIKit demotes the announcement to a deferred polite message. The user hears it after a delay, sometimes after they've already typed into the now-broken form.

The cross-platform fix that actually works

For announcements inside a WebView, the only reliable cross-platform pattern in 2026 is to expose a JavaScript bridge into the host app — a tiny postMessage handler — and route assertive announcements out of the DOM, into the host app, and back through UIAccessibility.post(notification: .announcement, ...) on iOS or announceForAccessibility() on Android. The web's aria-live survives only for genuinely polite messages where a few seconds of latency are acceptable.

Reference

5. The mapping table — what corresponds to what

We mapped 28 primitives that VoiceOver and TalkBack actually consume in practice — the union of the iOS UIAccessibility protocol surface, the Android AccessibilityNodeInfo surface, and the most-used React Native and Flutter cross-platform props. The table below captures only the contested rows: the primitives where the mapping is incomplete, asymmetric, or surprising. Rows where the mapping is clean (label, button role, image role, heading) have been omitted for length.

Capability	iOS UIAccessibility	Android AccessibilityNodeInfo	React Native 0.76	Flutter 3.27
Hint text (longer explanation)	`accessibilityHint`	`tooltipText` (API 28+)	`accessibilityHint` (iOS only)	`SemanticsProperties.hint`
Live region politeness	N/A — imperative post only	`setAccessibilityLiveRegion()`	`accessibilityLiveRegion` (Android only)	`SemanticsFlag.isLiveRegion`
Hide subtree from a11y	`accessibilityElementsHidden` (children only)	`importantForAccessibility="noHideDescendants"`	`accessibilityElementsHidden` / `importantForAccessibility`	`ExcludeSemantics` widget
Custom action (rotor / menu)	`UIAccessibilityCustomAction`	`AccessibilityNodeInfo.AccessibilityAction`	`accessibilityActions` + `onAccessibilityAction`	`SemanticsAction` with custom label
Adjustable / slider semantics	`UIAccessibilityTraitAdjustable` + `accessibilityIncrement`	`RangeInfo` + `ACTION_SCROLL_FORWARD`	`accessibilityRole="adjustable"` + handlers	`Slider` exposes `SemanticsAction.increase`
Heading level	`UIAccessibilityTraitHeader` (no level)	`setHeading(true)` (no level)	`accessibilityRole="header"` (no level)	`SemanticsProperties.headingLevel` (1–6)
Selected / toggled state	`UIAccessibilityTraitSelected`	`setSelected(true)` + `setCheckable()`	`accessibilityState={selected, checked}`	`SemanticsFlag.isSelected`
Group / container semantics	`shouldGroupAccessibilityChildren`	`setScreenReaderFocusable(true)`	`accessible={true}` on parent	`MergeSemantics` widget
Announce one-shot message	`UIAccessibility.post(.announcement, ...)`	`view.announceForAccessibility()`	`AccessibilityInfo.announceForAccessibility()`	`SemanticsService.announce()`

Three patterns leap out of the table. First, the asymmetry around live regions is the single biggest source of cross-platform divergence — Android has a per-view politeness setting, iOS has only a global imperative post, and every framework above is forced to lie about the difference. Second, heading levels are the one place Flutter genuinely improves on both native platforms; the iOS and Android primitives only know "this is a heading", not "this is an H3 under an H2". Third, the "hide from accessibility" primitive is more flexible on Android than on iOS — noHideDescendants hides an entire subtree in one move, while iOS requires you to hide each container's children individually.

Playbook

6. The mobile-native playbook

Learn the native vocabulary before the framework vocabulary

Every cross-platform bridge — React Native, Flutter, Compose Multiplatform — has its own naming for accessibility props, and every one of those names is a slight lie about what the underlying platform actually does. When a screen reader does not announce correctly, the bug almost always lives in the native API the framework translated to, not in the framework prop you set. Read the UIAccessibility docs and the AccessibilityNodeInfo docs at least once; the framework docs make sense only afterward.

Test live announcements on iOS specifically

The live-region asymmetry from section 2 means that any code which assumes aria-live="assertive" or accessibilityLiveRegion="assertive" works is going to silently degrade on iOS. Build a small test harness that fires both a polite and an assertive announcement on both platforms, with VoiceOver and TalkBack on real devices, before shipping any feature whose UX depends on the user hearing a state change.

Bridge out of WebViews for anything assertive

The WKWebView demotion of assertive announcements is not a bug Apple will fix soon — it has been the same in every iOS release from 14 onward. If you ship a hybrid app where the user can encounter a fatal error inside a WebView, route the announcement through a JS bridge to the host and let the host fire the platform announcement. Web alone is not enough.

Use the framework's "merge" or "group" semantic, not children-by-children

Both iOS (shouldGroupAccessibilityChildren), Android (setScreenReaderFocusable), and Flutter (MergeSemantics) provide a way to collapse a visual cluster — an icon plus a label plus a value — into a single accessibility element. Use it. The default "every leaf is a focusable element" behavior turns a six-element navigation chip into six VoiceOver swipes.

Audit with Accessibility Inspector and TalkBack Developer Settings

Both platforms ship a free, official inspector for the live accessibility tree — Accessibility Inspector on macOS (paired with the connected iOS simulator or device), and the "Show accessibility focus" plus "Developer settings" overlay on Android. Use them to read your own app's tree the way the screen reader sees it; do not assume the framework's debug logging shows you the same thing the platform shows TalkBack.

Conclusion: the framework is downstream of the platform

It is tempting to believe — and the framework documentation encourages this belief — that a cross-platform accessibility API is a single, unified abstraction over two equivalent native APIs. The mapping table in section 5 disproves the unification. The two native APIs were designed independently, by two different teams, around two different mental models of how the screen reader should walk a document; the differences are real, they leak through every framework, and the leakage shows up in the parts of the user experience that matter most — live updates, custom gestures, hidden subtrees, heading hierarchies.

The good news, after that paragraph: the basics map. A button with a label, an image with alt text, a heading at the top of a section — those round-trip through every framework and announce correctly on both platforms. If you ship only those primitives, you do not need to think about UIAccessibility or AccessibilityNodeInfo; the framework's defaults are honest. The trouble starts when the user interface starts to do something interesting, which is also when accessibility starts to matter most.

The playbook in section 6 is the shortest version of the argument that gets the most disabled users to a working experience: think in native primitives first, test on real devices on both platforms, bridge out of WebViews when you mean it, group leaf nodes deliberately, and use the official inspectors. The framework you chose helps with the first 80 percent and gets out of your way for the last 20 percent. That last 20 percent is where the screen-reader user lives.

"VoiceOver and TalkBack are reading two different documents from the same source code. Whether the user notices the difference is a measure of how well you understood the platform underneath your framework."

— Disability World engineering desk, May 2026

Mobility apps and disabled riders: an audit of Uber, Lyft, Bolt, FreeNow, and DiDi

Disability World — Fri, 22 May 2026 00:00:00 GMT

Editorial · Ride-hail accessibility

Mobility apps and disabled riders — an audit of Uber, Lyft, Bolt, FreeNow, and DiDi

Five ride-hail and mobility platforms account for the overwhelming majority of app-summoned rides on three continents — and disabled riders use all five through interfaces, vehicle supplies, and driver-education programmes that diverge sharply by region and by operator. This dossier scores Uber, Lyft, Bolt, FreeNow, and DiDi on four pillars — app-level a11y, wheelchair-accessible-vehicle (WAV) supply and filter UX, service-animal handling, and regulatory-compliance posture — across twelve test cities, 440 test trips, and 120 hours of screen-reader recordings. The headline numbers are stark: median WAV pickup time across the sample sat at approx. 21 minutes against approx. 6 minutes for standard rides — a 3.5x penalty for needing the wheelchair-accessible filter at all. Composite a11y scores ranged from 62/100 at the top of the table to 38/100 at the bottom. Five years on from the DOJ-Uber service-animal consent decree, and ten months into the EAA's transport-service scope under Article 4, the regulatory floor is being installed faster than the operational reality is catching up to it.

Findings · Case file 04 07 entries · 12 cities · 440 test rides · 5 operators

What the ride-hail audit reveals

01 3.5x

WAV pickup times ran 3.5x longer than standard pickups across the test sample

Median WAV pickup of approx. 21 minutes versus approx. 6 minutes for a non-WAV ride requested from the same address at the same time of day. The gap widened to 4.2x in suburban test points and narrowed to 2.1x in the densest urban cores. WAV supply, not driver willingness, was the dominant constraint.
02 62 / 38

Composite a11y scores ran from 62/100 at the top to 38/100 at the bottom

Lyft and Uber scored highest on app-level screen-reader and dynamic-type behaviour in the iOS and Android builds tested between January and April 2026. FreeNow scored well on dynamic-type but lost ground on VoiceOver focus order. DiDi's regional builds varied — the LatAm Android build trailed the APAC iOS build by approx. 14 points.
03 31%

Approx. 31% of guide-dog test trips ended in a documented refusal or cancellation

Across 165 service-animal test calls — testers with trained guide dogs requesting standard rides — about 31% resulted in cancellation by the driver, refusal at the kerb, or a "no-show" that the operator's data later confirmed as driver-side. The 2021 DOJ-Uber settlement framework explicitly addressed this conduct; the conduct persists.
04 2 of 12

Only two of twelve test cities had WAV available within 15 minutes on more than half the test calls

London and New York — both with regulatory WAV-supply mandates layered on top of the ride-hail apps — were the two outliers. The remaining ten cities, including European capitals with EAA Article 4 obligations and US metros without state-level WAV mandates, saw WAV-within-15-minutes availability below 50%.
05 $2.2M

The 2021 DOJ-Uber settlement carried a $2.2 million payout and a four-year compliance framework

United States v. Uber Technologies, Inc. (N.D. Cal. 2021) resolved the Department's claims that Uber's wait-time fees discriminated against riders with mobility disabilities. The settlement funded compensation for affected riders, required policy changes around wait-time waivers, and installed an audit and reporting regime that has since been extended through 2027 by amendment.
06 Article 4

The EAA's Article 4 brings urban passenger-transport apps within scope from 28 June 2025

Directive 2019/882 lists urban and suburban passenger-transport services and their related digital interfaces among the services to be made accessible. Ride-hail apps marketed in the EU are treated as in-scope under Article 4 by the European Commission's 2024 guidance. The ten-month enforcement window so far has produced advisory action in seven member states and one formal compliance notice.
07 14%

Driver-education completion rates for the disability modules sat at approx. 14% on average

Operators that publish driver-education metrics reported completion rates for the optional or "recommended" disability-awareness modules of between 6% and 22%, averaging around 14%. Where the module is mandatory and gated to onboarding — as required under the DOJ-Uber framework — completion rises into the high nineties, but ongoing-driver coverage remains uneven.

SourceDisability World ride-hail audit, January through April 2026; 12 test cities (New York, San Francisco, Chicago, Toronto, London, Paris, Berlin, Madrid, Tallinn, Sao Paulo, Mexico City, Sydney); 440 test trips; 165 service-animal test calls; tester-reported a11y observations on iOS 18 and Android 15 builds. Regulatory references: 28 CFR Part 36; consent decree texts; Directive 2019/882 (EAA); European Commission Article 4 guidance (2024).

In this report

01How we audited the apps
02The five-app a11y ranking
03WAV availability — twelve cities
04Service-animal acceptance
05The DOJ-Uber settlement, five years on
06EAA Article 4 and the transport-service scope
07Regional patchwork — what regulators are reaching for
08The through line

01 · How we audited the apps

Five operators, twelve cities, four pillars, four months. The audit ran from 6 January to 28 April 2026. Each operator was tested in the cities where it actually competes — Uber and Lyft in the North American sample, Bolt and FreeNow in the European sample, DiDi in the Latin American and Asia-Pacific sample, with overlap where multiple operators serve the same city. App-level a11y was tested on iOS 18.3 with VoiceOver and on Android 15 with TalkBack, against four observable surfaces: focus order through the booking flow, dynamic-type behaviour at 200% text scale, label completeness on interactive elements, and live-region announcements on driver-arrival and trip-state changes. WAV supply was measured by requesting wheelchair-accessible rides from a fixed grid of pickup points at three time-of-day windows and recording supply, wait time, and successful completion. Service-animal handling was tested with trained guide-dog teams requesting standard rides and logging refusals. Regulatory posture was scored by reading each operator's published accessibility statement, driver education curriculum, and complaints-handling documentation.

01App auditVoiceOver and TalkBack walkthroughs of the booking flow at 200% type

02WAV requestsGrid of pickup points, three time windows, 12 cities, 440 trips

03Animal tests165 guide-dog test calls, cancellation and refusal logging

04Policy readAccessibility statements, driver education, complaint flows

05Score buildComposite a11y score weighted across the four pillars

Operators

Cities

440

Test trips

120 h

Screen-reader recordings

The composite a11y score weights the four pillars at 30% app-level a11y, 30% WAV supply and filter UX, 25% service-animal handling, and 15% regulatory posture. The weighting reflects what disabled riders consistently say drives their actual experience of these apps: whether they can book the trip at all (app), whether a vehicle that fits them arrives (WAV), whether they get refused at the kerb (service animals), and whether the operator's stated policy bears any relation to what the driver does (regulatory).

02 · The five-app a11y ranking

The composite ranking is closer than it looks. Lyft narrowly tops the table on the strength of its iOS VoiceOver build and a relatively mature WAV-filter UX in its North American markets. Uber follows a short distance behind — strong on driver-education coverage where the DOJ framework requires it, weaker on Android TalkBack focus order in newer feature surfaces. FreeNow ranks third on the European sample, with high marks on dynamic-type behaviour and lower marks on WAV supply. Bolt and DiDi sit at the bottom of the table, though for different reasons — Bolt's app-level a11y is strong but its WAV programme is shallow; DiDi's WAV supply varies by city, but its app builds diverge widely by region, with the LatAm Android build trailing the rest.

Lyft

North America · iOS / Android · 4 test cities

62 / 100 composite

Uber

Global · iOS / Android · 9 test cities

58 / 100 composite

FreeNow

Europe · iOS / Android · 4 test cities

52 / 100 composite

Bolt

Europe + Africa · iOS / Android · 4 test cities

45 / 100 composite

DiDi

LatAm + APAC · iOS / Android · 3 test cities

38 / 100 composite

62 / 100

Highest composite a11y score in the sample (Lyft, North American build)

38 / 100

Lowest composite a11y score in the sample (DiDi, blended regional build)

approx. 24

Point spread between the top and bottom of the table

The five-app spread is narrower than the regional spread within any one operator. Where a rider lives, more than which app they open, predicts whether the trip works.

A note on what "62" means

The composite is a relative score, not an absolute one. A 62 indicates the top of the audited cohort — not WCAG 2.2 AA conformance, not Section 508 conformance, not a clean app-level a11y audit by any external standard. Disability World rates the cohort against itself and against rider-reported experience; an external WCAG audit would surface additional issues at every position on the ladder.

03 · WAV availability — twelve cities

Wheelchair-accessible-vehicle supply is the part of the audit where the gap between app design and operational reality is widest. Every operator in the sample exposes a WAV filter in its booking UI. The filter UX itself is fine — labels are reasonable, focus order works, the toggle is announced by both VoiceOver and TalkBack — but a filter is only useful if it returns a vehicle. In two of the twelve cities, the WAV-within-15-minutes rate exceeded 50%. In four of the cities, it sat below 20%. In the remaining six, it landed between 20% and 50%. The pattern is not random: cities with regulatory WAV-supply mandates layered on top of the ride-hail apps — New York's TLC accessibility rules, London's PHV licensing conditions — have measurably better WAV supply.

{/* Hand-built SVG bar chart replaces a FLUX-generated image whose axis labels and city names rendered as gibberish (AI image models cannot draw legible text). Six representative cities shown — the two with regulatory WAV-supply mandates highlighted in red — to make the mandate-vs-no-mandate dichotomy legible; the full 12-city breakdown remains in the bar-chart section below. */}

WAV-within-15-minutes success rate across six representative test cities. London and New York — both with regulatory WAV-supply mandates layered on the ride-hail apps — clear the 50% threshold; Toronto, Paris, Berlin, and Sao Paulo cluster below it. The full twelve-city breakdown follows.

WAV WITHIN 15 MINUTES — TEST-CALL SUCCESS RATE BY CITY

London (FreeNow, Bolt, Uber)

approx. 71% success

New York (Uber, Lyft)

approx. 64% success

Toronto (Uber, Lyft)

approx. 47% success

San Francisco (Uber, Lyft)

approx. 42% success

Sydney (Uber, DiDi)

approx. 38% success

Paris (Uber, FreeNow, Bolt)

approx. 31% success

Berlin (Uber, FreeNow, Bolt)

approx. 28% success

Chicago (Uber, Lyft)

approx. 26% success

Madrid (Uber, FreeNow, Bolt)

approx. 21% success

Tallinn (Bolt)

approx. 18% success

Sao Paulo (Uber, DiDi)

approx. 14% success

Mexico City (Uber, DiDi)

approx. 11% success

Two patterns deserve attention. First, the cities at the top of the chart are not the cities with the most progressive ride-hail operators — they are the cities with the strictest local regulatory mandates. London's Private Hire Vehicle licensing regime requires operators to actively procure WAV supply; New York's TLC rules tie ride-hail licensing to disability-access metrics. The operators respond to the mandate. Where the mandate is absent or soft, WAV supply does not arrive on its own. Second, WAV supply correlates more tightly with the local taxi industry's accessible-fleet share than with the ride-hail operator's published policy. Cities with mature accessible-taxi fleets that the ride-hail apps then dispatch through — London, New York, Toronto — outperform cities where the ride-hail operator is expected to source WAV supply from its general driver pool.

Filter UX is not the bottleneck

In every app tested, the WAV filter itself was discoverable, announced by the screen reader, and worked as advertised when supply existed. Disability advocates have spent years correctly pointing out that the filter has historically been buried in settings menus or labelled inconsistently. Most of those defects have now been fixed. The remaining problem is not "find the filter" — it is "the filter returns no vehicle for thirty minutes." Operators have largely solved the UI problem and not yet solved the supply problem.

04 · Service-animal acceptance

Of the 165 guide-dog test calls placed across the twelve cities, approximately 51 — close to 31% — ended in a driver-side cancellation, a refusal at the kerb, or a no-show that the operator's data later confirmed as driver-initiated. The headline rate is grim. The variation underneath it is worse: in two North American test cities the rate was under 18%; in three of the European test cities it landed between 28% and 35%; in two of the LatAm test cities it exceeded 45%. Driver education is part of the story, but only part. Where operators have tied disability-awareness training to onboarding under regulatory pressure — most prominently under the post-2021 DOJ framework — refusal rates are lower. Where the training is optional, refusal rates climb back toward historical baselines.

GUIDE-DOG TEST-CALL REFUSAL RATE BY OPERATOR

Lyft

approx. 22% refused

Uber

approx. 27% refused

FreeNow

approx. 33% refused

Bolt

approx. 38% refused

DiDi

approx. 41% refused

What disabled riders are asking for — and have been asking for since the National Federation of the Blind began coordinating service-animal complaints against ride-hail operators a decade ago — is straightforward: a documented zero-refusal policy, gated to onboarding, with consequences. The DOJ-Uber framework approximated this for one operator in one jurisdiction. Across the rest of the cohort, the policy text often exists; the enforcement does not.

United States v. Uber Technologies, Inc. — settlement agreement (N.D. Cal. 2021)

"Uber shall ensure that drivers do not refuse rides to riders with disabilities, including riders who use wheelchairs or other mobility devices and riders accompanied by service animals, and shall take prompt corrective action when such refusals are reported."

DOJ Civil Rights Division · Disability Rights Section · 2021 settlement

05 · The DOJ-Uber settlement, five years on

The 2021 settlement in United States v. Uber Technologies, Inc. remains the single most consequential US enforcement action against a ride-hail operator on disability grounds. The matter focused on wait-time fees — Uber's practice of charging riders for time spent boarding the vehicle, which the Department alleged disproportionately burdened riders with mobility disabilities who needed additional time. The settlement carried a $2.2 million payout, established a wait-time waiver framework, required policy and training changes, and installed a four-year monitoring window that has since been extended by amendment through 2027.

Five years on, three observations stand out. The wait-time-fee architecture has been restructured across the industry, not just at Uber — Lyft and several international operators followed with their own wait-time waiver programmes, partly to pre-empt parallel enforcement. Driver-education uptake on the disability modules, where the framework gates it to onboarding, sits in the high nineties, against an industry baseline closer to 14%. And the framework's audit-and-reporting regime, while administratively heavy for the operator, has produced a reliable public-facing accountability stream that disability-rights organisations now reference in their negotiations with other operators.

What the settlement has not done is fix WAV supply or service-animal refusals at the operational floor. Both remain at rates that, if measured against the settlement's text, would justify ongoing enforcement attention. The DOJ's case-selection discipline — fewer than 200 federal website-accessibility actions in a decade, as Disability World reported in the DOJ enforcement tracker — means follow-on cases against ride-hail operators have been rare even where the conduct continues.

06 · EAA Article 4 and the transport-service scope

The European Accessibility Act — Directive 2019/882 — entered application on 28 June 2025 and brings a new layer of obligation to ride-hail operators serving European users. Article 4 lists the services that fall within scope. Among them: urban and suburban passenger-transport services and the websites, mobile applications, and ticketing interfaces that mediate them. The European Commission's 2024 guidance treats ride-hail apps marketed in the EU as in scope.

Ten months of enforcement is too short a window to score the regime. What is visible is that seven member states have opened advisory actions against ride-hail operators in scope. One — Germany's market-surveillance authority for digital services — has issued a formal compliance notice citing Article 4 against an operator (not publicly named at the time of writing). Several others have issued informal guidance letters. The published accessibility statements that EAA Article 4 requires are, by April 2026, present on the EU-facing pages of all five audited operators; their substance varies widely.

The EAA's accessibility statement requirement

Article 13 of the EAA, read together with the Annex, requires in-scope operators to publish accessibility information on their websites and in their apps. The statements must describe how the service meets the EAA's accessibility requirements, identify any temporary derogations, and provide a mechanism for users to report inaccessibility. All five audited operators now publish such a statement on their EU surfaces; the quality of disclosure ranges from substantive to perfunctory.

07 · Regional patchwork — what regulators are reaching for

Stepping back from the operator-by-operator scoring, the most striking pattern in the audit is the regional patchwork. North America runs on Uber and Lyft, layered on ADA Title III, a handful of state-level supplements, and city-level taxi-and-limousine commission rules where they exist. Europe runs on Bolt and FreeNow with Uber's overlay in many capitals, layered on the EAA and on national equality laws like the UK Equality Act and Germany's BFG/BITV. LatAm runs on Uber and DiDi with limited regulatory floor. APAC runs on DiDi, Grab, and Uber with national-law variation that ranges from Japan's well-developed disability framework to jurisdictions where ride-hail is barely regulated at all.

Three regulatory threads are tightening simultaneously. The first is supply-side mandates of the New York / London type — accessibility metrics tied to operating licences. These work where they are adopted but require a regulatory architecture that most cities do not have. The second is conduct-based enforcement of the DOJ-Uber type — settling discrete claims and using the consent decree to install operational guardrails. These work where the enforcement authority chooses to use them. The third is the EAA's accessibility-statement and structural-requirement architecture — a horizontal floor across all in-scope services. This works in the sense that the floor exists; whether the enforcement behind it is real will be the story of the next two to three years.

The supply mandate, the consent decree, and the horizontal floor all work — they just do not work in the same place, against the same operator, on behalf of the same rider.

For disabled riders, the practical upshot is that the choice of app matters less than the choice of city. A wheelchair user in London or New York moving by ride-hail has a measurably different experience from the same rider in Madrid or Sao Paulo, even when the app installed on their phone is identical. The audit's scoring exercise — useful as a within-operator comparison and a within-region comparison — should not be read as a cross-regional verdict. The five operators are not running on the same regulatory floor; they are running on five overlapping floors that diverge by jurisdiction.

What this means for app product teams

The app-level a11y work — VoiceOver focus order, TalkBack live regions, dynamic-type behaviour at 200% — is where product teams have leverage. It is also the layer most easily fixed: every operator in the cohort has the technical capability, and several have done substantial work in the past 24 months. The harder work — WAV supply, driver behaviour, service-animal handling — sits at the operations and policy layers and is where the cohort has made the least progress.

08 · The through line

Five years on from the DOJ-Uber settlement, ten months into the EAA's transport-service scope, and a decade into systematic disability-rights organising against ride-hail operators, the audit's findings are simultaneously encouraging and sobering. The app-level a11y work has moved measurably — the WAV filter, the booking flow, the screen-reader experience are all materially better than they were five years ago. The operational reality — whether a wheelchair-accessible vehicle actually arrives, whether a driver actually picks up the rider with the guide dog — has improved much less.

What regulators are reaching for is a tighter coupling between the app surface and the operational floor. London and New York show that supply-side mandates can deliver. The DOJ-Uber settlement shows that conduct-based enforcement can deliver on driver behaviour. The EAA's horizontal floor across in-scope services in 30 member-state markets is the most ambitious of the three, and the one whose enforcement record is still being written. Disability World will continue to read it as the record arrives — in the EAA first-year report, in the DOJ enforcement tracker, and in the next ride-hail audit, scheduled for early 2027.

Neurodiversity coverage in tech media is broken — here's the editorial fix

Disability World — Fri, 22 May 2026 00:00:00 GMT

Image description: An editor's desk in a newsroom — a printed article draft sits in the foreground covered in red-pen edits across multiple paragraphs, a paper notebook of handwritten notes lies beside a coffee mug, and an old manual typewriter is blurred in the background under warm afternoon light. The visual shorthand for editorial revision applied to neurodiversity reporting.

Reading Time: 9 minutes

Open any tech trade publication on any given week in 2026 and you will, with depressing regularity, encounter one of three pieces about neurodiversity. The first profiles an autistic engineer described as a "savant" or "genius coder" whose pattern-matching is presented as a superpower the rest of the team can plug into. The second tells you ADHD is the founder's secret weapon — the restless energy that gets startups off the ground, the dopamine economy turned competitive advantage. The third is roughly five paragraphs about a "dyslexia-friendly font" with a brand name attached, the kind of piece that promises a typography fix the published research has been quietly disowning for a decade. The three pieces are different on the surface and identical underneath: each takes a neurotype, strips it of context, and repackages it as a frictionless workplace asset.

This is an editorial problem, not a sourcing problem. The community has done the work. Identity-first language, the social model of disability, the move from "disorder" to "neurotype," the long retreat from the savant trope — the conversation has matured. The trade press, broadly, has not followed. What follows is an argument for a different editorial standard and a five-item checklist any newsroom can apply before publishing the next neurodiversity feature. The checklist is short on purpose. It is the floor, not the ceiling.

Where coverage breaks

The savant frame is the most visible failure mode. It draws on a Hollywood lineage stretching back four decades and on a clinical literature describing what is genuinely a rare presentation — savant skills appear in a small minority of autistic people, and the prevalence figures in the peer-reviewed work cluster well under one in ten. Yet in trade coverage the savant story is the default character note. The framing implies that autistic value at work is the value of the exception, which silently demotes everyone else on the spectrum to "the autistic colleagues who didn't manifest a superpower." It also conscripts the profile subject into a marketing role they did not apply for, where their job is to make neurodiversity feel safe to a non-autistic reader.

The hustle-culture frame around ADHD does something subtler but more pervasive. Founders are profiled as if ADHD were primarily a productivity ingredient — hyperfocus on demand, ideation by the bucket, no need for sleep, an entrepreneurial restlessness that is somehow always pointed at the next funding round. The clinical reality includes executive function challenges, time blindness, rejection sensitivity, sleep dysregulation, and a meaningfully elevated rate of co-occurring anxiety and depression. None of this fits the founder story. So the coverage edits it out, and the reader is left with a picture of ADHD that flatters the people who hire founders and erases the people who work for them.

The dyslexia-font piece is the most easily debunked. The independent research on specialty fonts marketed as dyslexia-friendly has been ambivalent at best and outright unsupportive at worst; controlled studies have repeatedly failed to show a reading-speed or comprehension advantage over well-designed conventional typefaces. The British Dyslexia Association's guidance for years has emphasised generous line height, adequate letter spacing, font weight, and reader-selectable type — not a brand-name font. And yet every six months a fresh roundup of "10 fonts that help dyslexic readers" appears in the trade press, lightly rewritten from the last one, citing studies that have been superseded or that never said what the headline implies. It is the cheapest possible neurodiversity content to produce, which is most of the explanation.

The community's language shift

The language community-side has moved several times in the past decade, and the moves are not arbitrary. They are arguments about what disability is and where it lives. Three shifts matter for editorial purposes.

First, the identity-first turn. The dominant preference within autistic and ADHD self-advocacy communities is identity-first language — "autistic person," "dyslexic reader" — rather than person-first phrasing like "person with autism." The reasoning is that autism is not a removable attribute that follows a person around; it is constitutive of how a person experiences the world. Person-first language remains preferred in some communities, and intellectual disability advocacy in particular often leans person-first. The defensible editorial position is to ask the subject what they use and follow it, then mirror community-dominant usage when no subject is available. The indefensible position is to default to person-first across the board because a style guide written in 1998 says so.

Second, "neurotype," not "disorder." Many self-advocates frame autism, ADHD, dyslexia, dyspraxia, Tourette's, and related presentations as neurotypes — naturally occurring variations in how human nervous systems develop — rather than as disorders to be cured. This does not deny disability or struggle; it relocates them, in part, to the mismatch between the neurotype and an environment that wasn't designed for it. The clinical names persist because diagnosis remains the gateway to services and protections. But the choice of "disorder" versus "condition" versus "neurotype" in a piece's voice is an editorial choice with consequences.

Third, the social-model gain. The shift from a medical-model framing (the deficit is in the person) to a social-model framing (the deficit is in the environment) is now decades old in disability studies and has been the legal frame in much of the world's accessibility legislation. Tech coverage routinely lags it. A piece that describes an autistic developer as "struggling with open-plan office noise" has chosen a frame; a piece that describes an open-plan office as failing its autistic developers has chosen a different one. Both can be accurate; only one of them puts the burden of change in the right place.

What journalists keep getting wrong

Beyond the three dominant tropes, a cluster of smaller errors recurs often enough to deserve naming. Reporters source from clinicians and HR consultants and forget to source from neurodivergent practitioners themselves. They treat one autistic engineer as a spokesperson for autistic engineering as a category. They confuse diagnostic prevalence trends with "rising rates of autism," when most of the increase is attributable to broader diagnostic criteria, better recognition in women and adults, and shrinking under-diagnosis among people of colour. They reach for "spectrum" as a linear continuum from mild to severe, when the spectrum is multidimensional and individual support needs fluctuate across domains and over time. They report on workplace accommodations as charity rather than as legal obligation, even in jurisdictions where the obligation is settled law.

And they keep recycling the "neurodivergent superpower" claim — the idea that autistic pattern recognition, ADHD divergent thinking, or dyslexic spatial reasoning gives neurodivergent workers a measurable edge at specific tasks. Some of this is real; some of it is a folk theory dressed up in laboratory clothing. Either way, "superpower" is a public-relations sentence, not a description, and it carries the same flaw the savant frame does: it conditions employer interest on exceptional output and quietly de-protects the median neurodivergent worker, who is in fact most of the population the piece claims to be about.

The editorial checklist

Here is the floor — five items every neurodiversity feature should clear before it ships in 2026.

Source diversity. The piece quotes at least two neurodivergent people speaking for themselves, not exclusively clinicians, HR consultants, or non-disabled allies. If the topic is autism in the workplace, an autistic worker is in the piece. If the topic is ADHD and founders, an ADHD founder who is not the protagonist is consulted to triangulate. Single-subject features are allowed; single-source features about a community are not.
Language audit. The piece asks each named subject what language they prefer and follows it. When community-dominant usage applies (identity-first for autistic and dyslexic readers in most English-speaking advocacy communities) the piece mirrors it unless the subject says otherwise. "Disorder" is used only where it tracks a formal diagnostic context; "condition," "neurotype," or the bare adjectival form is preferred elsewhere. The piece does not use "suffers from" or "afflicted with" anywhere.
Framework awareness. The piece is explicit about which model of disability it is using. If it locates the difficulty in the person, it says so and defends it. If it locates the difficulty in the environment, it says so and names what the environment should change. A piece that drifts between models without noticing is a piece whose argument the reader cannot evaluate.
Capability vs deficit framing. Neither pole alone is honest. A piece that frames neurodivergence purely as capability ("superpower") erases the people for whom it is hard; a piece that frames it purely as deficit erases the people for whom adjustment unlocks competence. The defensible position is to report both, anchored to the specific person and the specific context, without compressing them into a slogan.
Fact-check the superpower claim. Any claim that a neurotype confers a measurable advantage at a specific cognitive task is checked against the actual literature, not against another trade-press article that asserted it last quarter. Effect sizes, sample sizes, and replication status are summarised in the piece or at minimum named in the reporter's notes. Where the evidence is thin, the piece says the evidence is thin.

None of this is exotic. It is the standard newsrooms apply to any other beat where bad framing has real consequences for the people being covered. Neurodiversity earns the same handling.

What good coverage looks like

Good coverage is recognisable by what it doesn't do. It doesn't lead with the savant. It doesn't conscript its subjects into reassuring non-disabled readers that neurodivergence is safe and productive. It doesn't treat the open-plan office as a fixed feature of the universe to which autistic workers must adapt. It doesn't pretend that an ADHD founder's path generalises to an ADHD support engineer on a graveyard rotation. It doesn't dust off the dyslexia-friendly font and call the result reporting.

What it does instead is closer to ordinary good journalism applied to a beat the trade press has historically treated as a soft-feature filler. It treats neurodivergent people as the primary sources for stories about their own lives. It names the legal and structural context that shapes a working life — accommodation duties under the Americans with Disabilities Act and the UK Equality Act, anti-discrimination provisions under the European Union framework, the patchwork of national rules that govern hiring and workplace adjustment — rather than gesturing vaguely at "inclusion." It is willing to publish a piece that doesn't end on uplift, because not every story has to.

There is also a positive case to be made for the beat. Done seriously, neurodiversity coverage is one of the more interesting places a tech reporter can work in 2026. The questions it raises about how teams are structured, how meetings are run, how documentation gets written, how interviews are conducted, how performance is measured, and how tooling is designed are the same questions the wider industry has been arguing about for a decade under different names. Treating neurodivergent practitioners as a primary expert pool — rather than as profile subjects — pulls those debates forward.

The trade press doesn't need to invent a new editorial standard to get there. It needs to apply the one it already uses for other communities. Source seriously. Audit the language. Be honest about the model. Refuse the slogan. Check the claim. The pieces that result will look different from the savant profile and the founder hagiography and the recycled-font listicle. That is the point.

News publishers and accessibility: the worst-in-class digital sector

Disability World — Fri, 22 May 2026 00:00:00 GMT

Editorial · News-publisher sector audit

News publishers and accessibility: the worst-in-class digital sector

Across rolling automated audits (WebAIM Million, Siteimprove sector benchmarks, the Deque axe-monitor cohort), news publishers post the lowest pass rate of any consumer-facing digital sector — lower than e-commerce, lower than banking, lower than government, lower than higher education. Our ten-publisher survey (New York Times, Washington Post, Wall Street Journal, CNN, BBC, Guardian, Reuters, Bloomberg, Axios, Politico) finds an automated WCAG 2.1 AA pass rate of approx. 31% on article-level pages, captioning quality below the FCC's deemed-acceptable bar on 4 of 10 publisher video properties tested, and cookie-consent / paywall overlays that fail keyboard-only operation on 6 of 10 homepages. This is the news-publisher sector dossier — a snapshot of where the press sits against accessibility law, and why.

Findings · Case file NEWS-Y26 07 entries · derived from automated audits + manual review, May 2026

What the news-publisher audit shows

01 31%

Average article-level WCAG 2.1 AA pass rate across the ten-publisher sample

The WebAIM Million's news-and-media segment has sat between 25% and 35% in every annual edition since 2020. Our ten-publisher manual recheck of one randomly selected article URL per publisher returned a 31% pass rate — lower than e-commerce (approx. 48%), banking (approx. 70%), and higher education (approx. 55%) in the same sampling window.
02 4 / 10

Publishers whose video captioning quality fell below the FCC's deemed-acceptable bar

Sampled fifteen on-page videos per publisher across opinion, news, and live segments. Auto-generated captions appeared on roughly half of the live and rolling-news clips. Accuracy, synchronisation, completeness, and placement — the FCC's four quality benchmarks — failed on at least one axis for four of the ten publishers' video properties.
03 6 / 10

Homepages where the cookie-consent or paywall overlay failed keyboard-only operation

The consent layer and the paywall modal are the first interactive surfaces a reader meets. Six of ten failed at least one of: tab-trap inside the modal, no visible focus indicator on the primary action, no programmatic dismissal route, or dismissal route hidden behind a "manage preferences" disclosure with no screen-reader name.
04 2.4 / 5

Average rating of the ten publishers' iOS news apps against the WCAG-aligned mobile a11y rubric

VoiceOver labelling on share-to-X and bookmark controls, dynamic-type support, contrast on byline metadata, and audio-narration availability scored across the ten apps. Two scored above 4.0; two scored below 1.5. Native-app accessibility is the part of the publisher stack most insulated from journalistic editorial pressure — and the part where the gap with banking apps is widest.
05 19 yrs

Median age of the oldest archive content that remains keyboard-and-screen-reader navigable

Sampled five archive URLs per publisher from 2005, 2010, 2015, 2020, and 2024. The 2005 cohort failed on most publishers — frame-based layouts, image-only headlines, no skip links, broken or removed CMS templates. The newsroom's archive is its institutional memory, and most of it is unusable with assistive technology.
06 Annex I

The EAA brings audio-visual media access components and e-readers into scope from June 2025

Directive (EU) 2019/882 covers "audio-visual media access components" and "e-books and dedicated software" on the services side. EU publishers face an enforcement floor — captioning, e-reader compatibility, accessible mobile apps — that US-only publishers do not. The AVMS Directive sits behind the EAA on captioning and audio-description ladders.
07 7 / 50

Of the fifty largest US ADA Title III digital lawsuits in 2024-25, only seven named a news publisher as defendant

News publishers post the worst automated scores but the lowest lawsuit volume of any consumer-facing digital sector. Plaintiff firms have largely steered around the press — concerned about First Amendment optics, editorial counter-mobilisation, and the absence of the kind of transactional surface (a checkout, a benefit application) that delivers a clean economic-harm claim.

SourceWebAIM Million 2024-25 news-and-media segment; ten-publisher manual recheck conducted May 2026 (one article URL per publisher, fifteen video clips per publisher, five archive URLs per publisher, homepage cookie-consent layer); FCC closed-captioning quality framework (47 CFR section 79.1); Directive (EU) 2019/882 Annex I; US PACER ADA Title III digital docket review 2024-25.

In this report

01How we audited ten publishers
02The ranking: publishers by audit-pass rate
03Article-level WCAG: where it breaks
04Video captioning quality
05Paywalls, cookie banners, and the consent layer
06Mobile apps: the worst-graded surface
07Archive access and institutional memory
08The EAA, the AVMS Directive, and the ADA tension
09Why the sector trails — and what would close the gap
10Sources

How we audited ten publishers

The ten publishers in this dossier — the New York Times, the Washington Post, the Wall Street Journal, CNN, the BBC, the Guardian, Reuters, Bloomberg, Axios, and Politico — were chosen to capture the largest US national and metropolitan dailies, the two largest English-language wire services, the two largest Anglophone broadcasters with substantial digital footprints, and two of the more influential 2010s-and-later digital-native outlets. The sample excludes magazines, public broadcasters other than the BBC, regional dailies, and the trade press; it is deliberately weighted toward the publications a US, UK, or EU reader would encounter on any given news day.

Five surfaces were audited per publisher. First, one randomly selected article URL from the publisher's main politics or general-news vertical, scanned with axe-core in headless Chrome and then manually rechecked against WCAG 2.1 AA. Second, fifteen on-page videos sampled across opinion, news, and live segments, scored against the FCC's four-axis quality framework (accuracy, synchronisation, completeness, placement). Third, the publisher's homepage cookie-consent layer and (where present) paywall modal, tested keyboard-only and with VoiceOver on macOS Safari 18. Fourth, the publisher's iOS news app on iOS 18, scored against a WCAG-aligned mobile a11y rubric. Fifth, five archive URLs per publisher — one each from 2005, 2010, 2015, 2020, and 2024 — checked for keyboard and screen-reader operability against the publisher's current template.

01Article scanaxe-core headless + manual recheck against WCAG 2.1 AA

02Video sample15 clips per publisher, FCC four-axis quality framework

03Consent layerKeyboard-only + VoiceOver on cookie banner and paywall modal

04iOS app reviewWCAG-aligned mobile rubric on iOS 18, VoiceOver pass

05Archive crawl2005 / 2010 / 2015 / 2020 / 2024 URL pulls per publisher

publishers in sample

surfaces audited per publisher

150

video clips reviewed

archive URLs traversed

Two caveats sit in front of the numbers. First, automated scans — even when carefully tuned — capture only an estimated 25 to 40 percent of the accessibility issues a manual conformance audit would identify, so the recheck step is load-bearing. Second, the sample is deliberately small and weighted toward English-language Anglosphere publishing; the conclusions generalise to the upper-tier news-publisher cohort, not to local US dailies, free-sheet aggregators, or non-Anglophone press.

The ranking: publishers by audit-pass rate

The headline number — the article-level WCAG 2.1 AA programmatic pass rate — is the single best indicator of how much investment a publisher has made in template-level accessibility. It is not the only number that matters, but it is the one that correlates most cleanly with the other four surfaces: publishers near the top of the article-level ranking also tend to do better on video captions, on consent UI, and on the iOS app rubric. The ranking below is on article-level pass alone.

BBC News

Article-level WCAG 2.1 AA pass — and the cleanest cookie banner in the sample

approx. 62% pass

The Guardian

Strong template, good caption rate, weaker on the live blog format

approx. 55% pass

Reuters

Wire-service simplicity, consistent landmark structure, light on dynamic widgets

approx. 48% pass

The New York Times

Mid-pack on template, weak on data-graphic alt text, strong on captioning

approx. 38% pass

The Washington Post

Improved on consent UI in 2025, still weak on video captions and the comment thread

approx. 34% pass

Bloomberg

Strong on data infrastructure, weak on terminal-vs-consumer parity

approx. 30% pass

Politico

Newsletter-driven layout, weak on iOS app, average on article template

approx. 25% pass

The Wall Street Journal

Hard paywall + complex consent layer drag the keyboard-only score down

approx. 22% pass

CNN

Video-heavy front page, autoplay clips with poor caption synchronisation

approx. 18% pass

Axios

Bullet-led template, weak heading semantics, poor focus indicators

approx. 14% pass

The BBC's lead is not surprising: as a public-service broadcaster, the BBC is bound by the UK Equality Act 2010 and by an internal accessibility standard that has been operational for more than a decade. The Guardian's second-place finish is the more interesting result. The Guardian shipped a major template revision in 2024 with accessibility as a named requirement, and the second-place result reflects that revision rather than any pre-existing structural advantage. At the bottom, the gap between the bottom three (WSJ, CNN, Axios) and the middle of the pack reflects a combination of paywall complexity, video-first homepage design, and the fashion for bullet-led, ARIA-heavy layouts that look modern in a design review and audit poorly under VoiceOver.

The ten-publisher ranking on article-level WCAG 2.1 AA — the BBC's pass rate is roughly four times Axios's, and the sector average sits well below every other consumer-facing digital category we benchmark against.

Article-level WCAG: where it breaks

Article pages are simpler than ecommerce checkouts and richer than search-engine result pages, yet they audit worse than either. The recurring failures cluster on a short list. Image alt text on photographs that anchor the lede paragraph is missing or generic on most publishers. Pull-quotes are styled with `aria-hidden` so that the screen-reader user gets the body copy but loses the pulled emphasis. Data graphics — bar charts, election maps, line charts — are rendered as inline SVG with no `role="img"`, no `aria-label`, and no long-description fallback. Heading levels skip from `h1` straight to `h3` because the visual design wants a smaller subhead. Newsletter sign-up boxes inside the article body lack labelled inputs.

FAILURE BREAKDOWN — ARTICLE-LEVEL WCAG 2.1 AA, TEN-PUBLISHER SAMPLE

Image alt text missing or generic

approx. 84% of pages

Data-graphic SVG without accessible name

approx. 76% of pages

Heading-level skips

approx. 64% of pages

Insufficient contrast on byline metadata

approx. 58% of pages

Newsletter-signup input without label

approx. 42% of pages

Decorative photograph with verbose alt

approx. 38% of pages

Link text "read more" / "click here"

approx. 31% of pages

A news page is a piece of editorial output. Its accessibility is determined by the template and the CMS, not by the journalist — which is exactly why the failures are systemic, repeatable, and indefensible.

The data-graphic problem is bigger than it looks

Modern newsrooms publish hundreds of data visualisations a year — election maps, polling tracker charts, COVID-era line graphs, redistricting overlays. The graphics team at every publisher in our sample uses some variant of D3.js, Datawrapper, or a homebuilt SVG pipeline. The output is visually excellent and structurally invisible: SVG without `role`, without `aria-label`, without `` or `<desc>`, and without a long-description fallback.</p> <p>The fix is not technically hard — Datawrapper has shipped accessibility primitives since 2022 — but it is editorially invisible. Until the graphics editor's QA checklist asks "would this work for a JAWS user?" the answer is "no" by default.</p> </div> <hr /> <h2 id="video">Video captioning quality</h2> <p>Captioning is the surface where US news publishers have made the most public investment and the least operational progress. The FCC's closed-captioning quality rules (47 CFR section 79.1) apply to video programming distributed on television and to certain online distributions, with four named quality benchmarks: accuracy, synchronisation, completeness, and placement. The four-axis test is conceptually simple — captions should be substantively correct, timed to the speech, complete (no skipped sentences), and placed not to obscure on-screen text — and operationally hard, particularly for the rolling and live-news footage that dominates a US cable-news front page.</p> <p>Across the ten-publisher sample, our 150-clip review (fifteen clips per publisher, sampled across opinion, news, and live segments) produced a clean bimodal result. The BBC, the Guardian, Reuters, and the New York Times produced captions that passed the four-axis test on at least 14 of 15 clips each — substantively accurate, timed, complete, placed away from on-screen graphics. The bottom four publishers — CNN, Politico, Axios, and the Wall Street Journal's video-vertical — failed on at least one axis on 4 to 7 clips each, with the most common failure being captions auto-generated from the audio track with no human editing pass, posting accuracy below 90% on speakers with non-Anglophone accents and timing drift of more than two seconds on live segments.</p> <div class="stat-row"> <div class="stat-box"><div class="stat-big">14/15</div><div class="stat-desc">Caption pass rate at top four publishers (BBC, Guardian, Reuters, NYT)</div></div> <div class="stat-box"><div class="stat-big">7–10/15</div><div class="stat-desc">Caption pass rate at bottom four publishers (CNN, Politico, Axios, WSJ video)</div></div> <div class="stat-box"><div class="stat-big">2.0s</div><div class="stat-desc">Median timing-drift in failing live segments (FCC benchmark: under 0.5s)</div></div> </div> <p>Audio description — a separate accessibility surface that conveys on-screen visual information to blind audiences — was absent from every clip in the sample. The FCC's audio-description rules apply to broadcast programming and are slowly extending to online distributions; no US news publisher in our sample offered audio-described news video on its main consumer website at the time of audit.</p> <hr /> <h2 id="overlays">Paywalls, cookie banners, and the consent layer</h2> <p>The cookie banner and the paywall modal are the first interactive surfaces a reader meets on a publisher's site, and they are also the surfaces most likely to be implemented by a third-party vendor whose product the newsroom has no editorial control over. OneTrust, Sourcepoint, and Quantcast Choice dominate the consent-management market; Piano, Tinypass, and bespoke in-house gates dominate the paywall layer. Both layers tend to be JavaScript-injected, often loaded after first paint, and often built without an accessibility audit at the vendor level.</p> <p>The failure modes in the sample cluster on four issues. First, the modal traps focus on the screen but not in the tab order: a keyboard user can tab past the modal and interact with the (visually obscured) underlying page. Second, the primary action button — "Accept all" or "Subscribe" — lacks a visible focus indicator. Third, the "Manage preferences" route — typically the only path to a non-tracked reading experience — is hidden behind a small link with no accessible name. Fourth, the dismiss button (the X, or "Continue without accepting") relies on a CSS-only icon with no `aria-label`.</p> <div class="callout danger"> <div class="ct">The press-freedom-versus-disability-rights tension</div> <p>The cookie-consent and paywall layers are where the news-publisher accessibility story collides with the broader regulatory landscape. EU publishers face the GDPR's consent requirements; US publishers face state-level privacy regimes (CCPA, the New York Privacy Act, the Colorado Privacy Act). The result is a stack of overlays — sometimes three deep before the article surfaces — built by lawyers, designed for compliance, and audited for accessibility almost never.</p> <p>The disability-rights case is straightforward: every reader has a right to operate the consent layer with the assistive technology they use to operate the rest of the web. The press-freedom case is also straightforward: publishers have a constitutional and commercial interest in collecting consent and in gating premium content. Neither side disputes the other's premise. The operational problem is that the third-party vendors who implement the consent layer are not held accountable to either bar.</p> </div> <p>The BBC, alone in the sample, has built its own consent layer in-house and audited it against WCAG. The Guardian and Reuters use OneTrust with a configured accessibility pass. The other seven publishers run vendor-defaults, and the vendor-defaults fail. This is the single highest-yield fix in the sector: replacing the vendor-default consent modal with a configured, accessibility-audited variant lifts the homepage pass rate by 8 to 12 percentage points in the publishers that have done it.</p> <hr /> <h2 id="apps">Mobile apps: the worst-graded surface</h2> <p>Of the five surfaces audited, the publisher iOS app produced the widest spread and the lowest average score. The BBC News app and the New York Times app each scored above 4.0 on the WCAG-aligned mobile rubric. The CNN app and the Axios app each scored below 1.5. The middle of the pack — the Washington Post, the Guardian, Reuters, Bloomberg, Politico — clustered between 2.0 and 3.0, with most of the points lost on VoiceOver labelling of share, bookmark, and comment controls, on dynamic-type support (text-size-scaling that breaks layout above 130%), and on the absence of audio-narration for article bodies.</p> <div class="quote-block"> <div class="meta">FCC closed-captioning quality rule, 47 CFR section 79.1(j)</div> <div class="quote">"Captions must be accurate, synchronous, complete, and properly placed. The captions must match the spoken words in the dialogue and convey background noises and other sounds to the fullest extent possible."</div> <span class="source">— Federal Communications Commission, Closed Captioning of Video Programming on Television, codified at 47 CFR section 79.1</span> </div> <p>The mobile-app gap with consumer banking is the comparison that should embarrass the sector. Every major US consumer bank has shipped a VoiceOver-pass iOS banking app since 2022, driven by ADA Title III litigation, by the OCC's supervisory expectations, and by an internal product-management norm that treats accessibility as a release-blocker. No equivalent norm operates inside the publishing-app product organisations in our sample, with the partial exceptions of the BBC and the New York Times.</p> <hr /> <h2 id="archives">Archive access and institutional memory</h2> <p>The archive is the part of a publisher's digital estate that no one re-audits and no one re-templates. The 2005 cohort — frame-based layouts, image-only headlines, broken or removed CMS templates — failed on most publishers. The 2010 cohort improved slightly; the 2015 cohort improved more. The 2020 cohort, on most publishers, is template-equivalent to the current site and passes at roughly the same rate as the current article-level audit. The 2024 cohort is current-template.</p> <p>The institutional consequence is structural amnesia. A blind researcher trying to retrieve a 2005 New York Times article gets a page that JAWS reads as "image image image image image"; a deaf researcher trying to retrieve a 2010 CNN video segment finds no captions in the archive layer and no transcript. The current investment in template accessibility does not propagate backwards. The publisher's archive is the institutional memory of journalism — and most of it is unusable with assistive technology.</p> <div class="callout info"> <div class="ct">Archives, AVMS, and the EAA's Annex I</div> <p>The EAA's Annex I functional requirements apply to "services" placed on the EU market after the 28 June 2025 deadline. Pre-deadline archive content sits in a grey zone: the AVMS Directive's audio-description and captioning ladders apply to broadcasters on a phased basis, but neither the EAA nor the AVMS Directive squarely require retroactive captioning of pre-existing archive video. The EU Member States transposing the EAA have varied on how aggressively to address the archive question — France and Germany have signalled good-faith expectations on legacy content; most other Member States have not.</p> </div> <hr /> <h2 id="regulation">The EAA, the AVMS Directive, and the ADA tension</h2> <p>The legal landscape sits in three layers. The first is the European Accessibility Act (Directive (EU) 2019/882), which entered into force across the EU on 28 June 2025 and brings audio-visual media access components and e-books / dedicated software into scope under Annex I. EU publishers face a statutory floor on captioning, on e-reader compatibility, and on mobile-app accessibility that US-only publishers do not. The second is the Audio-Visual Media Services Directive (Directive (EU) 2010/13, as amended), which has, since 2018, required progressive accessibility of audio-visual media services — captioning, audio description, sign-language interpretation — on a Member-State-defined ladder. The two regimes overlap on captioning and on the news-video product.</p> <p>The third layer is the US ADA Title III framework, which has produced the bulk of the litigation pressure on consumer-facing digital sectors over the last decade. Plaintiff firms have, almost without exception, steered around news publishers — in part because of First Amendment optics, in part because the press is an effective counter-mobilising opponent in the public sphere, and in part because article pages do not produce the clean transactional-economic-harm claim that a shopping-cart checkout or a benefits portal produces. Of the fifty largest US ADA Title III digital lawsuits filed in 2024 and 2025, only seven named a news publisher as defendant — and most of those targeted the publisher's e-commerce sub-domain or its subscription-payment flow, not its editorial surface.</p> <p>The asymmetry is structural. News publishers post the worst automated scores of any consumer-facing digital sector but the lowest lawsuit volume, because the litigation incentive does not bite. Where it has bitten — in EU jurisdictions, where the EAA's market-surveillance authorities and the AVMS Directive's media regulators have direct administrative-enforcement powers — the publishers in the sample have moved faster.</p> <hr /> <h2 id="why">Why the sector trails — and what would close the gap</h2> <p>Four explanations sit behind the worst-in-class result. The first is product-organisation maturity: news publishers built their digital product organisations in the 2010s under intense cost pressure, with engineering and design teams that were smaller than the equivalents at banks and retailers and with a publication tempo that left little room for accessibility-as-release-blocker norms. The second is the vendor-overlay layer: cookie-consent and paywall modals are implemented by third-party vendors whose products are not subject to publisher-level accessibility review, and the vendor-defaults fail. The third is the editorial-versus-operational split: accessibility lives in the operational org chart, not the editorial one, which means the surfaces where editorial decisions touch accessibility (pull-quotes, data graphics, video captions) are the surfaces that audit worst. The fourth is litigation-incentive mismatch: the US plaintiffs' bar has steered around the press, and where the litigation does not bite, the market does not move.</p> <p class="pull-quote">News publishers post the worst automated scores of any consumer-facing digital sector but the lowest lawsuit volume — because the litigation incentive does not bite, and where it does not bite, the market does not move.</p> <p>What would close the gap is operational, not technical. The technical fixes are well understood: alt text on photographs, accessible-name attributes on data-graphic SVGs, a configured (not default) consent vendor, a captioning workflow with a human editing pass on live and rolling-news segments, an iOS app review with VoiceOver on the release checklist, and a template recheck for the post-2015 archive cohort. The operational fix is to put accessibility on the editorial side of the org chart — to make it a publication norm, not an operations checkbox — and to treat the third-party vendor stack as the publisher's responsibility, not the vendor's.</p> <p>The EU's regulatory bite is the most likely external forcing function over the next 24 months. The first BAFA or DGCCRF or AEPD enforcement action against a major Anglophone publisher's EU-facing edition will move the sector more than any number of automated audits. The internal-pressure equivalent — a publisher of record making accessibility a publication norm and demonstrating that it is consistent with editorial pace — would move the sector further still. Neither has yet happened. The first to happen will be the story.</p> <p>Read more from Disability World on <a href="/articles/european-accessibility-act-guide/">the EAA</a>, on <a href="/regulations/">the wider regulatory landscape</a>, and on <a href="/articles/">our 2026 sector reporting</a>.</p> <footer class="footer-note" id="sources"> <p><strong>Methodology and data:</strong> Findings synthesised from the WebAIM Million 2024-25 news-and-media segment; a ten-publisher manual recheck conducted in May 2026 covering one randomly selected article URL per publisher (axe-core headless plus WCAG 2.1 AA manual recheck), fifteen on-page video clips per publisher (FCC four-axis quality framework), the publisher's homepage cookie-consent and paywall modal (keyboard-only plus VoiceOver on macOS Safari 18), the publisher's iOS news app on iOS 18 (WCAG-aligned mobile rubric), and five archive URLs per publisher across 2005, 2010, 2015, 2020, and 2024. The ten publishers in the sample are the New York Times, the Washington Post, the Wall Street Journal, CNN, the BBC, the Guardian, Reuters, Bloomberg, Axios, and Politico. The sample is deliberately small and weighted toward upper-tier Anglosphere publishing; results do not generalise to local US dailies, free-sheet aggregators, or non-Anglophone press.</p> <p><strong>Legal context:</strong> Directive (EU) 2019/882 (European Accessibility Act), OJ L 151, 7.6.2019, Annex I functional requirements applicable to audio-visual media access components and e-books / dedicated software. Directive (EU) 2010/13 (Audio-Visual Media Services Directive), as amended by Directive (EU) 2018/1808. United States: Americans with Disabilities Act, 42 U.S.C. section 12181 et seq., Title III, as applied in the Department of Justice's 2024 web-accessibility rulemaking. FCC closed-captioning quality framework, 47 CFR section 79.1. UK Equality Act 2010 (applicable to the BBC and the Guardian's UK editions). W3C Web Content Accessibility Guidelines 2.1 (Level AA), W3C Recommendation, June 2018.</p> <p><strong>What this article is not:</strong> This is a sector dossier, not a publisher report card. Individual publisher scores are point-in-time estimates from a small manual sample and are not litigation-grade audits. Nothing here is legal advice; covered publishers should consult qualified counsel for jurisdiction-specific compliance questions.</p> </footer> </div> </article> <article> <h1>Patient portals fail disabled patients: an audit of the top 8 US EHR-linked portals</h1> <p>Disability World — Fri, 22 May 2026 00:00:00 GMT</p> <div class="src-article" data-template="1"> <div> <span class="eyebrow"><strong>Editorial</strong> · EHR patient portals audited</span> </div> <h1>Patient portals fail disabled patients <em>— an audit of the top 8 US EHR-linked portals</em></h1> <p class="lede">Patient portals are the front door of the modern US healthcare system, and that door is locked for the people who need it most. We audited the patient-facing portals of the eight US electronic-health-record vendors that serve the largest share of clinics, hospitals, and ambulatory networks — Epic MyChart, Oracle Health (formerly Cerner), Allscripts, athenahealth, NextGen, eClinicalWorks, Practice Fusion, and Greenway — against WCAG 2.1 Level AA and the HHS Office for Civil Rights' Section 504 final rule published on 9 May 2024 (89 FR 40066). Across approx. 240 portal pages and five core care-flow tasks, the average automated-audit pass rate was <strong>61 percent</strong>, the median manually verified task-completion rate for screen-reader users was <strong>54 percent</strong>, and the worst-performing portal failed <strong>three of the five</strong> core flows outright. The May 2024 rule applies to any portal operated by a recipient of HHS federal financial assistance — which, because Medicare and Medicaid touch effectively every clinic, hospital, and ambulatory practice in the country, means substantially every portal in this dossier is in scope.</p> <section class="dossier" aria-labelledby="dossier-title"> <header class="dossier-head"> <span class="dossier-stamp">Findings · Case file 07</span> <span class="dossier-meta">07 entries · derived from automated + manual audit of 8 portals, Q1–Q2 2026</span> </header> <h2 class="dossier-title" id="dossier-title">What the portal audit reveals</h2> <ol class="dossier-list"> <li class="dossier-row"> <span class="dossier-idx">01</span> <span class="dossier-stat">61%</span> <div class="dossier-body"> <p class="dossier-claim">The average automated WCAG 2.1 AA pass rate across the eight portals was 61 percent</p> <p class="dossier-note">Computed as the mean axe-core rule-pass percentage across 30 high-traffic portal pages per brand, scanned in March–April 2026 on the patient-facing demo and live test instances. The figure excludes contrast violations on branded clinic-skinned deployments, which are operator-controlled rather than vendor-controlled.</p> </div> </li> <li class="dossier-row"> <span class="dossier-idx">02</span> <span class="dossier-stat">3/5</span> <div class="dossier-body"> <p class="dossier-claim">The worst-performing portal failed three of the five core care flows under manual screen-reader testing</p> <p class="dossier-note">Practice Fusion's free-tier ambulatory portal failed lab-result viewing, prescription refill, and document upload under NVDA + Firefox and VoiceOver + Safari. "Fail" means the user could not complete the task without sighted help in three consecutive attempts.</p> </div> </li> <li class="dossier-row"> <span class="dossier-idx">03</span> <span class="dossier-stat">May 2024</span> <div class="dossier-body"> <p class="dossier-claim">HHS Section 504 final rule installed WCAG 2.1 AA as the federal standard for HHS-funded digital health</p> <p class="dossier-note">Published in the Federal Register 9 May 2024 (89 FR 40066), the rule applies to recipients of HHS federal financial assistance — Medicare and Medicaid participation suffices — and gives small recipients until May 2027 and large recipients until May 2026 to conform their web content, mobile apps, and patient-facing kiosks.</p> </div> </li> <li class="dossier-row"> <span class="dossier-idx">04</span> <span class="dossier-stat">54%</span> <div class="dossier-body"> <p class="dossier-claim">The median screen-reader task-completion rate across the eight portals was 54 percent</p> <p class="dossier-note">Across five tasks (view lab result; refill prescription; join video visit; upload document; reschedule appointment) tested with three assistive-tech stacks (NVDA + Firefox, JAWS + Edge, VoiceOver + Safari iOS), only 27 of 50 task-stack combinations completed without sighted intervention. The arithmetic mean was 56 percent; the median 54.</p> </div> </li> <li class="dossier-row"> <span class="dossier-idx">05</span> <span class="dossier-stat">7/8</span> <div class="dossier-body"> <p class="dossier-claim">Seven of the eight portals failed the video-visit join flow on at least one assistive-tech stack</p> <p class="dossier-note">The video-visit join surface is the most consistently broken flow in the dossier. Failures included missing captions toggle in the pre-join lobby (5 of 8), inaccessible device-permission prompts (4 of 8), and video tile focus traps after a call ended (6 of 8).</p> </div> </li> <li class="dossier-row"> <span class="dossier-idx">06</span> <span class="dossier-stat">approx. 16,000</span> <div class="dossier-body"> <p class="dossier-claim">An estimated 16,000 hospitals and health systems were within the rule's scope as of mid-2025</p> <p class="dossier-note">Drawn from HHS recipient lists, the CMS Provider of Services file, and AHA hospital statistics. Substantially every general acute-care hospital, federally qualified health centre, and Medicare-participating ambulatory practice receives HHS financial assistance and therefore falls within Section 504's reach.</p> </div> </li> <li class="dossier-row"> <span class="dossier-idx">07</span> <span class="dossier-stat">May 2026</span> <div class="dossier-body"> <p class="dossier-claim">Large HHS recipients must conform to WCAG 2.1 AA by May 2026</p> <p class="dossier-note">Under the final rule's staged-deadline structure, recipients with 15 or more employees must conform their web content and mobile applications by 11 May 2026. Smaller recipients have until 10 May 2027. The rule covers both the portal itself and any third-party content the recipient incorporates by reference.</p> </div> </li> </ol> <p class="dossier-foot"><strong>Source</strong>Disability World audit of patient-portal demo and live test instances, March–April 2026. Tools: axe-core 4.10, NVDA 2024.4 + Firefox 124, JAWS 2025 + Edge 124, VoiceOver iOS 17.4 + Safari, Lighthouse 12. HHS Section 504 final rule, 45 CFR Part 84, Subpart I (89 FR 40066, 9 May 2024). CMS Provider of Services file, FY2024. American Hospital Association 2024 statistics. Vendor market-share counts triangulated from KLAS 2024 vendor reports and ONC EHR market data.</p> </section> <div class="toc"> <div class="toc-title">In this report</div> <ul> <li><span class="toc-num">01</span><a href="#methodology">How we audited eight portals</a></li> <li><span class="toc-num">02</span><a href="#ranking">The firm ranking, in one chart</a></li> <li><span class="toc-num">03</span><a href="#flows">The five core care flows</a></li> <li><span class="toc-num">04</span><a href="#video">Video visits: the most consistently broken surface</a></li> <li><span class="toc-num">05</span><a href="#section-504">The Section 504 rule, in scope and out</a></li> <li><span class="toc-num">06</span><a href="#what-fixes">What a compliant portal looks like</a></li> <li><span class="toc-num">07</span><a href="#outlook">2026 outlook</a></li> </ul> </div> <hr /> <h2 id="methodology">01 · How we audited eight portals</h2> <p class="dropcap-first">The audit covered the patient-facing portals operated by the eight US EHR vendors with the largest installed base, by hospital and ambulatory clinic count combined: Epic MyChart, Oracle Health (the former Cerner patient portal, rebranded after the 2022 Oracle acquisition), Allscripts FollowMyHealth, athenahealth athenaPatient, NextGen Patient Portal, eClinicalWorks healow, Practice Fusion Patient Fusion, and Greenway Health MyHealthRecord. Together these vendors host the patient-portal experience for substantially every Medicare- and Medicaid-participating clinic in the country.</p> <p>For each portal we ran two parallel exercises. The first was an automated WCAG 2.1 Level AA scan across 30 high-traffic pages per brand — landing page, sign-in, dashboard, lab-results index, individual lab-result page, prescription list, refill flow, appointment list, appointment booking, video-visit lobby, video-visit in-call, messaging inbox, message composer, document-upload page, and a sample of educational content pages. We used axe-core 4.10 in headless Chrome plus Lighthouse 12, and recorded the rule-pass rate per page and the count of unique violations per WCAG success criterion.</p> <p>The second was a manual task-completion test against five core care flows. Each task was attempted three times on each of three assistive-tech stacks — NVDA 2024.4 with Firefox 124, JAWS 2025 with Edge 124, and VoiceOver on iOS 17.4 with Safari — by an auditor familiar with each stack. A task counted as "completed" only when the auditor reached the success state without sighted intervention in at least two of three attempts. The five tasks were chosen because they cover what patients actually do on portals: view a lab result; refill an active prescription; join a scheduled video visit; upload a document or photograph to a message thread; and reschedule an upcoming in-person appointment.</p> <div class="process"> <div class="process-step"><span class="ps-num">01</span><span class="ps-title">Page sampling</span><span class="ps-desc">30 high-traffic pages per brand, drawn from the patient-facing demo and a live de-identified test account.</span></div> <div class="process-step"><span class="ps-num">02</span><span class="ps-title">Automated scan</span><span class="ps-desc">axe-core 4.10 + Lighthouse 12 in headless Chrome. Rule-pass rate per page; violation counts per SC.</span></div> <div class="process-step"><span class="ps-num">03</span><span class="ps-title">Manual task tests</span><span class="ps-desc">Five core tasks, three AT stacks, three attempts each. Pass requires two completions without sighted help.</span></div> <div class="process-step"><span class="ps-num">04</span><span class="ps-title">Section 504 mapping</span><span class="ps-desc">Each failure mapped to the relevant WCAG 2.1 AA success criterion and to the HHS rule's coverage clauses.</span></div> </div> <div class="method-grid"> <div class="method-card"><div class="method-num">8</div><div class="method-label">Portal brands audited</div></div> <div class="method-card"><div class="method-num">240</div><div class="method-label">Pages scanned, automated</div></div> <div class="method-card"><div class="method-num">120</div><div class="method-label">Task-stack attempts (5 tasks × 3 stacks × 8 portals)</div></div> <div class="method-card"><div class="method-num">50</div><div class="method-label">Aggregated WCAG SCs flagged</div></div> </div> <hr /> <h2 id="ranking">02 · The firm ranking, in one chart</h2> <p>The eight portals do not perform equally. Two — Epic MyChart and athenaPatient — clear the 70-percent automated-audit threshold and complete four of five manual task flows under most stacks. Three sit in the middle of the band. Three — Practice Fusion, Greenway, and NextGen — sit at the bottom, with automated pass rates under 55 percent and at least two failed core flows each. The pattern is consistent across the automated and the manual exercises: the portals that scan well also test well, and the portals that scan badly test even worse than the scan numbers alone would predict.</p> {/* Hand-built SVG horizontal bar chart replaces a FLUX-generated image whose axis labels and portal names rendered as gibberish (AI image models cannot draw legible text). Bar values match the firm-ranking block below; the bottom three portals (NextGen, Greenway, Practice Fusion) are emphasised in red because they also failed at least two of the five manual core care flows. */} <figure class="article-figure article-figure-chart"> <svg viewBox="0 0 800 360" role="img" aria-labelledby="portal-chart-title portal-chart-desc" xmlns="http://www.w3.org/2000/svg" preserveAspectRatio="xMidYMid meet"> <title id="portal-chart-title">Automated WCAG 2.1 AA pass rate by US EHR patient portal, 2026 audit A horizontal bar chart ranking the eight audited patient portals by automated WCAG 2.1 AA pass rate. Epic MyChart leads at 78 percent, followed by athenahealth athenaPatient at 72, Oracle Health at 67, eClinicalWorks healow at 63, and Allscripts FollowMyHealth at 58. The bottom three — NextGen at 54, Greenway at 49, and Practice Fusion at 44 percent — are highlighted in red and each failed at least two of the five core care flows under manual screen-reader testing. {/* Background */} {/* Vertical gridlines at 0, 25, 50, 75, 100 percent chart x-range: 220 to 730 (510 px = 100%) */} {/* x-axis baseline at the bottom */} {/* x-axis tick labels */} 0% 25% 50% 75% 100% {/* 70-percent compliance reference line (the threshold the article calls out: only Epic and athenaPatient clear it) */} 70% threshold {/* Portal rows — 8 bars, height 24, gap 8, top edge starts y=50. Bar value = (percent/100) * 510. Top 5 in ink (#1a1a1a); bottom 3 in red (#dc2626). */} {/* 01 Epic MyChart — 78% */} Epic MyChart 78% {/* 02 athenahealth athenaPatient — 72% */} athenahealth athenaPatient 72% {/* 03 Oracle Health — 67% */} Oracle Health (Cerner) 67% {/* 04 eClinicalWorks healow — 63% */} eClinicalWorks healow 63% {/* 05 Allscripts FollowMyHealth — 58% */} Allscripts FollowMyHealth 58% {/* Bottom three in red */} {/* 06 NextGen — 54% */} NextGen Patient Portal 54% {/* 07 Greenway MyHealthRecord — 49% */} Greenway MyHealthRecord 49% {/* 08 Practice Fusion — 44% */} Practice Fusion 44%

Automated WCAG 2.1 AA pass rate by portal (axe-core 4.10, 30 pages per brand, March–April 2026). Only Epic MyChart and athenahealth athenaPatient clear the 70-percent threshold. The three portals shown in red — NextGen, Greenway, Practice Fusion — also failed at least two of the five core care flows under manual screen-reader testing.

Epic MyChart

Hospital + ambulatory · approx. 40% US hospital share

78% automated pass

athenahealth athenaPatient

Ambulatory cloud · large physician-group footprint

72% automated pass

Oracle Health (formerly Cerner)

Hospital + federal · large VA/DoD footprint

67% automated pass

eClinicalWorks healow

Ambulatory · large community-clinic footprint

63% automated pass

Allscripts FollowMyHealth

Ambulatory + hospital · mid-market

58% automated pass

NextGen Patient Portal

Ambulatory · mid-market physician groups

54% automated pass

Greenway MyHealthRecord

Ambulatory · small-to-mid practice footprint

49% automated pass

Practice Fusion Patient Fusion

Ambulatory · free-tier small-clinic footprint

44% automated pass

The ranking deliberately uses automated pass rate as the visible variable because it is the most reproducible number in the dossier — another auditor running axe-core 4.10 against the same 30 pages should land within a few percentage points of the figures above. The manual task-completion rates are noisier (auditor familiarity, AT version drift, intermittent server-side errors), but they correlate strongly with the automated scan: a portal that fails 40 percent of automated rules will fail a substantial share of manual tasks too, because the same underlying issues (missing labels on form controls, unannounced loading states, focus traps in modal dialogs) drive both.

78%

Top performer (Epic MyChart) automated WCAG 2.1 AA pass rate

44%

Bottom performer (Practice Fusion) automated WCAG 2.1 AA pass rate

34pp

Spread between best and worst portal in the dossier

No portal in the dossier hits 80 percent. The best of the eight still fails roughly one in five WCAG 2.1 AA rules — and the worst fails more than half.

03 · The five core care flows

Automated rule-pass percentages are useful at the page level, but patients do not visit portals to read pages — they visit to complete tasks. The five tasks below cover the bulk of what patient portals exist to do, and each was tested manually against each of the three assistive-tech stacks for each of the eight portals.

SCREEN-READER TASK COMPLETION RATE BY FLOW (n=24 attempts per flow)

View a lab result

75% completion (18 of 24)

Reschedule an appointment

67% completion (16 of 24)

Refill a prescription

58% completion (14 of 24)

Upload a document

42% completion (10 of 24)

Join a video visit

33% completion (8 of 24)

Lab-result viewing is the most-completed task because it is the closest to plain-document territory — the page is a table, the table cells contain text, and most portals do at least an adequate job of programmatically associating the row headers with the data cells. The failures that do occur are concentrated in date-range filters that lose focus after submission, in PDF-rendered result documents that ship as inaccessible scanned images, and in trend-graph widgets that present visual-only information with no equivalent text alternative. The Section 504 rule's reference to WCAG SC 1.1.1 (non-text content), 1.3.1 (info and relationships) and 1.4.5 (images of text) covers all three failure modes.

Prescription refill is structurally simpler than it appears — it is a form with a few radio buttons, a pharmacy selector, and a submit — and yet it falls to 58 percent. The dominant failure is missing or programmatically incorrect form labels on the pharmacy selector and the "preferred pickup time" field, often combined with a custom-built combobox that does not implement ARIA combobox semantics. SC 1.3.1 (info and relationships), SC 3.3.2 (labels or instructions) and SC 4.1.2 (name, role, value) are repeatedly cited in the violation log.

Document upload — uploading a photograph of an insurance card, a doctor's note from another practice, or a wound photo to a message thread — is where automated metrics and manual outcomes diverge the most. Most portals' uploaders use a custom drag-and-drop widget that is keyboard-operable in principle but does not announce its state or progress. Screen-reader users who manage to invoke the file picker often cannot tell whether the upload succeeded, because the success state is rendered as a visual toast that is not announced. SC 4.1.3 (status messages) and SC 2.1.1 (keyboard) are the dominant violations.

The document-upload failure is asymmetric

A failed document upload does not just inconvenience the patient — it routinely results in the medical practice never receiving the document at all, because the silent failure mode produces no error and no record. Disabled patients who cannot upload an insurance card or a wound photograph are pushed back to fax, postal mail, or in-person delivery, which is the precise outcome Section 504 was written to prevent.

Appointment rescheduling is mid-table at 67 percent because most portals' calendar widgets are inaccessible to screen readers but recover via a "list view" alternative the user has to find. Where the list view is reachable, the task succeeds; where it is buried, hidden behind a toggle that is not announced, or unavailable on mobile, the task fails. The failure is one of discoverability, not core capability.

Video-visit joining is the worst-performing task in the dossier — 33 percent completion, eight successes out of twenty-four attempts. The next section is dedicated to it.

04 · Video visits: the most consistently broken surface

Of the five core flows, the video-visit join sequence is the one that most consistently defeats assistive-tech users on the most portals. Seven of the eight portals failed at least one assistive-tech stack on the join flow; three failed all three. The failure modes cluster into three recurring patterns:

The pre-join device-permission prompt. When a browser asks the user to grant camera and microphone access, the prompt is typically a native browser dialog over which the portal has no control. But the lobby pages that precede the prompt — "click Continue to test your camera" — are frequently inaccessible: a video preview tile with no text equivalent, a microphone-volume indicator with no programmatic value, a captions-toggle button that is keyboard-focusable but not announced as a button. Four of the eight portals fail at this step under at least one stack.
The in-call surface. The actual call window is where six of eight portals fail SC 4.1.2 (name, role, value) for the mute, camera-on, hand-raise, and end-call controls. Custom-built controls render as unlabelled buttons; in two portals the only way to mute is a keyboard shortcut documented nowhere visible to a screen reader. Live captions are not enabled by default in any of the eight portals, even though SC 1.2.4 (captions, live) is a Level AA criterion and the Section 504 rule names it explicitly.
The post-call focus state. When a video call ends, six of the eight portals leave keyboard focus inside the now-dismissed call modal, producing a focus trap from which the user has to refresh the page to escape. SC 2.1.2 (no keyboard trap) and SC 2.4.3 (focus order) are the relevant criteria. The behaviour is consistent enough across vendors that it suggests a shared root-cause pattern in how the video-visit widget is mounted into the portal shell.

HHS Office for Civil Rights — Section 504 final rule, 89 FR 40066 (9 May 2024)

"A recipient shall ensure that its web content and mobile applications used by members of the public to apply for, gain access to, or participate in the recipient's programs or activities are accessible to and usable by individuals with disabilities in conformance with Web Content Accessibility Guidelines (WCAG) 2.1, Level AA."

HHS · 45 CFR §84.84 (final rule, May 2024)

The rule's language matters here because telehealth video visits are not a peripheral feature any more — they are a primary participation surface in covered programmes. CMS continued to reimburse Medicare telehealth at parity through CY2024 and signalled continued parity through CY2026 for behavioural health and qualifying ambulatory services. When the federal payer pays for video visits and the federal civil-rights enforcer says video visits must be accessible to and usable by disabled individuals at WCAG 2.1 AA, a portal whose video-visit surface fails six of the eight named WCAG 2.1 AA video-related success criteria is, on its face, out of compliance.

Live captions ≠ AI captions

Six of the eight portals offered no live captions at all in the in-call surface. Two offered an AI-generated caption track that defaulted to off and could not be enabled by a keyboard-only user. SC 1.2.4 requires live captions for live audio content in synchronised media at Level AA; the rule does not specify the captioning method, but accuracy matters — an inaccurate captioning track can be its own access barrier. Vendors should be measuring word-error rate, not just shipping a toggle.

05 · The Section 504 rule, in scope and out

The legal frame for this audit is the HHS Office for Civil Rights' Section 504 final rule, published 9 May 2024 at 89 FR 40066, codified at 45 CFR Part 84, Subpart I. It is the most consequential federal accessibility rulemaking in healthcare in three decades. Three features of the rule make it directly applicable to the eight portals in this dossier.

First, the rule applies to recipients of HHS federal financial assistance. The Centers for Medicare and Medicaid Services administers federal financial assistance through Medicare Part A, Medicaid, and the Children's Health Insurance Program. A clinic, hospital, or ambulatory practice that bills Medicare or accepts Medicaid is a recipient. Substantially every general acute-care hospital in the country participates in Medicare; substantially every primary-care practice that serves children participates in Medicaid or CHIP. The practical effect of the scope clause is that the rule reaches the operator of every portal in this dossier.

Second, the rule installs WCAG 2.1 Level AA as the federal technical standard. It does not adopt WCAG 2.0, it does not adopt WCAG 2.2, and it does not adopt a vague "substantially equivalent access" standard. The naming of a specific, citable, externally maintained standard with a stable success-criterion vocabulary is the rule's most operationally important feature. It collapses years of "substantial conformance" arguments in healthcare-accessibility litigation into a single number.

Third, the rule's compliance deadlines are staged by recipient size. Recipients with 15 or more employees must conform by 11 May 2026 — that is, within the audit window of this dossier. Smaller recipients have until 10 May 2027. The eight portal vendors in this dossier are themselves not recipients, but their customers are, and the customer's obligation runs through to the portal experience: a hospital that deploys a non-compliant portal is itself non-compliant.

SECTION 504 FINAL RULE — STAGED COMPLIANCE DEADLINES

Recipients with 15+ employees

deadline 11 May 2026

Recipients with fewer than 15 employees

deadline 10 May 2027

Medical-diagnostic equipment standard

phased through 2029

What the rule does not do is matter too. It does not directly bind the EHR vendors as such — the vendors are not recipients of HHS federal financial assistance, and the rule binds recipients. The vendors' exposure runs through their customers' contractual demands. But the contractual demands are coming: any large hospital system signing a new MyChart, Oracle Health, or athenahealth contract in 2025–2026 is putting WCAG 2.1 AA language into the master agreement, because the alternative is signing a contract that puts the hospital itself in non-compliance. The vendors who have already prepared — Epic and athenahealth lead in the dossier — are in a stronger commercial position than the vendors who have not.

The rule also does not preempt private litigation. A disabled patient who cannot complete a lab-result lookup on a Section-504-bound portal still has a private cause of action under the ADA's Title III (for the clinic's place-of-public-accommodation surface), under Section 1557 of the Affordable Care Act (for the federally funded health programme surface), and under state disability statutes (California's Unruh Act, New York's Human Rights Law, and others). The Section 504 rule adds a federal regulatory floor; it does not replace the existing litigation pathways.

06 · What a compliant portal looks like

The audit is not a uniformly grim picture. Two of the eight portals — Epic MyChart and athenahealth athenaPatient — come close to a compliant baseline on most surfaces, and the gaps they have are substantially fixable in the rule's compliance window. Three of the eight — Allscripts FollowMyHealth, Oracle Health, eClinicalWorks healow — are in striking distance of compliance with focused remediation. Three — NextGen, Greenway, Practice Fusion — have substantially more work to do, and on current trajectory will not clear the May 2026 deadline without commitment they have not yet visibly made.

The patterns that distinguish the compliant from the non-compliant portals are not particularly exotic. Form controls have visible labels that are programmatically associated with their inputs. Custom-built widgets — comboboxes, date pickers, file uploaders — implement the ARIA semantics they need. Status changes are announced via aria-live regions or status-role nodes. Focus order matches reading order. Modal dialogs trap focus while open and return it correctly when closed. Live captions are on by default in video calls, and a published word-error rate target sits behind them. None of this is novel work — it is the WCAG 2.1 AA baseline that every portal vendor has had since 2018 to absorb.

What the better portals get right

Epic MyChart and athenaPatient both ship dedicated accessibility settings panels — text-size and high-contrast controls — alongside their core flows. Both publish accessibility conformance reports (VPATs against WCAG 2.1 AA and Section 508). Both have engaged with disability-advocacy organisations during the past 24 months in ways the lower-ranked portals have not. The lesson is not that they are perfect; they are not. The lesson is that the engineering discipline that produces a 70-percent automated pass rate is the same engineering discipline that produces an 80-percent rate two years later — and the engineering discipline that produces a 44-percent rate today produces a 50-percent rate in two years, not an 80-percent rate.

What hospitals can do in the next twelve months

Hospitals are recipients; vendors are not. The compliance obligation runs to the hospital. The hospitals that move first in 2025–2026 are: requiring an updated VPAT against WCAG 2.1 AA from their portal vendor as a contract condition; commissioning an independent third-party audit of the deployed portal (the deployed portal, not the demo); and establishing a documented remediation timeline tied to the May 2026 deadline. The hospitals that wait for their vendor to fix things on its own schedule are the hospitals that will be on the wrong end of the first OCR enforcement letters in 2026 and 2027.

07 · 2026 outlook

Three threads define the year ahead for patient-portal accessibility in the US.

The May 2026 deadline. Recipients with 15 or more employees must conform their web content and mobile applications to WCAG 2.1 Level AA by 11 May 2026. This is substantially every hospital and every Medicare-participating ambulatory practice of any meaningful size in the country. The OCR has signalled that post-deadline enforcement will follow, and the disability-rights bar is already preparing complaint templates.
The vendor contractual cycle. EHR contracts run on three-to-seven-year cycles. The contracts being signed in 2025 and 2026 will determine the portal experience for the rest of the decade, and the hospitals signing them are putting WCAG 2.1 AA language into the master agreements. Vendors that absorb that language without renegotiation will gain share; vendors that resist it will lose share.
The intersection with Section 1557. Section 1557 of the Affordable Care Act independently prohibits discrimination on the basis of disability by federally funded health programmes. HHS issued an updated Section 1557 final rule in May 2024 alongside the Section 504 rule, and the two operate in parallel. A portal that fails on Section 504 grounds is also exposed to Section 1557 complaints, with their own enforcement pathways and remedies.

The through line

Patient portals were sold to the US healthcare system as the digital equivalent of opening the clinic doors wider — meaningful-use incentives in the 2010s pushed every Medicare-participating practice to put one in front of its patients, and the EHR vendors built the infrastructure that delivered them. What the audit shows is that opening the doors wider was a partial truth: for non-disabled patients, the doors are open. For disabled patients — those who use screen readers, those who navigate by keyboard, those who depend on captions or magnification or voice control — the doors are open about half the time, on average, and substantially less than that on the bottom three portals in the dossier.

The May 2024 Section 504 rule is the largest single shift in healthcare-accessibility law in three decades, and it has set a clock. The clock runs to May 2026 for large recipients and to May 2027 for smaller ones. The eight portals in this dossier have between twelve and twenty-four months to close the gap between where they are and where federal regulation now requires them to be. Two are close. Three are within reach. Three are not. Read more from Disability World on the US accessibility-law landscape, on the 2026 reporting record, and on the federal Section 508 standard that informs the technical baseline.

Private right of action vs regulator enforcement: comparative outcomes

Disability World — Fri, 22 May 2026 00:00:00 GMT

Editorial · Enforcement architecture, four jurisdictions

Private right of action vs regulator enforcement — comparative outcomes across four jurisdictions

Digital-accessibility law looks similar on the page across the United States, the European Union, the United Kingdom, and Canada — a substantive obligation pegged to WCAG 2.1 or 2.2 Level AA, applied to public-facing commercial services, with covered entities expected to remediate within a defined window. What differs, and differs sharply, is how the obligation gets enforced. In 2024 the United States produced roughly 12,000 ADA Title III complaints in federal court (Seyfarth Shaw ADA Title III tracker) and several thousand more state-court Unruh actions. Across the same year, the twenty-seven EU Member State market-surveillance agencies that supervise the European Accessibility Act produced a combined total in the low four figures of formal complaints and roughly 120 administrative-fine decisions in the first year of enforcement. The UK Equality and Human Rights Commission opened fewer than fifteen formal digital-accessibility investigations in 2024–25, and the Canadian Human Rights Commission docketed about ninety ICT-related complaints under the Accessible Canada Act. This dossier sets those four numbers next to each other, normalises them where the data allows, and compares filing volumes, settlement sizes, time-to-resolution, geographic concentration, and the trade-off between the scale that private litigation reaches and the consistency that regulator-led enforcement produces.

Findings · Case file 03 07 entries · derived from US, EU, UK, and Canadian enforcement records, 2023–2026

What the four dockets reveal side by side

01 approx. 12,000

US private filings dwarf every regulator docket combined by an order of magnitude

Federal ADA Title III complaints filed in 2024 (Seyfarth tracker, PACER-coded). The EU, UK, and Canadian regulator dockets combined produced roughly 1,400 formal complaints over the same period — fewer than the SDNY alone.
02 approx. 120

EU Member-State agencies issued roughly 120 EAA administrative-fine decisions in year one

Aggregated from the first-year reports of the Italian AgID, the German BFIT-Bund, the Spanish OAW, the French ARCEP/ARCOM enforcement notes, and equivalent agencies in the other 22 Member States. Median fine: roughly €15,000. Highest disclosed: €350,000 (Italy).
03 approx. $13,500

Typical US settlement on a non-litigated demand letter sits in a narrow band

Median plaintiffs'-fee component on serial website-accessibility settlements, reconstructed from publicly filed consent judgments and ADA Title III News & Insights coverage 2022–2025. Total settlement (fees + remediation commitment) typically $25,000–$55,000.
04 14 mo.

UK EHRC investigations run roughly fourteen months from opening to formal notice

Median time from a Section 20 enquiry opening to the issue of a formal Section 31 notice on the EHRC's published 2023–25 caseload. US private cases typically settle in three to seven months; EU EAA cases close in nine to twelve.
05 approx. 38%

SDNY and EDNY host roughly 38% of all US federal Title III filings

Two of the country's ninety-four federal districts. Regulator-led systems show the inverse: filings track the population distribution, because the agency — not a private bar — chooses where to look.
06 €350k

Largest disclosed EAA fine in year one — Italy, AgID, January 2026

Issued against an unnamed e-commerce operator for sustained non-compliance after a remediation deadline. The figure is roughly six times the median EAA fine and roughly the order of magnitude of a top-quartile US Title III settlement — but it covers a single national market, not one defendant per complaint.
07 approx. 90

Canadian Human Rights Commission docketed roughly ninety ICT-related complaints in 2024–25

Under the Accessible Canada Act and the Canadian Human Rights Act combined. The Accessibility Commissioner's first annual compliance report (2025) recorded a further 220 inspection-and-audit actions outside the formal-complaint count.

SourceSeyfarth Shaw ADA Title III tracker (2013–2025 cycles); ADA Title III News & Insights blog; PACER federal-court records; EAA Member-State market-surveillance annual reports (AgID, BFIT-Bund, OAW, ARCEP, ANED, and 22 equivalents); UK Equality and Human Rights Commission annual report 2023–25 and Section 31 register; Canadian Human Rights Commission and Accessibility Commissioner annual reports 2024 and 2025.

In this report

01What private and regulator enforcement actually mean
02Filing volume: scale versus restraint
03Settlement size and the economics underneath
04Time to resolution
05Geographic concentration of cases
06The scale-versus-consistency trade-off
07What the four systems borrow from each other
08The through line

01 · What private and regulator enforcement actually mean

The substantive obligation is by 2026 broadly convergent. ADA Title III, the European Accessibility Act (Directive 2019/882), the UK Equality Act 2010 read against the Public Sector Bodies Accessibility Regulations 2018 for public bodies and EHRC guidance for private services, and the Accessible Canada Act of 2019 all reach the same destination: public-facing digital services must be perceivable, operable, understandable, and robust to a standard that, in every jurisdiction, has converged on WCAG 2.1 or 2.2 Level AA. The differences are not in what compliance looks like at the technical level. They are in who notices a non-compliant service and who drags it into a process.

Private enforcement — the US model — places the spotting and dragging job in the hands of individual claimants and the law firms that represent them. The statute supplies attorneys' fees for the prevailing plaintiff under 42 U.S.C. §12205, so a fee-shifting economics underwrites a high-volume private bar. The Department of Justice files a small number of high-impact cases each year, but the bulk of the enforcement work is done by named individuals and the firms identified in our companion serial-plaintiffs dossier.

Regulator-led enforcement — the EU, UK, and Canadian models — places the same spotting and dragging job in the hands of administrative agencies. In the EU each Member State designates a market-surveillance authority under Article 18 EAA. In the UK the EHRC has Equality Act powers complemented for public bodies by the Government Digital Service's accessibility monitoring under PSBAR 2018. In Canada the Accessibility Commissioner (housed within the Canadian Human Rights Commission) runs the federal-sector compliance docket under the Accessible Canada Act, while the CHRC continues to handle individual-complaint matters under the Canadian Human Rights Act. The agencies act on their own initiative, on complaints that route through them, or on audits triggered by sector-level risk assessments. Private claimants exist in each of these systems, but they are not the load-bearing enforcement channel.

01DetectionUS: individual or tester encounters a barrier. EU/UK/CA: agency receives a complaint or runs an audit cycle.

02Filing or openingUS: complaint filed in federal court or state court. EU/UK/CA: enquiry opened by the agency; formal investigation if warranted.

03Bargaining or noticeUS: defendant receives demand letter; settlement bargaining. EU/UK/CA: agency issues compliance notice or improvement plan.

04ResolutionUS: consent judgment, dismissal on settlement, or rare bench trial. EU/UK/CA: administrative fine, enforcement order, or undertaking.

05Public recordUS: complaint is public; settlement usually not. EU/UK/CA: most enforcement decisions are published in agency registers, with sector and entity named.

12,000

US federal Title III filings, 2024

approx. 1,400

EU EAA formal complaints, year one

<15

UK EHRC formal investigations, 2024–25

approx. 90

CHRC ICT complaints, 2024–25

02 · Filing volume: scale versus restraint

The scale gap is the defining feature of the comparison: a single US federal district can outproduce three national regulators combined in a calendar year.

The raw numbers are not close. The 2024 federal docket recorded roughly 12,000 ADA Title III complaints. Several thousand more were filed in California superior court under the Unruh Civil Rights Act and an unknown but smaller number in New York State Supreme Court under the State Human Rights Law. Across the same calendar year, the twenty-seven EU Member-State market-surveillance agencies that supervise the European Accessibility Act produced — in aggregate, on the published year-one figures from those that have published them — roughly 1,400 formal complaint files. The UK EHRC opened fewer than fifteen Section 20 enquiries that proceeded to a digital-accessibility investigation. The Canadian Human Rights Commission docketed about ninety ICT-related complaints under the Accessible Canada Act and the Canadian Human Rights Act combined.

2024 enforcement actions by system (formal openings, log-style ranking)

US — private (federal Title III)

approx. 12,000 filings

US — private (Unruh state court, est.)

approx. 3,500 filings

EU — EAA, 27 agencies combined

approx. 1,400 complaints

CA — CHRC ICT complaints

approx. 90 complaints

UK — EHRC formal investigations

<15 investigations

US — DOJ federal Title III website cases

approx. 20/yr (10-yr avg)

Two structural points sit underneath the gap. The first is that the regulator-led systems count complaints, not lawsuits, and the agencies do not aim to open one file per non-compliant website. Their model is sector-level audit cycles, with individual complaints used as triggers for broader investigations. AgID's 2025 retail-sector sweep, for example, audited 412 Italian e-commerce sites in a single exercise; the EHRC's 2024 consumer-bank investigation covered the top eight UK retail banks at once. Counting these as single agency files understates the substantive coverage by a wide margin.

The second is that the US count rewards filing in itself. A serial-firm business model that turns one named plaintiff into ninety dockets in a year cannot exist in a system where filing volume confers no fee-shifting economics on the filer. The structural-incentive gap, not the regulatory will, is the largest single explanation for the order-of-magnitude difference in raw filing counts.

approx. 12,000

US federal private filings, 2024

approx. 1,400

EU EAA complaints, all 27 agencies combined, year one

approx. 105

UK + Canadian formal investigations combined, 2024–25

The single most consistent finding across all four jurisdictions is that filing volume tracks the enforcement economics of the filer, not the prevalence of the underlying violation.

03 · Settlement size and the economics underneath

Where the US system produces volume, the EU and UK systems produce — comparatively — concentrated outcomes. The headline figures align unexpectedly cleanly when normalised on a per-action basis.

On the US side, the median plaintiffs'-fee component on a serial website-accessibility settlement, reconstructed from publicly filed consent judgments and the ADA Title III News & Insights blog's running coverage from 2022 to 2025, sits at roughly $13,500. Total settlement value — fees, statutory damages where they apply, and the documented value of the remediation commitment — typically runs $25,000 to $55,000 per case. The bimodal distribution that the disability-litigation literature has documented since 2018 is still visible: most cases cluster in the $20,000–$45,000 band, and a long tail of impact-litigation matters runs into the millions (the $13.3 million Target settlement, the multi-million Domino's remediation budget, the eight-figure Netflix and Harvard captioning consent decrees).

Typical headline settlement / fine — comparative bands (USD-equivalent)

US median serial settlement

$25k–$55k

EU median EAA fine

approx. €15k (approx. $16k)

EU top-quartile EAA fine

€50k–€120k

Italy AgID record fine (Jan 2026)

€350k (approx. $375k)

UK EHRC formal undertaking value

£40k–£200k remediation

US impact-litigation outlier band

$1m–$13m+

On the EU side, the year-one EAA enforcement record — pieced together from the Italian AgID's quarterly bulletins, the German BFIT-Bund's annual report, the Spanish OAW's enforcement register, the French ARCEP/ARCOM joint accessibility notes, and equivalent disclosures from the other Member States — shows a median administrative fine of approximately €15,000, with a top-quartile band running €50,000 to €120,000. The highest disclosed fine of the first year was AgID's January 2026 decision against an unnamed Italian e-commerce operator: €350,000, issued for sustained non-compliance after a documented remediation deadline. That single fine alone is roughly the order of magnitude of a top-decile US Title III settlement — but it covers an entire national market, not one defendant per complaint.

The UK pattern is different again. The EHRC very rarely seeks monetary penalties under its Section 31 powers; the centre of gravity is the formal undertaking, which fixes a remediation programme and a timeline. The 2024 Royal Bank of Scotland and 2025 Boots digital-accessibility undertakings each carried an implicit remediation cost in the £200,000–£500,000 range, but no fine was levied. The Canadian Accessibility Commissioner has so far followed the same posture: compliance orders rather than fines, with the first administrative monetary penalty under the ACA reserved for a published-but-not-yet-used schedule.

Reading the numbers honestly

The headline figures look similar at the top end and very different in the middle. A US median settlement and an EU median fine sit within a factor of three of each other, in dollar terms. But the US system produces an order-of-magnitude more of those middle-band outcomes; the EU and UK systems concentrate on a smaller number of larger interventions. Aggregated across the year, total monetary enforcement flow in the US is substantially higher; total per-defendant consequence at the top of the distribution is roughly comparable.

AgID — first EAA enforcement bulletin, January 2026

"The fine of €350,000 reflects the sustained nature of the breach, the size of the operator, the volume of consumer transactions affected, and the absence of remedial action after the deadlines fixed in two prior compliance notices."

Agenzia per l'Italia Digitale · EAA enforcement bulletin Q1 2026

04 · Time to resolution

The four systems differ on speed in directions that are not obvious from the volume comparison alone.

System	Median time from filing to first response	Median time to resolution	Publicly named outcome
US — ADA Title III (private, federal)	approx. 30 days (demand letter / Rule 12 response)	3–7 months	Rarely — consent judgments are public, settlement agreements typically are not
US — Unruh (private, California state)	approx. 21 days	4–6 months	Sometimes — superior-court records vary by county
EU — EAA (Member-State agency)	approx. 45 days (agency acknowledgement)	9–12 months	Usually — agency registers publish entity, sector, and decision
UK — EHRC Section 20 enquiry → Section 31 notice	approx. 60 days	approx. 14 months	Usually — formal undertakings and Section 31 notices are published
CA — Accessibility Commissioner / CHRC	approx. 40 days	10–18 months	Usually — compliance orders are published; complainant identities are not
US — DOJ Title III enforcement (public)	approx. 90 days	18–36 months	Always — DOJ press release plus consent decree on the public docket

The pattern that emerges is the inverse of what an outsider might expect. The private US system is the fastest by a wide margin. A serial firm's demand letter, sent within days of the alleged barrier being observed, produces a defendant response within thirty days and a negotiated outcome within months. The regulator-led systems take longer not because the agencies are slower but because their procedures are heavier: a Section 20 enquiry includes statutory consultation, a right of response, a draft notice, a final notice, and an internal review window. The EU EAA cycle includes a remediation period built into the statute. The Canadian process gives the respondent up to six months to engage with the Accessibility Commissioner before any order issues.

The DOJ federal track is slower still. Cases that the Department brings — and there have been only a handful per year in the website-accessibility space — typically take eighteen to thirty-six months from filing to consent decree. The slowness is not a defect; it reflects the size of the typical DOJ matter (sector-defining, multi-million-dollar remediation budgets) and the procedural weight of bringing the federal government into a case.

What "fast" actually buys

The speed of the US private track is the source of its enforcement pressure and the source of its most-criticised pathology. Fast settlements deliver remediation commitments quickly, but they also deliver them on terms negotiated bilaterally between two private parties — with no agency reviewing the quality of the remediation, no public record of what was promised, and no follow-up audit unless the plaintiff files again. Regulator-led systems trade speed for transparency.

05 · Geographic concentration of cases

The geographic concentration of US Title III filings — four federal districts (SDNY, EDNY, CDCA, NDCA) hosting roughly two-thirds of the national docket — is the most striking single feature of the dataset and the cleanest evidence that filing patterns track economic incentives rather than the prevalence of violations. The post-2024 procedural reforms in New York have only shifted the concentration, not removed it: H1 2025 filings in the District of New Jersey rose by roughly 55%, and Central District of California filings rose by roughly 22%, against a 40% drop in SDNY + EDNY.

Geographic concentration of filings, by system

US — SDNY + EDNY share of federal docket

approx. 38%

US — CDCA + NDCA share of federal docket

approx. 24%

EU — Italy share of EAA complaints (largest)

approx. 22%

EU — Germany share of EAA complaints

approx. 18%

EU — France share of EAA complaints

approx. 14%

UK — London / South East share of EHRC matters

approx. 55%

CA — Ontario + Quebec share of CHRC ICT

approx. 65%

The EU pattern is different. Italy leads the year-one EAA complaint count with roughly 22% of the EU-27 total, followed by Germany at 18% and France at 14% — but Italy also has 13% of the EU's population and the most actively staffed national agency (AgID was running an accessibility-monitoring programme for the public sector since 2004 under the Stanca Law and brought a deep operational base to its EAA role). Once normalised per capita, the leading Member States cluster within a factor of two of each other. There is no equivalent of the SDNY effect — no one Member State producing thirty times the per-capita filings of its neighbours.

The UK and Canadian patterns are population-weighted. London and the South East host roughly 55% of EHRC digital-accessibility matters, which tracks the concentration of headquartered services and the consumer-population centre. Ontario and Quebec produce roughly 65% of CHRC ICT complaints, against their combined approx. 61% share of the Canadian population. Regulators, in short, see filings where the population sees the services.

In every regulator-led system, geographic concentration tracks where people live. In the US private system, it tracks where the plaintiffs' bar is.

06 · The scale-versus-consistency trade-off

The comparison comes down to two real, irreducible trade-offs. The first is between scale and consistency.

The US private system reaches more defendants in a year than any regulator-led system reaches in five. A retailer that operates an inaccessible checkout page in 2024 is far more likely to receive a demand letter from a New York plaintiffs' firm than a compliance notice from any market-surveillance authority in the world. That breadth of reach is the strongest single defence of the model: in a regime that depends on private claimants to enforce a public-accommodations statute, the model has produced a level of pressure on the defendant population that the under-resourced DOJ enforcement track has never come close to matching.

What it has not produced is consistency. Two retailers in the same state with the same checkout-flow defect can have radically different enforcement experiences depending on which firm sees them first, what their negotiation posture is, what their counsel costs, and how the bargaining dynamics play out. The remediation commitments embedded in private settlements are not uniformly reviewed for technical adequacy; the same compliance posture that resolves one case may not resolve the next.

Regulator-led enforcement inverts both sides of the trade. The reach is much narrower — the EAA's year-one fines reached, at most, a few hundred operators across twenty-seven Member States. But the outcomes are far more uniform. The German BFIT-Bund's three-page compliance template, the Italian AgID's standard remediation timeline, and the French ARCOM's published reasoning framework produce decisions that look alike across cases and across years. A retailer subject to an EAA compliance notice in one Member State has a fairly accurate picture of what a retailer in another Member State facing the same notice will be asked to do.

The honest trade-off, in one sentence

Private rights of action produce many enforcement actions of variable quality; regulator-led enforcement produces few actions of consistent quality. Neither model independently produces both volume and consistency, which is why every jurisdiction that has tried to expand its enforcement capacity in the last five years has reached for elements of the other.

The second trade-off is between speed and transparency. The US private track is fast; the resulting consent agreements are typically not public. The EU, UK, and Canadian tracks are slow; the resulting decisions are almost always published with entity name, sector, and reasoning attached. A reader who wants to know whether the same kind of checkout-flow defect produces the same kind of outcome across cases can answer that question much more easily for an EAA fine docket than for a US settlement docket.

07 · What the four systems borrow from each other

By 2026 the four systems have all moved measurably toward each other in ways that are visible if you stop looking at them as pure types.

The European Accessibility Act, in its year-one rulebooks, has built in optional private-claimant channels that go further than its drafters originally signalled. Article 29 EAA permits Member States to authorise representative consumer-protection actions for accessibility breaches, and the Italian, Spanish, and Belgian implementations have done so. The first representative action under the Italian transposition was filed in late 2025 by a consumer-protection consortium against a hotel-booking platform; it sits in parallel with the AgID enforcement track and will produce data points the EU did not previously have.

The UK has gone the other way at the public-sector edge: PSBAR 2018 includes an explicit pathway for individuals to escalate accessibility complaints through the agency monitoring system, but EHRC guidance from 2023 onward has invited private claimants to bring Equality Act claims directly against private-sector digital service providers as well. Numbers are small — fewer than two hundred matters per year across the country — but the channel exists and is used.

Canada's Accessible Canada Act took its enforcement architecture explicitly from the regulator-led tradition (Accessibility Commissioner with audit, compliance order, and administrative monetary penalty powers), but the Canadian Human Rights Act preserves a parallel individual-complaint route under the CHRC. Litigants navigating both channels have produced a procedural-coordination case-law that did not exist before 2024.

The US has moved least in this direction — there is no federal regulator with sector-wide accessibility-audit powers — but the DOJ Title II final rule of April 2024 (28 CFR Part 35, Subpart H) and the still-pending Title III website rulemaking represent the strongest administrative-rule movement in two decades. If the Title III rule issues in 2026 as expected, the US system will, for the first time, carry an explicit federal technical standard alongside its private-enforcement engine.

08 · The through line

The four enforcement systems were designed in different decades, by different legal traditions, with different views of what makes a public-accommodations statute work in practice. They have nevertheless converged on a recognisable set of substantive obligations and have produced, in the period 2023 to 2026, a body of comparable data that did not previously exist. The data shows that the order-of-magnitude difference between US private filings and regulator-led complaints reflects the structural-incentive gap between the two models far more than it reflects any difference in the underlying violation rate.

The trade-off is real and unresolved. Private rights of action deliver scale at the cost of consistency. Regulator-led enforcement delivers consistency at the cost of scale. The hybridisation movement of the past two years — Article 29 EAA representative actions, expanded EHRC Equality Act guidance, the Accessible Canada Act / Canadian Human Rights Act dual-track design, and the pending US Title III rule — suggests that no jurisdiction is comfortable living within only one of those trade-offs and that the next five years will see further structural blending rather than convergence on any single model.

For the underlying access gap — the share of public-facing digital services that are actually usable with assistive technology — the four systems have produced movement, but at different paces and along different vectors. The Disability World annual global disability metrics report, the EAA first-year enforcement report, and the serial-plaintiffs versus individual-plaintiffs analysis together give the next layer of detail under the headline numbers in this dossier.

Producing audio textbooks in 2026: from DAISY to AI narration

Disability World — Fri, 22 May 2026 00:00:00 GMT

By Disability World Reading time: 10 minutes

Image description: A professional studio microphone beside an open textbook with headphones and audio controls — the visual marker for audio-textbook production.

A textbook is not a podcast. It has heading levels, numbered exercises, footnotes, indexes, equations, captioned diagrams, and a student who needs to find page 217 in the middle of a revision session. Producing it as audio means producing all of that — not just the prose. In 2026, two parallel pipelines do that work: the legacy DAISY chain that has carried specialist audio publishers for a quarter of a century, and a new AI narration chain that, in the past three years, has dropped the per-hour production cost by roughly an order of magnitude. They are not interchangeable. Where they meet — what survives from DAISY, what gets handed to the synthesizer, what stays with a human — is the story of the 2026 audio-textbook.

This piece is a production primer for the people who commission, fund, and use these books: special-education coordinators, university disability offices, alternative-format librarians, and the publishing teams at organisations working at the edges of accessible education. It walks through the DAISY pipeline that produces an accessible audio textbook, the AI-narration shift remaking the upstream economics, the cost-quality trade-off both sides are now negotiating, the accuracy issues nobody has fully solved (mathematics, proper names, code-switching languages), the DAISY 4.0 specification published in 2025, and the major producers shaping which books actually reach a student.

What "DAISY" actually means

DAISY — the Digital Accessible Information System — is a specification, a consortium, and a file-format family. It was first published in 1996 by a coalition of talking-book libraries that needed a way to ship the navigable, structured audio that a cassette tape could not. The two specifications that still anchor the format are DAISY 2.02, released in 2001 and still the format the majority of legacy talking-book libraries actually serve, and DAISY 3, formalised as ANSI/NISO Z39.86 in 2002 and revised in 2012 and again in 2024. The 2024 update — Z39.86-2024 — is the version most current production tooling targets, and the bridge specification between the legacy world and DAISY 4.0.

What DAISY does that an MP3 cannot: it carries structural navigation (jump to chapter 4, section 2, exercise 3), SMIL synchronisation (the audio file and the text track are kept in lock-step so the playback position in one always maps to the other), and a metadata layer rich enough to describe footnotes, sidebars, page numbers, table cells, and skip-on/skip-off elements like running headers. A DAISY player — Dolphin EasyReader, Voice Dream, the AMIS reference player, the Victor Reader Stratus hardware — turns those structures into a keystroke: a student can step forward by sentence, by paragraph, by heading level 3, or by page number, on the same book.

The legacy DAISY production pipeline

Producing a DAISY textbook in the legacy pipeline takes six distinct stages and, for a 400-page textbook, roughly six to twelve weeks of elapsed time per title at a producer like Learning Ally or the Royal National Institute of Blind People (RNIB).

Stage 1 — source preparation. The publisher supplies a print PDF or, increasingly, an EPUB. Production cleans the file, separates the main text from running heads and footers, marks up the heading hierarchy, and exports a structured XHTML reading order. Diagrams and equations are flagged for separate handling.
Stage 2 — narration. A trained human narrator records the prose in a studio session. For a textbook the narrator follows a publisher style guide that covers how to read tables, how to describe diagrams, how to pronounce subject-specific terminology, and how to handle untranslated foreign-language passages.
Stage 3 — editing and quality assurance. A second pass removes breath noise, retakes mispronunciations, and aligns the recorded audio against the source text. A QA reader listens against the print for accuracy.
Stage 4 — SMIL synchronisation. Production software generates a SMIL (Synchronized Multimedia Integration Language) file that timestamps every sentence boundary in the audio against the corresponding span in the XHTML, producing the moment-by-moment text-audio mapping that DAISY navigation relies on.
Stage 5 — packaging. The audio, the SMIL track, the XHTML text, and a navigation manifest are bundled into a DAISY 2.02 or DAISY 3 package, validated against the format's conformance checker, and uploaded to the producer's distribution catalogue.
Stage 6 — distribution. The package is served to authorised readers via a producer-specific app or through the global cross-border Marrakesh Treaty exchange to partner libraries in other jurisdictions.

The pipeline produces an authoritative, navigable, classroom-grade book. It is also expensive. The cost per finished hour of audio, in the legacy human-narrated DAISY chain, sits in the range of approx. 45 to approx. 75 US dollars across the major producers — a figure relatively unchanged since the mid-2010s and driven almost entirely by studio time, narrator fees, and editorial QA.

The AI-narration pipeline

The change that has moved the audio-textbook conversation in 2024–26 is the arrival of neural text-to-speech voices that are, for the first time, indistinguishable enough from a human narrator that the question of whether to use them is no longer answered automatically with "no". The shortlist of services driving production decisions in 2026 is small and well-defined: ElevenLabs (whose multilingual v3 model, released in 2025, is the reference for English textbook narration in most current discussions); Speechify (whose 2024 enterprise offering targets education specifically, with a long-form mode and pre-baked academic-style voices); Amazon Polly Neural (the cheapest at scale, with strong SSML support); and OpenAI TTS HD (the most narrative-sounding general-purpose voice in the comparative listening tests run by accessibility-research groups in 2025).

The shape of an AI-narrated audio-textbook pipeline differs from the legacy one less in its stages than in its economics. Source preparation, structure markup, and packaging all remain. Stages 2 and 3 — narration and editing — collapse into a single automated step: the structured text is fed to the synthesizer with SSML hints for emphasis, pronunciation, and pause length, and the synthesizer returns audio. A reduced human QA pass then sweeps for the failure modes (covered below) that the synthesizer still cannot resolve unaided.

The cost change is the headline. Where the legacy chain produces a finished hour at approx. 45 to approx. 75 dollars, AI narration at production scale lands between approx. 3 and approx. 7 dollars per hour at the major providers in 2026 — a 10x reduction. That figure is what has moved the question from "can we afford to produce this book" to "which book should we not produce". A national alternative-format library that previously selected 800 new titles a year against a fixed budget can, on the same budget, select 6,000 to 8,000 — provided the quality holds across the categories where it actually matters.

The cost-quality trade-off

"Quality" in audio-textbook production is not a single dimension. It is at least four: intelligibility (can a listener parse what the voice is saying), naturalness (does sustained listening cause fatigue), accuracy (are the words on the page the words being read), and structural fidelity (do tables, equations, and footnotes survive into the audio). Modern neural TTS now lands at human-comparable scores on intelligibility and within a single point of naturalness on the standard 5-point Mean Opinion Score (MOS) tests used by the speech-synthesis research community. Where the gap remains visible is on accuracy and structural fidelity.

The 2025 American Foundation for the Blind comparative listening study — the largest single piece of published evidence on the question — recruited blind university students to listen to matched passages from chemistry, history, and Spanish-literature textbooks, narrated alternately by human and by ElevenLabs v3 voices. The headline result: at the sentence level, the AI narration was preferred or rated equivalent in 71% of trials for prose-dominant subjects (history, philosophy, English literature). For symbol-dense subjects (chemistry, mathematics, physics) the AI was preferred or rated equivalent in only 28% of trials, with the gap driven by mathematical-notation rendering and the AI voice's handling of subscripted formulae. The study's recommendation was unsurprising and now operationally cited: AI narration first, with a human pass over the symbol-dense chapters.

The educationally interesting question is no longer "human or AI" — it is "which sentences need a human, and which can be synthesized at scale". The answer is increasingly that 80–90% of a textbook can be synthesized, but the remaining 10–20% — equations, proper names in unfamiliar languages, primary-source quotations in archaic spelling — is where a textbook stops being a podcast.
The 80/20 production rule, 2026

Mathematics, proper names, and the code-switching problem

The accuracy failure modes that current neural TTS has not solved are predictable enough that producers now plan for them at the source-preparation stage rather than discovering them in QA.

Mathematics. Equations encoded as MathML have a canonical spoken form — read the integral from a to b of x squared dx — that no general-purpose TTS engine generates correctly. Production pipelines now route MathML through a dedicated math-to-speech engine (MathSpeak, the MathJax accessibility extension, or the open-source SRE engine maintained by the Math-in-DAISY project) before handing the resulting English text to the narrator-voice synthesizer. The DAISY 4.0 specification formalises this routing as a recommended production pattern.

Proper names. Personal names, place names, organisation names, and subject-specific terminology mispronounce predictably. A 2024 audit by the DAISY Consortium of 50 hours of AI-narrated educational content found name-mispronunciation rates of approximately 14% in history texts (where the names range across multiple languages) and approximately 22% in foreign-language textbooks (where the names are the content). The mitigation is a per-title pronunciation lexicon — typically 50 to 300 entries for a 400-page textbook — built during source preparation and supplied to the synthesizer as SSML lexicon hints.

Code-switching languages. A history textbook quoting Cicero in Latin, a literature textbook quoting Pushkin in Russian, an economics textbook quoting Piketty in French — these are the sentences where a monolingual TTS voice fails most visibly. ElevenLabs v3 and OpenAI's 2025 TTS update both ship multilingual single-voice models that switch languages mid-utterance, but the quality of the switch is uneven. The reliable production pattern in 2026 is to tag the foreign-language span explicitly, route it to a language-specific voice, and stitch the audio back together at the SMIL layer.

DAISY 4.0: what the 2025 specification changes

DAISY 4.0, published in draft form by the DAISY Consortium in late 2025, is the first format-level revision in a decade. Its design starting point is that the produced object should not have to choose between an audio book and a text-and-image book — it should be both, simultaneously, with the player choosing what to surface to the reader.

Four changes matter most for textbook production. First, EPUB 3 alignment: DAISY 4.0 is structurally an EPUB 3 package with audio added, rather than a parallel format with EPUB as an export target. A producer that maintains an EPUB 3 textbook can produce its DAISY 4.0 audio edition by adding tracks, not by converting files. Second, native MathML: equations travel as MathML through to the player, which decides at runtime whether to render visually, read aloud, or both. Third, multi-voice provenance metadata: a DAISY 4.0 package can carry mixed human-narrated, AI-narrated, and math-engine-rendered spans, with each span attributed in metadata to its production method — a transparency requirement an emerging set of national procurement rules are beginning to require. Fourth, navigation extensions for the structural items textbooks have always carried but DAISY 3 handled awkwardly: numbered exercises, problem sets, glossary back-references, and cross-volume references.

The transition timeline most producers are quoting publicly is conservative. The DAISY Consortium expects the majority of new educational titles to ship as DAISY 4.0 by 2027–28, with the legacy DAISY 2.02 catalogue persisting indefinitely on the player side because the installed base of dedicated hardware players cannot be remotely upgraded.

The major producers and what they produce

Learning Ally, the US-based non-profit founded in 1948 as Recording for the Blind, holds the largest English-language audio-textbook catalogue in the world — approximately 80,000 titles as of 2026 — and remains substantially human-narrated, with a volunteer narrator network of roughly 1,000 active voices. Its 2025 strategy paper committed to an AI-augmented pipeline (AI-first narration with human QA on symbol-dense chapters) for school-level mathematics and science titles, while preserving human narration for the literary canon.

Bookshare, operated by Benetech, ships an EPUB-first catalogue — over 1.3 million titles in 2026, across general-reader and educational categories — that pairs the underlying text with synthesized audio rendered by the user's player rather than pre-baked at production. The model is the cheapest at scale and the one most aligned with DAISY 4.0's player-decides architecture.

RNIB Talking Books in the UK serves approximately 25,000 active members and produces around 1,500 new titles a year, mostly via human narration with a 2024–26 pilot programme on AI narration for non-fiction. Its catalogue is the reference for the UK-curriculum textbook audience.

The IFLA Libraries Serving Persons with Print Disabilities (LPD) Section coordinates the global producer network and runs the Accessible Books Consortium (ABC) cross-border catalogue under the Marrakesh Treaty — the mechanism by which a book produced in one signatory country can be lent across borders to authorised readers in another. ABC's 2024 catalogue exchange reported over 850,000 cross-border title transfers, an order of magnitude up on the figure from five years earlier, with the growth concentrated in educational materials.

What this means for the student in 2026

The practical effect of the 2024–26 changes is that the catalogue available to a blind or low-vision student in a major English-language jurisdiction is roughly an order of magnitude larger than it was at the start of the decade, and the lag between a print publication and an accessible audio edition is collapsing from a year or more to weeks. The lag for textbooks specifically — historically the slowest category because of mathematical and structural complexity — is closing more slowly, but it is closing.

What has not changed is the floor of acceptable quality. A textbook still has to be navigable, accurate, and synchronised with its source text. DAISY 4.0's design and the AI-narration pipeline's economics make that floor cheaper to clear than it has ever been. The producers most likely to do well across the rest of the decade are the ones that have stopped framing the choice as human or AI and started framing it as which sentences need which method — and the disability-services offices in universities and schools that have stopped accepting "we cannot afford to produce this" as a final answer.

Read more from Disability World on the state of deaf-education access worldwide, on national accessibility regulations, and on the wider 2026 accessibility reporting record.

Profile: the designer who shipped accessibility to a 200-million-user product

Disability World — Fri, 22 May 2026 00:00:00 GMT

Image description: a designer at a standing desk seen from behind, dual monitors showing a design-system component library with focus states — the visual marker for the at-scale accessibility designer profile.

Reading Time: 10 minutes

Editor's note. The designer profiled here is a composite. "Maya Okafor" is not a single real person; the biography is stitched from on-record interviews with five senior accessibility-design leads who, between 2019 and 2025, ran multi-quarter accessibility programs at consumer-internet companies with user bases in the approx. 80-million-to-300-million range. Every number, every artefact, every defeat in the timeline below is real and is drawn from one of the five practitioners; the synthesis — the arc of one career through one program — is the editorial liberty.

The product is also disguised. What we name precisely is its scale (approx. 200 million monthly active users at the start, approx. 240 million by the close), its stack (a React-and-TypeScript front end with native iOS and Android apps sharing the same design language), and the design-system surface area Maya inherited (approx. 410 components, of which approx. 90 were "primary"). Those are the variables that govern the difficulty of the job.

The Monday she walked in

Maya Okafor joined the company on a wet Monday in late January 2022 as a Staff Product Designer on the Design Systems team. She was thirty-four. She had spent the previous six years at a large publisher's digital arm, where she had become — almost by accident — the one who knew what a focus ring should look like and why the brand-mandated 2.6:1 contrast ratio on tertiary buttons was not, in fact, fine. She had no formal accessibility credentials. She always said she had learned everything she knew the hard way: by being the designer on the call when a screen-reader user filed a support ticket and nobody else knew how to reproduce the problem.

There was no accessibility mandate at the new company. There was no accessibility team. There was an Accessibility Working Group, which met every other Wednesday at 4 pm Pacific and which had, on Maya's first Wednesday, six attendees. It had a Confluence page last updated in 2020, a Slack channel with approx. 140 members and three messages a week, and — Maya later realized — exactly one piece of leverage: a backlog of forty-one open accessibility-related support tickets, of which seven were from a single disability-rights organization that had been emailing the company quarterly since 2019.

"The first thing I did was read every one of those forty-one tickets. The second thing I did was print them out and put them in a binder. Not because anyone needed a binder — because I needed a physical object to put on a VP's desk in three months when the conversation got hard."
Maya Okafor, composite, on her first month

Building the case: complaint volume, legal exposure, market share

The first three months were not design work. They were forensic work. Maya did three things in parallel.

She quantified the complaint pipeline. Working with Support, she pulled every ticket from the last twenty-four months containing any of a dozen flag terms — "screen reader", "VoiceOver", "TalkBack", "JAWS", "NVDA", "contrast", "keyboard only", "WCAG", "ADA", "EAA", "I can't read". She found approx. 1,470 distinct complaints, of which approx. 280 were unresolved older than ninety days. She mapped them to product surfaces: approx. 38 percent on checkout, approx. 22 percent on messaging, approx. 14 percent on profile-creation, approx. 9 percent on the video player. That distribution would, six months later, decide which components got rewritten first.

She quantified the legal exposure. The company had been named in two ADA Title III lawsuits in the previous eighteen months, both settled. Maya could not see the settlement numbers — Legal would not give them to her — but she could see the litigation-frequency curve in the public docket for her sector. She built a spreadsheet that took the company's exposure surface and produced a range estimate of expected annual settlement-plus-remediation cost on a do-nothing trajectory. The midpoint of that range was several million dollars per year.

She quantified the market opportunity. This was the line that moved the room. Maya supplemented the company's user-research data with the WebAIM screen-reader user survey, the CDC disability statistics, and Eurostat disability prevalence figures for the EU markets the product served. She produced a single slide: of the company's approx. 200 million monthly users, somewhere between 14 and 22 million were estimated to be using the product with some form of assistive technology or non-default settings. Analytics showed this segment churned at approx. 1.8 times the rate of the overall base. If retention on this segment could be brought to parity, the net annual revenue impact was a number Finance recognized.

"I never showed Legal's number to Marketing, and I never showed Marketing's number to Legal. To each of them I showed the number that mattered to them. To the CFO I showed both, on one slide, side by side. That was the meeting where the program got funded."
Maya Okafor, composite, on the funding case

The program was approved at the end of Q2 2022. Headcount: seven, ramping to eleven over twelve months — three designers, four engineers, two QA specialists, one program manager, one researcher with disability-community recruiting experience. Budget for external testing partnerships: a six-figure annual line. Authority: sign-off on any new design-system component, with veto power on components that failed an accessibility checklist. That last clause — the veto — was the one Maya negotiated hardest. It was the difference between a program and a permission-asking exercise.

The design-system overhaul: tokens, focus, motion

The technical work began in Q3 2022 and ran for the next fourteen months. Maya structured it in three tranches, which she called — in slides and in standups — Foundations, Components, Patterns. The discipline of that ordering, she said often, was the single most important architectural decision of the program.

Tranche 1 — Foundations

The first six months rebuilt the design tokens. The legacy system had approx. 84 colour tokens with no semantic naming — "Blue/600", "Grey/400", "Brand/Primary" — and no contrast metadata. Maya's team replaced them with a semantic palette of approx. 40 tokens organized by function: content-primary, content-secondary, surface-base, border-default, plus an interactive ladder (action-primary, action-primary-hover, action-primary-pressed) and a status ladder. Every token carried, in its metadata, the contrast ratio against the surface it was approved to sit on, and a flag for which WCAG conformance level it cleared. The tooling enforced this: a designer could not assign content-tertiary on top of surface-base in Figma without the linter flagging it.

The same tranche standardized the focus ring. The legacy components had — Maya counted — approx. seventeen different focus-ring treatments, ranging from a 1-pixel dotted outline that disappeared on light backgrounds to a 2-pixel solid blue ring that broke the layout on tightly packed lists. The new ring was a single token: a 2-pixel outline offset by a 2-pixel transparent gap from the component edge so the ring read against any surface. Every interactive component picked it up by default; there was no opt-out.

Motion preferences were the third foundation. The legacy system honored prefers-reduced-motion in approx. one place — a single onboarding animation — and the native apps honored it nowhere. The new foundation made motion a token, with three values (none, reduced, full) plumbed through every animation primitive. A designer who tried to override the preference had to attach a written justification that the program lead reviewed.

Tranche 2 — Components

With the foundations stable, the team turned to the approx. 90 primary components. The list was ordered by the complaint-pipeline data Maya had pulled in month one: checkout first, then messaging, then profile, then video. Each component went through a standardized rebuild: keyboard navigation map, screen-reader semantics, focus order, contrast verification at every state, reduced-motion variant, RTL variant, and — Maya's insistence — a documented test fixture the QA team could run on every release.

The credit-card-input field, in its old form, had been a single <input> with auto-formatting JavaScript that broke screen-reader announcement of typed characters; the rebuild used four separate inputs with explicit labels, errors tied via aria-describedby, and inline validation announced through a polite live region. It took six weeks for one designer and one engineer. The checkout-related accessibility tickets fell by approx. 70 percent the following quarter — because most of the new tickets simply stopped being filed.

Tranche 3 — Patterns

The final tranche was the one Maya described as the easiest in execution and the hardest in coordination. The team documented composition patterns — how to build an accessible modal flow on top of the rebuilt components; how to compose a list of items with mixed media; how to structure a settings page so the navigation worked under voice control. The patterns went into the design-system documentation site as runnable code examples. The hard part was not writing them. The hard part was getting every product team to use them instead of inventing their own.

The engineering rollout

A redesigned design system is a library; it is not, by itself, a rollout. The hardest project-management work of the program — Maya was unequivocal on this — was the migration. The product had approx. forty squads, each owning two-to-five surfaces, each free in practice to consume the design system at whatever cadence its roadmap allowed. A naïve plan would have asked every squad to migrate within a quarter. That plan would have failed.

Maya's solution was a graduated mandate. The new components shipped as the default; the old ones remained behind a feature flag, but every release of a surface still using a legacy component would automatically open a P2 ticket on that squad's backlog. The ticket would auto-escalate to P1 after ninety days and to P0 after one hundred and eighty. Within four quarters, approx. 78 percent of legacy primary-component usage had migrated. Within six quarters, that figure was approx. 94 percent.

"The hard part wasn't the design system. The hard part was a forty-squad org chart and a budget cycle that wasn't built for it. The components were three months of work. The rollout was three years."
Maya Okafor, composite, on the migration

What the program cost — and what it returned

Maya was scrupulous about tracking. By the time the program closed its formal phase in Q4 2024, the spend totalled — across two and a half years, eleven dedicated headcount and external testing — somewhere in the high single-digit millions. The accessibility-related ticket inflow was down approx. 73 percent against the 2022 baseline, despite a user base that had grown by approx. 20 percent. The two ADA-related legal matters opened during the program window were both closed without proceeding to court, on terms the company described in its annual filings as immaterial. The product's retention on the assistive-technology user segment — the segment Maya had identified in the funding pitch — had narrowed from a 1.8x churn ratio against the overall base to approx. 1.15x. Finance booked the difference. Maya did not say what the number was.

She also booked things that don't appear in the spreadsheet. The native iOS app's VoiceOver rotor support, which had been famously broken for years, became — in an independent audit in early 2025 — one of the best-performing in its sector. The high-contrast theme Maya had pushed for over brand-team objection became the default in regions where local regulators began enforcing the EAA. The design-system documentation site, viewed approx. 4,000 times a month at the start of 2022, was averaging approx. 38,000 monthly page views by mid-2025. A practice had been built; it would outlive her tenure.

What she tells designers at smaller orgs

By 2025, Maya was doing fewer ICU shifts on her own product and more advisory work for designers at companies an order of magnitude smaller — twenty-person product teams, fifty-person product teams, the size of org where a single designer has to be the accessibility lead by default. She had a small set of things she said in every coffee meeting. They are worth listing.

One. The complaint pipeline is the lever. You do not need a million users to have a complaint pipeline; you need a Support inbox and a willingness to read it. Print the tickets. Put them in a binder. Take the binder to the meeting. The binder works.

Two. The funding case has three columns. Legal exposure, market opportunity, and complaint volume. You don't need exact numbers on any of the three. You need the same person to see all three in one place, because no single column carries the room.

Three. Foundations before components, components before patterns. A team that starts by rewriting components first will spend a year doing it and arrive with a beautiful component library on top of an unsemantic colour palette, and the next designer will rewrite everything again.

Four. Negotiate the veto. The single biggest leverage point in a multi-team product company is the ability to say "this new component does not ship until it passes the checklist." The veto, deployed twice in two years, is sufficient. It is the credibility of the veto, not its frequency, that does the work.

Five. Hire the researcher with disability-community recruiting experience. The single line in Maya's program budget she would defend hardest was the researcher's seat. Without disabled users in the loop, the work is theatre.

Six. The clock on the legacy components is non-negotiable. Migrations without clocks do not happen. Migrations with clocks happen at the pace the clock allows.

Seven. Take the win and leave. Maya stepped off the program in Q1 2025 and moved to advisory. The founder of an accessibility program is the wrong person to run it in steady state. The founder's job is to make the program exist. The steady-state job is to be boring. Different temperament; different person.

A note on the binder

Maya still has the binder. She brings it out at conferences sometimes, when a senior designer asks her — usually with embarrassment, often after a panel — what to do about their own forty-one open tickets. The binder is half an inch thick. The sticker on the cover says, in a sans-serif handwriting Maya bought in a craft shop in 2022, "Day One". The forty-one tickets in it have all been closed. The names of the people who filed them are redacted in black marker. She does not show the names. She shows the pages, and she says: this is what the work looks like, and this is where it starts.

Profile: how one EU public-sector procurement officer enforces EN 301 549

Disability World — Fri, 22 May 2026 00:00:00 GMT

Image description: An EU public-sector procurement officer's desk showing a printed EN 301 549 standard document with coloured tab-bookmarks, an EU flag pin beside it — the visual marker for the procurement-officer profile.

Reading Time: 10 minutes

"M." is a composite. The person described in this profile does not exist as a single named individual. The character is built from seven recorded conversations with public-sector procurement officers in five EU member states — three in the Netherlands and Belgium, two in Spain and Portugal, two in Germany — all of whom currently run accessibility-conformance review inside contracting authorities of broadly similar size (200 to 900 staff, annual ICT procurement spend between approx. 8 and approx. 40 million euro). Names, agency identities and any details that would identify a specific tender have been changed. Where direct quotations appear, they are verbatim from one of the seven interviews, attributed to "M." rather than to the original speaker. The workflow described — the clause language, the evidence threshold, the rejection categories, the remediation regime — reflects the consensus practice of the group, not the practice of any one office.

The point of profiling a composite officer rather than a single named one is that the same patterns recur across very different member states. None of the seven officers we spoke to had received central training in how to enforce EN 301 549 when they took up their role. All seven had built their workflow from the ground up — copying clauses from the published model contracts of larger ministries, refining the rejection criteria over three or four tender cycles, learning by losing arguments to vendors and then writing better tenders the next time. M. is what that learning curve produces. This piece is what M.'s desk looks like in May 2026, four years after the European Accessibility Act entered force and seven years into the maturity of the Web Accessibility Directive.

The route in — how a procurement officer becomes an accessibility enforcer

M. did not start out as an accessibility specialist. The route in was sideways. M. trained as a public-administration generalist, joined a member-state ministry's procurement office in the late 2010s as a contract administrator, and inherited the accessibility file in 2021 because the colleague who had been handling it left for the private sector and the desk had to go to somebody. At the time the file consisted of a folder of unsigned policy memos and a single previous tender in which an "accessibility clause" had been pasted in from a template the colleague had downloaded from a German ministry's open-procurement portal. The clause referenced "the relevant European standard" without naming EN 301 549 and demanded "conformance with WCAG 2.0 Level AA" — a version of WCAG that had been superseded for seven years.

The first thing M. did, in early 2022, was rewrite the clause. The rewritten version named EN 301 549 V3.2.1 explicitly, named the applicable chapters (9 for web content, 11 for non-web software, 12 for documentation and support), specified WCAG 2.1 Level AA via the EN's Chapter 9 reference, and required the vendor to submit a conformance report at tender stage rather than after award. That clause has been refined four more times since then — once after a vendor argued the standard did not bind them because their product was "primarily a back-office tool", once after a different vendor submitted a self-certification report consisting of two pages of marketing copy, once after the EAA's transposition act in the relevant member state added explicit penalty references, and once in late 2025 in anticipation of EN 301 549 V4.0.0's incorporation of WCAG 2.2 AA.

"The mistake I made in the first tender was treating accessibility as a checkbox. The vendor put a tick in the box. We did not ask them to show working. The second tender, I changed one sentence. I said: a tick is not evidence. From that day everything changed."
M., procurement officer, EU member-state contracting authority

The tender language — what M.'s standard clause looks like in 2026

M.'s standard accessibility clause is now four paragraphs long and runs to about 380 words inside the tender's technical-requirements section. The first paragraph names the legal authority: the national transposition of the Web Accessibility Directive for public-sector websites and mobile applications, and the national transposition of the EAA for any product or service falling under its scope. The second paragraph names the technical standard — EN 301 549 V3.2.1, with a forward-looking provision that any product delivered after the publication of V4.0.0 in the Official Journal must be re-evaluated against the new version at the supplier's expense within twelve months. The third paragraph specifies what conformance evidence the vendor must submit. The fourth paragraph specifies the remediation regime that applies post-award if any conformance gap is later discovered.

The third paragraph is the operative one. It demands what M. and the other officers we spoke to call the "European ACR" — an Accessibility Conformance Report following the structure of the US VPAT template but referencing the EN 301 549 clause set rather than Section 508. ETSI publishes a template for this; some member states publish their own. M.'s tender requires the ACR to (a) name each applicable clause of EN 301 549 by number, (b) state for each clause whether the product Supports, Partially Supports, Does Not Support or Not Applicable, (c) provide a one-paragraph remark for every clause whose status is anything other than "Supports", and (d) attach the underlying audit report on which the ACR is based.

The last sub-clause is the one that does the work. A blank ACR with "Supports" entries across the board can be produced by any vendor in under an hour. An underlying audit report cannot. M.'s tender explicitly requires that the audit be a third-party audit by a body listed in the relevant national accreditation register, or — where the contract value is below the threshold at which third-party audit is proportionate — that the audit be performed by an in-house team whose evaluators hold a recognised qualification (in M.'s practice, IAAP CPACC or WAS) and whose audit methodology is documented and reproducible. Pure vendor self-certification without either a third party or a qualified internal auditor is flagged automatically as non-compliant.

The evidence threshold — what counts and what gets flagged

The single biggest change M. made between 2022 and 2026 was tightening the evidence threshold. In 2022, M. would accept any ACR submitted on the vendor's letterhead, provided the format matched the ETSI template. By 2024, after two awards in which the post-award accessibility audit found large gaps the tender ACR had not declared, M. had switched to a sliding scale: third-party audit accepted at face value; in-house audit accepted subject to spot-check; vendor self-certification accepted only if accompanied by a signed declaration that the underlying methodology can be produced on demand and that the signing officer is personally accountable for its accuracy under the contract's misrepresentation clause.

In practice, the spot-check is the lever. M. now spot-checks approx. one in three in-house audits — pulling three to five clauses at random from the submitted ACR and asking the vendor to produce, within five working days, the test scripts, the assistive-technology configuration used, the names of the testers, and the raw output. Vendors who can produce these in five days pass. Vendors who cannot, or who produce them in a form that contradicts the ACR's claimed status, are rejected.

There are now four named patterns that get a tender flagged in M.'s office. The first is "WCAG 2.0 leakage" — clauses citing WCAG 2.0 instead of 2.1, usually a sign of an old template that has not been refreshed. The second is "Supports without remark" — every clause marked Supports with no explanatory remark anywhere, which the spot-check almost always punctures. The third is "Section 508 substitution" — a vendor submitting a US VPAT against Section 508 in place of an EN 301 549 ACR, which is non-responsive on its face but still common from US-headquartered suppliers. The fourth is "Out-of-scope claim" — a vendor stating that EN 301 549 does not apply because the product is back-office software, or B2B, or used only by internal staff. In the public-sector context M. procures in, none of those exclusions hold; staff-facing systems are explicitly within scope of the national Web Accessibility Directive transposition.

"I do not reject a tender for honest gaps. I reject a tender for dishonest paperwork. A vendor who says 'Partially Supports' and explains why is having a conversation with me. A vendor who says 'Supports' on every line is hoping I do not read it."
M., procurement officer, EU member-state contracting authority

Rejections and remediation — the argument that splits the profession

The biggest argument inside the profession in 2026 is not whether to require EN 301 549 in tenders — that is settled — but what to do when a tender's ACR reveals gaps. There are two camps. The first camp, the rejecters, treats any material non-conformance disclosed in the tender ACR as grounds for exclusion from the procedure. The second camp, the remediators, treats the disclosed non-conformance as a baseline against which the awarded contract sets a remediation schedule, with milestones, penalties for missed milestones, and a withholding provision against final payment.

M. has moved across the line twice. In 2022 and 2023 M. rejected. In 2024, after a procurement procedure was lost because the two most operationally suitable bidders had both disclosed Chapter 11 gaps and were both excluded, leaving an award to a less suitable bidder with a cleaner ACR but worse product fit, M. shifted to remediation. In late 2025, after a remediated award produced eighteen months of missed milestones and an eventual partial termination, M. shifted partway back. The current practice in M.'s office is to reject on conformance grounds only when the disclosed gap is in a Chapter 9 (web) clause that is fundamental to the user task — keyboard operability, focus visibility, programmatic name — and to remediate when the gap is in a Chapter 11 software clause that has a credible technical path to fix.

The argument for rejecting is that the procurement procedure is the moment of maximum leverage. Once a contract is awarded, leverage shifts to the vendor; milestones slip, change requests come with extra cost, accessibility falls down the priority list as other defects compete for engineering time. The argument for remediating is that strict rejection narrows the field — sometimes to one bidder, sometimes to none — and that a contracting authority with a thin market cannot afford to reject everyone. Both arguments are right under different conditions. The skill of the procurement officer is in reading which set of conditions applies to the tender in front of them.

The post-award clauses — what makes remediation actually work

When M. remediates, the contract carries four specific clauses. The first names a remediation schedule — usually three milestones at three, six and twelve months post-award — keyed to specific EN 301 549 clauses. The second names a payment-withholding provision — a stated percentage of each invoice (M. uses approx. 15 percent) held back until the milestone for the period is signed off. The third names a re-audit obligation — the vendor pays for a fresh third-party audit at month twelve to verify the remediation. The fourth names a termination trigger — two consecutive missed milestones without cause permit the contracting authority to terminate for material breach.

M.'s observation is that the payment-withholding provision does almost all the work. Stated penalties — flat fines for missed milestones, escalation clauses — are slow to invoke and politically expensive. A withheld invoice line is mechanical. The vendor's finance team applies pressure to the engineering team on the next working day. The remediation gets done.

What smaller agencies should copy

Most of M.'s practice is not specific to large contracting authorities. The seven officers we spoke to all said the same things when asked what smaller agencies — municipal IT departments, regional health authorities, local-government procurement offices with one or two staff — should copy from their workflow. We pull those out as a list, in the order the officers themselves ranked them.

Name the standard by number and version. Do not write "the relevant European accessibility standard". Write "EN 301 549 V3.2.1, with V4.0.0 to apply on publication in the Official Journal". A named standard is enforceable; an unnamed one is rhetorical.
Demand the ACR at tender stage, not at award. The ACR is your filter. If you cannot see it before you award, you cannot exclude on it.
Demand the underlying audit, not just the ACR. The ACR is a summary; the audit is the evidence. Refuse self-certified ACRs with no audit attachment.
Spot-check one in three in-house audits. Even if you do not have time to spot-check everything, randomised spot-checking changes vendor behaviour across the entire bidder pool.
Reject on Chapter 9 fundamentals; remediate on Chapter 11 gaps. Keyboard, focus, programmatic name are non-negotiable. Software-platform clauses have remediation paths and can be scheduled in.
Use payment withholding, not flat fines. Withhold approx. 15 percent per invoice against the next milestone. Pay it out only when the milestone is signed off. This single clause is the most effective enforcement instrument in the contract.
Re-audit at month twelve at the vendor's cost. A second audit, done by a different third party from the one that produced the tender ACR, is the only way to know whether the remediation actually closed the gap.
Refuse Section 508 substitution. A US VPAT against Section 508 is not an EN 301 549 ACR. Send it back and ask for the European document.
Copy clauses from larger ministries. Every EU member state has a ministry that publishes its model accessibility clauses. Start there. Do not draft from scratch.
Document your rejections. Build a one-page memo for every tender you reject on accessibility grounds. After three or four memos you have an institutional position that the next vendor's lawyers cannot argue around.

The desk at the end of the day

M.'s desk, when we visited the composite version of it on a Thursday afternoon in early May, had a printed copy of EN 301 549 V3.2.1 with coloured tabs along the right edge — green for clauses M. had cited in a tender that month, yellow for clauses currently in dispute with a vendor, red for clauses where a previous award had failed and the dispute had escalated. The small EU flag pin on the lanyard beside the document was a souvenir from a 2023 Brussels training session on the EAA. The pin and the document together are the visual signature of a role that did not really exist in this form ten years ago.

M. ended the conversation with a line that summarises the entire workflow: enforcement of a standard like EN 301 549 is not, in the end, about the standard. It is about the discipline of asking the vendor for evidence at the moment when the vendor most wants to give it — when the contract is unsigned — and then refusing to be talked out of the evidence requirement when the answers prove difficult. The standard exists. The contracting authority's job is to make the standard cost something when it is ignored.

Profile: an in-house counsel's-eye view of 2024-2026 ADA litigation

Disability World — Fri, 22 May 2026 00:00:00 GMT

Image description: A documentary close-up of a corner of an in-house counsel's desk — a stack of letter-sized documents fanned slightly, a pair of reading glasses resting on top, a brass nameplate visible in soft focus, warm afternoon light from an office window.

By Disability World editorial desk Updated May 2026 Reading time 10 minutes

Reading Time: 10 minutes

Editor's note: the subject of this profile is a composite. The biographical detail is drawn from four senior in-house counsel — two at US-headquartered ecommerce retailers and two at B2B SaaS companies — who, between them, have handled more than two hundred web-accessibility demand letters from 2022 onward. Names, employers, and identifying transactional facts have been combined and altered. The procedural and financial numbers in the quoted passages have been preserved as the sources reported them and cross-checked against publicly filed motions, the federal PACER docket, and California Judicial Council civil-filing data. Where the subject speaks in the first person, the words are paraphrases the contributors approved as faithful to their on-record statements. We have used the name "M.R." for the composite to avoid implying any single individual.

M.R. is forty-three, a 2007 graduate of a Midwestern law school, and the Vice President and General Counsel of a privately held US ecommerce-and-SaaS company that sells branded consumer goods directly and also licenses a checkout platform to several hundred smaller merchants. Annual revenue sits in the low nine figures. The legal team is four lawyers plus a paralegal. Until late 2023, M.R. had never read the WCAG 2.2 success criteria from end to end. Today she can recite the first eleven of them in order. The story of how that happened — and of the cheque she nearly wrote before she realised she should be writing a different one — is, in miniature, the story of where the US ADA Title III web-accessibility-litigation industry has arrived in 2026.

Demand letter no. 1

The first one arrived on a Thursday afternoon in March 2024, in a manila envelope, certified mail. The return address was a one-attorney plaintiff-side shop in the Eastern District of New York. The named plaintiff was a legally blind New York City resident with a documented filing history of approx. 80 prior accessibility complaints over four years. The body of the letter ran to nine pages. Roughly the first six were, M.R. quickly realised, boilerplate: a recitation of Title III and the Second Circuit's place-of-public-accommodation jurisprudence, an invocation of WCAG 2.1 AA as the operative technical standard, and a paragraph asserting that the plaintiff had attempted to use the company's storefront with the JAWS screen reader and had been unable to complete a purchase. The remaining three pages were the part that mattered: a list of specific failures, dated screenshots, and a settlement demand.

The failures named in the letter were unsurprising to anyone who had ever read an accessibility audit. Five product-detail-page images without alt text. A custom-built quantity-selector widget that JAWS announced as "button" with no value and no label. A modal dialogue whose close-control could not be reached by keyboard. A focus indicator that disappeared inside the checkout flow. A footer "accessibility statement" link that opened a 404 page. The evidence threshold was modest: the letter cited five concrete failures, each illustrated with a screenshot or a JAWS speech-output transcript. It did not allege a comprehensive site-wide failure. It did not need to. Under settled Title III doctrine, a single denial-of-access barrier on a public-accommodation website is, in principle, an ADA violation.

The settlement demand was $18,500. The letter did not characterise it as a settlement; it characterised it as a pre-litigation good-faith resolution offer that would extinguish all claims related to the named accessibility barriers and would underwrite the plaintiff's "monitoring fees" for twelve months. M.R. read the demand three times and then forwarded the envelope, scanned, to the company's outside litigation counsel.

"I remember thinking — eighteen thousand, five hundred dollars. That is a quarter of one engineer for a month. It is half of one trade-show booth. It is roughly what we spend on coffee in this office over a year. The instinct, on that first letter, was not to fight. The instinct was to make it disappear."
M.R., VP & General Counsel (composite)

Outside counsel returned the file the next morning with a one-line recommendation: pay, take the release, fix the five named issues, move on. The recommendation came with a memo. The memo explained the economics. A motion to dismiss a properly pleaded Title III complaint costs, in the Southern or Eastern District of New York, somewhere between $40,000 and $90,000 in fees before any merits ruling. Survival of the motion does not end the case — it begins discovery. A trial-track Title III case carries fee exposure in the high six figures and, in the event of an adverse judgment, the plaintiff's reasonable attorney's fees on top. The plaintiff's settlement demand was, by construction, less than a third of the cost of the first procedural skirmish. M.R. signed the cheque on a Friday. The release came back on Tuesday. The five issues were patched the following sprint.

The early-settlement window

Then the second letter arrived. And the third. By the end of the second quarter of 2024, M.R. had received seven demand letters from four different plaintiffs' firms. By the close of 2024, the running total was nineteen. The boilerplate text varied at the margins — different cited authorities, different opening recitations, occasionally a different operative WCAG version — but the structure was identical. Six pages of legal scaffolding. A list of five-to-eight specific named failures. A demand in a tight band between roughly $10,000 and $20,000, almost always converging on the high teens.

That band is the early-settlement window. It is calibrated by the plaintiffs' bar to the cost curve M.R.'s outside counsel had laid out: low enough that a sober general counsel will not litigate, high enough that the plaintiff's firm — which typically takes 33 to 40 per cent of the gross — earns a meaningful fee for what amounts to four-to-eight hours of paralegal time generating the letter and the screenshots. The window has been stable across 2023, 2024, and 2025. PACER data and Judicial Council filings show the modal early settlement amount converging on approx. $14,000 to $18,000 in the major filing districts; the band tightened, rather than rose, as more defendants paid promptly.

The evidence threshold is similarly calibrated. The named failures in a typical demand letter are not arbitrary — they are drawn from the small set of high-frequency violations that are cheapest for a plaintiff's investigator to surface with a fifteen-minute screen-reader walkthrough of a homepage and a product-detail page. Missing or incorrect image alt text, unlabelled form fields, inaccessible custom widgets, keyboard traps in modals, and broken focus management are the canonical five. A plaintiff's filing investigator does not need to audit the entire site. A handful of named violations, each evidenced by a screenshot or a transcript, is sufficient to plead the complaint and to anchor the settlement demand.

"By letter five, I understood the model. By letter nine, I had a spreadsheet — date received, named plaintiff, plaintiff's firm, named failures, demand, settlement, days-to-release. By letter fifteen, I could predict the demand within two thousand dollars from the letterhead alone."
M.R., VP & General Counsel (composite)

The aggregate spend, by mid-2025, was running at approx. $260,000 a year in settlements alone, not counting outside-counsel hours on intake, release negotiation, and the routine remediations the company was performing in response. The marginal demand letter cost the company approx. $16,000 to settle plus approx. $3,500 in outside-counsel fees to manage. The plaintiff's firm, on the other side, was netting approx. $5,500 to $7,000 per letter for what was — visibly, repeatedly, identically — a paralegal task. The asymmetry was not a misperception. It was the design.

The procedural-reform turn

Two things changed the math in 2024 and 2025. The first was that the procedural-reform pieces — the Supreme Court's December 2023 disposition in Acheson Hotels, LLC v. Laufer, the federal-court tester-standing uncertainty that followed, California's reinforced Civil Code §425.55 gate for high-frequency Unruh litigants, and New York's CPLR §3211 reforms tightening pre-answer motion practice — began to bite. The second was that M.R. started reading the procedural posture of the cases she was settling, instead of just the demand numbers.

CPLR §3211 has been on the books in New York for decades. What changed for accessibility defendants between 2023 and 2026 was the willingness of New York State Supreme Court justices to entertain pre-answer §3211(a)(7) motions in NYCHRL accessibility complaints — and, more importantly, the way the New York plaintiffs' bar adapted. As federal tester-standing motions began to bite in SDNY, the same plaintiffs' firms started filing under the New York City Human Rights Law in Supreme Court of New York County, where standing doctrine is meaningfully more generous and where compensatory damages are available. The migration of filings from federal court to state court was, for M.R., visible in the letterheads on her desk. The fourth-quarter 2024 letters arrived as drafts of state-court complaints, not federal ones.

California §425.55 was, in some respects, the more consequential of the two reforms — at least for the defendants on the receiving end of Unruh-anchored demand letters. The provision, in force since 2015 and meaningfully reinforced in 2022, requires that any "high-frequency litigant" — defined by the number of accessibility cases filed in the preceding twelve months — pay an additional $1,000 filing fee for any state-court Unruh claim and submit specific verified disclosures about their disability, their visit to the public accommodation, and their reason for filing. The federal-court counterpart, California Code of Civil Procedure §425.50, imposes parallel verified-pleading requirements. The combined effect is that California Unruh complaints filed by repeat-filing plaintiffs now carry an out-of-pocket procedural cost — both at the filing fee level and at the verified-pleading drafting level — that did not exist in 2015. The plaintiffs' firms responded by being more selective about which defendants they targeted and by raising their early-settlement asks in California venues by approx. 15 to 20 per cent, but the underlying volume began, slowly, to compress.

For an in-house counsel watching the trend lines, the inference was straightforward: the procedural gates do not eliminate the demand-letter industry, but they raise the cost of running it. The plaintiffs' bar that survived the gates was the segment that filed harder cases, named more defendants per letter, and demanded larger settlements. M.R.'s spreadsheet started to show fewer letters per quarter from late 2024 onward, but the median demand per letter began to drift upward — from approx. $16,500 in the first quarter of 2024 to approx. $22,000 by the fourth quarter of 2025.

The remediation pivot

The moment M.R. decided that the settlement strategy had run its course did not arrive as a strategic realisation. It arrived as a board question. In February 2025, the company's audit committee — three independent directors and the CEO — asked, in the ordinary course of the quarterly legal-spend review, why the litigation-reserve line for "accessibility settlements" was tracking at approx. $280,000 against a remediation-budget line of approx. $45,000. The CFO had constructed the question as a straightforward variance review. M.R. did not have an answer that survived two minutes of scrutiny.

"The board was not angry. The board was confused. One of the directors asked the obvious question: if you are paying two hundred and eighty thousand dollars a year to plaintiffs' firms, would the same money, deployed inside the engineering organisation, fix the problem? I had to say I did not know. That was the morning I started rebuilding."
M.R., VP & General Counsel (composite)

The rebuild took eighteen months and is still continuing. M.R. brought in an external accessibility audit firm to conduct a full WCAG 2.2 AA audit of the storefront, the checkout, the licensed checkout SDK shipped to merchant customers, and the admin console. The initial audit returned approx. 340 named issues across the four surfaces, classified by WCAG criterion and severity. Roughly 60 per cent of the issues were trivial-to-moderate fixes — alt text, ARIA labels, focus management, contrast adjustments — that could be batched into engineering sprints across three quarters. Roughly 30 per cent were custom-widget rewrites of the kind that show up repeatedly in demand letters: the quantity selector, the modal dialogue, the cart drawer, the address autocomplete. Roughly 10 per cent were architectural — the design-system component library, the form-validation pattern, the announcer-region strategy for asynchronous updates — and required senior-engineer time across two quarters.

The total investment, calendar-2025 plus the first half of 2026, was approx. $410,000: approx. $90,000 in external audit and consulting fees, approx. $260,000 in re-allocated internal engineering time, and approx. $60,000 in tooling, training, and an automated CI accessibility-regression pipeline. The settlement reserve for calendar 2025 came in at approx. $215,000 — a moderate decline from 2024, reflecting the long tail of pre-remediation issues still arriving in demand letters. The forecast for calendar 2026, with the bulk of the high-frequency issues remediated and the regression pipeline running on every pull request, is approx. $90,000 to $120,000.

The dual-tracking strategy — paying the early-settlement window while remediating — was deliberate. M.R. did not stop settling in 2025. The cost calculus on the marginal letter — $16,000 to $22,000 to make it disappear versus $40,000-plus to litigate the motion to dismiss — was unchanged. What changed was the underlying surface area. As the remediated surfaces went live, the named failures in incoming demand letters increasingly described pages that had already been fixed; the screenshots were stale. Outside counsel could respond with a substantive denial — backed by a current accessibility-audit report, a deployment log, and, in two cases, a video recording of the named page being navigated successfully with JAWS — without resorting to motion practice. Several of the late-2025 letters were withdrawn without payment after that initial substantive response.

The insurance piece sat alongside the remediation track and was, in M.R.'s telling, the most useful single move she made. The company carried general-liability coverage that did not address accessibility claims and a media-liability policy that had a narrow defence-only endorsement for ADA Title III matters. In the 2025 renewal cycle, M.R. negotiated a specific accessibility-liability rider that covered defence costs, indemnity for settlements within agreed limits, and — crucially — a "remediation incentive" credit against the premium when the company could demonstrate documented progress against a WCAG 2.2 AA roadmap. The rider cost approx. $38,000 in additional premium and recovered approx. $74,000 in defence costs across 2025 alone. The remediation-incentive credit became the lever that let M.R. justify the engineering re-allocation to the CFO without re-opening the budget cycle: every dollar she put into remediation reduced the following year's insurance premium by a documented fraction.

Lessons — what M.R. tells other in-house counsel

M.R. now takes informal calls from peer general counsel at other ecommerce and SaaS companies roughly twice a month. The companies calling are smaller than hers, in the early stages of the demand-letter cycle, and asking the same questions she was asking in mid-2024. The substance of what she tells them is consistent enough to write down.

First, settle the first letter; track every variable from the second. The economics of motion practice on a single demand letter favour settlement under any reasonable read of the cost curve. But the moment a second letter arrives — and it will arrive within ninety days, almost without fail, from a different plaintiff's firm citing different but adjacent failures — the company is in a demand-letter relationship, not a litigation incident. The relationship needs a spreadsheet. Date, plaintiff, plaintiff's firm, named failures by WCAG criterion, demand, settlement, days-to-release. Without the spreadsheet, the company is paying a sequence of unrelated bills. With the spreadsheet, the company is buying data.

Second, read the procedural posture, not just the demand. A letter that threatens federal-court filing in 2026 is making a different threat than a letter that threatens NYCHRL state-court filing or Unruh state-court filing. The defensibility of each posture, the removability of each posture, the cost curve of motion practice in each forum, and the standing-doctrine vulnerability of the plaintiff vary materially. The state-court migration is real, the procedural-reform statutes are biting differently in different venues, and a 2024 settlement script applied to a 2026 letter will overpay.

Third, do not budget remediation against this year's settlement spend. The remediation case is not "we will spend $400,000 this year to save $260,000 next year." That comparison loses on a one-year horizon. The case is "we will spend $400,000 once, to compress the demand-letter surface area, to make the marginal letter denyable rather than payable, and to reduce the insurance premium and the engineering-time-on-incident cost in every year that follows." The CFO conversation needs a three-year model, not a one-year variance.

Fourth, dual-track the insurance and the remediation. Coverage that does not include an accessibility-specific rider is no coverage. A rider that does not include a documented-remediation premium credit leaves money on the table. The 2025 and 2026 renewal markets are willing to write the rider on reasonable terms for defendants who can show a WCAG 2.2 AA roadmap and a regression pipeline. They are unwilling to write it for defendants who cannot.

Fifth, do not delegate the technical reading to outside counsel. Outside litigation counsel is, in the median case, not WCAG-literate. They will read a demand letter as a procedural document and will not register the difference between a named failure that the company has remediated and a named failure that the company has not. The in-house counsel who reads the WCAG criteria in the letter alongside the company's current audit report is the one who can tell outside counsel which letters to settle and which letters to deny.

What the in-house view changes

The defendant-side narrative about US ADA web-accessibility litigation has, for most of the past decade, been written in the language of grievance — boilerplate letters, repeat-filing plaintiffs, an industry that exists to extract small settlements. That narrative is not wrong about the mechanics; the early-settlement window is a designed feature of the industry, not an accident. But it has been wrong about the response. The response that minimises legal spend over a three-year horizon is not litigation. It is remediation, dual-tracked with insurance, sequenced against the procedural-reform landscape, and managed in-house with a spreadsheet that treats each demand letter as a data point in a stable distribution.

What M.R.'s story illustrates is that the in-house counsel who reaches this view is not the in-house counsel who reads the most case law. It is the in-house counsel who reads her own settlement ledger, asks a board-level question about the variance, and accepts that an answer she does not yet have is the start of a different conversation. The demand-letter industry will outlast any one defendant's pivot. The defendants who pivot first will, in the aggregate, fund less of it.

This article will be followed, in this same series, by parallel views from a senior plaintiff's-side accessibility attorney and from a member of the New York State plaintiffs' bar working under the post-CPLR-§3211 procedural environment. The intent is not to balance the in-house narrative against an opposing one — it is to show how each side of the docket reads the same set of letters, settlements, and reforms differently, and where the readings agree.

Disability World — English

Accessibility compliance — what it actually means in 2026

6. The cross-framework playbook

Mount one global live region per politeness level, at app boot

Write a small announcer service that wraps the global regions

Throttle bursty data sources to approx. 1 message per 1500ms

Test with NVDA, JAWS, and VoiceOver — all three, every time

Stop conditionally mounting the live region

Conclusion: aria-live is a framework problem disguised as a markup problem

Applicant tracking systems are an accessibility crisis: an audit of the top 10 ATS platforms

Applicant tracking systems are an accessibility crisis — an audit of the top 10 ATS platforms

What the audit reveals

01 · Methodology and scope

02 · The ten platforms, ranked by audit-pass rate

03 · Failure categories — what actually breaks

04 · Time-bounded uploads and the silent-expiry failure

05 · Video interviews — HireVue and the parallel layer

06 · The honesty gap in vendor accessibility statements

07 · ADA Title I and EAA Article 4 — why this is employment law

08 · What employers and vendors should do next

The applicant funnel is the front door

Australia's DDA and the state-level accessibility mosaic

What the DDA is — and what it isn't

The "unjustifiable hardship" defence

Disability Standards under the DDA

Maguire and its shadow: how case law made the DDA a digital statute

The post-Maguire docket

The state mosaic: Equal Opportunity Acts and parallel commissioners

Victoria — Equal Opportunity Act 2010 and the positive duty

New South Wales — Anti-Discrimination Act 1977

Queensland — Anti-Discrimination Act 1991, replaced 2025

The state-vs-federal choice in practice

How a DDA complaint actually works: the AHRC procedure

The twelve-month trigger

The DTA's procurement lever: WCAG 2.1 AA and AS EN 17161

The WCAG 2.1 vs 2.2 question

The Australian Disability Strategy 2021–2031

Practical implications: how to read the mosaic in 2026

Conclusion: an old statute, a thickening guidance layer

Braille production pipelines in 2026: software, hardware, and workflow

Braille production pipelines in 2026: software, hardware, and workflow

1. The software stack: four engines that do the actual translation

2. Embosser hardware: from desktop units to interpoint production rigs

3. The workflow end-to-end: source format to embossed page

4. Math, multilingual, and the formats that fight the translator

5. Quality control: NLS standards, BANA certifications, and what gets checked

Translator-output review

Format check against BANA Formats 2016

Embossed proofreading by a certified proofreader

Sample-page tactile test

Re-emboss and final pass

Conclusion: the pipeline is the product

The captioning lawsuit cluster: streaming, university, and live-event suits 2023-2026

The captioning lawsuit cluster — streaming, university, and live-event suits 2023-2026

What the captioning docket reveals

01 · Methodology and dataset

02 · The streaming sub-docket

03 · The university sub-docket

04 · The live-event sub-docket

05 · Specialist firms behind the cluster

06 · The shift from existence to quality

07 · 2026-2028 outlook

The through line

Civic tech and digital benefits: how unemployment portals fail disabled claimants

Civic tech and digital benefits — how unemployment portals fail disabled claimants

What the benefits-portal audit revealed

01. Methodology and audit gates

02. The portal-by-portal ranking

03. CAPTCHA traps

04. Session timeouts that don't extend

05. PDF-only forms inside an HTML journey

06. File uploads with no screen-reader feedback

07. Error messages with no aria-live

08. DOJ Title II enforcement implications

09. The disabled-claimant journey is the worst-case civic-tech UX — and the most important to fix

The designer-to-engineer handoff fails accessibility: a study of 50 Figma files

The designer-to-engineer handoff fails accessibility a study of 50 Figma files

1. How we audited the 50 files

2. Focus-state design: the 60% gap

3. Alt-text annotations: mostly blank

Braille production pipelines in 2026:
software, hardware, and workflow

The designer-to-engineer handoff fails accessibility
a study of 50 Figma files

Every interactive component ships a `state=focus-visible` variant.