IP Telephones
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.
Hardware
Technical Criteria:
Where components of ICT are hardware and transmit information or have a user interface, such components shall conform to the requirements in Chapter 4.
The same degree of privacy of input and output shall be provided to all individuals. When speech output required by 402.2 is enabled, the screen shall not blank automatically.
Where provided, status indicators shall be discernible visually and by touch or sound.
Where provided, color coding shall not be used as the only means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.
ICT that provides two-way voice communication shall conform to 412.
ICT that provides two-way voice communication shall conform to 412.2.1 or 412.2.2.
E412.2.1 Volume Gain for Wireline Telephones -
Volume gain conforming to 47 CFR 68.317 shall be provided on analog and digital wireline telephones.
412.3 Interference Reduction and Magnetic Coupling -
Where ICT delivers output by a handset or other type of audio transducer that is typically held up to the ear, ICT shall reduce interference with hearing technologies and provide a means for effective magnetic wireless coupling in conformance with 412.3.1 or 412.3.2.
ICT in the form of wireless handsets shall conform to ANSI/IEEE C63.19-2011 (incorporated by reference, see 702.5.1).
ICT in the form of wireline handsets, including cordless handsets, shall conform to TIA-1083-B (incorporated by reference, see702.9.1).
Where provided, caller identification and similar telecommunications functions shall be visible and audible.
The requirements of Chapter 4 shall apply to ICT that is hardware 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.
Exceptions:
E412.2 Volume Gain -
ICT conforming to 412.2 shall not be required to conform to 402.3.
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.
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/refresh-toolkit) for further information on the procurement process.
