Name of Product: E2 Solutions
Description of Product: E2 Solutions provides travel and expense management for organizations following federal travel regulations. Users can create and track travel authorizations, book reservations, get approvals, submit expense reports, and receive reimbursements.
Platform: Web
Website: https://e2.gov.cwtsatotravel.com/
Accessibility contact for more information: Agency POC or Help Desk
For assistance with this report, please email us.
Chapter 1 Application and Administration
Section 508 (ICT Refresh)
Chapter 2 Scoping Requirements
| Criteria |
|---|
| E207.2 WCAG Conformance. User interface components and content of platforms and applications shall conform to Level A and Level AA Success Criteria and Conformance Requirements specified for web pages in WCAG 2.0. |
Information and user interface components must be presentable to users in ways they can perceive.
Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language.
| Criteria | Supporting Feature | Remarks and Explanations |
|---|---|---|
| 1.1.1 Non-text Content: All non-text content that is presented to the user has a text alternative that serves the equivalent purpose, except in situations listed in WCAG 2.0 1.1.1. | Supported |
Provide alternatives for time-based media.
| Criteria | Supporting Feature | Remarks and Explanations |
|---|---|---|
| 1.2.1 Audio-only and Video-only (Prerecorded): For prerecorded audio-only and prerecorded video-only media, the following are true, except when the audio or video is a media alternative for text and is clearly labeled as such: • Prerecorded Audio-only: An alternative for time-based media is provided that presents equivalent information for prerecorded audio-only content. • Prerecorded Video-only: Either an alternative for time-based media or an audio track is provided that presents equivalent information for prerecorded video-only content. | Not Applicable | |
| 1.2.2 Captions (Prerecorded): Captions are provided for all prerecorded audio content in synchronized media, except when the media is a media alternative for text and is clearly labeled as such. | Not Applicable | |
| 1.2.3 Audio Description or Media Alternative (Prerecorded): An alternative for time-based media or audio description of the prerecorded video content is provided for synchronized media, except when the media is a media alternative for text and is clearly labeled as such. | Not Applicable | |
| 1.2.4 Captions (Live): Captions are provided for all live audio content in synchronized media. | Not Applicable | |
| 1.2.5 Audio Description (Prerecorded): Audio description is provided for all prerecorded video content in synchronized media. | Not Applicable |
Create content that can be presented in different ways (for example simpler layout) without losing information or structure.
| Criteria | Supporting Feature | Remarks and Explanations |
|---|---|---|
| 1.3.1 Info and Relationships: Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. | Supported | |
| 1.3.2 Meaningful Sequence: When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined. | Supported | |
| 1.3.3 Sensory Characteristics: Instructions provided for understanding and operating content do not rely solely on sensory characteristics of components such as shape, size, visual location, orientation, or sound. | Supported |
Make it easier for users to see and hear content including separating foreground from background.
| Criteria | Supporting Feature | Remarks and Explanations |
|---|---|---|
| 1.4.1 Use of Color: Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. | Supported | |
| 1.4.2 Audio Control: If any audio on a Web page plays automatically for more than 3 seconds, either a mechanism is available to pause or stop the audio, or a mechanism is available to control audio volume independently from the overall system volume level. | Not Applicable | |
| 1.4.3 Contrast (Minimum): The visual presentation of text and images of text has a contrast ratio of at least 4.5:1, except for situations listed in WCAG 2.0 1.4.3. | Supported | |
| 1.4.4 Resize text: Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality. | Supported | |
| 1.4.5 Images of Text: If the technologies being used can achieve the visual presentation, text is used to convey information rather than images of text except for the following: Customizable: The image of text can be visually customized to the user’s requirements; Essential: A particular presentation of text is essential to the information being conveyed. |
Supported |
User interface components and navigation must be operable.
Make all functionality available from a keyboard.
| Criteria | Supporting Feature | Remarks and Explanations |
|---|---|---|
| 2.1.1 Keyboard: All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user’s movement and not just the endpoints. | Supports with Exceptions | The majority of CWTSatoTravel ETS2 E2 Solutions application enables complete navigation of application components via the keyboard. However, file upload for receipts & attachments is broken in Chrome for keyboard-only users. Using another browser for file uploads is recommended, as IE11+ and Firefox do not have the defect. |
| 2.1.2 No Keyboard Trap: If keyboard focus can be moved to a component of the page using a keyboard interface, then focus can be moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or tab keys or other standard exit methods, the user is advised of the method for moving focus away. | Supported |
Provide users enough time to read and use content.
| Criteria | Supporting Feature | Remarks and Explanations |
|---|---|---|
| 2.2.1 Timing Adjustable: For each time limit that is set by the content, at least one of the instances in WCAG 2.0 2.2.1 is true. | Supported | |
| 2.2.2 Pause, Stop, Hide: For moving, blinking, scrolling, or auto-updating information, all of the following are true: • Moving, blinking, scrolling: For any moving, blinking or scrolling information that (1) starts automatically, (2) lasts more than five seconds, and (3) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it unless the movement, blinking, or scrolling is part of an activity where it is essential; and • Auto-updating: For any auto-updating information that (1) starts automatically and (2) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it or to control the frequency of the update unless the auto-updating is part of an activity where it is essential. | Not Applicable |
Do not design content in a way that is known to cause seizures.
| Criteria | Supporting Feature | Remarks and Explanations |
|---|---|---|
| 2.3.1 Three Flashes or Below Threshold: Web pages do not contain anything that flashes more than three times in any one second period, or the flash is below the general flash and red flash thresholds. | Supported |
Provide ways to help users navigate, find content, and determine where they are.
| Criteria | Supporting Feature | Remarks and Explanations |
|---|---|---|
| 2.4.1 Bypass Blocks: A mechanism is available to bypass blocks of content that are repeated on multiple Web pages. | Supported | |
| 2.4.2 Page Titled: Web pages have titles that describe topic or purpose. | Supported | |
| 2.4.3 Focus Order: If a Web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability. | Supported | |
| 2.4.4 Link Purpose (In Context): The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general. | Supported | |
| 2.4.5 Multiple Ways: More than one way is available to locate a Web page within a set of Web pages except where the Web Page is the result of, or a step in, a process. | Supported | |
| 2.4.6 Headings and Labels: Headings and labels describe topic or purpose. | Supported | |
| 2.4.7 Focus Visible: Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible. | Supported |
Information and the operation of user interface must be understandable.
Make text content readable and understandable.
| Criteria | Supporting Feature | Remarks and Explanations |
|---|---|---|
| 3.1.1 Language of Page: The default human language of each Web page can be programmatically determined. | Supported | |
| 3.1.2 Language of Parts: The human language of each passage or phrase in the content can be programmatically determined except for proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text. | Supported |
Make Web pages appear and operate in predictable ways.
| Criteria | Supporting Feature | Remarks and Explanations |
|---|---|---|
| 3.2.1 On Focus: When any component receives focus, it does not initiate a change of context. | Supported | |
| 3.2.2 On Input: Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behavior before using the component | Supported | |
| 3.2.3 Consistent Navigation: Navigational mechanisms that are repeated on multiple Web pages within a set of Web pages occur in the same relative order each time they are repeated, unless a change is initiated by the user. | Supported | |
| 3.2.4 Consistent Identification: Components that have the same functionality within a set of Web pages are identified consistently. | Supported |
Help users avoid and correct mistakes.
| Criteria | Supporting Feature | Remarks and Explanations |
|---|---|---|
| 3.3.1 Error Identification: If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text. | Supported | |
| 3.3.2 Labels or Instructions: Labels or instructions are provided when content requires user input. | Supported | |
| 3.3.3 Error Suggestion: If an input error is automatically detected and suggestions for correction are known, then the suggestions are provided to the user, unless it would jeopardize the security or purpose of the content. | Supported | |
| 3.3.4 Error Prevention (Legal, Financial, Data): For Web pages that cause legal commitments or financial transactions for the user to occur, that modify or delete user-controllable data in data storage systems, or that submit user test responses, at least one of the following is true: 1. Reversible: Submissions are reversible. 2. Checked: Data entered by the user is checked for input errors and the user is provided an opportunity to correct them. 3. Confirmed: A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission. | Supported |
Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies.
Maximize compatibility with current and future user agents, including assistive technologies.
| Criteria | Supporting Feature | Remarks and Explanations |
|---|---|---|
| 4.1.1 Parsing: In content implemented using markup languages, elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique, except where the specifications allow these features. | Supported | |
| 4.1.2 Name, Role, Value: For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies. | Supported |
301.1 Scope The requirements of Chapter 3 shall apply to ICT 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.
| Criteria |
|---|
| 302.1 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. |
| 302.2 With limited vision. Where a visual mode of operation is provided, ICT shall provide at least one mode of operation that enables users to make use of limited vision. |
| 302.3 Without Perception of Color. Where a visual mode of operation is provided, ICT shall provide at least one visual mode of operation that does not require user perception of color. |
| 302.4 Without Hearing. Where an audible mode of operation is provided, ICT shall provide at least one mode of operation that does not require user hearing. |
| 302.5 With Limited Hearing. Where an audible mode of operation is provided, ICT shall provide at least one mode of operation that enables users to make use of limited hearing. |
| 302.6 Without Speech. Where speech is used for input, control, or operation, ICT shall provide at least one mode of operation that does not require user speech. |
| 302.7 With Limited Manipulation. Where a manual mode of operation is provided, ICT shall provide at least one mode of operation that does not require fine motor control or simultaneous manual operations. |
| 302.8 With Limited Reach and Strength. Where a manual mode of operation is provided, ICT shall provide at least one mode of operation that is operable with limited reach and limited strength. |
| 302.9 With Limited Language, Cognitive, and Learning Abilities. ICT shall provide features making its use by individuals with limited cognitive, language, and learning abilities simpler and easier. |
401.1 Scope. 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.
EXCEPTION: Hardware that is assistive technology shall not be required to conform to the requirements of this chapter.
402.1 General. ICT with closed functionality shall be operable without requiring the user to attach or install assistive technology other than personal headsets or other audio couplers, and shall conform to 402.
| Criteria | Supporting Feature | Remarks and Explanations |
|---|---|---|
| 402.2 Speech-Output Enabled. ICT with a display screen shall be speech-output enabled for full and independent use by individuals with vision impairments. | Not Applicable | |
| 402.2.1 Information Displayed On-Screen. Speech output shall be provided for all information displayed on-screen. | Not Applicable | |
| 402.2.2 Transactional Outputs. Where transactional outputs are provided, the speech output shall audibly provide all information necessary to verify a transaction. | Not Applicable | |
| 402.2.3 Speech Delivery Type and Coordination. Speech output shall be delivered through a mechanism that is readily available to all users, including, but not limited to, an industry standard connector or a telephone handset. Speech shall be recorded or digitized human, or synthesized. Speech output shall be coordinated with information displayed on the screen. | Not Applicable | |
| 402.2.4 User Control. Speech output for any single function shall be automatically interrupted when a transaction is selected. Speech output shall be capable of being repeated and paused. | Not Applicable | |
| 402.2.5 Braille Instructions. Where speech output is required by 402.2, braille instructions for initiating the speech mode of operation shall be provided. | Not Applicable | |
| 402.3 Volume. ICT that delivers sound, including speech output required by 402.2, shall provide volume control and output amplification conforming to 402.3. | Not Applicable | |
| 402.3.1 Private Listening. Where ICT provides private listening, it shall provide a mode of operation for controlling the volume. Where ICT delivers output by an audio transducer typically held up to the ear, a means for effective magnetic wireless coupling to hearing technologies shall be provided. | Not Applicable | |
| 402.3.2 Non-private Listening. Where ICT provides non-private listening, incremental volume control shall be provided with output amplification up to a level of at least 65 dB. A function shall be provided to automatically reset the volume to the default level after every use. | Not Applicable | |
| 402.4 Characters. At least one mode of characters displayed on the screen shall be in a sans serif font. Where ICT does not provide a screen enlargement feature, characters shall be 3/16 inch (4.8 mm) high minimum based on the uppercase letter “I”. Characters shall contrast with their background with either light characters on a dark background or dark characters on a light background. | Not Applicable | |
| 402.5 Characters on Variable Message Signs. Characters on variable message signs shall conform to section 703.7 Variable Message Signs of ICC A117.1-2009 (incorporated by reference, see 702.6.1). | Not Applicable |
| Criteria | Supporting Feature | Remarks and Explanations |
|---|---|---|
| 403.1 General. Biometrics shall not be the only means for user identification or control. | Not Applicable |
| Criteria | Supporting Feature | Remarks and Explanations |
|---|---|---|
| 404.1 General. ICT that transmits or converts information or communication shall not remove non-proprietary information provided for accessibility or shall restore it upon delivery. | Not Applicable |
| Criteria | Supporting Feature | Remarks and Explanations |
|---|---|---|
| 405.1 General. 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. | Not Applicable |
| Criteria | Supporting Feature | Remarks and Explanations |
|---|---|---|
| 406.1 General. Where data connections used for input and output are provided, at least one of each type of connection shall conform to industry standard non-proprietary formats. | Not Applicable |
407.1 General. Where provided, operable parts used in the normal operation of ICT shall conform to 407.
| Criteria | Supporting Feature | Remarks and Explanations |
|---|---|---|
| 407.2 Contrast. Where provided, keys and controls shall contrast visually from background surfaces. Characters and symbols shall contrast visually from background surfaces with either light characters or symbols on a dark background or dark characters or symbols on a light background. | Not Applicable | |
| 407.3 Input Controls. At least one input control conforming to 407.3 shall be provided for each function. | See 407.3.1, 407.3.2, and 407.3.3. | |
| 407.3.1 Tactilely Discernible. Input controls shall be operable by touch and tactilely discernible without activation. | Not Applicable | |
| 407.3.2 Alphabetic Keys. Where provided, individual alphabetic keys shall be arranged in a QWERTY-based keyboard layout and the “F” and “J” keys shall be tactilely distinct from the other keys. | Not Applicable | |
| 407.3.3 Numeric Keys. Where provided, numeric keys shall be arranged in a 12-key ascending or descending keypad layout. The number five key shall be tactilely distinct from the other keys. Where the ICT provides an alphabetic overlay on numeric keys, the relationships between letters and digits shall conform to ITU-T Recommendation E.161 (incorporated by reference, see 702.7.1). | Not Applicable | |
| 407.4 Key Repeat. Where a keyboard with key repeat is provided, the delay before the key repeat feature is activated shall be fixed at, or adjustable to, 2 seconds minimum. | Not Applicable | |
| 407.5 Timed Response. Where a timed response is required, the user shall be alerted visually, as well as by touch or sound, and shall be given the opportunity to indicate that more time is needed. | Supported | The current implementation of the CWTSatoTravel ETS notifies the user of a session time-out after 15 minutes of inactivity. Users of the ETS2 E2Solutions receive an accessible five minute warning prior to the final session time-out. This warning provides functionality to extend the session time by another 15 minutes, and this extension can repeated indefinitely upon each time-out warning notification. |
| 407.6 Operation. At least one mode of operation shall be operable with one hand and shall not require tight grasping, pinching, or twisting of the wrist. The force required to activate operable parts shall be 5 pounds (22.2 N) maximum. | Not Applicable | |
| 407.7 Tickets, Fare Cards, and Keycards. Where tickets, fare cards, or keycards are provided, they shall have an orientation that is tactilely discernible if orientation is important to further use of the ticket, fare card, or keycard. | Not Applicable | |
| 407.8 Reach Height and Depth. At least one of each type of operable part of stationary ICT shall be at a height conforming to 407.8.2 or 407.8.3 according to its position established by the vertical reference plane specified in 407.8.1 for a side reach or a forward reach. Operable parts used with speech output required by 402.2 shall not be the only type of operable part complying with 407.8 unless that part is the only operable part of its type. | Not Applicable | |
| 407.8.1 Vertical Reference Plane. Operable parts shall be positioned for a side reach or a forward reach determined with respect to a vertical reference plane. The vertical reference plane shall be located in conformance to 407.8.2 or 407.8.3. | Not Applicable | |
| 407.8.1.1 Vertical Plane for Side Reach. Where a side reach is provided, the vertical reference plane shall be 48 inches (1220 mm) long minimum. | Not Applicable | |
| 407.8.1.2 Vertical Plane for Forward Reach. Where a forward reach is provided, the vertical reference plane shall be 30 inches (760 mm) long minimum. | Not Applicable | |
| 407.8.2 Side Reach. Operable parts of ICT providing a side reach shall conform to 407.8.2.1 or 407.8.2.2. The vertical reference plane shall be centered on the operable part and placed at the leading edge of the maximum protrusion of the ICT within the length of the vertical reference plane. Where a side reach requires a reach over a portion of the ICT, the height of that portion of the ICT shall be 34 inches (865 mm) maximum. | Not Applicable | |
| 407.8.2.1 Unobstructed Side Reach. Where the operable part is located 10 inches (255 mm) or less beyond the vertical reference plane, the operable part shall be 48 inches (1220 mm) high maximum and 15 inches (380 mm) high minimum above the floor. | Not Applicable | |
| 407.8.2.2 Obstructed Side Reach. Where the operable part is located more than 10 inches (255 mm), but not more than 24 inches (610 mm), beyond the vertical reference plane, the height of the operable part shall be 46 inches (1170 mm) high maximum and 15 inches (380 mm) high minimum above the floor. The operable part shall not be located more than 24 inches (610 mm) beyond the vertical reference plane. | Not Applicable | |
| 407.8.3 Forward Reach. Operable parts of ICT providing a forward reach shall conform to 407.8.3.1 or 407.8.3.2. The vertical reference plane shall be centered, and intersect with, the operable part. Where a forward reach allows a reach over a portion of the ICT, the height of that portion of the ICT shall be 34 inches (865 mm) maximum. | Not Applicable | |
| 407.8.3.1 Unobstructed Forward Reach. Where the operable part is located at the leading edge of the maximum protrusion within the length of the vertical reference plane of the ICT, the operable part shall be 48 inches (1220 mm) high maximum and 15 inches (380 mm) high minimum above the floor. | Not Applicable | |
| 407.8.3.2 Obstructed Forward Reach. Where the operable part is located beyond the leading edge of the maximum protrusion within the length of the vertical reference plane, the operable part shall conform to 407.8.3.2. The maximum allowable forward reach to an operable part shall be 25 inches (635 mm). | Not Applicable | |
| 407.8.3.2.1 Operable Part Height for ICT with Obstructed Forward Reach. The height of the operable part shall conform to Table 407.8.3.2.1: Reach Depth :: Operable Part Height Less than 20 inches (510 mm) :: 48 inches (1220 mm) maximum 20 inches (510 mm) to 25 inches (635 mm) :: 44 inches (1120 mm) maximum |
Not Applicable | |
| 407.8.3.2.2 Knee and Toe Space under ICT with Obstructed Forward Reach. Knee and toe space under ICT shall be 27 inches (685 mm) high minimum, 25 inches (635 mm) deep maximum, and 30 inches (760 mm) wide minimum and shall be clear of obstructions. | Not Applicable |
408.1 General. Where provided, display screens shall conform to 408.
| Criteria | Supporting Feature | Remarks and Explanations |
|---|---|---|
| 408.2 Visibility. Where stationary ICT provides one or more display screens, at least one of each type of display screen shall be visible from a point located 40 inches (1015 mm) above the floor space where the display screen is viewed. | Not Applicable | |
| 408.3 Flashing Where ICT emits lights in flashes, there shall be no more than three flashes in any one-second period. | Not Applicable |
| Criteria | Supporting Feature | Remarks and Explanations |
|---|---|---|
| 409.1 General. Where provided, status indicators shall be discernible visually and by touch or sound. | Not Applicable |
| Criteria | Supporting Feature | Remarks and Explanations |
|---|---|---|
| 410.1 General. 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. | Not Applicable |
| Criteria | Supporting Feature | Remarks and Explanations |
|---|---|---|
| 411.1 General. Where provided, audible signals or cues shall not be used as the only means of conveying information, indicating an action, or prompting a response. | Not Applicable |
412.1 General. ICT that provides two-way voice communication shall conform to 412.
| Criteria | Supporting Feature | Remarks and Explanations |
|---|---|---|
| 412.2 Volume Gain. ICT that provides two-way voice communication shall conform to 412.2.1 or 412.2.2. | See 412.2.2 | |
| 412.2.1 Volume Gain for Wireline Telephones. Volume gain conforming to 47 CFR 68.317 shall be provided on analog and digital wireline telephones. | Not Applicable | |
| 412.2.2 Volume Gain for Non-Wireline ICT. A method for increasing volume shall be provided for non-wireline ICT. | Not Applicable | |
| 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. | See 412.3.1 | |
| 412.3.1 Wireless Handsets. ICT in the form of wireless handsets shall conform to ANSI/IEEE C63.19-2011 (incorporated by reference, see 702.5.1). | Not Applicable | |
| 412.3.2 Wireline Handsets. ICT in the form of wireline handsets, including cordless handsets, shall conform to TIA-1083-B (incorporated by reference, see702.9.1). | Not Applicable | |
| 412.4 Digital Encoding of Speech. ICT in IP-based networks shall transmit and receive speech that is digitally encoded in the manner specified by ITU-T Recommendation G.722.2 (incorporated by reference, see 702.7.2) or IETF RFC 6716 (incorporated by reference, see 702.8.1). | Not Applicable | |
| 412.5 Real-Time Text Functionality. Reserved. | Not Applicable | |
| 412.6 Caller ID. Where provided, caller identification and similar telecommunications functions shall be visible and audible. | Not Applicable | |
| 412.7 Video Communication. Where ICT provides real-time video functionality, the quality of the video shall be sufficient to support communication using sign language. | Not Applicable |
413.1 General. Where ICT displays or processes video with synchronized audio, ICT shall provide closed caption processing technology that conforms to 413.1.1 or 413.1.2.
| Criteria | Supporting Feature | Remarks and Explanations |
|---|---|---|
| 413.1.1 Decoding and Display of Closed Captions. Players and displays shall decode closed caption data and support display of captions. | Not Applicable | |
| 413.1.2 Pass-Through of Closed Caption Data. Cabling and ancillary equipment shall pass through caption data. | Not Applicable |
414.1 General. Where ICT displays or processes video with synchronized audio, ICT shall provide audio description processing technology conforming to 414.1.1 or 414.1.2.
| Criteria | Supporting Feature | Remarks and Explanations |
|---|---|---|
| 414.1.1 Digital Television Tuners. Digital television tuners shall provide audio description processing that conforms to ATSC A/53 Digital Television Standard, Part 5 (2014) (incorporated by reference, see 702.2.1). Digital television tuners shall provide processing of audio description when encoded as a Visually Impaired (VI) associated audio service that is provided as a complete program mix containing audio description according to the ATSC A/53 standard. | Not Applicable | |
| 414.1.2 Other ICT. ICT other than digital television tuners shall provide audio description processing. | Not Applicable |
415.1 General. Where ICT displays video with synchronized audio, ICT shall provide user controls for closed captions and audio descriptions conforming to 415.1.
| Criteria | Supporting Feature | Remarks and Explanations |
|---|---|---|
| 415.1.1 Caption Controls. Where ICT provides operable parts for volume control, ICT shall also provide operable parts for caption selection. | Not Applicable | |
| 415.1.2 Audio Description Controls. Where ICT provides operable parts for program selection, ICT shall also provide operable parts for the selection of audio description. | Not Applicable |
501.1 Scope. 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.
EXCEPTION: Where Web applications do not have access to platform accessibility services and do not include components that have access to platform accessibility services, they shall not be required to conform to 502 or 503 provided that they conform to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 (incorporated by reference, see 702.10.1).
502.1 General. 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.
| Criteria | Supporting Feature | Remarks and Explanations |
|---|---|---|
| 502.2.1 User Control of Accessibility Features. Platform software shall provide user control over platform features that are defined in the platform documentation as accessibility features. | Not Applicable | |
| 502.2.2 No Disruption of Accessibility Features. Software shall not disrupt platform features that are defined in the platform documentation as accessibility features. | Supported | |
| 502.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. | Not Applicable | |
| 502.3.1 Object Information. The object role, state(s), properties, boundary, name, and description shall be programmatically determinable. | Supported | |
| 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. | Not Applicable | |
| 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. | Not Applicable | |
| 502.3.4 Values. Any current value(s), and any set or range of allowable values associated with an object, shall be programmatically determinable. | Not Applicable | |
| 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. | Not Applicable | |
| 502.3.6 Label Relationships. Any relationship that a component has as a label for another component, or of being labeled by another component, shall be programmatically determinable. | Not Applicable | |
| 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. | Not Applicable | |
| 502.3.8 Text. The content of text objects, text attributes, and the boundary of text rendered to the screen, shall be programmatically determinable. | Not Applicable | |
| 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. | Not Applicable | |
| 502.3.10 List of Actions. A list of all actions that can be executed on an object shall be programmatically determinable. | Not Applicable | |
| 502.3.11 Actions on Objects. Applications shall allow assistive technology to programmatically execute available actions on objects. | Not Applicable | |
| 502.3.12 Focus Cursor. Applications shall expose information and mechanisms necessary to track focus, text insertion point, and selection attributes of user interface components. | Supported | |
| 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. | Not Applicable | |
| 502.3.14 Event Notification. 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. | Not Applicable | |
| 502.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. |
Not Applicable |
503.1 General. Applications shall conform to 503.
| Criteria | Supporting Feature | Remarks and Explanations |
|---|---|---|
| 503.2 User Preferences. Applications shall permit user preferences from platform settings for color, contrast, font type, font size, and focus cursor. | Supported | |
| 503.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. | Supported | |
| 503.4 User Controls for Captions and Audio Description. Where ICT displays video with synchronized audio, ICT shall provide user controls for closed captions and audio descriptions conforming to 503.4. | See 503.4.1 and 503.4.2 | |
| 503.4.1 Caption Controls. Where user controls are provided for volume adjustment, ICT shall provide user controls for the selection of captions at the same menu level as the user controls for volume or program selection. | Not Applicable | |
| 503.4.2 Audio Description Controls. Where user controls are provided for program selection, ICT shall provide user controls for the selection of audio descriptions at the same menu level as the user controls for volume or program selection. | Not Applicable |
504.1 General. 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.
| Criteria | Supporting Feature | Remarks and Explanations |
|---|---|---|
| 504.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. | Not Applicable | |
| 504.2.1 Preservation of Information Provided for Accessibility in Format Conversion. Authoring tools shall, when converting content from one format to another or saving content in multiple formats, preserve the information required for accessibility to the extent that the information is supported by the destination format. | Not Applicable | |
| 504.2.2 PDF Export. 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). | Not Applicable | |
| 504.3 Prompts. 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. | Not Applicable | |
| 504.4 Templates. 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. | Not Applicable |
602.1 General. Documentation that supports the use of ICT shall conform to 602.
| Criteria | Supporting Feature | Remarks and Explanations |
|---|---|---|
| 602.2 Accessibility and Compatibility Features. Documentation shall list and explain how to use the accessibility and compatibility features required by Chapters 4 and 5. Documentation shall include accessibility features that are built-in and accessibility features that provide compatibility with assistive technology. | Not Applicable | |
| 602.3 Electronic Support Documentation. Documentation in electronic format, including Web-based self-service support, shall conform to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 (incorporated by reference, see 702.10.1). | Supported | |
| 602.4 Alternate Formats for Non-Electronic Support Documentation. Where support documentation is only provided in non-electronic formats, alternate formats usable by individuals with disabilities shall be provided upon request. | Supported through equivalent facilitation | Any media presentations (e.g. training presentations) can be offered in a fully equivalent accessible presentation. |
603.1 General. ICT support services including, but not limited to, help desks, call centers, training services, and automated self-service technical support, shall conform to 603.
| Criteria | Supporting Feature | Remarks and Explanations |
|---|---|---|
| 603.2 Information on Accessibility and Compatibility Features. ICT support services shall include information on the accessibility and compatibility features required by 602.2. | Not Applicable | |
| 603.3 Accommodation of Communication Needs. Support services shall be provided directly to the user or through a referral to a point of contact. Such ICT support services shall accommodate the communication needs of individuals with disabilities. | Supported | Criteria apply to phone-based support elements of the ETS2 if the Agency provides special telephone equipment or services for the hearing impaired. All ETS2 E2 Solutions call centers (telephony enabled points of contact) support industry standard TTY signaling protocols (Baudot). |