Information and Communication Technology (ICT) Accessibility Requirements

What is ICT?

Information and Communications Technology (ICT) includes hardware, software, voice communication, video capabilities and digital content (including web and non-web-based information).

What is ICT accessibility and why is it important?

"ICT accessibility ensures that people with and without disabilities can access the same information, perform the same tasks, and receive the same services using information technology. It is the digital equivalent to accessibility in the physical environment —the curb cuts, ramps, railings, etc., of the digital age. While ICT accessibility can provide usability benefits to everyone who uses ICT, it is a vital necessity to many people with disabilities." - NASCIO - Accessibility in IT Procurement

About this document and Copyright Notice

This document reproduces relevant ICT accessibility requirements from the EN 301 549 V4.1.1 (2026-09) Harmonised European Standard – Accessibility requirements for ICT products and services (© used under license from European Telecommunications Standards Institute 2026. © Comité Européen de Normalisation 2026. © Comité Européen de Normalisation Électrotechnique 2026. All rights reserved.), which aligns with the Web Content Accessibility Guidelines (WCAG) 2.2 level AA by reference.

Intellectual Property Rights (IPRs) essential or potentially essential to normative deliverables may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (https://ipr.etsi.org/). Please visit ETSI IPR database to search for any IPRs.

Annexes include definitions and references.

The information in this document uses the language from Clauses 5-13 and Annex B (informative): Relationship between requirements and functional performance criteria from the EN 301 549 V4.1.1 (2026-09) Harmonised European Standard – Accessibility requirements for ICT products and services.

Sources used to compile this document

• EN 301 549 V4.1.1 (2026-09) Harmonised European Standard - Accessibility requirements for ICT products and services (PDF)
• Web Content Accessibility Guidelines (WCAG) 2.2 (W3C Recommendation 12 December 2024)
• Comparison with WCAG 2.1
• ITI VPAT® EN 301 549 (EU) version

Part A – 4.2 Functional Performance Criteria

4.2.1 Usage without vision

Where ICT provides visual modes of operation, the ICT shall provide at least one mode of operation that does not require vision. 

4.2.2 Usage with limited vision

Where ICT provides visual modes of operation, the ICT shall provide features that enable users to make better use of their limited vision. 

4.2.3 Usage without perception of colour

Where ICT provides visual modes of operation, the ICT shall provide a visual mode of operation that does not require user perception of colour. 

4.2.4 Usage without hearing

Where ICT provides auditory modes of operation, the ICT shall provide at least one mode of operation that does not require hearing. 

4.2.5 Usage with limited hearing

Where ICT provides auditory modes of operation, the ICT shall provide enhanced audio features.

4.2.6 Usage with no or limited vocal capability

Where ICT requires vocal input from users, the ICT shall provide at least one mode of operation that does not require them to generate vocal output. 

4.2.7 Usage with limited manipulation or strength

Where ICT requires manual actions, the ICT shall provide features that enable users to make use of the ICT through alternative actions not requiring manipulation, simultaneous action or hand strength.

4.2.8 Usage with limited reach

Where ICT is stationary, free-standing or installed, all the elements required for operation shall be within reach of all users.

4.2.9 Minimize photosensitive seizure triggers

Where ICT provides visual modes of operation, the ICT shall provide at least one mode of operation, that is the default mode, that minimizes the potential for triggering photosensitive seizures or optionally, for audiovisual material, a warning in advance that such triggers might be present.

4.2.10 Usage with limited cognition, language or learning

Where ICT provides information or requires user interaction, the ICT shall provide features and/or presentation that makes it simpler and easier to understand, operate and use.

4.2.11 Privacy

Where ICT provides features for accessibility,

the ICT shall ensure that the privacy of the users of the ICT is maintained irrespective of the use of these features for accessibility.

Part B - Functional Accessibility Requirements

Explanation of the table

The table consists of a single column which contains the following key information:

• The clause from the EN 301 549 which applies to the ICT
• The associated "relationship to Functional Performance Criterion" as indicated in Annex B
  • Table B.1: Key to the column header designations used in Table B.2

Column header abbreviation	Functional performance criterion	Clause number
WV	Usage without vision	4.2.1
LV	Usage with limited vision	4.2.2
WPC	Usage without perception of colour	4.2.3
WH	Usage without hearing	4.2.4
LH	Usage with limited hearing	4.2.5
WVC	Usage without vocal capability	4.2.6
LMS	Usage with limited manipulation or strength	4.2.7
LR	Usage with limited reach	4.2.8
PST	Minimize photosensitive seizure triggers	4.2.9
LC	Usage with limited cognition	4.2.10
PR	Privacy	4.2.11

• The following abbreviations have been used to represent the relationship between the requirements in clauses 5 to 13 and the functional performance criteria:
  • P = Primary relationship. The requirement supports the functional performance criterion.
  • S = Secondary relationship. The requirement provides partial support for the functional performance criterion because some users may use the feature in specific situations.

Found in this section

• 5 Generic requirements
• 6 ICT supporting real-time bidirectional communication
• 7 ICT with video capabilities
• 8 Hardware
• 9 Web
• 10 Non-web documents
• 11 Non-web software
• 12 Information about products and services
• 13 ICT providing relay or emergency service access
• Annex - Tables and figures (from EN 301 549)
• Annex - References (from EN 301 549)
• Annex – Definition of terms, symbols and abbreviations (from EN 301 549)

5 Generic requirements

5.1 Closed functionality

5.1.1 Introduction (informative)

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.

5.1.2 General

5.1.2.1 Closed functionality

Where ICT includes closed functionality, the closed functionality shall meet 5.1. For the non-closed functionality the applicable requirements set out in clauses 5.2 to 13 shall be met.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage without perception of colour (WPC), Usage without hearing (WH), Usage with limited hearing (LH), Usage without vocal capability (WVC), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Minimize photosensitive seizure triggers (PST), Usage with limited cognition (LC), Privacy (P)

5.1.2.2 Assistive technology and closed functionality

Where ICT includes closed functionality, that closed functionality shall be operable without requiring the user to attach, connect or install assistive technology and meet the generic requirements of clauses 5.1.3 to 5.1.6 as applicable. Personal headsets and personal induction loops are not classed as assistive technology for the purpose of this clause.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage without hearing (WH), Usage with limited hearing (LH), Usage without vocal capability (WVC), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Usage with limited cognition (LC), Privacy (P)

5.1.3 Non-visual access

5.1.3.1 Auditory output of visual information

Where ICT includes closed functionality, and visual information is needed to enable the use of the closed functionality of the ICT, the closed functionality shall be provided through one or more non-visual means that includes auditory output to enable the use of those functions.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV)

Secondary: Usage with limited vision (LV), Usage with limited cognition (LC)

5.1.3.2 Auditory output delivery including speech

Where ICT includes closed functionality, and auditory output is provided as non-visual access to closed functionality, the auditory output shall be delivered through one of the following:

1. directly by a mechanism included in or provided with the ICT; or
2. by a personal headset that can be connected through a 3,5 mm audio jack without requiring the use of vision; or
3. if it is a personal device (not a public-shared-use device), by a personal headset connected through any standard industry headset connection.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV)

Secondary: Usage with limited vision (LV), Usage with limited cognition (LC)

5.1.3.3 Auditory output correlation

Where ICT includes closed functionality, and auditory output is provided as non-visual access to closed functionality, and information that is under the control of the ICT is displayed on the screen, the ICT shall provide auditory information that includes all the non-decorative information displayed on the current screen.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV)

Secondary: Usage with limited cognition (LC)

5.1.3.4 Speech output user control

Where ICT includes closed functionality, and 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.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV)

Secondary: Usage with limited vision (LV), Usage with limited cognition (LC)

5.1.3.5 Speech output automatic interruption

Where ICT includes closed functionality, and speech output is provided as non-visual access to closed functionality, and the speech output is generated to provide feedback on user interface choices and user actions, the ICT shall interrupt current speech output when a user action occurs and when new speech output begins.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV)

Secondary: Usage with limited vision (LV), Usage with limited cognition (LC)

5.1.3.6 Auditory output for non-text content

Where ICT includes closed functionality that presents non-text content other than video, any alternative for non-text content shall be presented to users via auditory output, including speech, unless the non-text content is pure decoration or is used only for visual formatting.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV)

Secondary: Usage with limited vision (LV), Usage with limited cognition (LC)

5.1.3.7 Auditory output for video information

Where ICT includes closed functionality, and pre-recorded video content is needed to enable the use of closed functionality of the ICT, an auditory equivalent shall be provided for the pre-recorded video content originating from the ICT, and, if provided from another source along with video content, it is also made available by the ICT.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV)

Secondary: Usage with limited vision (LV), Usage with limited cognition (LC)

5.1.3.8 Masked entry

Where ICT includes closed functionality, and 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 if the option exists and the user explicitly chooses to allow non private auditory output.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Privacy (PR)

Secondary: Usage with limited vision (LV), Usage with limited cognition (LC)

5.1.3.9 Private access to personal data

Where ICT includes closed functionality, and the ICT is intended for public shared use, and auditory output is provided by that ICT as non-visual access to closed functionality, and that 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.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Privacy (PR)

Secondary: Usage with limited vision (LV), Usage with limited cognition (LC)

5.1.3.10 Non-interfering audio output

Where ICT includes closed functionality, and auditory output is provided as non-visual access to closed functionality, the ICT shall not automatically play, at the same time, any interfering audible output that lasts longer than three seconds.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV)

Secondary: Usage with limited vision (LV), Usage with limited cognition (LC)

5.1.3.11 Private listening volume

Where ICT includes closed functionality, and auditory output is provided as non-visual access to closed functionality, and the auditory output is delivered through a mechanism for private listening, the ICT shall provide at least one non-visual mode of operation for controlling the volume.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV)

Secondary: Usage with limited vision (LV), Usage with limited cognition (LC)

5.1.3.12 Speaker volume

Where ICT includes closed functionality, and auditory output is provided as non-visual access to closed functionality, and is delivered through speakers on the ICT, a non-visual incremental volume control shall be provided with output amplification up to a level of at least 65 dBA (-29 dBPaA).

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV)

Secondary: Usage with limited vision (LV), Usage with limited cognition (LC)

5.1.3.13 Volume reset

Where ICT includes closed functionality, and the ICT is intended for public shared use, and auditory output is provided as non-visual access to closed functionality through a mechanism for private listening, a function that resets the volume to be at a level of 65 dBA or less after every use, shall be provided.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV)

Secondary: Usage with limited vision (LV), Usage with limited cognition (LC)

5.1.3.14 Spoken languages

Where ICT includes closed functionality, and speech output is provided as non-visual access to closed functionality, the speech output shall be in the same human language as the displayed content provided, except:

1. 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;
2. where the content is generated externally and not under the control of the ICT vendor, the present clause shall not be required to apply for languages not supported by the ICT's speech synthesizer;
3. for displayed languages that cannot be selected using non-visual access;
4. where the user explicitly selects a speech language that is different from the language of the displayed content.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV)

Secondary: Usage with limited vision (LV), Usage with limited cognition (LC)

5.1.3.15 Non-visual error identification

Where ICT includes closed functionality, and speech output is provided as non-visual access to closed functionality, and an input error is automatically detected, and the error is indicated visually via text and/or other visual means, the speech output shall present equivalent error information.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV)

Secondary: Usage with limited vision (LV), Usage with limited cognition (LC)

5.1.3.16 Receipts, tickets, and transactional outputs

Where ICT includes closed functionality, and provides physical receipts, tickets or other outputs as a result of a self service transaction, output that provides all information necessary to complete or verify the transaction shall be provided through one or more non-visual means that includes auditory output, except information that is printed and that is not needed to complete the transaction, such as receipts, itineraries, maps, etc.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV)

Secondary: Usage with limited vision (LV), Usage with limited cognition (LC)

5.1.4 Functionality closed to text enlargement

Where ICT includes closed functionality, and any functionality of the ICT is closed to the text enlargement features of its 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 the x-height of the text is at least 16 CSSpx.

Relationship between requirements and functional performance criteria:

Primary: Usage with limited vision (LV)

5.1.5 Visual output for auditory information

Where ICT includes closed functionality, and auditory output is needed to enable the use of closed functionality of the ICT, the ICT shall provide visual information that is equivalent to the auditory information.

Relationship between requirements and functional performance criteria:

Primary: Usage without hearing (WH), Usage with limited hearing (LH)

Secondary: Usage with limited cognition (LC)

5.1.6 Operation without keyboard interface

5.1.6.1 Functionality closed to keyboards

Where ICT includes closed functionality, and the functionality is closed to keyboards or keyboard interfaces, the functionality closed to keyboards or keyboard interfaces shall be operable without vision as required by clause 5.1.3.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR)

Secondary: Usage with limited cognition (LC)

5.1.6.2 Input focus

Where ICT includes closed functionality, and the 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.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage without vocal capability (WVC), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR)

5.1.7 Access without speech

Where ICT includes closed functionality, and speech is needed to operate closed functionality of the ICT, the ICT shall provide at least one mode of operation using an alternative input mechanism that does not require speech.

Relationship between requirements and functional performance criteria:

Primary: Usage without vocal capability (WVC)

Secondary: Usage without hearing (WH), Usage with limited hearing (LH), Usage with limited cognition (LC)

5.1.8 Identify input purpose (closed functionality)

Where ICT includes closed functionality, and input field(s) collecting information about the user are needed to enable the use of the closed functionality of the ICT, and the input field(s) serve a purpose identified in the WCAG 2.2 Input Purposes for User Interface Components section [4], in at least one mode of operation the ICT shall present to the user, in an audio form, the purpose of each of these input fields.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage with limited cognition (LC)

5.2 Activation of accessibility features

Where ICT includes 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.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage without perception of colour (WPC), Usage without hearing (WH), Usage with limited hearing (LH), Usage without vocal capability (WVC), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Minimize photosensitive seizure triggers (PST), Usage with limited cognition (LC), Privacy (PR)

5.3 Biometrics

Where ICT uses biological characteristics, the ICT shall not rely on the use of a biological characteristic as the only means of user identification or for control of the ICT.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage without hearing (WH), Usage with limited hearing (LH), Usage without vocal capability (WVC), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Privacy (PR)

5.4 Preservation of accessibility information during conversion

Where ICT converts information or communication, the ICT 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.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage without perception of colour (WPC), Usage without hearing (WH), Usage with limited hearing (LH), Usage without vocal capability (WVC), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Minimize photosensitive seizure triggers (PST), Usage with limited cognition (LC), Privacy (PR)

5.5 Tactilely discernible operable parts

Where ICT includes functionality that requires manual operation and control, the ICT shall provide a mode of operation that allows all the functionality of the ICT that requires manual operation and control to be controlled without requiring vision using only tactilely discernible operable parts.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV)

Secondary: Usage with limited manipulation or strength (LMS), Usage with limited cognition (LC)

5.6 Locking or toggle controls

5.6.1 Tactile or auditory status

Where ICT includes a locking or toggle control, 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.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV)

Secondary: Usage with limited cognition (LC)

5.6.2 Visual status

Where ICT includes a locking or toggle control, 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.

Relationship between requirements and functional performance criteria:

Primary: Usage without hearing (WH), Usage with limited hearing (LH), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR)

Secondary: Usage with limited cognition (LC)

5.7 Key repeat

Where ICT includes a keyboard or keypad, and a key repeat function that cannot be turned off, and that key repeat will result in the generation of multiple entries of the same alphanumeric data into input fields or into documents:

1. the delay before the key repeat shall be adjustable to at least 2 seconds; and
2. the key repeat rate shall be adjustable down to one character per 2 seconds.

Relationship between requirements and functional performance criteria:

Primary: Usage with limited manipulation or strength (LMS)

Secondary: Usage with limited reach (LR), Usage with limited cognition (LC)

5.8 Double-strike key acceptance

Where ICT includes a device-independent keyboard interface service, keyboard, or keypad, and includes a capability to adjust the time before the same key can be accepted again, the delay after any keystroke, during which the same key-press will not be accepted, shall be adjustable up to at least 0,5 seconds.

Relationship between requirements and functional performance criteria:

Primary: Usage with limited manipulation or strength (LMS)

Secondary: Usage with limited reach (LR), Usage with limited cognition (LC)

5.9 Simultaneous user actions

Where ICT includes a mode of operation requiring simultaneous user actions for its operation, the ICT shall provide at least one mode of operation that does not require simultaneous user actions to operate the ICT.

Relationship between requirements and functional performance criteria:

Primary: Usage with limited manipulation or strength (LMS), Usage with limited reach (LR)

Secondary: Usage with limited cognition (LC)

5.10 Authoring tools

5.10.0 General (informative)

For those creating web content authoring tools, ATAG 2.0 [i.33] provides information that can be of interest to those who want to go beyond these requirements.

5.10.1 Content technology

Where ICT is, or includes, authoring tool functionality, the authoring tool shall meet clauses 5.10.2 to 5.10.5 to the extent that information required for accessibility is supported by the format used for the output of the authoring tool.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage without perception of colour (WPC), Usage without hearing (WH), Usage with limited hearing (LH), Usage without vocal capability (WVC), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Minimize photosensitive seizure triggers (PST), Usage with limited cognition (LC), Privacy (PR)

5.10.2 Accessible content creation

Where ICT is, or includes, authoring tool functionality, the authoring tool shall enable and guide the production of content that conforms to clause 9 (web), or clause 10 (Non web documents), or clause 11 (Non-web software) as applicable.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage without perception of colour (WPC), Usage without hearing (WH), Usage with limited hearing (LH), Usage without vocal capability (WVC), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Minimize photosensitive seizure triggers (PST), Usage with limited cognition (LC), Privacy (PR)

5.10.3 Preservation of accessibility information in transformations

Where ICT is, or includes, authoring tool functionality, and provides restructuring transformations or re-coding transformations, accessibility information shall be preserved in the output if equivalent mechanisms exist in the content technology of the output.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage without perception of colour (WPC), Usage without hearing (WH), Usage with limited hearing (LH), Usage without vocal capability (WVC), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Minimize photosensitive seizure triggers (PST), Usage with limited cognition (LC), Privacy (PR)

5.10.4 Repair assistance

Where ICT is, or includes, authoring tool functionality, and is capable of detecting that content does not meet a requirement of clause 9 (Web), or clause 10 (Non-web document), or clause 11 (Non-web software) as applicable, the authoring tool shall provide repair suggestion(s).

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage without perception of colour (WPC), Usage without hearing (WH), Usage with limited hearing (LH), Usage without vocal capability (WVC), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Minimize photosensitive seizure triggers (PST), Usage with limited cognition (LC), Privacy (PR)

5.10.5 Templates

Where ICT is, or includes, authoring tool functionality, and provides templates, at least one template that supports the creation of content that conforms to the requirements of clause 9 (Web) or clause 10 (Non-web document). or clause 11 (Non-web software) as applicable shall be available and identified as such.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage without perception of colour (WPC), Usage without hearing (WH), Usage with limited hearing (LH), Usage without vocal capability (WVC), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Minimize photosensitive seizure triggers (PST), Usage with limited cognition (LC), Privacy (PR)

6 ICT supporting real-time bidirectional communication

6.0 Accessible real-time bidirectional communication operational scenarios

6.0.1 Rationale for scenarios (informative)

Clauses 6.0.2 to 6.0.5 specify a minimum set of operational scenarios in which real-time bidirectional communication typically takes place. To deliver the goal of accessible communications it is necessary to ensure that applicable accessibility requirements defined in clauses 6.1 to 6.6 are met in all applicable scenarios for the communication described by the scenarios.

Clauses 6.0.6 to 6.0.9 specify a minimum set of operational scenarios in which ICT is expected to deliver emergency communications. To ensure that emergency communications are accessible, it is necessary to ensure that ICT meets the applicable accessibility requirements defined in clauses 6.1 to 6.6  of the present document in all applicable scenarios for the emergency communications described by the scenarios.

6.0.2 Communication client

Where ICT is, or includes, a communication client that supports real-time bidirectional voice communication with or within a communication system that provides real-time bidirectional voice communication, the communication client shall meet all applicable 6.1 and 6.3 to 6.6 requirements, when communicating with or within the communication system, and, where the communication client is part of a terminal with text handling capabilities, all applicable 6.2 requirements.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage without hearing (WH), Usage with limited hearing (LH), Usage without vocal capability (WVC)

Secondary: Usage with limited cognition (LC)

6.0.3 Communication system

Where ICT is, or includes, or is a part of, a communication system that provides real-time bidirectional voice communication with communication clients of the system, the system shall meet all applicable 6.1 to 6.6 requirements when communicating with communication clients.

EXAMPLE: The suitability of a home/office internet router for correctly handling RTT communication can be evaluated by ensuring that this router is part of the local ICT that is used to perform a test of RTT communication routed through the real-time bidirectional voice communication system.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage without hearing (WH), Usage with limited hearing (LH), Usage without vocal capability (WVC)

Secondary: Usage with limited cognition (LC)

6.0.4 System connecting to another communication system

Where ICT is, or includes, a communication system that provides real-time bidirectional voice communication with one or more other communication systems that support real-time bidirectional voice communication, the system shall meet all applicable 6.1 to 6.6 requirements when communicating with the other communication systems.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage without hearing (WH), Usage with limited hearing (LH), Usage without vocal capability (WVC)

Secondary: Usage with limited cognition (LC)

6.0.5 System with roaming visiting client

Where ICT is, or includes, a communication system that provides real-time bidirectional voice communication, and a communication client that supports real-time bidirectional voice communication with another compatible communication system, visits and connects to the communication system, the system shall meet all applicable 6.1 to 6.6 requirements when communicating with the visiting communication client.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage without hearing (WH), Usage with limited hearing (LH), Usage without vocal capability (WVC)

Secondary: Usage with limited cognition (LC)

6.0.6 Client in emergency communications

Where ICT is required to provide, or otherwise provides, emergency communications, and is, or includes, a communication client that supports real-time bidirectional voice communication with or within a communication system that provides real-time bidirectional voice emergency communication, the communication client shall meet applicable 6.1 and 6.3 to 6.6 requirements, when performing the emergency communication, and, where the communication client is part of a terminal with text handling capabilities, all applicable 6.2 requirements.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage without hearing (WH), Usage with limited hearing (LH), Usage without vocal capability (WVC)

Secondary: Usage with limited cognition (LC)

6.0.7 Emergency communications

Where ICT is, or includes, a communication system that provides real-time bidirectional voice communication in emergency communications with PSAPs, the communication system shall meet all applicable 6.1 to 6.6 requirements, when performing the emergency communication.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage without hearing (WH), Usage with limited hearing (LH), Usage without vocal capability (WVC)

Secondary: Usage with limited cognition (LC)

6.0.8 System with roaming visiting client in an emergency

Where ICT is, or includes, a (first) communication system that provides real-time bidirectional voice communication in emergency communications with PSAPs, and a communication client that supports real-time bidirectional voice communication with another compatible communication system that provides real-time bidirectional voice communication, visits and connects to the (first) communication system, the (first) communication system shall meet all applicable 6.1 to 6.6 requirements, when communicating with the visiting communication client and a PSAP in emergency communications.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage without hearing (WH), Usage with limited hearing (LH), Usage without vocal capability (WVC)

Secondary: Usage with limited cognition (LC)

6.0.9 System with client in emergency visiting another country

Where ICT is, or includes, a communication system that provides real-time bidirectional voice communication in emergency communications with PSAPs, and a communication client of the ICT that supports real-time bidirectional voice communication, visits another country than the home country, the communication system shall meet applicable 6.1 to 6.6 requirements when communicating with the communication client and a PSAP in the visited country in emergency communications.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage without hearing (WH), Usage with limited hearing (LH), Usage without vocal capability (WVC)

Secondary: Usage with limited cognition (LC)

6.1 Real-time bidirectional voice communication

6.1.1 Voice communication interoperability

Where ICT provides functionality that allows real-time bidirectional voice communication, and connects to other ICT that allows real-time bidirectional voice communication, the ICT's documentation shall contain information on the main specifications by which voice is implemented in a manner that allows the voice on the ICT to interoperate with the other ICT, providing electronic communication covering audio frequencies at least down to 100 Hz and at least up to 7 000 Hz using one of the following options:

1. Any set of specifications for voice communication that would fulfil the voice communications requirements in the present document that is mutually agreed to be used between the ICT and any other ICT with which the ICT interoperates for real-time bidirectional voice communication.
2. Recommendation ITU-T G.722 [i.20].

1. General VoIP and Multimedia communication: IETF, providing standards for Voice Over IP (VOIP) and Multimedia communications over IP based on the Session Initiation Protocol (SIP) IETF RFC 3261 [i.50]. In this technology, the following audio codecs capable of delivering sufficient quality are commonly used:
   • Recommendation ITU-T G.722 [i.20];
   • Recommendation ITU‑T G.722.2 [i.21] also called AMR-WB;
   • IETF RFC 6716 [i.83] defining the Opus Audio Codec, and updated by
   • IETF RFC 8251 [i.86].
2. IP Multimedia Sub-System (IMS): 3GPP, that provides standards for mobile communication systems, including IP Multimedia Sub-System (IMS) has standardized the Multimedia Telephony concept, for communications with voice, video and RTT using the set of protocols specified in ETSI TS 126 114 [i.11]:
   • Recommendation ITU‑T G.722.2 [i.21], also called AMR-WB for wide band audio;
   • EVS specified in ETSI TS 126 441 [i.88];
   • For interoperability with other systems Recommendation ITU-T G.722 [i.20] is specified.
3. GSMA, that provides selected profiles of standards for implementing globally interoperating mobile communications services, has in GSMA PRD IR.92 [i.45] specified how to apply ETSI TS 126 114 [i.11] to implement RTT and Voice over LTE (VoLTE) and, in GSMA PRD IR.94 [i.46], Video over LTE (ViLTE) in 4G mobile systems. A similar document is published for RTT, voice and video over 5G in GSMA NG.114 [i.46]. Wide band audio is specified in these documents to use the same audio codecs as under b).
4. Web technologies: For communication in web technologies, W3C^® and IETF have created the WebRTC concept specified in IETF RFC 8825 [i.87] where the mandatory audio codecs with wide band audio capabilities are specified in IETF RFC 7874 [i.84] to be Opus, while Recommendation ITU T G.722 [i.20] is also recommended by IETF RFC 7875 [i.85] and is usually provided in implementations.
5. Emergency communications: An interface to IP based emergency communications is specified in ETSI TS 103 479 [i.48]. It makes use of Recommendation ITU-T G.722.2 [i.21] AMR-WB, IETF RFC 6716 [i.83] updated by IETF RFC 8251 OPUS, and Recommendation ITU-T G.722 [i.20]. for wide-band audio. A corresponding standard exists for North America. For emergency apps, ETSI TS 103 478 [i.47] is specified in ETSI TS 103 945 [i.89] to implement wide band audio by use of Opus IETF RFC 6716 [i.83] updated by IETF RFC 8251 [i.86]. The use of these standards for accessible and interoperable emergency communications is specified in ETSI TS 103 919 [i.56].
6. Relay services: ETSI ES 202 975 [i.6] specifies in its clause 6.1 interfaces to relay services, referring to the present document for specific technologies.

Relationship between requirements and functional performance criteria:

Primary: Usage with limited hearing (LH)

6.1.2 Audio bandwidth for capture and presentation for voice communication

Where ICT provides functionality that allows real-time bidirectional voice communication, and has a user interface for real-time bidirectional voice communication, the ICT shall be able to capture, communicate and present voice communication with a frequency range of at least down to 250 Hz and up to at least 7 000 Hz.

Relationship between requirements and functional performance criteria:

Primary: Usage with limited hearing (LH)

6.1.3 Audio presentation in attached listening devices for voice communication (recommendation)

Where ICT provides functionality that allows real-time bidirectional voice communication, and has an interface for external presentation of voice communication, the ICT should be able to present audio with a frequency range of at least down to 100 Hz and up to at least 7 000 Hz.

Relationship between requirements and functional performance criteria:

Primary: Usage with limited hearing (LH)

6.1.4 Synchronization of subtitles (recommendation)

Where ICT provides subtitles for real-time bidirectional voice communication, the delay of provided subtitles in relation to the speech should not exceed 2 seconds.

Relationship between requirements and functional performance criteria:

Primary: Usage without hearing (WH), Usage with limited hearing (LH)

6.2 Real-Time Text (RTT)

6.2.1 RTT provision

6.2.1.1 RTT functionality

Where ICT provides functionality that allows real-time bidirectional voice communication, the ICT shall provide functionality that allows real-time bidirectional RTT communication.

Relationship between requirements and functional performance criteria:

Primary: Usage without hearing (WH), Usage with limited hearing (LH), Usage without vocal capability (WVC)

6.2.1.2 Concurrent voice and RTT

Where ICT provides real-time bidirectional voice communication, and supports RTT, the ICT shall allow concurrent voice and RTT.

Relationship between requirements and functional performance criteria:

Primary: Usage without hearing (WH), Usage with limited hearing (LH), Usage without vocal capability (WVC)

6.2.1.3 Single user action

Where ICT provides real-time bidirectional voice communication, and includes RTT capabilities, the ICT shall allow single user operations to act on all requested or already established media, during requests to establish media, answering requests to establish media, modifications during the communication, and disconnections.

Relationship between requirements and functional performance criteria:

Primary: Usage without hearing (WH), Usage with limited hearing (LH), Usage without vocal capability (WVC)

6.2.2 Display of RTT

6.2.2.1 Distinguishable display

Where ICT supports real-time bidirectional voice communication, and includes RTT presentation capabilities, displayed text that originates from different sources, as well as the text that is sent, shall be displayed with their sources indicated and differentiated.

Relationship between requirements and functional performance criteria:

Primary: Usage without hearing (WH), Usage with limited hearing (LH), Usage without vocal capability (WVC)

6.2.2.2 Active communicator indication

Where ICT supports real-time bidirectional voice communication, and includes RTT send and receive capabilities, and provides speaker indication for voice, the ICT shall provide indication of all active communicators including those using RTT.

Relationship between requirements and functional performance criteria:

Primary: Usage without hearing (WH), Usage with limited hearing (LH), Usage without vocal capability (WVC)

6.2.2.3 Indication of audio with RTT

Where ICT provides real-time bidirectional voice communication, and supports RTT, the ICT shall provide a real-time indicator of non-local audio activity on the display.

Relationship between requirements and functional performance criteria:

Primary: Usage without hearing (WH), Usage with limited hearing (LH), Usage without vocal capability (WVC)

6.2.2.4 Presentation of relative time order of text

Where ICT supports real-time bidirectional voice communication, and includes RTT presentation capabilities, the ICT shall present the text from each source, including the local source, as blocks of text that are arranged in order based on the point in time that each block of text is terminated by any sentence-terminating punctuation character followed by a space, or a line separator character is entered or received, or 5 seconds passes without a new character being entered or received. Editing of text in a block causes the entire block's termination time to change to the time of the last edited character.

Relationship between requirements and functional performance criteria:

Primary: Usage without hearing (WH), Usage with limited hearing (LH), Usage without vocal capability (WVC)

6.2.2.5 Review of RTT communication contents

Where ICT supports real-time bidirectional voice communication, and includes RTT presentation capabilities, the ICT shall provide the ability to review the whole RTT content of the communication during the communication and, if the communication is recorded, after the communication has ended.

Relationship between requirements and functional performance criteria:

Primary: Usage without hearing (WH), Usage with limited hearing (LH), Usage without vocal capability (WVC)

6.2.3 DTMF touch-tone generation during RTT operations

Where ICT is, or includes, a communication client, and provides functionality that allows real-time bidirectional voice communication, and supports the generation and transmission of touch-tone signals on voice calls, the client shall provide a method for generation and transmission of touch-tone signals for touch-tone characters (0-9,*,#,A,B,C,D) that is distinct from the method for generating RTT for those same characters, and is compatible with the standard method for sending touch-tones during voice calls.

Relationship between requirements and functional performance criteria:

Primary: Usage without hearing (WH), Usage with limited hearing (LH), Usage without vocal capability (WVC)

6.2.4 RTT responsiveness

Where ICT is, or includes, a communication client, and supports real-time bidirectional voice communication, and supports RTT, RTT input shall be transmitted to the ICT network on which the ICT runs within 500 ms of the time that the smallest reliably composed unit of text entry is available to the ICT for transmission where delays due to network performance are not included in the 500 ms limit.

Relationship between requirements and functional performance criteria:

Primary: Usage without hearing (WH), Usage with limited hearing (LH), Usage without vocal capability (WVC)

6.2.5 Adding and erasing of RTT input

Where ICT supports real-time bidirectional voice communication, and includes RTT capabilities, and supports RTT user input, the RTT user interface shall provide the functionality to enter new text and to erase text entered in an ongoing communication where the erasure is done from the current end of text without being limited by any new line or other delimiter in the earlier text.

Relationship between requirements and functional performance criteria:

Primary: Usage without hearing (WH), Usage with limited hearing (LH), Usage without vocal capability (WVC)

6.2.6 Processing rate of RTT

Where ICT supports real-time bidirectional voice communication, and supports multiparty communication, and includes RTT capabilities, the ICT shall have the capacity to receive and process RTT at a total rate of 90 characters per second coming from a minimum of 3 simultaneous sources sending 30 characters per second each.

Relationship between requirements and functional performance criteria:

Primary: Usage without hearing (WH), Usage with limited hearing (LH), Usage without vocal capability (WVC)

6.2.7 Character representation

Where ICT supports real-time bidirectional voice communication, and includes RTT capabilities, the ICT shall be capable of handling at least a subset of ISO/IEC 10646 [i.53] that includes at least:

• the Latin-1 part;
• the writing direction(s) and the characters for the languages of the regions in which the ICT is intended to be used;
• any emoji characters supported by the underlying platform;
• the ISO/IEC 10646 [i.53] "replacement character" (HEX:FFFD) used for indication of unsupported and lost characters, including emojis; and
• any characters used by the presentation protocol.

Relationship between requirements and functional performance criteria:

Primary: Usage without hearing (WH), Usage with limited hearing (LH), Usage without vocal capability (WVC)

6.2.8 RTT input methods

Where ICT is, or includes, a communication client, and supports real-time bidirectional voice communication, and supports RTT, the client shall provide RTT input methods in all ways available for general text input by the ICT.

Relationship between requirements and functional performance criteria:

Primary: Usage without hearing (WH), Usage with limited hearing (LH), Usage without vocal capability (WVC), Usage with limited manipulation or strength (LMS)

Secondary: Usage with limited reach (LR), Usage with limited cognition (LC)

6.2.9 RTT media establishment and use

Where ICT supports real-time bidirectional voice communication, and includes RTT capabilities, all of the following shall be true for the ICT regardless of any system or client settings:

• it is possible to request establishment of a communication with RTT media;
• it is possible to answer a request for a communication and get RTT media included regardless of whether it was included in the original request;
• it is possible to upgrade an existing communication by any party to include RTT media.

Relationship between requirements and functional performance criteria:

Primary: Usage without hearing (WH), Usage with limited hearing (LH), Usage without vocal capability (WVC)

6.2.10 RTT interoperability

Where ICT provides functionality that allows real-time bidirectional voice communication, and connects to other ICT that allows real-time bidirectional voice communication, the ICT's documentation shall contain information on the main specifications by which RTT is implemented in a manner that allows the RTT on the ICT to interoperate with the other ICT that the ICT interoperates with for voice, using one of the following options:

1. Any set of specifications for RTT communication that would fulfil the RTT requirements in the present document that is mutually agreed to be used between the ICT and any other ICT with which the ICT interoperates for real-time bidirectional voice communication.
2. Recommendation ITU-T T.140 [i.37] for functions including coding and presentation and IETF RFC 4103 [i.13] updated by IETF RFC 9071 [i.52] for other aspects of RTT communication.

1. General VoIP and Multimedia communication: IETF, providing standards for Voice Over IP (VOIP) and Multimedia communications over IP based on the Session Initiation Protocol (SIP) IETF RFC 3261 [i.50], has published IETF RFC 4103 [i.13] for session establishment and transport of RTT over RTP IETF RFC 3550 [i.51] and its update IETF RFC 9071 [i.52] for multiparty use.
2. IP Multimedia Sub-System (IMS): 3GPP, providing standards for mobile communication systems, including IP Multimedia Sub-System (IMS) has standardized the Multimedia Telephony concept, for communications with voice, video and RTT using the set of protocols specified in ETSI TS 126 114 [i.11] to create the services including RTT and Total Conversation services specified in ETSI TS 122 173 [i.12]. Multimedia Telephony is specified to use IETF RFC 4103 [i.13] updated by IETF RFC 9071 [i.52] for session establishment and transport of RTT over RTP or the RTT based on WebRTC Data Channel Technologies. Details of the use of these variants can be found in ETSI TR 126 982 [i.43].
   It should be noted that 3GPP and GSMA use the following varying terms for RTT: GTT, Global Text Telephony, GTT-IP, RTT, real time text, and text.
3. GSMA, providing selected profiles of standards for implementing globally interoperating mobile communication services has in GSMA PRD IR.92 [i.44] specified how to apply ETSI TS 126 114 [i.11] to implement RTT and Voice over LTE (VoLTE) and in GSMA PRD IR.94 [i.45] Video over LTE (ViLTE) in 4G mobile systems. A similar document is published for RTT, voice and video over 5G in GSMA NG.114 [i.46]. RTT is specified in these documents in clause B.2 to use ETSI TS 126 114 [i.11] for session establishment and transport of RTT.
4. Web technologies: For communication in web technologies, W3C and IETF have created the WebRTC concept where the Reliable WebRTC Data channel concept IETF RFC 8831 [i.57] in its section 3.2 use case U-C 5 is recommended to be used for RTT. The use of WebRTC Data Channels in web pages and apps is specified in W3C WebRTC: Real-Time Communication in Browsers [i.58].
5. Emergency communications: An interface to IP based emergency communications is specified in ETSI TS 103 479 [i.48], making use of IETF RFC 4103 [i.13] updated by IETF RFC 9071 [i.52] for RTT. A corresponding standard exists for North America. For emergency apps, ETSI TS 103 478 [i.47] is specified to implement RTT as specified in ETSI TS 103 871 [i.49]. The use of these standards for accessible and interoperable emergency communications including the use of RTT is specified in ETSI TS 103 919 [i.56]
6. Relay services: ETSI ES 202 975 [i.6] specifies in its Annexes A and B interfaces to relay services, referring to the present document for specific technologies.

Relationship between requirements and functional performance criteria:

Primary: Usage without hearing (WH), Usage with limited hearing (LH), Usage without vocal capability (WVC)

6.3 Caller ID

Where ICT provides caller identification or other identification functions, the caller identification and other identification functions shall be available in text form as well as being programmatically determinable, for all functionality that is not closed to programmatic access of information by assistive technologies.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV)

Secondary: Usage with limited cognition (LC)

6.4 Alternatives to voice-based services

Where ICT provides voice mail, auto-attendant, or interactive voice response facilities, the ICT shall offer users a means to access the information and carry out the tasks provided by the ICT without the use of hearing or speech.

Relationship between requirements and functional performance criteria:

Primary: Usage without hearing (WH), Usage with limited hearing (LH), Usage without vocal capability (WVC)

6.5 Video communication

6.5.1 General (informative)

Clause 6.5 (Video communication) provides performance requirements that support users who communicate using sign language and lip-reading. For these users, good usability is achieved with a resolution of at least Quarter Video Graphics Array (QVGA, 320 × 240), 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.

Increasing the resolution and frame rate further improves both sign language (especially finger spelling) and lipreading, with frame rate being more important than resolution.

Time differences between audio and video (asynchronicity) can have a great impact on lip-reading - with video that lags behind audio having greater negative effect.

End-to-end latency can be a problem in video (sign) communication. Overall delay values below 400 ms are preferred, with an increase in preference down to 100 ms. Overall delay depends on multiple factors, including e.g. network delay and video processing. For this reason a testable requirement on minimum values for overall delay cannot be produced.

6.5.2 Resolution

Where ICT provides real-time bidirectional voice communication, and includes real-time bidirectional video communication, the ICT:

1. shall support at least QVGA resolution;
2. should preferably support at least VGA resolution.

Relationship between requirements and functional performance criteria:

Primary: Usage without hearing (WH), Usage with limited hearing (LH)

Secondary: Usage without vocal capability (WVC), Usage with limited cognition (LC)

6.5.3 Frame rate

Where ICT provides real-time bidirectional voice communication, and includes real-time bidirectional video communication, the ICT:

1. shall support a frame rate of at least 20 Frames Per Second (FPS);
2. should preferably support a frame rate of at least 30 Frames Per Second (FPS) with or without sign language in the video stream.

Relationship between requirements and functional performance criteria:

Primary: Usage without hearing (WH), Usage with limited hearing (LH)

Secondary: Usage without vocal capability (WVC), Usage with limited cognition (LC)

6.5.4 Synchronization between audio and video

Where ICT provides real-time bidirectional voice communication, and includes real-time bidirectional video communication, the ICT shall ensure that voice is received by the user not earlier than 100 ms before and not later than 100 ms after the corresponding video is presented to the user.

Relationship between requirements and functional performance criteria:

Primary: Usage without hearing (WH), Usage with limited hearing (LH)

Secondary: Usage without vocal capability (WVC), Usage with limited cognition (LC)

6.5.5 Indicator of audio with video

Where ICT provides real-time bidirectional voice communication, and includes real-time bidirectional video communication, the ICT shall provide a real-time indicator of audio activity.

Relationship between requirements and functional performance criteria:

Primary: Usage without hearing (WH), Usage with limited hearing (LH)

Secondary: Usage without vocal capability (WVC), Usage with limited cognition (LC)

6.5.6 Indication of all active communication participants

Where ICT provides real-time bidirectional voice communication, includes real-time bidirectional video communication, and provides speaker indication for voice users, the ICT shall provide indication of all active communicators including those signing.

Relationship between requirements and functional performance criteria:

Primary: Usage without hearing (WH), Usage with limited hearing (LH)

Secondary: Usage without vocal capability (WVC), Usage with limited cognition (LC)

6.6 Alternatives to video-based services (recommendation)

Where ICT provides real-time bidirectional voice communication, and includes real-time bidirectional video communication, and 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:

1. for audible information, without the use of hearing;
2. for spoken commands, without the use of speech;
3. for visual information, without the use of vision.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage without hearing (WH), Usage with limited hearing (LH), Usage without vocal capability (WVC),

Secondary: Usage with limited cognition (LC)

6.7 Total conversation

6.7.1 Total conversation provision

Where ICT provides real-time bidirectional voice communication, and includes real-time bidirectional video functionality, the ICT shall provide total conversation by also including RTT capability that conforms to the requirements of clause 6.2, voice that conforms to clause 6.1, and video that conforms to clause 6.5, conforming also to clauses 6.3 and 6.4.

Relationship between requirements and functional performance criteria:

Primary: Usage without hearing (WH), Usage with limited hearing (LH), Usage without vocal capability (WVC)

Secondary: Usage with limited cognition (LC)

6.7.2 Total conversation interoperability

Where ICT provides functionality that allows real-time bidirectional voice communication, and includes real-time bidirectional video functionality, and connects to other ICT that allows real-time bidirectional voice communication, including real-time bidirectional video functionality, the ICT's documentation shall contain information on the main specifications by which video is implemented in a manner that allows the video on the ICT to interoperate with other ICT that the ICT interoperates with for voice and video, using one of the following options:

1. Any set of specifications for video communication that would fulfil the total conversation requirements in the present document that is mutually agreed to be used between the ICT and any other ICT with which the ICT interoperates for real-time bidirectional voice and video communication.
2. Recommendation ITU-T H.264 [i.74] at least version 10 and at least constrained baseline level 3 for functions including coding and presentation, and/or, where codec negotiation is implemented, Recommendation ITU-T H.265 [i.75] and IETF RFC 6386 VP8 [i.76] to avoid transcoding.

Relationship between requirements and functional performance criteria:

Primary: Usage without hearing (WH), Usage with limited hearing (LH), Usage without vocal capability (WVC)

Secondary: Usage with limited cognition (LC)

7 ICT with video capabilities

7.1 Subtitle processing technology

7.1.1 Subtitle playback

Where ICT displays video with synchronized audio, the ICT shall have a mode of operation to display the available subtitles. Where closed subtitles are provided as part of the content, the ICT shall allow the user to choose to display the subtitles.

Relationship between requirements and functional performance criteria:

Primary: Usage without hearing (WH), Usage with limited hearing (LH)

Secondary: Usage with limited cognition (LC)

7.1.2 Subtitle synchronization

Where ICT displays video with synchronized audio, and displays subtitles, the ICT shall display subtitles within 100 ms of the timecode value attached to the subtitle.

Relationship between requirements and functional performance criteria:

Primary: Usage without hearing (WH), Usage with limited hearing (LH)

Secondary: Usage with limited cognition (LC)

7.1.3 Preservation of subtitles

Where ICT transmits, converts, or records video with synchronized audio, the ICT shall preserve subtitle data such that the subtitles can be displayed in a manner consistent with clause 7.1.1, including any data relating to presentational aspects such as screen position, text and background colours, text style and text fonts.

Relationship between requirements and functional performance criteria:

Primary: Usage without hearing (WH), Usage with limited hearing (LH)

Secondary: Usage with limited cognition (LC)

7.1.4 Subtitle characteristics

Where ICT displays video with synchronized audio, and has control over the presentation of its subtitles, the ICT shall provide a way for the user to adapt the displayed characteristics of subtitles to their individual requirements, except where the subtitles are displayed as unmodifiable characters.

Relationship between requirements and functional performance criteria:

Primary: Usage without hearing (WH), Usage with limited hearing (LH), Usage with limited cognition (LC)

7.1.5 Spoken subtitles

Where ICT displays video with synchronized audio, the ICT shall have a mode of operation to enable output of the available spoken subtitles.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage with limited cognition (LC)

7.2 Audio description technology

7.2.1 Audio description playback

Where ICT displays video with synchronized audio, the ICT 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 one of several audio tracks.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage with limited cognition (LC)

7.2.2 Audio description synchronization

Where ICT displays video with synchronized audio, and has a mechanism to play audio description, the ICT shall preserve the synchronization between the audio/visual content and the corresponding audio description.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage with limited cognition (LC)

7.2.3 Preservation of audio description

Where ICT transmits, converts, or records video with synchronized audio, the ICT shall preserve audio description data such that the audio description can be played in a manner consistent with clauses 7.2.1 and 7.2.2.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage with limited cognition (LC)

7.3 User control of audiovisual accessibility features

Where ICT primarily displays video with synchronized audio, and has control over the activation of subtitles, audio description, and spoken subtitles, the ICT shall provide at least one mode of operation that allows the activation and deactivation of the user's choice of either subtitles, audio description, or spoken subtitles with a single user operation that is at the same level as the volume control and that meets the other accessibility requirements of the present document.

EXAMPLE: One solution would be to have a single button at the volume control level, bring up a list of subtitles, audio description, spoken subtitles and (potentially) other accessibility features if it was held down for more than 2 seconds. The user could activate any accessibility feature from that menu - as well as chose an accessibility feature that would be turned on and off with a single short press of the same button that was used to bring up the menu with a long press. (If this was standardized across manufacturers it would facilitate dissemination of information about this feature and provide cross-manufacturer consistency). It is best practice to have a dedicated button for doing the above (providing single button to both chose and then later activate the single chosen function with a simple press), but a button that exists in a current design, like the mute button, could be repurposed for this where a remote has only a few buttons and a dedicated button cannot be provided.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage without hearing (WH), Usage with limited hearing (LH), Usage with limited cognition (LC)

8 Hardware

8.1 General

The "generic requirements" of clause 5 also apply to ICT that is hardware.

8.2 Hardware products with speech output

8.2.1 Speech volume

8.2.1.1 Speech volume gain

Where ICT is, or includes, hardware, and has speech output, and is a device that is typically held to the ear, the ICT shall provide a means to adjust the speech output volume level to achieve at least 18 dB of conversational gain.

Relationship between requirements and functional performance criteria:

Primary: Usage with limited hearing (LH)

8.2.1.2 Incremental volume control

Where ICT is, or includes, hardware, and has speech output, and is a device that is typically held to the ear, and its volume control is incremental, the ICT shall provide at least one intermediate step of 12 dB gain above the lowest volume setting.

Relationship between requirements and functional performance criteria:

Primary: Usage with limited hearing (LH)

8.2.2 Magnetic coupling

8.2.2.1 Fixed-line devices and handsets

Where ICT is, or includes, hardware, and has speech output, and is a fixed-line communication device or wired handset that is typically held to the ear, the ICT shall provide a means of magnetic coupling to hearing technologies which meets the requirements of ETSI ES 200 381-1 [2] and shall be marked as being compatible with magnetic coupling if the ICT is designed for public use.

Relationship between requirements and functional performance criteria:

Primary: Usage with limited hearing (LH)

8.2.2.2 Wireless communication devices

Where ICT is, or includes, hardware, and has speech output, and is a wireless communication device that is typically held to the ear, the ICT shall provide a means of magnetic coupling and reduced interference to hearing technologies which meets the requirements of ETSI ES 200 381-2 [3].

Relationship between requirements and functional performance criteria:

Primary: Usage with limited hearing (LH)

8.3 Stationary ICT

8.3.1 General (informative)

The present document defines the requirements for the design of stationary ICT that can be placed in a built environment, but does not define the dimensions of the built environment. The current clause contains only those accessibility requirements that are caused by functional and design requirements of the ICT.

The scope includes stationary ICT and includes ICT installed in closed spaces (typically kiosks and cabins).

Access space and manoeuvring space needed to access the stationary ICT (whether inside or outside of a closed space) are out of the scope of this clause 8.3. Advice and requirements related to the size and design of access spaces can be found in [i.35], [i.64] and [i.63].

For certain stationary ICT it may not be possible to meet the requirements in some clauses due to functional or design requirements which restrict the possible design of stationary ICT. The present document contains therefore two sets of requirements for ICT with no functional or design restrictions (8.3.3.1, 8.3.5.1, 8.3.7.1, 8.3.9.2, 8.3.10.2, or 8.3.11.1,) (called "Set 1") and for ICT with functional or design restrictions (8.3.3.2, 8.3.5.2, 8.3.7.2, 8.3.9.3, 8.3.10.3, or 8.3.11.2) (called "Set 2").

Stationary ICT which is unable to meet the requirements in Set 1 is expected to meet the requirements in Set 2.

If in a specified location several stationary ICT devices with identical functionality and purpose are installed, it may be possible to apply the requirements of this clause 8.3 to only a limited number of these stationary ICT devices. This exception and how it may be handled is out of scope of this clause 8.3.

8.3.2 Display screen location

Where ICT is stationary ICT, display screens which are part of the ICT shall be placed in a way that no part of the display extends below 800 mm above the floor of the access space.

Relationship between requirements and functional performance criteria:

Primary: Usage with limited manipulation or strength (LMS), Usage with limited reach (LR)

8.3.3 Presentation of information necessary for the operation of stationary ICT

8.3.3.1 Presentation of information necessary for the operation of stationary ICT (no design restrictions)

Where ICT is stationary ICT and there are no functional or design requirements which do not allow to present necessary information below 1 600 mm above the floor space, information necessary to operate the stationary ICT shall be placed not higher than 1 600 mm above the floor of the access space.

Relationship between requirements and functional performance criteria:

Primary: Usage with limited manipulation or strength (LMS), Usage with limited reach (LR)

8.3.3.2 Presentation of information necessary for the operation of stationary ICT (with design restrictions)

Where ICT is stationary ICT and there are functional or design requirements which do not allow to present necessary information below 1 600 mm above the floor space
information necessary to operate the stationary ICT shall be placed not higher than 2 000 mm above the floor of the access space.

Relationship between requirements and functional performance criteria:

Primary: Usage with limited manipulation or strength (LMS), Usage with limited reach (LR)

8.3.4 Legibility of display screens (informative)

Where a display screen has closed functionality regarding text enlargement, clause 5.1.4 applies.

Where a display screen is a touch screen, the requirements in clauses 8.3.5 and 8.3.6 apply.

8.3.5 Control location (vertical)

8.3.5.1 Control location (vertical, no design restrictions)

Where ICT is stationary ICT and there are no functional or design requirements which do not allow to duplicate operable parts or locate them above 800 mm and below 1 100 mm, at least one of each type of operable part shall be located in an elevation between 800 mm (minimum) and 1 100 mm (maximum) above the floor of the floor space.

Relationship between requirements and functional performance criteria:

Primary: Usage with limited manipulation or strength (LMS), Usage with limited reach (LR)

8.3.5.2 Control location (vertical, with design restrictions)

Where ICT is stationary ICT and there are functional or design requirements which do not allow duplication of operable parts or locate them above 800 mm and below 1 100 mm, the minimum height of operable parts which cannot be duplicated shall be 380 mm, and the maximum height of operable parts which cannot be duplicated shall be 1 220 mm, and access to operable parts which cannot be copied shall not be hindered by obstructions.

Relationship between requirements and functional performance criteria:

Primary: Usage with limited manipulation or strength (LMS), Usage with limited reach (LR)

8.3.6 Control location (horizontal)

Where ICT is stationary ICT, at least one of each type of operable part shall be located in an area that has a maximum horizontal extent of 900 mm.

Relationship between requirements and functional performance criteria:

Primary: Usage with limited manipulation or strength (LMS), Usage with limited reach (LR)

8.3.7 Reach depth

8.3.7.1 Reach depth (no design restrictions)

Where ICT is stationary ICT, and there are no functional or design requirements which do not allow duplication of operable parts or locating them in an area that has a maximum distance of 300 mm from the edge of the ICT, at least one of each type of operable part shall be located in an area that has a maximum distance of 300 mm from the edge of the ICT which has the shortest distance to the user.

Relationship between requirements and functional performance criteria:

Primary: Usage with limited manipulation or strength (LMS), Usage with limited reach (LR)

8.3.7.2 Reach depth (with design restrictions)

Where ICT is stationary ICT, and there are functional or design requirements which do not allow duplication of operable parts or locating them in an area that has a maximum distance of 300 mm from the edge of the ICT, at least one of each type of operable part shall be located in an area that has a maximum distance of 510 mm (for forward reach) and 610 mm (for side reach) from the edge of the ICT which has the shortest distance to the user.

Relationship between requirements and functional performance criteria:

Primary: Usage with limited manipulation or strength (LMS), Usage with limited reach (LR)

8.3.8 Forward or side reach (informative)

Stationary ICT may be designed to enable users of wheeled mobility devices to access the stationary ICT for forward reach or for side reach.

1. For simple interactions (e.g. pushing a button, pulling a ticket), side reach is sufficient.
2. For more comprehensive interactions (e.g. reading comprehensive information on a screen, entering non sensitive information on an input device), forward reach is preferred.
3. For interactions where privacy is essential and/or physical effort is required, forward approach is the best solution where other design constraints permit.
4. For ICT devices which require the use of both hands for control and input, forward reach is necessary.

Relationship between requirements and functional performance criteria:

Primary: Usage with limited manipulation or strength (LMS), Usage with limited reach (LR)

8.3.9 Forward reach

8.3.9.1 Unobstructed forward reach (informative)

For unobstructed forward reach clauses 8.3.5 and 8.3.6 define the correct positioning of controls.

8.3.9.2 Obstructed forward reach (no design constraints)

Where ICT is stationary ICT, and has an obstruction that is an integral part of the ICT (this is called obstructed forward reach), and there are no functional or design constraints which require an obstruction deeper than 300 mm, the ICT shall be designed so that:

1. the height of the obstruction shall not exceed 800 mm;
2. the maximum depth of the obstruction shall not exceed 300 mm.

Relationship between requirements and functional performance criteria:

Primary: Usage with limited manipulation or strength (LMS), Usage with limited reach (LR)

8.3.9.3 Obstructed forward reach (with design constraints)

Where ICT is stationary ICT, and has an obstruction that is an integral part of the ICT (this is called obstructed forward reach), and there are functional or design constraints which require an obstruction deeper than 300 mm
the ICT shall be designed so that:

1. the height of the obstruction shall not exceed 800 mm
2. the maximum depth of the obstruction shall not exceed 510 mm

Relationship between requirements and functional performance criteria:

Primary: Usage with limited manipulation or strength (LMS), Usage with limited reach (LR)

8.3.10 Side reach

8.3.10.1 Unobstructed side reach (informative)

For unobstructed side reach clauses 8.3.5 and 8.3.6 define the correct positioning of controls.

Relationship between requirements and functional performance criteria:

Primary: Usage with limited manipulation or strength (LMS), Usage with limited reach (LR)

8.3.10.2 Obstructed side reach (no design constraints)

Where ICT is stationary ICT, and has an obstruction that is an integral part of the ICT (this is called obstructed side reach), and there are no functional or design constraints which require an obstruction deeper than 300 mm, the ICT shall be designed so that:

1. the height of the obstruction shall not exceed 800 mm;
2. the maximum depth of the obstruction shall not exceed 300 mm.

Relationship between requirements and functional performance criteria:

Primary: Usage with limited manipulation or strength (LMS), Usage with limited reach (LR)

8.3.10.3 Obstructed side reach (with design constraints)

Where ICT is stationary ICT, and has an obstruction that is an integral part of the ICT (this is called obstructed side reach), and there are functional or design constraints which require an obstruction deeper than 300 mm, the ICT shall be designed so that:

1. the height of the obstruction shall not exceed 865 mm;
2. the maximum depth of the obstruction shall not exceed 610 mm.

This is shown in Figure 8.1: Obstructed side reach (see Table 8.1 for explanations)

8.3.11 Free space underneath stationary ICT with or without an obstruction

8.3.11.1 Free space underneath stationary ICT with or without an obstruction (no design constraints)

Where ICT is stationary ICT and there are no functional or design constraints which prevent the provision of a free space underneath the ICT or restrict the size of that free space, the stationary ICT shall provide an open space (knee and toe clearance) with the dimensions listed in Table 8.2, column "Values for stationary ICT which complies with clause 8.3.11.1" (see Figure 8.2).

This is shown in Figure 8.2: Knee and toe clearance underneath an obstruction (see Table 8.2 for explanations)

8.3.11.2 Free space underneath stationary ICT with or without an obstruction (with design constraints)

Where ICT is stationary ICT and there are no functional or design constraints which prevent the provision of a free space underneath the ICT, but there are functional or design requirements restricting the size of an open space below the ICT, the stationary ICT shall provide an open space (knee and toe clearance) with the dimensions listed in Table 8.2, column "Values for stationary ICT which complies with clause 8.3.11.2". (see Figure 8.2).

• Security requirements (e.g. for ATMs).
• Vandalism protection.
• Need to have operable parts below the limits set in clause 8.3.5.1.
• Positioning stationary ICT freestanding (with a base which is part of the stationary ICT) and related stability requirements.
• There may be legal requirements or national standards which restrict the design of stationary ICT to exclude the provision of free space underneath such stationary ICT.

Relationship between requirements and functional performance criteria:

Primary: Usage with limited manipulation or strength (LMS), Usage with limited reach (LR)

8.3.12 Floor characteristics (informative)

All floor characteristics including floor level changes, clear floor requirements, and the dimensions of necessary manoeuvring spaces are not caused by functional or design requirements of the stationary ICT and are therefore not in scope of this clause.

Advice and requirements related to the floor characteristics can be found in ISO 21542 [i.35] and [i.63].

There should be no change in floor level inside a kiosk, cabin or other closed space in which stationary ICT is installed.

8.3.13 Approach (informative)

The dimensions of the space required in front of stationary ICT for approaching the stationary ICT are not derived from functional or design requirements of the stationary ICT and are therefore not in scope of this clause.

Advice and requirements related to access and manoeuvring spaces can be found in [i.35] and [i.63].

8.3.14 Installation instructions

Where ICT is stationary ICT, installation instructions shall be made available, that give guidance on how to install the ICT in compliance with the applicable requirements of clause 8.3 of the present document and take into account applicable requirements for accessibility of the built environment as they apply to the installation of the ICT.

Relationship between requirements and functional performance criteria:

Primary: Usage with limited manipulation or strength (LMS), Usage with limited reach (LR)

8.4 Operable parts

8.4.1 Numeric keys

Where ICT is, or includes, hardware, and has physical numeric keys arranged in a rectangular keypad layout, the number five key shall be tactilely distinct from the other keys of the keypad.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Usage with limited cognition (LC)

Secondary: Usage with limited vision (LV)

8.4.2 Operation of operable parts

8.4.2.1 Means of operation

Where ICT is, or includes, hardware, and has operable parts that require grasping, pinching, or twisting of the wrist to operate, the ICT shall provide at least one mode of operation that does not require these actions.

Relationship between requirements and functional performance criteria:

Primary: Usage with limited manipulation or strength (LMS)

Secondary: Usage with limited reach (LR)

8.4.2.2 Force of operation of operable parts

Where ICT is, or includes, hardware, and has a control that requires a force greater than 22,2 N to operate it, the ICT shall provide a means of operation that does not requires a force greater than 22,2 N.

Relationship between requirements and functional performance criteria:

Primary: Usage with limited manipulation or strength (LMS)

Secondary: Usage with limited reach (LR)

8.4.3 Keys, tickets and cards

Where ICT is, or includes, hardware, and has keys, tickets or cards, and the orientation of the keys, tickets or cards is important for further use, the keys, tickets or cards shall each have an orientation that is tactilely discernible.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage with limited cognition (LC)

8.5 Tactile indication of speech mode

Where ICT is, or includes, hardware, and the ICT is intended for public shared use, and speech output is available, a tactile indication of the means to initiate the speech mode of operation shall be provided.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV)

Secondary: Usage with limited vision (LV), Usage with limited cognition (LC)

8.6 Standard connections

Where ICT is, or includes, hardware, and provides 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.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage with limited hearing (LH), Usage without vocal capability (WVC), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Usage with limited cognition (LC)

8.7 Colour on hardware

Where ICT is, or includes, hardware, and colour is used on the hardware to convey information, colour shall not be used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.

Relationship between requirements and functional performance criteria:

Primary: Usage without perception of colour (WPC)

Secondary: Usage with limited vision (LV), Usage with limited cognition (LC)

8.8 Contrast on hardware

Where ICT is, or includes, hardware, non-digitally displayed characters or symbols required for use, or hardware operable parts without labels on them that are not tactilely discernible, shall contrast visually from their background as either light on a dark background or dark on a light background.

Relationship between requirements and functional performance criteria:

Primary: Usage with limited vision (LV), Usage without perception of colour (WPC)

Secondary: Usage with limited cognition (LC)

9 Web

9.0 General (informative)

Requirements in clause 9 apply to web pages including:

• Conformance with W3C^® Web Content Accessibility Guidelines (WCAG 2.0) [i.41] Level AA is equivalent to conforming with clauses 9.1.1, 9.1.2, 9.1.3.1 to 9.1.3.3, 9.1.4.1 to 9.1.4.5, 9.2.1.1, 9.2.1.2, 9.2.2, 9.2.3, 9.2.4 except 9.2.4.11, 9.3 except 9.3.2.6, 9.3.3.7 and 9.3.3.8, 9.4.1.2 and the conformance requirements of clause 9.6 of the present document.
• Conformance with W3C Web Content Accessibility Guidelines (WCAG 2.1) [i.42] Level AA is equivalent to conforming with all of clauses 9.1 to 9.4 except 9.2.4.11, 9.2.5.7, 9.2.5.8, 9.3.2.6, 9.3.3.7, 9.3.3.8 and with the conformance requirements of clause 9.6 of the present document.
• Conformance with W3C Web Content Accessibility Guidelines (WCAG 2.2) [4] Level AA is equivalent to conforming with all of clauses 9.1 to 9.4 and the conformance requirements of clause 9.6 of the present document.
• Requirements for non-web documents and non-web software are given in clauses 10 and 11 respectively.

The requirements in clauses 9.1 to 9.4 are written using the concept of satisfying success criteria (defined in clause 3.1). A web page satisfies a WCAG success criterion when the success criterion does not evaluate to false when applied to the web page. This implies that if the success criterion puts conditions on a specific feature and that specific feature does not occur in the web page, then the web page satisfies the success criterion.

EXAMPLE: For example, a web page that does not contain pre-recorded audio content in synchronized media will automatically satisfy WCAG success criterion 1.2.2 (captions - pre-recorded) and, in consequence, will also meet clause 9.1.2.2.

In addition to Level AA success criteria, the Web Content Accessibility Guidelines also include success criteria for Level AAA. These are listed in clause 9.5 of the present document. Web authors and procurement accessibility specialists are encouraged to consider whether any of the WCAG Level AAA success criteria offer suggestions that may be applicable and relevant to their project, as well as potentially beneficial to some users.

9.1 Perceivable

9.1.1 Text alternatives

9.1.1.1 Non-text content

Where ICT is, or includes, a web page, the web page shall satisfy WCAG 2.2 Success Criterion 1.1.1 Non-text content.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage without hearing (WH), Usage with limited hearing (LH)

Secondary: Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Usage with limited cognition (LC)

9.1.2 Time-based media

9.1.2.1 Audio-only and video-only (pre-recorded)

Where ICT is, or includes, a web page, the web page shall satisfy WCAG 2.2 Success Criterion 1.2.1 Audio-only and Video-only (Prerecorded).

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage without hearing (WH), Usage with limited hearing (LH)

Secondary: Usage with limited cognition (LC)

9.1.2.2 Subtitles (pre-recorded)

Where ICT is, or includes, a web page, the web page shall satisfy WCAG 2.2 Success Criterion 1.2.2 Captions (Prerecorded).

Relationship between requirements and functional performance criteria:

Primary: Usage without hearing (WH), Usage with limited hearing (LH)

Secondary: Usage with limited cognition (LC)

9.1.2.3 Audio description or media alternative (pre-recorded)

Where ICT is, or includes, a web page, the web page shall satisfy WCAG 2.2 Success Criterion 1.2.3 Audio Description or Media Alternative (Prerecorded).

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV)

Secondary: Usage with limited vision (LV), Usage with limited cognition (LC)

9.1.2.4 Subtitles (live)

Where ICT is, or includes, a web page, the web page shall satisfy WCAG 2.2 Success Criterion 1.2.4 Captions (Live).

Relationship between requirements and functional performance criteria:

Primary: Usage without hearing (WH), Usage with limited hearing (LH), Usage with limited cognition (LC)

9.1.2.5 Audio description (pre-recorded)

Where ICT is, or includes, a web page, the web page shall satisfy WCAG 2.2 Success Criterion 1.2.5 Audio Description (Prerecorded).

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV)

Secondary: Usage with limited vision (LV), Usage with limited cognition (LC)

9.1.3 Adaptable

9.1.3.1 Info and relationships

Where ICT is, or includes, a web page, the web page shall satisfy WCAG 2.2 Success Criterion 1.3.1 Info and Relationships.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV)

Secondary: Usage with limited vision (LV), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Usage with limited cognition (LC)

9.1.3.2 Meaningful sequence

Where ICT is, or includes, a web page, the web page shall satisfy WCAG 2.2 Success Criterion 1.3.2 Meaningful Sequence.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV)

Secondary: Usage with limited vision (LV), Usage with limited cognition (LC)

9.1.3.3 Sensory characteristics

Where ICT is, or includes, a web page, the web page shall satisfy WCAG 2.2 Success Criterion 1.3.3 Sensory Characteristics.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage without perception of colour (WPC), Usage without hearing (WH), Usage with limited hearing (LH)

Secondary: Usage with limited cognition (LC)

9.1.3.4 Orientation

Where ICT is, or includes, a web page, the web page shall satisfy WCAG 2.2 Success Criterion 1.3.4 Orientation.

Relationship between requirements and functional performance criteria:

Primary: Usage with limited vision (LV), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR),

Secondary: Usage with limited cognition (LC)

9.1.3.5 Identify input purpose

Where ICT is, or includes, a web page, the web page shall satisfy WCAG 2.2 Success Criterion 1.3.5 Identify Input Purpose.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage with limited cognition (LC)

Secondary: Usage with limited manipulation or strength (LMS), Usage with limited reach (LR)

9.1.4 Distinguishable

9.1.4.1 Use of colour

Where ICT is, or includes, a web page, the web page shall satisfy WCAG 2.2 Success Criterion 1.4.1 Use of Color.

Relationship between requirements and functional performance criteria:

Primary: Usage with limited vision (LV), Usage without perception of colour (WPC),

Secondary: Usage with limited cognition (LC)

9.1.4.2 Audio control

Where ICT is, or includes, a web page, the web page shall satisfy WCAG 2.2 Success Criterion 1.4.2 Audio Control.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited hearing (LH), Usage with limited cognition (LC)

Secondary: Usage with limited vision (LV)

9.1.4.3 Contrast (minimum)

Where ICT is, or includes, a web page, the web page shall satisfy WCAG 2.2 Success Criterion 1.4.3 Contrast (Minimum).

Relationship between requirements and functional performance criteria:

Primary: Usage with limited hearing (LH), Usage with limited cognition (LC)

9.1.4.4 Resize text

Where ICT is, or includes, a web page, the web page shall satisfy WCAG 2.2 Success Criterion 1.4.4 Resize text.

Relationship between requirements and functional performance criteria:

Primary: Usage with limited hearing (LH), Usage with limited cognition (LC)

9.1.4.5 Images of text

Where ICT is, or includes, a web page, the web page shall satisfy WCAG 2.2 Success Criterion 1.4.5 Images of Text.

Relationship between requirements and functional performance criteria:

Primary: Usage with limited vision (LV), Usage without perception of colour (WPC), Usage with limited cognition (LC)

9.1.4.6 Void

9.1.4.7 Void

9.1.4.8 Void

9.1.4.9 Void

9.1.4.10 Reflow

Where ICT is, or includes, a web page, the web page shall satisfy WCAG 2.2 Success Criterion 1.4.10 Reflow.

Relationship between requirements and functional performance criteria:

Primary: Usage with limited vision (LV), Usage with limited cognition (LC)

9.1.4.11 Non-text contrast

Where ICT is, or includes, a web page, the web page shall satisfy WCAG 2.2 Success Criterion 1.4.11 Non-text Contrast.

Relationship between requirements and functional performance criteria:

Primary: Usage with limited vision (LV), Usage with limited cognition (LC)

9.1.4.12 Text spacing

Where ICT is, or includes, a web page, the web page shall satisfy WCAG 2.2 Success Criterion 1.4.12 Text spacing.

Relationship between requirements and functional performance criteria:

Primary: Usage with limited vision (LV), Usage with limited cognition (LC)

9.1.4.13 Content on hover or focus

Where ICT is, or includes, a web page, the web page shall satisfy WCAG 2.2 Success Criterion 1.4.13 Content on Hover or Focus.

Relationship between requirements and functional performance criteria:

Primary: Usage with limited vision (LV), Usage with limited manipulation or strength (LMS). Usage with limited cognition (LC)

9.2 Operable

9.2.1 Keyboard accessible

9.2.1.1 Keyboard

Where ICT is, or includes, a web page, the web page shall satisfy WCAG 2.2 Success Criterion 2.1.1 Keyboard.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR)

9.2.1.2 No keyboard trap

Where ICT is, or includes, a web page, the web page shall satisfy WCAG 2.2 Success Criterion 2.1.2 No Keyboard Trap.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR)

9.2.1.3 Void

9.2.1.4 Character key shortcuts

Where ICT is, or includes, a web page, the web page shall satisfy WCAG 2.2 Success Criterion 2.1.4 Character Key Shortcuts.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR)

Secondary: Usage with limited cognition (LC)

9.2.2 Enough time

9.2.2.1 Timing adjustable

Where ICT is, or includes, a web page, the web page shall satisfy WCAG 2.2 Success Criterion 2.2.1 Timing Adjustable.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage without hearing (WH), Usage with limited hearing (LH), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Usage with limited cognition (LC)

9.2.2.2 Pause, stop, hide

Where ICT is, or includes, a web page, the web page shall satisfy WCAG 2.2 Success Criterion 2.2.2 Pause, Stop, Hide.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage without hearing (WH), Usage with limited hearing (LH), Usage with limited cognition (LC)

Secondary: Usage with limited manipulation or strength (LMS), Usage with limited reach (LR)

9.2.3 Seizures and physical reactions

9.2.3.1 Three flashes or below threshold

Where ICT is, or includes, a web page, the web page shall satisfy WCAG 2.2 Success Criterion 2.3.1 Three Flashes or Below Threshold.

Relationship between requirements and functional performance criteria:

Primary: Minimize photosensitive seizure triggers (PST)

9.2.4 Navigable

9.2.4.1 Bypass blocks

Where ICT is, or includes, a web page, the web page shall satisfy WCAG 2.2 Success Criterion 2.4.1 Bypass Blocks.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Usage with limited cognition (LC)

9.2.4.2 Page titled

Where ICT is, or includes, a web page, the web page shall satisfy WCAG 2.2 Success Criterion 2.4.2 Page Titled.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Usage with limited cognition (LC)

9.2.4.3 Focus order

Where ICT is, or includes, a web page, the web page shall satisfy WCAG 2.2 Success Criterion 2.4.3 Focus Order.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Usage with limited cognition (LC)

9.2.4.4 Link purpose (in context)

Where ICT is, or includes, a web page, the web page shall satisfy WCAG 2.2 Success Criterion 2.4.4 Link Purpose (In Context).

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Usage with limited cognition (LC)

9.2.4.5 Multiple ways

Where ICT is, or includes, a web page, the web page shall satisfy WCAG 2.2 Success Criterion 2.4.5 Multiple Ways.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage without vocal capability (WVC), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Usage with limited cognition (LC)

9.2.4.6 Headings and labels

Where ICT is, or includes, a web page, the web page shall satisfy WCAG 2.2 Success Criterion 2.4.6 Headings and Labels.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage without vocal capability (WVC), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Usage with limited cognition (LC)

Secondary: Usage without hearing (WH)

9.2.4.7 Focus visible

Where ICT is, or includes, a web page, the web page shall satisfy WCAG 2.2 Success Criterion 2.4.7 Focus Visible.

Relationship between requirements and functional performance criteria:

Primary: Usage with limited vision (LV), Usage without vocal capability (WVC), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Usage with limited cognition (LC)

9.2.4.8 Void

9.2.4.9 Void

9.2.4.10 Void

9.2.4.11 Focus not obscured (minimum)

Where ICT is, or includes, a web page, the web page shall satisfy WCAG 2.2 Success Criterion 2.4.11 Focus Not Obscured (Minimum).

Relationship between requirements and functional performance criteria:

Primary: Usage with limited vision (LV), Usage without vocal capability (WVC), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Usage with limited cognition (LC)

9.2.5 Input modalities

9.2.5.1 Pointer gestures

Where ICT is, or includes, a web page, the web page shall satisfy WCAG 2.2 Success Criterion 2.5.1 Pointer Gestures.

Relationship between requirements and functional performance criteria:

Primary: Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Usage with limited cognition (LC)

9.2.5.2 Pointer cancellation

Where ICT is, or includes, a web page, the web page shall satisfy WCAG 2.2 Success Criterion 2.5.2 Pointer Cancellation.

Relationship between requirements and functional performance criteria:

Primary: Usage with limited vision (LV), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Usage with limited cognition (LC)

9.2.5.3 Label in name

Where ICT is, or includes, a web page, the web page shall satisfy WCAG 2.2 Success Criterion 2.5.3 Label in Name.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR)

Secondary: Usage with limited cognition (LC)

9.2.5.4 Motion actuation

Where ICT is, or includes, a web page, the web page shall satisfy WCAG 2.2 Success Criterion 2.5.4 Motion Actuation.

Relationship between requirements and functional performance criteria:

Primary: Usage with limited manipulation or strength (LMS), Usage with limited reach (LR)

Secondary: Usage without vision (WV), Usage with limited vision (LV), Usage with limited cognition (LC)

9.2.5.5 Void

9.2.5.6 Void

9.2.5.7 Dragging movements

Where ICT is, or includes, a web page, the web page shall satisfy WCAG 2.2 Success Criterion 2.5.7 Dragging Movements.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR)

Secondary: Usage with limited cognition (LC)

9.2.5.8 Target size (minimum)

Where ICT is, or includes, a web page, the web page shall satisfy WCAG 2.2 Success Criterion 2.5.8 Target Size (Minimum).

Relationship between requirements and functional performance criteria:

Primary: Usage with limited vision (LV), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR)

Secondary: Usage with limited cognition (LC)

9.3 Understandable

9.3.1 Readable

9.3.1.1 Language of page

Where ICT is, or includes, a web page, the web page shall satisfy WCAG 2.2 Success Criterion 3.1.1 Language of Page.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited cognition (LC)

Secondary: Usage with limited vision (LV), Usage without hearing (WH), Usage with limited hearing (LH), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR)

9.3.1.2 Language of parts

Where ICT is, or includes, a web page, the web page shall satisfy WCAG 2.2 Success Criterion 3.1.2 Language of Parts.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited cognition (LC)

Secondary: Usage with limited vision (LV), Usage without hearing (WH), Usage with limited hearing (LH), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR)

9.3.2 Predictable

9.3.2.1 On focus

Where ICT is, or includes, a web page, the web page shall satisfy WCAG 2.2 Success Criterion 3.2.1 On Focus.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Usage with limited cognition (LC)

9.3.2.2 On input

Where ICT is, or includes, a web page, the web page shall satisfy WCAG 2.2 Success Criterion 3.2.2 On Input.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Usage with limited cognition (LC)

9.3.2.3 Consistent navigation

Where ICT is, or includes, a web page, the web page shall satisfy WCAG 2.2 Success Criterion 3.2.3 Consistent Navigation.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage with limited cognition (LC)

Secondary: Usage with limited manipulation or strength (LMS), Usage with limited reach (LR)

9.3.2.4 Consistent identification

Where ICT is, or includes, a web page, the web page shall satisfy WCAG 2.2 Success Criterion 3.2.4 Consistent Identification.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage with limited cognition (LC)

Secondary: Usage with limited manipulation or strength (LMS), Usage with limited reach (LR)

9.3.2.5 Void

9.3.2.6 Consistent help

Where ICT is, or includes, a web page, the web page shall satisfy WCAG 2.2 Success Criterion 3.2.6 Consistent Help.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage with limited cognition (LC)

Secondary: Usage with limited manipulation or strength (LMS), Usage with limited reach (LR)

9.3.3 Input assistance

9.3.3.1 Error identification

Where ICT is, or includes, a web page, the web page shall satisfy WCAG 2.2 Success Criterion 3.3.1 Error Identification.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage without perception of colour (WPC), Usage with limited cognition (LC)

Secondary: Usage without hearing (WH), Usage with limited hearing (LH), Usage without vocal capability (WVC), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Minimize photosensitive seizure triggers (PST)

9.3.3.2 Labels or instructions

Where ICT is, or includes, a web page, the web page shall satisfy WCAG 2.2 Success Criterion 3.3.2 Labels or Instructions.

Relationship between requirements and functional performance criteria:

Primary: Usage with limited cognition (LC)

Secondary: Usage without vision (WV), Usage with limited vision (LV), Usage without perception of colour (WPC), Usage without hearing (WH), Usage with limited hearing (LH), Usage without vocal capability (WVC), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Minimize photosensitive seizure triggers (PST)

9.3.3.3 Error suggestion

Where ICT is, or includes, a web page, the web page shall satisfy WCAG 2.2 Success Criterion 3.3.3 Error Suggestion.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage without perception of colour (WPC), Usage with limited cognition (LC)

Secondary: Usage without hearing (WH), Usage with limited hearing (LH), Usage without vocal capability (WVC), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Minimize photosensitive seizure triggers (PST)

9.3.3.4 Error prevention (legal, financial, data)

Where ICT is, or includes, a web page, the web page shall satisfy WCAG 2.2 Success Criterion 3.3.4 Error Prevention (Legal, Financial, Data).

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage without perception of colour (WPC), Minimize photosensitive seizure triggers (PST), Usage with limited cognition (LC), Privacy (PR)

Secondary: Usage without hearing (WH), Usage with limited hearing (LH), Usage without vocal capability (WVC), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR)

9.3.3.5 Void

9.3.3.6 Void

9.3.3.7 Redundant entry

Where ICT is, or includes, a web page, the web page shall satisfy WCAG 2.2 Success Criterion 3.3.7 Redundant Entry.

Relationship between requirements and functional performance criteria:

Primary: Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Usage with limited cognition (LC)

Secondary: Usage without vision (WV), Usage with limited vision (LV)

9.3.3.8 Accessible authentication (minimum)

Where ICT is, or includes, a web page, the web page shall satisfy WCAG 2.2 Success Criterion 3.3.8 Accessible Authentication (Minimum).

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage without perception of colour (WPC), Usage without hearing (WH), Usage with limited hearing (LH), Usage without vocal capability (WVC), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Minimize photosensitive seizure triggers (PST), Usage with limited cognition (LC), Privacy (PR)

9.4 Robust

9.4.1 Compatible

9.4.1.1 Void

9.4.1.2 Name, role, value

Where ICT is, or includes, a web page, the web page shall satisfy WCAG 2.2 Success Criterion 4.1.2 Name, Role, Value.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Usage with limited cognition (LC)

Secondary: Usage without perception of colour (WPC), Usage without hearing (WH), Usage with limited hearing (LH)

9.4.1.3 Status messages

Where ICT is, or includes, a web page, the web page shall satisfy WCAG 2.2 Success Criterion 4.1.3 Status Messages.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage without vocal capability (WVC), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Usage with limited cognition (LC)

9.5 WCAG 2.2 AAA Success Criteria (informative)

In addition to the Level AA success criteria, included in clauses 9.1 to 9.4, the Web Content Accessibility Guidelines include success criteria for Level AAA. These are listed in Table 9.1. Web authors and procurement accessibility specialists are encouraged to consider the WCAG 2.2 Level AAA success criteria that, when it is possible to apply them, may provide access beyond that required in the present document.

This is shown in Table 9.1: WCAG 2.2 Level AAA Success Criteria

9.6 WCAG conformance requirements

Where ICT is, or includes, a web page, the web page shall satisfy all the following five WCAG 2.2 conformance requirements at Level AA [4]:

1. Conformance level
2. Full pages
3. Complete processes
4. Only Accessibility-Supported Ways of Using Technologies
5. Non-interference

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage without perception of colour (WPC), Usage without hearing (WH), Usage with limited hearing (LH), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Minimize photosensitive seizure triggers (PST), Usage with limited cognition (LC), Privacy (PR)

Secondary: Usage without vocal capability (WVC)

9.7 User preferences for web pages

Where ICT is, or includes, a web page, the web page shall not block the user agent's mode(s) of operation that present the web page according to user preference settings, or explicitly override user preference settings for documented platform accessibility features in these modes of operation, unless this is essential to the information or function of the web page.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage without perception of colour (WPC), Usage without hearing (WH), Usage with limited hearing (LH), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Minimize photosensitive seizure triggers (PST), Usage with limited cognition (LC), Privacy (PR)

Secondary: Usage without vocal capability (WVC)

10 Non-web documents

10.0 General (informative)

Requirements in clause 10 apply to:

• documents that are not web pages;
• documents that are not embedded in web pages; and
• documents that are provided with web pages but are neither embedded nor rendered together with the web page from which they are provided (i.e. the present clause applies to downloadable 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.

EXAMPLE: For example, a non-web document that does not contain pre-recorded audio content in synchronized media will automatically satisfy WCAG success criterion 1.2.2 (captions - pre recorded) and, in consequence, will also meet clause 10.1.2.2.

10.1 Perceivable

10.1.1 Text alternatives

10.1.1.1 Non-text content

Where ICT is, or includes, a non-web document, the non-web document shall satisfy WCAG 2.2 Success Criterion 1.1.1 Non-text content.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage without hearing (WH), Usage with limited hearing (LH)

Secondary: Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Usage with limited cognition (LC)

10.1.2 Time-based media

10.1.2.1 Audio-only and video-only (pre-recorded)

Where ICT is, or includes, a non-web document, the non-web document shall satisfy WCAG 2.2 Success Criterion 1.2.1 Audio-only and Video-only (Prerecorded).

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage without hearing (WH), Usage with limited hearing (LH)

Secondary: Usage with limited cognition (LC)

10.1.2.2 Subtitles (pre-recorded)

Where ICT is, or includes, a non-web document, the non-web document shall satisfy the WCAG 2.2 Success Criterion 1.2.2 Captions (Prerecorded).

Relationship between requirements and functional performance criteria:

Primary: Usage without hearing (WH), Usage with limited hearing (LH)

Secondary: Usage with limited cognition (LC)

10.1.2.3 Audio description or media alternative (pre-recorded)

Where ICT is, or includes, a non-web document, the non-web document shall satisfy the WCAG 2.2 Success Criterion 1.2.3 Audio Description or Media Alternative (Prerecorded).

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV)

Secondary: Usage with limited vision (LV), Usage with limited cognition (LC)

10.1.2.4 Subtitles (live)

Where ICT is, or includes, a non-web document, the non-web document shall satisfy the WCAG 2.2 Success Criterion 1.2.4 Captions (Live).

Relationship between requirements and functional performance criteria:

Primary: Usage without hearing (WH), Usage with limited hearing (LH), Usage with limited cognition (LC)

10.1.2.5 Audio description (pre-recorded)

Where ICT is, or includes, a non-web document, the non-web document shall satisfy the WCAG 2.2 Success Criterion 1.2.5 Audio Description (Prerecorded).

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV)

Secondary: Usage with limited vision (LV), Usage with limited cognition (LC)

10.1.3 Adaptable

10.1.3.1 Info and relationships

Where ICT is, or includes, a non-web document, the non-web document shall satisfy the WCAG 2.2 Success Criterion 1.3.1 Info and Relationships.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV)

Secondary: Usage with limited vision (LV), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Usage with limited cognition (LC)

10.1.3.2 Meaningful sequence

Where ICT is, or includes, a non-web document, the non-web document shall satisfy the WCAG 2.2 Success Criterion 1.3.2 Meaningful Sequence.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV)

Secondary: Usage with limited vision (LV), Usage with limited cognition (LC)

10.1.3.3 Sensory characteristics

Where ICT is, or includes, a non-web document, the non-web document shall satisfy the WCAG 2.2 Success Criterion 1.3.3 Sensory Characteristics.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage without perception of colour (WPC), Usage without hearing (WH), Usage with limited hearing (LH)

Secondary: Usage with limited cognition (LC)

10.1.3.4 Orientation

Where ICT is, or includes, a non-web document, and the non-web document is displayed on hardware that is designed to be reoriented in typical use, the non-web document shall satisfy the WCAG 2.2 Success Criterion 1.3.4 Orientation.

EXAMPLE: A non-web document that is only used on hardware that supports a single display orientation, or is only displayed on hardware that is physically fixed in one orientation (e.g. a digital building directory) is excluded by the precondition and therefore does not need to provide support for orientation changes.

Relationship between requirements and functional performance criteria:

Primary: Usage with limited vision (LV), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR)

Secondary: Usage with limited cognition (LC)

10.1.3.5 Identify input purpose

Where ICT is, or includes, a non-web document, the non-web document shall satisfy the WCAG 2.2 Success Criterion 1.3.5 Identify Input Purpose.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV) Usage with limited vision (LV), Usage with limited cognition (LC)

Secondary: Usage with limited manipulation or strength (LMS), Usage with limited reach (LR)

10.1.4 Distinguishable

10.1.4.1 Use of colour

Where ICT is, or includes, a non-web document, the non-web document shall satisfy the WCAG 2.2 Success Criterion 1.4.1 Use of Color.

Relationship between requirements and functional performance criteria:

Primary: Usage with limited vision (LV), Usage without perception of colour (WPC)

Secondary: Usage with limited cognition (LC)

10.1.4.2 Audio control

Where ICT is, or includes, a non-web document, the non-web document shall satisfy the success criterion in Table 10.1.

Table 10.1: Non-web document success criterion: Audio control

If any audio in the non-web 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.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited hearing (LH)

Secondary: Usage with limited vision (LV)

10.1.4.3 Contrast (minimum)

Where ICT is, or includes, a non-web document, the non-web document shall satisfy the WCAG 2.2 Success Criterion 1.4.3 Contrast (Minimum).

Relationship between requirements and functional performance criteria:

Primary: Usage with limited vision (LV), Usage with limited cognition (LC)

10.1.4.4 Resize text

Where ICT is, or includes, a non-web document, the non-web document shall satisfy the WCAG 2.2 Success Criterion 1.4.4 Resize text.

Relationship between requirements and functional performance criteria:

Primary: Usage with limited vision (LV), Usage with limited cognition (LC)

10.1.4.5 Images of text

Where ICT is, or includes, a non-web document, the non-web document shall satisfy the WCAG 2.2 Success Criterion 1.4.5 Images of Text.

Relationship between requirements and functional performance criteria:

Primary: Usage with limited vision (LV), Usage without perception of colour (WPC), Usage with limited cognition (LC)

10.1.4.6 Void

10.1.4.7 Void

10.1.4.8 Void

10.1.4.9 Void

10.1.4.10 Reflow

Where ICT is, or includes, a non-web document, and where underlying user agent or platform software can present content at a width equivalent to 320 CSS pixels or more for vertical scrolling content and a height equivalent to 256 CSS pixels or more for horizontal scrolling content, the non-web document shall satisfy the success criterion in Table 10.2.

Table 10.2: Non-web document success criterion: Reflow

Content can be presented without loss of information or functionality, and without requiring scrolling in two dimensions for:

• Vertical scrolling content at a width equivalent to 320 CSS pixels.
• Horizontal scrolling content at a height equivalent to 256 CSS pixels.

Except for parts of the content which require two-dimensional layout for usage or meaning.

Relationship between requirements and functional performance criteria:

Primary: Usage with limited vision (LV), Usage with limited cognition (LC)

10.1.4.11 Non-text contrast

Where ICT is, or includes, a non-web document, the non-web document shall satisfy the success criterion in Table 10.3.

Table 10.3: Non-web document success criterion: Non-text contrast

The visual presentation of the following have a contrast ratio of at least 3:1 against adjacent colour(s):

• User Interface Components: Visual information required to identify user interface components and states, except for inactive components or where the appearance of the component is determined by the user agent or other platform software and not modified by the author;
• Graphical Objects: Parts of graphics required to understand the content, except when a particular presentation of graphics is essential to the information being conveyed.

Relationship between requirements and functional performance criteria:

Primary: Usage with limited vision (LV), Usage with limited cognition (LC)

10.1.4.12 Text spacing

Where ICT is, or includes, a non-web document, that is implemented using markup languages that allow users to modify text spacing properties, the non-web document shall satisfy WCAG 2.2 Success Criterion 1.4.12 Text spacing.

Relationship between requirements and functional performance criteria:

Primary: Usage with limited vision (LV), Usage with limited cognition (LC)

10.1.4.13 Content on hover or focus

Where ICT is, or includes, a non-web document, the non-web document shall satisfy the success criterion in Table 10.4.

Table 10.4: Non-web document success criterion: Content on hover or focus

Where receiving and then removing pointer hover or keyboard focus triggers additional content to become visible and then hidden, the following are true:

• Dismissible: A mechanism is available to dismiss the additional content without moving pointer hover or keyboard focus, unless the additional content communicates an input error or does not obscure or replace other content;
• Hoverable: If pointer hover can trigger the additional content, then the pointer can be moved over the additional content without the additional content disappearing;
• Persistent: The additional content remains visible until the hover or focus trigger is removed, the user dismisses it, or its information is no longer valid.

Exception: The visual presentation of the additional content is controlled by the user agent or other platform software and is not modified by the author.

Relationship between requirements and functional performance criteria:

Primary: Usage with limited vision (LV), Usage with limited manipulation or strength (LMS), Usage with limited cognition (LC)

10.2 Operable

10.2.1 Keyboard accessible

10.2.1.1 Keyboard

Where ICT is, or includes, a non-web document, and the document provides a keyboard or accepts input from a keyboard or keyboard interface, the non-web document shall satisfy the WCAG 2.2 Success Criterion 2.1.1 Keyboard.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR)

10.2.1.2 No keyboard trap

Where ICT is, or includes, a non-web document, and the document provides a keyboard or accepts input from a keyboard or keyboard interface, the non-web document shall satisfy the success criterion in Table 10.5.

Table 10.5: Non-web document success criterion: No keyboard trap

If keyboard focus can be moved to a component of the non-web 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.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR)

10.2.1.3 Void

10.2.1.4 Character key shortcuts

Where ICT is, or includes, a non-web document, and the document provides a keyboard or accepts input from a keyboard or keyboard interface, the non-web document shall satisfy WCAG 2.2 Success Criterion 2.1.4 Character Key Shortcuts.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR)

Secondary: Usage with limited cognition (LC)

10.2.2 Enough time

10.2.2.1 Timing adjustable

Where ICT is, or includes, a non-web document, the non-web document shall satisfy the success criterion in Table 10.6.

Table 10.6: Non-web document success criterion: Timing adjustable

For each time limit that is set by the non-web document, at least one of the following is true:

• Turn off: The user is allowed to turn off the time limit before encountering it; or
• Adjust: The user is allowed to adjust the time limit before encountering it over a wide range that is at least ten times the length of the default setting; or
• Extend: The user is warned before time expires and given at least 20 seconds to extend the time limit with a simple action (for example, "press the space bar"), and the user is allowed to extend the time limit at least ten times; or
• Real-time Exception: The time limit is a required part of a real-time event (for example, an auction), and no alternative to the time limit is possible; or
• Essential Exception: The time limit is essential and extending it would invalidate the activity; or
• 20 Hour Exception: The time limit is longer than 20 hours.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage without hearing (WH), Usage with limited hearing (LH), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Usage with limited cognition (LC)

10.2.2.2 Pause, stop, hide

Where ICT is, or includes, a non-web document, the non-web document shall satisfy the success criterion in Table 10.7.

Table 10.7: Non-web document success criterion: 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.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage without hearing (WH), Usage with limited hearing (LH), Usage with limited cognition (LC)

Secondary: Usage with limited manipulation or strength (LMS), Usage with limited reach (LR)

10.2.3 Seizures and physical reactions

10.2.3.1 Three flashes or below threshold

Where ICT is, or includes, a non-web document, the non-web document shall satisfy the success criterion in Table 10.8.

Table 10.8: Non-web document success criterion: Three flashes or below threshold

Non-web 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.

Relationship between requirements and functional performance criteria:

Primary: Minimize photosensitive seizure triggers (PST)

10.2.4 Navigable

10.2.4.1 Void

10.2.4.2 Non-web document titled

Where ICT is, or includes, a non-web document implemented in a format that supports a programmatically determinable "Title" attribute that is editable using common authoring tools for that document format, the non-web document shall have a title that describes the name, topic, or purpose.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Usage with limited cognition (LC)

10.2.4.3 Focus order

Where ICT is, or includes, a non-web document, and the document provides a keyboard or accepts input from a keyboard or keyboard interface, the non-web document shall satisfy the success criterion in Table 10.9.

Table 10.9: Non-web document success criterion: Focus order

If a non-web 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.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Usage with limited cognition (LC)

10.2.4.4 Link purpose (in context)

Where ICT is, or includes, a non-web document, the non-web document shall satisfy the WCAG 2.2 Success Criterion 2.4.4 Link Purpose (In Context).

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Usage with limited cognition (LC)

10.2.4.5 Multiple ways (Void)

10.2.4.6 Headings and labels

Where ICT is, or includes, a non-web document, the non-web document shall satisfy the WCAG 2.2 Success Criterion 2.4.6 Headings and Labels.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage without vocal capability (WVC), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Usage with limited cognition (LC)

Secondary: Usage without hearing (WH)

10.2.4.7 Focus visible

Where ICT is, or includes, a non-web document and the document provides a keyboard or accepts input from a keyboard or keyboard interface, the non-web document shall satisfy the WCAG 2.2 Success Criterion 2.4.7 Focus Visible.

Relationship between requirements and functional performance criteria:

Primary: Usage with limited vision (LV), Usage without vocal capability (WVC), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Usage with limited cognition (LC)

10.2.4.8 Void

10.2.4.9 Void

10.2.4.10 Void

10.2.4.11 Focus not obscured (minimum)

Where ICT is, or includes, a non-web document, and the document provides a keyboard or accepts input from a keyboard or keyboard interface, the non-web document shall satisfy WCAG 2.2 Success Criterion 2.4.11 Focus Not Obscured (Minimum).

Relationship between requirements and functional performance criteria:

Primary: Usage with limited vision (LV), Usage without vocal capability (WVC), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Usage with limited cognition (LC)

10.2.5 Input modalities

10.2.5.1 Pointer gestures

Where ICT is, or includes, a non-web document, the non-web document shall satisfy the success criterion in Table 10.10.

Table 10.10: Non-web document success criterion: Pointer gestures

All functionality that uses multipoint or path-based gestures for operation can be operated with a single pointer without a path-based gesture, unless a multipoint or path-based gesture is essential.

Relationship between requirements and functional performance criteria:

Primary: Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Usage with limited cognition (LC)

10.2.5.2 Pointer cancellation

Where ICT is, or includes, a non-web document, the non-web document shall satisfy the success criterion in Table 10.11.

Table 10.11: Non-web document success criterion: Pointer cancellation

For functionality that can be operated using a single pointer, at least one of the following is true:

• No Down-Event: The down-event of the pointer is not used to execute any part of the function;
• Abort or Undo: Completion of the function is on the up-event, and a mechanism is available to abort the function before completion or to undo the function after completion;
• Up Reversal: The up-event reverses any outcome of the preceding down-event;
• Essential: Completing the function on the down-event is essential.

Relationship between requirements and functional performance criteria:

Primary: Usage with limited vision (LV), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Usage with limited cognition (LC)

10.2.5.3 Label in name

Where ICT is, or includes, a non-web document, the non-web document shall satisfy WCAG 2.2 Success Criterion 2.5.3 Label in Name.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR)

Secondary: Usage with limited cognition (LC)

10.2.5.4 Motion actuation

Where ICT is, or includes, a non-web document, the non-web document shall satisfy WCAG 2.2 Success Criterion 2.5.4 Motion Actuation.

Relationship between requirements and functional performance criteria:

Primary: Usage with limited manipulation or strength (LMS), Usage with limited reach (LR)

Secondary: Usage without vision (WV), Usage with limited vision (LV), Usage with limited cognition (LC)

10.2.5.5 Void

10.2.5.6 Void

10.2.5.7 Dragging movements

Where ICT is, or includes, a non-web document, the non-web document shall satisfy the success criterion in Table 10.12.

Table 10.12: Non-web document success criterion: Dragging movements

All functionality that uses a dragging movement for operation can be achieved by a single pointer without dragging, unless dragging is essential or the functionality is determined by the user agent or other platform software and not modified by the author.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR)

Secondary: Usage with limited cognition (LC)

10.2.5.8 Target size (minimum)

Where ICT is, or includes, a non-web document, the non-web document shall satisfy the success criterion in Table 10.13.

Table 10.13: Non-web document success criterion: Target size (minimum)

The size of the target for pointer inputs is at least 24 by 24 CSS pixels, except when:

• Spacing: Undersized targets (those less than 24 by 24 CSS pixels) are positioned so that if a 24 CSS pixel diameter circle is centred on the bounding box of each, the circles do not intersect another target or the circle for another undersized target;
• Equivalent: The function can be achieved through a different control in the same non-web document that meets this criterion;
• Inline: The target is in a sentence or its size is otherwise constrained by the line-height of non-target text;
• User agent or other platform software control: The size of the target is determined by the user agent or other platform software and is not modified by the author;
• Essential: A particular presentation of the target is essential or is legally required for the information being conveyed.

Relationship between requirements and functional performance criteria:

Primary: Usage with limited vision (LV), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR)

Secondary: Usage with limited cognition (LC)

10.3 Understandable

10.3.1 Readable

10.3.1.1 Language of non-web document

Where ICT is, or includes, a non-web document, the non-web document shall satisfy the success criterion in Table 10.14.

Table 10.14: Non-web document success criterion: Language of non-web document

The default human language of each non-web document can be programmatically determined.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited cognition (LC)

Secondary: Usage with limited vision (LV), Usage without hearing (WH), Usage with limited hearing (LH), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR)

10.3.1.2 Language of parts

Where ICT is, or includes, a non-web document, the non-web document shall satisfy the success criterion in Table 10.15.

Table 10.15: Non-web document success criterion: Language of parts

The human language of each passage or phrase in the non-web document 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.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited cognition (LC)

Secondary: Usage with limited vision (LV), Usage without hearing (WH), Usage with limited hearing (LH), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR)

10.3.2 Predictable

10.3.2.1 On focus

Where ICT is, or includes, a non-web document, the non-web document shall satisfy the WCAG 2.2 Success Criterion 3.2.1 On Focus.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Usage with limited cognition (LC)

10.3.2.2 On input

Where ICT is, or includes, a non-web document, the non-web document shall satisfy the WCAG 2.2 Success Criterion 3.2.2 On Input.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Usage with limited cognition (LC)

10.3.2.3 Consistent navigation

Where ICT is, or includes, a non-web document within a set of non-web documents, the non-web document shall satisfy the success criterion in Table 10.16.

Table 10.16: Non-web document success criterion: Consistent navigation

Navigational mechanisms that are repeated in multiple non-web documents within a set of non-web documents occur in the same relative order each time they are repeated, unless a change is initiated by the user.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), ), Usage with limited cognition (LC)

Secondary: Usage with limited manipulation or strength (LMS), Usage with limited reach (LR)

10.3.2.4 Consistent identification

Where ICT is, or includes, a non-web document within a set of non-web documents, the non-web document shall satisfy the success criterion in Table 10.17.

Table 10.17: Non-web document success criterion: Consistent identification

Components that have the same functionality within a set of non-web documents are identified consistently.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage with limited cognition (LC)

Secondary: Usage with limited manipulation or strength (LMS), Usage with limited reach (LR)

10.3.2.5 Void

10.3.2.6 Consistent help

Where ICT is, or includes, a non-web document, the non-web document shall satisfy the success criterion in Table 10.18.

Table 10.18: Non-web document success criterion: Consistent Help

If a non-web document contains any of the following help mechanisms, and those mechanisms are repeated in multiple non-web documents within a set of non-web documents, they occur in the same order relative to other content, unless a change is initiated by the user:

• Human contact details;
• Human contact mechanism;
• Self-help option;
• A fully automated contact mechanism.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage with limited cognition (LC)

Secondary: Usage with limited manipulation or strength (LMS), Usage with limited reach (LR)

10.3.3 Input assistance

10.3.3.1 Error identification

Where ICT is, or includes, a non-web document, the non-web document shall satisfy the WCAG 2.2 Success Criterion 3.3.1 Error Identification.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage without perception of colour (WPC), Usage with limited cognition (LC)

Secondary: Usage without hearing (WH), Usage with limited hearing (LH), Usage without vocal capability (WVC), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Minimize photosensitive seizure triggers (PST)

10.3.3.2 Labels or instructions

Where ICT is, or includes, a non-web document, the non-web document shall satisfy the WCAG 2.2 Success Criterion 3.3.2 Labels or Instructions.

Relationship between requirements and functional performance criteria:

Primary: Usage with limited cognition (LC)

Secondary: Usage without vision (WV), Usage with limited vision (LV), Usage without perception of colour (WPC), Usage without hearing (WH), Usage with limited hearing (LH), Usage without vocal capability (WVC), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Minimize photosensitive seizure triggers (PST)

10.3.3.3 Error suggestion

Where ICT is, or includes, a non-web document, the non-web document shall satisfy the WCAG 2.2 Success Criterion 3.3.3 Error Suggestion.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage without perception of colour (WPC), Usage with limited cognition (LC)

Secondary: Usage without hearing (WH), Usage with limited hearing (LH), Usage without vocal capability (WVC), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Minimize photosensitive seizure triggers (PST)

10.3.3.4 Error prevention (legal, financial, data)

Where ICT is, or includes, a non-web document, the non-web document shall satisfy the success criterion in Table 10.19.

Table 10.19: Non-web document success criterion: Error prevention (legal, financial, data)

For non-web 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:

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.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage without perception of colour (WPC), Usage with limited cognition (LC), Privacy (PR)

Secondary: Usage without hearing (WH), Usage with limited hearing (LH), Usage without vocal capability (WVC), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Minimize photosensitive seizure triggers (PST)

10.3.3.5 Void

10.3.3.6 Void

10.3.3.7 Redundant entry

Where ICT is, or includes, a non-web document, the non-web document shall satisfy WCAG 2.2 Success Criterion 3.3.7 Redundant Entry.

Relationship between requirements and functional performance criteria:

Primary: Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Usage with limited cognition (LC)

Secondary: Usage without vision (WV), Usage with limited vision (LV)

10.3.3.8 Accessible authentication (minimum)

Where ICT is, or includes, a non-web document, the non-web document shall satisfy the success criterion in Table 10.20.

Table 10.20: Non-web document success criterion: Accessible authentication (minimum)

A cognitive function test (such as remembering a password or solving a puzzle) is not required for any step in an authentication process unless that step provides at least one of the following:

• Alternative: Another authentication method that does not rely on a cognitive function test.
• Mechanism: A mechanism is available to assist the user in completing the cognitive function test.
• Object Recognition: The cognitive function test is to recognize objects.
• Personal Content: The cognitive function test is to identify non-text content the user provided to a non web document.

1. support for password entry by password managers to reduce memory need, and
2. copy and paste to reduce the cognitive burden of re-typing.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage without perception of colour (WPC), Usage without hearing (WH), Usage with limited hearing (LH), Usage without vocal capability (WVC), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Minimize photosensitive seizure triggers (PST), Usage with limited cognition (LC), Privacy (PR)

10.4 Robust

10.4.1 Compatible

10.4.1.1 Void

10.4.1.2 Name, role, value

Where ICT is, or includes, a non-web document, the non-web document shall satisfy the success criterion in Table 10.21.

Table 10.21: Non-web document success criterion: 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 assistive technologies and accessibility features of underlying software.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Usage with limited cognition (LC)

Secondary: Usage without perception of colour (WPC), Usage without hearing (WH), Usage with limited hearing (LH)

10.4.1.3 Status messages

Where ICT is, or includes, a non-web document, the non-web document shall satisfy WCAG 2.2 Success Criterion 4.1.3 Status Messages.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage without vocal capability (WVC), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Usage with limited cognition (LC)

10.5 Subtitle positioning (recommendation)

Where ICT is, or includes, a non-web document, and contains synchronized media with subtitles, the subtitles should not obscure relevant information in the synchronized media.

Relationship between requirements and functional performance criteria:

Primary: Usage without hearing (WH), Usage with limited hearing (LH)

Secondary: Usage with limited cognition (LC)

10.6 Audio description timing (recommendation)

Where ICT is, or includes, a non-web document, and the non-web document contains synchronized media with audio description, the audio description should not interfere with relevant audio information in the synchronized media.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited cognition (LC)

Secondary: Usage with limited vision (LV)

10.7 User preferences for non-web documents

Where ICT is, or includes, a non-web document, the non-web document shall not block the user agents mode(s) of operation that present the web page according to user preference settings, or explicitly override user preference settings for documented platform accessibility features in these modes of operation, unless this is essential to the information or function of the non-web document.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage without perception of colour (WPC), Usage without hearing (WH), Usage with limited hearing (LH), Usage without vocal capability (WVC), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Minimize photosensitive seizure triggers (PST), Usage with limited cognition (LC), Privacy (PR)

11 Non-web software

11.0 General (informative)

This clause includes requirements for the following types of non-web software as scoped by the preconditions for each requirement:

• platform software;
• non-web software that provides a user interface including content that is in the software;
• non-web software that operates as assistive technology;
• mobile applications.

EXAMPLE: For example, a non-web software that does not contain pre-recorded audio content in synchronized media will automatically satisfy WCAG success criterion 1.2.2 (captions - pre-recorded) and, in consequence, will also meet clause 11.1.2.2.

Requirements in clauses 11.1 to 11.5 apply to non-web 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.

Some requirements in clauses 11.1 to 11.5 have a pre-condition that indicates that they do not apply to closed functionality, so these requirements only apply to the open functionality of the ICT.

Requirements that do not have a closed functionality pre-condition apply to both the open and closed functionality of the ICT. The requirements under clause 5.1 apply to the closed functionality of the ICT.

For non-web software that has functionality that is closed and other functionality that is not closed, the requirements in clauses 11.1 to 11.5 will still need to be met for the functionality that is not closed.

The success criteria set out in clauses 11.1 to 11.5 are intended to harmonize with the W3C^® Working Group Note [i.25] produced by the W3C's WCAG2ICT Task Force.

11.1 Perceivable

11.1.1 Text alternatives

11.1.1.1 Non-text content

Where ICT is, or includes, non-web software that provides a user interface, and the non-web software includes functionality that is not closed to programmatic access of information by assistive technologies, the functionality that is not closed shall satisfy WCAG 2.2 Success Criterion 1.1.1 Non-text content.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage without hearing (WH), Usage with limited hearing (LH)

Secondary: Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Usage with limited cognition (LC)

11.1.2 Time-based media

11.1.2.1 Audio-only and video-only (pre-recorded)

Where ICT is, or includes, non-web software that provides a user interface, and the non-web software includes functionality that is not closed to programmatic access of information by assistive technologies, the functionality that is not closed shall satisfy the WCAG 2.2 Success Criterion 1.2.1 Audio-only and Video-only (Prerecorded).

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage without hearing (WH), Usage with limited hearing (LH)

Secondary: Usage with limited cognition (LC)

11.1.2.2 Subtitles (pre-recorded)

Where ICT is, or includes, non-web software that provides a user interface, the non-web software shall satisfy the WCAG 2.2 Success Criterion 1.2.2 Captions (Prerecorded).

Relationship between requirements and functional performance criteria:

Primary: Usage without hearing (WH), Usage with limited hearing (LH)

Secondary: Usage with limited cognition (LC)

11.1.2.3 Audio description or media alternative (pre-recorded)

Where ICT is, or includes, non-web software that provides a user interface, and the non-web software includes functionality that is not closed to programmatic access of information by assistive technologies, the functionality that is not closed shall satisfy the WCAG 2.2 Success Criterion 1.2.3 Audio Description or Media Alternative (Prerecorded).

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV)

Secondary: Usage with limited vision (LV), Usage with limited cognition (LC)

11.1.2.4 Subtitles (live)

Where ICT is, or includes, non-web software that provides a user interface, the non-web software shall satisfy the WCAG 2.2 Success Criterion 1.2.4 Captions (Live).

Relationship between requirements and functional performance criteria:

Primary: Usage without hearing (WH), Usage with limited hearing (LH), Usage with limited cognition (LC)

11.1.2.5 Audio description (pre-recorded)

Where ICT is, or includes, non-web software that provides a user interface, the non-web software shall satisfy the WCAG 2.2 Success Criterion 1.2.5 Audio Description (Prerecorded).

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV)

Secondary: Usage with limited vision (LV), Usage with limited cognition (LC)

11.1.3 Adaptable

11.1.3.1 Info and relationships

Where ICT is, or includes, non-web software that provides a user interface, and the non-web software includes functionality that is not closed to programmatic access of information by assistive technologies, the functionality that is not closed shall satisfy the WCAG 2.2 Success Criterion 1.3.1 Info and Relationships.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV)

Secondary: Usage with limited vision (LV), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Usage with limited cognition (LC)

11.1.3.2 Meaningful sequence

Where ICT is, or includes, non-web software that provides a user interface, and the non-web software includes functionality that is not closed to programmatic access of information by assistive technologies, the functionality that is not closed shall satisfy the WCAG 2.2 Success Criterion 1.3.2 Meaningful Sequence.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV)

Secondary: Usage with limited vision (LV), Usage with limited cognition (LC)

11.1.3.3 Sensory characteristics

Where ICT is, or includes, non-web software that provides a user interface, the non-web software shall satisfy the WCAG 2.2 Success Criterion 1.3.3 Sensory Characteristics.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage without perception of colour (WPC), Usage without hearing (WH), Usage with limited hearing (LH)

Secondary: Usage with limited cognition (LC)

11.1.3.4 Orientation

Where ICT is, or includes, non-web software that provides a user interface, and the non-web software is displayed on hardware that is designed to be reoriented in typical use, the non-web software shall satisfy the WCAG 2.2 Success Criterion 1.3.4 Orientation.

EXAMPLES: Software that is excluded by the precondition:

• The software on a typical handheld calculator (one that typically would only be used in one orientation).
• Software that runs on wristwatches (where the software typically only runs in one orientation) (sleep mode being non-typical).
• Building directory software written to ONLY be used on tablet devices bolted to the wall, all in the same orientation.

Relationship between requirements and functional performance criteria:

Primary: Usage with limited vision (LV), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR)

Secondary: Usage with limited cognition (LC)

11.1.3.5 Identify input purpose

Where ICT is, or includes, non-web software that provides a user interface, and the non-web software includes functionality that is not closed to programmatic access of information by assistive technologies, and where the technology used supports attributes to identify the meaning of form input data, the functionality that is not closed shall satisfy the WCAG 2.2 Success Criterion 1.3.5 Identify Input Purpose.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage with limited cognition (LC)

Secondary: Usage with limited manipulation or strength (LMS), Usage with limited reach (LR)

11.1.4 Distinguishable

11.1.4.1 Use of colour

Where ICT is, or includes, non-web software that provides a user interface, the non-web software shall satisfy the WCAG 2.2 Success Criterion 1.4.1 Use of Color.

Relationship between requirements and functional performance criteria:

Primary: Usage with limited vision (LV), Usage without perception of colour (WPC)

Secondary: Usage with limited cognition (LC)

11.1.4.2 Audio control

Where ICT is, or includes, non-web software that provides a user interface, the non-web software shall satisfy the success criterion in Table 11.1.

Table 11.1: Non-web software success criterion: Audio control

1.4.2 Audio Control: If any audio in the non-web 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.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited hearing (LH), Usage with limited cognition (LC)

Secondary: Usage with limited vision (LV)

11.1.4.3 Contrast (minimum)

Where ICT is, or includes, non-web software that provides a user interface, the non-web software shall satisfy the WCAG 2.2 Success Criterion 1.4.3 Contrast (Minimum).

Relationship between requirements and functional performance criteria:

Primary: Usage with limited vision (LV), Usage with limited cognition (LC)

11.1.4.4 Resize text

Where ICT is, or includes, non-web software that provides a user interface, and is not closed to enlargement, the non-web software shall satisfy the success criterion in Table 11.2.

Table 11.2: Non-web software success criterion: Resize Text

1.4.4 Resize Text: Except for captions and images of text, text can be resized without loss of content or functionality and without assistive technology either up to 200 percent or, if the platform provides text resizing capabilities but it does not reach 200 percent for all text, up to the text sizing capabilities of the platform.

Relationship between requirements and functional performance criteria:

Primary: Usage with limited vision (LV), Usage with limited cognition (LC)

11.1.4.5 Images of text

Where ICT is, or includes, non-web software that provides a user interface, and the non-web software includes functionality that is not closed to programmatic access of information by assistive technologies, the functionality that is not closed shall satisfy the WCAG 2.2 Success Criterion 1.4.5 Images of Text.

Relationship between requirements and functional performance criteria:

Primary: Usage with limited vision (LV), Usage without perception of colour (WPC), Usage with limited cognition (LC)

11.1.4.6 Void

11.1.4.7 Void

11.1.4.8 Void

11.1.4.9 Void

11.1.4.10 Reflow

Where ICT is, or includes, non-web software that provides a user interface, the non-web software shall satisfy the success criterion in Table 11.3.

Table 11.3: Non-web software success criterion: Reflow

Content can be presented without loss of information or functionality, and without requiring scrolling in two dimensions for:

• Vertical scrolling content at a width equivalent to 320 CSS pixels;
• Horizontal scrolling content at a height equivalent to 256 CSS pixels.

Except for parts of the content which require two-dimensional layout for usage or meaning.

• When the non-web software has a complex user interface with toolbars that need to be visible while manipulating content, as explained in the Intent from Understanding 1.4.10 Reflow.

Relationship between requirements and functional performance criteria:

Primary: Usage with limited vision (LV), Usage with limited cognition (LC)

11.1.4.11 Non-text contrast

Where ICT is, or includes, non-web software that provides a user interface, the non-web software shall satisfy WCAG 2.2 Success Criterion 1.4.11 Non-text Contrast.

Relationship between requirements and functional performance criteria:

Primary: Usage with limited vision (LV), Usage with limited cognition (LC)

11.1.4.12 Text spacing

Where ICT is, or includes, non-web software that provides a user interface, that is implemented using markup languages that allow users to modify text spacing properties, the non-web software shall satisfy WCAG 2.2 Success Criterion 1.4.12 Text spacing.

Relationship between requirements and functional performance criteria:

Primary: Usage with limited vision (LV), Usage with limited cognition (LC)

11.1.4.13 Content on hover or focus

Where ICT is, or includes, non-web software that provides a user interface, and any visual presentation of the additional content caused by a hover or focus is not controlled by the user agent or platform software, or that visual presentation is modified by the non-web software, the non-web software shall satisfy the success criterion in Table 11.4.

Table 11.4: Non-web software success criterion: Content on Hover or Focus

Where receiving and then removing pointer hover or keyboard focus triggers additional content to become visible and then hidden, the following are true:

• Dismissible: A mechanism is available to dismiss the additional content without moving pointer hover or keyboard focus, unless the additional content communicates an input error or does not obscure or replace other content;
• Hoverable: If pointer hover can trigger the additional content, then the pointer can be moved over the additional content without the additional content disappearing;
• Persistent: The additional content remains visible until the hover or focus trigger is removed, the user dismisses it, or its information is no longer valid.

Exception: The visual presentation of the additional content is controlled by the user agent or other platform software and is not modified by the author.

Relationship between requirements and functional performance criteria:

Primary: Usage with limited vision (LV), Usage with limited manipulation or strength (LMS), Usage with limited cognition (LC)

11.2 Operable

11.2.1 Keyboard accessible

11.2.1.1 Keyboard

Where ICT is, or includes, non-web software that can be run on a software platform that provides a device-independent keyboard interface service, the non-web software shall satisfy the WCAG 2.2 Success Criterion 2.1.1 Keyboard in accordance with the Intent from Understanding Success Criterion 2.1.1.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR)

11.2.1.2 No keyboard trap

Where ICT is, or includes, non-web software that provides a user interface, and that provides a keyboard or accepts input from a keyboard or keyboard interface, the non-web software shall satisfy the success criterion in Table 11.5.

Table 11.5: Non-web software success criterion: No keyboard trap

If keyboard focus can be moved to a component of the non-web 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.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR)

11.2.1.3 Void

11.2.1.4 Character key shortcuts

Where ICT is, or includes, non-web software that provides a user interface, and that provides a keyboard or accepts input from a keyboard or keyboard interface, the non-web software shall satisfy WCAG 2.2 Success Criterion 2.1.4 Character Key Shortcuts.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR)

Secondary: Usage with limited cognition (LC)

11.2.2 Enough time

11.2.2.1 Timing adjustable

Where ICT is, or includes, non-web software that provides a user interface, the non-web software shall satisfy the success criterion in Table 11.6.

Table 11.6: Non-web software success criterion: Timing adjustable

For each time limit that is set by the non-web software, at least one of the following is true:

• Turn off: The user is allowed to turn off the time limit before encountering it; or
• Adjust: The user is allowed to adjust the time limit before encountering it over a wide range that is at least ten times the length of the default setting; or
• Extend: The user is warned before time expires and given at least 20 seconds to extend the time limit with a simple action (for example, "press the space bar"), and the user is allowed to extend the time limit at least ten times; or
• Real-time Exception: The time limit is a required part of a real-time event (for example, an auction), and no alternative to the time limit is possible; or
• Essential Exception: The time limit is essential and extending it would invalidate the activity; or
• 20 Hour Exception: The time limit is longer than 20 hours.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage without hearing (WH), Usage with limited hearing (LH), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Usage with limited cognition (LC)

11.2.2.2 Pause, stop, hide

Where ICT is, or includes, non-web software that provides a user interface, the non-web software shall satisfy the success criterion in Table 11.7.

Table 11.7: Non-web software success criterion: 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.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage without hearing (WH), Usage with limited hearing (LH), Usage with limited cognition (LC)

Secondary: Usage with limited manipulation or strength (LMS), Usage with limited reach (LR)

11.2.3 Seizures and physical reactions

11.2.3.1 Three flashes or below threshold

Where ICT is, or includes, non-web software that provides a user interface, the non-web software shall satisfy the success criterion in Table 11.8.

Table 11.8: Non-web software success criterion: Three flashes or below threshold

Non-web 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.

Relationship between requirements and functional performance criteria:

Primary: Minimize photosensitive seizure triggers (PST)

11.2.4 Navigable

11.2.4.1 Bypass blocks (Void)

Void.

11.2.4.2 Non-web software titled

Where ICT is, or includes, non-web software that provides a user interface, implemented on a platform that supports "Title" attributes for windows or screens, the non-web software shall provide titles that describe the name, topic or purpose of each window or screen.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Usage with limited cognition (LC)

11.2.4.3 Focus order

Where ICT is, or includes, non-web software that provides a user interface, and that provides a keyboard or accepts input from a keyboard or keyboard interface, the non-web software shall satisfy the success criterion in Table 11.9.

Table 11.9: Non-web software success criterion: Focus order

If non-web 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.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Usage with limited cognition (LC)

11.2.4.4 Link purpose (in context)

Where ICT is, or includes, non-web software that provides a user interface, the non-web software shall satisfy WCAG 2.2 Success Criterion 2.4.4 Link Purpose (In Context).

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage without vocal capability (WVC), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Usage with limited cognition (LC)

11.2.4.5 Multiple ways (Void)

11.2.4.6 Headings and labels

Where ICT is, or includes, non-web software that provides a user interface, the non-web software shall satisfy the WCAG 2.2 Success Criterion 2.4.6 Headings and Labels.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage without vocal capability (WVC), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Usage with limited cognition (LC)

Secondary: Usage without hearing (WH)

11.2.4.7 Focus visible

Where ICT is, or includes, non-web software that provides a user interface, and that provides a keyboard or accepts input from a keyboard or keyboard interface, the non-web software shall satisfy the WCAG 2.2 Success Criterion 2.4.7 Focus Visible.

Relationship between requirements and functional performance criteria:

Primary: Usage with limited vision (LV), Usage without vocal capability (WVC), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Usage with limited cognition (LC)

11.2.4.8 Void

11.2.4.9 Void

11.2.4.10 Void

11.2.4.11 Focus not obscured (minimum)

Where ICT is, or includes, non-web software that provides a user interface, and that provides a keyboard or accepts input from a keyboard or keyboard interface, the non-web software shall satisfy the WCAG 2.2 Success Criterion 2.4.11 Focus not obscured (minimum).

Relationship between requirements and functional performance criteria:

Primary: Usage with limited vision (LV), Usage without vocal capability (WVC), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Usage with limited cognition (LC)

11.2.5 Input modalities

11.2.5.1 Pointer gestures

Where ICT is, or includes, non-web software that provides a user interface, and that provides a pointing mechanism or accepts input from pointing devices, the non-web software shall satisfy the success criterion in Table 11.10.

Table 11.10: Non-web software success criterion: Pointer gestures

All functionality that uses multipoint or path-based gestures for operation can be operated with a single pointer without a path-based gesture, unless a multipoint or path-based gesture is essential.

Relationship between requirements and functional performance criteria:

Primary: Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Usage with limited cognition (LC)

11.2.5.2 Pointer cancellation

Where ICT is, or includes, non-web software that provides a user interface, and that provides a pointing mechanism or accepts input from pointing devices, the non-web software shall satisfy the success criterion in Table 11.11.

Table 11.11: Non-web software success criterion: Pointer cancellation

For functionality that can be operated using a single pointer, at least one of the following is true:

• No Down-Event: The down-event of the pointer is not used to execute any part of the function.
• Abort or Undo: Completion of the function is on the up-event, and a mechanism is available to abort the function before completion or to undo the function after completion.
• Up Reversal: The up-event reverses any outcome of the preceding down-event.
• Essential: Completing the function on the down-event is essential.

EXAMPLE: Examples of essential functionality for non-web software are features for meeting environmental energy usage requirements (like waking a device from sleep, power saver mode, and low power state).

Relationship between requirements and functional performance criteria:

Primary: Usage with limited vision (LV), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Usage with limited cognition (LC)

11.2.5.3 Label in name

Where ICT is, or includes, non-web software that provides a user interface, and the non-web software includes functionality that is not closed to programmatic access of information by assistive technologies, the functionality that is not closed shall satisfy WCAG 2.2 Success Criterion 2.5.3 Label in Name.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR)

Secondary: Usage with limited cognition (LC)

11.2.5.4 Motion actuation

Where ICT is, or includes, non-web software that provides a user interface, the non-web software shall satisfy WCAG 2.2 Success Criterion 2.5.4 Motion Actuation.

Relationship between requirements and functional performance criteria:

Primary: Usage with limited manipulation or strength (LMS), Usage with limited reach (LR)

Secondary: Usage without vision (WV), Usage with limited vision (LV), Usage with limited cognition (LC)

11.2.5.5 Void

11.2.5.6 Void

11.2.5.7 Dragging movements

Where ICT is, or includes, non-web software that provides a user interface, the non-web software shall satisfy the success criterion in Table 11.12.

Table 11.12: Non-web software success criterion: Dragging Movements

All functionality that uses a dragging movement for operation can be achieved by a single pointer without dragging, unless dragging is essential or the functionality is determined by the user agent or other platform software and not modified by the author.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR)

Secondary: Usage with limited cognition (LC)

11.2.5.8 Target size (minimum)

Where ICT is, or includes, non-web software that provides a user interface, the non-web software shall satisfy the success criterion in Table 11.13.

Table 11.13: Non-web software success criterion: Target size (minimum)

The size of the target for pointer inputs is at least 24 by 24 CSS pixels, except when:

• Spacing: Undersized targets (those less than 24 by 24 CSS pixels) are positioned so that if a 24 CSS pixel diameter circle is centred on the bounding box of each, the circles do not intersect another target or the circle for another undersized target;
• Equivalent: The function can be achieved through a different control in the same non-web software that meets this criterion;
• Inline: The target is in a sentence or its size is otherwise constrained by the line-height of non-target text;
• User agent or other platform software control: The size of the target is determined by the user agent or other platform software and is not modified by the author;
• Essential: A particular presentation of the target is essential or is legally required for the information being conveyed.

Relationship between requirements and functional performance criteria:

Primary: Usage with limited vision (LV), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR)

Secondary: Usage with limited cognition (LC)

11.3 Understandable

11.3.1 Readable

11.3.1.1 Language of non-web software

Where ICT is, or includes, non-web software that provides a user interface, and the non-web software includes functionality that is not closed to programmatic access of information by assistive technologies, the functionality that is not closed shall satisfy the success criterion in Table 11.14.

Table 11.14: Non-web software success criterion: Language of non-web software

The default human language of non-web software can be programmatically determined.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited cognition (LC)

Secondary: Usage with limited vision (LV), Usage without hearing (WH), Usage with limited hearing (LH), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR)

11.3.1.2 Language of parts (Void)

11.3.2 Predictable

11.3.2.1 On focus

Where ICT is, or includes, non-web software that provides a user interface, the non-web software shall satisfy the WCAG 2.2 Success Criterion 3.2.1 On Focus.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Usage with limited cognition (LC)

11.3.2.2 On input

Where ICT is, or includes, non-web software that provides a user interface, the non-web software shall satisfy the WCAG 2.2 Success Criterion 3.2.2 On Input.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Usage with limited cognition (LC)

11.3.2.3 Consistent navigation (Void)

11.3.2.4 Consistent identification

Where ICT is, or includes, non-web software that provides a user interface, components that have the same functionality within the non-web software program shall be identified consistently, except where not doing so is essential to the function of the non-web software.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage with limited cognition (LC)

Secondary: Usage with limited manipulation or strength (LMS), Usage with limited reach (LR)

11.3.2.5 Void

11.3.2.6 Consistent help (Void)

11.3.3 Input assistance

11.3.3.1 Error identification

Where ICT is, or includes, non-web software that provides a user interface, and the non-web software includes functionality that is not closed to programmatic access of information by assistive technologies, the functionality that is not closed shall satisfy the WCAG 2.2 Success Criterion 3.3.1 Error Identification.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage without perception of colour (WPC), Usage with limited cognition (LC)

Secondary: Usage without hearing (WH), Usage with limited hearing (LH), Usage without vocal capability (WVC), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Minimize photosensitive seizure triggers (PST)

11.3.3.2 Labels or instructions

Where ICT is, or includes, non-web software that provides a user interface, the non-web software shall satisfy the WCAG 2.2 Success Criterion 3.3.2 Labels or Instructions.

Relationship between requirements and functional performance criteria:

Primary: Usage with limited cognition (LC)

Secondary: Usage without vision (WV), Usage with limited vision (LV), Usage without perception of colour (WPC), Usage without hearing (WH), Usage with limited hearing (LH), Usage without vocal capability (WVC), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Minimize photosensitive seizure triggers (PST)

11.3.3.3 Error suggestion

Where ICT is, or includes, non-web software that provides a user interface, the non-web software shall satisfy the WCAG 2.2 Success Criterion 3.3.3 Error Suggestion.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage without perception of colour (WPC), Usage with limited cognition (LC)

Secondary: Usage without hearing (WH), Usage with limited hearing (LH), Usage without vocal capability (WVC), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Minimize photosensitive seizure triggers (PST)

11.3.3.4 Error prevention (legal, financial, data)

Where ICT is, or includes, non-web software that provides a user interface, the non-web software shall satisfy the success criterion in Table 11.15.

Table 11.15: Non-web software success criterion: Error prevention (legal, financial, data)

For non-web 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:

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.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage without perception of colour (WPC), Minimize photosensitive seizure triggers (PST), Usage with limited cognition (LC), Privacy (PR)

Secondary: Usage without hearing (WH), Usage with limited hearing (LH), Usage without vocal capability (WVC), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR)

11.3.3.5 Void

11.3.3.6 Void

11.3.3.7 Redundant entry

Where ICT is, or includes, non-web software that provides a user interface, the non-web software shall satisfy WCAG 2.2 Success Criterion 3.3.7 Redundant Entry.

Relationship between requirements and functional performance criteria:

Primary: Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Usage with limited cognition (LC)

Secondary: Usage without vision (WV), Usage with limited vision (LV)

11.3.3.8 Accessible authentication (minimum)

Where ICT is, or includes, non-web software that provides a user interface, the non-web software shall satisfy the success criterion in Table 11.16.

Table 11.16: Non-web software success criterion: Accessible authentication (minimum)

A cognitive function test (such as remembering a password or solving a puzzle) is not required for any step in an authentication process unless that step provides at least one of the following:

• Alternative: Another authentication method that does not rely on a cognitive function test.
• Mechanism: A mechanism is available to assist the user in completing the cognitive function test.
• Object Recognition: The cognitive function test is to recognize objects.
• Personal Content: The cognitive function test is to identify non-text content the user provided to a website, non-web document, or software.

1. support for password entry by password managers to reduce memory need; and
2. copy and paste to reduce the cognitive burden of re-typing.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage without perception of colour (WPC), Usage without hearing (WH), Usage with limited hearing (LH), Usage without vocal capability (WVC), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Minimize photosensitive seizure triggers (PST), Usage with limited cognition (LC), Privacy (PR)

11.4 Robust

11.4.1 Compatible

11.4.1.1 Void

11.4.1.2 Name, role, value

Where ICT is, or includes, non-web software that provides a user interface, and the software includes functionality that is not closed to programmatic access of information by assistive technologies, the functionality that is not closed shall satisfy the success criterion in Table 11.17.

Table 11.17: Non-web software success criterion: 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 assistive technologies and accessibility features of underlying software.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Usage with limited cognition (LC)

Secondary: Usage without perception of colour (WPC), Usage without hearing (WH), Usage with limited hearing (LH)

11.4.1.3 Status messages

Where ICT is, or includes, non-web software that provides a user interface, and the software includes functionality that is not closed to programmatic access of information by assistive technologies, and the functionality that is not closed supports status message notifications, status messages from the functionality that is not closed can be programmatically determined so that they can be presented to the user by assistive technologies without receiving focus.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage without vocal capability (WVC), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Usage with limited cognition (LC)

11.5 Interoperability with keyboards and assistive technology

11.5.1 Closed functionality (informative)

Some requirements in clauses 11.1 to 11.5 have a pre-condition that indicates that they do not apply to closed functionality, so these requirements only apply to the open functionality of the ICT.

Requirements that do not have a closed functionality pre-condition apply to both the open and closed functionality of the ICT. The requirements under clause 5.1 apply to the closed functionality of the ICT.

For non-web software that has functionality that is closed and other functionality that is not closed, the requirements in clause 11.1 to 11.5 will still need to be met for the functionality that is not closed.

11.5.2 Accessibility services

11.5.2.1 Platform interoperability with assistive technologies

Where ICT is, or includes, platform software, the platform software shall provide a set of documented platform accessibility services that cover any user interface concept corresponding to clauses 11.5.2.5 to 11.5.2.17 supported within the platform software.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage without perception of colour (WPC), Usage without hearing (WH), Usage with limited hearing (LH), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Usage with limited cognition (LC)

Secondary: Privacy (PR)

11.5.2.2 Void

11.5.2.3 Use of accessibility services (recommendation)

Where ICT is, or includes, non-web software that provides a user interface, and the software includes functionality that is not closed to programmatic access of information by assistive technologies, the functionality that is not closed should use the applicable documented platform accessibility services listed in clause 11.5.2.1. If the documented platform accessibility services do not allow the software to meet the applicable requirements of clauses 11.5.2.5 to 11.5.2.17, then the functionality that is not closed should use other documented platform services to interoperate with assistive technology.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage without perception of colour (WPC), Usage without hearing (WH), Usage with limited hearing (LH), Usage without vocal capability (WVC), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Minimize photosensitive seizure triggers (PST), Usage with limited cognition (LC)

Secondary: Privacy (PR)

11.5.2.4 Assistive technology

Where ICT is, or includes, non-web software that is assistive technology, the assistive technology shall use the documented platform accessibility services corresponding to clauses 11.5.2.5 to 11.5.2.17.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage without perception of colour (WPC), Usage without hearing (WH), Usage with limited hearing (LH), Usage without vocal capability (WVC), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Minimize photosensitive seizure triggers (PST), Usage with limited cognition (LC), Privacy (PR)

11.5.2.5 Object information

Where ICT is, or includes, non-web software that provides a user interface, and the software includes functionality that is not closed to programmatic access of information by assistive technologies, the functionality that is not closed shall, by using the services as described in clause 11.5.2.3, make the user interface elements' role, state(s), boundary, name, and description programmatically determinable by assistive technologies for all functionality that is not closed to programmatic access of information by assistive technologies.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage without perception of colour (WPC), Usage without hearing (WH), Usage with limited hearing (LH), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Usage with limited cognition (LC)

Secondary: Privacy (PR)

11.5.2.6 Row, column, and headers

Where ICT is, or includes, non-web software that provides a user interface, and the software includes functionality that is not closed to programmatic access of information by assistive technologies, the functionality that is not closed shall, by using the services as described in clause 11.5.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 for all functionality that is not closed to programmatic access of information by assistive technologies.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Usage with limited cognition (LC)

11.5.2.7 Values

Where ICT is, or includes, non-web software that provides a user interface, and the software includes functionality that is not closed to programmatic access of information by assistive technologies, and there are user interface elements that can have values, the functionality that is not closed shall, by using the services as described in clause 11.5.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 for all functionality that is not closed to programmatic access of information by assistive technologies.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Usage with limited cognition (LC)

11.5.2.8 Label relationships

Where ICT is, or includes, non-web software that provides a user interface, and the software includes functionality that is not closed to programmatic access of information by assistive technologies, and there are user interface elements that are labels of other user interface elements, the functionality that is not closed 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.5.2.3, so that this information is programmatically determinable by assistive technologies for all functionality that is not closed to programmatic access of information by assistive technologies.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Usage with limited cognition (LC)

11.5.2.9 Parent-child relationships

Where ICT is, or includes, non-web software that provides a user interface, and the software includes functionality that is not closed to programmatic access of information by assistive technologies, and there are user interface elements that are parents of other user interface elements in a hierarchical structure, the functionality that is not closed shall, by using the services as described in clause 11.5.2.3, make the relationship between a user interface element and any parent or children elements programmatically determinable by assistive technologies for all functionality that is not closed to programmatic access of information by assistive technologies.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Usage with limited cognition (LC)

11.5.2.10 Text

Where ICT is, or includes, non-web software that provides a user interface, and the software includes functionality that is not closed to programmatic access of information by assistive technologies, and renders text to a screen, the software shall, by using the services as described in clause 11.5.2.3, make the text contents, text attributes used or available for user generated content, and the boundary of text programmatically determinable by assistive technologies for all functionality that is not closed to programmatic access of information by assistive technologies.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Usage with limited cognition (LC)

11.5.2.11 List of available actions

Where ICT is, or includes, non-web software that provides a user interface, and the software includes functionality that is not closed to programmatic access of information by assistive technologies, the functionality that is not closed shall, by using the services as described in clause 11.5.2.3, make a list of available actions that can be executed on a user interface element, programmatically determinable by assistive technologies for all functionality that is not closed to programmatic access of information by assistive technologies.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Usage with limited cognition (LC)

11.5.2.12 Execution of available actions

Where ICT is, or includes, non-web software that provides a user interface, and the software includes functionality that is not closed to programmatic access of information by assistive technologies, and there are user interface elements that have actions that can be executed by the user, the functionality that is not closed shall, by using the services as described in clause 11.5.2.3, allow the programmatic execution of the actions exposed according to clause 11.5.2.11 by assistive technologies where permitted by security requirements for all functionality that is not closed to programmatic access of information by assistive technologies.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Usage with limited cognition (LC)

11.5.2.13 Tracking of focus and selection attributes

Where ICT is, or includes, non-web software that provides a user interface, and the software includes functionality that is not closed to programmatic access of information by assistive technologies, the functionality that is not closed shall, by using the services as described in clause 11.5.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 for all functionality that is not closed to programmatic access of information by assistive technologies.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Usage with limited cognition (LC)

11.5.2.14 Modification of focus and selection attributes

Where ICT is, or includes, non-web software that provides a user interface, and the software includes functionality that is not closed to programmatic access of information by assistive technologies, and there are user interface elements that can receive focus or that enable text editing, the functionality that is not closed shall, by using the services as described in clause 11.5.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 permitted by security requirements for all functionality that is not closed to programmatic access of information by assistive technologies.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Usage with limited cognition (LC)

11.5.2.15 Change notification

Where ICT is, or includes, non-web software that provides a user interface, and the software includes functionality that is not closed to programmatic access of information by assistive technologies, the functionality that is not closed shall, by using the services as described in clause 11.5.2.3, notify assistive technologies about changes in those programmatically determinable attributes of user interface elements that are referenced in requirements 11.5.2.5 to 11.5.2.11 and 11.5.2.13, for all functionality that is not closed to programmatic access of information by assistive technologies.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Usage with limited cognition (LC)

11.5.2.16 Modifications of states and properties

Where ICT is, or includes, non-web software that provides a user interface, and the software includes functionality that is not closed to programmatic access of information by assistive technologies, and there are user interface elements whose state or properties can be modified by a user without the use of assistive technology, the functionality that is not closed shall, by using the services as described in clause 11.5.2.3, allow assistive technologies to programmatically modify states and properties of user interface elements, where the user can modify these items where permitted by security requirements for all functionality that is not closed to programmatic access of information by assistive technologies.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Usage with limited cognition (LC)

11.5.2.17 Modifications of values and text

Where ICT is, or includes, non-web software that provides a user interface, and the software includes functionality that is not closed to programmatic access of information by assistive technologies, and there are user interface elements whose values or text can be modified by a user without the use of assistive technology, the functionality that is not closed shall, by using the services as described in clause 11.5.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 where permitted by security requirements for all functionality that is not closed to programmatic access of information by assistive technologies.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Usage with limited cognition (LC)

11.6 Documented accessibility features

11.6.1 User control of accessibility features

Where ICT is, or includes, platform software, the platform software shall provide sufficient modes of operation for user control over documented platform accessibility features.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage without perception of colour (WPC), Usage without hearing (WH), Usage with limited hearing (LH), Usage without vocal capability (WVC), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Minimize photosensitive seizure triggers (PST), Usage with limited cognition (LC), Privacy (PR)

11.6.2 No disruption of accessibility features

Where ICT is, or includes, non-web software, the non-web software shall not disrupt documented platform accessibility features except when requested to do so by the user during the operation of the software.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage without perception of colour (WPC), Usage without hearing (WH), Usage with limited hearing (LH), Usage without vocal capability (WVC), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Minimize photosensitive seizure triggers (PST), Usage with limited cognition (LC), Privacy (PR)

11.7 User preferences

Where ICT is, or includes, non-web software that provides a user interface, and is not designed to be isolated from its platform, that user interface shall follow the values of the user preference settings for documented platform accessibility features unless this is essential to the function of the non-web software to not follow a user preference setting.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage without perception of colour (WPC), Usage without hearing (WH), Usage with limited hearing (LH), Usage without vocal capability (WVC), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Minimize photosensitive seizure triggers (PST), Usage with limited cognition (LC), Privacy (PR)

12 Information about products and services

12.1 Accessible information about products

Where ICT is, or includes, information about a product, made available in a digital form, the presentation of the information shall conform to the requirements of clause 9 if it is available in a web format, clause 10 if it is available as a non-web document, and clause 11 if it is available as part of non-web software.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage without perception of colour (WPC), Usage without hearing (WH), Usage with limited hearing (LH), Usage without vocal capability (WVC), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Minimize photosensitive seizure triggers (PST), Usage with limited cognition (LC), Privacy (PR)

12.2 Accessible information about services

Where ICT is, or includes, information about a service, made available in a digital form, the presentation of the information shall conform to the requirements of clause 9 if it is available in a web format, clause 10 if it is available as a non-web document, and clause 11 if it is available as part of non-web software.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage without perception of colour (WPC), Usage without hearing (WH), Usage with limited hearing (LH), Usage without vocal capability (WVC), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Minimize photosensitive seizure triggers (PST), Usage with limited cognition (LC), Privacy (PR)

12.3 Accessibility and compatibility features

Where ICT has documentation about the use of the ICT on the ICT or there is an official webpage that provides documentation about the use of the ICT, this documentation about the use of the ICT on the ICT shall include directly or via a link to a web page that, directly or via further links, provides information on the accessibility features of the ICT, how to use the features, and how to get support for accessibility features.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage without perception of colour (WPC), Usage without hearing (WH), Usage with limited hearing (LH), Usage without vocal capability (WVC), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Minimize photosensitive seizure triggers (PST), Usage with limited cognition (LC), Privacy (PR)

12.4 Electronic program guides

Where ICT is an Electronic Programme Guide (EPG), the EPG shall provide information on the availability of subtitles, audio description, spoken subtitles, and sign language interpretation of the media.

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage without perception of colour (WPC), Usage without hearing (WH), Usage with limited hearing (LH), Usage without vocal capability (WVC), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Minimize photosensitive seizure triggers (PST), Usage with limited cognition (LC), Privacy (PR)

12.5 Electronic program guide display

Where ICT displays an Electronic Programme Guide (EPG) presenting media item(s), and information about the availability of subtitles, audio description, spoken subtitles, or sign language interpretation for the media item(s), the ICT shall provide a mode of operation in which the availability of subtitles, audio description, spoken subtitles, sign language can be determined without activating the media item(s).

Relationship between requirements and functional performance criteria:

Primary: Usage without vision (WV), Usage with limited vision (LV), Usage without perception of colour (WPC), Usage without hearing (WH), Usage with limited hearing (LH), Usage without vocal capability (WVC), Usage with limited manipulation or strength (LMS), Usage with limited reach (LR), Minimize photosensitive seizure triggers (PST), Usage with limited cognition (LC), Privacy (PR)

13 ICT providing relay or emergency service access

13.1 Relay services requirements

13.1.1 General (informative)

Relay services enable users with speech or hearing disabilities to communicate with other users of services providing real-time bidirectional voice. The relay services convert communication modalities, allowing each user to communicate in their preferred way, using human assistance or automated translation or hybrids between these forms. Relay services also support users with cognitive and memory disabilities.

Users who use relay services because of a disability are here called "primary users", while others involved are called "secondary users".

If a primary user needs to communicate using media not supported by the secondary user's system, the primary user makes use of a system that offers that media. For instance, a sign language user communicating with a voice-only user might connect via a relay service handling sign language in video.

Even if it is unusual in practice, relay services can be interconnected to facilitate communication between primary users who cannot directly communicate. For example, a hard of hearing person using a text relay service can communicate with a deaf sign language user via a video relay service by connecting their respective services by voice.

Clause 13.1.2 of the present document addresses invocation and connection, while clause 13.1.3 of the present document addresses the media transmission and modality conversion, also including media transmission and relay service use in some special contexts.

The types of possible relay services include, but are not limited to the following types, which are more completely described in ETSI ES 202 975 [i.6]:

1. Text relay services which provide conversion between real-time text and voice. Text relay services can be divided in the following three subtypes regarding their mediation directions:
   • Bidirectional text relay service, which converts between speech and real-time text in both directions with the primary user both reading and sending text.
   • Text relay service with voice through. which convert speech towards the primary user to text and let speech through from the primary user.
   • Text relay service with hearing through, which convert text from the primary user to speech, and let speech through to the primary user.
2. Captioned telephony services which convert speech to real-time text towards the primary user while letting voice through in both directions.
3. Video relay services which convert between sign language in video to and from primary users and spoken language from and to secondary users.
4. Speech-to-speech relay services which convert between unclear speech from the primary user to clear speech to the secondary users, also letting speech through in both directions.
5. Lipspeaking relay services which convert from speech in a voice channel to lipspeaking in a video channel towards the primary user and let voice through in the both directions.
6. Cognitive support services which provide support for memory and other cognitive functions in the voice channel in the direction towards the primary user and let voice through in both directions.

For detailed guidelines on how to develop and implement relay service, it is best practice to meet the applicable relay service requirements of ETSI ES 202 975 [i.6].

Relay service access is also essential in emergency communication cases. These aspects are elaborated in ETSI EN 202 919 [i.56].

The general accessibility requirements contained in the clauses 13.1.2 and 13.1.3 of the present document are based on the functional architecture and invocation of relay services described in ETSI ES 202 975 [i.6].

13.1.2 Relay service access

13.1.2.1 General remarks on access to relay services (informative)

To ensure that the primary users of the relay service have equivalent access to electronic communication, they need to have free choice of communicating with or without the support of relay services. For instance, primary users with hearing impairments who use an ICT communication system that includes alternatives to voice communication such as RTT or total conversation, and where these media are also used by the secondary users, should, if desired, be able to contact the secondary users using a common communication channel, without involvement of the relay services.

Clause 13.1.2 of the present document provides requirements for providing the access to relay services for the primary users that ensures their equivalent access to the communication services.

13.1.2.2 Use of the primary user destination address in relayed communications

Where ICT is intended to support relay service inclusion in communication, and is, or includes, relay service invocation functions, the relay service invocation functions shall use destination addresses given to the primary users by their communication systems.

Relationship between requirements and functional performance criteria:

Primary: Usage without hearing (WH), Usage with limited hearing (LH), Usage without vocal capability (WVC)

Secondary: Usage with limited cognition (LC)

13.1.2.3 Conveying of caller identifier in relayed communications for primary relay users

Where ICT is intended to support relay service inclusion in communication, and is, or includes, relay service invocation functions, the ICT shall convey the caller identifiers of primary users of relay services in their communication establishments to secondary users, unless the calling user equipment is set to anonymous communication mode.

Relationship between requirements and functional performance criteria:

Primary: Usage without hearing (WH), Usage with limited hearing (LH), Usage without vocal capability (WVC)

Secondary: Usage with limited cognition (LC)

13.1.2.4 Relay service invocation decision in outgoing communications

Where ICT is intended to support relay service inclusion in communication, and is, or includes, relay service invocation functions, the ICT shall provide features that enable the primary user to decide by user action at the moment of initiating an outgoing communication if a relay service will be invoked in the communication or not.

Relationship between requirements and functional performance criteria:

Primary: Usage without hearing (WH), Usage with limited hearing (LH), Usage without vocal capability (WVC)

Secondary: Usage with limited cognition (LC)

13.1.2.5 Relay service invocation decision in incoming communications

Where ICT is intended to support relay service inclusion in communication, and is, or includes, relay service invocation functions, the ICT shall provide features that enable the primary user to decide by user action at the moment of receiving an incoming communication if a relay service will be invoked in the communication or not.

Relationship between requirements and functional performance criteria:

Primary: Usage without hearing (WH), Usage with limited hearing (LH), Usage without vocal capability (WVC)

Secondary: Usage with limited cognition (LC)

13.1.2.6 Relay service support requested by the primary user for emergency communications

Where ICT is intended to support relay service inclusion in communication, and is, or includes, a relay service invocation function, the ICT shall initiate and perform emergency communications on the request by the primary user and invoke relay service.

Relationship between requirements and functional performance criteria:

Primary: Usage without hearing (WH), Usage with limited hearing (LH), Usage without vocal capability (WVC)

Secondary: Usage with limited cognition (LC)

13.1.3 Relay service requirements

13.1.3.1 Relaying action in real-time bidirectional voice communication

Where ICT is, or includes, a relay service, the relay service shall allow primary users to participate in speech communication with secondary users by performing modality conversion or communication support functions according to the type and mode of operation of the relay service.

Relationship between requirements and functional performance criteria:

Primary: Usage without hearing (WH), Usage with limited hearing (LH), Usage without vocal capability (WVC)

Secondary: Usage with limited cognition (LC)

13.1.3.2 Media handling in relay service communication

Where ICT is intended to support relay service inclusion in communication, and is, or includes, relay functions, the relay service invocation functions shall allow passing-through media not involved in the conversation but enabled by the communication clients of the primary and secondary users.

Relationship between requirements and functional performance criteria:

Primary: Usage without hearing (WH), Usage with limited hearing (LH), Usage without vocal capability (WVC)

Secondary: Usage with limited cognition (LC)

13.1.3.3 Relay service support in ICT based conferences

Where ICT is, or includes, a relay service, the ICT shall support participation of primary users in conferences.

Relationship between requirements and functional performance criteria:

Primary: Usage without hearing (WH), Usage with limited hearing (LH), Usage without vocal capability (WVC)

Secondary: Usage with limited cognition (LC)

13.1.3.4 Relay service support during emergency communications initiated by the PSAP

Where ICT is, or includes, a relay service, the relay service shall accept invocations by emergency communication PSAPs.

Relationship between requirements and functional performance criteria:

Primary: Usage without hearing (WH), Usage with limited hearing (LH), Usage without vocal capability (WVC)

Secondary: Usage with limited cognition (LC)

13.2 Void

13.3 Access to emergency services (informative)

The present document addresses the accessibility of emergency communication by means of the emergency communication-specific scenarios of clauses 6.0.6 to 6.0.9 and by specific references to emergency communication in some of the clause C.6 conformance tests of the accessibility requirements.

List

The following selections were made when creating this document:

• No provisions have been removed.

Annex - Tables and figures (from EN 301 549)

Table 5.1

Viewing distance (mm)	x-height (mm) for 16CSSpx
400	2,38
500	2,98
700	4,17
1 000	5,95
2 000	11,90
3 000	17,86
5 000	29,76
10 000	59,52

Figure 8.1: Obstructed side reach (see Table 8.1 for explanations)

Table 8.1: Values for the size of obstructions for side reach

Description	Values for stationary ICT which complies with clause 8.3.10.2	Values for stationary ICT which complies with clause 8.3.10.3
(a) Obstruction depth (Side reach)	Maximum 300 mm	Maximum 610 mm
(b) High reach	Maximum 1 100 mm	Maximum 1 220 mm for depth (a) up to 255 mm Maximum 1 170 mm for depth (a) of up to 610mm
(c) Obstruction height	Maximum 800 mm	Maximum 865 mm

Figure 8.2: Knee and toe clearance underneath an obstruction (see Table 8.2 for explanations)

Table 8.2: Values for obstructions and knee and toe space below obstructions

Description	Values for stationary ICT which complies with clause 8.3.11.1	Values for stationary ICT which complies with clause 8.3.11.2
(a) Width of the clear space	900 mm, but max. the width of the stationary ICT	760 mm, but max. the width of the ICT
(b) Height of the free space below an obstruction	Min 700 mm	Min. 685 mm
(c) Depth of the knee space at the height of the free space (b)	Min 280 mm but not larger than depth of the stationary ICT including the depth of any obstruction	Min 205 mm but not larger than depth of the stationary ICT including the depth of any obstruction
(d) Depth of the knee space at the minimum height of the toe space.	Min. 350 but not larger than the depth of the ICT including the depth of any obstruction	Min. 280 but not larger than the depth of the ICT including the depth of any obstruction
(e) Depth of the toe space at the Height of the toe space (f).	Minimum 450 mm, but not larger than the depth of the ICT including the depth of any obstruction	Minimum 430 mm, but not larger that the depth of the ICT including the depth of any obstruction
(f) Height of the toe space	Minimum 350 mm	Minimum 230 mm
(g) Height of the obstruction	Maximum 800 mm	Maximum 865 mm

Table 9.1: WCAG 2.2 Level AAA Success Criteria

No.	Guideline	Success Criterion Number	Success Criteria Name
1	Time-based media	1.2.6	Sign Language (Prerecorded)
2	Time-based media	1.2.7	Extended Audio Description (Prerecorded)
3	Time-based media	1.2.8	Media Alternative (Prerecorded)
4	Time-based media	1.2.9	Audio-only (Live)
5	Adaptable	1.3.6	Identify Purpose
6	Distinguishable	1.4.6	Contrast (Enhanced)
7	Distinguishable	1.4.7	Low or No Background Audio
8	Distinguishable	1.4.8	Visual Presentation
9	Distinguishable	1.4.9	Images of Text (No Exception)
10	Keyboard Accessible	2.1.3	Keyboard (No Exception)
11	Enough time	2.2.3	No Timing
12	Enough time	2.2.4	Interruptions
13	Enough time	2.2.5	Re-authenticating
14	Enough time	2.2.6	Timeouts
15	Seizures and physical reactions	2.3.2	Three Flashes
16	Seizures and physical reactions	2.3.3	Animation from Interactions
17	Navigable	2.4.8	Location
18	Navigable	2.4.9	Link Purpose (Link Only)
19	Navigable	2.4.10	Section Headings
20	Navigable	2.4.12	Focus Not Obscured (Enhanced)
21	Navigable	2.4.13	Focus Appearance
22	Input modalities	2.5.5	Target Size (Enhanced)
23	Input modalities	2.5.6	Concurrent Input Mechanisms
24	Readable	3.1.3	Unusual Words
25	Readable	3.1.4	Abbreviations
26	Readable	3.1.5	Reading Level
27	Readable	3.1.6	Pronunciation
28	Predictable	3.2.5	Change on Request
29	Input assistance	3.3.5	Help
30	Input assistance	3.3.6	Error Prevention (All)
31	Input assistance	3.3.9	Accessible Authentication (Enhanced)

Annex - References (from EN 301 549)

2.1 Normative references

References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies.

Referenced documents which are not found to be publicly available in the expected location might be found in the ETSI docbox.

The following referenced documents are necessary for the application of the present document.

• [1] Void.
• [2] ETSI ES 200 381-1 (V1.2.1) (October 2012): "Telephony for hearing impaired people; Inductive coupling of telephone earphones to hearing aids; Part 1: Fixed-line speech terminals".
• [3] ETSI ES 200 381-2 (V1.1.1) (October 2012): "Telephony for hearing impaired people; Inductive coupling of telephone earphones to hearing aids; Part 2: Cellular speech terminals".
• [4] W3C^® Recommendation (12 December 2024)/ISO/IEC 40500:2025: "Web Content Accessibility Guidelines (WCAG) 2.2".

2.2 Informative references

References are either specific (identified by date of publication and/or edition number or version number) or non specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies.

The following referenced documents may be useful in implementing an ETSI deliverable or add to the reader's understanding, but are not required for conformance to the present document.

• [i.1] ANSI/IEEE C63.19 (2019): "American National Standard Methods of Measurement of Compatibility between Wireless Communication Devices and Hearing Aids".
• [i.2] ANSI/TIA-4965: "Telecommunications telephone terminal equipment receive volume control requirements for digital and analogue wireline handset terminals".
• [i.3] ANSI/TIA-5050: "Telecommunications Communications Products Receive Volume Control Requirements for Wireless (Mobile) Devices".
• [i.4] European Commission M 376 - EN: "Standardisation Mandate to CEN, CENELEC and ETSI in support of European accessibility requirements for public procurement of products and services in the ICT domain".
• [i.5] ETSI EG 201 013: "Human Factors (HF); Definitions, abbreviations and symbols".
• [i.6] ETSI ES 202 975: "Human Factors (HF); Requirements for relay services".
• [i.7] ETSI ETS 300 767: "Human Factors (HF); Telephone Prepayment Cards; Tactile Identifier".
• [i.8] Void.
• [i.9] Void.
• [i.10] Void.
• [i.11] ETSI TS 126 114: "Universal Mobile Telecommunications System (UMTS); LTE; 5G; IP Multimedia Subsystem (IMS); Multimedia Telephony; Media handling and interaction (3GPP TS 26.114)".
• [i.12] ETSI TS 122 173: "Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; IP Multimedia Core Network Subsystem (IMS) Multimedia Telephony Service and supplementary services; Stage 1 (3GPP TS 22.173)".
• [i.13] IETF RFC 4103 (2005): "RTP Payload for Text Conversation".
• [i.14] ISO/IEC 17007:2009: "Conformity assessment — Guidance for drafting normative documents suitable for use for conformity assessment".
• [i.15] ISO 9241-11:2018: "Ergonomics of human-system interaction — Part 11: Usability: Definitions and concepts".
• [i.16] ISO 9241-110:2020: "Ergonomics of human-system interaction — Part 110: Interaction principles".
• [i.17] ISO 9241-171:2008: "Ergonomics of human-system interaction — Part 171: Guidance on software accessibility".
• [i.18] ISO/IEC 13066-1:2011: "Information technology — Interoperability with assistive technology (AT) — Part 1: Requirements and recommendations for interoperability".
• [i.19] Recommendation ITU-T E.161 (2001): "Arrangement of digits, letters and symbols on telephones and other devices that can be used for gaining access to a telephone network".
• [i.20] Recommendation ITU-T G.722 (1988): "7 kHz audio-coding within 64 kbit/s".
• [i.21] Recommendation ITU-T G.722.2 (2003): "Wideband coding of speech at around 16 kbit/s using Adaptive Multi-Rate Wideband (AMR-WB)".
• [i.22] Recommendation ITU-T V.18 (2000): "Operational and interworking requirements for DCEs operating in the text telephone mode".
• [i.23] TIA-1083-B (2015): "Telecommunications Communications Product; Handset Magnetic Measurement Procedures and Performance Requirements".
• [i.24] Void.
• [i.25] W3C^® Group Note (21 August 2025): "Guidance on Applying WCAG 2 to Non-Web Information and Communications Technologies (WCAG2ICT)".
• [i.26] C(2017)2585 - Standardisation request M/554: "Commission Implementing Decision of 27.4.2017 on a standardisation request to the European standardisation organisations in support of Directive (EU) 2016/2102 of the European Parliament and of the Council on the accessibility of the websites and mobile applications of public sector bodies".
• [i.27] Directive (EU) 2016/2102 of the European Parliament and of the Council of 26 October 2016 on the accessibility of the websites and mobile applications of public sector bodies.
• [i.28] C(2022)6456 - Standardisation request M/587: " Commission Implementing Decision of 14.9.2022 on a standardisation request to the European standardisation organisations as regards the accessibility requirements of products and services in support of Directive (EU) 2019/882 of the European Parliament and of the Council".
• [i.29] Directive (EU) 2019/882 of the European Parliament and of the Council of 17 April 2019 on the accessibility requirements for products and services.
• [i.30] EN 301 549 (V3.2.1) (March 2021): "Accessibility requirements for ICT products and services" (jointly produced by ETSI/CEN/CENELEC).
• [i.31] Void.
• [i.32] ISO/IEC TS 20071-25:2017: "Information technology — User interface component accessibility — Part 25: Guidance on the audio presentation of text in videos, including captions, subtitles and other on-screen text".
• [i.33] W3C^® Recommendation (24 September 2015): "Authoring Tool Accessibility Guidelines (ATAG) 2.0".
• [i.34] W3C^® Working Group Note (15 December 2015): "User Agent Accessibility Guidelines (UAAG) 2.0".
• [i.35] ISO 21542:2021: "Building construction — Accessibility and usability of the built environment".
• [i.36] Void.
• [i.37] Recommendation ITU-T T.140 (1998): "Protocol for multimedia application text conversation".
• [i.38] Recommendation ITU-T F.703 (2000): "Multimedia conversational services".
• [i.39] Final Community Group Report (26 March 2026): "Schema.org Accessibility Properties for Discoverability Vocabulary".
• [i.40] Directive 2014/24/EU of the European Parliament and of the Council of 26 February 2014 on public procurement and repealing Directive 2004/18/EC.
• [i.41] W3C^® Recommendation (11 December 2008)/ISO/IEC 40500:2012: "Web Content Accessibility Guidelines (WCAG) 2.0".
• [i.42] W3C^® Recommendation (5 June 2018): "Web Content Accessibility Guidelines (WCAG) 2.1".
• [i.43] ETSI TR 126 982: "5G; Implementation guidelines for Multiparty RTT (3GPP TR 26.982)".
• [i.44] GSMA PRD IR.92: "IMS Profile for Voice and SMS".
• [i.45] GSMA PRD IR.94 "IMS Profile for Conversational Video Service".
• [i.46] GSMA NG.114: "IMS Profile for Voice, Video and Messaging over 5GS".
• [i.47] ETSI TS 103 478: "Emergency Communications (EMTEL); Pan-European Mobile Emergency Application".
• [i.48] ETSI TS 103 479: "Emergency Communications (EMTEL); Core elements for network independent access to emergency services".
• [i.49] ETSI TS 103 871: "Emergency Communications (EMTEL); PEMEA Real-Time Text Extension".
• [i.50] IETF RFC 3261: "SIP: Session Initiation Protocol", J. Rosenberg et al., 2005.
• [i.51] IETF RFC 3550: "RTP: A Transport Protocol for Real-Time Applications", H. Schulzrinne et al., 2003.
• [i.52] IETF RFC 9071 (2021): "RTP-Mixer Formatting of Multiparty Real-Time Text".
• [i.53] ISO/IEC 10646:2020: "Information technology — Universal coded character set (UCS)".
• [i.54] ISO/IEC 17549-1:2022: "Information technology — User interface requirements and recommendations on menu navigation: Part 1: Framework".
• [i.55] ETSI TS 126 226: "Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); Cellular text telephone modem; General description (3GPP TS 26.226)".
• [i.56] ETSI TS 103 919: "Emergency Communications (EMTEL); Accessibility and Interoperability of Emergency Communications
• [i.57] IETF RFC 8831: "WebRTC Data Channels".
• [i.58] W3C^® Recommendation (8 October 2024): "WebRTC: Real-Time Communication in Browsers".
• [i.59] ETSI TR 103 708: "Human Factors (HF); Real-Time Text (RTT) in Multiparty Conference Calling".
• [i.60] ISO/IEC 23859:2023: "Information technology — User interfaces — Requirements and recommendations on making written text easy to read and understand".
• [i.61] Recommendation ITU-T P.1305 (2016): "Effect of delays on telemeeting quality".
• [i.62] IETF RFC 5194 (2008): "Framework for Real-Time Text over IP Using the Session Initiation Protocol (SIP)".
• [i.63] Center for Inclusive Design and Environmental Access (2010): "Anthropometry of Wheeled Mobility Project - Final Report".
• [i.64] CEN/CENELEC EN 17210: "Accessibility and usability of the built environment - Functional requirements".
• [i.65] Recommendation ITUT H.Sup1 (1999): "Application profile - Sign language and lip-reading real-time conversation using low bit rate video communication".
• [i.66] ETSI TR 104 060: "Human Factors (HF); Guidance on how to apply the EN 301 549 to digital television products".
• [i.67] Void.
• [i.68] Void.
• [i.69] ISO/TR 22411:2021: "Ergonomics data for use in the application of ISO/IEC Guide 71:2014".
• [i.70] W3C^® Recommendation (7 June 2011): "Cascading Style Sheets Level 2 Revision 1 (CSS 2.1) Specification", 2011 / 2016 / 2021.
• [i.71] ISO 14289-1:2014: Document management applications — Electronic document file format enhancement for accessibility: Part 1: Use of ISO 32000-1 (PDF/UA-1).
• [i.72] ISO 14289-2:2024: Document management applications — Electronic document file format enhancement for accessibility: Part 2: Use of ISO 32000-2 (PDF/UA-2).
• [i.73] ISO/IEC TS 20071-23:2018: "Information technology — User interface component accessibility — Part 23: Visual presentation of audio information (including captions and subtitles)".
• [i.74] Recommendation ITU T H.264: "Advanced video coding for generic audiovisual services".
• [i.75] Recommendation ITU T H.265: "High efficiency video coding".
• [i.76] IETF RFC 6386 (2011): "VP8 Data Format and Decoding Guide".
• [i.77] ETSI ES 204 009: "Human Factors (HF); Requirements for interoperable total conversation services".
• [i.78] ADA Accessibility Standards: "Americans with Disabilities Act – Accessibility Standards", 2010.
• [i.79] ISO/IEC 18012-1:2004: "Information technology — Home Electronic System — Guidelines for product interoperability Part 1: Introduction".
• [i.80] ETSI ETS 300 381 (Edition 1) (December 1994): "Telephony for hearing impaired people; Inductive coupling of telephone earphones to hearing aids".
• [i.81] Directive (EU) 2018/1972 of the European Parliament and of the Council of 11 December 2018 establishing the European Electronic Communications Code (Recast) (Text with EEA relevance).
• [i.82] Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing Directive 95/46/EC (General Data Protection Regulation) (Text with EEA relevance).
• [i.83] IETF RFC 6716: "Definition of the Opus Audio Codec", 2012.
• [i.84] IETF RFC 7874: "WebRTC Audio Codec and Processing Requirements", 2016.
• [i.85] IETF RFC 7875: "Additional WebRTC Audio Codecs for Interoperability", 2016.
• [i.86] IETF RFC 8251: "Updates to the Opus Audio Codec", 2017.
• [i.87] IETF RFC 8825: "Overview: Real-Time Protocols for Browser-Based Applications", 2021.
• [i.88] ETSI TS 126 441: "Universal Mobile Telecommunications System (UMTS); LTE; 5G; Codec for Enhanced Voice Services (EVS); General overview (3GPP TS 26.441)".
• [i.89] ETSI TS 103 495: "Emergency Communications (EMTEL); PEMEA Audio Video Extension".

Annex – Definition of terms, symbols and abbreviations (from EN 301 549)

3.1 Terms

For the purposes of the present document, the terms given in ETSI EG 201 013 [i.5] and the following apply:

access space

space intended to be occupied by the person, including their Assistive Technology, while they are using the product

accessibility

extent to which products, systems, services, environments and facilities can be used by people from a population with the widest range of user needs, characteristics and capabilities, to achieve identified goals in identified contexts of use (from ISO 9241-11:2018 [i.15])

NOTE 1: Context of use includes direct use or use supported by assistive technologies.

NOTE 2: The context in which the ICT is used may affect its overall accessibility. This context could include other products and services with which the ICT may interact.

accessibility inspection tool for platforms

software-based tool that can be used by developers or third party accessibility evaluators to check the use of the documented platform accessibility services

NOTE 1: For a given platform, the accessibility inspection tool can be:

1. Platform-provided tool for accessibility inspection.
2. Platform-provided assistive technologies, if 1 is not available or is not useful to test a given requirement.
3. Generally-available assistive technologies for the platform, if neither 1 nor 2 are available.

NOTE 2: Platform tools are resources provided to software developers by the organization producing the platform. Some platform tools may include the function of inspecting the accessibility of ICTs developed for that platform. Some platform tools may be available to developers but not to 3rd party accessibility evaluators.

NOTE 3: Platform-provided assistive technologies are assistive technologies that are part of the platform. In the context of the present document, operating systems are popular examples of platforms.

NOTE 4: Examples of assistive technologies (either platform or non-platform) that can be used as inspection tools are, but are not limited to, a screen reader and a voice control system.

applicable (accessibility) requirement

requirement, whose preconditions are true for an ICT

applicable scenario

scenario, whose preconditions are true for an ICT

applicable test

test, whose preconditions are true for an ICT

Application Programming Interface (API)

collection of invocation methods and associated parameters used by one piece of software to request actions from another piece of software (from ISO/IEC 18012-1:2004 [i.79])

Assistive Listening Devices (ALDs)

devices that help separate the sounds, particularly speech, that a person wants to hear from background noise by bringing sound directly into the ear

NOTE: These are often found in meetings and public venues such as plays, concerts and places of worship. They can also be used at home with televisions and other products with auditory output.

Assistive Technology (AT)

any item, piece of equipment, service or product system including software that is used to increase, maintain, substitute or improve functional capabilities of persons with disabilities or for, alleviation and compensation of impairments, activity limitations or participation restrictions

NOTE 1: Assistive technology is an umbrella term that is broader than assistive products.

NOTE 2: Assistive technology can include assistive services, and professional services needed for assessment, recommendation and provision. Some examples of "assistive services" would be: all of the relay services, text to speech services, OCR services that change images of text to text, AI's that shift the language level of a document.

NOTE 3: Where ICT does not support directly connected assistive technology, but which can be operated by a system connected over a network or other remote connection, such a separate system (with any included assistive technology) can also be considered assistive technology. 

audio description

narration added to the soundtrack to describe important visual details of synchronized audio-visual content, which cannot be understood from the main soundtrack alone

NOTE 1: This is also variously described using terms such as "video description" or variants such as "descriptive narration" and "described video".

NOTE 2: Audio description helps blind persons, persons with low vision, and persons who need assistance with understanding important facial expressions and other visual content to perceive and understand the visual content of audio-visual media.

NOTE 3: Audio description can provide information about actions, characters, scene changes, on-screen text, and other visual content.

NOTE 4: The audio description is generally inserted in the gaps in the main audio narrative. It typically uses a different voice, tone, or speed to separate it from the main audio.

authoring tool

software that can be used to create or modify content

NOTE 1: An authoring tool may be used by a single user or multiple users working collaboratively.

NOTE 2: An authoring tool may be a single stand-alone application or be comprised of collections of applications.

NOTE 3: An authoring tool may produce content that is intended for further modification or for use by end-users.

NOTE 4: Authoring tool software can be web-based or non-web-based application(s) such as Content Management Systems, social media, word processors and courseware tools. 

caller identifier (caller ID)

information presented to the recipient of an incoming request for a communication session (such as a phone call, video call, or messaging) that uniquely specifies the identity of the originating party

captioned telephony

service which converts speech to real-time text towards the primary user while letting voice through in both directions

NOTE 1: When provided for VoIP, it is called IP Captioned Telephony Service or IPCTS in the US.

NOTE 2: A conversation may have more than one primary user.

closed functionality

functionality that is limited by characteristics that prevent a user from attaching, installing or using assistive technology

closed subtitles

subtitle visually presented only in response to user preference (after ISO/IEC TS 20071-23 [i.73])

communication client

terminating software that transmits and receives communications

NOTE 1: A communication client can be limited to work with only one communication system that is provided by one specific system provider.

NOTE 2: The ICT that is, or includes, the communication client is responsible for ensuring that the content of the communication is communicated to and from the user of the communication client.

communication system

ICT that enables real-time bidirectional voice communications to flow between communication clients

NOTE 1: A communication system can contain several component parts that may not be separately identifiable from outside the system. Some communication systems might simply be an "interpersonal communication service" as defined in point 5 of Article 2 of Directive (EU) 2018/1972 [i.81].

NOTE 2: Some communication systems are separate from their communication clients while in others the communication clients form an integral part of a proprietary communication system.

communicator

: natural person, or software imitating a natural person, using a communication client to communicate

NOTE: Software that imitates a natural person can also be an effective way to test whether the requirements in the present document are met.

compatible communication system

communication system that uses the same communication standards as another communication system

content

information and sensory experience to be communicated to the user by means of software, including code or mark-up that defines the content's structure, presentation, and interactions (after WCAG2ICT [i.25])

NOTE 1: Content occurs in three places: web pages, non-web documents and non-web software. When content occurs in a web page or a non-web document, a user agent is needed in order to communicate the content's information and sensory experience to the user. When content occurs in software, a separate user agent is not needed in order to communicate the content's information and sensory experience to the user - the software itself performs that function.

NOTE 2: For non-web software, content also includes the user interface.

context of use

combination of users, goals and tasks, resources, and environment (from ISO 9241-11:2018 [i.15])

NOTE: The "environment" in a context of use includes the technical, physical, social, cultural and organizational environments.

control (when used as a noun in the form of a "user interface control")

user interface element that is operated by a user in order to interact with a product

NOTE 1: Examples of things controls are used for include, but are not limited to, input of information, direct actions, adjustments or commands for the product to act on, store, or pass along.

NOTE 2: Controls may be physical, or virtual (buttons on a screen, or gestures in the air, or biological measurements, etc.).

conversational gain

increase, measured in decibels [dB], of the speech level delivered to a user's ear above a reference level of 70 dB SPL

discoverability metadata

information about a digital resource (e.g. a PDF document, a video document, an audio document, etc.) that supports users and systems to find, identify, and evaluate that resource

document (non-web document)

logically distinct assembly of content (such as a file, set of files, or streamed media) that functions as a single entity rather than a collection, that is not part of software and that does not include its own user agent (after WCAG2ICT [i.25])

NOTE 1: A document always requires a user agent to present its content to the user.

NOTE 2: Letters, e-mail messages, spreadsheets, books, pictures, presentations, and movies are examples of documents.

NOTE 3: Software configuration and storage files such as databases and virus definitions, as well as computer instruction files such as source code, batch/script files, and firmware, are examples of files that function as part of software and thus are not examples of documents. If and where software retrieves "information and sensory experience to be communicated to the user" from such files, it is just another part of the content that occurs in software and is covered by WCAG2ICT like any other parts of the software. Where such files contain one or more embedded documents, the embedded documents remain documents under this definition.

NOTE 4: A collection of files zipped together into an archive, stored within a single virtual hard drive file, or stored in a single encrypted file system file, do not constitute a single document when so collected together. The software that archives/encrypts those files or manages the contents of the virtual hard drive does not function as a user agent for the individually collected files in that collection because that software is not providing a fully functioning presentation of that content.

NOTE 5: Anything that can present its own content without involving a user agent, such as a self-playing book, is not a document but is software.

NOTE 6: A single document may be composed of multiple files such as the video content and closed caption text. This fact is not usually apparent to the end-user consuming the document/content.

NOTE 7: An assembly of files that represented the video, audio, subtitles and timing files for a movie is an example of a document.

NOTE 8: A binder file used to bind together the various exhibits for a legal case would not be a document.

NOTE 9: Documents may contain sub-documents.

documented accessibility feature

feature of an ICT offered to end-users that can enhance accessibility and is documented

documented platform accessibility feature

feature of a platform offered to end users that can enhance accessibility and is documented

documented platform accessibility service

subset of the platform's Application Programming Interface (API) that supports interoperability between a user interface running on the platform software and assistive technology

NOTE 1: They allow application developers to create software that is compatible with assistive technologies.

NOTE 2: These services are also often used by non-accessibility software and testing software.

documented platform service

service provided by the platform that is documented by the platform author for public use by accessibility applications and utilities created by third parties

NOTE: Platform services provide documented methods that allow software to add or integrate functionality provided by the platform rather than having to attach themselves in an ad-hoc fashion which is hard for both parties to support.

Electronic Program Guide (EPG)

means of presenting available content to the consumer, allowing selection of desired content

embedded

directly included in the content that is downloaded to the user agent and its extension, and is intended to be used in rendering the web page

NOTE: Something that is downloaded using a mechanism on the web page but is not used in rendering the page is not "embedded" in the page.

height in CSSpx

height as measured in CSS pixels

NOTE 1: CSS pixels are not a unit of length but a measure of angle of view. A CSS pixel (CSSpx) is based on the reference pixel, which is defined by a visual angle. The angle of view for a reference pixel is defined as 2*arctan (1 / (28 × 192)). (The angle which is created by looking at a real pixel with the size 1/96^th of an inch at 28 inches viewing distance (the reference viewing distance). The height in CSSpx is transposed into a physical measure of height by multiplying the viewing distance with 1 / (28 × 96)) which is equivalent to 1 / 2 688.
The formula for calculating the physical height (in mm) from the height (in CSSpx) and the distance D (in mm) from the eye to the display is therefore physical height (mm) = D (mm) × height (CSSpx) / 2 688.

NOTE 2: See https://www.w3.org/TR/CSS2/syndata.html#length-units for an explanation of absolute length calculations.

Information and Communication Technology (ICT)

technology, interconnected system or subsystem used for the creation, conversion, processing, transmission, gathering, or presentation of information or commands from users

NOTE 1: Examples of ICT include but are not limited to web pages, non-web and hybrid documents, electronic content, hardware, communication products, computers and ancillary equipment, software including mobile applications, information kiosks and transaction machines, audiovisual technologies, videos, intelligent user agents, information services.

NOTE 2: Anything with a digital user interface would fall within this definition although most but not all requirements relate to ICT that accepts information or commands from a user in addition to transmitting and/or presenting information.

ICT network

technology and resources supporting the connection and operation of interconnected ICT

interlingual subtitles

subtitles that translate the original audio information into a different language

NOTE: Interlingual subtitles provide a translation of the audio content into a different language, which is visually displayed to enable the understanding of the content by persons who do not understand, or have difficulties understanding, the language of the original audio content.

keyboard interface

interface used by software to obtain keystroke input

NOTE 1: A keyboard interface allows users to provide keystroke input to programs even if the native technology does not contain a keyboard.

EXAMPLE: A touchscreen PDA has a keyboard interface built into its operating system as well as a connector for external keyboards. Applications on the PDA can use the interface to obtain keyboard input either from an external keyboard or from other applications that provide simulated keyboard output, such as handwriting interpreters or speech-to-text applications with "keyboard emulation" functionality.

NOTE 2: Operation of the application (or parts of the application) through a keyboard-operated mouse emulator, such as MouseKeys, does not qualify as operation through a keyboard interface because operation of the program is through its pointing device interface, not through its keyboard interface. 

lipspeaking

a specialized communication service where a trained hearing person (a lipspeaker) silently or quietly repeats a speaker's words, reproducing the rhythm, flow, and facial expressions to make speech easy for deaf or hard-of-hearing people to follow

manual operation and control

using physical human actions to perform an operation or to exert control

NOTE: Examples of manual operation and control include, but are not limited to:

• pushing a physical button in a way that causes button travel;
• making a gesture on a touchscreen;
• grasping or pinching a physical tactile operable part in a way that will allow that tactile operable part to be physically moved or rotated in some direction;
• inserting or retrieving cards, coins, tickets, etc. into or from slots in the ICT are also examples of manual operation and control.

mechanism for private listening

auditory output designed so that only the current user can receive the sound

NOTE: Personal headsets, directional speakers and audio hoods are examples of mechanisms for private listening.

media

different specific forms of presenting information to the user

NOTE: Examples of media include, but are not limited to, text, video, audio, graphics, animations, etc.

media establishment

process of agreeing between ICT about resources and characteristics of media to be used in a communication session, so that media then can be communicated and used

menu

set of selectable options (after ISO 17549-1:2022 [i.54])

multimedia

combinations of static and/or dynamic media presented simultaneously

NOTE: Examples of multimedia include combinations of text and video, or audio and animation, etc.

non-text content

content that is not a sequence of characters that can be programmatically determined or where the sequence is not expressing something in human language (after WCAG 2.2 [4])

NOTE: An image, graphic, audio clip, or other feature that conveys meaning through either a picture or sound. Examples include: buttons, check boxes, input fields, pictures, animations, and audio/video that is embedded or streamed.

non-web document

document that is not a web page, not embedded in web pages nor used in the rendering or functioning of the page

non-web software

software that is not a web page, not embedded in web pages nor used in the rendering or functioning of the page

open functionality

functionality that supports access by assistive technology

NOTE: This is the opposite of closed functionality.

open subtitles

subtitle visually presented regardless of user preference (after ISO/IEC TS 20071-23 [i.73])

NOTE: Open subtitles cannot be turned off or moved because they are embedded in the video content.

operable part

hardware element that operates the ICT when touched or manipulated

NOTE 1: The areas of a touch screen that need to be touched for operation are operable parts.

NOTE 2: When used as a surface for non-location specific gestures, the entire touch area is considered a single operable part whose location as a whole need only be discerned.

NOTE 3: Not all operable parts are required to meet the requirements of the present document, only enough to allow full operation in one mode of operation unless otherwise stated.

NOTE 4: Under the conformance requirement in clause 14.2, not all operable parts will be expected to meet all the requirements that apply to operable parts in all contexts.

NOTE 5: Operable parts may also include slots for input of cards, coins and bills as well as slots to receive printed tickets, paper receipts and change (coins).

physical height

actual height (of a pixel or other item) in units of linear measure such as mm or inch

NOTE: See the notes below height in CSSPx for more information about physical height and height in CSSpx.

platform software (platform)

collection of software components that runs on an underlying software or hardware layer, and that provides a set of software services to other software components that allows those applications to be isolated from the underlying software or hardware layer (after ISO/IEC 13066-1 [i.18])

NOTE: A particular software component might play the role of a platform in some situations and a client in others.

primary user (of relay service)

person who is using relay services because of a disability

NOTE: See secondary user.

programmatically determinable

able to be read by software from developer-supplied data in a way that other software, including assistive technologies, can extract and present this information to users in different modalities

NOTE: WCAG 2.2 uses "determined" where this definition uses "able to be read" (to avoid ambiguity with the word "determined").

Real-Time Text (RTT)

: form of text conversation in point to point situations or in multipoint conferencing where the text being entered is sent in such a way that the communication is perceived by the user as being continuous on a character-by-character basis

NOTE 1: Users will perceive communication as continuous if the delay between text being created by the sender and received by the recipient is less than 1 s. However, the actual delay will be dependent on the communications network.

NOTE 2: The creation of text will differ between systems where text is entered on a word-by-word basis (e.g. speech‑to‑text and predictive-text based systems) and systems where each character is separately generated (e.g. typing on a physical keyboard).

NOTE 3: Although RTT may often be "perceived by the user" as being sent character-by-character, none of the RTT standards require this to be the case. They assume accumulation of characters before sending and only require that no character is held for more than 500 ms after it is created before the accumulated text is sent. An accumulation time of 300 ms or less is recommended.

NOTE 4: It is already common for autonomous ICT to be at one end of continuous bidirectional voice communication. The RTT requirements in the present document ensure that there will be RTT communication wherever there is real-time bidirectional voice communication, even when there is an autonomous ICT at one end.

relay service

electronic communication service which enables real-time bidirectional communication between remote end-users of different modes of communication

NOTE: This is typically achieved by providing conversion between different modes of communication such as text, sign, and speech, or by providing the needed cognitive support for end-users during the communication, by a human operator or automatic means.

relay service invocation functions

set of functions related to decisions, communication establishments and media interconnections between users and a relay service

satisfies a success criterion

success criterion does not evaluate to "false" when applied to the ICT (after WCAG 2.2 [4])

secondary user (of relay service)

communication user other than a primary user, participating in a communication session facilitated by a relay service that is invoked based on the primary user's preferences and actions

NOTE 1: See primary user.

NOTE 2: A secondary user may initiate or answer a communication in which a relay service is invoked by primary user's preferences or actions.

NOTE 3: A secondary user may also be another primary user participating in a communication via another relayed communication.

set of non-web documents

collection of non-web documents that share a common purpose; are created by the same author, group or organization; are published together; and all refer to each other by name or link (after WCAG2ICT [i.25])

NOTE 1: Republishing or bundling previously published documents as a collection does not constitute a set of documents.

NOTE 2: If a set is broken apart, the individual parts are no longer part of a set, and would be evaluated as any other individual document is evaluated.

single user operation

operation performed by a user and recognized by the ICT as a discrete and complete operation

NOTE: A double-click is not a single user operation.

speech output

speech received during voice communication, or spoken information originating from ICT

spoken subtitles

subtitles that are voiced over the audiovisual content (after ISO/IEC TS 20071-25 [i.32])

stationary ICT

ICT that stands directly or indirectly on the floor, or is mounted on, fully integrated into, or installed through a wall or other immovable structure, and is not intended to be moved by its user

NOTE 1: Typically, stationary ICT rests on the ground or a plinth (such as an information kiosk) or is installed in a wall (such as control panels for lifts, lighting or air-conditioning) or through a wall (such as a machine that dispenses cash or performs other banking services) or attached to a pole (such as passenger information systems) or permanently mounted on a desk (such as check-in systems).

NOTE 2: A manufacturer cannot control the third party installation of a stationary ICT but can provide installation guidance to meet requirements for reach ranges, lighting or privacy.

NOTE 3: Mounted on the wall means: the stationary ICT is protruding:

• Integrated in a wall means: the surface of the stationary ICT is nearly flush with the wall. It may be slightly recessed or protrude due to an installation frame. 
• Installed through a wall means: The main components of the ICT are installed behind a wall and only the panel of the stationary ICT is integrated in the wall. Stationary ICT integrated in or installed through a wall are often protected by a security shutter.

Sound Pressure Level (SPL)

logarithmic measure, expressed in decibels (dB), of the effective sound pressure of a sound relative to a reference value

subtitles

written text that is offered in the audiovisual content, which aims to account for (i) either the spoken words of the content, or (ii) the spoken words of the content in combination with other elements of a soundtrack

NOTE 1: When subtitles are used as an accommodation for deaf or hard of hearing users, they are also known as captions or as subtitles for the deaf and hard of hearing and also include additional information on other elements of the soundtrack needed to understand the audiovisual content.

NOTE 2: Outside North America, the term Subtitles is often used synonymously with Closed Captions. The term "Hardsubs" is sometimes used in place of Open Captions.

NOTE 3: Subtitles can appear anywhere on the display, and where possible are positioned to avoid overlapping content that needs to be visible (such as a "news ticker"), or where the background content would make the subtitles difficult to read.

NOTE 4: Subtitles may be open subtitles or closed subtitles.

tactilely discernible operable part

operable part that can be located via the sense of touch without activating it

NOTE 1: Physical properties of the tactilely discernible operable part, or its surroundings, that enable operable part to be tactilely discerned include, but are not limited to:

• some portion of the operable part being above or below the surface that surrounds it;
• the operable part having a raised feature that differentiates it from its surroundings;
• a detectable gap that surrounds the tactile part;
• having a different surface texture to surrounding surfaces;
• a part of a touchscreen being located adjacent to a tactilely discernible edge, corner, tactile markings on a screen frame;
• a touchscreen or touchpad that is tactilely discernible that is used as a whole as a gesture surface for non-location-specific gestures.

NOTE 2: The part of a touchscreen where an on-screen control is located is a tactilely discernible operable part if it is located adjacent to a tactilely discernible edge, corner, or tactile marking on a screen frame.

terminal

combination of hardware and/or software with which the end user directly interacts and that provides the user interface

NOTE 1: The hardware may consist of more than one device working together e.g. a mobile device and a computer.

NOTE 2: For some systems, the software that provides the user interface may reside on more than one device such as a telephone and a server.

NOTE 3: The software in a communications terminal is often called "communication client".

text handling capabilities

means to accept text input from and present text to a user

NOTE: This would typically be the presence of, or ability to connect, an alphanumeric keyboard and display or device which can act as an alphanumeric keyboard and display.

total conversation

bidirectional symmetric real time transfer of motion video, real-time text and voice between users in two or more locations

Uniform Resource Identifier (URI)

compact string of characters for identifying an abstract or physical resource

NOTE 1: Examples of ICT resources that can be identified by URIs are communications addresses, web pages, digital books, servers, etc.

NOTE 2: A Uniform Resource Locator (URL) is a type of URI. One example of a URL is "https://www.w3.org". When entered in the address bar of a browser, it will render the home web page of the World Wide Web Consortium.

user agent

software that retrieves and presents content for users (after WCAG 2.2 [4])

NOTE 1: Software that only displays the content contained within it is treated as software and not considered to be a user agent.

NOTE 2: An example of software that is not a user agent is a calculator application that does not retrieve the calculations from outside the software to present it to a user. In this case, the calculator software is not a user agent, it is simply software with a user interface.

NOTE 3: Software that only shows a preview of content such as a thumbnail or other non-fully functioning presentation is not providing user agent functionality.

user interface

all components of an interactive system (software or hardware) that provide information and/or controls for the user to accomplish specific tasks with the interactive system (from ISO 9241-110 [i.16])

user interface element

entity of the user interface that is presented to the user by the software (after ISO 9241 171 [i.17])

NOTE 1: This term is also known as "user interface component".

NOTE 2: User-interface elements can be interactive or not.

visiting communication client

communication client that is registered to work with a communication system that is different from the one it is currently connected to

web content

content that belongs to a web page, and that is used in the rendering or that is intended to be used in the rendering of the web page

NOTE: Web content is the text, visual or audio content that is made available online and encountered by users as part of the online usage and experience on websites. It may include text, images, sounds and audio, online videos, among other items placed within web pages.

web page

non-embedded resource obtained from a single URI using HTTP plus any other resources that are used in the rendering or intended to be rendered together with it by a user agent (after WCAG 2.2 [4])

x-height

height of the lower-case character "x" of a font in mm (for a given distance) or CSSpx

3.2 Symbols

Void.

3.3 Abbreviations

For the purposes of the present document, the following abbreviations apply:

ADA

Americans with Disabilities Act

AI

Artificial Intelligence

ALD

Assistive Listening Device

AMR-WB

Adaptive Multi-Rate WideBand

ANSI

American National Standards Institute

API

Application Programming Interface

AT

Assistive Technology

ATAG

Authoring Tool Accessibility Guidelines (of W3C^®)

ATM

Automated Teller Machine

AV

AudioVisual

CEN

Comité Européen de Normalisation

CPS

Characters Per Second

CSS

Cascading Style Sheets

DTMF

Dual Tone Multi-Frequency

EAA

European Accessibility Act (Directive (EU) 2019/882 [i.29])

EFTA

European Free Trade Area

EPG

Electronic Program Guide

EU

European Union

EVS

(Codec for) Enhanced Voice Services

FPS

Frames Per Second

GDPR

General Data Privacy Regulation

GTT

Global Text Telephony

GTT-IP

Global Text Telephony over IP

HEX

HEXadecimal

HTML

HyperText Markup Language

HTTP

HyperText Transfer Protocol

ICT

Information and Communication Technology

ID

IDentity

IETF

Internet Engineering Task Force

IMS

IP Multimedia System

IP

Internet Protocol

ISO

International Organization for Standardization

ITU-T

International Telecommunication Union - Telecommunication standardization sector

LED

Light Emitting Device

LTE

Long-Term Evolution

NAT

Network Address Translation

OCR

Optical Character Recognition

PDA

Personal Digital Assistant

PSAP

Public Safety Answering Point

QVGA

Quarter Video Graphics Array

RFC

Request For Comment

RTP

Real-Time Protocol

RTT

Real-Time Text

SIP

Session Initiation Protocol

SPL

Sound Pressure Level

TIA

Telecommunications Industry Association

UAAG

User Agent Accessibility Guidelines (of W3C)

U-C

Use Case

URI

Uniform Resource Identifier

URL

Uniform Resource Locator

USB

Universal Serial Bus

VGA

Video Graphics Array

ViLTE

Video over LTE

VoIP

Voice over Internet Protocol

VOIP

Voice Over IP

VoLTE

Voice over LTE

W3C

World Wide Web Consortium

WAI

Web Accessibility Initiative

WCAG

Web Content Accessibility Guidelines (of W3C)

WLAN

Wireless Local Access Network

XAML

eXtensible Application Markup Language

XML

eXtensible Markup Language

XUL

XML User interface Language