L5 · Non-functional depth
L5Reference5 min read

Accessibility law: the European Accessibility Act

Accessibility became enforceable rather than aspirational for a large class of products in the EU. Enough to know whether it applies to what you ship, and what evidence you would need if asked.

Every year thousands of companies receive demand letters or lawsuits over inaccessible websites, and the pace keeps climbing. Legal teams now treat accessibility as a compliance line item, not a design preference, because courts and regulators have settled on a shared reference point for what "accessible" means. This guide walks through the major laws, who they cover, and why QA evidence of accessibility testing has become a real legal defense artifact rather than a nice-to-have.

ADA Title III and the US lawsuit trend

The Americans with Disabilities Act (ADA) predates the web, so it never defined digital accessibility directly. Courts filled that gap by ruling that websites count as "places of public accommodation" under Title III. That applies when a site is connected to physical goods or services, and it opened the door to tens of thousands of website accessibility lawsuits over the past decade.

Plaintiffs' firms typically scan a site with automated tools, find missing alt text or unlabeled form fields, and send a demand letter before filing. Most cases settle quietly for amounts in the tens of thousands of dollars, well below trial costs for either side. Retailers, restaurants, and healthcare sites are the most common targets because they combine high traffic with a public-facing checkout or booking flow.

Section 508 for federal agencies and contractors

Section 508 of the Rehabilitation Act applies to federal agencies and to companies that sell technology to the federal government. It requires that electronic and information technology be accessible to people with disabilities. It was refreshed in 2018 to align directly with WCAG 2.0 Level AA. Any vendor bidding on a federal contract now has to demonstrate conformance, often through a formal Voluntary Product Accessibility Template (VPAT).

Unlike ADA litigation, Section 508 enforcement runs through procurement and contract compliance rather than the courts. Losing a bid or a contract renewal over accessibility gaps is the practical consequence, and it can be just as costly as a lawsuit.

The European Accessibility Act and EN 301 549

The European Accessibility Act (EAA) became enforceable across EU member states in June 2025. It covers a wide range of digital products and services, including e-commerce, banking, transport ticketing, and consumer electronics. It applies to any company selling into the EU regardless of where it is headquartered, and national regulators can now issue fines and market withdrawal orders against non-compliant products.

The EAA points to EN 301 549 as its technical standard, and EN 301 549 itself incorporates WCAG 2.1 Level AA as the baseline for web content. The legal instruments differ by region, but ADA cases, Section 508 audits, and EAA enforcement all converge on the same underlying checklist.

Neither the ADA nor most EAA member-state laws name WCAG explicitly in every clause. Judges, settlement agreements, and regulators consistently cite it as the measurable bar for "accessible enough." The US Department of Justice has referenced WCAG 2.1 AA in consent decrees, and EU technical standards adopt it by name. That consistency is what makes WCAG conformance auditable: a reviewer can check specific success criteria instead of arguing over a subjective standard.

This matters for engineering teams because it turns a vague legal risk into a concrete test target. The question is no longer "is our site accessible enough." It is "which WCAG success criteria do our automated and manual tests cover, and where are the gaps." That reframing is exactly what tools like axe-core and other accessibility scanners are built to answer at scale.

Settlement costs are only part of the exposure. Consider a mid-sized e-commerce company that receives a demand letter alleging its checkout flow is unusable with a screen reader. Legal fees and settlement might run $30,000 to $75,000. The deeper cost is the emergency remediation sprint that follows.

Engineers get pulled off the roadmap for a rushed audit, and the public settlement draws attention from competitors and other plaintiffs' firms. Companies that already ran automated accessibility checks in CI, with dated reports showing test coverage over time, have settled faster and for less. They can show a documented good-faith effort rather than total neglect.

The risk categories worth tracking:

  • Litigation and settlement costs from ADA Title III claims, which rarely go to trial but rarely go away quietly either.
  • Lost or blocked government contracts tied to Section 508 non-conformance in a VPAT review.
  • EAA fines and market withdrawal in EU jurisdictions, which apply per product and per country.
  • Reputational damage when a lawsuit becomes public, especially for consumer brands.
  • Remediation cost multiplication, since fixing accessibility after a lawsuit is far more expensive than building it in during development.
axe-ci-check.js
// Example: fail CI if any WCAG 2.1 AA violations are found
const { AxePuppeteer } = require('@axe-core/puppeteer')

async function checkAccessibility(page) {
  const results = await new AxePuppeteer(page)
    .withTags(['wcag2a', 'wcag2aa', 'wcag21aa'])
    .analyze()

  if (results.violations.length > 0) {
    console.error(`Found ${results.violations.length} WCAG violations`)
    process.exit(1)
  }
}

A dated log of accessibility test runs, stored alongside your CI/CD pipeline history, does more than catch regressions before they ship. It becomes documentary evidence that your organization made a continuous, good-faith effort to meet WCAG criteria. That is precisely what courts and regulators look for when assessing intent and diligence.

Pair automated scans with periodic manual audits. Automated tools like axe catch roughly a third of WCAG failures, and manual review is still required for things like meaningful alt text or logical tab order.

Treat accessibility test results the same way you treat API contract test coverage. Version it, date it, and keep it retrievable, because six months from now it may be the artifact your legal team asks for first.

FAQ

Questions people ask

Does the ADA explicitly require WCAG compliance?

The ADA text does not name WCAG. DOJ consent decrees and most settlement agreements specify WCAG 2.1 Level AA as the remediation standard, making it the practical requirement.

Who has to comply with the European Accessibility Act?

Any company selling covered digital products or services, including e-commerce and banking, into EU member states, regardless of where the company is headquartered.

Can automated accessibility scans alone satisfy legal requirements?

No. Automated tools catch a meaningful share of issues but miss things like logical reading order or meaningful alt text. Manual review is still expected as part of a defensible testing process.

How is Section 508 enforced compared to the ADA?

Section 508 compliance is checked through federal procurement and VPAT reviews, while ADA claims are typically pursued through private litigation and settlement.