Section 508 Compliance Guide: Federal Accessibility Requirements

Section 508 of the Rehabilitation Act requires federal agencies to make their electronic and information technology (ICT) accessible to people with disabilities. The 2017 refresh aligned Section 508 with WCAG 2.0 Level AA, creating a unified standard for federal digital accessibility. Organizations selling to federal agencies, receiving federal funding, or operating as federal contractors must understand and meet these requirements.

This guide covers Section 508 requirements, how they align with WCAG, procurement implications, and compliance strategies for organizations subject to federal accessibility standards.

Q: What is Section 508 compliance?

A: Section 508 compliance means meeting the accessibility standards for electronic and information technology used by federal agencies. Since 2018, this requires conformance to WCAG 2.0 Level A and AA success criteria, with additional requirements for hardware, software, and support documentation.

Section 508 Overview

Legal Foundation

Section 508 of the Rehabilitation Act (29 U.S.C. § 794d):

• Enacted 1986, strengthened 1998
• Applies to federal agencies and recipients of federal funding
• Requires accessible ICT development, procurement, maintenance, and use
• Enforced by agency-level Section 508 coordinators

2017 Refresh (Effective 2018)

The Section 508 Standards Refresh:

• Aligned with WCAG 2.0 Level AA
• Adopted internationally harmonized standards (EN 301 549)
• Applies to all ICT, not just websites
• Includes functional performance criteria

Who Must Comply

Federal agencies: All executive branch agencies must comply

Federal contractors: Companies providing ICT to federal agencies

Grant recipients: Organizations receiving federal funding

Federally-funded programs: Education, healthcare, and other programs receiving federal support

Section 508 Standards Structure

Categories of Requirements

E205 Electronic Content:

• Web content
• Electronic documents
• Multimedia

E206 Hardware:

• Standard connections
• Audio and visual outputs
• Input devices

E207 Software:

• Platform accessibility features
• Interoperability with assistive technology
• User preferences

E208 Support Documentation:

• Accessible user documentation
• Support services accessibility

Web Content Requirements

For web content, Section 508 incorporates WCAG by reference:

E205.4 Accessibility Standard: "Electronic content shall conform to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0"

This means WCAG 2.0 AA is the technical standard for:

• Websites
• Web applications
• Web-based content management systems
• Intranets and extranets
• Mobile web content

WCAG 2.0 AA Requirements (Section 508)

Principle 1: Perceivable

1.1 Text Alternatives

• 1.1.1 Non-text Content (A)

1.2 Time-based Media

• 1.2.1 Audio-only and Video-only (A)
• 1.2.2 Captions (A)
• 1.2.3 Audio Description or Media Alternative (A)
• 1.2.4 Captions (Live) (AA)
• 1.2.5 Audio Description (AA)

1.3 Adaptable

• 1.3.1 Info and Relationships (A)
• 1.3.2 Meaningful Sequence (A)
• 1.3.3 Sensory Characteristics (A)

1.4 Distinguishable

• 1.4.1 Use of Color (A)
• 1.4.2 Audio Control (A)
• 1.4.3 Contrast (Minimum) (AA)
• 1.4.4 Resize Text (AA)
• 1.4.5 Images of Text (AA)

Principle 2: Operable

2.1 Keyboard Accessible

• 2.1.1 Keyboard (A)
• 2.1.2 No Keyboard Trap (A)

2.2 Enough Time

• 2.2.1 Timing Adjustable (A)
• 2.2.2 Pause, Stop, Hide (A)

2.3 Seizures

• 2.3.1 Three Flashes or Below Threshold (A)

2.4 Navigable

• 2.4.1 Bypass Blocks (A)
• 2.4.2 Page Titled (A)
• 2.4.3 Focus Order (A)
• 2.4.4 Link Purpose (In Context) (A)
• 2.4.5 Multiple Ways (AA)
• 2.4.6 Headings and Labels (AA)
• 2.4.7 Focus Visible (AA)

Principle 3: Understandable

3.1 Readable

• 3.1.1 Language of Page (A)
• 3.1.2 Language of Parts (AA)

3.2 Predictable

• 3.2.1 On Focus (A)
• 3.2.2 On Input (A)
• 3.2.3 Consistent Navigation (AA)
• 3.2.4 Consistent Identification (AA)

3.3 Input Assistance

• 3.3.1 Error Identification (A)
• 3.3.2 Labels or Instructions (A)
• 3.3.3 Error Suggestion (AA)
• 3.3.4 Error Prevention (AA)

Principle 4: Robust

4.1 Compatible

• 4.1.1 Parsing (A) - deprecated in WCAG 2.2
• 4.1.2 Name, Role, Value (A)

Beyond WCAG: Additional Section 508 Requirements

Functional Performance Criteria (Chapter 3)

When WCAG doesn't apply or is insufficient:

302.1 Without Vision: Provide modes that don't require user vision

302.2 With Limited Vision: Provide modes for users with limited vision

302.3 Without Perception of Color: Don't use color as only means of conveying information

302.4 Without Hearing: Provide modes that don't require user hearing

302.5 With Limited Hearing: Provide modes for users with limited hearing

302.6 Without Speech: Don't require speech input for operation

302.7 With Limited Manipulation: Provide modes not requiring fine motor control

302.8 With Limited Reach and Strength: Provide modes accessible without reaching or significant force

302.9 With Limited Language, Cognitive, and Learning Abilities: Provide modes that minimize cognitive requirements

Hardware Requirements (Chapter 4)

407 Operable Parts: Controls must be operable with one hand, not require tight grasping

408 Display Screens: Must be visible from point of operation

409 Status Indicators: Must be discernible visually and tactilely

410 Color Coding: Color alone cannot convey information

412 ICT with Two-Way Voice Communication: Real-time text capability, volume gain

Software Requirements (Chapter 5)

502 Interoperability with Assistive Technology:

• Object information available to AT
• Modification of accessible values supported
• Row, column, and headers available for data tables

503 Applications:

• User preferences respected
• Alternative user interfaces permitted
• Applications don't disrupt AT function

Support Documentation (Chapter 6)

602 Support Documentation:

• Product support documentation must conform to Level A and Level AA
• Available in accessible formats

603 Support Services:

• IT support must accommodate users with disabilities
• Information provided in accessible formats

Procurement Requirements

FAR Clause 52.204-20

Federal Acquisition Regulation requires:

• Contractors to supply accessible ICT
• Documentation of Section 508 conformance
• Accessibility Conformance Reports (ACRs)

VPATs and ACRs

Voluntary Product Accessibility Template (VPAT):

• Standard format for documenting accessibility conformance
• Required for federal procurement

Accessibility Conformance Report (ACR):

• Completed VPAT for specific product
• Documents conformance level for each criterion
• Includes explanatory remarks

VPAT versions:

• VPAT 2.4 (current)
• Sections for WCAG, Section 508, EN 301 549

Creating ACRs

Conformance levels:

• Supports: Fully meets criterion
• Partially Supports: Some functionality meets criterion
• Does Not Support: Majority doesn't meet criterion
• Not Applicable: Criterion not relevant to product

Best practices:

• Be accurate—inaccurate ACRs are contractual risks
• Include specific version numbers
• Update ACRs with each major release
• Detail remediation plans for known issues

Compliance Strategies

For Federal Agencies

Agency responsibilities:

1. Appoint Section 508 Coordinator
2. Develop accessibility policies
3. Train staff on accessibility
4. Evaluate ICT before procurement
5. Monitor ongoing compliance
6. Report on program status

GSA resources:

• Section508.gov
• Trusted Tester certification
• Procurement guidance

For Contractors and Vendors

Compliance approach:

1. Understand Section 508 requirements
2. Design with accessibility from start
3. Test against WCAG 2.0 AA
4. Create accurate ACR/VPAT documentation
5. Maintain accessibility through updates
6. Provide accessible support documentation

TestParty for federal compliance:

• Automated WCAG 2.0/2.1 AA scanning
• Remediation guidance for violations
• Documentation support for ACRs
• Continuous compliance monitoring

For Grant Recipients

Organizations receiving federal grants must ensure:

• Funded program materials are accessible
• Websites and applications meet Section 508
• Documents and multimedia are accessible
• Reasonable accommodations are provided

Testing for Section 508

Trusted Tester Process

GSA's Trusted Tester program provides:

• Standardized testing methodology
• Certification for testers
• Consistent evaluation across agencies

Testing approach:

1. Conformance baseline testing
2. Manual verification of automated results
3. Functional performance evaluation
4. Documentation review

Automated Testing

Automated tools test many WCAG success criteria:

• Structure and semantics (headings, landmarks)
• Color contrast
• Form labels
• Alt text presence (not quality)
• Language attributes

Limitations: Automated testing catches ~30-40% of issues. Section 508 compliance requires manual testing.

Manual Testing Requirements

Human evaluation needed for:

• Alt text accuracy and appropriateness
• Keyboard operability
• Focus management
• Reading order
• Error handling effectiveness
• Overall usability

FAQ Section

Q: Is Section 508 the same as ADA?

A: No. Section 508 applies specifically to federal agencies and federal ICT. ADA Title II applies to state/local government, and ADA Title III applies to places of public accommodation. However, both reference similar WCAG standards for web accessibility.

Q: Does Section 508 require WCAG 2.1 or 2.2?

A: The current Section 508 standards reference WCAG 2.0. However, meeting WCAG 2.1 or 2.2 AA exceeds Section 508 requirements. Some agencies may specify newer WCAG versions in contracts.

Q: Do I need a VPAT to sell to federal agencies?

A: Practically, yes. While not always legally mandated, federal procurement officers typically require VPATs to evaluate accessibility conformance. Products without VPATs are disadvantaged or excluded from consideration.

Q: How do I become a Trusted Tester?

A: Complete GSA's Trusted Tester certification through DHS training. The certification validates competency in Section 508 testing methodology. See Section508.gov for current requirements.

Q: Does Section 508 apply to mobile apps?

A: Yes. Section 508 applies to all ICT, including mobile applications. WCAG provides applicable guidance, though native mobile apps require additional platform-specific considerations.

Key Takeaways

• Section 508 requires WCAG 2.0 Level AA for web content and electronic documents.
• Applies to federal agencies, contractors, and grant recipients—not just government websites.
• VPATs/ACRs are essential for federal procurement. Accurate conformance documentation is critical.
• Includes more than WCAG: Hardware, software, and support documentation have additional requirements.
• Testing requires both automated and manual evaluation. Trusted Tester methodology provides standardized approach.
• Compliance is ongoing. Changes to products require updated conformance documentation.

Conclusion

Section 508 compliance is essential for organizations working with federal agencies. While the web content requirements align with WCAG 2.0 AA, Section 508 encompasses broader ICT accessibility requirements including hardware, software, and documentation.

Understanding these requirements—and maintaining accurate conformance documentation—is critical for federal procurement success and legal compliance.

TestParty helps organizations achieve and maintain Section 508 compliance through automated WCAG testing and remediation. For vendors creating federal-focused products or agencies ensuring internal compliance, TestParty provides the continuous monitoring and fix generation needed for sustainable accessibility.

Ready to achieve Section 508 compliance? Get a free accessibility scan to assess your current conformance status.

Related Articles:

• WCAG Conformance Levels Explained: A, AA, and AAA
• ADA Website Compliance 2025: Complete Legal Requirements
• VPAT and ACR Guide: Accessibility Conformance Documentation

Quick note: we used AI to help write this article, and our team reviewed it for accuracy. We're passionate about making the web accessible, but accessibility law can get complicated. If you're making decisions about compliance, definitely loop in a professional who knows your specific situation.