Skip to content
Tutorials Center
My learning

Topics

Lesson 33 of 38 ยท Legal, Process and Culture

Accessibility Laws and Standards

An overview of web accessibility law and standards: WCAG versions and levels, ADA, Section 508, the European Accessibility Act, EN 301 549, AODA and the UK Equality Act.

Accessibility is first a matter of people being able to use what you build. It is also a legal topic in many countries, and legal pressure is one reason organizations fund the work. This lesson maps the landscape: the technical standards that define "accessible", and the laws that point at them.

This lesson is an educational overview, not legal advice. Laws change, apply differently by sector and size, and are interpreted by courts and regulators. Ask a qualified lawyer about your specific obligations.

The standards

WCAG

The Web Content Accessibility Guidelines, published by the W3C, are the technical backbone almost everywhere. Versions are backward compatible: each newer version adds success criteria.

Version Notes
WCAG 2.0 (2008) Still referenced in older laws. ISO standard ISO/IEC 40500.
WCAG 2.1 (2018) Added mobile, low vision and cognitive criteria (orientation, reflow, text spacing, target input).
WCAG 2.2 (2023) Added focus appearance and not obscured, dragging alternatives, target size (minimum), consistent help, redundant entry, accessible authentication.
WCAG 3.0 Long-term working draft; not a replacement yet.

Three conformance levels: A (basic, must), AA (the usual legal target), AAA (best, not required for whole sites since not all content can meet it). When a rule says "WCAG 2.1 AA", you must meet all A and AA criteria of that version.

Other standards

  • EN 301 549: the European standard for accessibility of ICT products and services. Its web chapter incorporates WCAG 2.1 AA (with updates following later versions).
  • ATAG: Authoring Tool Accessibility Guidelines, for tools that create content (CMS, editors).
  • UAAG: for browsers and user agents.
  • WAI-ARIA and ARIA Authoring Practices Guide: how to build custom widgets.
  • PDF/UA (ISO 14289) and EPUB Accessibility: documents and e-books.

The laws, by region

United States

  • Americans with Disabilities Act (ADA), Title II (state and local government) and Title III (places of public accommodation). Courts have applied it to websites; a large number of web accessibility lawsuits are filed every year. The Department of Justice rule for state and local governments points to WCAG 2.1 AA, with compliance dates depending on the size of the entity.
  • Section 508 of the Rehabilitation Act: federal agencies and their contractors must buy and build accessible ICT, using WCAG 2.0 AA via the Revised 508 Standards.
  • Section 504, 21st Century Communications and Video Accessibility Act (CVAA), and state laws add more.

European Union

  • Web Accessibility Directive (2016/2102): public sector websites and apps must meet EN 301 549 (WCAG 2.1 AA) and publish an accessibility statement.
  • European Accessibility Act (EAA, Directive 2019/882): from 28 June 2025, many private-sector products and services sold in the EU must be accessible, including e-commerce, banking services, e-books, passenger transport services, and electronic communications. There are limited exemptions for microenterprises providing services and for disproportionate burden.

United Kingdom

  • Equality Act 2010: service providers must make reasonable adjustments.
  • Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018: WCAG 2.2 AA is now the expected target for public sector bodies, plus an accessibility statement.

Canada

  • Accessible Canada Act (federal sector), AODA in Ontario (WCAG 2.0 AA for larger organizations), and provincial laws elsewhere.

Elsewhere

Australia (Disability Discrimination Act), India (Rights of Persons with Disabilities Act and GIGW guidelines), Israel (IS 5568, based on WCAG), Japan (JIS X 8341-3) and Brazil (LBI) all reference WCAG or close equivalents. The pattern repeats worldwide: WCAG 2.1 or 2.2 level AA is the practical target.

What "compliance" looks like in practice

Laws rarely specify a checklist beyond pointing to a standard. Organizations typically:

  1. Pick a target (usually WCAG 2.2 AA).
  2. Audit current products (automated plus manual; see the audit checklist).
  3. Fix, prioritizing by impact and traffic.
  4. Publish an accessibility statement (see statements and VPAT).
  5. Monitor continuously and provide a feedback channel.

An overlay widget that claims to "make your site compliant with one line of code" is not a legal shield. Accessibility advocates and several court cases have shown overlays do not fix underlying code, and they can interfere with assistive technology. Fix the source.

Mapping a requirement

Map a WCAG failure to a fix

Procurement and contracts

Buyers increasingly demand accessibility in contracts: a VPAT or Accessibility Conformance Report from vendors, remediation timelines, and the right to terminate for failure. If you build for clients, put the target (for example WCAG 2.2 AA) and the test method into the specification so everyone agrees on what "done" means.

flowchart LR
  A["Law or contract"] --> B["Points to a standard"]
  B --> C["WCAG 2.x level AA"]
  C --> D["Audit"]
  D --> E["Fix"]
  E --> F["Statement and monitoring"]

The law sets the duty; the standard defines the test.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Which WCAG conformance level is the usual legal target?

    Most laws and regulations reference level AA, which includes all level A criteria.
  2. 2. What did WCAG 2.2 add?

    2.2 added several criteria such as 2.5.8 Target Size (Minimum), 2.4.11 Focus Not Obscured and 3.3.8 Accessible Authentication.
  3. 3. Which law applies from June 2025 to many private-sector services in the EU?

    The EAA extends accessibility requirements to private-sector products and services such as e-commerce and banking.
  4. 4. Does an accessibility overlay widget guarantee legal compliance?

    Overlays do not repair the underlying code and are not accepted as proof of conformance.

Summary

  • WCAG (2.0, 2.1, 2.2) with levels A, AA and AAA is the core technical standard; AA is the usual target.
  • Key laws: ADA and Section 508 (US), EU Web Accessibility Directive and European Accessibility Act, UK Equality Act and public sector regulations, AODA (Ontario) and others.
  • Compliance means audit, fix, publish a statement and keep monitoring.
  • This is not legal advice: confirm duties for your sector and region.

Next: Accessibility Statements and VPATs