Skip to content

Evidence request lists

Section 508 - ICT Accessibility (Revised)

Evidence request list. 30 controls, 30 carrying auditor artefact guidance. Generated from the compliance knowledge graph on 12 September 2026. Published by The Art of Service.

Chapter 2: Scoping Requirements

E101
Application Scope

The standards apply to ICT developed, procured, maintained, or used by federal agencies to ensure accessibility.

Artefacts an auditor will ask for
  • Training records for content authors and procurement officers
  • Alternative means of access documentation for legacy systems
  • Accessibility Conformance Reports (ACR) using VPAT template
  • WCAG 2.0 Level AA test results for digital content
  • Procurement market research records documenting accessibility evaluation
Where this commonly fails
  • Support documentation not provided in accessible formats
  • Real-time text functionality absent from two-way voice products
  • VPAT documentation outdated or missing for procured ICT
  • WCAG 2.0 Level AA conformance not verified through user testing
E205
Electronic Content Scoping

All web and non-web electronic content must conform to WCAG 2.0 Level AA Success Criteria with limited exceptions.

Artefacts an auditor will ask for
  • Training records for content authors and procurement officers
  • Alternative means of access documentation for legacy systems
  • Accessibility Conformance Reports (ACR) using VPAT template
  • WCAG 2.0 Level AA test results for digital content
  • Procurement market research records documenting accessibility evaluation
Where this commonly fails
  • Real-time text functionality absent from two-way voice products
  • VPAT documentation outdated or missing for procured ICT
  • WCAG 2.0 Level AA conformance not verified through user testing
  • Hardware accessibility features not validated against operable parts criteria
  • Support documentation not provided in accessible formats
E205.4
Electronic Content Accessibility

Electronic content shall conform to WCAG 2.0 Level A and Level AA for documents, spreadsheets, presentations, and other content created or used by federal agencies.

Artefacts an auditor will ask for
  • Document accessibility audit results
  • Author training records
  • Template library conformance
  • Remediation processes for legacy content
  • Public content accessibility status
Where this commonly fails
  • Legacy documents not remediated
  • Authors not trained
  • Templates inaccessible
  • No audit of public content
E207
Software Scoping

Software and platforms must conform to WCAG 2.0 Level AA and additional software-specific accessibility requirements.

Artefacts an auditor will ask for
  • Training records for content authors and procurement officers
  • Alternative means of access documentation for legacy systems
  • Accessibility Conformance Reports (ACR) using VPAT template
Where this commonly fails
  • VPAT documentation outdated or missing for procured ICT
  • WCAG 2.0 Level AA conformance not verified through user testing
  • Hardware accessibility features not validated against operable parts criteria
  • Support documentation not provided in accessible formats
  • Real-time text functionality absent from two-way voice products
E207.2
WCAG Conformance

Web content shall conform to WCAG 2.0 Level A and Level AA Success Criteria and Conformance Requirements for both public facing and agency internal web content.

Artefacts an auditor will ask for
  • WCAG 2.0 AA conformance audit report
  • Automated accessibility scan results
  • Manual testing reports
  • VPAT 2.0 documentation
  • Remediation tracking for non conformance
Where this commonly fails
  • Audit not performed
  • Only automated testing used
  • VPAT outdated
  • Non conformance not tracked
E208
Agency Official Communications

Agency official communications must be accessible including emergency notifications and public-facing content.

Artefacts an auditor will ask for
  • Procurement market research records documenting accessibility evaluation
  • Remediation plans for non-conformant ICT products
  • Training records for content authors and procurement officers
  • Alternative means of access documentation for legacy systems
  • Accessibility Conformance Reports (ACR) using VPAT template
Where this commonly fails
  • Support documentation not provided in accessible formats
  • Real-time text functionality absent from two-way voice products
  • VPAT documentation outdated or missing for procured ICT
  • WCAG 2.0 Level AA conformance not verified through user testing

Chapter 3: Functional Performance Criteria

302.1
Functional Performance Without Vision

Where a visual mode of operation is provided, ICT shall provide at least one mode of operation that does not require user vision and supports non-visual interaction throughout the user experience.

Artefacts an auditor will ask for
  • Screen reader testing report (JAWS, NVDA, VoiceOver)
  • Non-visual operation walkthroughs
  • Audio output verification
  • Keyboard only navigation evidence
  • User testing with blind participants
Where this commonly fails
  • Critical content delivered visually only
  • Screen reader announcements incomplete
  • Dynamic content not announced
  • Audio cues absent
302.2
Functional Performance with Limited Vision

ICT shall provide at least one mode of operation that enables users with limited vision to use the ICT including features for enlargement, contrast adjustment, and reduced visual complexity.

Artefacts an auditor will ask for
  • Zoom and magnification testing at 200 percent
  • High contrast mode testing
  • User configurable text size evidence
  • Color contrast measurements
  • Reflow testing
Where this commonly fails
  • Layout breaks at 200 percent zoom
  • Contrast not user adjustable
  • Fixed font sizes
  • Horizontal scrolling required
302.3
Functional Performance Without Perception of Color

Where ICT uses color to convey information, an alternative means of conveying that information shall be provided so that users who cannot perceive color can use the ICT.

Artefacts an auditor will ask for
  • Color use audit report
  • Alternative text or pattern indicators
  • Greyscale rendering tests
  • Color blindness simulator results
  • Form validation alternative indicators
Where this commonly fails
  • Required fields indicated by red only
  • Charts rely on color alone
  • Error states color only
  • Status indicators not duplicated
302.4
Functional Performance Without Hearing

Where ICT provides an auditory mode of operation, at least one mode shall not require hearing and shall provide alternatives for all auditory information necessary for using the ICT.

Artefacts an auditor will ask for
  • Captioned video evidence
  • Transcripts for audio content
  • Visual notification alternatives
  • Auditory CAPTCHA alternatives
  • Sign language interpretation where applicable
Where this commonly fails
  • Videos without captions
  • Audio only alerts
  • Auto generated captions inaccurate
  • No transcripts for audio
302.8
Functional Performance with Limited Reach and Strength

Where physical operation is required, at least one mode shall be operable with limited reach and limited strength including consideration of forward and side reach ranges.

Artefacts an auditor will ask for
  • Operable parts within reach range documentation
  • Force measurement testing
  • Hardware accessibility specifications
  • Kiosk reach range verification
  • Alternative input device support
Where this commonly fails
  • Controls outside reach range
  • Excessive force required
  • Kiosks not wheelchair accessible
  • No alternative input ports

Chapter 4: Hardware

402
Closed Functionality

ICT with closed functionality must meet specific accessibility requirements without relying on assistive technology.

Artefacts an auditor will ask for
  • Training records for content authors and procurement officers
  • Alternative means of access documentation for legacy systems
  • Accessibility Conformance Reports (ACR) using VPAT template
  • WCAG 2.0 Level AA test results for digital content
Where this commonly fails
  • Support documentation not provided in accessible formats
  • Real-time text functionality absent from two-way voice products
  • VPAT documentation outdated or missing for procured ICT
403.1
Biometrics

Where biometrics are the only means for user identification or control, an alternative method shall be provided that does not require user biometrics.

Artefacts an auditor will ask for
  • Alternative authentication methods documented
  • PIN or password backup verification
  • Multi-factor alternatives
  • Accommodation request process
  • Setup documentation
Where this commonly fails
  • Biometrics with no alternative
  • Alternative not user friendly
  • Setup requires biometrics
  • No accommodation process
407
Operable Parts

Hardware operable parts must be usable with one hand and not require tight grasping, pinching, or twisting.

Artefacts an auditor will ask for
  • Alternative means of access documentation for legacy systems
  • Accessibility Conformance Reports (ACR) using VPAT template
  • WCAG 2.0 Level AA test results for digital content
Where this commonly fails
  • WCAG 2.0 Level AA conformance not verified through user testing
  • Hardware accessibility features not validated against operable parts criteria
  • Support documentation not provided in accessible formats
407.2
Contrast Operable Parts

Operable parts on hardware including keys, buttons, and controls shall be tactilely discernible and have sufficient visual contrast from background surfaces.

Artefacts an auditor will ask for
  • Tactile testing of operable parts
  • Contrast measurements
  • Raised character labelling where required
  • Symbol placement evidence
  • Color independent indicators
Where this commonly fails
  • Touch screen only with no tactile reference
  • Insufficient contrast on labels
  • No raised characters where required
  • Symbols rely on color
412
ICT with Two-Way Voice Communication

ICT providing two-way voice communication must support volume gain, hearing aid compatibility, and TTY connectivity.

Artefacts an auditor will ask for
  • Alternative means of access documentation for legacy systems
  • Accessibility Conformance Reports (ACR) using VPAT template
  • WCAG 2.0 Level AA test results for digital content
  • Procurement market research records documenting accessibility evaluation
  • Remediation plans for non-conformant ICT products
Where this commonly fails
  • WCAG 2.0 Level AA conformance not verified through user testing
  • Hardware accessibility features not validated against operable parts criteria
  • Support documentation not provided in accessible formats
  • Real-time text functionality absent from two-way voice products

Chapter 5: Software

501.0
Scope of Software

Software including applications, web content, electronic documents, and authoring tools shall conform to applicable software accessibility requirements covering interoperability and platform accessibility services.

Artefacts an auditor will ask for
  • Software accessibility conformance report
  • Platform accessibility API usage evidence
  • Assistive technology compatibility testing
  • VPAT for software
  • Authoring tool conformance
Where this commonly fails
  • Custom controls without ARIA
  • Platform API not used
  • AT compatibility unverified
  • Authoring tool produces inaccessible output
501.1
Scope of Hardware

Hardware that transmits, receives, processes, or stores information and communication shall conform to applicable hardware requirements including operable parts, biometrics, and connections.

Artefacts an auditor will ask for
  • Hardware accessibility conformance reports
  • VPAT for hardware products
  • Operable parts testing records
  • Biometric alternative documentation
  • Standard connection verification
Where this commonly fails
  • Hardware VPAT missing
  • No alternative to biometrics
  • Proprietary connections only
  • Operable parts not tested
502
Interoperability with Assistive Technology

Software must support interoperability with assistive technology through platform accessibility services.

Artefacts an auditor will ask for
  • Procurement market research records documenting accessibility evaluation
  • Remediation plans for non-conformant ICT products
  • Training records for content authors and procurement officers
  • Alternative means of access documentation for legacy systems
Where this commonly fails
  • WCAG 2.0 Level AA conformance not verified through user testing
  • Hardware accessibility features not validated against operable parts criteria
  • Support documentation not provided in accessible formats
  • Real-time text functionality absent from two-way voice products
  • VPAT documentation outdated or missing for procured ICT
502.2.1
User Control of Accessibility Features

Software shall not disrupt or disable activated features of any operating system platform that are documented to be accessibility features or that interoperate with assistive technology.

Artefacts an auditor will ask for
  • AT compatibility test reports
  • Platform accessibility setting preservation tests
  • No override evidence for accessibility features
  • Screen reader integration testing
  • Switch device compatibility
Where this commonly fails
  • Software overrides high contrast
  • AT not detected
  • Platform settings ignored
  • Switch input blocked
503
Applications

Applications must provide user preferences for accessibility settings and support assistive technology access to content.

Artefacts an auditor will ask for
  • Accessibility Conformance Reports (ACR) using VPAT template
  • WCAG 2.0 Level AA test results for digital content
  • Procurement market research records documenting accessibility evaluation
Where this commonly fails
  • VPAT documentation outdated or missing for procured ICT
  • WCAG 2.0 Level AA conformance not verified through user testing
  • Hardware accessibility features not validated against operable parts criteria
504
Authoring Tools

Authoring tools must be accessible and support the creation of accessible content where possible.

Artefacts an auditor will ask for
  • Accessibility Conformance Reports (ACR) using VPAT template
  • WCAG 2.0 Level AA test results for digital content
  • Procurement market research records documenting accessibility evaluation
  • Remediation plans for non-conformant ICT products
  • Training records for content authors and procurement officers
  • Alternative means of access documentation for legacy systems
Where this commonly fails
  • WCAG 2.0 Level AA conformance not verified through user testing
  • Hardware accessibility features not validated against operable parts criteria
  • Support documentation not provided in accessible formats

Chapter 6: Support Documentation and Services

602
Support Documentation

Documentation and support services must describe accessibility features and be provided in accessible formats.

Artefacts an auditor will ask for
  • WCAG 2.0 Level AA test results for digital content
  • Procurement market research records documenting accessibility evaluation
  • Remediation plans for non-conformant ICT products
Where this commonly fails
  • VPAT documentation outdated or missing for procured ICT
  • WCAG 2.0 Level AA conformance not verified through user testing
  • Hardware accessibility features not validated against operable parts criteria
  • Support documentation not provided in accessible formats
  • Real-time text functionality absent from two-way voice products
603
Support Services

Support services including help desks must accommodate communication needs of users with disabilities.

Artefacts an auditor will ask for
  • Remediation plans for non-conformant ICT products
  • Training records for content authors and procurement officers
  • Alternative means of access documentation for legacy systems
  • Accessibility Conformance Reports (ACR) using VPAT template
Where this commonly fails
  • Real-time text functionality absent from two-way voice products
  • VPAT documentation outdated or missing for procured ICT
  • WCAG 2.0 Level AA conformance not verified through user testing
603.2
Support Services Information About Accommodations

Support services shall include information on the accessibility and compatibility features of the ICT and shall be provided through accessible channels for users with disabilities.

Artefacts an auditor will ask for
  • Support staff accessibility training records
  • TTY or relay service availability
  • Multiple contact channel options
  • Response time parity for accessible channels
  • Knowledge base on accessibility
Where this commonly fails
  • Phone only support
  • TTY or relay unavailable
  • Support untrained on accessibility
  • Longer response times for accessible channels

Chapter 7: Referenced Standards

707
Real-Time Text Functionality

ICT providing real-time text must support interoperability, concurrent voice and text, and visual indicators.

Artefacts an auditor will ask for
  • Training records for content authors and procurement officers
  • Alternative means of access documentation for legacy systems
  • Accessibility Conformance Reports (ACR) using VPAT template
Where this commonly fails
  • Hardware accessibility features not validated against operable parts criteria
  • Support documentation not provided in accessible formats
  • Real-time text functionality absent from two-way voice products
  • VPAT documentation outdated or missing for procured ICT
  • WCAG 2.0 Level AA conformance not verified through user testing

Documentation

FIVEOEIGHT-4
Support Documentation and Services

Per Section 508: support documentation + services. Requirements include (a) accessible documentation + (b) accessible support services + (c) maintain VPATs (Voluntary Product Accessibility Templates) + (d) integrate with procurement.

Artefacts an auditor will ask for
  • Section 508 evidence for FIVEOEIGHT-4
Where this commonly fails
  • WCAG conformance + VPAT partial

Functional Performance

FIVEOEIGHT-1
Functional Performance Criteria (Chapter 3)

Per Section 508 ICT Accessibility Revised + WCAG 2.0/2.1: functional performance. Requirements include (a) Functional Performance Without Vision + (b) Without Hearing + (c) Without Speech + (d) Without Color Perception + (e) Without Manipulation/Strength + (f) for users with photosensitivity + (g) understanding capabilities. Align with WCAG 2.x A + AA.

Artefacts an auditor will ask for
  • Section 508 evidence for FIVEOEIGHT-1
Where this commonly fails
  • WCAG conformance + VPAT partial

Hardware

FIVEOEIGHT-2
Hardware (Chapter 4) - Closed Functionality, Speech, Operability

Per Section 508 Chapter 4: hardware. Requirements include (a) Closed Functionality including ATMs + kiosks accessible + (b) Speech Output + (c) Operability including keys + controls + tactile features + (d) maintain documentation.

Artefacts an auditor will ask for
  • Section 508 evidence for FIVEOEIGHT-2
Where this commonly fails
  • WCAG conformance + VPAT partial

Software

FIVEOEIGHT-3
Software (Chapter 5) - WCAG 2.0 AA + Authoring Tools

Per Section 508 Chapter 5: software. Requirements include (a) WCAG 2.0 Level A + AA conformance + (b) Authoring Tools accessibility + (c) accessibility services + (d) maintain documentation.

Artefacts an auditor will ask for
  • Section 508 evidence for FIVEOEIGHT-3
Where this commonly fails
  • WCAG conformance + VPAT partial
Assembled from the framework's own control set. Every line traces to a control in the graph, so this pack is regenerated rather than written, and stays current as the graph does.

Assembled from the framework’s own control set, so this list is regenerated rather than written and stays current as the graph does. See the Section 508 - ICT Accessibility (Revised) framework page.