Electronic Documents
ICT Accessibility Requirements Statement per the Revised Section 508 of the Rehabilitation Act
General Exceptions
Technical Criteria:
Where components of ICT are software and transmit information or have a user interface, such components shall conform to E207 and the requirements in Chapter 5
User interface components, as well as the content of platforms and applications, shall conform to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 (incorporated by reference, see 702.10.1).
When Applying WCAG to Non-Web Software For non-Web software, wherever the term “Web page” or “page” appears in WCAG 2.0 Level A and AA Success Criteria and Conformance Requirements, the term “software” shall be substituted for the terms “Web page” and “page”. In addition, in Success Criterion in 1.4.2, the phrase “in software” shall be substituted for the phrase “on a Web page.”
E207.3 Complete Process for Non-Web Software -
Where non-Web software requires multiple steps to accomplish an activity, all software related to the activity to be accomplished shall conform to WCAG 2.0 as specified in E207.2.
Electronic Content
Technical Criteria:
Electronic content shall comply with E205.
E205.3 Agency Official Communication -
Electronic content that is not public facing shall conform to the accessibility requirements specified in E205.4 when such content constitutes official business and is communicated by an agency through one or more of the following:
- An emergency notification;
- An initial or final decision adjudicating an administrative claim or proceeding;
- An internal or external program or policy announcement;
- A notice of benefits, program eligibility, employment opportunity, or personnel action;
- A formal acknowledgement of receipt;
- A survey questionnaire;
- A template or form;
- Educational or training materials; or
- Intranet content designed as a Web page.
E205.4 Accessibility Standard (WCAG 2.0) -
Electronic content that is not public facing shall conform to the accessibility requirements specified in E205.4 when such content constitutes official business and is communicated by an agency through one or more of the following:
- An emergency notification;
- An initial or final decision adjudicating an administrative claim or proceeding;
- An internal or external program or policy announcement;
- A notice of benefits, program eligibility, employment opportunity, or personnel action;
- A formal acknowledgement of receipt;
- A survey questionnaire;
- A template or form;
- Educational or training materials; or
- Intranet content designed as a Web page.
E205.4.1 Word Substitution when Applying WCAG to non-Web Documents -
For non-Web documents, wherever the term “Web page” or “page” appears in WCAG 2.0 Level A and AA Success Criteria and Conformance Requirements, the term “document” shall be substituted for the terms “Web page” and “page”. In addition, in Success Criterion in 1.4.2, the phrase “in a document” shall be substituted for the phrase “on a Web page”..
The following standards are applicable:
- All WCAG A & AA Success Criteria apply.
- 602 Support Documentation
- 603 Support Services
- 302 Functional Performance Criteria
The following standards are applicable:
- All WCAG A & AA Success Criteria - except
- 2.4.1 Bypass Blocks
- 2.4.5 Multiple Ways
- 3.2.3 Consistent Navigation
- 3.2.4 Consistent Identification
- 602 Support Documentation
- 603 Support Services
- 302 Functional Performance Criteria
302 Functional Performance Criteria
Software
Technical Criteria:
The requirements of Chapter 5 shall apply to software where required by 508 Chapter 2 (Scoping Requirements), 255 Chapter 2 (Scoping Requirements), and where otherwise referenced in any other chapter of the Revised 508 Standards or Revised 255 Guidelines.
Software shall interoperate with assistive technology and shall conform to 502.
Where an application is an authoring tool, the application shall conform to 504 to the extent that information required for accessibility is supported by the destination format.
E504.2 Content Creation or Editing -
Authoring tools shall provide a mode of operation to create or edit content that conforms to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 (incorporated by reference, see 702.10.1) for all supported features and, as applicable, to file formats supported by the authoring tool. Authoring tools shall permit authors the option of overriding information required for accessibility.
E504.2.1 Preservation of Information Provided for Accessibility in Format Conv
Authoring tools capable of exporting PDF files that conform to ISO 32000-1:2008 (PDF 1.7) shall also be capable of exporting PDF files that conform to ANSI/AIIM/ISO 14289-1:2016 (PDF/UA-1) (incorporated by reference, see 702.3.1).
Authoring tools shall provide a mode of operation that prompts authors to create content that conforms to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 (incorporated by reference, see 702.10.1) for supported features and, as applicable, to file formats supported by the authoring tool.
Where templates are provided, templates allowing content creation that conforms to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 (incorporated by reference, see 702.10.1) shall be provided for a range of template uses for supported features and, as applicable, to file formats supported by the authoring tool.
502.2 Documented Accessibility Features -
Software with platform features defined in platform documentation as accessibility features shall conform to 502.2.
502.2.2 No Disruption of Accessibility Features -
Software shall not disrupt platform features that are defined in the platform documentation as accessibility features.
The object role, state(s), properties, boundary, name, and description shall be programmatically determinable.
502.3.2 Modification of Object Information -
States and properties that can be set by the user shall be capable of being set programmatically, including through assistive technology.
502.3.3 Row, Column, and Headers -
If an object is in a data table, the occupied rows and columns, and any headers associated with those rows or columns, shall be programmatically determinable.
Any current value(s), and any set or range of allowable values associated with an object, shall be programmatically determinable.
502.3.5 Modification of Values -
Values that can be set by the user shall be capable of being set programmatically, including through assistive technology.
Any relationship that a component has as a label for another component, or of being labeled by another component, shall be programmatically determinable.
502.3.7 Hierarchical Relationships -
Any hierarchical (parent-child) relationship that a component has as a container for, or being contained by, another component shall be programmatically determinable.
The content of text objects, text attributes, and the boundary of text rendered to the screen, shall be programmatically determinable.
502.3.9 Modification of Text -
Text that can be set by the user shall be capable of being set programmatically, including through assistive technology.
Applications shall allow assistive technology to programmatically execute available actions on objects.
Applications shall expose information and mechanisms necessary to track focus, text insertion point, and selection attributes of user interface components.
502.3.13 Modification of Focus Cursor -
Focus, text insertion point, and selection attributes that can be set by the user shall be capable of being set programmatically, including through the use of assistive technology.
Notification of events relevant to user interactions, including but not limited to, changes in the component’s state(s), value, name, description, or boundary, shall be available to assistive technology.
Applications shall conform to 503.
Applications shall permit user preferences from platform settings for color, contrast, font type, font size, and focus cursor.
Instructions
The Accessibility Requirements Report should be incorporated into the solicitation requirements document (SOO, SOW, PWS, etc.). Please go to the Revised 508 Standards Toolkit (https://section508.gov/manage/program-roadmap) for further information on the procurement process.
