Accessibility compliance can feel like a maze of acronyms. ADA, WCAG, Section 508… What do they all mean? Which ones apply to your organization? And how do you avoid falling out of compliance?
In this guide, we’ll break down the three pillars of digital accessibility—ADA, WCAG, and Section 508—and explain how they connect, where they differ, and what it means for your agency in 2025 and beyond.
The ADA: America’s Broad Disability Rights Law
The Americans with Disabilities Act (ADA) is a civil rights law enacted in 1990. It prohibits discrimination against individuals with disabilities in all areas of public life.
Title II of the ADA
Title II applies specifically to state and local governments. It requires that public entities provide equal access to programs, services, and activities.
For a long time, the ADA didn’t clearly define how websites and digital content should meet that requirement. That changed in April 2024, when the U.S. Department of Justice issued a final rule establishing WCAG 2.1 Level AA as the standard for digital accessibility under the ADA.
WCAG: The Technical Standard
WCAG stands for the Web Content Accessibility Guidelines, created by the W3C. It’s a technical set of standards that help developers create accessible websites, apps, and documents.
WCAG Versions and Levels
- WCAG 2.0 – Published 2008
- WCAG 2.1 – Published 2018 (adds mobile and cognitive criteria)
- WCAG 2.2 – Published 2023 (new, not yet widely adopted)
- Level A – Minimum
- Level AA – Legal standard for most regulations
- Level AAA – Highest bar (not typically required)
The 2024 DOJ rule sets WCAG 2.1 Level AA as the baseline for compliance.
Section 508: Federal-Specific Rules
Section 508 is part of the Rehabilitation Act of 1973. It requires federal agencies to make electronic and information technology accessible to people with disabilities.
Originally limited to federal systems, it’s become a model for broader accessibility efforts—including many state and local governments.
What Section 508 Covers
- Websites
- PDFs and other digital documents
- Software and applications
- Multimedia (videos, webinars, etc.)
Section 508 already uses WCAG 2.1 AA as its standard. So in many ways, the DOJ rule for Title II under ADA brings state/local governments in line with federal expectations.
Key Differences
| Law/Standard | Who It Applies To | What It Requires | Enforcement |
|---|---|---|---|
| ADA (Title II) | State & local governments | WCAG 2.1 AA (as of 2024) | DOJ, lawsuits |
| Section 508 | Federal agencies | WCAG 2.1 AA | DOJ, internal audits |
| WCAG | Everyone (voluntary) | Technical accessibility | Not enforceable directly |
What This Means for You
If you work for a state or local agency, you now have a clear legal mandate to:
- Audit your websites and PDFs
- Remediate issues using WCAG 2.1 AA
- Maintain accessibility going forward
Deadlines:
- April 2026 for jurisdictions with 50K+ residents
- April 2027 for smaller agencies
Final Thoughts
Don’t let the alphabet soup overwhelm you. ADA gives you the mandate. WCAG gives you the rules. Section 508 shows you how it’s already being done.
Need help making sense of what this means for your site or documents?
