Functional Accessibility Requirements
There is currently no content classified with this term.
5.1. Closed functionality
ICT has closed functionality for many reasons, including design or policy. Some of the functionality of products can be closed because the product is self-contained and users are precluded from adding peripherals or software in order to access that functionality.
ICT may have closed functionality in practice even though the ICT was not designed, developed or supplied to be closed.
Computers that do not allow end-users to adjust settings or install software are functionally closed.
Where ICT has closed functionality, it shall meet the requirements set out in clauses 5.2 to 13, as applicable.
Where ICT has closed functionality, that closed functionality shall be operable without requiring the user to attach, connect or install assistive technology and shall conform to the generic requirements of clauses 5.1.3 to 5.1.7 as applicable. Personal headsets and induction loops shall not be classed as assistive technology for the purpose of this clause.
Where visual information is needed to enable the use of those functions of ICT that are closed to assistive technologies for screen reading, ICT shall provide at least one mode of operation using non-visual access to enable the use of those functions.
Where auditory output is provided as non-visual access to closed functionality, the auditory output shall be delivered:
- either directly by a mechanism included in or provided with the ICT;
- or by a personal headset that can be connected through a 3,5 mm audio jack, or an industry standard connection, without requiring the use of vision
Where auditory output is provided as non-visual access to closed functionality, and where information is displayed on the screen, the ICT should provide auditory information that allows the user to correlate the audio with the information displayed on the screen.
Where speech output is provided as non-visual access to closed functionality, the speech output shall be capable of being interrupted and repeated when requested by the user, where permitted by security requirements.
Where speech output is provided as non-visual access to closed functionality, the ICT shall interrupt current speech output when a user action occurs and when new speech output begins.
Where ICT presents non-text content, the alternative for non-text content shall be presented to users via speech output unless the non-text content is pure decoration or is used only for visual formatting. The speech output for non-text content shall follow the guidance for "text alternative" described in WCAG 2.0 [4] Success Criterion 1.1.1.
Where pre-recorded video content is needed to enable the use of closed functions of ICTand where speech output is provided as non-visual access to closed functionality, the speech output shall present equivalent information for the pre-recorded video content.
<p>Where auditory output is provided as non-visual access to closed functionality, and the characters displayed are masking characters, the auditory output shall not be a spoken version of the characters entered unless the auditory output is known to be delivered only to a mechanism for private listening, or the user explicitly chooses to allow non-private auditory output.</p>
Where auditory output is provided as non-visual access to closed functionality, and the output contains data that is considered to be private according to the applicable privacy policy, the corresponding auditory output shall only be delivered through a mechanism for private listening that can be connected without requiring the use of vision, or through any other mechanism explicitly chosen by the user.
Where auditory output is provided as non-visual access to closed functionality, the ICTshall not automatically play, at the same time, any interfering audible output that lasts longer than three seconds.
Where auditory output is provided as non-visual access to closed functionality and is delivered through a mechanism for private listening, ICT shall provide at least one non-visual mode of operation for controlling the volume.
Where auditory output is provided as non-visual access to closed functionality and is delivered through speakers on ICT, a non-visual incremental volume control shall be provided with output amplification up to a level of at least 65 dBA (-29 dBPaA).
Where auditory output is provided as non-visual access to closed functionality, a function that resets the volume to be at a level of 65 dBA or less after every use, shall be provided, unless the ICT is dedicated to a single user.
Where speech output is provided as non-visual access to closed functionality, speech output shall be in the same human language as the displayed content provided, except:
a) 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;
b) where the content is generated externally and not under the control of the ICT vendor, clause 5.1.3.14 shall not be required to apply for languages not supported by the ICT's speech synthesizer;
c) for displayed languages that cannot be selected using non-visual access;
d) where the user explicitly selects a speech language that is different from the language of the displayed content.
Where speech output is provided as non-visual access to closed functionality and an input error is automatically detected, speech output shall identify and describe the item that is in error.
Where ICT is closed to visual access and provides receipts, tickets or other outputs as a result of a self-service transaction, speech output shall be provided which shall include all information necessary to complete or verify the transaction. In the case of ticketing machines, printed copies of itineraries and maps shall not be required to be audible.
Where any functionality of ICT is closed to the text enlargement features of platform or assistive technology, the ICT shall provide a mode of operation where the text and images of text necessary for all functionality is displayed in such a way that a non-accented capital "H" subtends an angle of at least 0,7 degrees at a viewing distance specified by the supplier.
The subtended angle, in degrees, may be calculated from:
Ψ = (180 x 60 x H) / (π x D)
Where:
- ψ is the subtended angle
- H is the height of the text
- D is the viewing distance.
- D and H are expressed in the same units
Where pre-recorded auditory information is needed to enable the use of closed functions of ICT, the ICT shall provide visual information that is equivalent to the pre-recorded auditory output.
Where ICT functionality is closed to keyboards or keyboard interfaces, all functionality shall be operable without vision as required by clause 5.1.3.
Where ICT functionality is closed to keyboards or keyboard interfaces and where input focus can be moved to a user interface element, it shall be possible to move the input focus away from that element using the same mechanism, in order to avoid trapping the input focus.
5.2. Activation of accessibility features
Where ICT has documented accessibility features, it shall be possible to activate those documented accessibility features that are required to meet a specific need without relying on a method that does not support that need.
5.3. Biometrics
Where ICT uses biological characteristics, it shall not rely on the use of a particular biological characteristic as the only means of user identification or for control of ICT.
5.4. Preservation of accessibility information during conversion
Where ICT converts information or communication it shall preserve all documented non-proprietary information that is provided for accessibility, to the extent that such information can be contained in or supported by the destination format.
5.5. Operable parts
Where ICT has operable parts that require grasping, pinching, or twisting of the wrist to operate, an accessible alternative means of operation that does not require these actions shall be provided.
Where ICT has operable parts, it shall provide a means to discern each operable part, without requiring vision and without performing the action associated with the operable part.
5.6. Locking or toggle controls
Where ICT has a locking or toggle control and that control is visually presented to the user, the ICT shall provide at least one mode of operation where the status of the control can be determined either through touch or sound without operating the control.
When ICT has a locking or toggle control and the control is non-visually presented to the user, the ICT shall provide at least one mode of operation where the status of the control can be visually determined when the control is presented.
5.7. Key repeat
Where ICT with key repeat is provided and the key repeat cannot be turned off:
a) the delay before the key repeat shall be adjustable to at least 2 seconds; and
b) the key repeat rate shall be adjustable down to one character per 2 seconds.
5.8. Double-strike key acceptance
Where a keyboard or keypad is provided, the delay after any keystroke, during which an additional key-press will not be accepted if it is identical to the previous keystroke, shall be adjustable up to at least 0,5 seconds.
5.9. Simultaneous user actions
Where ICT uses simultaneous user actions for its operation, such ICT shall provide at least one mode of operation that does not require simultaneous user actions to operate the ICT.
6.1. Audio bandwidth for speech (informative recommendation)
Where ICT provides two-way voice communication, in order to provide good audio quality, that ICT should be able to encode and decode two-way voice communication with a frequency range with an upper limit of at least 7 000 Hz.
6.2: Real-Time Text (RTT) functionality
Where ICT supports two-way voice communication in a specified context of use, the ICT shall allow a user to communicate with another user by RTT.
Where the ICT, or set of ICT, provided to a user, supports two-way voice communication and enables a user to communicate with another user by RTT, it shall provide a mechanism to select a mode of operation allowing concurrent voice and text.
Where ICT has RTT send and receive capabilities, displayed sent text shall be visually differentiated from and separated from received text.
Where ICT has RTT send and receive capabilities, the send/receive direction of transmitted text shall be programmatically determinable, unless the RTT has closed functionality.
Where ICT with RTT functionality interoperates with other ICT with RTT functionality (as required by 6.2.1.1) they shall support at least one of the four RTT interoperability mechanisms described below:
a) ICT interoperating over the Public Switched Telephone Network (PSTN), with other ICT that directly connects to the PSTN as described in Recommendation ITU-T V.18 [i.23] or any of its annexes for text telephony signals at the PSTN interface;
b) ICT interoperating with other ICT using VOIP with Session Initiation Protocol (SIP) and using real-time text that conforms to RFC 4103 [i.13];
c) ICT interoperating with other ICT using RTT that conforms with the IP Multimedia Sub-System (IMS) set of protocols specified in TS 126 114 [i.10], TS 122 173 [i.11] and TS 134 229 [i.12];
d) ICT interoperating with other ICT using a relevant and applicable common specification for RTT exchange that is published and available. This common specification shall include a method for indicating loss or corruption of characters.
Where ICT utilises RTT input, that RTT input shall be transmitted to the ICT network supporting RTT within 1 second of the input entry.
6.3. Caller ID
Where ICT provides caller identification and similar telecommunications functions are provided, the caller identification and similar telecommunications functions shall be available in text form and in at least one other modality.
6.4. Alternatives to voice-based services
Where ICT provides real-time voice-based communication and also provides voice mail, auto-attendant, or interactive voice response facilities, the ICT should offer users a means to access the information and carry out the tasks provided by the ICT without the use of hearing or speech.
6.5: Video Communication
Clause 6.5 (Video communications) provides performance requirements that support users who communicate using sign language and lip-reading. For these users, good usability is achieved with Common Intermediate Format (CIF) resolution, a frame rate of 20 frames per second and over, with a time difference between speech audio and video that does not exceed 100 ms.
Where ICT that provides two-way voice communication includes real time video functionality, the ICT:
a) shall support at least QCIF resolution;
b) should preferably support at least CIF resolution.
Where ICT that provides two-way voice communication includes real-time video functionality, the ICT:
a) shall support a frame rate of at least 12 frames per second (FPS);
b) should preferably support a frame rate of at least 20 frames per second (FPS) with or without sign language in the video stream.
Where ICT that provides two-way voice communication includes real-time video functionality, the ICT should ensure a maximum time difference of 100 ms between the speech and video presented to the user.
6.6. Alternatives to video-based services
Where ICT provides real-time video-based communication and also provides answering machine, auto attendant or interactive response facilities, the ICT should offer users a means to access the information and carry out the tasks related to these facilities:
a) for audible information, without the use of hearing;
b) for spoken commands, without the use of speech;
c) for visual information, without the use of vision.
7.1: Caption processing technology
Where ICT displays video with synchronized audio, it shall have a mode of operation to display the available captions. Where closed captions are provided as part of the content, the ICT shall allow the user to choose to display the captions.
Where ICT displays captions, the mechanism to display captions shall preserve synchronization between the audio and the corresponding captions.
Where ICT transmits, converts or records video with synchronized audio, it shall preserve caption data such that it can be displayed in a manner consistent with clauses 7.1.1 and 7.1.2.
Additional presentational aspects of the text such as screen position, text colours, text style and text fonts may convey meaning, based on regional conventions. Altering these presentational aspects could change the meaning and should be avoided wherever possible.
7.2: Audio description technology
Where ICT displays video with synchronized audio, it shall provide a mechanism to select and play available audio description to the default audio channel.
Where video technologies do not have explicit and separate mechanisms for audio description, an ICT is deemed to satisfy this requirement if the ICT enables the user to select and play several audio tracks.
Where ICT has a mechanism to play audio description, it shall preserve the synchronization between the audio/visual content and the corresponding audio description.
Where ICT transmits, converts, or records video with synchronized audio, it shall preserve audio description data such that it can be played in a manner consistent with clauses 7.2.1 and 7.2.2.
7.3. User controls for captions and audio description
Where ICT primarily displays materials containing video with associated audio content, user controls to activate subtitling and audio description shall be provided to the user at the same level of interaction (i.e. the number of steps to complete the task) as the primary media controls.
8.1. General
Where an ICT provides user input or output device connection points, the ICT shall provide at least one input and/or output connection that conforms to an industry standard non-proprietary format, directly or through the use of commercially available adapters.
Where the ICT has hardware aspects that use colour, colour shall not be used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.
8.2: Hardware products with speech output
Where ICT hardware has speech output, it shall provide a means to adjust the speech output volume level over a range of at least 18 dB.
Where ICT hardware has speech output and its volume control is incremental, it shall provide at least one intermediate step of 12 dB gain above the lowest volume setting.
Where ICT hardware is a fixed-line communication device with speech output and which is normally held to the ear and which carries the "T" symbol specified in ETS 300 381 [1], it shall provide a means of magnetic coupling which meets the requirements of ES 200 381-1 [2].
Where ICT hardware is a wireless communication device with speech output which is normally held to the ear, it shall provide a means of magnetic coupling to hearing technologies which meets the requirements of ES 200 381-2 [3].
8.3: Physical access to ICT
Clauses 8.3.2 to 8.3.4 describe recommendations on those dimensions that are integral to the ICT (e.g. integral shelves, or integral cabins that may restrict access to the operable parts of the ICT).
When ICT is installed, the dimensions of the surrounding space combined with the dimensions of the ICT might affect the physical access to the ICT. Accessible physical access of the ICT would be achieved if the installation instructions referred to in clause 8.3.5 are followed.
It may not be possible to apply all recommendations of clause 8.3 to all aspects of maintenance, repair, or occasional monitoring of equipment in all circumstances. Nevertheless, it is best practice to apply the recommendations in clause 8.3, where feasible and safe to do so.
Where there is a change in floor level that is integral to the ICT then it shall be ramped with a slope no steeper than 1:48.
Where the operating area is integral to the ICT, it should provide a clear floor area that has the minimum dimensions of 760 mm (30 inches) by 1 220 mm (48 inches) from which to operate the ICT.
Where the access space is integral to the ICT, at least one full side of the space shall be unobstructed.
Where the operating area is inside an alcove integral to the ICT, the alcove is deeper than 610 mm (24 inches), and where a forward approach is necessary, the dimension of the access space should be a minimum of 915 mm (36 inches) wide.
Where the operating area is inside an alcove integral to the ICT, the alcove is deeper than 380 mm (15 inches), and where a parallel approach is possible, the dimension of the access space should be a minimum of 1 525 mm (60 inches) wide.
Where the space under an obstacle that is integral to the ICT is part of access space, the clearance should be at least 760 mm (30 inches) wide.
Where an obstacle is integral to the ICT, a space under the obstacle that is less than 230 mm (9 inches) above the floor is considered toe clearance and should:
a) extend 635 mm (25 inches) maximum under the whole obstacle;
b) provide a space at least 430 mm (17 inches) deep and 230 mm above the floor under the obstacle;
c) extend no more than 150 mm (6 inches) beyond any obstruction at 230 mm (9 inches) above the floor.
Where an obstacle is integral to the ICT, a space under the obstacle that is less than 230 mm (9 inches) above the floor is considered toe clearance and should:
a) extend 635 mm (25 inches) maximum under the whole obstacle;
b) provide a space at least 430 mm (17 inches) deep and 230 mm above the floor under the obstacle;
c) extend no more than 150 mm (6 inches) beyond any obstruction at 230 mm (9 inches) above the floor.
Where the access space is integral to the ICT and the forward reach is unobstructed, the essential controls should be located no higher than 1 220 mm (48 inches) above the floor of the access space.
When the access space is integral to the ICT and the forward reach is unobstructed, the essential controls shall be located no lower than 380 mm (15 inches) above the floor of the access space.
Where the access space is integral to the ICT, allows a parallel approach, and the side reach is unobstructed or obstructed by an element integral to the ICT which is less than 255 mm (10 inches), all essential controls should be within a high side reach which is less than or equal to 1 220 mm (48 inches) above the floor of the access space.
Where the access space is integral to the ICT, allows a parallel approach, and the side reach is unobstructed or obstructed by an element integral to the ICT which is less than 255 mm (10 inches), all essential controls should be within a low side reach which is greater than or equal to 380 mm (15 inches) above the floor of the access space.
Where the operating area is integral to the ICT, and a display screen is provided, information on the screen should be legible from a point located 1 015 mm (40 inches) above the centre of the floor of the operating area (as defined in clause 8.3.2.2).
Where an ICT is intended to be installed, instructions should be made available which outline a method to install the ICT in a manner that ensures that the dimensions of the integral spaces of the ICT conform to clauses 8.3.2 to 8.3.4.
8.4: Mechanically operable parts
Where provided, physical numeric keys arranged in a rectangular keypad layout shall have the number five key tactilely distinct from the other keys of the keypad.
Where a control requires grasping, pinching, or twisting of the wrist to operate it, an accessible alternative means of operation that does not require these actions shall be provided.
Where a control requires a force greater than 22,2 N to operate it, an accessible alternative means of operation that requires a force less than 22,2 N shall be provided.
Where ICT provides keys, tickets or fare cards, and their orientation is important for further use, they shall have an orientation that is tactilely discernible.
8.5: Tactile indication of speech mode
Where ICT is designed for shared use and speech output is available, a tactile indication of the means to initiate the speech mode of operation shall be provided.
9.2. Web content requirements
Where ICT is a web page, it shall satisfy WCAG 2.0 Success Criterion 1.1.1 Non-text content.
Where ICT is a web page, it shall satisfy WCAG 2.0 Success Criterion 1.2.1 Audio-only and Video-only (Pre-recorded).
Where ICT is a web page, it shall satisfy WCAG 2.0 Success Criterion 1.2.2 Captions (Pre-recorded).
Where ICT is a web page, it shall satisfy WCAG 2.0 Success Criterion 1.2.3 Audio Description or Media Alternative (Pre-recorded).
Where ICT is a web page, it shall satisfy WCAG 2.0 Success Criterion 1.2.4 Captions (Live).
Where ICT is a web page, it shall satisfy WCAG 2.0 Success Criterion 1.2.5 Audio Description (Pre-recorded).
Where ICT is a web page, it shall satisfy WCAG 2.0 Success Criterion 1.3.1 Info and Relationships.
Where ICT is a web page, it shall satisfy WCAG 2.0 Success Criterion 1.3.2 Meaningful Sequence.
Where ICT is a web page, it shall satisfy WCAG 2.0 Success Criterion 1.3.3 Sensory Characteristics.
Where ICT is a web page, it shall satisfy WCAG 2.0 Success Criterion 1.4.1 Use of Color.
Where ICT is a web page, it shall satisfy WCAG 2.0 Success Criterion 1.4.2 Audio Control.
Where ICT is a web page, it shall satisfy WCAG 2.0 Success Criterion 1.4.3 Contrast (Minimum).
Where ICT is a web page, it shall satisfy WCAG 2.0 Success Criterion 1.4.4 Resize text.
Where ICT is a web page, it shall satisfy WCAG 2.0 Success Criterion 1.4.5 Images of Text.
Where ICT is a web page, it shall satisfy WCAG 2.0 Success Criterion 2.1.1 Keyboard.
Where ICT is a web page, it shall satisfy WCAG 2.0 Success Criterion 2.1.2 No Keyboard Trap.
WCAG 2.0 success criterion: 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.
Where ICT is a web page, it shall satisfy WCAG 2.0 Success Criterion 2.2.1 Timing Adjustable.
Where ICT is a web page, it shall satisfy WCAG 2.0 Success Criterion 2.2.2 Pause, Stop, Hide.
Where ICT is a web page, it shall satisfy WCAG 2.0 Success Criterion 2.3.1 Three Flashes or Below Threshold.
Where ICT is a web page, it shall satisfy WCAG 2.0 Success Criterion 2.4.1 Bypass Blocks.
Where ICT is a web page, it shall satisfy WCAG 2.0 Success Criterion 2.4.2 Page Titled.
Where ICT is a web page, it shall satisfy WCAG 2.0 Success Criterion 2.4.3 Focus Order.
Where ICT is a web page, it shall satisfy WCAG 2.0 Success Criterion 2.4.4 Link Purpose (In Context).
Where ICT is a web page, it shall satisfy WCAG 2.0 Success Criterion 2.4.5 Multiple Ways.
Where ICT is a web page, it shall satisfy WCAG 2.0 Success Criterion 2.4.6 Headings and Labels.
Where ICT is a web page, it shall satisfy WCAG 2.0 Success Criterion 2.4.7 Focus Visible.
Where ICT is a web page, it shall satisfy WCAG 2.0 Success Criterion 3.1.1 Language of Page.
Where ICT is a web page, it shall satisfy WCAG 2.0 Success Criterion 3.1.2 Language of Parts.
Where ICT is a web page, it shall satisfy WCAG 2.0 Success Criterion 3.2.1 On Focus.
Where ICT is a web page, it shall satisfy WCAG 2.0 Success Criterion 3.2.2 On Input.
Where ICT is a web page, it shall satisfy WCAG 2.0 Success Criterion 3.2.3 Consistent Navigation.
Where ICT is a web page, it shall satisfy WCAG 2.0 Success Criterion 3.2.4 Consistent Identification.
Where ICT is a web page, it shall satisfy WCAG 2.0 Success Criterion 3.3.1 Error Identification.
Where ICT is a web page, it shall satisfy WCAG 2.0 Success Criterion 3.3.2 Labels or Instructions.
Where ICT is a web page, it shall satisfy WCAG 2.0 Success Criterion 3.3.3 Error Suggestion.
Where ICT is a web page, it shall satisfy WCAG 2.0 Success Criterion 3.3.4 Error Prevention (Legal, Financial, Data).
Where ICT is a web page, it shall satisfy WCAG 2.0 Success Criterion 4.1.2 Name, Role, Value.
9.3. WCAG 2.0 conformance requirements
Where ICT is a web page, it shall satisfy all the following five WCAG 2.0 conformance requirements at Level AA.
- Conformance level
- Full pages
- Complete processes
- Only Accessibility-Supported Ways of Using Technologies
- Non-interference
10.1: General (informative)
Requirements in clause 10 apply to documents:
Clause 9 provides requirements for documents that are in web pages or that are embedded in web pages and that are used in the rendering or that are intended to be rendered together with the web page in which they are embedded.
-
- that are not web pages;
- that are not embedded in web pages;
- that are embedded in web pages and that are not used in the rendering and that are not intended to be rendered together with the web page in which they are embedded.
10.2: Document success criteria
Note: The success criteria set out in this clause are intended to harmonize with the Working Group Note [i.26] produced by the W3C's WCAG2 ICT Task Force 
Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.1.
Table 10.1: Document success criterion: Non-text content
|
All non-text content that is presented to the user has a text alternative that serves the equivalent purpose, except for the situations listed below:
|
|
NOTE 1: CAPTCHAs do not currently appear outside of the Web. However, if they do appear, this guidance is accurate. NOTE 2: This success criterion is identical to the WCAG 2.0 Success Criterion 1.1.1 Non-text content with the words |
Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.2.
|
For pre-recorded audio-only and pre-recorded video-only media, the following are true, except when the audio or video is a media alternative for text and is clearly labelled as such:
|
|
NOTE 1: The alternative can be provided directly in the document - or provided in an alternate version that meets the success criterion. NOTE 2: This success criterion is identical to the WCAG 2.0 |
Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.3.
|
For pre-recorded audio-only and pre-recorded video-only media, the following are true, except when the audio or video is a media alternative for text and is clearly labelled as such:
|
|
NOTE 1: The alternative can be provided directly in the document - or provided in an alternate version that meets the success criterion. NOTE 2: This success criterion is identical to the WCAG 2.0 Success Criterion 1.2.1 Audio-only and Video-only (Pre-recorded) with the addition of note 1 above. |
Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.4.
|
An alternative for time-based media or audio description of the pre-recorded video content is provided for synchronized media, except when the media is a media alternative for text and is clearly labeled as such. |
|
NOTE 1: The WCAG 2.0 definition of "audio description" says that "audio description" is "Also called 'video description' and 'descriptive narration'". NOTE 2: Secondary or alternate audio tracks are commonly used for this purpose. NOTE 3: This success criterion is identical to the WCAG 2.0 Success Criterion 1.2.3 Audio Description or Media Alternative (Pre-recorded) with the addition of notes 1 and 2 above. |
Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.5.
|
Captions are provided for all live audio content in synchronized media. |
|
NOTE 1: The WCAG 2.0 definition of "captions" notes that "in some countries, captions are called subtitles". They are also sometimes referred to as "subtitles for the hearing impaired". Per the definition in WCAG 2.0, to meet this success criterion, whether called captions or subtitles, they would have to provide "synchronized visual and / or text alternative for both speech and non-speech audio information needed to understand the media content" where non-speech information includes "sound effects, music, laughter, speaker identification and location". NOTE 2: This success criterion is identical to the WCAG 2.0 Success Criterion 1.2.4 Captions (Live) with the addition of note 1 above. |
Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.6.
|
Audio description is provided for all pre-recorded video content in synchronized media. |
|
NOTE 1: The WCAG 2.0 definition of "audio description" says that audio description is "Also called 'video description' and 'descriptive narration'". NOTE 2: Secondary or alternate audio tracks are commonly used for this purpose. NOTE 3: This success criterion is identical to the WCAG 2.0 Success Criterion 1.2.5 Audio Description (Pre-recorded) (Level AA) with the addition of note 1 above. |
Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.7.
|
Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. |
|
NOTE: This success criterion is identical to the WCAG 2.0 Success Criterion 1.3.1 Info and Relationships. |
Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.8.
|
When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined. |
|
NOTE: This success criterion is identical to the WCAG 2.0 Success Criterion 1.3.2 Meaningful Sequence. |
Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.9.
|
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. |
|
NOTE 1: For requirements related to colour, refer to WCAG 2.0 Guideline 1.4 [4]. NOTE 2: This success criterion is identical to the WCAG 2.0 Success Criterion 1.3.3 Sensory Characteristics with the words "WCAG 2.0" added before the word "Guideline" in note 1 above. |
Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.10.
|
Colour is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. |
|
NOTE 1: This success criterion addresses colour perception specifically. Other forms of perception are covered in WCAG 2.0 Guideline 1.3 [4] including programmatic access to colour and other visual presentation coding. NOTE 2: This success criterion is identical to the WCAG 2.0 Success Criterion 1.4.1 Use of Color with the words "WCAG 2.0" added before the word "Guideline" in note 1 above. |
Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.11.
|
If any audio in a document 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. |
|
NOTE 1: Since any part of a document that does not meet this success criterion can interfere with a user's ability to use the whole document, all content in the document (whether or not it is used to meet other success criteria) shall meet this success criterion. NOTE 2: This success criterion is identical to the WCAG 2.0 Success Criterion 1.4.2 Audio Control replacing "on a Web page" with "in a document", "any content" with "any part of a document", "whole page" with "whole document", "on the Web page" with "in the document", removing "See Conformance Requirement 5: Non-Interference" and adding note 1. |
Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.12.
|
The visual presentation of text and images of text has a contrast ratio of at least 4.5:1, except for the following:
|
| NOTE: This success criterion is identical to the WCAG 2.0 Success Criterion 1.4.3 Contrast (Minimum). |
Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.13.
|
Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality. |
|
NOTE 1: Content for which there are software players, viewers or editors with a 200 percent zoom feature would automatically meet this success criterion when used with such players, unless the content will not work with zoom. NOTE 2: This success criterion is about the ability to allow users to enlarge the text on screen at least up to 200 % without needing to use assistive technologies. This means that the application provides some means for enlarging the text 200 % (zoom or otherwise) without loss of content or functionality or that the application works with the platform features that meet this requirement. NOTE 3: This success criterion is identical to the WCAG 2.0 Success Criterion 1.4.4 Resize text with the addition of notes 1 and 2 above. |
Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.14.
|
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:
|
|
NOTE 1: Logotypes (text that is part of a logo or brand name) are considered essential. NOTE 2: This success criterion is identical to the WCAG 2.0 Success Criterion 1.4.5 Images of Text. |
Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.15.
|
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. |
|
NOTE 1: This exception relates to the underlying function, not the input technique. For example, if using handwriting to enter text, the input technique (handwriting) requires path-dependent input but the underlying function (text input) does not. NOTE 2: This does not forbid and should not discourage providing mouse input or other input methods in addition to keyboard operation. NOTE 3: This success criterion is identical to the WCAG 2.0 Success Criterion 2.1.1 Keyboard. |
Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.16.
|
If keyboard focus can be moved to a component of the document 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. |
|
NOTE 1: Since any part of a document that does not meet this success criterion can interfere with a user's ability to use the whole document, all content in the document (whether or not it is used to meet other success criteria) must meet this success criterion. NOTE 2: Standard exit methods may vary by platform. For example, on many desktop platforms, the Escape key is a standard method for exiting. NOTE 3: This success criterion is identical to the WCAG 2.0 Success Criterion 2.1.2 No Keyboard Trap replacing "page" and "Web page" with "document", removing "See Conformance Requirement 5: Non-Interference" and with the addition of note 1 above. |
Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.17.
|
For each time limit that is set by the document, at least one of the following is true:
|
|
NOTE 1: This success criterion helps ensure that users can complete tasks without unexpected changes in content or context that are a result of a time limit. This success criterion should be considered in conjunction with WCAG 2.0 Success Criterion 3.2.1, which puts limits on changes of content or context as a result of user action. NOTE 2: This success criterion is identical to the WCAG 2.0 Success Criterion 2.2.1 Timing Adjustable replacing "the content" with "documents" and with the words "WCAG 2.0" added before the word "Success Criterion" in note 1 above. |
Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.18.
|
For moving, blinking, scrolling, or auto-updating information, all of the following are true:
|
|
NOTE 1: For requirements related to flickering or flashing content, refer to WCAG 2.0 Guideline 2.3. NOTE 2: This success criteria is applicable to all content in the document (whether or not there is an alternate accessible version of the document) since any part of a document that does not meet this success criterion can interfere with a user's ability to use the whole document (including a link to the alternate version). NOTE 3: Content that is updated periodically by software or that is streamed to the user agent is not required to preserve or present information that is generated or received between the initiation of the pause and resuming presentation, as this may not be technically possible, and in many situations could be misleading to do so. NOTE 4: An animation that occurs as part of a preload phase or similar situation can be considered essential if interaction cannot occur during that phase for all users and if not indicating progress could confuse users or cause them to think that content was frozen or broken. NOTE 5: This is to be applied to all content. Any content, whether informative or decorative, that is updated automatically, blinks, or moves may create an accessibility barrier. NOTE 6: This success criterion is identical to the WCAG 2.0 Success Criterion 2.2.2 Pause, Stop, Hide replacing "page" and "Web page" with "document", removing "See Conformance Requirement 5: Non-Interference" in note 2 of the success criterion, with the words "WCAG 2.0" added before the word "Guideline" in note 1 above and with note 2 above re-drafted to avoid the use of the word "must". |
Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.19.
|
Documents 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. |
|
NOTE 1: This success criterion is applicable to all content in the document (whether or not there is an alternate accessible version of the document) since any part of a document that does not meet this success criterion can interfere with a user's ability to use the whole document (including a link to the alternate version). NOTE 2: This success criterion is identical to the WCAG 2.0 Success Criterion 2.3.1 Three Flashes or Below Threshold replacing "Web pages" with "documents", "the whole page" with "the whole document", "the Web page" with "the document" and removing "See Conformance Requirement 5: Non-Interference" and with note 2 above re-drafted to avoid the use of the word "must". |
Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.21.
|
Documents have titles that describe topic or purpose. |
|
NOTE 1: The name of a document (e.g. document, media file) is a sufficient title if it describes the topic or purpose. NOTE 2: This success criterion is identical to the WCAG 2.0 Success Criterion 2.4.2 Page Titled replacing "Web pages" with "documents", "Page" with "Document" and with the addition of note 1 above. |
Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.22.
|
If a document can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability. |
|
NOTE: This success criterion is identical to the WCAG 2.0 Success Criterion 2.4.3 Focus Order replacing "Web page" with "document". |
Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.23.
|
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. |
|
NOTE: This success criterion is identical to the WCAG 2.0 Success Criterion 2.4.4 Link Purpose (In Context). |
Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.25.
| Headings and labels describe topic or purpose. |
| NOTE: This success criterion is identical to the WCAG 2.0 Success Criterion 2.4.6 Headings and Labels. |
Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.26.
| Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible. |
| NOTE: This success criterion is identical to the WCAG 2.0 Success Criterion 2.4.7 Focus Visible. |
Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.27.
| The default human language of each document can be programmatically determined. |
| NOTE: This success criterion is identical to the WCAG 2.0 Success Criterion 3.1.1 Language of Page replacing "web page" with "document". |
Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.28.
Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.29.
| When any component receives focus, it does not initiate a change of context. |
|
NOTE 1: Some compound documents and their user agents are designed to provide significantly different viewing and editing functionality depending upon what portion of the compound document is being interacted with (e.g. a presentation that contains an embedded spreadsheet, where the menus and toolbars of the user agent change depending upon whether the user is interacting with the presentation content, or the embedded spreadsheet content). If the user uses a mechanism other than putting focus on that portion of the compound document with which they mean to interact (e.g. by a menu choice or special keyboard gesture), any resulting change of context would not be subject to this success criterion because it was not caused by a change of focus. NOTE 2: This success criterion is identical to the WCAG 2.0 Success Criterion 3.2.1 On Focus with the addition of note 1. |
Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.30.
| Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behaviour before using the component. |
| NOTE: This success criterion is identical to the WCAG 2.0 Success Criterion 3.2.2 On Input. |
Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.33.
| 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. |
| NOTE: This success criterion is identical to the WCAG 2.0 Success Criterion 3.3.1 Error Identification. |
Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.34.
| Labels or instructions are provided when content requires user input. |
| NOTE: This success criterion is identical to the WCAG 2.0 Success Criterion 3.3.2 Labels or Instructions. |
Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.35.
| 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. |
| NOTE: This success criterion is identical to the WCAG 2.0 Success Criterion 3.3.3 Error Suggestion. |
Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.36.
|
For documents 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:
|
| NOTE: This success criterion is identical to the WCAG 2.0 Success Criterion 3.3.4 Error Prevention (Legal, Financial, Data) replacing "web pages" with "documents". |
<p>Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.37.</p>
<table class="table">
<caption>Table 10.37: Document success criterion: Parsing</caption>
<tbody>
<tr>
<td>For documents that use markup languages, in such a way that the markup is separately exposed and available to assistive technologies and accessibility features of software or to a user-selectable user agent, 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.</td>
</tr>
<tr>
<td>
<p>NOTE 1: Start and end tags that are missing a critical character in their formation, such as a closing angle bracket or a mismatched attribute value quotation mark are not complete.</p>
<p>NOTE 2: Markup is not always available to assistive technology or to user selectable user agents such as browsers. In such cases, conformance to this provision would have no impact on accessibility as it can for web content where it is exposed.</p>
<p>NOTE 3: Examples of markup that is separately exposed and available to assistive technologies and to user agents include but are not limited to: documents encoded in HTML, ODF, and OOXML. In these examples, the markup can be parsed entirely in two ways: (a) by assistive technologies which may directly open the document, (b) by assistive technologies using DOM APIs of user agents for these document formats.</p>
<p>NOTE 4: This success criterion is identical to the WCAG 2.0 Success Criterion 4.1.1 Parsing replacing "In content implemented using markup languages" with "For documents that use markup languages, in such a way that the markup is separately exposed and available to assistive technologies and accessibility features of software or to a user-selectable user agent" with the addition of notes 2 and 3 above.</p>
</td>
</tr>
</tbody>
</table>
Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.38.
| 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. |
|
NOTE 1: This success criterion is primarily for software developers who develop or use custom user interface components. Standard user interface components on most accessibility-supported platforms already meet this success criterion when used according to specification. NOTE 2: For document formats that support interoperability with assistive technology, standard user interface components often meet this success criterion when used according to the general design and accessibility guidance for the document format. NOTE 3: This success criterion is identical to the WCAG 2.0 Success Criterion 4.1.2 Name, Role, Value replacing the original WCAG 2.0 note with: "This success criterion is primarily for software developers who develop or use custom user interface components. For example, standard user interface components on most accessibility-supported platforms already meet this success criterion when used according to specification." and with the addition of note 2 above. |
<p>Where ICT is a non-web document that contains synchronized media with captions, the captions should not obscure relevant information in the synchronized media.</p>
Where ICT is a non-web document that contains synchronized media with audio description, the audio description should not interfere with relevant audio information in the synchronized media.
11.1: General (informative)
This clause provides requirements for:
- platform software;
- software that provides a user interface including content that is in the software;
- authoring tools;
- software that operates as assistive technology.
11.2: Non-Web software success criteria
Requirements in clause 11.2 apply to software:
- that is not a web page;
- not embedded in web pages nor used in the rendering or functioning of the page.
Clause 9 provides requirements for software that is in web pages or that is embedded in web pages and that is used in the rendering or that is intended to be rendered together with the web page in which it is embedded.
Clause 11.2.1 contains the software requirements for the functionality of software that provides a user interface and that is not closed functionality.
Clause 11.2.2 contains the software requirements for the closed functionality of software that provides a user interface.
The success criteria set out in clause 11.2 are intended to harmonize with the W3C Working Group Note [i.26] produced by the W3C's WCAG2ICT Task Force (http://www.w3.org/WAI/GL/WCAG2ICT-TF/ ).
Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, it shall satisfy the success criterion in Table 11.1.
|
All non-text content that is presented to the user has a text alternative that serves the equivalent purpose, except for the situations listed below:
|
| NOTE 1: CAPTCHAs do not currently appear outside of the Web. However, if they do appear, this guidance is accurate. NOTE 2: This success criterion is identical to the WCAG 2.0 Success Criterion 1.1.1 Non-text content with the words "WCAG 2.0" added before each occurrence of the word "guideline" and with the addition of note 1 above. |
Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading and where pre-recorded auditory information is not needed to enable the use of closed functions of ICT, it shall satisfy the success criterion in Table 11.2.
|
For pre-recorded audio-only and pre-recorded video-only media, the following are true, except when the audio or video is a media alternative for text and is clearly labelled as such:
|
| NOTE 1: The alternative can be provided directly in the software - or provided in an alternate version that meets the success criterion. NOTE 2: This success criterion is identical to the WCAG 2.0 Success Criterion 1.2.1 Audio-only and Video-only (Pre-recorded) with the addition of note 1 above. |
Where ICT is non-web software that provides a user interface, it shall satisfy the success criterion in Table 11.3.
| Captions are provided for all pre-recorded audio content in synchronized media, except when the media is a media alternative for text and is clearly labeled as such. |
|
NOTE 1: The WCAG 2.0 definition of "captions" notes that "in some countries, captions are called subtitles". They are also sometimes referred to as "subtitles for the hearing impaired". Per the definition in WCAG 2.0, to meet this success criterion, whether called captions or subtitles, they would have to provide "synchronized visual and / or text alternative for both speech and non-speech audio information needed to understand the media content" where non-speech information includes "sound effects, music, laughter, speaker identification and location". NOTE 2: This success criterion is identic. |
Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, it shall satisfy the success criterion in Table 11.4.
| An alternative for time-based media or audio description of the pre-recorded video content is provided for synchronized media, except when the media is a media alternative for text and is clearly labeled as such. |
|
NOTE 1: The WCAG 2.0 definition of "audio description" says that "audio description" is "also called 'video description' and 'descriptive narration'". NOTE 2: Secondary or alternate audio tracks are commonly used for this purpose. NOTE 3: This success criterion is identical to the WCAG 2.0 Success Criterion 1.2.3 Audio Description or Media Alternative (Pre-recorded) with the addition of notes 1 and 2 above. |
Where ICT is non-web software that provides a user interface, it shall satisfy the success criterion in Table 11.5.
| Captions are provided for all live audio content in synchronized media. |
|
NOTE 1: The WCAG 2.0 definition of "captions" notes that "in some countries, captions are called subtitles". They are also sometimes referred to as "subtitles for the hearing impaired". Per the definition in WCAG 2.0, to meet this success criterion, whether called captions or subtitles, they would have to provide "synchronized visual and / or text alternative for both speech and non-speech audio information needed to understand the media content" where non-speech information includes "sound effects, music, laughter, speaker identification and location". NOTE 2: This success criterion is identical to the WCAG 2.0 Success Criterion 1.2.4 Captions (Live) with the addition of note 1 above. |
Where ICT is non-web software that provides a user interface, it shall satisfy the success criterion in Table 11.6.
| Audio description is provided for all pre-recorded video content in synchronized media. |
|
NOTE 1: The WCAG 2.0 definition of "audio description" says that audio description is "Also called 'video description' and 'descriptive narration'". |
Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, it shall satisfy the success criterion in Table 11.7.
| Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. |
|
NOTE 1: In software, programmatic determinability is best achieved through the use of accessibility services provided by platform software to enable interoperability between software and assistive technologies and accessibility features of software. (see clause 11.3 Interoperability with assistive technology). NOTE 2: This success criterion is identical to the WCAG 2.0 Success Criterion 1.3.1 Info and Relationships with the addition of note 1 above. |
Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, it shall satisfy the success criterion in Table 11.8.
| When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined. |
| NOTE: This success criterion is identical to the WCAG 2.0 Success Criterion 1.3.2 Meaningful Sequence. |
Where ICT is non-web software that provides a user interface, it shall satisfy the success criterion in Table 11.9.
| 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. |
|
NOTE 1: For requirements related to colour, refer to WCAG 2.0 Guideline 1.4 [4]. NOTE 2: This success criterion is identical to the WCAG 2.0 Success Criterion 1.3.3 Sensory Characteristics with the words "WCAG 2.0" added before the word "Guideline" in note 1 above. |
Where ICT is non-web software that provides a user interface, it shall satisfy the success criterion in Table 11.10.
| Colour is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. |
|
NOTE 1: This success criterion addresses colour perception specifically. Other forms of perception are covered in WCAG 2.0 Guideline 1.3 [4] including programmatic access to colour and other visual presentation coding. NOTE 2: This success criterion is identical to the WCAG 2.0 Success Criterion 1.4.1 Use of Color with the words "WCAG 2.0" added before the word "Guideline" in note 1 above. |
Where ICT is non-web software that provides a user interface, it shall satisfy the success criterion in Table 11.11.
| If any audio in a software 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. |
|
NOTE 1: Since any part of a software that does not meet this success criterion can interfere with a user's ability to use the whole software, all content in the software (whether or not it is used to meet other success criteria) shall meet this success criterion. NOTE 2: This success criterion is identical to the WCAG 2.0 Success Criterion 1.4.2 Audio Control replacing "on a Web page" with "in a software", "any content" with "any part of a software", "whole page" with "whole software", "on the Web page" with "in the software", removing "See Conformance Requirement 5: Non-Interference" and adding note 1. |
Where ICT is non-web software that provides a user interface, it shall satisfy the success criterion in Table 11.12.
|
The visual presentation of text and images of text has a contrast ratio of at least 4.5:1, except for the following:
|
| NOTE: This success criterion is identical to the WCAG 2.0 Success Criterion 1.4.3 Contrast (Minimum). |
Where ICT is non-web software that provides a user interface and that supports access to enlargement features of platform or assistive technology, it shall satisfy the success criterion in Table 11.13.
| Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality. |
|
NOTE 1: Content for which there are software players, viewers or editors with a 200 percent zoom feature would automatically meet this success criterion when used with such players, unless the content will not work with zoom. NOTE 2: This success criterion is about the ability to allow users to enlarge the text on screen at least up to 200 % without needing to use assistive technologies. This means that the application provides some means for enlarging the text 200 % (zoom or otherwise) without loss of content or functionality or that the application works with the platform features that meet this requirement. NOTE 3: This success criterion is identical to the WCAG 2.0 Success Criterion 1.4.4 Resize text with the addition of notes 1 and 2 above. |
Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, it shall satisfy the success criterion in Table 11.14.
|
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:
|
|
NOTE 1: Logotypes (text that is part of a logo or brand name) are considered essential. NOTE 2: This success criterion is identical to the WCAG 2.0 Success Criterion 1.4.5 Images of Text. |
Where ICT is non-web software that provides a user interface and that supports access to keyboards or a keyboard interface, it shall satisfy the success criterion in Table 11.15.
| 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. |
|
NOTE 1: This exception relates to the underlying function, not the input technique. For example, if using handwriting to enter text, the input technique (handwriting) requires path-dependent input but the underlying function (text input) does not. NOTE 2: This does not forbid and should not discourage providing mouse input or other input methods in addition to keyboard operation. NOTE 3: This does not imply that software is required to directly support a keyboard or "keyboard interface". Nor does it imply that software is required to provide a soft keyboard. Underlying platform software may provide device independent input services to applications that enable operation via a keyboard. Software that supports operation via such platform device independent services would be operable by a keyboard and would comply. NOTE 4: This success criterion is identical to the WCAG 2.0 Success Criterion 2.1.1 Keyboard with the addition of note 3 above. |
Where ICT is non-web software that provides a user interface, it shall satisfy the success criterion in Table 11.16.
| If keyboard focus can be moved to a component of the software 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. |
|
NOTE 1: Since any part of a software that does not meet this success criterion can interfere with a user's ability to use the whole document, all content in the document (whether or not it is used to meet other success criteria) shall meet this success criterion. NOTE 2: Standard exit methods may vary by platform. For example, on many desktop platforms, the Escape key is a standard method for exiting. NOTE 3: This success criterion is identical to the WCAG 2.0 Success Criterion 2.1.2 No Keyboard Trap replacing "page" and "Web page" with "document", removing "See Conformance Requirement 5: Non-Interference" and with the addition of note 1 above. |
Where ICT is non-web software that provides a user interface, it shall satisfy the success criterion in Table 11.17.
|
For each time limit that is set by the software, at least one of the following is true:
|
|
NOTE 1: This success criterion helps ensure that users can complete tasks without unexpected changes in content or context that are a result of a time limit. This success criterion should be considered in conjunction with clause 11.2.1.29 (On focus), which puts limits on changes of content or context as a result of user action. NOTE 2: This success criterion is identical to the WCAG 2.0 Success Criterion 2.2.1 Timing Adjustable replacing "the content" with "software" and with the words "WCAG 2.0" added before the word "Success Criterion" in note 1 above. |
Where ICT is non-web software that provides a user interface, it shall satisfy the success criterion in Table 11.18.
|
For moving, blinking, scrolling, or auto-updating information, all of the following are true:
|
|
NOTE 1: For requirements related to flickering or flashing content, refer to WCAG 2.0 Guideline 2.3. NOTE 2: This success criteria is applicable to all content in the software (whether or not there is an alternate accessible mode of operation of the software) since any part of a software that does not meet this success criterion can interfere with a user's ability to use the whole software (including a user interface element that enables the user to activate the alternate accessible mode of operation). NOTE 3: Content that is updated periodically by software or that is streamed to the user agent is not required to preserve or present information that is generated or received between the initiation of the pause and resuming presentation, as this may not be technically possible, and in many situations could be misleading to do so. NOTE 4: An animation that occurs as part of a preload phase or similar situation can be considered essential if interaction cannot occur during that phase for all users and if not indicating progress could confuse users or cause them to think that content was frozen or broken. NOTE 5: This is to be applied to all content. Any content, whether informative or decorative, that is updated automatically, blinks, or moves may create an accessibility barrier. NOTE 6: This success criterion is identical to the WCAG 2.0 Success Criterion 2.2.2 Pause, Stop, Hide replacing "page" and "Web page" with "software", removing "See Conformance Requirement 5: Non-Interference" in note 2 of the success criterion, with the words "WCAG 2.0" added before the word "Guideline" in note 1 above, with note 2 above re-drafted to avoid the use of the word "must" and with the addition of note 5 above. |
Where ICT is non-web software that provides a user interface, it shall satisfy the success criterion in Table 11.19.
| Software does 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. |
|
NOTE 1: This success criteria is applicable to all content in the software (whether or not there is an alternate accessible mode of operation of the software) since any part of a software that does not meet this success criterion can interfere with a user's ability to use the whole software (including a user interface element that enables the user to activate the alternate accessible mode of operation). NOTE 2: This success criterion is identical to the WCAG 2.0 Success Criterion 2.3.1 Three Flashes or Below Threshold replacing "Web pages" with "software", "the whole page" with "the whole software", "the Web page" with "the software" and removing "See Conformance Requirement 5: Non-Interference" and with note 1 above re-drafted to avoid the use of the word "must". |
Where ICT is non-web software that provides a user interface, it shall satisfy the success criterion in Table 11.22.
| If software can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability. |
| NOTE: This success criterion is identical to the WCAG 2.0 Success Criterion 2.4.3 Focus order replacing "Web page" with "software". |
Where ICT is non-web software that provides a user interface, it shall satisfy the success criterion in Table 11.23.
| 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. |
|
NOTE 1: In software, a "link" is any text string or image in the user interface outside a user interface control that behaves like a hypertext link. This does not include general user interface controls or buttons. (An OK button, for example, would not be a link.) NOTE 2: This success criterion is identical to the WCAG 2.0 Success Criterion 2.4.4 Link purpose (in context), replacing both "web page" and "page" with "software" and with the addition of note 1 above. |
Where ICT is non-web software that provides a user interface, it shall satisfy the success criterion in Table 11.25.
| Headings and labels describe topic or purpose. |
|
NOTE 1: In software, headings and labels are used to describe sections of content and controls respectively. In some cases it may be unclear whether a piece of static text is a heading or a label. But whether treated as a label or a heading, the requirement is the same: that if they are present they describe the topic or purpose of the item(s) they are associated with. NOTE 2: This success criterion is identical to the WCAG 2.0 Success Criterion 2.4.6 Headings and labels with the addition of note 1 above. |
Where ICT is non-web software that provides a user interface, it shall satisfy the success criterion in Table 11.26.
| Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible. |
| NOTE: This success criterion is identical to the WCAG 2.0 Success Criterion 2.4.7 Focus visible. |
Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, it shall satisfy the success criterion in Table 11.27.
| The default human language of software can be programmatically determined. |
|
NOTE 1: Where software platforms provide a "locale / language" setting, applications that use that setting and render their interface in that "locale / language" would comply with this success criterion. Applications that do not use the platform "locale / language" setting but instead use an accessibility-supported method for exposing the human language of the software would also comply with this success criterion. Applications implemented in technologies where assistive technologies cannot determine the human language and that do not support the platform "locale / language" setting may not be able to meet this success criterion in that locale / language. NOTE 2: This success criterion is identical to the WCAG 2.0 Success Criterion 3.1.1 Language of page, replacing "each web page" with "software" and with the addition of note 1 above. |
Where ICT is non-web software that provides a user interface, it shall satisfy the success criterion in Table 11.29.
| When any component receives focus, it does not initiate a change of context. |
|
NOTE 1: Some compound documents and their user agents are designed to provide significantly different viewing and editing functionality depending upon what portion of the compound document is being interacted with (e.g. a presentation that contains an embedded spreadsheet, where the menus and toolbars of the user agent change depending upon whether the user is interacting with the presentation content, or the embedded spreadsheet content). If the user uses a mechanism other than putting focus on that portion of the compound document with which they mean to interact (e.g. by a menu choice or special keyboard gesture), any resulting change of context would not be subject to this success criterion because it was not caused by a change of focus. NOTE 2: This success criterion is identical to the WCAG 2.0 Success Criterion 3.2.1 On focus, with the addition of note 1 above. |
Where ICT is non-web software that provides a user interface, it shall satisfy the success criterion in Table 11.30.
| 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. |
| NOTE: This success criterion is identical to the WCAG 2.0 Success Criterion 3.2.2 On input. |
Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, it shall satisfy the success criterion in Table 11.33.
| 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. |
| NOTE: This success criterion is identical to the WCAG 2.0 Success Criterion 3.3.1 Error identification. |
Where ICT is non-web software that provides a user interface, it shall satisfy the success criterion in Table 11.34.
| Labels or instructions are provided when content requires user input. |
| NOTE: This success criterion is identical to the WCAG 2.0 Success Criterion 3.3.2 Labels or instructions. |
Where ICT is non-web software that provides a user interface, it shall satisfy the success criterion in Table 11.35.
| 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. |
| NOTE: This success criterion is identical to the WCAG 2.0 Success Criterion 3.3.3 Error suggestion. |
Where ICT is non-web software that provides a user interface, it shall satisfy the success criterion in Table 11.36.
|
For software 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:
|
| NOTE: This success criterion is identical to the WCAG 2.0 Success Criterion 3.3.4 Error prevention (legal, financial, data) replacing "web pages" with "software". |
Where ICT is non-web software that provides a user interface and that supports access to any assistive technologies, it shall satisfy the success criterion in Table 11.37.
| For software that uses markup languages, in such a way that the markup is separately exposed and available to assistive technologies and accessibility features of software or to a user-selectable user agent, 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. |
|
NOTE 1: Start and end tags that are missing a critical character in their formation, such as a closing angle bracket or a mismatched attribute value quotation mark are not complete. NOTE 2: Markup is not always available to assistive technology or to user selectable user agents such as browsers. In such cases, conformance to this provision would have no impact on accessibility as it can for web content where it is exposed. NOTE 3: Examples of markup that is separately exposed and available to assistive technologies and to user agents include but are not limited to: documents encoded in HTML, ODF, and OOXML. In these examples, the markup can be parsed entirely in two ways: (a) by assistive technologies which may directly open the document, (b) by assistive technologies using DOM APIs of user agents for these document formats. NOTE 4: Examples of markup used internally for persistence of the software user interface that are never exposed to assistive technology include but are not limited to: XUL, GladeXML, and FXML. In these examples assistive technology only interacts with the user interface of generated software. NOTE 5: This success criterion is identical to the WCAG 2.0 Success Criterion 4.1.1 Parsing replacing "In content implemented using markup languages" with "For software that uses markup languages, in such a way that the markup is separately exposed and available to assistive technologies and accessibility features of software or to a user-selectable user agent" with the addition of notes 2 and 3 above. |
Where ICT is non-web software that provides a user interface and that supports access to any assistive technologies, it shall satisfy the success criterion in Table 11.38.
| 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. |
|
NOTE 1: This success criterion is primarily for software developers who develop or use custom user interface components. Standard user interface components on most accessibility-supported platforms already meet this success criterion when used according to specification. NOTE 2: For conforming to this success criterion, it is usually best practice for software user interfaces to use the accessibility services provided by platform software. These accessibility services enable interoperability between software user interfaces and both assistive technologies and accessibility features of software in standardised ways. Most platform accessibility services go beyond programmatic exposure of name and role, and programmatic setting of states, properties and values (and notification of same), and specify additional information that could or should be exposed and / or set (for instance, a list of the available actions for a given user interface component, and a means to programmatically execute one of the listed actions). NOTE 3: This success criterion is identical to the WCAG 2.0 Success Criterion 4.1.2 Name, Role, Value replacing the original WCAG 2.0 note with: "This success criterion is primarily for software developers who develop or use custom user interface components. For example, standard user interface components on most accessibility-supported platforms already meet this success criterion when used according to specification." and the addition of note 2 above. |
Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading, it shall meet requirement 5.1.3.6 (Speech output for non-text content).
Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading and pre-recorded auditory information is needed to enable the use of closed functions of ICT, the functionality of software that provides a user interface shall meet requirement 5.1.5 (Visual output for auditory information).
Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading, it shall meet requirement 5.1.3.7 (Speech output for video information).
Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading, it shall meet requirement 5.1.3.7 (Speech output for video information).
WhereICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading and where information is displayed on the screen, the ICT should provide auditory information that allows the user to correlate the audio with the information displayed on the screen.
Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading and where information is displayed on the screen, the ICT should provide auditory information that allows the user to correlate the audio with the information displayed on the screen.
Where ICT is non-web software that provides a user interface which is not able to access to enlargement features of platform or assistive technology, it shall meet requirement 5.1.4 (Functionality closed to text enlargement).
Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading, it does not need to meet the "Images of text" success criterion in Table 11.14 because there is no need to impose a requirement on all closed functionality that text displayed on the screen actually be represented internally as text (as defined by WCAG 2.0), given that there is no interoperability with assistive technology.
Where ICT is non-web software that provides a user interface which is closed to keyboards or keyboard interface, it shall meet requirement 5.1.6.1 (Operation without keyboard interface: Closed functionality).
Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading, it shall meet requirement 5.1.3.14 (Spoken languages).
Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen reading, it shall meet requirement 5.1.3.15 (Non-visual error identification).
Where ICT is non-web software that provides a user interface which is closed to all assistive technology it shall not have to meet the "Parsing" success criterion in Table 11.37 because the intent of this success criterion is to provide consistency so that different user agents or assistive technologies will yield the same result.
Where ICT is non-web software that provides a user interface which is closed to all assistive technology it shall not have to meet the "Name, role, value" success criterion in Table 11.38 because this success criterion requires information in a programmatically determinable form.
11.3. Interoperability with assistive technology
Where the closed functionality of software conforms to clause 5.1 (Closed functionality) it shall not be required to conform with clause 11.3.2 to clause 11.3.17
Platform software shall provide a set of documented platform services that enable software that provides a user interface running on the platform software to interoperate with assistive technology.
Platform software should support requirements 11.3.2.5 to 11.3.2.17 except that, where a user interface concept that corresponds to one of the clauses 11.3.2.5 to 11.3.2.17 is not supported within the software environment, these requirements are not applicable. For example, selection attributes from 11.3.2.14 (Modification of focus and selection attributes) may not exist in environments that do not allow selection, which is most commonly associated with copy and paste.
Platform software shall provide a set of documented platform accessibility services that enable assistive technology to interoperate with software that provides a user interface running on the platform software.
Platform software should support the requirements of clauses 11.3.2.5 to 11.3.2.17 except that, where a user interface concept that corresponds to one of the clauses 11.3.2.5 to 11.3.2.17 is not supported within the software environment, these requirement are not applicable. For example, selection attributes from 11.3.2.14 (Modification of focus and selection attributes) may not exist in environments that do not allow selection, which is most commonly associated with copy and paste.
Where the software provides a user interface it shall use the applicable documented platform accessibility services. If the documented platform accessibility services do not allow the software to meet the applicable requirements of clauses 11.3.2.5 to 11.3.2.17, then software that provides a user interface shall use other documented services to interoperate with assistive technology.
Where the ICT is assistive technology it shall use the documented platform accessibility services.
Where the software provides a user interface it shall, by using the services as described in clause 11.3.2.3, make the user interface elements' role, state(s), boundary, name, and description programmatically determinable by assistive technologies.
Where the software provides a user interface it shall, by using the services as described in clause 11.3.2.3, make the row and column of each cell in a data table, including headers of the row and column if present, programmatically determinable by assistive technologies.
Where the software provides a user interface, it shall, by using the services as described in clause 11.3.2.3, make the current value of a user interface element and any minimum or maximum values of the range, if the user interface element conveys information about a range of values, programmatically determinable by assistive technologies.
Where the software provides a user interface it shall expose the relationship that a user interface element has as a label for another element, or of being labelled by another element, using the services as described in clause 11.3.2.3, so that this information is programmatically determinable by assistive technologies.
Where the software provides a user interface it shall, by using the services as described in clause 11.3.2.3, make the relationship between a user interface element and any parent or children elements programmatically determinable by assistive technologies.
Where the software provides a user interface it shall, by using the services as described in clause 11.3.2.3, make the text contents, text attributes, and the boundary of text rendered to the screen programmatically determinable by assistive technologies.
Where the software provides a user interface it shall, by using the services as described in clause 11.3.2.3, make a list of available actions that can be executed on a user interface element, programmatically determinable by assistive technologies.
When permitted by security requirements, software that provides a user interface shall, by using the services as described in clause 11.3.2.3, allow the programmatic execution of the actions exposed according to clause 11.3.2.11 by assistive technologies.
Where software provides a user interface it shall, by using the services as described in clause 11.3.2.3, make information and mechanisms necessary to track focus, text insertion point, and selection attributes of user interface elements programmatically determinable by assistive technologies
When permitted by security requirements, software that provides a user interface shall, by using the services as described in clause 11.3.2.3, allow assistive technologies to programmatically modify focus, text insertion point, and selection attributes of user interface elements where the user can modify these items.
Where software provides a user interface it shall, by using the services as described in 11.3.2.3, notify assistive technologies about changes in those programmatically determinable attributes of user interface elements that are referenced in requirements 11.3.2.5 to 11.3.2.11 and 11.3.2.13.
When permitted by security requirements, software that provides a user interface shall, by using the services as described in clause 11.3.2.3, allow assistive technologies to programmatically modify states and properties of user interface elements, where the user can modify these items.
When permitted by security requirements, software that provides a user interface shall, by using the services as described in 11.3.2.3, allow assistive technologies to modify values and text of user interface elements using the input methods of the platform, where a user can modify these items without the use of assistive technology.
11.4. Documented accessibility usage
Where software is a platform it shall provide sufficient modes of operation for user control over those platform accessibility features documented as intended for users.
Where software provides a user interface it shall not disrupt those documented accessibility features that are defined in platform documentation except when requested to do so by the user during the operation of the software.
11.5. User preferences
Where software provides a user interface it shall provide sufficient modes of operation that use user preferences for platform settings for colour, contrast, font type, font size, and focus cursor except for software that is designed to be isolated from its underlying platforms.
11.6. Authoring tools
Authoring tools shall conform to clauses 11.6.2 to 11.6.5 to the extent that information required for accessibility is supported by the format used for the output of the authoring tool.
Authoring tools shall enable and guide the production of content that conforms to clauses 9 (Web content) or 10 (Non-Web content) as applicable.
If the authoring tool provides restructuring transformations or re-coding transformations, then accessibility information shall be preserved in the output if equivalent mechanisms exist in the content technology of the output.
If the accessibility checking functionality of an authoring tool can detect that content does not meet a requirement of clauses 9 (Web content) or 10 (Documents) as applicable, then the authoring tool shall provide repair suggestion(s).
When an authoring tool provides templates, at least one template that supports the creation of content that conforms to the requirements of clauses 9 (Web content) or 10 (Documents) as applicable shall be available and identified as such.
12.1. Product documentation
Product documentation provided with the ICT whether provided separately or integrated within the ICT shall list and explain how to use the accessibility and compatibility features of the ICT.
Product documentation provided with the ICT shall be made available in at least one of the following electronic formats:
a) a Web format that conforms to clause 9, or
b) a non-web format that conforms to clause 10.
12.2. Support services
ICT support services include, but are not limited to: help desks, call centres, technical support, and training services.
ICT support services shall provide information on the accessibility and compatibility features that are included in the product documentation.
ICT support services shall accommodate the communication needs of individuals with disabilities either directly or through a referral point.
Documentation provided by support services shall be made available in at least one of the following electronic formats:
a) a Web format that conforms to clause 9, or
b) a non-web format that conforms to clause 10.
13.1. Relay services requirements
Relay services enable users of different modes of communication e.g. text, sign, speech, to interact remotely through ICT with two-way communication by providing conversion between the modes of communication, normally by a human operator.
It is best practice to meet the applicable relay service requirements of ES 202 975 [i.5].
Where ICT is intended to provide a text relay service, the text relay service shall enable text users and speech users to interact by providing conversion between the two modes of communication.
Where ICT is intended to provide a sign relay service, the sign relay service shall enable sign language users and speech users to interact by providing conversion between the two modes of communication.
Where ICT is intended to provide a lip-reading relay service, the lip-reading service shall enable lip-readers and voice telephone users to interact by providing conversion between the two modes of communication.
Where ICT is intended to provide a captioned telephony service, the captioned telephony service shall assist a deaf or hard of hearing user in a spoken dialogue by providing text captions translating the incoming part of the conversation.
Where ICT is intended to provide a speech to speech relay service, the speech to speech relay service shall enable speech or cognitively impaired telephone users and any other user to communicate by providing assistance between them.
13.2. Access to relay services
Where ICT systems support two-way communication and a set of relay services for such communication is specified, access to those relay services shall not be prevented for outgoing and incoming calls.
13.3. Access to emergency services
Where ICT systems support two-way communication and a set of emergency services for such communication is specified, access to those emergency services shall not be prevented for outgoing and incoming calls.