Section 508 vs WCAG: Understanding the Relationship and Differences

Section 508federal accessibilitygovernment compliance508 complianceBrowseCheck
·11 min read

Organizations navigating accessibility compliance often encounter both Section 508 and WCAG (Web Content Accessibility Guidelines). Understanding the relationship between these standards—and their differences—is crucial for efficient compliance strategy. Since the 2017 Section 508 Refresh, the relationship has become clearer: Section 508 incorporates WCAG 2.0 Level AA by reference for web content while extending requirements to software, hardware, and documentation. This guide clarifies what's the same, what's different, and how to navigate both standards effectively.

The Fundamental Relationship

WCAG 2.0: International web accessibility standard published by W3C (World Wide Web Consortium) in December 2008 Section 508: U.S. federal law requiring accessible electronic and information technology, updated in 2017

Key relationship: Section 508 (Revised 2017) incorporates WCAG 2.0 Level AA by reference for web and digital content.

This means:

  • If your web content meets WCAG 2.0 Level AA, you've met the web content portion of Section 508
  • Section 508 adds requirements beyond WCAG for software, hardware, and documentation
  • WCAG is an international standard; Section 508 is U.S. federal law

Historical Context

Before 2017: Different Standards

Original Section 508 (2001): Had its own technical standards that diverged from WCAG

  • Separate requirements for web (§1194.22)
  • Often confusing which standard to follow
  • Created compliance challenges for international organizations

WCAG 1.0 and 2.0 (1999, 2008): Developed as international consensus standards

  • More comprehensive than original Section 508
  • Widely adopted globally
  • Better aligned with modern web technologies

The problem: Organizations had to meet potentially conflicting standards, creating inefficiency and confusion.

After 2017: Harmonization

The 2017 Section 508 Refresh solved this by:

  • Incorporating WCAG 2.0 Level AA for web content
  • Aligning with international standards (EN 301 549 in Europe also uses WCAG)
  • Maintaining additional requirements for non-web technologies
  • Creating single compliance path for web content

What's Covered: Scope Comparison

WCAG 2.0 Scope

Web content: HTML pages, CSS, JavaScript, AJAX Web applications: Browser-based applications Mobile web: Responsive designs, mobile browsers Documents: When accessed via web browsers PDF and office documents: Guidance exists but not explicitly in WCAG Native software: Not explicitly covered (though WCAG principles apply) Hardware: Not covered

WCAG 2.0 focuses primarily on web and digital content presented through browsers.

Section 508 Scope

Everything WCAG covers, PLUS: Software: Desktop applications, mobile apps (iOS, Android) Hardware: Kiosks, copiers, phones, computers Documents: Explicit requirements for PDFs, Word, Excel, PowerPoint Multimedia: Video and audio content Support documentation: Help systems, user guides Customer support: Technical support accessibility

Section 508 is comprehensive across all federal electronic and information technology.

Technical Requirements Comparison

Web Content: WCAG 2.0 Level AA

For web content, Section 508 requires conformance to WCAG 2.0 Level AA success criteria:

All 38 WCAG 2.0 Level AA criteria apply:

  • 25 Level A criteria
  • 13 Level AA criteria

Four WCAG 2.0 criteria exempted for non-web documents/software:

  • 1.2.4 Captions (Live) - AA
  • 1.2.5 Audio Description (Prerecorded) - AA
  • 2.4.1 Bypass Blocks - A
  • 2.4.2 Page Titled - A

These exemptions exist because non-web software has different architectural patterns. Section 508 provides alternative requirements addressing the same user needs.

Software: Section 508 Goes Beyond WCAG

Platform Accessibility Services (Section 502.2):

  • Must use platform accessibility APIs (MSAA, UIA, UIAccessibility, Accessibility Framework)
  • Must expose roles, states, properties to assistive technology
  • Not explicitly required by WCAG

Accessibility Services (Section 502.3):

  • Must not interfere with platform accessibility features
  • Screen readers, magnifiers, high contrast must work
  • WCAG doesn't specify this level of integration

Hardware: Section 508 Unique Requirements

407 - Operable Parts: Tactilely discernible controls 408 - Display Screens: Minimum character height (3/16 inch) 409 - Status Indicators: Audio or tactile alternatives to visual indicators 412 - Two-Way Voice Communication: Real-time text (RTT) for phones 413 - Closed Functionality: Kiosks where assistive tech can't attach

WCAG has no hardware requirements—it's a web content standard.

Functional Performance Criteria: Section 508 Unique

Section 302: Seven (later nine) functional performance criteria ensuring technology is usable:

  • 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

WCAG principles (Perceivable, Operable, Understandable, Robust) are similar but not identical. FPC provides outcomes-based requirements when technical standards don't apply.

Conformance Models

WCAG 2.0 Conformance Levels

Level A: Minimum accessibility (25 criteria)

  • Essential requirements
  • Without Level A, some users completely blocked

Level AA: Recommended accessibility (13 additional, 38 total)

  • Addresses common barriers
  • Most laws and policies reference Level AA
  • Section 508 requires Level AA for web

Level AAA: Enhanced accessibility (23 additional, 61 total)

  • Not recommended for entire sites
  • May not be achievable for all content
  • Optional under Section 508

Section 508 Conformance

Section 508 doesn't use A/AA/AAA levels. Instead:

Web content: Must meet WCAG 2.0 Level AA Software: Must meet Section 502 requirements Hardware: Must meet Sections 407-415 requirements Documents: Must meet Section 501 requirements Functional Performance: Must meet Section 302 criteria

Conformance is binary: Either compliant or non-compliant for each applicable section.

Testing Differences

WCAG 2.0 Testing

Focus: Web content accessibility Methods:

  • Automated scanning (axe, WAVE, Lighthouse)
  • Manual keyboard and visual testing
  • Screen reader testing (NVDA, JAWS, VoiceOver)

Success criteria: 61 total (38 for Level AA)

Section 508 Testing

Focus: Comprehensive technology accessibility Methods:

  • Everything in WCAG testing for web content
  • Platform accessibility API testing for software
  • Hardware evaluation for physical devices
  • PDF tagging and structure testing
  • Caption and audio description review
  • Support documentation review

Requirements: WCAG 2.0 Level AA plus software, hardware, documents, multimedia, and support requirements

Tool Compatibility

Most modern accessibility testing tools support both:

axe DevTools: Tests against WCAG 2.0 (covers Section 508 web requirements) WAVE: Labels violations as both WCAG and Section 508 BrowseCheck: Monitors WCAG 2.0 Level AA compliance (Section 508 web portion) Section 508 specific: Accessibility Insights, Trusted Tester, PEAT

Documentation Requirements

WCAG 2.0

Conformance claim recommended but not required:

  • Conformance level (A, AA, AAA)
  • Scope (what's covered)
  • WCAG version
  • Accessibility support baseline (browsers, assistive tech)

No mandatory documentation format.

Section 508

Accessibility Conformance Report (ACR/VPAT) often required:

  • Section 508 uses VPAT format
  • Required for federal procurement
  • Must document: Supports, Partially Supports, Does Not Support, Not Applicable
  • Must explain non-conformance

Support documentation must:

  • Describe accessibility features
  • Explain how to activate them
  • List compatible assistive technologies
  • Be available in accessible formats

Legal Implications

WCAG 2.0

Not a law itself, but referenced by many laws and standards:

  • ADA (U.S.) - courts increasingly reference WCAG
  • AODA (Ontario, Canada) - explicitly requires WCAG 2.0 Level AA
  • Equality Act 2010 (UK) - WCAG often cited
  • European Accessibility Act - via EN 301 549 incorporating WCAG
  • Australia DDA - references WCAG through Australian standard

WCAG is a technical standard that laws point to as the compliance benchmark.

Section 508

Federal law in the United States:

  • Legally binding for federal agencies
  • Contractually binding for federal contractors
  • Enforceable through complaints and litigation
  • Can result in contract rejection or termination

Enforcement:

  • Federal agency administrative processes
  • Department of Justice complaints
  • Civil lawsuits
  • Contract performance requirements

Geographic Applicability

WCAG 2.0

Global standard:

  • Published by W3C, international consortium
  • Adopted by governments worldwide
  • Referenced in accessibility laws globally
  • Language translations available

WCAG is the de facto international accessibility standard.

Section 508

United States federal law:

  • Applies to U.S. federal agencies
  • Applies to federal contractors (even if based abroad)
  • Doesn't directly apply outside federal context
  • Influential on U.S. private sector accessibility

Section 508 is U.S.-specific but influences broader U.S. accessibility expectations.

Evolution and Updates

WCAG Evolution

WCAG 1.0 (1999): First version WCAG 2.0 (2008): Current Section 508 reference point WCAG 2.1 (2018): Adds 17 criteria (mobile, low vision, cognitive) WCAG 2.2 (2023): Adds 9 criteria (mobile, cognitive) WCAG 3.0 (draft): Complete restructuring (years away)

W3C regularly updates WCAG to address new technologies and user needs.

Section 508 Evolution

Original Section 508 (2001): First technical standards Section 508 Refresh (2017): Incorporated WCAG 2.0 Level AA Future updates: May adopt WCAG 2.1 or 2.2

Section 508 updates less frequently and goes through federal regulatory process.

Compliance Strategy: Meeting Both Standards

If You're Subject to Section 508

Priority 1: Ensure WCAG 2.0 Level AA compliance for web content Priority 2: Address Section 508 software requirements (502) if applicable Priority 3: Ensure PDFs and documents meet Section 508 (501) Priority 4: Verify multimedia has captions and audio descriptions (503) Priority 5: Create Accessibility Conformance Report (VPAT)

This covers everything.

If You're Only Targeting WCAG

For web content only:

  • Target WCAG 2.0 Level AA minimum (or 2.1, 2.2 for better accessibility)
  • Focus on web and web applications
  • No hardware, software platform APIs, or formal documentation required

WCAG is simpler scope but doesn't cover non-web technologies.

Recommended Approach

For most organizations:

  1. Start with WCAG 2.0 Level AA (or 2.1) for all web properties
  2. If you have federal contracts, add Section 508 requirements for software, documents, multimedia
  3. Consider WCAG 2.1 even if Section 508 doesn't require it (better mobile and cognitive accessibility)
  4. Create VPATs for products sold to federal government
  5. Monitor continuously to maintain compliance as content evolves

BrowseCheck helps by monitoring WCAG 2.0 Level AA compliance (covering the web portion of Section 508) continuously across your site.

Common Misconceptions

Misconception 1: "Section 508 and WCAG are competing standards"

Reality: Section 508 incorporates WCAG 2.0 Level AA for web content. They're aligned, not competing.

Misconception 2: "Meeting WCAG means you've met Section 508"

Reality: WCAG 2.0 Level AA satisfies Section 508 web content requirements. Section 508 has additional requirements for software, hardware, documents, and support.

Misconception 3: "Section 508 is stricter than WCAG"

Reality: For web content, they're identical (both require WCAG 2.0 Level AA). Section 508 is broader in scope (covers more technology types), not stricter.

Misconception 4: "WCAG 2.1 satisfies Section 508"

Reality: Section 508 currently references WCAG 2.0, not 2.1. However, meeting WCAG 2.1 Level AA exceeds Section 508 web requirements and is recommended.

Misconception 5: "Only federal agencies need Section 508"

Reality: Federal contractors, vendors, and grant recipients must also comply. Private companies without federal ties can optionally adopt Section 508 as a standard.

Comparison Table Summary

| Aspect | WCAG 2.0 | Section 508 (Revised) | |--------|----------|----------------------| | Type | Technical standard | Federal law | | Geography | Global | United States (federal) | | Scope | Web content | Web, software, hardware, docs | | Web Requirements | Level A, AA, AAA options | WCAG 2.0 Level AA required | | Software Requirements | Principles apply, not explicit | Explicit (Section 502) | | Hardware Requirements | None | Explicit (Sections 407-415) | | Documentation | Optional conformance claim | Required ACR/VPAT | | Enforcement | Via laws that reference it | Direct federal enforcement | | Updates | Regular (2.0→2.1→2.2) | Infrequent (regulatory process) | | Levels | A, AA, AAA | Binary (compliant/non-compliant) |

Conclusion

Section 508 and WCAG 2.0 are aligned for web content—Section 508 requires WCAG 2.0 Level AA conformance. The key difference is scope: WCAG focuses on web content, while Section 508 comprehensively covers software, hardware, documents, multimedia, and support services.

For web developers, meeting WCAG 2.0 Level AA satisfies Section 508 web requirements. Federal contractors must additionally address Section 508's software, hardware, and documentation requirements beyond WCAG's scope.

Organizations should:

  • Target WCAG 2.0 Level AA minimum for all web properties
  • Consider WCAG 2.1 or 2.2 for enhanced mobile and cognitive accessibility
  • Add Section 508 software, hardware, and documentation requirements if subject to federal procurement
  • Create VPATs when selling to federal government
  • Monitor continuously with tools like BrowseCheck for ongoing web compliance

Understanding the relationship between Section 508 and WCAG eliminates confusion, streamlines compliance efforts, and ensures you're meeting the right requirements for your situation.

← Back to blog