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
The standards apply to ICT developed, procured, maintained, or used by federal agencies to ensure accessibility.
- 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
- 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
All web and non-web electronic content must conform to WCAG 2.0 Level AA Success Criteria with limited exceptions.
- 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
- 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
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.
- Document accessibility audit results
- Author training records
- Template library conformance
- Remediation processes for legacy content
- Public content accessibility status
- Legacy documents not remediated
- Authors not trained
- Templates inaccessible
- No audit of public content
Software and platforms must conform to WCAG 2.0 Level AA and additional software-specific accessibility requirements.
- Training records for content authors and procurement officers
- Alternative means of access documentation for legacy systems
- Accessibility Conformance Reports (ACR) using VPAT template
- 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
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.
- WCAG 2.0 AA conformance audit report
- Automated accessibility scan results
- Manual testing reports
- VPAT 2.0 documentation
- Remediation tracking for non conformance
- Audit not performed
- Only automated testing used
- VPAT outdated
- Non conformance not tracked
Agency official communications must be accessible including emergency notifications and public-facing 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
- Accessibility Conformance Reports (ACR) using VPAT template
- 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
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.
- Screen reader testing report (JAWS, NVDA, VoiceOver)
- Non-visual operation walkthroughs
- Audio output verification
- Keyboard only navigation evidence
- User testing with blind participants
- Critical content delivered visually only
- Screen reader announcements incomplete
- Dynamic content not announced
- Audio cues absent
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.
- Zoom and magnification testing at 200 percent
- High contrast mode testing
- User configurable text size evidence
- Color contrast measurements
- Reflow testing
- Layout breaks at 200 percent zoom
- Contrast not user adjustable
- Fixed font sizes
- Horizontal scrolling required
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.
- Color use audit report
- Alternative text or pattern indicators
- Greyscale rendering tests
- Color blindness simulator results
- Form validation alternative indicators
- Required fields indicated by red only
- Charts rely on color alone
- Error states color only
- Status indicators not duplicated
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.
- Captioned video evidence
- Transcripts for audio content
- Visual notification alternatives
- Auditory CAPTCHA alternatives
- Sign language interpretation where applicable
- Videos without captions
- Audio only alerts
- Auto generated captions inaccurate
- No transcripts for audio
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.
- Operable parts within reach range documentation
- Force measurement testing
- Hardware accessibility specifications
- Kiosk reach range verification
- Alternative input device support
- Controls outside reach range
- Excessive force required
- Kiosks not wheelchair accessible
- No alternative input ports
Chapter 4: Hardware
ICT with closed functionality must meet specific accessibility requirements without relying on assistive technology.
- 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
- 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
Where biometrics are the only means for user identification or control, an alternative method shall be provided that does not require user biometrics.
- Alternative authentication methods documented
- PIN or password backup verification
- Multi-factor alternatives
- Accommodation request process
- Setup documentation
- Biometrics with no alternative
- Alternative not user friendly
- Setup requires biometrics
- No accommodation process
Hardware operable parts must be usable with one hand and not require tight grasping, pinching, or twisting.
- 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
- 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
Operable parts on hardware including keys, buttons, and controls shall be tactilely discernible and have sufficient visual contrast from background surfaces.
- Tactile testing of operable parts
- Contrast measurements
- Raised character labelling where required
- Symbol placement evidence
- Color independent indicators
- Touch screen only with no tactile reference
- Insufficient contrast on labels
- No raised characters where required
- Symbols rely on color
ICT providing two-way voice communication must support volume gain, hearing aid compatibility, and TTY connectivity.
- 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
- 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
Software including applications, web content, electronic documents, and authoring tools shall conform to applicable software accessibility requirements covering interoperability and platform accessibility services.
- Software accessibility conformance report
- Platform accessibility API usage evidence
- Assistive technology compatibility testing
- VPAT for software
- Authoring tool conformance
- Custom controls without ARIA
- Platform API not used
- AT compatibility unverified
- Authoring tool produces inaccessible output
Hardware that transmits, receives, processes, or stores information and communication shall conform to applicable hardware requirements including operable parts, biometrics, and connections.
- Hardware accessibility conformance reports
- VPAT for hardware products
- Operable parts testing records
- Biometric alternative documentation
- Standard connection verification
- Hardware VPAT missing
- No alternative to biometrics
- Proprietary connections only
- Operable parts not tested
Software must support interoperability with assistive technology through platform accessibility services.
- 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
- 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
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.
- AT compatibility test reports
- Platform accessibility setting preservation tests
- No override evidence for accessibility features
- Screen reader integration testing
- Switch device compatibility
- Software overrides high contrast
- AT not detected
- Platform settings ignored
- Switch input blocked
Applications must provide user preferences for accessibility settings and support assistive technology access to content.
- Accessibility Conformance Reports (ACR) using VPAT template
- WCAG 2.0 Level AA test results for digital content
- Procurement market research records documenting accessibility evaluation
- 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
Authoring tools must be accessible and support the creation of accessible content where possible.
- 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
- 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
Documentation and support services must describe accessibility features and be provided in accessible formats.
- WCAG 2.0 Level AA test results for digital content
- Procurement market research records documenting accessibility evaluation
- Remediation plans for non-conformant ICT 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
- Real-time text functionality absent from two-way voice products
Support services including help desks must accommodate communication needs of users with disabilities.
- 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
- 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
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.
- Support staff accessibility training records
- TTY or relay service availability
- Multiple contact channel options
- Response time parity for accessible channels
- Knowledge base on accessibility
- Phone only support
- TTY or relay unavailable
- Support untrained on accessibility
- Longer response times for accessible channels
Chapter 7: Referenced Standards
ICT providing real-time text must support interoperability, concurrent voice and text, and visual indicators.
- Training records for content authors and procurement officers
- Alternative means of access documentation for legacy systems
- Accessibility Conformance Reports (ACR) using VPAT template
- 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
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.
- Section 508 evidence for FIVEOEIGHT-4
- WCAG conformance + VPAT partial
Functional Performance
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.
- Section 508 evidence for FIVEOEIGHT-1
- WCAG conformance + VPAT partial
Hardware
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.
- Section 508 evidence for FIVEOEIGHT-2
- WCAG conformance + VPAT partial
Software
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.
- Section 508 evidence for FIVEOEIGHT-3
- WCAG conformance + VPAT partial
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.