Need help? Email shivaji@ananyoo.com Contact

Accessibility

Section 508 vs WCAG vs ADA: Which Accessibility Standard Applies to Your Website?

Section 508 vs WCAG vs ADA explained in plain English: what each one is, who it applies to, which WCAG version it uses, and how one audit can cover all three.

A woman at her home office desk holds a handwritten sign reading Section 508 vs WCAG vs ADA, next to a monitor showing a website with an accessibility icon and a small US desk flag.

Section 508 vs WCAG vs ADA is one of the most common questions I get from new clients. A procurement officer asks for "508 compliance", a lawyer mentions the ADA, and the developer says the site already "meets WCAG". All three sound like different rules, and many site owners worry they need three separate audits. They do not.

I have been building and testing accessible websites since 2003, and our team audits sites for US government vendors, universities and businesses every week. You can see some of that work in our web accessibility case studies.

In this guide I explain what each one actually is, who it applies to, which version of WCAG it points to, and how one piece of work can cover all three. There is a simple decision check further down if you just want to know which one applies to your website.

On this pageJump to any part of this page12 sections

The short answer

Section 508 and the ADA are laws. WCAG is a technical standard. The laws say your website must be accessible, and WCAG is the checklist that defines what "accessible" means in practice. So it is not really Section 508 vs WCAG vs ADA. It is Section 508 or the ADA, measured with WCAG.

  • Section 508 covers US federal agencies and the technology they buy. It points to WCAG 2.0 Level AA.
  • The ADA covers state and local governments (Title II) and businesses open to the public (Title III). Title II points to WCAG 2.1 Level AA. Title III has no written web standard, but courts and settlements use WCAG 2.1 or 2.2 AA.
  • WCAG is written by the W3C. The current version is WCAG 2.2, and a site that meets 2.2 AA also meets the older versions in practice.

What is Section 508?

Section 508 is part of the Rehabilitation Act of 1973. It was expanded in 1998 to cover electronic and information technology, and the standards were refreshed in January 2017, with compliance required from January 2018. The refreshed Section 508 standards from the US Access Board adopt WCAG 2.0 Level A and AA for web content, documents and software.

Section 508 applies directly to federal agencies. They must make their own websites, apps and documents accessible, and they must buy accessible products. That second part is why it matters to so many private companies. If you sell software, a SaaS platform, e-learning or a website build to a federal agency, the agency will ask you to prove your product meets Section 508. Many state governments and universities also copy the Section 508 rules into their own buying policies.

The proof is usually a VPAT, a standard form that becomes your Accessibility Conformance Report (ACR). It lists every Section 508 and WCAG requirement and says whether your product supports it. Our VPAT and ACR service prepares this from a real audit, not from guesswork.

This is the real Section 508 vs ADA difference for most companies. Section 508 is about selling to the government. The ADA is about serving the public.

What is the ADA?

The Americans with Disabilities Act of 1990 is a civil rights law. It bans discrimination against people with disabilities, and the Department of Justice and US courts have long said that this includes websites and apps. Two parts of the ADA matter for websites:

  • Title II covers state and local governments: cities, counties, public schools, public universities, courts, libraries and transit. In 2024 the Department of Justice published a rule that names WCAG 2.1 Level AA. After the April 2026 extension, large public bodies have until 26 April 2027 and smaller ones until 26 April 2028. Our ADA Title II website compliance page explains this in detail.
  • Title III covers businesses and organisations open to the public: online stores, hotels, banks, hospitals, private schools, nonprofits and many more. There is no written web rule with a deadline, but thousands of lawsuits and demand letters are filed every year, and they almost always measure the site against WCAG 2.1 or 2.2 AA.

If you have already received a letter, read our guide on what to do after an ADA demand letter.

A woman thinks at her desk, looking at a monitor with sticky notes labelled 508, WCAG and ADA, with a printed VPAT document on the desk.

What is WCAG?

The Web Content Accessibility Guidelines are published by the World Wide Web Consortium (W3C), the same group that writes the HTML and CSS standards. WCAG is not a law. It is a set of testable success criteria organised under four principles: content must be perceivable, operable, understandable and robust.

Each criterion has a level. Level A is the bare minimum, Level AA is the level every law asks for, and Level AAA is the highest, used for specific content rather than whole sites. There are three versions in use today:

  • WCAG 2.0 (2008): the version Section 508 points to.
  • WCAG 2.1 (2018): added mobile, low vision and cognitive criteria. This is the version in the ADA Title II rule and the European Accessibility Act.
  • WCAG 2.2 (2023): added nine more criteria, such as visible focus, target size and accessible login. In October 2025 it was also approved as the international standard ISO/IEC 40500:2025. Our guide to WCAG 2.2 explained covers every new criterion with code fixes.

Each version builds on the one before, so meeting WCAG 2.2 AA means you meet 2.1 AA and 2.0 AA as well in practice. That is the heart of the WCAG vs ADA question: WCAG tells you how to make a site accessible, and the ADA tells you that you must.

Section 508 vs WCAG vs ADA at a glance

WCAG is not a law, so it is not a column of its own here. It is the measuring stick that both laws use. Here is how the two laws compare:

TopicSection 508ADA
What it isUS federal lawUS civil rights law
Who it coversFederal agencies and what they buyPublic bodies (Title II) and businesses open to the public (Title III)
WCAG versionWCAG 2.0 AATitle II: 2.1 AA. Title III: courts use 2.1 or 2.2 AA
Also coversSoftware, PDFs, hardware, help documentsServices, buildings, digital content
Enforced byAgencies, through complaints and buyingThe DOJ and private lawsuits
Main riskLost federal contractsLawsuits and legal costs

The key difference between Section 508 vs ADA is who it applies to. The key difference between WCAG vs ADA is that one is a technical checklist and the other is the law that makes you follow it.

Which one applies to your website?

Most organisations fall into one or more of these groups. To settle the Section 508 vs WCAG vs ADA question for your own site, ask yourself these questions in order:

Section 508 vs WCAG vs ADA flowchart in a notebook: Federal? leads to Section 508, Public body? leads to ADA Title II, Business? leads to ADA Title III, and all of them point to WCAG.
  • Are you a federal agency, or do you sell software or services to one? Section 508 applies. Expect to provide a VPAT or ACR, and aim for WCAG 2.0 AA as a minimum.
  • Are you a state or local government, public school or public university? ADA Title II applies, with WCAG 2.1 AA and a fixed deadline.
  • Are you a business, nonprofit, private college or healthcare provider serving the public? ADA Title III applies. Use WCAG 2.1 AA as a minimum and WCAG 2.2 AA as the safer target.
  • Do you receive federal funding, for example in healthcare or education? Section 504 of the Rehabilitation Act may also apply. The 2024 Department of Health and Human Services rule under Section 504 names WCAG 2.1 AA for recipients of its funding.
  • Do you also sell into other countries? The European Accessibility Act, Canada's AODA and India's accessibility rules are all built on WCAG too. See our guides to the European Accessibility Act and digital accessibility law in India.

It is common to fall into more than one group. A software company might sell to a federal agency (Section 508), run a public website for customers (ADA Title III) and have buyers in Europe (EAA). Because all of these rest on WCAG, one well planned audit covers them all.

Why WCAG 2.2 AA is the safest target

If you are still unsure which law applies, the practical answer is the same: build and test to WCAG 2.2 Level AA. Here is why:

  • It covers Section 508 (WCAG 2.0 AA) and ADA Title II (WCAG 2.1 AA), because each WCAG version includes the one before.
  • It is the version most buyers now write into contracts and RFPs, and the one recent lawsuits refer to.
  • It is now an ISO standard, which matters for public tenders in many countries.
  • You avoid doing the work twice when the laws are updated to the newer version.

One thing to keep in mind: Section 508 goes beyond websites. It also covers software, PDFs, help documents and support services. If you sell to federal agencies, your audit should include those too, not just the marketing site. Our article on accessible PDF forms covers the document side.

A woman tests a website on her laptop showing an accessibility icon, with a WCAG 2.2 AA checklist on a clipboard beside her.

Common mistakes when choosing a standard

  • Asking for "508 compliance" on a private business site. Section 508 does not apply to most private websites. What protects you from lawsuits is meeting WCAG under the ADA.
  • Targeting WCAG 2.0 because Section 508 says so. That is the floor, not the goal. Many federal buyers already ask for WCAG 2.1 or 2.2.
  • Filling in a VPAT without testing. A VPAT that says "Supports" everywhere, with no audit behind it, is easy for a buyer's accessibility team to see through.
  • Relying on an automated scan. Scanners catch only part of WCAG. Section 508, the ADA and WCAG all expect the site to work for real people using keyboards and screen readers. Read why in why most city websites pass a scan and still fail.
  • Installing an overlay widget. A toolbar on top of the site does not make the code meet WCAG, and it does not stop lawsuits. See accessibility overlays: pros and cons explained.

Three real-world examples

Here is how the Section 508 vs ADA question plays out for three typical clients we see:

A SaaS company selling to a federal agency

A US software company wins a pilot with a federal department. Before the contract is signed, the agency asks for a VPAT. That is Section 508. The company also has a public marketing site and a customer portal used by thousands of people, which brings ADA Title III into play. The right plan is one audit of the product and the website against WCAG 2.2 AA, a Section 508 VPAT for the agency, and fixes to the shared design system so both are covered at once.

A county government website

A county with a population of 120,000 runs its website, online payments and meeting agendas on a content management system. Section 508 does not apply, because it is not a federal body. ADA Title II does, with WCAG 2.1 AA and a deadline of 26 April 2027. The work focuses on templates, online forms, PDFs and video captions, and we recommend testing to WCAG 2.2 AA so the site is ready when the rule is updated.

An online store

A mid-sized online store receives a demand letter claiming its checkout cannot be used with a screen reader. There is no Section 508 angle and no fixed deadline, but ADA Title III applies and the letter measures the site against WCAG. The fastest safe route is a manual audit of the key journeys (search, product, cart, checkout, account), quick fixes to the theme, and a written accessibility statement.

In all three cases the answer to WCAG vs ADA is the same: the law decides whether you must act, and WCAG decides what "done" looks like.

How to meet all three with one audit

You do not need to pick a side in Section 508 vs WCAG vs ADA. This is the process we follow for clients who need all three covered together:

  • Agree the target. Usually WCAG 2.2 AA, with a Section 508 mapping if you sell to federal agencies.
  • Pick a sample. One page of every template, every form and every key user journey, plus the PDFs and documents people actually download.
  • Test by hand. Keyboard only, NVDA and JAWS on Windows, VoiceOver on Mac and iPhone, TalkBack on Android, zoom and colour contrast checks.
  • Fix in the right place. Most issues come from the theme, components and forms, so one fix often clears hundreds of pages.
  • Document it. An audit report, a VPAT or ACR for buyers, and a public accessibility statement.

How Ananyoo can help

Whatever your answer to Section 508 vs WCAG vs ADA, the work underneath is the same. I am Shivaji Mitra, a DHS Trusted Tester, which is the federal testing method for Section 508, and our audit team is IAAP certified. We audit websites, apps and documents against WCAG 2.2 AA and Section 508, fix the problems in your code, and give you the reports your buyers and legal team ask for.

Start with a website accessibility audit, then accessibility remediation, and a VPAT or ACR if you sell to government or large companies. If you run WordPress, our Ariade accessible themes and free WordPress accessibility plugins are built to WCAG 2.2 AA from the start. Send your website address through our contact page, and you will get a written reply within one working day.

Frequently asked questions

Is Section 508 the same as WCAG?

No. Section 508 is a US federal law. Its web requirements are based on WCAG 2.0 Level A and AA, so a site that meets WCAG 2.0 AA meets most of Section 508 for web content.

Does Section 508 apply to private companies?

Only when they sell technology or services to federal agencies, or when a state or university contract asks for it. Most private websites fall under the ADA instead.

What WCAG level does the ADA require?

ADA Title II names WCAG 2.1 Level AA. Title III has no written standard, but courts and settlements use WCAG 2.1 or 2.2 AA.

Do I need separate audits for Section 508, WCAG and the ADA?

No. One manual audit against WCAG 2.2 AA, with a Section 508 mapping where needed, covers all three.

Which is stricter in the Section 508 vs WCAG vs ADA comparison?

WCAG 2.2 AA has the most detailed technical requirements for websites. Section 508 is wider in scope, because it also covers software, documents and hardware. The ADA carries the biggest legal risk for businesses, because anyone can bring a lawsuit.

Does WCAG apply outside the United States?

Yes. WCAG is an international standard. The European Accessibility Act, Canada's AODA, the UK public sector rules and India's government guidelines all point to WCAG 2.0 or 2.1 AA, and many are moving to 2.2. If your website serves customers in several countries, testing to WCAG 2.2 AA once covers most of these rules together.

What is the difference between a VPAT and an ACR?

A VPAT is the blank template. Once it is filled in for your product, it becomes your Accessibility Conformance Report (ACR).

Shivaji Mitra Avatar

About the author

Leave a Reply

Your email address will not be published. Required fields are marked *


Accessibility settings

Saved on this device. Change them any time.

Read our accessibility statement