EBooks
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 Documentatio
- 603 Support Service
- 302 Functional Performance Criteri
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.
E502.2 Documented Accessibility Features -
Software with platform features defined in platform documentation as accessibility features shall conform to 502.2.
E502.3 Accessibility Services -
Platform software and software tools that are provided by the platform developer shall provide a documented set of accessibility services that support applications running on the platform to interoperate with assistive technology and shall conform to 502.3. Applications that are also platforms shall expose the underlying platform accessibility services or implement other documented accessibility services.
E502.4 Platform Accessibility Features -
Platforms and platform software shall conform to the requirements in ANSI/HFES 200.2, Human Factors Engineering of Software User Interfaces — Part 2: Accessibility (2008) (incorporated by reference, see 702.4.1) listed below:
- Section 9.3.3 Enable sequential entry of multiple (chorded) keystrokes;
- Section 9.3.4 Provide adjustment of delay before key acceptance;
- Section 9.3.5 Provide adjustment of same-key double-strike acceptance;
- Section 10.6.7 Allow users to choose visual alternative for audio output;
- Section 10.6.8 Synchronize audio equivalents for visual events;
- Section 10.6.9 Provide speech output services; and
- Section 10.7.1 Display any captions provided.
E503.3 Alternative User Interfaces -
Where an application provides an alternative user interface that functions as assistive technology, the application shall use platform and other industry standard accessibility services.
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.
