accessibility act

WCAG, ADA, Section 508, EAA, VPAT, CPACC… Which Accessibility Framework Actually Matters?

WCAG, ADA, Section 508, EAA, VPAT, CPACC… Which Accessibility Framework Actually Matters?

get in touch

Know where you stand. Know what to work on next.

Tell us what you’re working on and where you need support. Our accessibility specialists can help with audits, remediation, VPAT/ACR, accessible development, and ongoing compliance.

Free 30-minute consultation (opens in new tab)

Free 30-minute call: talk through where you stand, scope a project or get a quote.

Need technical answers now? Book the $100 one-hour consultation to walk through an audit, talk with a developer or review your site live.

Let’s find the barriers before your users do

Indicates a required field.


Your information is kept private and never shared with third parties.

If you’ve spent any time in digital accessibility, you’ve probably heard a confusing mix of acronyms:

  • WCAG
  • ADA
  • Section 508
  • EAA
  • VPAT
  • CPACC
  • Trusted Tester

For newcomers, it often feels like learning six different accessibility systems at once.

The reality is much simpler.

Most accessibility laws, procurement requirements, and compliance programs ultimately point back to one thing: WCAG.

Once you understand WCAG, the rest becomes a matter of understanding who a law applies to, how compliance is evaluated, and what documentation is required.

This accessibility framework guide breaks down what each one is, who it applies to, and how they fit together.

The Foundation: WCAG

The Web Content Accessibility Guidelines (WCAG) are the international technical standard for digital accessibility developed by the W3C’s Web Accessibility Initiative (see W3C’s WCAG overview; the current version is WCAG 2.2). WCAG provides the actual requirements that determine whether a website, application, or digital product is accessible.  

When people talk about accessibility issues such as:

  • Missing alternative text
  • Poor color contrast
  • Keyboard navigation problems
  • Unlabeled form fields
  • Improper heading structure
  • Screen reader compatibility

They’re talking about WCAG requirements.

WCAG is built around four core principles:

Perceivable

Users must be able to perceive content regardless of disability.

Examples:

  • Images need meaningful alt text.
  • Videos require captions.
  • Text must have sufficient color contrast.

Operable

Users must be able to operate the interface.

Examples:

  • Full keyboard accessibility.
  • Visible keyboard focus indicators.
  • No keyboard traps.

Understandable

Content and functionality must be easy to understand.

Examples:

  • Clear labels and instructions.
  • Consistent navigation.
  • Predictable interactions.

Robust

Content should work reliably with assistive technologies.

Examples:

  • Proper semantic HTML.
  • ARIA used correctly.
  • Compatibility with screen readers and future technologies.

These principles form the basis of nearly every accessibility standard used worldwide.  

ADA: The Accessibility Law Most U.S. Businesses Encounter

The Americans with Disabilities Act (ADA) is a civil rights law in the United States.

Unlike WCAG, the ADA does not provide technical requirements for websites.

Instead, it prohibits discrimination against people with disabilities.

This creates an important distinction:

  • ADA tells organizations they must provide equal access.
  • WCAG tells organizations how to provide equal access.

When courts evaluate whether a website creates barriers for people with disabilities, WCAG is commonly used as the benchmark for accessibility even though the ADA itself does not explicitly mention WCAG.

This is why most website accessibility lawsuits in the United States reference ADA obligations while remediation work is performed against WCAG success criteria. Our ADA website lawsuit statistics for 2026 show how often that happens.

There is one big exception. For state and local governments, the Justice Department’s ADA Title II web rule adopts WCAG 2.1 Level AA as the technical standard. After an April 2026 interim final rule extended the deadlines, public entities serving 50,000 or more people must comply by 26 April 2027, and smaller entities and special district governments by 26 April 2028. Private businesses under Title III still have no adopted technical standard.

Who Should Care About ADA?

  • E-commerce companies
  • Universities
  • Healthcare providers
  • Financial institutions
  • Service businesses
  • Public-facing websites

If your organization serves the public online in the United States, ADA accessibility compliance should be on your radar.

Section 508: Accessibility for Federal Government Work

Many people confuse ADA and Section 508, but they serve different purposes.

Section 508 applies specifically to federal agencies and organizations that provide technology to the U.S. federal government.

If your company:

  • Builds websites for federal agencies
  • Develops software used by government employees
  • Sells digital products through government procurement

Then Section 508 becomes relevant.

The important thing to understand is that the Revised Section 508 Standards, in force since January 2018, incorporate WCAG 2.0 Level AA by reference. Because WCAG 2.1 and 2.2 are backward compatible, building to WCAG 2.1 or 2.2 AA meets the 508 web requirements and also prepares you for newer rules that use them.

In practice, when a development team works toward Section 508 compliance, they are often implementing WCAG requirements.

Who Should Care About Section 508?

  • Government contractors
  • Software vendors selling to federal agencies
  • Technology procurement teams
  • Public sector development firms

For many private businesses, Section 508 may never apply.

For government contractors, it is essential.

EAA: Why U.S. Companies Are Suddenly Paying Attention to Europe

The European Accessibility Act (EAA) became enforceable on June 28, 2025, introducing accessibility obligations for many digital products and services offered within the European Union. Businesses outside Europe can also be affected if they serve EU customers.  

This surprises many organizations.

A company based in:

  • United States
  • Canada
  • India
  • Australia

may still need to consider EAA requirements if it sells products or services to customers in EU member states.

Examples include:

  • SaaS platforms
  • E-commerce stores
  • Banking services
  • Ticketing systems
  • Digital communication tools

Again, the pattern appears.

The EAA is legislation.

WCAG remains the technical framework organizations use to achieve compliance. The directive itself is Directive (EU) 2019/882, and its technical standard, EN 301 549, maps to WCAG 2.1 AA. Our European Accessibility Act guide covers scope and requirements, and the EAA compliance playbook covers deadlines and enforcement.  

Who Should Care About EAA?

  • SaaS companies
  • International e-commerce brands
  • Software vendors
  • Subscription platforms
  • Organizations serving EU customers

If your website has European users, EAA should be part of your accessibility strategy.

VPAT: Not a Law, But Still Extremely Important

One of the biggest misconceptions in accessibility is treating a VPAT like a certification.

A VPAT (Voluntary Product Accessibility Template) is not a law.

It is not a compliance standard.

It is not a certification.

A VPAT is simply a document used to communicate how well a product conforms to accessibility requirements.

Think of it as an accessibility report card.

Organizations use VPATs to document conformance against standards such as:

  • WCAG
  • Section 508
  • EN 301 549

Procurement teams frequently request VPATs before purchasing software or digital products. Section508.gov explains how buyers use VPATs, and our VPAT and ACR documentation service can prepare one for you.

Why VPATs Matter

Imagine you’re selling software to:

  • Government agencies
  • Universities
  • Large enterprises

Their procurement team may ask:

“Can you provide a VPAT?”

What they’re really asking is:

“Can you demonstrate how accessible your product is?”

Without a VPAT, many procurement processes become significantly more difficult.

CPACC and Trusted Tester: Certifications for Professionals

Another common misunderstanding is assuming websites need to become “CPACC certified” or “Trusted Tester approved.”

That is not how these programs work.

CPACC

The Certified Professional in Accessibility Core Competencies (CPACC) credential, offered by the International Association of Accessibility Professionals, validates foundational accessibility knowledge.

It demonstrates that a professional understands:

  • Disability types
  • Accessibility principles
  • Standards and regulations
  • Inclusive design concepts

Trusted Tester

The Trusted Tester program, run by the Department of Homeland Security, is a federal accessibility testing methodology used within the U.S. government.

Professionals can become certified in this testing process, demonstrating competency in evaluating accessibility against federal requirements.

Important Distinction

These certifications apply to people.

Not websites.

Not mobile apps.

Not software products.

A website cannot “pass CPACC.”

A developer or accessibility specialist can earn a CPACC certification.

Which WCAG Version Each Accessibility Framework Uses (2026)

Saying “we follow WCAG” is not quite enough, because each framework points to a specific version. Here is where things stand in October 2026.

FrameworkTechnical standardWho it applies toKey dates and status
ADA Title III (private businesses)No technical standard adopted in regulation; courts and settlements commonly use WCAG 2.1 AABusinesses open to the publicComplaint and lawsuit driven
ADA Title II (state and local government)WCAG 2.1 AAState and local governments26 April 2027 (population 50,000+); 26 April 2028 (smaller entities and special districts)
Section 504 (HHS funding recipients)WCAG 2.1 AAOrganizations that receive HHS funding11 May 2027 (15+ employees); 10 May 2028 (fewer than 15)
Section 508WCAG 2.0 AA (Revised 508 Standards)Federal agencies and the ICT they buyIn force since January 2018
European Accessibility ActEN 301 549 v3.2.1, which maps to WCAG 2.1 AACovered products and services sold in the EUEnforceable since 28 June 2025; v4.1.1 (WCAG 2.2) published September 2026, awaiting Official Journal citation
UK public sector (PSBAR)WCAG 2.2 AAUK public sector websites and appsMonitored against WCAG 2.2 since October 2024
India (RPwD Act, IS 17802, GIGW)Aligned with WCAG 2.1 AAGovernment bodies and regulated entitiesIS 17802 binding under the 2023 RPwD rules
VPAT / ACRReports against WCAG, Section 508 and/or EN 301 549Vendors selling to government and enterpriseRefresh with each major release

The pattern is easy to see. Older rules point to WCAG 2.0 or 2.1, and newer guidance is moving to WCAG 2.2. W3C designed the versions to be backward compatible: content that meets WCAG 2.2 also meets 2.1 and 2.0 (2.2 only drops 4.1.1 Parsing, which no longer matters for modern browsers). So one engineering target, WCAG 2.2 Level AA, covers every row in the table above.

The one moving piece is Europe. AccessibleEU reported in September 2026 that EN 301 549 v4.1.1 is published, but until the European Commission cites it in the Official Journal, v3.2.1 and WCAG 2.1 AA stay the legal reference for EAA presumption of conformity. Our EN 301 549 v4.1.1 guide lists the six WCAG 2.2 criteria to fix first.

Documentation follows the same logic. A VPAT or ACR should name the exact standard and version it was tested against, for example “WCAG 2.2 Level AA” or “EN 301 549 v3.2.1”, not just “WCAG compliant”. Buyers increasingly check that detail.

Why Everyone Eventually Ends Up Talking About WCAG

Let’s connect the dots.

FrameworkWhat It IsUses WCAG?
WCAGTechnical accessibility standardThe source
ADAU.S. civil rights lawYes, indirectly
Section 508U.S. federal procurement requirementYes
EAAEuropean accessibility lawYes
VPATAccessibility reporting documentUsually
CPACCProfessional certificationBased on accessibility knowledge
Trusted TesterProfessional testing certificationEvaluates against accessibility requirements

Notice the pattern?

Everything keeps leading back to WCAG.

That is why accessibility professionals spend most of their time learning:

  • WCAG success criteria
  • WCAG testing methods
  • WCAG remediation techniques
  • WCAG conformance requirements

The laws may differ.

The procurement processes may differ.

The documentation may differ.

But the technical work remains largely the same.

Where Businesses Should Focus

Many organizations waste months trying to understand every accessibility acronym before taking action.

A better approach is:

Step 1: Learn WCAG

Understand:

  • Keyboard accessibility
  • Color contrast
  • Forms and labels
  • Headings and landmarks
  • Screen reader compatibility
  • Focus management

Step 2: Determine Applicable Regulations

Ask:

  • Do we operate in the U.S.?
  • Do we serve EU customers?
  • Do we work with government agencies?
  • Do procurement teams require VPATs?

Step 3: Build Accessibility Into Development

Accessibility is far cheaper when integrated into:

  • Design
  • Development
  • Quality assurance
  • Content publishing

rather than treated as a legal emergency.

Final Thoughts

The accessibility industry often overwhelms people with terminology.

WCAG. ADA. Section 508. EAA. VPAT. CPACC. Trusted Tester.

They sound like separate worlds.

They are not.

WCAG is the technical foundation. ADA, Section 508, and the EAA are legal or regulatory frameworks that depend heavily on it. VPAT is the documentation used to communicate accessibility status. CPACC and Trusted Tester are credentials earned by professionals.  

If you focus on mastering WCAG, you’ve already learned the language that most accessibility laws and procurement requirements speak.

The challenge isn’t mastering seven frameworks.

It’s understanding one framework deeply and knowing where it applies.

Work With Us

Not sure which framework actually applies to you? Our 1-hour accessibility consultation gives you a clear, prioritized answer for $100 — or start with a full WCAG 2.2 accessibility audit if you’re ready to dig in.

Get a free accessibility needs assessment — no commitment required.

Get an Audit Benchmarked to Your Framework

Whichever framework applies to you, we run audits benchmarked to the right standard: ADA & Section 508 (USA), UK (Equality Act & PSBAR), Canada (AODA & ACA), or EU (European Accessibility Act).

Explore Country-Specific Accessibility Services

Need an audit mapped to a specific country’s framework? See our India, Australia, and UAE accessibility audit services.

Frequently Asked Questions

Is WCAG a law?

No.

WCAG (Web Content Accessibility Guidelines) is a technical standard, not legislation. However, many accessibility laws and regulations rely on WCAG as the benchmark for determining whether a website or application is accessible. This includes Section 508 in the United States and accessibility requirements associated with the European Accessibility Act (EAA).

Think of it this way:

  • WCAG = the rules
  • ADA/EAA/Section 508 = the laws that often point to those rules
What’s the difference between ADA compliance and WCAG compliance?

The ADA and WCAG serve different purposes.

The ADA is a civil rights law that requires equal access for people with disabilities.

WCAG provides the technical criteria used to achieve that access.

A company might be sued under the ADA, but the accessibility experts hired to evaluate the website will usually measure it against WCAG success criteria.

If my website passes WCAG, am I automatically ADA compliant?

Not necessarily.

WCAG conformance is strong evidence that you’re providing accessible experiences, but legal compliance involves more than technical requirements alone. Policies, support processes, procurement practices, and ongoing maintenance can also matter.

In practice, however, WCAG AA conformance is generally considered the strongest foundation for reducing ADA-related risk.

Does the European Accessibility Act (EAA) apply to companies outside Europe?

Potentially, yes.

Many organizations assume the EAA only affects European businesses. In reality, companies outside the EU may fall within scope if they provide digital products or services to EU customers.

That includes:

  • SaaS platforms
  • E-commerce stores
  • Banking services
  • Ticketing systems
  • Mobile applications

If you serve European customers, it’s worth reviewing your obligations under the EAA.

Is a VPAT the same as accessibility certification?

No.

This is one of the most common misconceptions.

A VPAT is a reporting template used to document accessibility conformance. It does not certify anything and does not make a product compliant by itself.

A VPAT simply communicates how a product performs against standards such as WCAG, Section 508, or EN 301 549.

Do I need a VPAT for ADA compliance?

No.

The ADA does not require a VPAT.

Many organizations create VPATs because procurement teams, universities, government agencies, and enterprise buyers often request them during purchasing decisions.

A VPAT can support accessibility efforts, but it is not a legal requirement under the ADA.

What’s the difference between a VPAT and an ACR?

People often use the terms interchangeably, but they’re technically different.

VPAT

  • The template

ACR (Accessibility Conformance Report)

  • The completed document generated from the VPAT

A simple analogy:

  • Tax form = VPAT
  • Completed tax return = ACR

Most buyers asking for a “VPAT” are actually looking for an ACR.

Is CPACC required for accessibility compliance?

No.

CPACC is a professional certification earned by individuals.

A website cannot become “CPACC certified.”

A developer, auditor, designer, consultant, or accessibility specialist can earn the CPACC credential to demonstrate accessibility knowledge and expertise.

The same principle applies to Trusted Tester certification.

These credentials apply to people—not websites.

Can automated accessibility tools make my website compliant?

No.

Automated scanners are useful, but they only detect a portion of accessibility issues.

They typically struggle with:

  • Meaningful alternative text
  • Keyboard usability
  • Screen reader experience
  • Focus management
  • Contextual form instructions
  • Cognitive accessibility issues

Manual testing remains essential for achieving reliable WCAG conformance.

Which accessibility framework should I learn first?

WCAG.

Without question.

Many newcomers try to learn:

  • ADA
  • Section 508
  • EAA
  • VPAT
  • EN 301 549
  • Trusted Tester
  • CPACC

all at once.

But almost every one of those frameworks ultimately traces back to WCAG.

If you understand:

  • Perceivable
  • Operable
  • Understandable
  • Robust (POUR)

and the WCAG success criteria, you’ll already understand the technical foundation behind most accessibility requirements worldwide.

Written by Shadab Saifi Published Last updated

Related Articles

View all