International Accessibility Law

The plain-language idea

The previous lesson covered the ADA, which is US-specific. A product with any international user base or market needs awareness beyond that one law. A few names come up repeatedly:

• The European Accessibility Act (EAA) — EU legislation setting accessibility requirements for a range of products and services sold in the EU, including many digital products. It's the EU's rough counterpart to the legal pressure the ADA creates in the US, though the legal mechanism (what it covers, how it's enforced) is genuinely different.
• EN 301 549 — the EU's detailed technical accessibility standard. Where the EAA sets the legal requirement, EN 301 549 is the technical document that spells out what "accessible" actually means at the implementation level — and it's heavily aligned with WCAG.
• Section 508 — a US standard, but a different one from the ADA. Section 508 specifically governs US federal agencies' own procurement and technology (an agency buying or building software has to meet Section 508), while the ADA applies more broadly to public accommodations generally, including many private companies. Don't conflate the two just because both are American.
• Other countries and regions increasingly have their own accessibility regulations too. This lesson won't invent details for markets not confidently known here, but the pattern below holds broadly: the direction is toward more countries adopting accessibility requirements, not fewer.

See it in a real thing: one WCAG conformance report, many jurisdictions

Imagine a product team ships to users in the US, the EU, and a handful of other markets, and asks: "which accessibility standard do we actually need to meet?" The honest, reusable answer is that nearly every major accessibility regulation worldwide converges on WCAG as the underlying technical standard, even though the legal mechanism differs by jurisdiction:

• In the US, WCAG AA is the de facto benchmark referenced in ADA-related litigation and settlements (previous lesson), and Section 508 (for federal procurement specifically) is itself closely aligned with WCAG.
• In the EU, EN 301 549 — the technical standard behind the EAA — is built heavily on WCAG's success criteria.
• Elsewhere, WCAG increasingly serves as the reference point other regulations point back to, even where the specific law and enforcement mechanism looks different.

What people usually miss

Watch out

• The legal mechanism differs by jurisdiction, but the technical target mostly doesn't. Who enforces the law, what triggers it, and what the consequences are changes country to country — but "conform to WCAG AA" remains the practical engineering answer almost everywhere.
• Section 508 and the ADA are not the same thing, despite both being American. Section 508 is specifically about federal agencies' own procurement and technology; the ADA (Title III, from the previous lesson) applies much more broadly, including to many private companies.
• EN 301 549 is not a competing standard to WCAG — it's built on it. Treating it as a separate thing to learn from scratch misses that its accessibility criteria are heavily aligned with WCAG's existing success criteria.
• "We only sell in the US" doesn't make international law irrelevant forever. Products expand into new markets, and accessibility requirements are a genuinely easier retrofit early than late — knowing this landscape exists is useful well before it becomes an active blocker.

Why this matters in interviews

"Is WCAG only a US requirement?" or "what happens if we expand to the EU?" are real questions that test whether a candidate understands accessibility law as a global pattern (many jurisdictions, one converging technical standard) rather than assuming the ADA is the whole story.