The 2025 Guide to ADA & Section 508:

What Changed, Who’s Affected, and How to Get Compliant

Digital accessibility just moved from “best practice” to “must-do.” In the last couple of years, the U.S. Department of Justice (DOJ) finalized clear web and mobile app rules for state and local governments under the ADA, the federal government tightened Section 508 implementation, and civil penalties for ADA violations climbed with inflation. Here’s what that means for municipalities, not-for-profits/publicly funded orgs, and private-sector businesses—with deadlines, enforcement, and practical tools to start fixing issues now.

What’s new at a glance

• ADA Title II (state & local governments): DOJ’s final rule requires conformance with WCAG 2.1 Level AA for public-facing web content and mobile apps. Compliance dates depend on entity size:

  • April 24, 2026: states/localities serving ≥50,000 people.

  • April 24, 2027: <50,000 population and special district governments. Federal Register+1

• Section 508 (federal agencies & federally procured ICT): Still aligned to WCAG 2.0 AA (2017 “Refresh”) but OMB’s M-24-08 memo tightened agency accountability (programs, procurement, monitoring, and public accessibility statements). (Vendors/partners feel this through RFPs and contract deliverables.) Section508.gov+1

• ADA civil penalties (Title III—businesses open to the public): Inflation-adjusted maximums for DOJ civil penalties are now $118,225 (first violation) and $236,451 (subsequent). (Courts can also order injunctive relief and attorneys’ fees; states may add remedies.)

• For everyone: DOJ reiterates that websites and apps must be accessible under the ADA, even though there’s no Title III tech standard yet. The DOJ’s web guidance remains the enforcement north star for businesses. ADA.gov

Municipalities (cities, counties, school districts)

What’s required

• Meet WCAG 2.1 AA for web content and mobile apps (with limited exceptions, e.g., some archives and third-party content you don’t control). Federal Register

Deadlines

• April 24, 2026 (≥50k population)

• April 24, 2027 (<50k & special districts) Federal Register

Enforcement & risk

• DOJ can enforce Title II via investigations and settlement agreements; courts typically order injunctive relief (fix it on a timeline) and may award damages/fees consistent with Section 504 remedies. Plan now—DOJ even published a “first steps” planning guide. Legal Information Institute+1

Action checklist

• Inventory public-facing sites, apps, PDFs, video, forms; triage high-traffic and high-risk content.

• Publish an accessibility statement with a feedback channel (OMB M-24-08’s model is useful even beyond federal). The White House

Not-for-profits & publicly funded organizations

When ADA and 508 hit you

• If you provide public services (e.g., transit info, health, education) or receive government funding, you’re often covered by the ADA and Section 504 obligations; your federal grants and contracts may also bind you to 508-aligned requirements on deliverables and ICT you produce or maintain. Section508.gov

What to expect in procurements

• Federal partners increasingly require WCAG-conformant sites/docs, VPAT/ACR documentation, and periodic accessibility reporting—driven by M-24-08 and Section508.gov guidance. The White House+1

Enforcement & risk

• Complaints can lead to required remediation, monitoring, and potential loss of funding; if your services are “open to the public,” Title III-style private litigation risk increases, too. ADA.gov

Private-sector businesses (Title III “public accommodations”)

Obligation

• DOJ guidance makes clear the ADA applies to business websites and apps; many courts look to WCAG (2.0/2.1) AA as the de-facto bar in settlements. ADA.gov

Penalties & exposure

• DOJ civil penalties up to $118,225 / $236,451, plus injunctive relief; private lawsuits can add attorneys’ fees and state-law damages (e.g., California’s Unruh).

Bottom line

• Even without a Title III tech rule, aligning with WCAG 2.1 AA is the safest course—and typically the expectation in enforcement and settlements. ADA.gov

Section 508: where federal agencies – and their vendors – must land

• Standard: Revised 508 aligns to WCAG 2.0 AA plus other ICT requirements; it’s been in force since Jan 18, 2018 (with safe harbor for unchanged legacy ICT). Section508.gov+1

• Programmatic lift (M-24-08): Agencies must run mature accessibility programs (policy, procurement, testing, public statements, monitoring)—raising the bar on contractor deliverables. The White House

Practical timelines to consider (2025–2027)

• Now (2025): Audit your web/app/PDF posture against WCAG 2.1 AA; tag and remediate high-impact PDFs; set up a repeatable testing workflow.

• By Apr 24, 2026/2027 (Title II entities): Achieve conformance or have documented exceptions and alternative access where allowed. Federal Register

• Ongoing (all orgs): Bake accessibility into procurement, authoring, design/dev, and QA; publish & maintain an accessibility statement and feedback loop. The White House

Tools to help you evaluate (free / low-cost)

Website & app testing

• WAVE (WebAIM) – quick, visual checks for WCAG issues (browser extension & web). WAVE

• axe DevTools (Deque) – free browser extension powered by axe-core (the engine behind many audits). Chrome Web Store

• Accessibility Insights (Microsoft) – guided checks and fast automated scans (Web & Windows). accessibilityinsights.io

• ANDI (SSA) – bookmarklet from the Social Security Administration for focused inspections. Social Security

• Lighthouse (Chrome/Edge DevTools) – built-in automated audits (use alongside manual testing). Chrome for Developers

• Screen readers for spot-checks – NVDA (Windows, free) and VoiceOver (macOS/iOS built-in). NV Access

Documents & PDFs

• Microsoft Accessibility Checker – in Word/PowerPoint/Excel/Outlook while you work. Microsoft Support

• Adobe Acrobat Pro “Prepare for Accessibility” / Preflight – structure tags, reading order, PAC handoff. Adobe Help Center

• PAC 2024 (PDF/UA Foundation) – the free gold-standard checker for PDF/UA & WCAG machine-testable items. PDF Accessibility Checker

• Colour Contrast Analyser (TPGi) – free desktop app for precise contrast testing (useful across web, slides, PDFs). TPGi — a Vispero company

Tip: automated tools catch approximately 30–40% of issues. Pair them with manual keyboard testing, basic screen reader checks, and structured content practices (headings, labels, alt text).

Your quick-start remediation plan

1. Baseline audit: Run WAVE/axe/Insights across key templates and high-traffic pages; pull a representative PDF sample into Acrobat + PAC. PDF Accessibility Checker+3WAVE+3Chrome Web Store+3
2. Prioritize: Fix blockers first—keyboard traps, missing form labels, focus order, alt text, captions for media, and color contrast. TPGi — a Vispero company
3. Harden the process:
   
   

   • Add accessibility acceptance criteria to tickets.

   • Require VPAT/ACR in procurements (and verify). Section508.gov

   • Keep Microsoft Accessibility Checker “on” for authors. Microsoft Support

4. Publish an accessibility statement with contact & remediation SLA; route feedback to accountable owners. The White House

This article has been generated by AI and peer-reviewed.