Section 508 vs ADA: Which Accessibility Requirements Apply?

Comparing ADA vs Section 508 starts with a simple rule. Use Section 508 when you are a US federal agency or providing technology to one. Use the ADA when you operate a place of public accommodation or provide services to the public in the US. This article explains the scope, technical standards, enforcement mechanisms, and practical steps for organisations and vendors.

Quick answer: which law applies to you?

• If you are a federal agency or a system the agency buys or runs, Section 508 applies.
• If you are a private business or a state or local government that provides goods or services to the public, the ADA usually applies.
• If you sell to federal agencies, your product may need to meet Section 508 requirements through procurement clauses even if you are not a federal agency.

What the ADA covers

Scope and who is covered

The Americans with Disabilities Act is a federal civil-rights law. Title II covers state and local government services. Title III covers places of public accommodation and commercial facilities. Courts and enforcement actions have extended ADA obligations to many websites and apps used by the public.

Technical standards and guidance

The ADA itself does not contain a single technical standard for web or app content. Federal guidance from the Department of Justice and many court settlements point to the Web Content Accessibility Guidelines as the practical benchmark. In practice, organisations are often asked to meet WCAG at Level AA, commonly using WCAG 2.1 AA as the reference today.

Enforcement and remedies

The ADA is enforced by the Department of Justice and by private lawsuits. Remedies can include injunctive relief, accessibility fixes, and in some cases monetary damages and legal costs. Litigation outcomes vary by court and facts.

What Section 508 covers

Scope and who is covered

Section 508 is part of the US Rehabilitation Act. It applies to federal executive branch agencies and to information and communication technology those agencies procure, develop, maintain or use. The rule protects federal employees and members of the public who need information or services from federal agencies.

Technical standards and guidance

Section 508 was updated to align with the Web Content Accessibility Guidelines. The update references WCAG success criteria for most web content. Section 508 also includes provisions specific to ICT, such as hardware, software and documentation, that go beyond web pages alone.

Enforcement and remedies

Enforcement is primarily administrative. Individuals can raise accessibility complaints with the federal agency responsible for the technology, or pursue remedies within federal processes tied to procurement and employment. The US Access Board issues standards and technical guidance used to judge compliance.

Key differences at a glance

Topic	ADA	Section 508
Primary target	Private businesses, state and local government services	Federal executive branch agencies and agency ICT
Technical baseline	No statutory standard. Courts and settlements often use WCAG 2.0/2.1 Level AA	References WCAG success criteria and adds ICT-specific requirements
Enforcement	DOJ and private lawsuits	Administrative complaints, procurement remedies, Access Board guidance
Defences	Undue burden and fundamental alteration	Undue burden and limited national-security or procurement exceptions

How WCAG fits both laws

The Web Content Accessibility Guidelines are not a law. They are the technical standard most often referenced when courts or agencies decide whether content is accessible. WCAG 2.1 Level AA is the practical baseline many organisations choose because it covers mobile and modern web patterns and is widely accepted in settlements and procurement.

For federal procurement, vendors commonly supply a Voluntary Product Accessibility Template, or VPAT, to report conformance to Section 508 and to WCAG criteria. A truthful VPAT with test evidence speeds procurement and reduces risk of later findings.

Which law applies: a short decision checklist

1. Are you a federal agency? If yes, Section 508 applies.
2. Do you provide goods or services to the public in the US? If yes, consider ADA obligations.
3. Do you sell products to federal agencies? If yes, expect contract clauses that reference Section 508 and WCAG conformity.
4. If you are unsure, use WCAG 2.1 Level AA as the working standard until you get legal advice.

Procurement checklist for purchasers and vendors

• Request a current VPAT or accessibility conformance report that maps to WCAG 2.1 AA and to Section 508 where relevant.
• Require a remediation plan and timelines for any non-conformances discovered during evaluation.
• Ask for evidence of testing with assistive technologies such as NVDA, VoiceOver and common screen readers.
• Include acceptance criteria in the contract and retain the right to withhold payment until agreed accessibility fixes are complete.
• Plan for ongoing monitoring because software updates can introduce regressions.

Common mistakes and how to avoid them

• Relying only on automated accessibility tools. Automated checks catch 20 to 40 percent of issues. Manual testing with assistive technology is essential.
• Assuming Section 508 only covers websites. It covers a wider set of ICT including software, hardware, video and documentation.
• Using a generic VPAT without test evidence. A VPAT alone is not proof of accessibility.
• Ignoring mobile accessibility. WCAG 2.1 added criteria that address mobile interfaces and touch targets.

Real-world scenarios

Scenario 1: Federal agency public website

The agency must meet Section 508. Use the Section 508 standards and conform to the referenced WCAG success criteria. Include VPATs from vendors and run manual tests with assistive technology.

Scenario 2: Online retailer open to the public

The retailer should follow the ADA. Courts and settlements commonly require WCAG 2.1 AA conformance. Accessibility statements, accessible checkout and accessible PDFs are frequent focus areas.

Scenario 3: Commercial product sold to a federal agency

The buying agency will expect proof the product meets Section 508. The vendor should provide a VPAT, testing results and a plan to fix any gaps found during procurement testing.

Practical next steps

• If you are responsible for compliance, run an audit that combines automated checks with manual testing and user testing with disabled people.
• Set WCAG 2.1 Level AA as your baseline unless a contract or agency rule requires a different level.
• Document accessibility in procurement, and require vendors to supply up-to-date VPATs and remediation commitments.
• Train product, procurement and legal teams so they understand the different rules that apply to federal and non-federal contexts.

Section 508 and the ADA serve different audiences but often push towards the same technical outcome: content that works with assistive technology and is perceivable, operable, understandable and robust. For most organisations a clear, documented programme based on WCAG 2.1 Level AA will cover both laws in practice and reduce legal and operational risk.