Section 508 Compliance Requirements: Technical Standards and Success Criteria

Section 508federal accessibilitygovernment compliance508 complianceBrowseCheck
·10 min read

Meeting Section 508 compliance requires understanding a complex web of technical standards covering web content, software, hardware, documentation, and support services. Since the 2017 Refresh, Section 508 incorporates WCAG 2.0 Level AA by reference while adding requirements specific to non-web technologies. This comprehensive guide breaks down exactly what you need to meet Section 508 compliance across all technology categories.

Section 508 Standards Organization

The Revised Section 508 Standards are organized into chapters addressing different technology types:

Chapter 1 - Application and Administration: Scope and referenced standards Chapter 2 - Scoping Requirements: What must be accessible and when Chapter 3 - Functional Performance Criteria: Performance-based requirements Chapter 4 - Hardware: Physical device requirements Chapter 5 - Software: Application software requirements Chapter 6 - Support Documentation and Services: Documentation and support requirements

For web developers and content creators, Chapter 5 (502 Software) and E205/E207 (WCAG incorporation) are most relevant.

Web Content Requirements (WCAG 2.0 Level AA)

E205.4 - Accessibility Standard

Section 508 requires web content to conform to WCAG 2.0 Level AA success criteria, with four exceptions that don't apply to web content.

This means all 38 WCAG 2.0 Level AA success criteria (25 Level A + 13 Level AA) must be met.

Key WCAG 2.0 Level AA Requirements

Perceivable:

  • 1.1.1 Non-text Content (A): Alt text for images
  • 1.2.2 Captions (Prerecorded) (A): Video captions
  • 1.2.3 Audio Description or Media Alternative (A): Audio descriptions for video
  • 1.2.4 Captions (Live) (AA): Live captions
  • 1.2.5 Audio Description (Prerecorded) (AA): Audio descriptions required
  • 1.3.1 Info and Relationships (A): Semantic structure
  • 1.3.2 Meaningful Sequence (A): Logical reading order
  • 1.3.3 Sensory Characteristics (A): Don't rely only on shape/color/location
  • 1.4.1 Use of Color (A): Color not sole method
  • 1.4.2 Audio Control (A): Ability to pause audio
  • 1.4.3 Contrast (Minimum) (AA): 4.5:1 for normal text
  • 1.4.4 Resize Text (AA): Text resizable to 200%
  • 1.4.5 Images of Text (AA): Avoid images of text

Operable:

  • 2.1.1 Keyboard (A): All functionality via keyboard
  • 2.1.2 No Keyboard Trap (A): No trapped focus
  • 2.2.1 Timing Adjustable (A): Control over time limits
  • 2.2.2 Pause, Stop, Hide (A): Control over moving content
  • 2.3.1 Three Flashes (A): No excessive flashing
  • 2.4.1 Bypass Blocks (A): Skip navigation links
  • 2.4.2 Page Titled (A): Descriptive page titles
  • 2.4.3 Focus Order (A): Logical focus sequence
  • 2.4.4 Link Purpose (A): Understandable link text
  • 2.4.5 Multiple Ways (AA): Multiple navigation methods
  • 2.4.6 Headings and Labels (AA): Descriptive headings/labels
  • 2.4.7 Focus Visible (AA): Visible keyboard focus

Understandable:

  • 3.1.1 Language of Page (A): Page language identified
  • 3.1.2 Language of Parts (AA): Language changes identified
  • 3.2.1 On Focus (A): No unexpected context changes on focus
  • 3.2.2 On Input (A): No unexpected context changes on input
  • 3.2.3 Consistent Navigation (AA): Consistent navigation
  • 3.2.4 Consistent Identification (AA): Consistent component identification
  • 3.3.1 Error Identification (A): Errors clearly identified
  • 3.3.2 Labels or Instructions (A): Sufficient labels
  • 3.3.3 Error Suggestion (AA): Helpful error suggestions
  • 3.3.4 Error Prevention (Legal, Financial, Data) (AA): Confirmation for critical actions

Robust:

  • 4.1.1 Parsing (A): Valid HTML markup
  • 4.1.2 Name, Role, Value (A): Proper ARIA implementation

Section 508 Exceptions to WCAG 2.0

Four WCAG 2.0 success criteria don't apply to non-web documents and software under Section 508:

  • 1.2.4 Captions (Live): Not required for non-web software
  • 1.2.5 Audio Description (Prerecorded): Alternative requirements apply
  • 2.4.1 Bypass Blocks: Alternative requirements for software
  • 2.4.2 Page Titled: Alternative requirements for documents

These exceptions exist because non-web technologies have different architectural constraints. Alternative Section 508 requirements address the same user needs.

Software Requirements (Section 502)

Software includes desktop applications, mobile apps, and web applications. Section 502 provides specific requirements beyond WCAG:

502.2 Interoperability with Assistive Technology

Software must use platform accessibility services and frameworks:

Windows: Microsoft UI Automation (UIA), MSAA macOS/iOS: NSAccessibility, UIAccessibility Android: Android Accessibility Framework Linux: AT-SPI (Assistive Technology Service Provider Interface)

Software must expose:

  • Object roles (button, link, heading, etc.)
  • Object states (checked, expanded, selected, etc.)
  • Object properties (name, value, description)
  • Object relationships (labeling, grouping)
  • Actions available (click, expand, edit)

502.3 Accessibility Services

Software must not interfere with platform accessibility features:

  • Screen readers
  • Magnification utilities
  • High contrast modes
  • Keyboard navigation
  • Voice control

Common violations: Overlaying custom renderers that bypass accessibility APIs.

502.4 Platform Accessibility Features

Software using platform APIs must support platform accessibility features automatically. Custom UI components must implement equivalent accessibility.

Hardware Requirements (Section 407-415)

407 Operable Parts

407.3 Keys, Tickets, and Fare Cards: Tactilely discernible orientation if orientation-dependent

407.4 Numeric Keys: Standard 12-key telephonic layout with tactile differentiation on 5 key

407.5 Tickets, Tokens, and Fare Cards: Sufficient color contrast (light-on-dark or dark-on-light)

407.8 Input Controls: Tactilely or visually discernible without vision; understandable with limited vision

408 Display Screens

408.2 Visibility: Characters on displays at least 3/16 inch (4.8mm) high

408.3 Flashing: No flashing between 2-55 Hz

409 Status Indicators

Visual status indicators must be accompanied by tactile or audible alternatives (e.g., notification lights also have sound or vibration).

410 Color Coding

Information conveyed by color must also be available without color perception.

412 ICT with Two-Way Voice Communication

Telecommunication devices must provide:

  • Real-time text (RTT) capability
  • Voice mail with visual indicators
  • Caller ID with visual and audible output

413 Closed Functionality

For devices where assistive technology can't be attached (like kiosks):

  • Speech output for visual information
  • Audio or tactile indication of control locations
  • Biometric alternatives to fingerprints
  • Privacy maintained for speech output users

Document Requirements (Section 501.1 - Scope)

PDF Accessibility (501.1)

Electronic documents, including PDFs, must be accessible:

Tagged PDFs: Proper document structure with tags Reading order: Logical content flow Alternative text: Descriptions for images and graphics Form field labels: Properly labeled form fields Table structure: Headers and data relationships identified Bookmarks and navigation: Document navigation aids Language specification: Document and inline language identification

Common PDF issues:

  • Scanned PDFs without OCR or tagging
  • Untagged form fields
  • Images without alt text
  • Complex tables without proper structure
  • Poor reading order

Office Documents

Microsoft Office (Word, Excel, PowerPoint):

  • Use built-in styles for headings
  • Add alt text to images
  • Create accessible tables with headers
  • Ensure sufficient color contrast
  • Provide meaningful link text
  • Use built-in accessibility checker

Google Workspace:

  • Similar requirements for Docs, Sheets, Slides
  • Use built-in accessibility features
  • Provide alt text and proper structure

Multimedia Requirements (Section 503)

503.4 User Controls for Captions and Audio Description

Media players must provide user controls for:

  • Enabling/disabling captions
  • Selecting caption language
  • Enabling/disabling audio descriptions
  • Adjusting volume independently for audio descriptions

Captions

All prerecorded video: Synchronized captions required

Live video: Captions strongly recommended (though technically not required for non-web under exceptions)

Caption quality:

  • Accurate and complete
  • Synchronized timing
  • Identify speakers
  • Include relevant sound descriptions [applause], [door slams]

Audio Descriptions

Prerecorded video with meaningful visual content: Audio descriptions describing visual information

Methods:

  • Integrated into standard audio track
  • Separate audio description track
  • Extended audio description (pausing video to describe)

Support Documentation and Services (Section 602)

602.2 Accessibility and Compatibility Features

Documentation must include:

  • List of accessibility features
  • How to activate and use accessibility features
  • How to create accessible content with the product
  • Known assistive technology compatibility and incompatibility

602.3 Electronic Support Documentation

Electronic documentation must conform to WCAG 2.0 Level A minimum (not AA like web content).

602.4 Alternate Formats for Non-Electronic Support Documentation

On request, provide:

  • Braille
  • Audio
  • Large print
  • Electronic formats usable with assistive technology

603 Support Services

Technical support must be accessible:

  • Alternative communication methods (TTY, relay services, video relay)
  • Information about accessibility features
  • Troubleshooting accessibility issues

Functional Performance Criteria (Section 302)

When technical provisions don't address specific situations, Functional Performance Criteria ensure technology is still accessible:

302.1 Without Vision: Full functionality available through audio or tactile means

302.2 With Limited Vision: Usable with magnification, high contrast, or audio

302.3 Without Perception of Color: No information by color alone

302.4 Without Hearing: Full functionality without hearing

302.5 With Limited Hearing: Operable with limited hearing (volume control, assistive listening)

302.6 Without Speech: Operable without speech (no voice-only input)

302.7 With Limited Manipulation: Operable with limited dexterity

302.8 With Limited Reach and Strength: Operable within limited reach and force ranges

302.9 With Limited Language, Cognitive, and Learning Abilities: Minimize cognitive load; provide help

Testing Section 508 Compliance

Automated Testing

Web scanning tools:

  • axe DevTools (WCAG 2.0 compliance)
  • WAVE
  • Lighthouse
  • BrowseCheck (continuous monitoring)

Document testing:

  • PDF Accessibility Checker (PAC)
  • Adobe Acrobat Accessibility Checker
  • Microsoft Office Accessibility Checker

Manual Testing

Keyboard navigation: Navigate entire interface with keyboard only

Screen reader testing:

  • JAWS (Windows)
  • NVDA (Windows, free)
  • VoiceOver (macOS/iOS)
  • TalkBack (Android)

Color contrast: Check all text and UI components

Structure review: Verify semantic HTML and proper heading hierarchy

Multimedia review: Verify captions and descriptions

Assistive Technology Compatibility Testing

Test software with:

  • Platform screen readers
  • Screen magnifiers
  • Voice control software
  • Switch controls
  • Alternative input devices

Compliance Documentation

Creating Section 508 Conformance Reports

Use VPAT (Voluntary Product Accessibility Template) or ACR (Accessibility Conformance Report):

Identify applicable criteria: Web, software, hardware, documents Evaluate conformance: Supports, Partially Supports, Does Not Support, Not Applicable Provide explanations: Describe non-conformance and workarounds Include contact information: For accessibility support

Maintaining Compliance

Regular audits: Schedule periodic accessibility reviews Regression testing: Monitor for introduced barriers User feedback: Collect and respond to accessibility issues Training: Educate developers, designers, and content creators Continuous monitoring: Use tools like BrowseCheck for ongoing compliance verification

Conclusion

Section 508 compliance requires meeting WCAG 2.0 Level AA for web content plus additional requirements for software, hardware, documents, and support services. The Revised Section 508 Standards provide comprehensive, technology-neutral requirements ensuring accessibility across the full range of federal information technology.

Key compliance areas:

  • Web content: WCAG 2.0 Level AA (38 success criteria)
  • Software: Platform accessibility API integration
  • Hardware: Accessible operable parts, displays, and controls
  • Documents: Tagged PDFs and accessible office documents
  • Multimedia: Captions and audio descriptions
  • Support: Accessible documentation and services

Organizations subject to Section 508 should conduct comprehensive audits across all technology types, prioritize remediation based on impact and effort, and implement continuous monitoring to maintain compliance as technology evolves.

Ready to assess your Section 508 compliance? Start with WCAG 2.0 Level AA testing for web content, evaluate software against platform accessibility standards, and review documentation and support processes for accessibility. Comprehensive compliance requires addressing all aspects of the standards, not just web content.

← Back to blog