Accessibility Laws & Regulations — Section 508, ADA & EN 301 549 Guide

Accessibility laws and regulations — including the ADA, Section 508, EN 301 549, the EU Web Accessibility Directive, and others — establish legal requirements for digital Accessibility, with WCAG as the common technical standard referenced by most legislation worldwide.

What You'll Learn

By the end of this guide, you'll understand the major Accessibility laws in the United States (ADA, Section 508), Europe (EN 301 549, EU Web Accessibility Directive), Canada (AODA), the UK (Equality Act 2010), and Australia (DDA). You'll learn how these laws reference WCAG, who they apply to, what the penalties for non-Compliance are, and how to build a Compliance Strategy for your organization.

Why Accessibility Laws Matter

In 2024, ADA website Accessibility lawsuits exceeded 4,000 in the US alone. European regulators fined organizations over 2 million euros for non-Compliance with the EU Web Accessibility Directive. Beyond legal risk, Accessibility Compliance is increasingly a procurement requirement — governments and enterprises will not buy software that fails Accessibility standards. At DodaTech, Durga Antivirus Pro maintains WCAG AA Compliance for its enterprise dashboard, and Doda Browser includes built-in Accessibility features that exceed legal minimums.

Accessibility Law Decision Tree

flowchart TD
  A[Your organization] --> B{Which country/region?}
  B -->|USA| C[ADA Title III]
  B -->|USA Federal| D[Section 508]
  B -->|European Union| E[EN 301 549]
  B -->|Canada| F[AODA / ACA]
  B -->|UK| G[Equality Act 2010]
  B -->|Australia| H[DDA]
  C --> I[WCAG AA standard]
  D --> I
  E --> I
  F --> I
  G --> I
  H --> I
  I --> J[<a href="/cyber-security/compliance-risk-management/">Compliance</a> <a href="/design-patterns/strategy/">Strategy</a>]
  J --> K[Audit]
  J --> L[Remediate]
  J --> M[Document]
  J --> N[Monitor]

{{< callout type="info" icon="sparkles" >}} Prerequisites: Understanding of WCAG principles. This guide covers legal frameworks, not technical implementation. For technical WCAG details, see the WCAG Compliance guide. {{< /callout >}}

United States Laws

Americans with Disabilities Act (ADA) Title III

The ADA prohibits discrimination on the basis of disability in places of public accommodation. Courts have increasingly interpreted "places of public accommodation" to include websites. While the ADA does not explicitly mention WCAG, courts have used WCAG 2.1 AA as the de facto standard.

Who it applies to: Businesses open to the public (retail, hospitality, banking, healthcare, entertainment).

Penalties: First violation fines up to $75,000; second violation up to $150,000. Plaintiff attorneys' fees and settlement costs average $50,000+ per case.

What to do: Ensure your public-facing website meets WCAG 2.2 Level AA. Maintain an Accessibility statement and conformance documentation.

Section 508 of the Rehabilitation Act

Section 508 requires federal agencies to procure, develop, maintain, and use electronic and information technology that is accessible. In 2018, Section 508 was updated to incorporate WCAG 2.0 Level AA.

Who it applies to: Federal agencies, organizations receiving federal funding, contractors selling to the government.

Penalties: Contract cancellation, debarment from future contracts, complaints filed with the agency's Section 508 coordinator.

What to do: If you sell to the US government, your product must comply with Section 508. Provide a current VPAT/ACR (Voluntary Product Accessibility Template) as part of your procurement response.

European Laws

EN 301 549

EN 301 549 is the European standard for ICT Accessibility. Version 3.2.1 references WCAG 2.1 Level AA as the baseline. The European Accessibility Act (EAA), effective June 2025, mandates EN 301 549 Compliance for products and services sold in the EU.

Who it applies to: All products and services sold in the EU — hardware, software, websites, mobile apps, ebooks, and e-commerce.

Penalties: Varies by member State. Fines up to 5% of annual turnover in some countries.

What to do: Ensure your product meets EN 301 549 / WCAG 2.1 AA. Document conformance with a EU declaration of conformity.

EU Web Accessibility Directive

The EU Web Accessibility Directive (Directive 2016/2102) requires public sector websites and mobile apps to be accessible. It references EN 301 549.

Who it applies to: Public sector bodies in EU member states — government agencies, municipalities, public hospitals, universities.

Penalties: Member states set their own penalties. Includes fines, Compliance orders, and public naming.

What to do: Public sector organizations must publish an Accessibility statement, provide a feedback mechanism, and monitor Compliance regularly.

Canadian Laws

Accessibility for Ontarians with Disabilities Act (AODA)

AODA requires organizations in Ontario to meet Accessibility standards, including WCAG 2.0 Level AA for websites. Similar legislation exists in other provinces.

Who it applies to: Organizations in Ontario with 50+ employees (private sector), all public sector organizations.

Deadlines: Private sector with 50+ employees must comply by 2021 (extended for some requirements). New requirements under the Accessible Canada Act (ACA) continue to roll out.

Penalties: Fines up to $100,000 per day for directors and officers.

UK Law

Equality Act 2010

The Equality Act 2010 prohibits discrimination against people with disabilities. While it does not explicitly mention WCAG, the UK government recommends WCAG 2.2 AA as the standard for Compliance.

Who it applies to: All organizations providing goods, facilities, or services to the public in the UK — including websites and mobile apps.

Penalties: Unlimited fines in civil cases. Claims are brought to county court.

What to do: Follow the UK Government's Accessibility requirements, which mandate WCAG 2.2 AA for public sector websites.

Australian Law

Disability Discrimination Act 1992 (DDA)

The DDA makes it unlawful to discriminate against a person on the grounds of disability. The Australian Human Rights Commission has published World Wide Web Access Guidelines that recommend WCAG 2.1 AA.

Who it applies to: All organizations operating in Australia, including private sector.

Penalties: Unlimited damages in federal court. The Commission can issue enforceable undertakings.

Global Compliance Comparison

Building a Compliance Strategy

Follow this five-step Process to achieve and maintain legal Compliance:

// compliance-tracker.js — Track accessibility compliance status
const complianceTracker = {
  requirements: [
    { law: 'ADA Title III', wcag: '2.2 AA', status: 'not-started' },
    { law: 'EN 301 549', wcag: '2.1 AA', status: 'in-progress' },
    { law: 'AODA', wcag: '2.0 AA', status: 'not-started' },
  ],

  getPriority() {
    return this.requirements
      .filter(r => r.status !== 'compliant')
      .sort((a, b) => {
        const urgency = { 'ADA Title III': 1, 'EN 301 549': 2, 'AODA': 3 };
        return (urgency[a.law] || 99) - (urgency[b.law] || 99);
      });
  },

  updateStatus(law, status) {
    const req = this.requirements.find(r => r.law === law);
    if (req) req.status = status;
  },

  generateReport() {
    return {
      compliant: this.requirements.filter(r => r.status === 'compliant').length,
      inProgress: this.requirements.filter(r => r.status === 'in-progress').length,
      notStarted: this.requirements.filter(r => r.status === 'not-started').length,
      details: this.requirements
    };
  }
};

Expected output:

{
  "compliant": 0,
  "inProgress": 1,
  "notStarted": 2,
  "details": [
    { "law": "ADA Title III", "wcag": "2.2 AA", "status": "not-started" },
    { "law": "AODA", "wcag": "2.0 AA", "status": "not-started" },
    { "law": "EN 301 549", "wcag": "2.1 AA", "status": "in-progress" }
  ]
}

Common Mistakes

1. Assuming WCAG Compliance Equals Legal Compliance

WCAG Compliance does not guarantee legal Compliance. Courts interpret Accessibility requirements case by case. Documentation and good-faith efforts matter.

2. Ignoring Procurement Requirements

Many Accessibility lawsuits target organizations that buy inaccessible software. If you purchase an inaccessible tool for your website, you share liability.

3. No Accessibility Statement

The EU Web Accessibility Directive and many other laws require a published Accessibility statement. Without one, you are non-compliant regardless of your technical Accessibility.

4. Treating Accessibility as a One-Time Fix

Accessibility is not a project — it is a practice. New content, features, and redesigns can introduce violations. Continuous monitoring is essential.

5. Ignoring Mobile Apps

The European Accessibility Act and many other laws explicitly cover mobile apps. A website that is accessible but an app that is not still leaves you exposed.

6. No VPAT/ACR Documentation

Enterprise customers and governments require VPATs as part of procurement. Without a current VPAT, you lose contracts.

7. Relying on a Single Country's Compliance

If you sell globally, you must comply with multiple overlapping laws. The safest approach is WCAG 2.2 AA globally, as it meets or exceeds most regional requirements.

Practice Questions

1. What WCAG version and level does Section 508 reference?

WCAG 2.0 Level AA, as updated in the 2018 refresh of Section 508.

2. What is the difference between ADA Title III and Section 508?

ADA Title III applies to private sector businesses open to the public. Section 508 applies to federal agencies and their contractors.

3. When does the European Accessibility Act take effect?

June 2025, with some provisions phased through 2030.

4. What is a VPAT/ACR and why is it important?

A VPAT (Voluntary Product Accessibility Template) or ACR (Accessibility Conformance Report) documents a product's conformance with Accessibility standards. It is required for government and enterprise procurement.

5. Challenge: Research the Accessibility laws applicable to your organization. Create a Compliance matrix listing each law, its WCAG standard, who it applies to, penalties, and your organization's current status.

Real-World Task

Download a VPAT template from the ITIC website. Fill it out for a product you use or build. Identify which sections are compliant, partially compliant, or non-compliant. Create a remediation plan for non-compliant sections.

FAQ

Try It Yourself

Create a Compliance checklist for your organization:

# Accessibility Compliance Checklist

## US Compliance
- [ ] ADA Title III — website meets WCAG 2.2 AA
- [ ] ADA Title III — VPAT completed and current
- [ ] ADA Title III — Accessibility statement published
- [ ] Section 508 — VPAT available for procurement

## EU Compliance
- [ ] EN 301 549 — product meets WCAG 2.1 AA
- [ ] EAA — declaration of conformity prepared

## Canada Compliance
- [ ] AODA — website meets WCAG 2.0 AA
- [ ] AODA — Accessibility statement published

## Ongoing
- [ ] Quarterly automated Accessibility scans
- [ ] Annual manual Accessibility audit
- [ ] User testing with people with disabilities

What's Next