What's the Difference Between Section 508, WCAG, and the EAA?

Section 508 vs WCAG vs EAA represents the most common accessibility standards comparison facing organizations today. These three frameworks—the US federal procurement standard, the W3C's technical guidelines, and the European Union's comprehensive accessibility legislation—each serve different purposes but increasingly overlap in practice. Understanding their relationships, differences, and requirements is essential for organizations operating in global markets, serving government clients, or aiming for comprehensive accessibility compliance.

Key Takeaways

• WCAG is a technical standard, while Section 508 and the EAA are laws that reference WCAG for technical requirements
• Section 508 requires WCAG 2.0 Level AA (2017 refresh), while the EAA references WCAG 2.1 AA through EN 301 549
• Section 508 applies to US federal agencies and contractors; the EAA applies to private sector products and services sold in the EU
• Organizations serving both US and EU markets should adopt WCAG 2.1 AA as a minimum baseline
• The EAA has broader scope than Section 508, covering hardware, software, and services beyond web content

Understanding the Three Standards

Before comparing these frameworks, it's essential to understand what each one is and what it aims to accomplish.

Section 508: The US Federal Standard

Section 508 of the Rehabilitation Act requires US federal agencies to make their electronic and information technology (EIT) accessible to people with disabilities. Originally enacted in 1998, Section 508 was significantly updated in 2017 (the "Refresh") to incorporate WCAG 2.0.

Core Purpose: Ensure federal agencies and their contractors provide accessible technology

Legal Status: US federal law and regulation

Technical Basis: WCAG 2.0 Level AA (incorporated by reference)

Primary Scope: Federal agencies, federal contractors, recipients of federal funding

WCAG: The Technical Guidelines

The Web Content Accessibility Guidelines (WCAG) are developed by the World Wide Web Consortium (W3C) through the Web Accessibility Initiative (WAI). WCAG provides technical specifications for making web content accessible.

Core Purpose: Define technical accessibility requirements for web content

Legal Status: Not a law; a voluntary technical standard adopted by laws worldwide

Technical Basis: Self-contained technical specifications

Primary Scope: Web content (and increasingly, all digital content)

Current Versions:

• WCAG 2.0 (2008)
• WCAG 2.1 (2018)
• WCAG 2.2 (2023)

EAA: The European Comprehensive Law

The European Accessibility Act (EAA) is EU legislation requiring accessibility for a broad range of products and services. It references EN 301 549, which incorporates WCAG 2.1.

Core Purpose: Harmonize accessibility requirements across the EU single market

Legal Status: EU directive transposed into 27 member state laws

Technical Basis: EN 301 549 (which includes WCAG 2.1 AA)

Primary Scope: Private sector products and services across defined categories

Comparing Scope and Applicability

One of the most significant differences between Section 508, WCAG, and the EAA is who must comply and what is covered.

Section 508 Scope

Who Must Comply:

• Federal agencies (all executive, legislative, and judicial agencies)
• Federal contractors (when delivering EIT to federal agencies)
• Recipients of federal funding (depending on program requirements)
• State agencies receiving federal technology assistance

What Is Covered:

• Websites and web applications
• Software applications
• Electronic documents
• Multimedia content
• Hardware with embedded software
• Telecommunications products

What Is Not Covered:

• Private sector (except when contracting with federal government)
• State and local governments (unless receiving federal funding)
• General consumer products

WCAG Scope

Who Should Apply WCAG: WCAG itself has no mandatory applicability—it's a technical standard. However, various laws require WCAG compliance:

• Section 508 (WCAG 2.0 AA)
• ADA (courts reference WCAG)
• EAA (through EN 301 549, WCAG 2.1 AA)
• Various national laws worldwide

What WCAG Covers:

• Web content (primary focus)
• Web applications
• Non-web documents (WCAG2ICT adaptation)
• Mobile applications (WCAG2ICT adaptation)

WCAG Levels:

• Level A: Minimum accessibility
• Level AA: Standard compliance target
• Level AAA: Enhanced accessibility (rarely required by law)

EAA Scope

Who Must Comply:

• Private sector organizations selling covered products/services in the EU
• EU-based and non-EU companies serving EU consumers
• Manufacturers, importers, distributors, and service providers

Covered Products:

• Computers and operating systems
• Self-service terminals (ATMs, ticketing machines, check-in kiosks)
• Consumer telecommunications equipment
• Consumer audiovisual equipment
• E-readers

Covered Services:

• E-commerce services
• Banking services for consumers
• Electronic communications services
• Access to audiovisual media services
• Transport services (passenger information, booking, ticketing)
• E-books and dedicated software

Exemptions:

• Microenterprises (services only)
• Disproportionate burden (with documentation)
• Content posted before June 28, 2025 (limited)

Technical Requirements Comparison

The technical requirements of each standard vary, though they share significant overlap through WCAG.

WCAG Version Requirements

+-----------------------------------+---------------------------+--------------------+
|              Standard             |   WCAG Version Required   |   Level Required   |
+-----------------------------------+---------------------------+--------------------+
|            Section 508            |          WCAG 2.0         |         AA         |
+-----------------------------------+---------------------------+--------------------+
|        EAA (via EN 301 549)       |          WCAG 2.1         |         AA         |
+-----------------------------------+---------------------------+--------------------+
|   ADA (judicial interpretation)   |      WCAG 2.0 or 2.1      |    AA (typical)    |
+-----------------------------------+---------------------------+--------------------+

WCAG 2.0 vs WCAG 2.1

WCAG 2.1 builds on WCAG 2.0, adding 17 new success criteria addressing:

Mobile Accessibility:

• Orientation (1.3.4)
• Identify Input Purpose (1.3.5)
• Pointer Cancellation (2.5.2)
• Target Size (2.5.5 - AAA)
• Motion Actuation (2.5.4)

Cognitive Accessibility:

• Timeouts (2.2.6 - AAA)
• Identify Purpose (1.3.6 - AAA)

Low Vision:

• Reflow (1.4.10)
• Non-text Contrast (1.4.11)
• Text Spacing (1.4.12)
• Content on Hover or Focus (1.4.13)

Practical Implications: Organizations meeting only WCAG 2.0 AA (Section 508 baseline) may not meet EAA requirements. The gap primarily affects mobile and responsive design accessibility.

EN 301 549 Beyond WCAG

EN 301 549, referenced by the EAA, includes requirements beyond WCAG:

Hardware Requirements (Chapter 8):

• Physical dimensions and reach ranges
• Operability of mechanical controls
• Key identification and discernibility
• Visual indicators for audio output

Software Requirements (Chapter 11):

• Interoperability with assistive technology
• Platform accessibility services usage
• Closed functionality provisions
• Authoring tool accessibility

Documentation Requirements (Chapter 12):

• Accessible product documentation
• Accessible support services
• Relay service compatibility

Section 508 Specific Requirements

Section 508's 2017 Refresh incorporated WCAG 2.0 AA and added:

Functional Performance Criteria:

• Without vision
• With limited vision
• Without perception of color
• Without hearing
• With limited hearing
• Without speech
• With limited manipulation
• With limited reach and strength
• With limited language, cognitive, and learning abilities

Technical Standards Beyond Web:

• Hardware accessibility requirements
• Software application requirements
• Electronic content requirements
• Support documentation requirements

Comparison Matrix

High-Level Comparison

+-----------------------+-----------------------------------------+---------------------------+--------------------------------+
|         Aspect        |               Section 508               |          WCAG 2.1         |              EAA               |
+-----------------------+-----------------------------------------+---------------------------+--------------------------------+
|          Type         |              US federal law             |     Technical standard    |          EU directive          |
+-----------------------+-----------------------------------------+---------------------------+--------------------------------+
|    Geographic Scope   |              United States              |     Global (voluntary)    |         European Union         |
+-----------------------+-----------------------------------------+---------------------------+--------------------------------+
|      Sector Focus     |              Public sector              |            All            |   Private sector (primarily)   |
+-----------------------+-----------------------------------------+---------------------------+--------------------------------+
|      WCAG Version     |                  2.0 AA                 |            2.1            |    2.1 AA (via EN 301 549)     |
+-----------------------+-----------------------------------------+---------------------------+--------------------------------+
|   Hardware Coverage   |                   Yes                   |             No            |              Yes               |
+-----------------------+-----------------------------------------+---------------------------+--------------------------------+
|      Enforcement      |     Federal complaints, procurement     |   No direct enforcement   |    Member state authorities    |
+-----------------------+-----------------------------------------+---------------------------+--------------------------------+
|       Penalties       |   Contract remedies, agency liability   |            N/A            |       Fines, market bans       |
+-----------------------+-----------------------------------------+---------------------------+--------------------------------+

Content Coverage

+---------------------------+-----------------+-------------------+----------------------+
|        Content Type       |   Section 508   |      WCAG 2.1     |   EAA (EN 301 549)   |
+---------------------------+-----------------+-------------------+----------------------+
|        Web content        |       Yes       |        Yes        |         Yes          |
+---------------------------+-----------------+-------------------+----------------------+
|        Mobile apps        |       Yes       |   Yes (adapted)   |         Yes          |
+---------------------------+-----------------+-------------------+----------------------+
|      Native software      |       Yes       |   Yes (adapted)   |         Yes          |
+---------------------------+-----------------+-------------------+----------------------+
|   Documents (PDF, Word)   |       Yes       |   Yes (adapted)   |         Yes          |
+---------------------------+-----------------+-------------------+----------------------+
|        Video/audio        |       Yes       |        Yes        |         Yes          |
+---------------------------+-----------------+-------------------+----------------------+
|    Hardware interfaces    |       Yes       |         No        |         Yes          |
+---------------------------+-----------------+-------------------+----------------------+
|     Physical products     |     Limited     |         No        |         Yes          |
+---------------------------+-----------------+-------------------+----------------------+

Organizational Applicability

+----------------------------+------------------------------+-----------------------------+-----------------------------+
|     Organization Type      |         Section 508          |           WCAG 2.1          |             EAA             |
+----------------------------+------------------------------+-----------------------------+-----------------------------+
|    US federal agencies     |           Required           |          Referenced         |             N/A             |
+----------------------------+------------------------------+-----------------------------+-----------------------------+
|   US federal contractors   |   Required (for contracts)   |          Referenced         |             N/A             |
+----------------------------+------------------------------+-----------------------------+-----------------------------+
|     US private sector      |         Not required         |   Voluntary/ADA reference   |     Required (EU sales)     |
+----------------------------+------------------------------+-----------------------------+-----------------------------+
|      EU public sector      |             N/A              |        Required (WAD)       |   Additional requirements   |
+----------------------------+------------------------------+-----------------------------+-----------------------------+
|     EU private sector      |             N/A              |   Voluntary/EAA reference   |           Required          |
+----------------------------+------------------------------+-----------------------------+-----------------------------+
|     Global e-commerce      |          Voluntary           |        Best practice        |     Required (EU sales)     |
+----------------------------+------------------------------+-----------------------------+-----------------------------+

Practical Compliance Strategies

Organizations facing multiple standards need practical approaches to achieve comprehensive compliance.

Strategy 1: Meet the Highest Standard

For most organizations, adopting WCAG 2.1 AA (or WCAG 2.2 AA) as the baseline satisfies most requirements:

What WCAG 2.1 AA Achieves:

• Meets Section 508 requirements (exceeds WCAG 2.0 AA)
• Satisfies web content requirements of EN 301 549
• Provides foundation for EAA compliance
• Aligns with most global accessibility laws

What Additional Steps Are Needed:

For Section 508:

• Ensure functional performance criteria are met
• Document compliance in VPAT format
• Address hardware and software requirements (if applicable)

For EAA:

• Address EN 301 549 chapters beyond web content
• Ensure hardware accessibility (if applicable)
• Provide accessible documentation and support

Strategy 2: Create Unified Documentation

Develop documentation that addresses multiple standards:

Accessibility Conformance Reports:

• Use VPAT 2.4 format (includes WCAG, Section 508, and EN 301 549)
• Document conformance for all applicable standards
• Update when standards or products change

Policy Documentation:

• Create unified accessibility policy
• Reference all applicable standards
• Define compliance procedures

Strategy 3: Build for the Most Demanding Requirements

When developing new products or services, design for the most comprehensive requirements:

Development Checklist:

1. Follow WCAG 2.1 AA (or 2.2 AA) for all digital content
2. Implement EN 301 549 Chapter 11 for software applications
3. Apply hardware accessibility requirements where applicable
4. Create accessible documentation from the start
5. Plan for accessible support services

Strategy 4: Prioritize by Business Impact

When resources are limited, prioritize based on business exposure:

Priority Assessment Questions:

1. Do we have federal government customers? (Section 508)
2. Do we sell to EU consumers? (EAA)
3. What products/services have the highest user volume?
4. Where are we most vulnerable to complaints or litigation?

How the Standards Interact

Understanding how Section 508, WCAG, and the EAA interact helps organizations navigate the compliance landscape.

WCAG as the Common Foundation

WCAG serves as the technical foundation for both Section 508 and the EAA:

                    WCAG 2.1
                       |
          +------------+------------+
          |                         |
    Section 508              EN 301 549
    (WCAG 2.0 AA)            (WCAG 2.1 AA)
          |                         |
    US Federal              European Union
    Agencies &                  Markets
    Contractors

Organizations meeting WCAG 2.1 AA automatically satisfy the WCAG-based portions of both Section 508 and EN 301 549.

Mutual Recognition and Harmonization

There is no formal mutual recognition between Section 508 and the EAA. However:

Practical Equivalence:

• WCAG-based requirements are substantially similar
• Documentation formats (VPAT) address both
• Testing methodologies overlap significantly

Key Differences Requiring Separate Attention:

• EN 301 549 hardware requirements not in Section 508
• Section 508 functional performance criteria emphasis
• EN 301 549 documentation/support requirements

Future Convergence

Both standards are expected to evolve toward greater alignment:

Expected Updates:

• Section 508 may update to reference WCAG 2.1 or 2.2
• EN 301 549 will likely incorporate WCAG 2.2
• International harmonization efforts continue

Testing and Documentation Approaches

Testing for Multiple Standards

Automated Testing: Automated tools can identify approximately 30-40% of accessibility issues across all three standards. Common tools check for:

• Missing alternative text
• Color contrast failures
• Missing form labels
• Structural issues
• ARIA implementation problems

Manual Testing: Manual testing is essential for full conformance assessment:

• Keyboard navigation testing
• Screen reader testing (multiple screen readers)
• Cognitive accessibility assessment
• Complex interaction evaluation
• Content review

Assistive Technology Testing: EN 301 549 and Section 508 both emphasize interoperability with assistive technology:

• Screen readers (JAWS, NVDA, VoiceOver, TalkBack)
• Screen magnification (ZoomText, built-in magnifiers)
• Voice control (Dragon, Voice Control, Voice Access)
• Switch access (various switch interfaces)

Documentation Formats

VPAT 2.4 (Voluntary Product Accessibility Template): The VPAT 2.4 format includes columns for:

• WCAG 2.x (any version)
• Revised Section 508
• EN 301 549
• International edition (all three)

EU Accessibility Statement: EAA compliance may require:

• Formal accessibility statement
• Compliance status declaration
• Known limitations disclosure
• Feedback mechanism information

Section 508 Documentation: Federal agencies and contractors may need:

• Product accessibility documentation
• Testing methodology descriptions
• Conformance claims
• Exception justifications

Common Compliance Gaps

Organizations often encounter specific gaps when navigating between standards.

Gap 1: WCAG 2.0 to 2.1 Transition

Issue: Section 508 requires WCAG 2.0, but EAA requires WCAG 2.1.

Gap Areas:

• Mobile accessibility (orientation, touch targets)
• Reflow at 400% zoom
• Non-text contrast (graphics, icons)
• Text spacing adjustments

Resolution: Adopt WCAG 2.1 AA as baseline for all development.

Gap 2: Hardware Accessibility

Issue: EN 301 549 has extensive hardware requirements not covered by WCAG.

Affected Products:

• Self-service kiosks
• Payment terminals
• Interactive displays
• Consumer electronics

Resolution: Conduct specific EN 301 549 Chapter 8 assessments for hardware products.

Gap 3: Documentation Accessibility

Issue: EN 301 549 Chapter 12 requires accessible documentation and support.

Requirements:

• Product documentation in accessible formats
• Support services accessible to people with disabilities
• Information about accessibility features

Resolution: Create accessibility documentation program addressing all user touchpoints.

Gap 4: Closed Functionality

Issue: EN 301 549 Chapter 11 addresses software on closed systems (where users cannot install assistive technology).

Affected Systems:

• Kiosk applications
• Embedded software
• Locked-down terminals

Resolution: Implement built-in accessibility features for closed systems.

Frequently Asked Questions

If I meet Section 508, do I meet the EAA?

Partially. Section 508 requires WCAG 2.0 AA, while the EAA requires WCAG 2.1 AA (through EN 301 549). You would need to address the additional WCAG 2.1 success criteria, plus any applicable EN 301 549 requirements for hardware, software, and documentation that go beyond WCAG.

If I meet WCAG 2.1 AA, do I meet both Section 508 and EAA?

For web content, meeting WCAG 2.1 AA satisfies both Section 508 web requirements (since 2.1 AA exceeds 2.0 AA) and the web content portion of EN 301 549. However, both standards include requirements beyond WCAG for software, hardware, and documentation that require separate attention.

Which standard should I prioritize?

Prioritize based on your business context. If you primarily serve US federal agencies, focus on Section 508 with WCAG 2.0 AA minimum. If you sell to EU consumers, prioritize EN 301 549 with WCAG 2.1 AA. For global operations, adopt WCAG 2.1 AA (or 2.2 AA) as your baseline and address specific standard requirements as needed.

How do enforcement risks compare between Section 508 and EAA?

They differ significantly. Section 508 enforcement is primarily through procurement mechanisms and agency complaints, though violation can result in contract loss. EAA enforcement involves member state authorities with powers to impose fines and ban products from the market. Both carry significant business risk, but the EAA's market ban potential makes it particularly consequential for product manufacturers.

Is there a single certification that covers all three standards?

No formal certification exists for any of these standards. Compliance is demonstrated through conformance reports (VPATs), testing documentation, and self-attestation. Third-party audits can validate compliance but don't constitute certification.

What about WCAG 2.2? Do I need to meet that?

WCAG 2.2 is not yet required by Section 508 or EN 301 549. However, adopting WCAG 2.2 proactively positions you for future updates to both standards and provides enhanced accessibility. Several WCAG 2.2 success criteria address mobile and cognitive accessibility areas that represent common user pain points.

Related Resources

• WCAG 2.2 Compliance: What's New and How to Prepare
• ADA vs EAA: Complete Compliance Comparison Guide
• European Accessibility Act: Everything You Need to Know
• EN 301 549: Complete European Accessibility Guide
• Creating a VPAT: Complete Guide to Accessibility Conformance Reports

This article was crafted using a cyborg approach—human expertise enhanced by AI to deliver accurate, comprehensive accessibility guidance. Last updated January 2026.