Section 508 vs. ADA Compliance: What's the Difference?
Section 508 only applies if you're a federal agency or sell to one, tested against an older accessibility standard. The ADA applies to basically everyone else, and it's testing against a newer, stricter one. You can pass one and still get sued under the other.
Here's how that actually plays out. A checkout that only works with a swipe gesture, no tap option, can pass a Section 508 check without anyone blinking. That standard was written in 2008 and never asks about swipe gestures. Put that same checkout in front of an ADA-standard test and it fails immediately, because the newer standard added a rule for exactly that.
Section 508 covers federal agencies and their contractors, tested against WCAG 2.0 AA, enforced through procurement. The ADA covers most public-facing organizations, Title II for state and local governments, Title III for public-facing businesses. Title II now formally requires WCAG 2.1 AA under the DOJ Final rule, and courts treat 2.1 AA as the practical bar for Title III too, even without it being written into the law directly.
Why organizations confuse the two
Both laws reference WCAG. Both involve web accessibility. Both increasingly ask for a VPAT. It's an easy conflation, and it's wrong in a way that matters: the two laws come from different statutes, cover different organizations, and get enforced through completely different mechanisms.
The comparison
| ADA | Section 508 | |
| Applies to | Public-facing businesses under Title III and state or local governments under Title II | Federal agencies and federal contractors only |
| Technical standard | Title II: WCAG 2.1 Level AA under the DOJ Final Rule.Title III: WCAG 2.1 Level AA is widely treated as the practical benchmark, although no formal technical regulation has been established. | WCAG 2.0 Level AA, incorporated into the Revised Section 508 Standards |
| Scope tested | Public-facing web content and digital services | The specific digital product, service or deliverable included in a federal contract |
| Enforcement | DOJ enforcement action or private lawsuit | Federal procurement or contract compliance review |
| Cost of non-compliance | Legal fees, remediation costs, settlements and potential court orders | Lost bid, rejected procurement submission or terminated contract |
| Current deadline | Public entities serving populations of 50,000 or more: April 26, 2027.Smaller public entities: April 26, 2028. | Ongoing compliance requirement with no single fixed deadline |
| Document often requested | Increasingly requested as evidence of accessibility remediation and compliance efforts | VPAT, commonly required during procurement evaluation |
Most public-facing private businesses fall under ADA Title III, while state and local government entities fall under Title II.
Why the standard gap matters more than the audience split
WCAG 2.0 doesn't cover pointer gestures. WCAG 2.1 does. A mobile checkout using only swipe gestures, no tap alternative, may satisfy 2.0 AA and fail 2.1's Pointer Gestures criterion outright. A Section 508 review can pass that checkout clean, while an ADA-standard test fails it on the first click.
| New in WCAG 2.1 | Why It Matters |
| Pointer Gestures (2.5.1) | Swipe- or drag-only controls fail unless a simple tap or click alternative is available. |
| Reflow (1.4.10) | Content must remain usable at mobile widths without requiring horizontal scrolling. |
| Orientation (1.3.4) | Content must not be locked to portrait or landscape orientation unless essential. |
| Input Purpose (1.3.5) | Form fields must be coded correctly so browsers and assistive technologies can identify their purpose and support autofill. |
| Status Messages (4.1.3) | Screen readers must be notified about important changes or updates without requiring a page reload. |
| Text Spacing (1.4.12) | Content must remain readable and functional when users adjust text and paragraph spacing. |
| Motion Actuation (2.5.4) | No action should rely only on device movement, such as shaking or tilting. |
Real-world examples
A SaaS company selling to the U.S. Department of Education answers to both: Section 508 for the contracted product, ADA for its own marketing site. A local restaurant answers to ADA Title III only. A county government site answers to ADA Title II. A federal agency's own portal answers to Section 508 only.
Common misconceptions
An automated scan passing doesn't mean compliance, it catches a fraction of WCAG criteria. The two laws are not the same law with two names. Private businesses carry the larger share of active litigation, not just government sites. The ADA has no size exemption. WCAG 2.0 isn't enough for a Title II or increasingly Title III standard.
Which standard should you build for?
Build to WCAG 2.1 AA regardless of which law technically governs a site, it's the higher bar and satisfies 2.0 automatically. Run a free scan to see where a site sits against it today.
Decision matrix (table)
| Organization Type | Applicable Requirement |
| Federal agency or contractor | Section 508 |
| State or city government | ADA Title II |
| Retail store or SaaS startup | ADA Title III |
| Software vendor serving a federal agency | ADA and Section 508 |
The document both sides often ask for
Federal procurement processes commonly require a VPAT to document accessibility conformance during technology evaluation. Many organizations also use one during ADA-related audits or settlement discussions.
What Section 508 actually is
A 1998 amendment to the Rehabilitation Act: federal agencies and the vendors selling technology to them. Section 504 of the same Act is separate, covering federally funded entities that aren't contractors, universities and hospitals are the common example.
What the ADA actually is
A 1990 civil rights law. Robles v. Domino's Pizza, LLC, 913 F.3d 898 (9th Cir. 2019), held that the ADA applied to Domino's website and mobile app because they were closely connected to its physical restaurants, a significant milestone in website accessibility litigation under Title III.
Enforcement is where the risk diverges
Section 508 has no private lawsuit pipeline. The ADA runs through federal court: according to Seyfarth Shaw's 2026 report, 3,117 federal website accessibility lawsuits were filed in 2025, up 27 percent from 2,452 in 2024.
Quick checklist
- Selling to a federal agency, or responding to a federal procurement requirement? Section 508 likely applies.
- State or local government entity? Title II applies.
- Public-facing private business? Title III generally applies.
- Either way, build to WCAG 2.1 AA and keep a VPAT ready.
FAQs
No. They're separate laws with separate audiences and separate technical standards, Section 508 for federal agencies and contractors under WCAG 2.0 AA, the ADA for most everyone else, trending toward WCAG 2.1 AA.
No, they're independent. An organization with no federal contracts has no Section 508 obligation at all, regardless of its ADA status.
Not automatically. Section 508 incorporates WCAG 2.0 AA. ADA Title II now references WCAG 2.1 AA, which covers more ground, including mobile-specific criteria like pointer gestures.
The ADA: Title III for a public-facing business, Title II for government.
Only if acting as a federal contractor. Otherwise it's not exposed to 508 at all.
Yes. DOJ extended it a year: April 26, 2027 for larger entities, April 26, 2028 for smaller ones.
The key difference is that Section 508 mainly applies to federal organizations, while the ADA covers a wider range of websites. Following WCAG 2.1 AA is usually the safest way to address the main differences between both.
