EN 301 549 V2.1.2 (2018-08)

HARMONISED EUROPEAN STANDARD

Accessibility requirements for ICT products and services

2
EN 301 549 V2.1.2 (2018-08)

Reference
REN/HF-00 301 549

Keywords
accessibility, HF, ICT, procurement

CEN

CENELECETSI

Rue de la science, 23
B-1040 Brussels- BELGIUM

Rue de la science, 23
B-1040 Brussels- BELGIUM

650 Route des Lucioles
F-06921 Sophia Antipolis Cedex FRANCE

Tel: + 32 2 550 08 11
Fax: + 32 2 550 08 19

Tel.: +32 2 519 68 71
Fax: +32 2 519 69 19

Tel.: +33 4 92 94 42 00
Fax: +33 4 93 65 47 16
Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à laSous-Préfecture de Grasse (06) N° 7803/88

Important notice
Individual copies of the present document can be downloaded from:ETSI Search & Browse Standards
The present document may be made available in more than one electronic version or in print. In any case of existing orperceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In
case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
ETSI deliverable status
If you find errors in the present document, please send your comment to one of the following services:
ETSI Committee Support Staff

Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 2018.
© Comité Européen de Normalisation 2018.
© Comité Européen de Normalisation Electrotechnique 2018.
All rights reserved.
DECTTM, PLUGTESTSTM, UMTSTM and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.
3GPPTM and LTE™ are trademarks of ETSI registered for the benefit of its Members andof the 3GPP Organizational Partners.
oneM2M logo is protected for the benefit of its Members.
GSM® and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI

3
EN 301 549 V2.1.2 (2018-08)

Contents
Contents .............................................................................................................................................................. 3Intellectual Property Rights ................................................................................................................................ 8
Foreword............................................................................................................................................................. 8
Modal verbs terminology ................................................................................................................................... 9
Introduction ........................................................................................................................................................ 9
1

Scope ...................................................................................................................................................... 10

2

References .............................................................................................................................................. 10

2.1
2.2

3
3.1
3.2

4
4.1
4.2
4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
4.2.6
4.2.7
4.2.8
4.2.9
4.2.104.2.11

5
5.1
5.1.1
5.1.2
5.1.3
5.1.4
5.1.5
5.1.6
5.2
5.3
5.4
5.5
5.5.1
5.5.2
5.6
5.6.1
5.6.2
5.7
5.8
5.9

6
6.1
6.2
6.2.1

Normative references ....................................................................................................................................... 10
Informative references ..................................................................................................................................... 11

Definitions and abbreviations................................................................................................................. 13
Definitions ....................................................................................................................................................... 13
Abbreviations ................................................................................................................................................... 16

Functional performance.......................................................................................................................... 17
Meeting functional performance statements .................................................................................................... 17
Functional performance statements ................................................................................................................. 17
Usage without vision .................................................................................................................................. 17
Usage with limited vision ........................................................................................................................... 17
Usage without perception of colour ........................................................................................................... 18
Usage without hearing ................................................................................................................................ 18
Usage with limited hearing ........................................................................................................................ 18
Usage without vocal capability .................................................................................................................. 18
Usage with limited manipulation or strength ............................................................................................. 18
Usage with limited reach ............................................................................................................................ 18
Minimize photosensitive seizure triggers ................................................................................................... 19
Usage with limited cognition ..................................................................................................................... 19
Privacy ....................................................................................................................................................... 19

Generic requirements ............................................................................................................................. 20
Closed functionality ......................................................................................................................................... 20
Introduction (informative) .......................................................................................................................... 20
General ....................................................................................................................................................... 20
Non-visual access ....................................................................................................................................... 20
Functionality closed to text enlargement .................................................................................................... 23
Visual output for auditory information....................................................................................................... 24
Operation without keyboard interface ........................................................................................................ 24
Activation of accessibility features .................................................................................................................. 25
Biometrics ........................................................................................................................................................ 25
Preservation of accessibility information during conversion ........................................................................... 25
Operable parts .................................................................................................................................................. 25
Means of operation ..................................................................................................................................... 25
Operable parts discernibility ...................................................................................................................... 25
Locking or toggle controls ............................................................................................................................... 25
Tactile or auditory status ............................................................................................................................ 25
Visual status ............................................................................................................................................... 26
Key repeat ........................................................................................................................................................ 26
Double-strike key acceptance .......................................................................................................................... 26
Simultaneous user actions ................................................................................................................................ 26

ICT with two-way voice communication ............................................................................................... 27
Audio bandwidth for speech ............................................................................................................................ 27
Real-time text (RTT) functionality .................................................................................................................. 27
RTT provision ............................................................................................................................................ 27

ETSI

4
EN 301 549 V2.1.2 (2018-08)

6.2.2
6.2.3
6.2.4
6.3
6.4
6.5
6.5.1
6.5.2
6.5.3
6.5.4
6.6

7
7.1
7.1.1
7.1.2
7.1.3
7.2
7.2.1
7.2.2
7.2.3
7.3

8
8.1
8.1.1
8.1.2
8.1.3
8.2
8.2.1
8.2.2
8.3
8.3.1
8.3.2
8.3.3
8.3.4
8.3.5
8.4
8.4.1
8.4.2
8.4.3
8.5

9
9.0
9.1
9.1.1
9.1.2
9.1.3
9.1.4
9.2
9.2.1
9.2.2
9.2.3
9.2.4
9.2.5
9.3
9.3.1
9.3.2
9.3.3
9.4

Display of Real-time Text .......................................................................................................................... 27
Interoperability ........................................................................................................................................... 28
Real-time text responsiveness .................................................................................................................... 28
Caller ID .......................................................................................................................................................... 28
Alternatives to voice-based services ................................................................................................................ 28
Video communication ...................................................................................................................................... 28
General (informative) ................................................................................................................................. 28
Resolution .................................................................................................................................................. 29
Frame rate .................................................................................................................................................. 29
Synchronization between audio and video ................................................................................................. 29
Alternatives to video-based services ................................................................................................................ 29

ICT with video capabilities .................................................................................................................... 30
Caption processing technology ........................................................................................................................ 30
Captioning playback ................................................................................................................................... 30
Captioning synchronization........................................................................................................................ 30
Preservation of captioning .......................................................................................................................... 30
Audio description technology .......................................................................................................................... 30
Audio description playback ........................................................................................................................ 30
Audio description synchronization ............................................................................................................. 30
Preservation of audio description ............................................................................................................... 30
User controls for captions and audio description ............................................................................................. 31

Hardware ................................................................................................................................................ 32
General............................................................................................................................................................. 32
Generic requirements ................................................................................................................................. 32
Standard connections.................................................................................................................................. 32
Colour......................................................................................................................................................... 32
Hardware products with speech output ............................................................................................................ 32
Speech volume gain ................................................................................................................................... 32
Magnetic coupling ...................................................................................................................................... 32
Physical access to ICT ..................................................................................................................................... 33
General (informative) ................................................................................................................................. 33
Clear floor or ground space ........................................................................................................................ 33
Reach range for ICT ................................................................................................................................... 36
Visibility..................................................................................................................................................... 38
Installation instructions .............................................................................................................................. 38
Mechanically operable parts ............................................................................................................................ 38
Numeric keys ............................................................................................................................................. 38
Operation of mechanical parts .................................................................................................................... 39
Keys, tickets and fare cards ........................................................................................................................ 39
Tactile indication of speech mode ................................................................................................................... 39

Web ........................................................................................................................................................ 40
General (informative) ...................................................................................................................................... 40
Perceivable....................................................................................................................................................... 41
Text alternatives ......................................................................................................................................... 41
Time-based media ...................................................................................................................................... 41
Adaptable ................................................................................................................................................... 41
Distinguishable ........................................................................................................................................... 42
Operable........................................................................................................................................................... 43
Keyboard accessible ................................................................................................................................... 43
Enough time ............................................................................................................................................... 43
Seizures and physical reactions .................................................................................................................. 43
Navigable ................................................................................................................................................... 43
Input modalities .......................................................................................................................................... 44
Understandable ................................................................................................................................................ 44
Readable ..................................................................................................................................................... 44
Predictable .................................................................................................................................................. 44
Input assistance .......................................................................................................................................... 45
Robust .............................................................................................................................................................. 45

ETSI

5
EN 301 549 V2.1.2 (2018-08)

9.4.1
9.5

10
10.0
10.1
10.1.110.1.210.1.310.1.410.2
10.2.110.2.210.2.310.2.410.2.510.3
10.3.1
10.3.210.3.310.4
10.4.1
10.5
10.6

11
11.0
11.1
11.1.111.1.2
11.1.311.1.411.2
11.2.111.2.211.2.311.2.411.2.511.3
11.3.1
11.3.211.3.311.4
11.4.1
11.5
11.5.1
11.5.2
11.6
11.6.1
11.6.2
11.7
11.8
11.8.1
11.8.211.8.311.8.411.8.512
12.1
12.1.1Compatible ................................................................................................................................................. 45
WCAG conformance requirements .................................................................................................................. 45

Non-web documents............................................................................................................................... 47
General (informative) ...................................................................................................................................... 47
Perceivable....................................................................................................................................................... 47
Text alternatives ......................................................................................................................................... 47
Time-based media ...................................................................................................................................... 47
Adaptable ................................................................................................................................................... 48
Distinguishable ........................................................................................................................................... 49
Operable........................................................................................................................................................... 50
Keyboard accessible ................................................................................................................................... 50
Enough time ............................................................................................................................................... 51
Seizures and physical reactions .................................................................................................................. 52
Navigable ................................................................................................................................................... 52
Input modalities .......................................................................................................................................... 53
Understandable ................................................................................................................................................ 54
Readable ..................................................................................................................................................... 54
Predictable .................................................................................................................................................. 55
Input assistance .......................................................................................................................................... 55
Robust .............................................................................................................................................................. 56
Compatible ................................................................................................................................................. 56
Caption positioning .......................................................................................................................................... 56
Audio description timing ................................................................................................................................. 57

Software ................................................................................................................................................. 57
General (informative) ...................................................................................................................................... 57
Perceivable....................................................................................................................................................... 58
Text alternatives ......................................................................................................................................... 58
Time-based media ...................................................................................................................................... 58
Adaptable ................................................................................................................................................... 59
Distinguishable ........................................................................................................................................... 61
Operable........................................................................................................................................................... 63
Keyboard accessible ................................................................................................................................... 63
Enough time ............................................................................................................................................... 64
Seizures and physical reactions .................................................................................................................. 65
Navigable ................................................................................................................................................... 66
Input modalities .......................................................................................................................................... 66
Understandable ................................................................................................................................................ 67
Readable ..................................................................................................................................................... 67
Predictable .................................................................................................................................................. 68
Input assistance .......................................................................................................................................... 68
Robust .............................................................................................................................................................. 69
Compatible ................................................................................................................................................. 69
Interoperability with assistive technology ....................................................................................................... 70
Closed functionality ................................................................................................................................... 70
Accessibility services ................................................................................................................................. 70
Documented accessibility usage ...................................................................................................................... 74
User control of accessibility features ......................................................................................................... 74
No disruption of accessibility features ....................................................................................................... 74
User preferences .............................................................................................................................................. 74
Authoring tools ................................................................................................................................................ 74
Content technology .................................................................................................................................... 74
Accessible content creation ........................................................................................................................ 74
Preservation of accessibility information in transformations ..................................................................... 74
Repair assistance ........................................................................................................................................ 74
Templates ................................................................................................................................................... 75

Documentation and support services ...................................................................................................... 76
Product documentation .................................................................................................................................... 76
Accessibility and compatibility features .................................................................................................... 76

ETSI

6
EN 301 549 V2.1.2 (2018-08)

12.1.212.2
12.2.112.2.212.2.312.2.413
13.1
13.1.113.1.213.1.313.1.413.1.513.1.6
13.2
13.3

Accessible documentation .......................................................................................................................... 76
Support services ............................................................................................................................................... 76
General (informative) ................................................................................................................................. 76
Information on accessibility and compatibility features ............................................................................. 76
Effective communication ........................................................................................................................... 76
Accessible documentation .......................................................................................................................... 77

ICT providing relay or emergency service access.................................................................................. 78
Relay services requirements ............................................................................................................................ 78
General (informative) ................................................................................................................................. 78
Text relay services ...................................................................................................................................... 78
Sign relay services ...................................................................................................................................... 78
Lip-reading relay services .......................................................................................................................... 78
Captioned telephony services ..................................................................................................................... 78
Speech to speech relay services.................................................................................................................. 78
Access to relay services ................................................................................................................................... 78
Access to emergency services .......................................................................................................................... 79

Annex A (informative): Relationship between the present document and the essential requirements of
Directive 2016/2102 ............................................................................................................................... 80
Annex B (informative): Relationship between requirements and functional performance statements ............ 88
B.1

Relationships between clauses 5 to 13 and the functional performance statements ........................................ 88

Annex C (normative): Determination of compliance ....................................................................................... 96
C.1
C.2
C.3
C.4
C.5
C.5.1
C.5.2
C.5.3
C.5.4
C.5.5
C.5.6
C.5.7
C.5.8
C.5.9
C.6
C.6.1
C.6.2
C.6.3
C.6.4
C.6.5
C.6.6
C.7
C.7.1
C.7.2
C.7.3
C.8
C.8.1
C.8.2
C.8.3
C.8.4
C.8.5
C.9
C.9.0
C.9.1
C.9.2
C.9.3

Introduction...................................................................................................................................................... 96
Empty clause .................................................................................................................................................... 96
Empty clause .................................................................................................................................................... 97
Functional performance ................................................................................................................................... 97
Generic requirements ....................................................................................................................................... 97
Closed functionality ................................................................................................................................... 97
Activation of accessibility features .......................................................................................................... 101
Biometrics ................................................................................................................................................ 101
Preservation of accessibility information during conversion ................................................................... 101
Operable parts .......................................................................................................................................... 102
Locking or toggle controls ....................................................................................................................... 102
Key repeat ................................................................................................................................................ 102
Double-strike key acceptance ................................................................................................................... 103
Simultaneous user actions ........................................................................................................................ 103
ICT with two-way voice communication....................................................................................................... 103
Audio bandwidth for speech .................................................................................................................... 103
Real-Time Text (RTT) functionality ........................................................................................................ 103
Caller ID ................................................................................................................................................... 105
Alternatives to voice-based services ........................................................................................................ 105
Video communication .............................................................................................................................. 106
Alternatives to video-based services ........................................................................................................ 106
ICT with video capabilities ............................................................................................................................ 106
Caption processing technology ................................................................................................................ 106
Audio description technology .................................................................................................................. 107
User controls for captions and audio description ..................................................................................... 107
Hardware ....................................................................................................................................................... 108
General ..................................................................................................................................................... 108
Hardware products with speech output .................................................................................................... 108
Physical access to ICT.............................................................................................................................. 109
Mechanically operable parts ..................................................................................................................... 113
Tactile indication of speech mode ............................................................................................................ 114
Web ................................................................................................................................................................ 114
General (informative) ............................................................................................................................... 114
Perceivable ............................................................................................................................................... 114
Operable ................................................................................................................................................... 117
Understandable ......................................................................................................................................... 120

ETSI

7
EN 301 549 V2.1.2 (2018-08)

C.9.4
C.9.5
C.10
C.10.0C.10.1
C.10.2C.10.3C.10.4C.10.5C.10.6
C.11
C.11.0C.11.1C.11.2C.11.3C.11.4C.11.5C.11.6C.11.7C.11.8
C.12
C.12.1C.12.2C.13
C.13.1C.13.2C.13.3

Robust ...................................................................................................................................................... 122
WCAG 2.1 conformance requirements .................................................................................................... 122
Non-web documents ...................................................................................................................................... 122
General (informative) ............................................................................................................................... 122
Perceivable ............................................................................................................................................... 123
Operable ................................................................................................................................................... 126
Understandable ......................................................................................................................................... 129
Robust ...................................................................................................................................................... 130
Caption positioning .................................................................................................................................. 130
Audio description timing .......................................................................................................................... 130
Software ......................................................................................................................................................... 130
General ..................................................................................................................................................... 130
Perceivable ............................................................................................................................................... 131
Operable ................................................................................................................................................... 136
Understandable ......................................................................................................................................... 139
Robust ...................................................................................................................................................... 141
Interoperability with assistive technology ................................................................................................ 141
Documented accessibility usage ............................................................................................................... 146
User preferences ....................................................................................................................................... 146
Authoring tools......................................................................................................................................... 147
Documentation and support services ............................................................................................................. 148
Product documentation ............................................................................................................................. 148
Support services ....................................................................................................................................... 148
ICT providing relay or emergency service access ......................................................................................... 149
Relay service requirements ...................................................................................................................... 149
Access to relay services ............................................................................................................................ 150
Access to emergency services .................................................................................................................. 150

Annex D (informative): WCAG 2.1 AAA Success Criteria........................................................................... 151
History ............................................................................................................................................................ 152

ETSI

8
EN 301 549 V2.1.2 (2018-08)

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 foundin 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/).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys noright to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.

Foreword
This Harmonised European Standard (EN) has been produced by ETSI Technical Committee Human Factors (HF), andthe eAccessibility Joint Working Group (JWG) of CEN/CENELEC/ETSI.
The present document has been prepared under the Commission's standardisation request C(2017) 2585 final [i.27] toprovide one voluntary means of conforming to the essential requirements of Directive 2016/2102 [i.28] on theaccessibility of the websites and mobile applications of public sector bodies.
Once the present document is cited in the Official Journal of the European Union under that Directive, compliance with
the normative clauses of the present document given in tables A.1 and A.2 confers, within the limits of the scope of thepresent document, a presumption of conformity with the corresponding essential requirements of that Directive andassociated EFTA regulations.
The present document has been developed from ETSI EN 301 549 [i.29] V1.1.2 (2015-04). The changes are limited tothose necessary to comply with the requirements of a Harmonised Standard, inclusion of requirements for mobile
applications, updating to reflect the state of the art in W3C WCAG, updating of clause 6.1, and corrections of errors.

National transposition dates
Date of adoption of this EN:

24 August 2018

Date of latest announcement of this EN (doa):

30 November 2018

Date of latest publication of new National Standard
or endorsement of this EN (dop/e):

31 May 2019

Date of withdrawal of any conflicting National Standard (dow):

31 May 2020

ETSI

9
EN 301 549 V2.1.2 (2018-08)

Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "may not", "need", "need not", "will","will not", "can" and "cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms
for the expression of provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.

Introduction
The present document is developed in response to standardisation request M 554 from the European Commission to
CEN, CENELEC and ETSI. It is based on the European Standard (EN) that was one of several deliverables prepared in
response to Phase 2 of Mandate M 376 [i.3].
NOTE:

The present document reflects the content of the W3C WCAG 2.1 Proposed Recommendation [5], whichis expected to become the formal W3C WCAG 2.1 Recommendation.

The primary objective of Mandate M 376 was to produce a European Standard that sets out in a single source, detailed,practical and quantifiable functional accessibility requirements that take note of global initiatives in that field and which
are applicable to all Information and Communication Technology (ICT) products and services identified in Phase I of
the Mandate (ETSI TR 102 612 [i.9]) and usable in public procurement.
The European Standard prepared in response to Mandate M 376 is supported by three Technical Reports. The first(ETSI TR 101 550 [i.7]) lists the standards and technical specifications used in the creation of the compliancerequirements for accessibility set out in the European Standard. The second Technical Report (ETSI TR 101 551 [i.8])
gives guidance to procurers on the award criteria relevant to each of the accessibility-related needs of ICT users in the
products and services under consideration. The third Technical Report (ETSI TR 101 552 [i.30]) incorporates all
information and documentation needed in the framework of the procurement process in order to allow conveying theassessment of accessibility via conformity with the functional accessibility requirements contained in the present
document and with award criteria.

ETSI

10
EN 301 549 V2.1.2 (2018-08)

1

Scope

The present document specifies the functional accessibility requirements applicable to ICT products and services,
together with a description of the test procedures and evaluation methodology for each accessibility requirement in aform that is suitable for use in public procurement within Europe . The present document might be useful for otherpurposes such as procurement in the private sector.
The relationship between the present document and the essential requirements of Directive 2016/2102 on theaccessibility of the websites and mobile applications of public sector bodies [i.28] is given in Annex A.
The present document contains the necessary functional requirements and provides a reference document such that if
procedures are followed by different actors, the results of testing are similar and the interpretation of those results isclear. The test descriptions and evaluation methodology included in the present document are elaborated to a level ofdetail compliant with ISO/IEC 17007:2009 [i.14], so that conformance testing can give conclusive results.
All clauses except those in clause 12, related to documentation and support services, are self-scoping. This means they
are introduced with the phrase 'Where ICT <pre-condition>'. Compliance is achieved either when the pre-condition istrue and the corresponding test (in Annex C) is passed, or when the pre-condition is false (i.e. the pre-condition is not
met or not valid).
NOTE 1: Compliance issues are covered in normative clause C.1.
The inherent nature of certain situations makes it impossible to make reliable and definitive statements that accessibility
requirements have been met. In those situations therefore, the requirements in the present document are not applicable:•

when the product is in a failure, repair or maintenance state where the ordinary set of input or output functions
are not available;•

during those parts of start-up, shutdown, and other state transitions that can be completed without userinteraction.

NOTE 2: Even in the above situations, it is best practice to apply requirements in the present document wherever it
is feasible and safe to do so.

2

References

2.1

Normative references

References are specific, identified by date of publication and/or edition number or version number. Only the citedversion applies.
Referenced documents which are not found to be publicly available in the expected location might be found at ETSI
References in docbox.
NOTE:

While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.

The following referenced documents are necessary for the application of the present document.
[1]

ETSI ETS 300 381 (Edition 1) (December 1994): "Telephony for hearing impaired people;
Inductive coupling of telephone earphones to hearing aids".

[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".

ETSI

11
EN 301 549 V2.1.2 (2018-08)

[4]
NOTE:
[5]
NOTE:

2.2

W3C Recommendation (December 2008) /ISO/IEC 40500:2012: "Web Content Accessibility
Guidelines (WCAG) 2.0".
Available at WCAG 2.0.
W3C Proposed Recommendation (June 2018): "Web Content Accessibility Guidelines (WCAG)
2.1".
Available at WCAG 2.1.

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 thereferenced document (including any amendments) applies.
NOTE:

While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.

The following referenced documents are not necessary for the application of the present document but they assist theuser with regard to a particular subject area.
[i.1]

ANSI/IEEE C63.19 (2011): "American National Standard Method of Measurement ofCompatibility between Wireless Communication Devices and Hearing Aids".

[i.2]

ANSI/TIA-4965: "Receive volume control requirements for digital and analogue wireline
terminals".

[i.3]

European Commission M 376-EN: "Standardization Mandate to CEN, CENELEC and ETSI in
support of European accessibility requirements for public procurement of products and services in
the ICT domain".

[i.4]

ETSI EG 201 013: "Human Factors (HF); Definitions, abbreviations and symbols".

[i.5]

ETSI ES 202 975: "Human Factors (HF); Requirements for relay services".

[i.6]

ETSI ETS 300 767: "Human Factors (HF); Telephone Prepayment Cards; Tactile Identifier".

[i.7]

ETSI CEN/CENELEC/ETSI TR 101 550: "Documents relevant to EN 301 549 "Accessibility
requirements suitable for public procurement of ICT products and services in Europe"".

[i.8]

ETSI CEN/CENELEC/ETSI TR 101 551: "Guidelines on the use of accessibility award criteria
suitable for publicly procured ICT products and services in Europe".

[i.9]

ETSI TR 102 612: "Human Factors (HF); European accessibility requirements for public
procurement of products and services in the ICT domain (European Commission Mandate M 376,
Phase 1)".

[i.10]ETSI TS 126 114: "Universal Mobile Telecommunications System (UMTS); LTE; IP Multimedia
Subsystem (IMS); Multimedia telephony; Media handling and interaction (3GPP TS 26.114)".

[i.11]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.12]ETSI TS 134 229: "Universal Mobile Telecommunications System (UMTS); LTE; Internet
Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) andSession Description Protocol (SDP); User Equipment (UE) conformance specification (3GPP
TS 34.229)".

[i.13]IETF RFC 4103 (2005): "RTP Payload for Text Conversation".

ETSI

12
EN 301 549 V2.1.2 (2018-08)[i.14]

ISO/IEC 17007:2009: "Conformity assessment - Guidance for drafting normative documents
suitable for use for conformity assessment".

[i.15]

ISO 9241-11:1998: "Ergonomic requirements for office work with visual display terminals(VDTs) -- Part 11: Guidance on usability".

[i.16]

ISO 9241-110:2006: "Ergonomics of human-system interaction -- Part 110: Dialogue principles".

[i.17]

ISO 9241-171:2008: "Ergonomics of human-system interaction-Part 171: Guidance on software
accessibility".

[i.18]

ISO 26800:2011: "Ergonomics - General approach, principles and concepts".

[i.19]

ISO/IEC 13066-1:2011: "Information technology - Interoperability with assistive technology (AT)- Part 1: Requirements and recommendations for interoperability".

[i.20]

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.21]

Recommendation ITU-T G.722 (1988): "7 kHz audio-coding within 64 kbit/s".

[i.22]

Recommendation ITU-T G.722.2 (2003): "Wideband coding of speech at around 16 kbit/s using
Adaptive Multi-Rate Wideband (AMR-WB)".

[i.23]

Recommendation ITU-T V.18 (2000): "Operational and interworking requirements for DCEs
operating in the text telephone mode".

[i.24]

TIA-1083-A (2010): "Telecommunications; Telephone Terminal equipment; Handset magnetic
measurement procedures and performance requirements".

[i.25]US Department of Justice: "2010 ADA Standards for Accessible Design".

[i.26]

W3C Working Group Note 5 September 2013: "Guidance on Applying WCAG 2.0 to Non-Web
Information and Communications Technologies (WCAG2ICT)".

NOTE:

Available at http://www.w3.org/TR/wcag2ict/.

[i.27]

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 Parliamentand of the Council on the accessibility of the websites and mobile applications of public sector
bodies.

[i.28]

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.29]ETSI EN 301 549 (V1.1.2) (04-2015): "Accessibility requirements suitable for public procurementof ICT products and services in Europe".

[i.30]ETSI TR 101 552: "Guidance for the application of conformity assessment to accessibility
requirements for public procurement of ICT products and services in Europe".

ETSI

13
EN 301 549 V2.1.2 (2018-08)

3

Definitions and abbreviations

3.1

Definitions

For the purposes of the present document, the terms and definitions given in ETSI EG 201 013 [i.4] and the following
apply:
accessibility: extent to which products, systems, services, environments and facilities can be used by people from a
population with the widest range of characteristics and capabilities, to achieve a specified goal in a specified context ofuse (from ISO 26800 [i.18])
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 otherproducts and services with which the ICT may interact.
assistive technology: hardware or software added to or connected to a system that increases accessibility for anindividual
NOTE 1: Examples are Braille displays, screen readers, screen magnification software and eye tracking devices thatare added to the ICT.
NOTE 2: Where ICT does not support directly connected assistive technology, but which can be operated by asystem 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: additional audible narrative, interleaved with the dialogue, which describes the significant aspectsof the visual content of audio-visual media that cannot be understood from the main soundtrack alone
NOTE:

This is also variously described using terms such as "video description" or variants such as "descriptive
narration".

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.
caption: synchronized visual and/or text alternative for both speech and non-speech audio information needed tounderstand the media content (after WCAG 2.1 [5])NOTE:This is also variously described using terms such as "subtitles" or variants such as "subtitles for the deaf
and hard-of-hearing".

closed functionality: functionality that is limited by characteristics that prevent a user from attaching, installing or
using assistive technology
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.26])
NOTE:

Content occurs in three places: web pages, documents and software. When content occurs in a web pageor a 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 tocommunicate the content's information and sensory experience to the user - the software itself performs
that function.

context of use: users, tasks, equipment (hardware, software and materials), and the physical and social environments inwhich a product is used (from ISO 9241-11 [i.15])

ETSI

14
EN 301 549 V2.1.2 (2018-08)

document: logically distinct assembly of content (such as a file, set of files, or streamed media) that functions as asingle entity rather than a collection, that is not part of software and that does not include its own user agent. (after
WCAG2ICT [i.26])
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 "informationand sensory experience to be communicated to the user" from such files, it is just another part of thecontent 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 notproviding 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, closed caption text etc.
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, captions 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.
ICT network: technology and resources supporting the connection and operation of interconnected ICT
Information and Communication Technology (ICT): technology, equipment, or interconnected system or subsystemof equipment for which the principal function is the creation, conversion, duplication, automatic acquisition, storage,
analysis, evaluation, manipulation, management, movement, control, display, switching, interchange, transmission,
reception, or broadcast of data or information
NOTE:

Examples of ICT are web pages, electronic content, telecommunications products, computers andancillary equipment, software including mobile applications, information kiosks and transaction
machines, videos, IT services, and multifunction office machines which copy, scan, and fax documents.

mechanically operable part: operable part that has a mechanical interface to activate, deactivate, or adjust the ICT
NOTE:

Examples of mechanically operable parts include scanner covers, notebook docking stations and lids aswell as physical switches and latches.

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.

non-text content: content that is not a sequence of characters that can be programmatically determined or where thesequence is not expressing something in human language (after WCAG 2.1 [5])non-web document: document that is not a web page, not embedded in web pages nor used in the rendering orfunctioning of the page
non-web software: software that is not a web page, not embedded in web pages nor used in the rendering orfunctioning of the page

ETSI

15
EN 301 549 V2.1.2 (2018-08)

open functionality: functionality that supports access by assistive technology
NOTE:

This is the opposite of Closed Functionality.

operable part: component of ICT used to activate, deactivate, or adjust the ICTNOTE:Operable parts can be provided in either hardware (see mechanically operable parts, above) or software.
An on-screen button is an example of an operable part provided by software.

platform software: collection of software components that runs on an underlying software or hardware layer, and thatprovides a set of software services to other software components that allows those applications to be isolated from theunderlying software or hardware layer (after ISO/IEC 13066-1 [i.19])
NOTE:

A particular software component might play the role of a platform in some situations and a client inothers.

programmatically determinable: able to be read by software from developer-supplied data in a way that othersoftware, including assistive technologies, can extract and present this information to users in different modalities
NOTE:

WCAG 2.1 uses "determined" where this definition uses "able to be read" (to avoid ambiguity with theword "determined").

real-time text: form of a 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
satisfies a success criterion: success criterion does not evaluate to "false" when applied to the ICT(after WCAG 2.1 [5])terminal: combination of hardware and/or software with which the end user directly interacts and that provides the userinterface
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 suchas a telephone and a server.
user agent: software that retrieves and presents content for users (after WCAG 2.1 [5])NOTE 1: Software that only displays the content contained within it is treated as software and not considered to bea user agent.
NOTE 2: An example of software that is not a user agent is a calculator application that does not retrieve thecalculations from outside the software to present it to a user. In this case, the calculator software is not auser 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.
web content: content that belongs to a web page, and that is used in the rendering or that is intended to be used in therendering of the web page
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.1 [5])

ETSI

16
EN 301 549 V2.1.2 (2018-08)

3.2

Abbreviations

For the purposes of the present document, the following abbreviations apply:
ADA
ANSI
AT
CIF
CSS
DOM
EU
FPS
FXML
HTML
HTTP
ICT
IETF
IMS
IP
JWG
ODF
OOXML
PSTN
QCIF
RFC
RTT
SC
SIP
URI
USB
VoIP
W3C
WCAG
XML
XUL

Americans with Disabilities Act
American National Standards Institute
Assistive Technology
Common Intermediate Format
Cascading Style Sheets
Document Object Model
European Union
Frames Per Second
XML-based user interface markup language
HyperText Markup Language
HyperText Transfer Protocol
Information and Communication Technology
Internet Engineering Task Force
IP Multimedia System
Internet Protocol
Joint Working Group (of CEN/CENELEC/ETSI)Open Document Format
Office Open eXtensible Markup Language
Public Switched Telephone Network
Quarter Common Intermediate Format
Request For Comment
Real-Time Text
Success Criterion
Session Initiation Protocol
Uniform Resource Identifier
Universal Serial Bus
Voice over IP
World Wide Web Consortium
Web Content Accessibility Guidelines (of W3C)
eXtensible Markup Language
XML User interface Language

ETSI

17
EN 301 549 V2.1.2 (2018-08)

4Functional performance

4.1

Meeting functional performance statements

The statements set out in clause 4.2 are intended to describe the functional performance of ICT enabling people tolocate, identify, and operate ICT functions, and to access the information provided, regardless of physical, cognitive or
sensory abilities. Any ability impairments may be permanent, temporary or situational.
ICT meeting the applicable requirements of clauses 5 to 13 is deemed to have met a level of accessibility conformant
with the present document and consistent with the user accessibility needs identified in clause 4.2 (Functional
performance statements).
NOTE 1: The relationship between the requirements from clauses 5 to 13 and the accessibility-related user needs is
set out in Annex B.
NOTE 2: The intent of clause 4.2 is to describe the users' accessibility needs in accessing the full functionality anddocumentation of the product or the service with or without the use of assistive technologies.
NOTE 3: The methods of meeting the accessibility needs of users with multiple impairments will depend on thespecific combination of impairments. Meeting these user accessibility needs may be addressed byconsidering multiple clauses in clause 4.2.
NOTE 4: Several users' accessibility needs rely on ICT providing specific modes of operation. If a user is toactivate, engage or switch to the mode that complies with his or her user accessibility needs, the method
for activating, engaging or switching to that mode is also expected to comply with the same user
accessibility needs.

4.2

Functional performance statements

4.2.1

Usage without vision

Where ICT provides visual modes of operation, some users need ICT to provide at least one mode of operation that
does not require vision.
NOTE 1: A web page or application with a well formed semantic structure can allow users without vision to
identify, navigate and interact with a visual user interface.
NOTE 2: Audio and tactile user interfaces may contribute towards meeting this clause.

4.2.2

Usage with limited vision

Where ICT provides visual modes of operation, some users will need the ICT to provide features that enable users tomake better use of their limited vision.
NOTE 1: Magnification, reduction of required field of vision and control of contrast, brightness and intensity cancontribute towards meeting this clause.
NOTE 2: Where significant features of the user interface are dependent on depth perception, the provision of
additional methods of distinguishing between the features may contribute towards meeting this clause.
NOTE 3: Users with limited vision may also benefit from non-visual access (see clause 4.2.1).

ETSI

18
EN 301 549 V2.1.2 (2018-08)

4.2.3

Usage without perception of colour

Where ICT provides visual modes of operation, some users will need the ICT to provide a visual mode of operation that
does not require user perception of colour.
NOTE:

4.2.4

Where significant features of the user interface are colour-coded, the provision of additional methods of
distinguishing between the features may contribute towards meeting this clause.

Usage without hearing

Where ICT provides auditory modes of operation, some users need ICT to provide at least one mode of operation that
does not require hearing.
NOTE:

4.2.5

Visual and tactile user interfaces may contribute towards meeting this clause.

Usage with limited hearing

Where ICT provides auditory modes of operation, some users will need the ICT to provide enhanced audio features.
NOTE 1: Enhancement of the audio clarity, reduction of background noise, increased range of volume and greater
volume in the higher frequency range can contribute towards meeting this clause.
NOTE 2: Users with limited hearing may also benefit from non-hearing access (see clause 4.2.4).

4.2.6

Usage without vocal capability

Where ICT requires vocal input from users, some users will need the ICT to provide at least one mode of operation that
does not require them to generate vocal output.
NOTE 1: This clause covers the alternatives to the use of orally-generated sounds, including speech, whistles,
clicks, etc.
NOTE 2: Keyboard, pen or touch user interfaces may contribute towards meeting this clause.

4.2.7

Usage with limited manipulation or strength

Where ICT requires manual actions, some users will need the ICT to provide features that enable users to make use of
the ICT through alternative actions not requiring manipulation or hand strength.
NOTE 1: Examples of operations that users may not be able to perform include those that require fine motor
control, path dependant gestures, pinching, twisting of the wrist, tight grasping, or simultaneous manual
actions.
NOTE 2: One-handed operation, sequential key entry and speech user interfaces may contribute towards meeting
this clause.
NOTE 3: Some users have limited hand strength and may not be able to achieve the level of strength to perform an
operation. Alternative user interface solutions that do not require hand strength may contribute towards
meeting this clause.

4.2.8

Usage with limited reach

Where ICT products are free-standing or installed, the operational elements will need to be within reach of all users.
NOTE:

Considering the needs of wheelchair users and the range of user statures in the placing of operational
elements of the user interface may contribute towards meeting this clause.

ETSI

19
EN 301 549 V2.1.2 (2018-08)

4.2.9

Minimize photosensitive seizure triggers

Where ICT provides visual modes of operation, some users need ICT to provide at least one mode of operation thatminimizes the potential for triggering photosensitive seizures.
NOTE:

4.2.10Limiting the area and number of flashes per second may contribute towards meeting this clause.

Usage with limited cognition

Some users will need the ICT to provide features that make it simpler and easier to use.
NOTE 1: This clause is intended to include the needs of persons with limited cognitive, language and learning
abilities.
NOTE 2: Adjustable timings, error indication and suggestion, and a logical focus order are examples of design
features that may contribute towards meeting this clause.

4.2.11

Privacy

Where ICT provides features that are provided for accessibility, some users will need their privacy to be maintained
when using those ICT features that are provided for accessibility.
NOTE:

Enabling the connection of personal headsets for private listening, not providing a spoken version ofcharacters being masked and enabling user control of legal, financial and personal data are examples ofdesign features that may contribute towards meeting this clause.

ETSI

20
EN 301 549 V2.1.2 (2018-08)

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 beclosed because the product is self-contained and users are precluded from adding peripherals or software in order toaccess that functionality.
ICT may have closed functionality in practice even though the ICT was not designed, developed or supplied to beclosed.
Computers that do not allow end-users to adjust settings or install software are functionally closed.

5.1.2
5.1.2.1

GeneralClosed functionality

Where ICT has closed functionality, it shall meet the requirements set out in clauses 5.2 to 13, as applicable.
NOTE 1: ICT may close some, but not all, of its functionalities. Only the closed functionalities have to conform to
the requirements of clause 5.1.
NOTE 2: The provisions within this clause are requirements for the closed functionality of ICT that replace thoserequirements in clauses 5.2 to 13 that specifically state that they do not apply to closed functionality. Thismay be because they relate to compatibility with assistive technology or to the ability for the user toadjust system accessibility settings in products with closed functionality (e.g. products that prevent accessto the system settings control panel).

5.1.2.2

Assistive technology

Where ICT has closed functionality, that closed functionality shall be operable without requiring the user to attach,connect or install assistive technology and shall conform to the generic requirements of clauses 5.1.3 to 5.1.6 asapplicable. Personal headsets and induction loops shall not be classed as assistive technology for the purpose of thisclause.

5.1.3
5.1.3.1

Non-visual access
GeneralWhere visual information is needed to enable the use of those functions of ICT that are closed to assistive technologies
for screen reading, ICT shall provide at least one mode of operation using non-visual access to enable the use of thosefunctions.
NOTE 1: Non-visual access may be in an audio form, including speech, or a tactile form.
NOTE 2: The visual information needed to enable use of some functions may include operating instructions andorientation, transaction prompts, user input verification, error messages and non-text content.

5.1.3.2

Auditory output delivery including speech

Where auditory output is provided as non-visual access to closed functionality, the auditory output shall be delivered:a)either directly by a mechanism included in or provided with the ICT; or

ETSI

21
EN 301 549 V2.1.2 (2018-08)b)

by a personal headset that can be connected through a 3,5 mm audio jack, or an industry standard connection,
without requiring the use of vision.

NOTE 1: Mechanisms included in or provided with ICT may be, but are not limited to, a loudspeaker, a built-in
handset/headset, or other industry standard coupled peripheral.
NOTE 2: An industry standard connection could be a wireless connection.
NOTE 3: Some users may benefit from the provision of an inductive loop.

5.1.3.3

Auditory output correlation

Where auditory output is provided as non-visual access to closed functionality, and where information is displayed on
the screen, the ICT should provide auditory information that allows the user to correlate the audio with the information
displayed on the screen.
NOTE 1: Many people who are legally blind still have visual ability, and use aspects of the visual display even if itcannot be fully comprehended. An audio alternative that is both complete and complementary includes all
visual information such as focus or highlighting, so that the audio can be correlated with information thatis visible on the screen at any point in time.
NOTE 2: Examples of auditory information that allows the user to correlate the audio with the information
displayed on the screen include structure and relationships conveyed through presentation.

5.1.3.4

Speech output user control

Where speech output is provided as non-visual access to closed functionality, the speech output shall be capable ofbeing interrupted and repeated when requested by the user, where permitted by security requirements.
NOTE 1: It is best practice to allow the user to pause speech output rather than just allowing them to interrupt it.
NOTE 2: It is best practice to allow the user to repeat only the most recent portion rather than requiring play to startfrom the beginning.

5.1.3.5

Speech output automatic interruption

Where speech output is provided as non-visual access to closed functionality, the ICT shall interrupt current speech
output when a user action occurs and when new speech output begins.
NOTE:

5.1.3.6

Where it is essential that the user hears the entire message, e.g. a safety instruction or warning, the ICT
may need to block all user action so that speech is not interrupted.

Speech output for non-text content

Where ICT presents non-text content, the alternative for non-text content shall be presented to users via speech output
unless the non-text content is pure decoration or is used only for visual formatting. The speech output for non-text
content shall follow the guidance for "text alternative" described in WCAG 2.1 [5] Success Criterion 1.1.1.

5.1.3.7

Speech output for video information

Where pre-recorded video content is needed to enable the use of closed functions of ICT and where speech output isprovided as non-visual access to closed functionality, the speech output shall present equivalent information for the
pre-recorded video content.
NOTE:

This speech output can take the form of an audio description or an auditory transcript of the video
content.

ETSI

22
EN 301 549 V2.1.2 (2018-08)

5.1.3.8

Masked entry

Where auditory output is provided as non-visual access to closed functionality, and the characters displayed aremasking characters, the auditory output shall not be a spoken version of the characters entered unless the auditory
output is known to be delivered only to a mechanism for private listening, or the user explicitly chooses to allow
non-private auditory output.
NOTE 1: Masking characters are usually displayed for security purposes and include, but are not limited toasterisks representing personal identification numbers.
NOTE 2: Unmasked character output might be preferred when closed functionality is used, for example, in theprivacy of the user's home. A warning highlighting privacy concerns might be appropriate to ensure thatthe user has made an informed choice.

5.1.3.9

Private access to personal data

Where auditory output is provided as non-visual access to closed functionality, and the output contains data that is
considered to be private according to the applicable privacy policy, the corresponding auditory output shall only bedelivered 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.
NOTE 1: This requirement does not apply in cases where data is not defined as being private according to theapplicable privacy policy or where there is no applicable privacy policy.
NOTE 2: Non-private output might be preferred when closed functionality is used, for example, in the privacy of
the user's home. A warning highlighting privacy concerns might be appropriate to ensure that the user has
made an informed choice.

5.1.3.10

Non-interfering audio output

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

5.1.3.11

Private listening volume

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

5.1.3.12

Speaker volume

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

5.1.3.13

For noisy environments, 65 dBA may not be sufficient.

Volume reset

Where auditory output is provided as non-visual access to closed functionality, a function that resets the volume to be at
a level of 65 dBA or less after every use, shall be provided, unless the ICT is dedicated to a single user.
NOTE:

A feature to disable the volume reset function may be provided in order to enable the single-user
exception to be met.

ETSI

23
EN 301 549 V2.1.2 (2018-08)

5.1.3.14

Spoken languages

Where speech output is provided as non-visual access to closed functionality, speech output shall be in the same humanlanguage as the displayed content provided, except:
a)for proper names, technical terms, words of indeterminate language, and words or phrases that have become
part of the vernacular of the immediately surrounding text;b)where the content is generated externally and not under the control of the ICT vendor, clause 5.1.3.14 shall not
be required to apply for languages not supported by the ICT's speech synthesizer;c)for displayed languages that cannot be selected using non-visual access;d)where the user explicitly selects a speech language that is different from the language of the displayed content.

5.1.3.15

Non-visual error identification

Where speech output is provided as non-visual access to closed functionality and an input error is automaticallydetected, speech output shall identify and describe the item that is in error.

5.1.3.16

Receipts, tickets, and transactional outputs

Where ICT is closed to visual access and provides receipts, tickets or other outputs as a result of a self-service
transaction, speech output shall be provided which shall include all information necessary to complete or verify thetransaction. In the case of ticketing machines, printed copies of itineraries and maps shall not be required to be audible.
NOTE:

5.1.4

The speech output may be provided by any element of the total ICT system.

Functionality closed to text enlargement

Where any functionality of ICT is closed to the text enlargement features of platform or assistive technology, the ICT
shall provide a mode of operation where the text and images of text necessary for all functionality is displayed in such a
way that a non-accented capital "H" subtends an angle of at least 0,7 degrees at a viewing distance specified by the
supplier.
The subtended angle, in degrees, may be calculated from:Ψ = (180 x H) / (π x D)
Where:•

ψ is the subtended angle in degrees•

H is the height of the text•

D is the viewing distance•

D and H are expressed in the same units

NOTE 1: The intent is to provide a mode of operation where text is large enough to be used by most users with low
vision.
NOTE 2: Table 5.1 and Figure 1 illustrate the relationship between the maximum viewing distance and minimum
character height at the specified minimum subtended angle.

ETSI

24
EN 301 549 V2.1.2 (2018-08)

Table 5.1: Relationship between maximum design viewing distance andminimum character height at the limit of subtended angle
Minimum
subtended
angle

Maximum design
viewing distance

Minimum characterheight0,7 degrees

100 mm
200 mm
250 mm
300 mm
350 mm
400 mm
450 mm
500 mm
550 mm
600 mm

1,2 mm
2,4 mm
3,1 mm
3,7 mm
4,3 mm
4,9 mm
5,5 mm
6,1 mm
6,7 mm
7,3 mmFigure 1: Relationship between minimum character height and maximum design viewing distance

5.1.5

Visual output for auditory information

Where pre-recorded auditory information is needed to enable the use of closed functions of ICT, the ICT shall provide
visual information that is equivalent to the pre-recorded auditory output.
NOTE:

5.1.6
5.1.6.1

This visual information can take the form of captions or text transcripts.

Operation without keyboard interface
Closed functionality

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

ETSI

25
EN 301 549 V2.1.2 (2018-08)

5.1.6.2

Input focus

Where ICT functionality is closed to keyboards or keyboard interfaces and where input focus can be moved to a userinterface element, it shall be possible to move the input focus away from that element using the same mechanism, inorder to avoid trapping the input focus.

5.2

Activation of accessibility features

Where ICT has documented accessibility features, it shall be possible to activate those documented accessibility
features that are required to meet a specific need without relying on a method that does not support that need.

5.3

Biometrics

Where ICT uses biological characteristics, it shall not rely on the use of a particular biological characteristic as the onlymeans of user identification or for control of ICT.
NOTE 1: Alternative means of user identification or for control of ICT could be non-biometric or biometric.
NOTE 2: Biometric methods based on dissimilar biological characteristics increase the likelihood that individuals
with disabilities possess at least one of the specified biological characteristics. Examples of dissimilar
biological characteristics are fingerprints, eye retinal patterns, voice, and face.

5.4

Preservation of accessibility information during conversion

Where ICT converts information or communication it shall preserve all documented non-proprietary information that isprovided for accessibility, to the extent that such information can be contained in or supported by the destination
format.

5.5

Operable parts

5.5.1

Means of operation

Where ICT has operable parts that require grasping, pinching, or twisting of the wrist to operate, an accessible
alternative means of operation that does not require these actions shall be provided.

5.5.2

Operable parts discernibility

Where ICT has operable parts, it shall provide a means to discern each operable part, without requiring vision andwithout performing the action associated with the operable part.
NOTE:

One way of meeting this requirement is by making the operable parts tactilely discernible.

5.6

Locking or toggle controls

5.6.1

Tactile or auditory status

Where ICT has a locking or toggle control and that control is visually presented to the user, the ICT shall provide atleast one mode of operation where the status of the control can be determined either through touch or sound without
operating the control.
NOTE 1: Locking or toggle controls are those controls that can only have two or three states and that keep theirstate while being used.

ETSI

26
EN 301 549 V2.1.2 (2018-08)

NOTE 2: An example of a locking or toggle control is the "Caps Lock" key found on most keyboards. Anotherexample is the volume button on a pay telephone, which can be set at normal, loud, or extra loud volume.

5.6.2

Visual status

Where ICT has a locking or toggle control and the control is non-visually presented to the user, the ICT shall provide atleast one mode of operation where the status of the control can be visually determined when the control is presented.
NOTE 1: Locking or toggle controls are those controls that can only have two or three states and that keep theirstate while being used.
NOTE 2: An example of a locking or toggle control is the "Caps Lock" key found on most keyboards. An example
of making the status of a control determinable is a visual status indicator on a keyboard.

5.7

Key repeat

Where ICT has a key repeat function that cannot be turned off:a)the delay before the key repeat shall be adjustable to at least 2 seconds; andb)the key repeat rate shall be adjustable down to one character per 2 seconds.

5.8

Double-strike key acceptance

Where ICT has a keyboard or keypad, the delay after any keystroke, during which an additional key-press will not be
accepted if it is identical to the previous keystroke, shall be adjustable up to at least 0,5 seconds.

5.9

Simultaneous user actions

Where ICT uses simultaneous user actions for its operation, such ICT shall provide at least one mode of operation that
does not require simultaneous user actions to operate the ICT.
NOTE:Having to use both hands to open the lid of a laptop, having to press two or more keys at the same time or
having to touch a surface with more than one finger are examples of simultaneous user actions.

ETSI

27
EN 301 549 V2.1.2 (2018-08)

6

ICT with two-way voice communication

6.1

Audio bandwidth for speech

Where ICT provides two-way voice communication, in order to provide good audio quality, that ICT shall be able toencode and decode two-way voice communication with a frequency range with an upper limit of at least 7 000 Hz.
NOTE 1: For the purposes of interoperability, support of Recommendation ITU-T G.722 [i.21] is widely used.
NOTE 2: Where codec negotiation is implemented, other standardized codecs such as Recommendation
ITU-T G.722.2 [i.22] are sometimes used so as to avoid transcoding.

6.2

Real-time text (RTT) functionality

6.2.1

RTT provision

6.2.1.1

RTT communication

Where ICT supports two-way voice communication in a specified context of use, the ICT shall allow a user tocommunicate with another user by RTT.
NOTE 1: The RTT capability can be provided as a factory default or added later.
NOTE 2: Provision of RTT may require additional service provision, additional hardware and/or software which
may be provided separately or together.

6.2.1.2

Concurrent voice and text

Where ICT supports two-way voice communication in a specified context of use, and enables a user to communicate
with another user by RTT, it shall provide a mechanism to select a mode of operation which allows concurrent voiceand text.
NOTE:

6.2.2
6.2.2.1

The availability of voice and RTT running concurrently can allow the RTT to replace or support voiceand transfer additional information such as numbers, currency amounts and spelling of names.

Display of Real-time Text
Visually distinguishable display

Where ICT has RTT send and receive capabilities, displayed sent text shall be visually differentiated from andseparated from received text.

6.2.2.2

Programmatically determinable send and receive direction

Where ICT has RTT send and receive capabilities, the send/receive direction of transmitted text shall be
programmatically determinable, unless the RTT has closed functionality.
NOTE:

The intent of this clause is to enable screen readers to be able to distinguish between incoming text andoutgoing text when used with RTT functionality.

ETSI

28
EN 301 549 V2.1.2 (2018-08)

6.2.3

Interoperability

Where ICT with RTT functionality interoperates with other ICT with RTT functionality (as required by clause 6.2.1.1)
they shall support at least one of the four RTT interoperability mechanisms described below:a)

ICT interoperating over the Public Switched Telephone Network (PSTN), with other ICT that directly
connects to the PSTN as described in Recommendation ITU-T V.18 [i.23] or any of its annexes for text
telephony signals at the PSTN interface;b)

ICT interoperating with other ICT using VOIP with Session Initiation Protocol (SIP) and using real-time textthat conforms to IETF RFC 4103 [i.13];c)

ICT interoperating with other ICT using RTT that conforms with the IP Multimedia Sub-System (IMS) set of
protocols specified in ETSI TS 126 114 [i.10], ETSI TS 122 173 [i.11] and ETSI TS 134 229 [i.12];d)

ICT interoperating with other ICT using a relevant and applicable common specification for RTT exchangethat is published and available. This common specification shall include a method for indicating loss or
corruption of characters.

6.2.4

Real-time text responsiveness

Where ICT utilises RTT input, that RTT input shall be transmitted to the ICT network supporting RTT within 1 secondof the input entry.
NOTE 1: Input entry is considered to have occurred when sufficient user input has occurred for the ICT to establish
which character(s) to send.
NOTE 2: Input entry 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.

6.3

Caller ID

Where ICT provides caller identification or similar telecommunications functions are provided, the caller identificationand similar telecommunications functions shall be available in text form and in at least one other modality.

6.4

Alternatives to voice-based services

Where ICT provides real-time voice-based communication and also provides voice mail, auto-attendant, or interactive
voice response facilities, the ICT should offer users a means to access the information and carry out the tasks provided
by the ICT without the use of hearing or speech.
NOTE:

Solutions capable of handling audio, real-time text and video media could satisfy the above requirement.

6.5

Video communication

6.5.1

General (informative)

Clause 6.5 (Video communications) provides performance requirements that support users who communicate using sign
language and lip-reading. For these users, good usability is achieved with Common Intermediate Format (CIF)
resolution, a frame rate of 20 frames per second and over, with a time difference between speech audio and video that
does not exceed 100 ms.
When the resolution is reduced to Quarter Common Intermediate Format (QCIF) and the frame rate drops to 12 frames
per second the communication is still usable with some restrictions.
A lower resolution causes less disturbance to the perception of sign language and lip-reading than that caused by alower frame rate.

ETSI

29
EN 301 549 V2.1.2 (2018-08)

Delay can be a problem in video communication. Overall delay values below 0,4 s are preferred, with an increase in
preference down to 0,1 s. Values over 0,8 s are felt to hinder a good sign conversation. 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 that provides two-way voice communication includes real-time video functionality, the ICT:a)shall support at least QCIF resolution;b)should preferably support at least CIF resolution.

6.5.3

Frame rate

Where ICT that provides two-way voice communication includes real-time video functionality, the ICT:a)shall support a frame rate of at least 12 frames per second (FPS);b)should preferably support a frame rate of at least 20 frames per second (FPS) with or without sign language inthe video stream.

6.5.4

Synchronization between audio and video

Where ICT that provides two-way voice communication includes real-time video functionality, the ICT should ensure amaximum time difference of 100 ms between the speech and video presented to the user.

6.6

Alternatives to video-based services

Where ICT provides real-time video-based communication and also provides answering machine, auto attendant orinteractive response facilities, the ICT should offer users a means to access the information and carry out the tasks
related to these facilities:a)for audible information, without the use of hearing;b)

for spoken commands, without the use of speech;c)for visual information, without the use of vision.

NOTE:

Solutions capable of generating real-time captions or handling real-time text could satisfy the above
requirement.

ETSI

30
EN 301 549 V2.1.2 (2018-08)

7

ICT with video capabilities

7.1

Caption processing technology

7.1.1

Captioning playback

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

7.1.2

Captions may contain information about timing, colour and positioning. This caption data is important for
caption users. Timing is used for caption synchronization. Colour can be used for speaker identification.
Position can be used to avoid obscuring important information.

Captioning synchronization

Where ICT displays captions, the mechanism to display captions shall preserve synchronization between the audio andthe corresponding captions.

7.1.3

Preservation of captioning

Where ICT transmits, converts or records video with synchronized audio, it shall preserve caption data such that it canbe displayed in a manner consistent with clauses 7.1.1 and 7.1.2.
Additional presentational aspects of the text such as screen position, text colours, text style and text fonts may convey
meaning, based on regional conventions. Altering these presentational aspects could change the meaning and should be
avoided wherever possible.

7.2

Audio description technology

7.2.1

Audio description playback

Where ICT displays video with synchronized audio, it shall provide a mechanism to select and play available audio
description to the default audio channel.
Where video technologies do not have explicit and separate mechanisms for audio description, an ICT is deemed tosatisfy this requirement if the ICT enables the user to select and play several audio tracks.
NOTE 1: In such cases, the video content can include the audio description as one of the available audio tracks.
NOTE 2: Audio descriptions in digital media sometimes include information to allow descriptions that are longer
than the gaps between dialogue. Support in digital media players for this "extended audio description"
feature is useful, especially for digital media that is viewed personally.

7.2.2

Audio description synchronization

Where ICT has a mechanism to play audio description, it shall preserve the synchronization between the audio/visualcontent and the corresponding audio description.

7.2.3

Preservation of audio description

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

ETSI

31
EN 301 549 V2.1.2 (2018-08)

7.3

User controls for captions and audio description

Where ICT primarily displays materials containing video with associated audio content, user controls to activate
subtitling and audio description shall be provided to the user at the same level of interaction (i.e. the number of steps tocomplete the task) as the primary media controls.
NOTE 1: Primary media controls are the set of controls that the user most commonly uses to control media.
NOTE 2: Products that have a general hardware volume control, such as a telephone, or a laptop which can be
configured to display video through software but which is not its primary purpose, would not need
dedicated hardware controls for captions and descriptions; however software controls, or hardware
controls mapped through software, would need to be at the same level of interaction.
NOTE 3: It is best practice for ICT to include additional controls enabling the user to select whether captions andaudio description are turned on or off by default.

ETSI

32
EN 301 549 V2.1.2 (2018-08)

8Hardware

8.1

General

8.1.1

Generic requirements

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

8.1.2

Standard connections

Where an ICT provides user input or output device connection points, the ICT shall provide at least one input and/or
output connection that conforms to an industry standard non-proprietary format, directly or through the use ofcommercially available adapters.
NOTE 1: The intent of this requirement is to ensure compatibility with assistive technologies by requiring the useof standard connections on ICT.
NOTE 2: The word connection applies to both physical and wireless connections.
NOTE 3: Current examples of industry standard non-proprietary formats are USB and Bluetooth.

8.1.3

Colour

Where the ICT has hardware aspects that use colour, colour shall not be used as the only visual means of conveying
information, indicating an action, prompting a response, or distinguishing a visual element.

8.2

Hardware products with speech output

8.2.1

Speech volume gain

8.2.1.1

Speech volume range

Where ICT hardware has speech output, it shall provide a means to adjust the speech output volume level over a rangeof at least 18 dB.
NOTE:

8.2.1.2

Fixed-line handsets and headsets fulfilling the requirements of ANSI/TIA-4965 [i.2] are deemed tocomply with this requirement.

Incremental volume control

Where ICT hardware has speech output and its volume control is incremental, it shall provide at least one intermediatestep of 12 dB gain above the lowest volume setting.

8.2.2

Magnetic coupling

8.2.2.1

Fixed-line devices

Where ICT hardware is a fixed-line communication device with speech output and which is normally held to the ear andwhich carries the "T" symbol specified in ETSI ETS 300 381 [1], it shall provide a means of magnetic coupling whichmeets the requirements of ETSI ES 200 381-1 [2].
NOTE:

ICT fulfilling the requirements of TIA-1083-A [i.24] is deemed to comply with the requirements of thisclause.

ETSI

33
EN 301 549 V2.1.2 (2018-08)

8.2.2.2

Wireless communication devices

Where ICT hardware is a wireless communication device with speech output which is normally held to the ear, it shallprovide a means of magnetic coupling to hearing technologies which meets the requirements of ETSI ES 200 381-2 [3].
NOTE:

ICT fulfilling the requirements of ANSI/IEEE C63.19 [i.1] is deemed to comply with the requirements ofthis clause.

8.3

Physical access to ICT

8.3.1

General (informative)

Clauses 8.3.2 to 8.3.4 describe recommendations on those dimensions that are integral to the ICT (e.g. integral shelves,or integral cabins that may restrict access to the operable parts of the ICT).
When ICT is installed, the dimensions of the surrounding space combined with the dimensions of the ICT might affectthe physical access to the ICT. Accessible physical access of the ICT would be achieved if the installation instructions
referred to in clause 8.3.5 are followed.
It may not be possible to apply all recommendations of clause 8.3 to all aspects of maintenance, repair, or occasional
monitoring of equipment in all circumstances. Nevertheless, it is best practice to apply the recommendations inclause 8.3, where feasible and safe to do so.
NOTE 1: The dimensions set out in clause 8.3 are identical to those given in the American 2010 ADA standards foraccessible design [i.25].
NOTE 2: Physical access to ICT is dependent on the dimensions of both the ICT and the environment in which it isinstalled and operated. Clause 8.3 does not apply to the accessibility of the physical environment external
to the ICT.

8.3.2

Clear floor or ground space

8.3.2.1

Change in level

Where there is a change in floor level that is integral to the ICT then it should be ramped with a slope no steeper than
1:48.
Exceptions:a)

If the change in floor level is less than or equal to 6,4 mm (¼ inch) the change may be vertical as shown in
Figure 2.

b)

If the change in floor level is less than or equal to 13 mm (½ inch) the change may have a slope not steeper
than 1:2 as shown in Figure 3.

Figure 2: Vertical change in level

ETSI

34
EN 301 549 V2.1.2 (2018-08)

mm
mm
mm

Figure 3: Bevelled change in level

8.3.2.2

Clear floor or ground space

Where the operating area is integral to the ICT, it should provide a clear floor area that has the minimum dimensions of
760 mm (30 inches) by 1 220 mm (48 inches) from which to operate the ICT. This is shown in Figure 4.

Figure 4: Clear floor or ground space

8.3.2.3

Approach

8.3.2.3.1

GeneralWhere the access space is integral to the ICT, at least one full side of the space should be unobstructed.

8.3.2.3.2

Forward approach

Where the operating area is inside an alcove integral to the ICT, the alcove is deeper than 610 mm (24 inches), andwhere a forward approach is necessary, the dimension of the access space should be a minimum of 915 mm (36 inches)
wide. This is shown in Figure 5.

Figure 5: Manoeuvring Clearance in an Alcove, Forward Approach

ETSI

35
EN 301 549 V2.1.2 (2018-08)

8.3.2.3.3

Parallel approach

Where the operating area is inside an alcove integral to the ICT, the alcove is deeper than 380 mm (15 inches), andwhere a parallel approach is possible, the dimension of the access space should be a minimum of 1 525 mm (60 inches)
wide. This is shown in Figure 6.

Figure 6: Manoeuvring Clearance in an Alcove, Parallel Approach

8.3.2.4

Knee and toe clearance width

Where the space under an obstacle that is integral to the ICT is part of access space, the clearance should be at least
760 mm (30 inches) wide.

8.3.2.5

Toe clearance

Where an obstacle is integral to the ICT, a space under the obstacle that is less than 230 mm (9 inches) above the floor
is considered toe clearance and should:a)extend 635 mm (25 inches) maximum under the whole obstacle;b)provide a space at least 430 mm (17 inches) deep and 230 mm above the floor under the obstacle;c)extend no more than 150 mm (6 inches) beyond any obstruction at 230 mm (9 inches) above the floor.

This is shown in Figure 7.

Figure 7: Toe clearance

8.3.2.6

Knee clearance

Where an obstacle is integral to the ICT, the space under the obstacle that is between 230 mm and 685 mm above thefloor is considered knee clearance and should:a)extend no more than 635 mm (25 inches) under the obstacle at a height of 230 mm (9 inches) above the floor;b)extend at least 280 mm (11 inches) under the obstacle at a height of 230 mm (9 inches) above the floor;c)extend at least 205 mm (8 inches) under the obstacle at a height of 685 mm (27 inches) above the floor;

ETSI

36
EN 301 549 V2.1.2 (2018-08)d)be permitted to be reduced in depth at a rate of 25 mm (1 inch) for each 150 mm (6 inches) in height.

This is shown in Figure 8.

Figure 8: Knee clearance

8.3.3
8.3.3.1
8.3.3.1.1

Reach range for ICT
Forward reach
Unobstructed high forward reach

Where the access space is integral to the ICT and the forward reach is unobstructed, the essential controls should belocated no higher than 1 220 mm (48 inches) above the floor of the access space. This is shown in Figure 9.

8.3.3.1.2

Unobstructed low forward reach

Where the access space is integral to the ICT and the forward reach is unobstructed, the essential controls should belocated no lower than 380 mm (15 inches) above the floor of the access space. This is shown in Figure 9.

Figure 9: Unobstructed forward reach

8.3.3.1.3

Obstructed reach

8.3.3.1.3.1

Clear floor space

Where the access space is integral to the ICT and has an obstruction which is integral to the ICT which hinders theaccess to any essential controls, the ICT should provide a clear floor space which extends beneath the obstructing
element for a distance not less than the required reach depth over the obstruction.

ETSI

37
EN 301 549 V2.1.2 (2018-08)

8.3.3.1.3.2

Obstructed (< 510 mm) forward reach

Where the access space is integral to the ICT and has an obstruction which is integral to the ICT and which is less than
510 mm (20 inches), the forward reach to all essential controls should be no higher than 1 220 mm (48 inches) above
the floor contact of the ICT. This is shown in Figure 10 (a).
8.3.3.1.3.3

Obstructed (< 635 mm) forward reach

Where the access space is integral to the ICT and has an obstruction which is integral to the ICT and which is greaterthan 510 mm (20 inches) and less than 635 mm (25 inches) maximum, the forward reach to all essential controls should
be no higher than 1 120 mm (44 inches) above the floor contact of the ICT. This is shown in Figure 10 (b).

Figure 10: Obstructed high reach

8.3.3.2
8.3.3.2.1

Side reach
Unobstructed high side reach

Where the access space is integral to the ICT, allows a parallel approach, and the side reach is unobstructed or
obstructed by an element integral to the ICT which is less than 255 mm (10 inches), all essential controls should bewithin a high side reach which is less than or equal to 1 220 mm (48 inches) above the floor of the access space. This isshown in Figure 11.

8.3.3.2.2

Unobstructed low side reach

Where the access space is integral to the ICT, allows a parallel approach, and the side reach is unobstructed or
obstructed by an element integral to the ICT which is less than 255 mm (10 inches), all essential controls should bewithin a low side reach which is greater than or equal to 380 mm (15 inches) above the floor of the access space. This isshown in Figure 11.

Figure 11: Unobstructed side reach

ETSI

38
EN 301 549 V2.1.2 (2018-08)

8.3.3.2.3
8.3.3.2.3.1

Obstructed side reach
Obstructed (≤ 255 mm) side reach

Where the access space is integral to the ICT, allows a parallel approach and has an obstruction which is integral to the
ICT, the height of the obstruction should be less than 865 mm (34 inches). Where the depth of the obstruction is lessthan or equal to 255 mm (10 inches), the high side reach to all essential controls should be no higher than 1 220 mm(48 inches) above the floor of the access space. This is shown in Figure 12 (a).
8.3.3.2.3.2

Obstructed (≤ 610 mm) side reach

Where the access space is integral to the ICT, allows a parallel approach and has an obstruction which is integral to the
ICT, the height of the obstruction should be less than 865 mm (34 inches). Where the depth of the obstruction is greaterthan 255 mm (10 inches) with a maximum depth of 610 mm (24 inches), the high side reach to all essential controls
should be no higher than 1 170 mm (46 inches) above the floor of the access space. This is shown in Figure12 (b).

Figure 12: Obstructed high side reach

8.3.4

Visibility

Where the operating area is integral to the ICT, and a display screen is provided, information on the screen should be
legible from a point located 1 015 mm (40 inches) above the centre of the floor of the operating area (as defined inclause 8.3.2.2).
NOTE:

8.3.5

The intent of this provision is that the information on the screen can be read by users with normal vision
and appropriate language skills, when seated in a wheelchair.

Installation instructions

Where an ICT is intended to be installed, instructions should be made available which outline a method to install the
ICT in a manner that ensures that the dimensions of the integral spaces of the ICT conform to clauses 8.3.2 to 8.3.4.

8.4

Mechanically operable parts

8.4.1

Numeric keys

Where provided, physical numeric keys arranged in a rectangular keypad layout shall have the number five key tactilely
distinct from the other keys of the keypad.
NOTE:

Recommendation ITU-T E.161 [i.20] describes the 12-key telephone keypad layout and provides further
details of the form of tactile markers.

ETSI

39
EN 301 549 V2.1.2 (2018-08)

8.4.2
8.4.2.1

Operation of mechanical parts
Means of operation of mechanical parts

Where a control requires grasping, pinching, or twisting of the wrist to operate it, an accessible alternative means ofoperation that does not require these actions shall be provided.

8.4.2.2

Force of operation of mechanical parts

Where a control requires a force greater than 22,2 N to operate it, an accessible alternative means of operation that
requires a force less than 22,2 N shall be provided.

8.4.3

Keys, tickets and fare cards

Where ICT provides keys, tickets or fare cards, and their orientation is important for further use, they shall have an
orientation that is tactilely discernible.
NOTE:

8.5

ETSI ETS 300 767 [i.6] defines suitable tactile indications for plastic cards.

Tactile indication of speech mode

Where ICT is designed for shared use and speech output is available, a tactile indication of the means to initiate thespeech mode of operation shall be provided.
NOTE:

The tactile indication could include Braille instructions.

ETSI

40
EN 301 549 V2.1.2 (2018-08)

9

Web

9.0

General (informative)

Requirements in clause 9 apply to web pages (as defined in clause 3.1) including:•Conformance with WCAG 2.0 Level AA is equivalent to conforming with clauses 9.1.1, 9.1.2, 9.1.3.1 to9.1.3.3, 9.1.4.1 to 9.1.4.5, 9.2.1.1, 9.2.1.2, 9.2.1.4, 9.2.1.1, 9.2.1.2, 9.2.2, 9.2.3, 9.2.4, 9.3, 9.4.1.1, 9.4.1.2 andthe conformance requirements of clause 9.5 of the present document.

•

Conformance with WCAG 2.1 Level AA is equivalent to conforming with all of clauses 9.1 to 9.4 and theconformance requirements of clause 9.5 of the present document.

•

Requirements for other documents and software are provided in clauses 10 and 11 respectively.

NOTE 1: When evaluating web sites they are evaluated as individual web pages. Web applications, mobile web
applications etc. are covered under the definition of web page which is quite broad and covers all web
content types.
The web content requirements in clauses 9.1 to 9.4 set out all of the Level A and Level AA Success Criteria from theW3C Web Content Accessibility Guidelines (WCAG 2.1) [5]:•Web Pages conforming to WCAG 2.0 Level A and AA also conform to clauses 9.1.1.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.1 to 9.2.4.7, 9.3.1.1 to 9.4.1.2 and the conformance requirements of clause 9.5.

•

Web Pages that conform to WCAG 2.1 Level AA conform to all of clauses 9.1 to 9.4 and the conformancerequirements of clause 9.5.

•

Web Pages conforming to clauses 9.1.1.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.1 to 9.2.4.7,
9.3.1.1 to 9.4.1.2, and the conformance requirements of clause 9.5, also conform to WCAG 2.0 Level AA.

•

Web Pages that conform to all of clauses 9.1 to 9.4, and the conformance requirements of clause 9.5, conformto WCAG 2.1 Level AA.

NOTE 2: WCAG 2.0 is identical to ISO/IEC 40500 (2012): "Information technology - W3C Web Content
Accessibility Guidelines (WCAG) 2.0" [4].
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 featuredoes not occur in the web page, then the web page satisfies the success criterion.
NOTE 3: For example, a web page that does not contain pre-recorded audio content in synchronized media willautomatically satisfy WCAG success criterion 1.2.2 (captions - pre-recorded) and, in consequence, will
also conform to clause 9.1.2.2.
In addition to Level AA success criteria, the Web Content Accessibility Guidelines also include success criteria forLevel AAA. These are included in Annex D of the present document.
NOTE 4: The body of the present document does not include the Level AAA success criteria, both to avoid
confusion with the Level A and Level AA based requirements and for harmonisation with otherprocurement standards.
Web authors and procurement accessibility specialists are encouraged to improve accessibility beyond therequirements of the present document and should therefore 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.
NOTE 5: The W3C states that "It is not recommended that Level AAA conformance be required as a general policy
for entire sites because it is not possible to satisfy all Level AAA Success Criteria for some content".

ETSI

41
EN 301 549 V2.1.2 (2018-08)

NOTE 6: "Void" clauses have been inserted in order to maintain alignment with the numbering of WCAG 2.1
Level A and Level AA Success Criteria.

9.1

Perceivable

9.1.1

Text alternatives

9.1.1.1

Non-text content

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.1.1 Non-text content.

9.1.2
9.1.2.1

Time-based media
Audio-only and video-only (pre-recorded)

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.2.1 Audio-only and Video-only (Prerecorded).

9.1.2.2

Captions (pre-recorded)

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.2.2 Captions (Prerecorded).

9.1.2.3

Audio description or media alternative (pre-recorded)

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

9.1.2.4

Captions (live)

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.2.4 Captions (Live).

9.1.2.5

Audio description (pre-recorded)

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.2.5 Audio Description (Prerecorded).

9.1.3
9.1.3.1

Adaptable
Info and relationships

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.3.1 Info and Relationships.

9.1.3.2

Meaningful sequence

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.3.2 Meaningful Sequence.

9.1.3.3

Sensory characteristics

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.3.3 Sensory Characteristics.

9.1.3.4

Orientation

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.3.4 Orientation.

ETSI

42
EN 301 549 V2.1.2 (2018-08)

9.1.3.5

Identify input purpose

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.3.5 Identify Input Purpose.

9.1.4

Distinguishable

9.1.4.1

Use of colour

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.4.1 Use of Color.

9.1.4.2

Audio control

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.4.2 Audio Control.

9.1.4.3

Contrast (minimum)

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.4.3 Contrast (Minimum).

9.1.4.4

Resize text

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.4.4 Resize text.

9.1.4.5

Images of text

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.4.5 Images of Text.

9.1.4.6

Void

9.1.4.7

Void

9.1.4.8

Void

9.1.4.9Void

9.1.4.10

Reflow

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.4.10 Reflow.

9.1.4.11

Non-text contrast

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.4.11 Non-text Contrast.

9.1.4.12

Text spacing

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.4.12 Text spacing.

9.1.4.13

Content on hover or focus

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.4.13 Content on Hover or Focus.

ETSI

43
EN 301 549 V2.1.2 (2018-08)

9.2

Operable

9.2.1

Keyboard accessible

9.2.1.1

Keyboard

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.1.1 Keyboard.

9.2.1.2

No keyboard trap

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.1.2 No Keyboard Trap.

9.2.1.3

Void

9.2.1.4

Character key shortcuts

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.1.4 Character Key Shortcuts.

9.2.2
9.2.2.1

Enough time
Timing adjustable

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.2.1 Timing Adjustable.

9.2.2.2

Pause, stop, hide

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.2.2 Pause, Stop, Hide.

9.2.3

Seizures and physical reactions

9.2.3.1

Three flashes or below threshold

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.3.1 Three Flashes or Below Threshold.

9.2.4
9.2.4.1

Navigable
Bypass blocks

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.4.1 Bypass Blocks.

9.2.4.2

Page titled

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.4.2 Page Titled.

9.2.4.3

Focus Order

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.4.3 Focus Order.

9.2.4.4

Link purpose (in context)

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.4.4 Link Purpose (In Context).

ETSI

44
EN 301 549 V2.1.2 (2018-08)

9.2.4.5

Multiple ways

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.4.5 Multiple Ways.

9.2.4.6

Headings and labels

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.4.6 Headings and Labels.

9.2.4.7

Focus visible

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.4.7 Focus Visible.

9.2.5

Input modalities

9.2.5.1

Pointer gestures

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.5.1 Pointer Gestures.

9.2.5.2

Pointer cancellation

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.5.2 Pointer Cancellation.

9.2.5.3

Label in name

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.5.3 Label in Name.

9.2.5.4

Motion actuation

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 2.5.4 Motion Actuation.

9.3

Understandable

9.3.1

Readable

9.3.1.1

Language of page

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 3.1.1 Language of Page.

9.3.1.2

Language of parts

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 3.1.2 Language of Parts.

9.3.2

Predictable

9.3.2.1

On focus

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 3.2.1 On Focus.

9.3.2.2

On input

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 3.2.2 On Input.

ETSI

45
EN 301 549 V2.1.2 (2018-08)

9.3.2.3

Consistent navigation

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 3.2.3 Consistent Navigation.

9.3.2.4

Consistent identification

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 3.2.4 Consistent Identification.

9.3.3
9.3.3.1

Input assistance
Error identification

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 3.3.1 Error Identification.

9.3.3.2

Labels or instructions

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 3.3.2 Labels or Instructions.

9.3.3.3

Error suggestion

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 3.3.3 Error Suggestion.

9.3.3.4

Error prevention (legal, financial, data)

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 3.3.4 Error Prevention (Legal, Financial, Data).

9.4

Robust9.4.1

Compatible

9.4.1.1

Parsing

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 4.1.1 Parsing.

9.4.1.2

Name, role, value

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 4.1.2 Name, Role, Value.

9.4.1.3

Status messages

Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 4.1.3 Status Messages.

9.5

WCAG conformance requirements

Where ICT is a web page, it shall satisfy all the following five WCAG 2.1 conformance requirements at Level AA [5].
1)

Conformance level2)

Full pages

3)

Complete processes

4)

Only Accessibility-Supported Ways of Using Technologies

5)

Non-interference

ETSI

46
EN 301 549 V2.1.2 (2018-08)

NOTE 1: A Web page that meets all of requirements 9.1 to 9.4, or where a Level AA conforming alternate version(as defined in WCAG 2.1 [5]) is provided, will meet conformance requirement 1.
NOTE 2: According to W3C: "WCAG 2.1 extends Web Content Accessibility Guidelines 2.0 [4], which was
published as a W3C Recommendation December 2008. Content that conforms to WCAG 2.1 also
conforms to WCAG 2.0, and therefore to policies that reference WCAG 2.0" [4].
NOTE 3: Conformance requirement 5 states that all content on the page, including content that is not otherwise
relied upon to meet conformance, meets clauses 9.1.4.2, 9.2.1.2, 9.2.2.2 and 9.2.3.1.

ETSI

47
EN 301 549 V2.1.2 (2018-08)

10

Non-web documents

10.0

General (informative)

Requirements in clause 10 apply to documents:•that are not web pages;•that are not embedded in web pages;•that are embedded in web pages and that are not used in the rendering and that are not intended to be rendered
together with the web page in which they are embedded.

Clause 9 provides requirements for documents that are in web pages or that are embedded in web pages and that areused in the rendering or that are intended to be rendered together with the web page in which they are embedded.
NOTE 1: Some examples of documents are letters, spreadsheets, emails, books, pictures, presentations, and movies
that have an associated user agent such as a document reader, editor or media player.
NOTE 2: A single document may be composed of multiple files such as the video content, closed caption text, etc.
This fact is not usually apparent to the end-user consuming the document/content.
NOTE 3: Documents require a user agent in order for the content to be presented to users. The requirements foruser agents can be found in clause 11.
NOTE 4: The requirements for content that is part of software, can be found in clause 11.
NOTE 5: The success criteria set out in clause 10 are intended to harmonize with the Working Group Note [i.26]
produced by the W3C's WCAG2ICT Task Force.
NOTE 6: "Void" clauses have been inserted in order to maintain alignment of the numbering in clauses 9, 10 and
11.

10.1

Perceivable

10.1.1

Text alternatives

10.1.1.1

Non-text content

Where ICT is a non-web document, it shall satisfy the WCAG 2.1 Success Criterion 1.1.1 Non-text Content.
NOTE:

10.1.210.1.2.1

CAPTCHAs do not currently appear outside of the Web. However, if they do appear, this guidance isaccurate.

Time-based media
Audio-only and video-only (pre-recorded)

Where ICT is a non-web document, it shall satisfy WCAG 2.1 Success Criterion 1.2.1 Audio-only and Video-only(Prerecorded).
NOTE:

The alternative can be provided directly in the document - or provided in an alternate version that meetsthe success criterion.

ETSI

48
EN 301 549 V2.1.2 (2018-08)

10.1.2.2

Captions (pre-recorded)

Where ICT is a non-web document, it shall satisfy the WCAG 2.1 Success Criterion 1.2.2 Captions (Prerecorded).
NOTE:

10.1.2.3

The WCAG 2.1 definition of "captions" notes that "in some countries, captions are called subtitles". They
are also sometimes referred to as "subtitles for the hearing impaired". Per the definition in WCAG 2.1, tomeet this success criterion, whether called captions or subtitles, they would have to provide"synchronized visual and / or text alternative for both speech and non-speech audio information needed tounderstand the media content" where non-speech information includes "sound effects, music, laughter,speaker identification and location".

Audio description or media alternative (pre-recorded)

Where ICT is a non-web document, it shall satisfy the WCAG 2.1 Success Criterion 1.2.3 Audio Description or Media
Alternative (Prerecorded).
NOTE 1: The WCAG 2.1 definition of "audio description" says that "audio description" is "Also called 'video
description' and 'descriptive narration'".
NOTE 2: Secondary or alternate audio tracks are commonly used for this purpose.

10.1.2.4

Captions (live)

Where ICT is a non-web document, it shall satisfy the WCAG 2.1 Success Criterion 1.2.4 Captions (Live).
NOTE:

10.1.2.5

The WCAG 2.1 definition of "captions" notes that "in some countries, captions are called subtitles". They
are also sometimes referred to as "subtitles for the hearing impaired". Per the definition in WCAG 2.1, tomeet this success criterion, whether called captions or subtitles, they would have to provide"synchronized visual and / or text alternative for both speech and non-speech audio information needed tounderstand the media content" where non-speech information includes "sound effects, music, laughter,speaker identification and location".

Audio description (pre-recorded)

Where ICT is a non-web document, it shall satisfy the WCAG 2.1 Success Criterion 1.2.5 Audio Description(Prerecorded).
NOTE 1: The WCAG 2.1 definition of "audio description" says that audio description is "Also called 'video
description' and 'descriptive narration'".
NOTE 2: Secondary or alternate audio tracks are commonly used for this purpose.

10.1.310.1.3.1

Adaptable
Info and relationships

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

10.1.3.2

Meaningful sequence

Where ICT is a non-web document, it shall satisfy the WCAG 2.1 Success Criterion 1.3.2 Meaningful Sequence.

10.1.3.3

Sensory characteristics

Where ICT is a non-web document, it shall satisfy the WCAG 2.1 Success Criterion 1.3.3 Sensory Characteristics.

ETSI

49
EN 301 549 V2.1.2 (2018-08)

10.1.3.4

Orientation

Where ICT is a non-web document, it shall satisfy the WCAG 2.1 Success Criterion 1.3.4 Orientation.

10.1.3.5

Identify input purpose

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

10.1.4

Distinguishable

10.1.4.1

Use of colour

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

10.1.4.2

Audio control

Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.1.
Table 10.1: Document success criterion: Audio control
If any audio in a document plays automatically for more than 3 seconds, either a mechanism is available to pause
or stop the audio, or a mechanism is available to control audio volume independently from the overall system
volume level.
NOTE 1: Since any part of a document that does not meet this success criterion can interfere with a user's ability
to use the whole document, all content in the document (whether or not it is used to meet other successcriteria) shall meet this success criterion.
NOTE 2: This success criterion is identical to the WCAG 2.1 Success Criterion 1.4.2 Audio Control, replacing "ona Web page" with "in a document" "any content" with "any part of a document", "whole page" with "whole
document", "on the Web page" with "in the document", removing "See Conformance Requirement 5:
Non-Interference" and adding note 1.

10.1.4.3

Contrast (minimum)

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

10.1.4.4

Resize text

Where ICT is a non-web document, it shall satisfy the WCAG 2.1 Success Criterion 1.4.4 Resize Text.
NOTE 1: Content for which there are software players, viewers or editors with a 200 percent zoom feature would
automatically meet this success criterion when used with such players, unless the content will not workwith zoom.
NOTE 2: This success criterion is about the ability to allow users to enlarge the text on screen at least up to 200 %without needing to use assistive technologies. This means that the application provides some means forenlarging the text 200 % (zoom or otherwise) without loss of content or functionality or that theapplication works with the platform features that meet this requirement.

10.1.4.5

Images of text

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

10.1.4.6

Void

10.1.4.7

Void

10.1.4.8

Void

ETSI

50
EN 301 549 V2.1.2 (2018-08)

10.1.4.9

Void

10.1.4.10

Reflow

Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.2.
Table 10.2: 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.
NOTE 1: 320 CSS pixels is equivalent to a starting viewport width of 1280 CSS pixels wide at 400% zoom. For
documents which are designed to scroll horizontally (e.g. with vertical text), the 256 CSS pixels is
equivalent to a starting viewport height of 1024px at 400% zoom.
NOTE 2: Examples of content which require two-dimensional layout are images, maps, diagrams, video, games,
presentations, data tables, and interfaces where it is necessary to keep toolbars in view while
manipulating content.
NOTE 3: This success criterion is identical to the WCAG 2.1 Success Criterion 1.4.10 Reflow replacing the original
WCAG 2.1 notes with notes 1 and 2, above.

10.1.4.11

Non-text contrast

Where ICT is a non-web document, it shall satisfy WCAG 2.1 Success Criterion 1.4.11 Non-text Contrast.

10.1.4.12

Text spacing

Where ICT is a non-web document that does not have a fixed size content layout area that is essential to the information
being conveyed, it shall satisfy WCAG 2.1 Success Criterion 1.4.12 Text spacing.

10.1.4.13

Content on hover or focus

Where ICT is a non-web document, it shall satisfy WCAG 2.1 Success Criterion 1.4.13 Content on Hover or Focus.

10.2

Operable

10.2.1

Keyboard accessible

10.2.1.1

Keyboard

Where ICT is a non-web document, it shall satisfy the WCAG 2.1 Success Criterion 2.1.1 Keyboard.

ETSI

51
EN 301 549 V2.1.2 (2018-08)

10.2.1.2

No keyboard trap

Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.3.
Table 10.3: Document success criterion: No keyboard trap
If keyboard focus can be moved to a component of the document using a keyboard interface, then focus can be
moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or
tab keys or other standard exit methods, the user is advised of the method for moving focus away.
NOTE 1: Since any part of a document that does not meet this success criterion can interfere with a user's ability
to use the whole document, it is necessary for all content in the document (whether or not it is used tomeet other success criteria) to meet this success criterion.
NOTE 2: Standard exit methods may vary by platform. For example, on many desktop platforms, the Escape key
is a standard method for exiting.
NOTE 3: This success criterion is identical to the WCAG 2.1 Success Criterion 2.1.2 No Keyboard Trap replacing"page" and "Web page" with "document", removing "See Conformance Requirement 5: Non-Interference"
and with the addition of note 2 above and with note 1 above re-drafted to avoid the use of the word
"must".

10.2.1.3

Void

10.2.1.4

Character key shortcuts

Where ICT is a non-web document, it shall satisfy WCAG 2.1 Success Criterion 2.1.4 Character Key Shortcuts.

10.2.210.2.2.1

Enough time
Timing adjustable

Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.4.
Table 10.4: Document success criterion: Timing adjustable
For each time limit that is set by the 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 witha simple action (for example, "press the space bar"), and the user is allowed to extend the time limit atleast ten times; or•
Real-time Exception: The time limit is a required part of a real-time event (for example, an auction), andno 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.
NOTE 1: This success criterion helps ensure that users can complete tasks without unexpected changes incontent or context that are a result of a time limit. This success criterion should be considered inconjunction with WCAG 2.1 Success Criterion 3.2.1, which puts limits on changes of content or context
as a result of user action.
NOTE 2: This success criterion is identical to the WCAG 2.1 Success Criterion 2.2.1 Timing Adjustable replacing"the content" with "documents" and with the words "WCAG 2.1" added before the word "Success
Criterion" in note 1 above.

ETSI

52
EN 301 549 V2.1.2 (2018-08)

10.2.2.2

Pause, stop, hide

Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.5.
Table 10.5: 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 inparallel with other content, there is a mechanism for the user to pause, stop, or hide it or to control thefrequency of the update unless the auto-updating is part of an activity where it is essential.
NOTE 1: For requirements related to flickering or flashing content, refer to WCAG 2.1 Guideline 2.3.
NOTE 2: Since any part of a document that does not meet this success criterion can interfere with a user's ability
to use the whole document, it is necessary for all content in the document (whether it is used to meetother success criteria or not) to meet this success criterion.
NOTE 3: Content that is updated periodically by software or that is streamed to the user agent is not required topreserve or present information that is generated or received between the initiation of the pause andresuming presentation, as this may not be technically possible, and in many situations could be
misleading to do so.
NOTE 4: An animation that occurs as part of a preload phase or similar situation can be considered essential ifinteraction cannot occur during that phase for all users and if not indicating progress could confuse users
or cause them to think that content was frozen or broken.
NOTE 5: This success criterion is identical to the WCAG 2.1 Success Criterion 2.2.2 Pause, Stop, Hide replacing"page" and "Web page" with "document", removing "See Conformance Requirement 5: Non-Interference"in note 2 of the success criterion, with the words "WCAG 2.1" added before the word "Guideline" innote 1 above and with note 2 above re-drafted to avoid the use of the word "must".

10.2.3

Seizures and physical reactions

10.2.3.1

Three flashes or below threshold

Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.6.
Table 10.6: Document success criterion: Three flashes or below threshold
Documents do not contain anything that flashes more than three times in any one second period, or the flash is
below the general flash and red flash thresholds.
NOTE 1: Since any part of a document that does not meet this success criterion can interfere with a user's ability
to use the whole document, it is necessary for all content in the document (whether it is used to meetother success criteria or not) to meet this success criterion.
NOTE 2: This success criterion is identical to the WCAG 2.1 Success Criterion 2.3.1 Three Flashes or Below
Threshold replacing "Web pages" with "documents", "the whole page" with "the whole document", "theWeb page" with "the document" and removing "See Conformance Requirement 5: Non-Interference" andwith note 1 above re-drafted to avoid the use of the word "must".

10.2.4

Navigable

10.2.4.1

Void

10.2.4.2

Document titled

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

ETSI

53
EN 301 549 V2.1.2 (2018-08)

Table 10.7: Document success criterion: Document titledDocuments have titles that describe topic or purpose.
NOTE 1: The name of a document (e.g. document, media file) is a sufficient title if it describes the topic or
purpose.
NOTE 2: This success criterion is identical to the WCAG 2.1 Success Criterion 2.4.2 Page Titled replacing "Webpages" with "documents" and with the addition of note 1 above.

10.2.4.3

Focus Order

Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.8.
Table 10.8: Document success criterion: Focus order
If a document can be navigated sequentially and the navigation sequences affect meaning or operation, focusable
components receive focus in an order that preserves meaning and operability.
NOTE:
This success criterion is identical to the WCAG 2.1 Success Criterion 2.4.3 Focus Order replacing "Webpage" with "document".

10.2.4.4

Link purpose (in context)

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

10.2.4.5

Void

10.2.4.6

Headings and labels

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

10.2.4.7

Focus visible

Where ICT is a non-web document, it shall satisfy the WCAG 2.1 Success Criterion 2.4.7 Focus Visible.

10.2.5

Input modalities

10.2.5.1

Pointer gestures

Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.9.
Table 10.9: Document success criterion: Pointer gestures
All functionality that uses multipoint or path-based gestures for operation can be operated with a single pointerwithout a path-based gesture, unless a multipoint or path-based gesture is essential.
NOTE 1: This requirement applies to documents that interpret pointer actions (i.e. this does not apply to actions
that are required to operate the user agent or assistive technology).
NOTE 2: This success criterion is identical to the WCAG 2.1 Success Criterion 2.5.1 Pointer Gestures replacing
the original WCAG 2.1 note with note 1 above.

10.2.5.2

Pointer cancellation

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

ETSI

54
EN 301 549 V2.1.2 (2018-08)

Table 10.10: 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 thefunction 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.
NOTE 1: Functions that emulate a keyboard or numeric keypad key press are considered essential.
NOTE 2: This requirement applies to a document that interprets pointer actions (i.e. this does not apply to actions
that are required to operate the user agent or assistive technology).
NOTE 3: This success criterion is identical to the WCAG 2.1 Success Criterion 2.5.2 Pointer Cancellation
replacing the original WCAG 2.1 note with notes 1 and 2 above.

10.2.5.3

Label in name

Where ICT is a non-web document, it shall satisfy WCAG 2.1 Success Criterion 2.5.3 Label in Name.

10.2.5.4

Motion actuation

Where ICT is a non-web document, it shall satisfy WCAG 2.1 Success Criterion 2.5.4 Motion Actuation.

10.3

Understandable

10.3.1

Readable

10.3.1.1

Language of page

Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.11.
Table 10.11: Document success criterion: Language of pageThe default human language of each document can be programmatically determined.
NOTE:
This success criterion is identical to the WCAG 2.1 Success Criterion 3.1.1 Language of Page replacing"web page" with "document".

10.3.1.2

Language of parts

Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.12.
Table 10.12: Document success criterion: Language of parts
The human language of each passage or phrase in the document can be programmatically determined except for
proper names, technical terms, words of indeterminate language, and words or phrases that have become part ofthe vernacular of the immediately surrounding text.
NOTE 1: There are some document technologies where there is no assistive technology supported method formarking the language for the different passages or phrases in the document, and it would not be possible
to meet this success criterion with those technologies.
NOTE 2: Inheritance is one common method. For example a document provides the language that it is using and it
can be assumed that all of the text or user interface elements within that document will be using thesame language unless it is indicated.
NOTE 3: This success criterion is identical to the WCAG 2.1 Success Criterion 3.1.2 Language of Parts replacing"content" with "document" and with the addition of notes 1 and 2 above.

ETSI

55
EN 301 549 V2.1.2 (2018-08)

10.3.2

Predictable

10.3.2.1

On focus

Where ICT is a non-web document, it shall satisfy the WCAG 2.1 Success Criterion 3.2.1 On Focus.
NOTE:

10.3.2.2

Some compound documents and their user agents are designed to provide significantly different viewing
and editing functionality depending upon what portion of the compound document is being interactedwith (e.g. a presentation that contains an embedded spreadsheet, where the menus and toolbars of the useragent change depending upon whether the user is interacting with the presentation content, or theembedded spreadsheet content). If the user uses a mechanism other than putting focus on that portion of
the compound document with which they mean to interact (e.g. by a menu choice or special keyboard
gesture), any resulting change of context would not be subject to this success criterion because it was notcaused by a change of focus.

On input

Where ICT is a non-web document, it shall satisfy the WCAG 2.1 Success Criterion 3.2.2 On Input.

10.3.2.3

Void

10.3.2.4

Void

10.3.310.3.3.1

Input assistance
Error identification

Where ICT is a non-web document, it shall satisfy the WCAG 2.1 Success Criterion 3.3.1 Error Identification.

10.3.3.2

Labels or instructions

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

10.3.3.3

Error suggestion

Where ICT is a non-web document, it shall satisfy the WCAG 2.1 Success Criterion 3.3.3 Error Suggestion.

10.3.3.4

Error prevention (legal, financial, data)

Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.13.
Table 10.13: Document success criterion: Error prevention (legal, financial, data)
For documents that cause legal commitments or financial transactions for the user to occur, that modify or deleteuser-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 correctthem.
3) Confirmed: A mechanism is available for reviewing, confirming, and correcting information before finalizing thesubmission.
NOTE:
This success criterion is identical to the WCAG 2.1 Success Criterion 3.3.4 Error Prevention (Legal,
Financial, Data) replacing "web pages" with "documents".

ETSI

56
EN 301 549 V2.1.2 (2018-08)

10.4

Robust

10.4.1Compatible

10.4.1.1

Parsing

Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.14.
Table 10.14: Document success criterion: Parsing
For documents that use markup languages, in such a way that the markup is separately exposed and available toassistive technologies and accessibility features of software or to a user-selectable user agent, elements havecomplete start and end tags, elements are nested according to their specifications, elements do not contain
duplicate attributes, and any IDs are unique, except where the specifications allow these features.
NOTE 1: Start and end tags that are missing a critical character in their formation, such as a closing angle bracket
or a mismatched attribute value quotation mark are not complete.
NOTE 2: Markup is not always available to assistive technology or to user selectable user agents such asbrowsers. In such cases, conformance to this provision would have no impact on accessibility as it canfor web content where it is exposed.
NOTE 3: Examples of markup that is separately exposed and available to assistive technologies and to useragents include but are not limited to: documents encoded in HTML, ODF, and OOXML. In theseexamples, the markup can be parsed entirely in two ways: (a) by assistive technologies which may
directly open the document, (b) by assistive technologies using DOM APIs of user agents for these
document formats.
NOTE 4: This success criterion is identical to the WCAG 2.1 Success Criterion 4.1.1 Parsing replacing "In content
implemented using markup languages" with "For documents that use markup languages, in such a waythat the markup is separately exposed and available to assistive technologies and accessibility featuresof software or to a user-selectable user agent" with the addition of notes 2 and 3 above.

10.4.1.2

Name, role, value

Where ICT is a non-web document, it shall satisfy the success criterion in Table 10.15.
Table 10.15: Document success criterion: Name, role, value
For all user interface components (including but not limited to: form elements, links and components generated byscripts), the name and role can be programmatically determined; states, properties, and values that can be set by
the user can be programmatically set; and notification of changes to these items is available to user agents,
including assistive technologies.
NOTE 1: This success criterion is primarily for software developers who develop or use custom user interface
components. Standard user interface components on most accessibility-supported platforms alreadymeet this success criterion when used according to specification.
NOTE 2: For document formats that support interoperability with assistive technology, standard user interface
components often meet this success criterion when used according to the general design andaccessibility guidance for the document format.
NOTE 3: This success criterion is identical to the WCAG 2.1 Success Criterion 4.1.2 Name, Role, Value replacing
the original WCAG 2.1 note with: "This success criterion is primarily for software developers who develop
or use custom user interface components. For example, standard user interface components on mostaccessibility-supported platforms already meet this success criterion when used according to
specification." and with the addition of note 2 above.

10.4.1.3

10.5

Void

Caption positioning

Where ICT is a non-web document that contains synchronized media with captions, the captions should not obscure
relevant information in the synchronized media.

ETSI

57
EN 301 549 V2.1.2 (2018-08)

10.6

Audio description timing

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

11

Software

11.0

General (informative)

This clause provides requirements for:•platform software;•

software that provides a user interface including content that is in the software;•authoring tools;•

software that operates as assistive technology.

NOTE 1: User agents are examples of software that provide a user interface.
NOTE 2: The requirements for Web content, including software that is Web content, can be found in clause 9.
NOTE 3: The requirements for documents, that may be presented by user agents, can be found in clause 10.
NOTE 4: Although the accessibility of command line interfaces is not dealt with in the present document,
accessibility may be achieved by context specific requirements, some of which may be found in clauses 5
or 11.
Requirements in clauses 11.1 to 11.5 apply to software:•that is not a web page;•

not embedded in web pages nor used in the rendering or functioning of the page.

Clause 9 provides requirements for software that is in web pages or that is embedded in web pages and that is used in
the rendering or that is intended to be rendered together with the web page in which it is embedded.
Some requirements in clauses 11.1 to 11.5 have different versions for open or closed functionality. In those cases, thecorresponding clause will be divided into two subclauses.
The success criteria set out in clauses 11.1 to 11.5 are intended to harmonize with the W3C Working Group Note [i.26]
produced by the W3C's WCAG2ICT Task Force.
NOTE 5: Software that provides a user interface includes its own content. Some examples of content in software
include: the controls and text displayed in a menu bar of a graphical user interface application, images
that appear in a toolbar, prompts spoken in an auditory user interface, other user interaction controls, andother text, graphics or material that is not loaded from outside the software.
NOTE 6: "Void" clauses have been inserted in order to maintain alignment of the numbering in clauses 9, 10 and
11.

ETSI

58
EN 301 549 V2.1.2 (2018-08)

11.1

Perceivable

11.1.1

Text alternatives

11.1.1.1

Non-text content

11.1.1.1.1

Non-text content (open functionality)

Where ICT is non-web software that provides a user interface and that supports access to assistive technologies forscreen reading, it shall satisfy WCAG 2.1 Success Criterion 1.1.1 Non-text Content.
NOTE:

11.1.1.1.2

CAPTCHAs do not currently appear outside of the Web. However, if they do appear, this guidance isaccurate.

Non-text content (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen
reading, it shall meet requirement 5.1.3.6 (Speech output for non-text content).

11.1.2
11.1.2.1
11.1.2.1.1

Time-based media
Audio-only and video-only (pre-recorded)
Audio-only and video-only (pre-recorded - open functionality)

Where ICT is non-web software that provides a user interface and that supports access to assistive technologies forscreen reading and where pre-recorded auditory information is not needed to enable the use of closed functions of ICT,it shall satisfy the WCAG 2.1 Success Criterion 1.2.1 Audio-only and Video-only (Prerecorded).
NOTE:

11.1.2.1.2
11.1.2.1.2.1

The alternative can be provided directly in the software - or provided in an alternate version that meetsthe success criterion.

Audio-only and video-only (pre-recorded - closed functionality)
Pre-recorded audio-only (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen
reading and where pre-recorded auditory information is needed to enable the use of closed functions of ICT, thefunctionality of software that provides a user interface shall meet requirement 5.1.5 (Visual output for auditory
information).
11.1.2.1.2.2

Pre-recorded video-only (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen
reading, it shall meet requirement 5.1.3.7 (Speech output for video information).

11.1.2.2

Captions (pre-recorded)

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

ETSI

59
EN 301 549 V2.1.2 (2018-08)

NOTE:

11.1.2.3
11.1.2.3.1

The WCAG 2.1 definition of "captions" notes that "in some countries, captions are called subtitles". They
are also sometimes referred to as "subtitles for the hearing impaired". Per the definition in WCAG 2.1, tomeet this success criterion, whether called captions or subtitles, they would have to provide"synchronized visual and / or text alternative for both speech and non-speech audio information needed tounderstand the media content" where non-speech information includes "sound effects, music, laughter,speaker identification and location".

Audio description or media alternative (pre-recorded)
Audio description or media alternative (pre-recorded - open functionality)

Where ICT is non-web software that provides a user interface and that supports access to assistive technologies forscreen reading, it shall satisfy the WCAG 2.1 Success Criterion 1.2.3 Audio Description or Media Alternative(Prerecorded).
NOTE 1: The WCAG 2.1 definition of "audio description" says that "audio description" is "also called 'video
description' and 'descriptive narration'".
NOTE 2: Secondary or alternate audio tracks are commonly used for this purpose.

11.1.2.3.2

Audio description or media alternative (pre-recorded - closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen
reading, it shall meet requirement 5.1.3.7 (Speech output for video information).

11.1.2.4

Captions (live)

Where ICT is non-web software that provides a user interface, it shall satisfy the WCAG 2.1 Success Criterion 1.2.4
Captions (Live).
NOTE:

11.1.2.5

The WCAG 2.1 definition of "captions" notes that "in some countries, captions are called subtitles". They
are also sometimes referred to as "subtitles for the hearing impaired". Per the definition in WCAG 2.1, tomeet this success criterion, whether called captions or subtitles, they would have to provide"synchronized visual and / or text alternative for both speech and non-speech audio information needed tounderstand the media content" where non-speech information includes "sound effects, music, laughter,speaker identification and location".

Audio description (pre-recorded)

Where ICT is non-web software that provides a user interface, it shall satisfy the WCAG 2.1 Success Criterion 1.2.5
Audio Description (Prerecorded).
NOTE 1: The WCAG 2.1 definition of "audio description" says that audio description is "Also called 'video
description' and 'descriptive narration'".
NOTE 2: Secondary or alternate audio tracks are commonly used for this purpose.

11.1.311.1.3.1
11.1.3.1.1

Adaptable
Info and relationships
Info and relationships (open functionality)

Where ICT is non-web software that provides a user interface and that supports access to assistive technologies forscreen reading, it shall satisfy the WCAG 2.1 Success Criterion 1.3.1 Info and Relationships.

ETSI

60
EN 301 549 V2.1.2 (2018-08)

NOTE:

11.1.3.1.2

In software, programmatic determinability is best achieved through the use of accessibility services
provided by platform software to enable interoperability between software and assistive technologies andaccessibility features of software. (see clause 11.5 Interoperability with assistive technology).

Info and relationships (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen
reading and where information is displayed on the screen, the ICT should provide auditory information that allows theuser to correlate the audio with the information displayed on the screen.
NOTE 1: Many people who are legally blind still have visual ability, and use aspects of the visual display even if itcannot be fully comprehended. An audio alternative that is both complete and complementary includes all
visual information such as focus or highlighting, so that the audio can be correlated with information thatis visible on the screen at any point in time.
NOTE 2: Examples of auditory information that allows the user to correlate the audio with the information
displayed on the screen include structure and relationships conveyed through presentation.

11.1.3.2
11.1.3.2.1

Meaningful sequence
Meaningful sequence (open functionality)

Where ICT is non-web software that provides a user interface and that supports access to assistive technologies forscreen reading, it shall satisfy the WCAG 2.1 Success Criterion 1.3.2 Meaningful Sequence.

11.1.3.2.2

Meaningful sequence (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen
reading and where information is displayed on the screen, the ICT should provide auditory information that allows theuser to correlate the audio with the information displayed on the screen.
NOTE 1: Many people who are legally blind still have visual ability, and use aspects of the visual display even if itcannot be fully comprehended. An audio alternative that is both complete and complementary includes all
visual information such as focus or highlighting, so that the audio can be correlated with information thatis visible on the screen at any point in time.
NOTE 2: Examples of auditory information that allows the user to correlate the audio with the information
displayed on the screen include structure and relationships conveyed through presentation.

11.1.3.3

Sensory characteristics

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

11.1.3.4

Orientation

Where ICT is non-web software that provides a user interface, it shall satisfy the WCAG 2.1 Success Criterion 1.3.4
Orientation.

11.1.3.5

Identify input purpose

Where ICT is non-web software that provides a user interface, it shall satisfy the WCAG 2.1 Success Criterion 1.3.5
Identify Input Purpose.

ETSI

61
EN 301 549 V2.1.2 (2018-08)

11.1.4

Distinguishable

11.1.4.1

Use of colour

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

11.1.4.2

Audio control

Where ICT is non-web software that provides a user interface, it shall satisfy the success criterion in Table 11.1.
Table 11.1: Software success criterion: Audio control
If any audio in a software plays automatically for more than 3 seconds, either a mechanism is available to pause orstop the audio, or a mechanism is available to control audio volume independently from the overall system volumelevel.
NOTE 1: Since any part of a software that does not meet this success criterion can interfere with a user's ability to
use the whole software, all content in the software (whether or not it is used to meet other successcriteria) shall meet this success criterion.
NOTE 2: This success criterion is identical to the WCAG 2.1 Success Criterion 1.4.2 Audio Control replacing "on aWeb page" with "in a software", "any content" with "any part of a software", "whole page" with "wholesoftware", "on the Web page" with "in the software", removing "See Conformance Requirement 5:
Non-Interference" and adding note 1.

11.1.4.3

Contrast (minimum)

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

11.1.4.4
11.1.4.4.1

Resize text
Resize text (open functionality)

Where ICT is non-web software that provides a user interface and that supports access to enlargement features ofplatform or assistive technology, it shall satisfy the WCAG 2.1 Success Criterion 1.4.4 Resize Text.
NOTE 1: Content for which there are software players, viewers or editors with a 200 percent zoom feature would
automatically meet this success criterion when used with such players, unless the content will not workwith zoom.
NOTE 2: This success criterion is about the ability to allow users to enlarge the text on screen at least up to 200 %without needing to use assistive technologies. This means that the application provides some means forenlarging the text 200 % (zoom or otherwise) without loss of content or functionality or that theapplication works with the platform features that meet this requirement.

11.1.4.4.2

Resize text (closed functionality)

Where ICT is non-web software that provides a user interface which is not able to access the enlargement features ofplatform or assistive technology, it shall meet requirement 5.1.4 (Functionality closed to text enlargement).
NOTE:

Because the text rendering support in a closed environment may be more limited than the support foundin user agents for the Web, meeting 11.1.4.4.2 in a closed environment may place a much heavier burden
on the content author.

ETSI

62
EN 301 549 V2.1.2 (2018-08)

11.1.4.5
11.1.4.5.1

Images of text
Images of text (open functionality)

Where ICT is non-web software that provides a user interface and that supports access to assistive technologies forscreen reading, it shall satisfy the WCAG 2.1 Success Criterion 1.4.5 Images of Text.

11.1.4.5.2

Images of text (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen
reading, it does not need to meet the WCAG 2.1 Success Criterion 1.4.5 Images of Text because there is no need to
impose a requirement on all closed functionality that text displayed on the screen actually be represented internally astext (as defined by WCAG 2.1), given that there is no interoperability with assistive technology.

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

11.1.4.10.1

Reflow (open functionality)

Where ICT is non-web software that provides a user interface and that supports access to assistive technologies forscreen reading, it shall satisfy the success criterion in Table 11.2.
Table 11.2: Document success criterion: Reflow (open functionality)
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.
NOTE 1: 320 CSS pixels is equivalent to a starting viewport width of 1 280 CSS pixels wide at 400 % zoom. For
non-web software which are designed to scroll horizontally (e.g. with vertical text), the 256 CSS pixels is
equivalent to a starting viewport height of 1 024 px at 400 % zoom.
NOTE 2: Examples of content which require two-dimensional layout are images, maps, diagrams, video, games,
presentations, data tables, and interfaces where it is necessary to keep toolbars in view while
manipulating content.
NOTE 3: This success criterion is identical to the WCAG 2.1 Success Criterion 1.4.10 Reflow replacing the original
WCAG 2.1 notes with notes 1 and 2, above.

11.1.4.10.2

Reflow (closed functionality)

Where ICT is non-web software that provides a user interface which is not able to access the enlargement features ofplatform or assistive technology, it shall meet requirement 5.1.4 (Functionality closed to text enlargement).

11.1.4.11

Non-text contrast

Where ICT is non-web software that provides a user interface, it shall satisfy WCAG 2.1 Success Criterion 1.4.11 Nontext Contrast.

ETSI

63
EN 301 549 V2.1.2 (2018-08)

11.1.4.12

Text spacing

Where ICT is non-web software that provides a user interface and that does not have a fixed size content layout areathat is essential to the information being conveyed, it shall satisfy WCAG 2.1 Success Criterion 1.4.12 Text spacing.

11.1.4.13

Content on hover or focus

Where ICT is a non-web software that provides a user interface, it shall satisfy WCAG 2.1 Success Criterion 1.4.13
Content on hover or focus.

11.2

Operable

11.2.1

Keyboard accessible

11.2.1.1
11.2.1.1.1

Keyboard
Keyboard (open functionality)

Where ICT is non-web software that provides a user interface and that supports access to keyboards or a keyboard
interface, it shall satisfy the WCAG 2.1 Success Criterion 2.1.1 Keyboard.
NOTE:

11.2.1.1.2

This does not imply that software is required to directly support a keyboard or "keyboard interface". Nordoes it imply that software is required to provide a soft keyboard. Underlying platform software may
provide device independent input services to applications that enable operation via a keyboard. Softwarethat supports operation via such platform device independent services would be operable by a keyboard
and would comply.

Keyboard (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to keyboards or keyboard interface, it
shall meet requirement 5.1.6.1 (Operation without keyboard interface: Closed functionality).

ETSI

64
EN 301 549 V2.1.2 (2018-08)

11.2.1.2

No keyboard trap

Where ICT is non-web software that provides a user interface, it shall satisfy the success criterion in Table 11.3.
Table 11.3: Software success criterion: No keyboard trap
If keyboard focus can be moved to a component of the software using a keyboard interface, then focus can be
moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or
tab keys or other standard exit methods, the user is advised of the method for moving focus away.
NOTE 1: Since any part of a software that does not meet this success criterion can interfere with a user's ability to
use the whole software, it is necessary for all content in the software (whether or not it is used to meetother success criteria) to meet this success criterion.
NOTE 2: Standard exit methods may vary by platform. For example, on many desktop platforms, the Escape key
is a standard method for exiting.
NOTE 3: This success criterion is identical to the WCAG 2.1 Success Criterion 2.1.2 No Keyboard Trap replacing"content", "page" and "Web page" with "software", removing "See Conformance Requirement 5: NonInterference" and with the addition of note 2 above " and with note 1 above re-drafted to avoid the use of
the word "shall".

11.2.1.3

Void

11.2.1.4

Character key shortcuts

11.2.1.4.1

Character key shortcuts (open functionality)

Where ICT is non-web software that provides a user interface, it shall satisfy WCAG 2.1 Success Criterion 2.1.4
Character Key Shortcuts.

11.2.1.4.2

Character key shortcuts (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to keyboards or keyboard interface, it
shall meet requirement 5.1.6.1 (Operation without keyboard interface: Closed functionality).

11.2.211.2.2.1

Enough time
Timing adjustable

Where ICT is non-web software that provides a user interface, it shall satisfy the success criterion in Table 11.4.
Table 11.4: Software success criterion: Timing adjustable
For each time limit that is set by the 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 witha simple action (for example, "press the space bar"), and the user is allowed to extend the time limit atleast ten times; or•
Real-time Exception: The time limit is a required part of a real-time event (for example, an auction), andno 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.
NOTE 1: This success criterion helps ensure that users can complete tasks without unexpected changes incontent or context that are a result of a time limit. This success criterion should be considered inconjunction with WCAG 2.1 Success Criterion 3.2.1, which puts limits on changes of content or context
as a result of user action.
NOTE 2: This success criterion is identical to the WCAG 2.1 Success Criterion 2.2.1 Timing Adjustable replacing"the content" with "software" and with the words "WCAG 2.1" added before the word "Success Criterion"
in note 1 above.

ETSI

65
EN 301 549 V2.1.2 (2018-08)

11.2.2.2

Pause, stop, hide

Where ICT is non-web software that provides a user interface, it shall satisfy the success criterion in Table 11.5.
Table 11.5: 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 inparallel with other content, there is a mechanism for the user to pause, stop, or hide it or to control thefrequency of the update unless the auto-updating is part of an activity where it is essential.
NOTE 1: For requirements related to flickering or flashing content, refer to WCAG 2.1 Guideline 2.3.
NOTE 2: This success criteria is applicable to all content in the software (whether or not there is an alternate
accessible mode of operation of the software) since any part of a software that does not meet thissuccess criterion can interfere with a user's ability to use the whole software (including a user interface
element that enables the user to activate the alternate accessible mode of operation).
NOTE 3: Content that is updated periodically by software or that is streamed to the user agent is not required topreserve or present information that is generated or received between the initiation of the pause andresuming presentation, as this may not be technically possible, and in many situations could be
misleading to do so.
NOTE 4: An animation that occurs as part of a preload phase or similar situation can be considered essential ifinteraction cannot occur during that phase for all users and if not indicating progress could confuse users
or cause them to think that content was frozen or broken.
NOTE 5: This is to be applied to all content. Any content, whether informative or decorative, that is updated
automatically, blinks, or moves may create an accessibility barrier.
NOTE 6: This success criterion is identical to the WCAG 2.1 Success Criterion 2.2.2 Pause, Stop, Hide replacing"page" and "Web page" with "software", removing "See Conformance Requirement 5: Non-Interference"in note 2 of the success criterion, with the words "WCAG 2.1" added before the word "Guideline" innote 1 above, with note 2 above re-drafted to avoid the use of the word "must" and with the addition ofnote 5 above.

11.2.3

Seizures and physical reactions

11.2.3.1

Three flashes or below threshold

Where ICT is non-web software that provides a user interface, it shall satisfy the success criterion in Table 11.6.
Table 11.6: Software success criterion: Three flashes or below threshold
Software does not contain anything that flashes more than three times in any one second period, or the flash is
below the general flash and red flash thresholds.
NOTE 1: This success criteria is applicable to all content in the software (whether or not there is an alternate
accessible mode of operation of the software) since any part of a software that does not meet thissuccess criterion can interfere with a user's ability to use the whole software (including a user interface
element that enables the user to activate the alternate accessible mode of operation).
NOTE 2: This success criterion is identical to the WCAG 2.1 Success Criterion 2.3.1 Three Flashes or Below
Threshold replacing "Web pages" with "software", "the whole page" with "the whole software", "the Web
page" with "the software" and removing "See Conformance Requirement 5: Non-Interference" and withnote 1 above re-drafted to avoid the use of the word "must".

ETSI

66
EN 301 549 V2.1.2 (2018-08)

11.2.4

Navigable

11.2.4.1

Void

11.2.4.2

Void

11.2.4.3

Focus order

Where ICT is non-web software that provides a user interface, it shall satisfy the success criterion in Table 11.7.
Table 11.7: Software success criterion: Focus order
If software can be navigated sequentially and the navigation sequences affect meaning or operation, focusable
components receive focus in an order that preserves meaning and operability.
NOTE:
This success criterion is identical to the WCAG 2.1 Success Criterion 2.4.3 Focus order replacing "Webpage" with "software".

11.2.4.4

Link purpose (in context)

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

11.2.4.5

Void

11.2.4.6

Headings and labels

Where ICT is non-web software that provides a user interface, it shall satisfy the WCAG 2.1 Success Criterion 2.4.6
Headings and Labels.
NOTE:

11.2.4.7

In software, headings and labels are used to describe sections of content and controls respectively. In
some cases it may be unclear whether a piece of static text is a heading or a label. But whether treated as alabel or a heading, the requirement is the same: that if they are present they describe the topic or purposeof the item(s) they are associated with.

Focus visible

Where ICT is non-web software that provides a user interface, it shall satisfy the WCAG 2.1 Success Criterion 2.4.7
Focus Visible.

11.2.5

Input modalities

11.2.5.1

Pointer gestures

Where ICT is non-web software that provides a user interface, it shall satisfy the success criterion in Table 11.8.
Table 11.8: Document success criterion: Pointer gestures
All functionality that uses multipoint or path-based gestures for operation can be operated with a single pointerwithout a path-based gesture, unless a multipoint or path-based gesture is essential.
NOTE 1: This requirement applies to non-web software that interprets pointer actions (i.e. this does not apply toactions that are required to operate the user agent or assistive technology).
NOTE 2: This success criterion is identical to the WCAG 2.1 Success Criterion 2.5.1 Pointer Gestures replacing
the original WCAG 2.1 note with note 1 above.

11.2.5.2

Pointer cancellation

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

ETSI

67
EN 301 549 V2.1.2 (2018-08)

Table 11.9: 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 thefunction 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.
NOTE 1: Functions that emulate a keyboard or numeric keypad key press are considered essential.
NOTE 2: This requirement applies to non-web software that interprets pointer actions (i.e. this does not apply toactions that are required to operate the user agent or assistive technology).
NOTE 3: This success criterion is identical to the WCAG 2.1 Success Criterion 2.5.2 Pointer Cancellation
replacing the original WCAG 2.1 note with notes 1 and 2 above.

11.2.5.3

Label in name

Where ICT is non-web software that provides a user interface, it shall satisfy WCAG 2.1 Success Criterion 2.5.3 Labelin Name.

11.2.5.4

Motion actuation

Where ICT is non-web software that provides a user interface, it shall satisfy WCAG 2.1 Success Criterion 2.5.4
Motion Actuation.

11.3

Understandable

11.3.1

Readable

11.3.1.1
11.3.1.1.1

Language of software
Language of software (open functionality)

Where ICT is non-web software that provides a user interface and that supports access to assistive technologies forscreen reading, it shall satisfy the success criterion in Table 11.10.
Table 11.10: Software success criterion: Language of software
The default human language of software can be programmatically determined.
NOTE 1: Where software platforms provide a "locale / language" setting, applications that use that setting andrender their interface in that "locale / language" would comply with this success criterion. Applications
that do not use the platform "locale / language" setting but instead use an accessibility-supported method
for exposing the human language of the software would also comply with this success criterion.
Applications implemented in technologies where assistive technologies cannot determine the humanlanguage and that do not support the platform "locale / language" setting may not be able to meet thissuccess criterion in that locale / language.
NOTE 2: This success criterion is identical to the WCAG 2.1 Success Criterion 3.1.1 Language of page, replacing"each web page" with "software" and with the addition of note 1 above.

11.3.1.1.2

Language of software (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen
reading, it shall meet requirement 5.1.3.14 (Spoken languages).

ETSI

68
EN 301 549 V2.1.2 (2018-08)

11.3.1.2

Void

11.3.2

Predictable

11.3.2.1

On focus

Where ICT is non-web software that provides a user interface, it shall satisfy the WCAG 2.1 Success Criterion 3.2.1 On
Focus.
NOTE:

11.3.2.2

Some compound documents and their user agents are designed to provide significantly different viewing
and editing functionality depending upon what portion of the compound document is being interactedwith (e.g. a presentation that contains an embedded spreadsheet, where the menus and toolbars of the useragent change depending upon whether the user is interacting with the presentation content, or theembedded spreadsheet content). If the user uses a mechanism other than putting focus on that portion of
the compound document with which they mean to interact (e.g. by a menu choice or special keyboard
gesture), any resulting change of context would not be subject to this success criterion because it was notcaused by a change of focus.

On input

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

11.3.2.3

Void

11.3.2.4

Void

11.3.311.3.3.1
11.3.3.1.1

Input assistance
Error identification
Error identification (open functionality)

Where ICT is non-web software that provides a user interface and that supports access to assistive technologies forscreen reading, it shall satisfy the WCAG 2.1 Success Criterion 3.3.1 Error Identification.

11.3.3.1.2

Error Identification (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to assistive technologies for screen
reading, it shall meet requirement 5.1.3.15 (Non-visual error identification).

11.3.3.2

Labels or instructions

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

11.3.3.3

Error suggestion

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

11.3.3.4

Error prevention (legal, financial, data)

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

ETSI

69
EN 301 549 V2.1.2 (2018-08)

Table 11.11: Software success criterion: Error prevention (legal, financial, data)
For software that cause legal commitments or financial transactions for the user to occur, that modify or delete usercontrollable 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 correctthem.
3) Confirmed: A mechanism is available for reviewing, confirming, and correcting information before finalizing thesubmission.
NOTE:
This success criterion is identical to the WCAG 2.1 Success Criterion 3.3.4 Error Prevention (Legal,
Financial, Data) replacing "web pages" with "software".

11.4

Robust

11.4.1Compatible

11.4.1.1

Parsing

11.4.1.1.1

Parsing (open functionality)

Where ICT is non-web software that provides a user interface and that supports access to any assistive technologies, it
shall satisfy the success criterion in Table 11.12.
Table 11.12: Software success criterion: Parsing
For software that uses markup languages, in such a way that the markup is separately exposed and available toassistive technologies and accessibility features of software or to a user-selectable user agent, elements havecomplete start and end tags, elements are nested according to their specifications, elements do not contain
duplicate attributes, and any IDs are unique, except where the specifications allow these features.
NOTE 1: Start and end tags that are missing a critical character in their formation, such as a closing angle bracket
or a mismatched attribute value quotation mark are not complete.
NOTE 2: Markup is not always available to assistive technology or to user selectable user agents such asbrowsers. In such cases, conformance to this provision would have no impact on accessibility as it canfor web content where it is exposed.
NOTE 3: Examples of markup that is separately exposed and available to assistive technologies and to useragents include but are not limited to: documents encoded in HTML, ODF, and OOXML. In theseexamples, the markup can be parsed entirely in two ways: (a) by assistive technologies which may
directly open the document, (b) by assistive technologies using DOM APIs of user agents for these
document formats.
NOTE 4: Examples of markup used internally for persistence of the software user interface that are never exposed
to assistive technology include but are not limited to: XUL, GladeXML, and FXML. In these examples
assistive technology only interacts with the user interface of generated software.
NOTE 5: This success criterion is identical to the WCAG 2.1 Success Criterion 4.1.1 Parsing replacing "In content
implemented using markup languages" with "For software that uses markup languages, in such a waythat the markup is separately exposed and available to assistive technologies and accessibility featuresof software or to a user-selectable user agent" with the addition of notes 2, 3 and 4 above.

11.4.1.1.2

Parsing (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to all assistive technology it shall nothave to meet the "Parsing" success criterion in Table 11.10 because the intent of this success criterion is to provide
consistency so that different user agents or assistive technologies will yield the same result.

ETSI

70
EN 301 549 V2.1.2 (2018-08)

11.4.1.2
11.4.1.2.1

Name, role, value
Name, role, value (open functionality)

Where ICT is non-web software that provides a user interface and that supports access to any assistive technologies, it
shall satisfy the success criterion in Table 11.13.
Table 11.13: Software success criterion: Name, role, value
For all user interface components (including but not limited to: form elements, links and components generated byscripts), the name and role can be programmatically determined; states, properties, and values that can be set by
the user can be programmatically set; and notification of changes to these items is available to user agents,
including assistive technologies.
NOTE 1: This success criterion is primarily for software developers who develop or use custom user interface
components. Standard user interface components on most accessibility-supported platforms alreadymeet this success criterion when used according to specification.
NOTE 2: For conforming to this success criterion, it is usually best practice for software user interfaces to use theaccessibility services provided by platform software. These accessibility services enable interoperability
between software user interfaces and both assistive technologies and accessibility features of softwarein standardised ways. Most platform accessibility services go beyond programmatic exposure of nameand role, and programmatic setting of states, properties and values (and notification of same), andspecify additional information that could or should be exposed and / or set (for instance, a list of theavailable actions for a given user interface component, and a means to programmatically execute one of
the listed actions).
NOTE 3: This success criterion is identical to the WCAG 2.1 Success Criterion 4.1.2 Name, Role, Value replacing
the original WCAG 2.1 note with: "This success criterion is primarily for software developers who develop
or use custom user interface components. Standard user interface components on most accessibilitysupported platforms already meet this success criterion when used according to specification." and the
addition of note 2 above.

11.4.1.2.2

Name, role, value (closed functionality)

Where ICT is non-web software that provides a user interface which is closed to all assistive technology it shall nothave to meet the "Name, role, value" success criterion in Table 11.11 because this success criterion requires information
in a programmatically determinable form.

11.4.1.3

Void

11.5

Interoperability with assistive technology

11.5.1

Closed functionality

Where the closed functionality of software conforms to clause 5.1 (Closed functionality) it shall not be required toconform with clause 11.5.2 to clause 11.5.2.17.

11.5.2
11.5.2.1

Accessibility services
Platform accessibility service support for software that provides a userinterface

Platform software shall provide a set of documented platform services that enable software that provides a user interface
running on the platform software to interoperate with assistive technology.
Platform software should support requirements 11.5.2.5 to 11.5.2.17 except that, where a user interface concept that
corresponds to one of the clauses 11.5.2.5 to 11.5.2.17 is not supported within the software environment, theserequirements are not applicable. For example, selection attributes from 11.5.2.14 (Modification of focus and selection
attributes) may not exist in environments that do not allow selection, which is most commonly associated with copy andpaste.

ETSI

71
EN 301 549 V2.1.2 (2018-08)

NOTE 1: These define the minimum functionality of software providing user interfaces when using platform
services.
NOTE 2: In some platforms these services may be called accessibility services, but in some other platforms these
services may be provided as part of the user interface services.
NOTE 3: User interface services that provide accessibility support by default are considered to be part of theservices provided to conform to this clause (e.g. the service for creating a new user interface element
provides role, state, boundary, name and description).
NOTE 4: To comply with this requirement the platform software can provide its own set of services or expose theservices provided by its underlying platform layers, if those services conform to this requirement.
NOTE 5: Within specific programming environments, the technical attributes associated with the user interface
properties described in clauses 11.5.2.5 to 11.5.2.17 might have different names than those used within
the clauses.

11.5.2.2

Platform accessibility service support for assistive technologies

Platform software shall provide a set of documented platform accessibility services that enable assistive technology tointeroperate with software that provides a user interface running on the platform software.
Platform software should support the requirements of clauses 11.5.2.5 to 11.5.2.17 except that, where a user interface
concept that corresponds to one of the clauses 11.5.2.5 to 11.5.2.17 is not supported within the software environment,these requirement are not applicable. For example, selection attributes from 11.5.2.14 (Modification of focus andselection attributes) may not exist in environments that do not allow selection, which is most commonly associated withcopy and paste.
NOTE 1: These define the minimum functionality available to assistive technologies when using platform services.
NOTE 2: The definition of platform in clause 3.1 applies to software that provides services to other software,
including but not limited to, operating systems, web browsers, virtual machines.
NOTE 3: In some platforms these services may be called accessibility services, but in some other platforms these
services may be provided as part of the user interface services.
NOTE 4: Typically these services belong to the same set of services that are described in clause 11.5.2.1.
NOTE 5: To comply with this requirement the platform software can provide its own set of services or expose theservices provided by its underlying platform layers, if those services conform to this requirement.

11.5.2.3

Use of accessibility services

Where the software provides a user interface it shall use the applicable documented platform accessibility services. If
the documented platform accessibility services do not allow the software to meet the applicable requirements ofclauses 11.5.2.5 to 11.5.2.17, then software that provides a user interface shall use other documented services tointeroperate with assistive technology.
NOTE:

The term "documented platform accessibility services" refers to the set of services provided by theplatform according to clauses 11.5.2.1 and 11.5.2.2.

It is best practice to develop software using toolkits that automatically implement the underlying platform accessibility
services.

11.5.2.4

Assistive technology

Where the ICT is assistive technology it shall use the documented platform accessibility services.
NOTE 1: The term "documented platform accessibility services" refers to the set of services provided by theplatform according to clauses 11.5.2.1 and 11.5.2.2.
NOTE 2: Assistive technology can also use other documented accessibility services.

ETSI

72
EN 301 549 V2.1.2 (2018-08)

11.5.2.5

Object information

Where the software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make the userinterface elements' role, state(s), boundary, name, and description programmatically determinable by assistive
technologies.

11.5.2.6

Row, column, and headers

Where the software provides a user interface it 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, programmaticallydeterminable by assistive technologies.

11.5.2.7

Values

Where the software provides a user interface, it shall, by using the services as described in clause 11.5.2.3, make thecurrent 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.

11.5.2.8

Label relationships

Where the software provides a user interface it shall expose the relationship that a user interface element has as a label
for another element, or of being labelled by another element, using the services as described in clause 11.5.2.3, so that
this information is programmatically determinable by assistive technologies.

11.5.2.9

Parent-child relationships

Where the software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make therelationship between a user interface element and any parent or children elements programmatically determinable byassistive technologies.

11.5.2.10

Text

Where the software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make the text
contents, text attributes, and the boundary of text rendered to the screen programmatically determinable by assistive
technologies.

11.5.2.11

List of available actions

Where the software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make a list ofavailable actions that can be executed on a user interface element, programmatically determinable by assistive
technologies.

11.5.2.12

Execution of available actions

Where permitted by security requirements, software that provides a user interface 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 byassistive technologies.
NOTE 1: In some cases the security requirements imposed on a software product may forbid external software frominterfering with the ICT product. Examples of systems under strict security requirements are systems
dealing with intelligence activities, cryptologic activities related to national security, command andcontrol of military forces.
NOTE 2: Assistive technologies may be required to maintain the same level of security as the standard input
mechanisms supported by the platform.

ETSI

73
EN 301 549 V2.1.2 (2018-08)

11.5.2.13

Tracking of focus and selection attributes

Where software provides a user interface it shall, by using the services as described in clause 11.5.2.3, makeinformation and mechanisms necessary to track focus, text insertion point, and selection attributes of user interface
elements programmatically determinable by assistive technologies.

11.5.2.14

Modification of focus and selection attributes

Where permitted by security requirements, software that provides a user interface shall, by using the services as
described in clause 11.5.2.3, allow assistive technologies to programmatically modify focus, text insertion point, andselection attributes of user interface elements where the user can modify these items.
NOTE 1: In some cases the security requirements imposed on a software product may forbid external software frominterfering with the ICT product and so this requirement would not apply. Examples of systems understrict security requirements are systems dealing with intelligence activities, cryptologic activities related
to national security, command and control of military forces.
NOTE 2: Assistive technologies may be required to maintain the same level of security as the standard input
mechanisms supported by the platform.

11.5.2.15

Change notification

Where software provides a user interface it 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 arereferenced in requirements 11.5.2.5 to 11.5.2.11 and 11.5.2.13.

11.5.2.16

Modifications of states and properties

Where permitted by security requirements, software that provides a user interface shall, by using the services as
described in clause 11.5.2.3, allow assistive technologies to programmatically modify states and properties of userinterface elements, where the user can modify these items.
NOTE 1: In some cases the security requirements imposed on a software product may forbid external software frominterfering with the ICT product and so this requirement would not apply. Examples of systems understrict security requirements are systems dealing with intelligence activities, cryptologic activities related
to national security, command and control of military forces.
NOTE 2: Assistive technologies may be required to maintain the same level of security as the standard input
mechanisms supported by the platform.

11.5.2.17

Modifications of values and text

Where permitted by security requirements, software that provides a user interface 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.
NOTE 1: In some cases the security requirements imposed on a software product may forbid external software frominterfering with the ICT product and so this requirement would not apply. Examples of systems understrict security requirements are systems dealing with intelligence activities, cryptologic activities related
to national security, command and control of military forces.
NOTE 2: Assistive technologies may be required to maintain the same level of security as the standard input
mechanisms supported by the platform.

ETSI

74
EN 301 549 V2.1.2 (2018-08)

11.6

Documented accessibility usage

11.6.1

User control of accessibility features

Where software is a platform it shall provide sufficient modes of operation for user control over those platform
accessibility features documented as intended for users.

11.6.2

No disruption of accessibility features

Where software provides a user interface it shall not disrupt those documented accessibility features that are defined inplatform documentation except when requested to do so by the user during the operation of the software.

11.7

User preferences

Where software provides a user interface it shall provide sufficient modes of operation that use user preferences forplatform settings for colour, contrast, font type, font size, and focus cursor except for software that is designed to beisolated from its underlying platforms.
NOTE:

Software that is isolated from its underlying platform has no access to user settings in the platform andthus cannot adhere to them.

11.8

Authoring tools

11.8.1

Content technology

Authoring tools shall conform to clauses 11.8.2 to 11.8.5 to the extent that information required for accessibility is
supported by the format used for the output of the authoring tool.

11.8.2

Accessible content creation

Authoring tools shall enable and guide the production of content that conforms to clauses 9 (Web content) or 10(Non-Web content) as applicable.
NOTE:

11.8.3

Authoring tools may rely on additional tools where conformance with specific requirements is notachievable by a single tool. For example, a video editing tool may enable the creation of video files for
distribution via broadcast television and the web, but authoring of caption files for multiple formats may
be provided by a different tool.

Preservation of accessibility information in transformations

If the authoring tool provides restructuring transformations or re-coding transformations, then accessibility information
shall be preserved in the output if equivalent mechanisms exist in the content technology of the output.
NOTE 1: Restructuring transformations are transformations in which the content technology stays the same, but thestructural features of the content are changed (e.g. linearizing tables, splitting a document into pages).
NOTE 2: Re-coding transformations are transformations in which the technology used to encode the content ischanged.

11.8.4

Repair assistanceIf the accessibility checking functionality of an authoring tool can detect that content does not meet a requirement ofclauses 9 (Web) or 10 (Non-web documents) as applicable, then the authoring tool shall provide repair suggestion(s).

ETSI

75
EN 301 549 V2.1.2 (2018-08)

NOTE:

11.8.5This does not preclude automated and semi-automated repair which is possible (and encouraged) for
many types of content accessibility problems.

Templates

When an authoring tool provides templates, at least one template that supports the creation of content that conforms to
the requirements of clauses 9 (Web) or 10 (Non-web documents) as applicable shall be available and identified as such.

ETSI

76
EN 301 549 V2.1.2 (2018-08)

12Documentation and support services

12.1

Product documentation

12.1.1

Accessibility and compatibility features

Product documentation provided with the ICT whether provided separately or integrated within the ICT shall list andexplain how to use the accessibility and compatibility features of the ICT.
NOTE:

12.1.2

Accessibility and compatibility features include accessibility features that are built-in and accessibility
features that provide compatibility with assistive technology.

Accessible documentation

Product documentation provided with the ICT shall be made available in at least one of the following electronic
formats:a)a Web format that conforms to the requirements of clause 9, orb)

a non-web format that conforms to the requirements of clause 10.

NOTE 1: This does not preclude the possibility of also providing the product documentation in other formats(electronic or printed) that are not accessible.
NOTE 2: It also does not preclude the possibility of providing alternate formats that meet the needs of somespecific type of users (e.g. Braille documents for blind people or easy-to-read information for persons
with cognitive impairments).
NOTE 3: Where the documentation is integral to the ICT it will be provided through the user interface which isaccessible.
NOTE 4: A user agent that supports automatic media conversion would be beneficial to enhancing accessibility.

12.2

Support services

12.2.1

General (informative)

ICT support services include, but are not limited to: help desks, call centres, technical support, relay services andtraining services.

12.2.2

Information on accessibility and compatibility features

ICT support services shall provide information on the accessibility and compatibility features that are included in the
product documentation.
NOTE:

12.2.3

Accessibility and compatibility features include accessibility features that are built-in and accessibility
features that provide compatibility with assistive technology.

Effective communication

ICT support services shall accommodate the communication needs of individuals with disabilities either directly or
through a referral point.

ETSI

77
EN 301 549 V2.1.2 (2018-08)

12.2.4

Accessible documentation

Documentation provided by support services shall be made available in at least one of the following electronic formats:a)a Web format that conforms to clause 9; orb)a non-web format that conforms to clause 10.

NOTE 1: This does not preclude the possibility of also providing the documentation in other formats (electronic or
printed) that are not accessible.
NOTE 2: It also does not preclude the possibility of providing alternate formats that meet the needs of somespecific type of users (e.g. Braille documents for blind people or easy-to-read information for persons
with cognitive impairments).
NOTE 3: A user agent that supports automatic media conversion would be beneficial to enhancing accessibility.

ETSI

78
EN 301 549 V2.1.2 (2018-08)

13

ICT providing relay or emergency service access

13.1

Relay services requirements

13.1.1

General (informative)

Relay services enable users of different modes of communication e.g. text, sign, speech, to interact remotely throughICT with two-way communication by providing conversion between the modes of communication, normally by ahuman operator.
It is best practice to meet the applicable relay service requirements of ETSI ES 202 975 [i.5].

13.1.2

Text relay services

Where ICT is intended to provide a text relay service, the text relay service shall enable text users and speech users tointeract by providing conversion between the two modes of communication.

13.1.3Sign relay services

Where ICT is intended to provide a sign relay service, the sign relay service shall enable sign language users and speechusers to interact by providing conversion between the two modes of communication.
NOTE:

13.1.4Sign relay services are also sometimes referred to as sign language relay services or video relay services.

Lip-reading relay services

Where ICT is intended to provide a lip-reading relay service, the lip-reading service shall enable lip-readers and voice
telephone users to interact by providing conversion between the two modes of communication.

13.1.5

Captioned telephony services

Where ICT is intended to provide a captioned telephony service, the captioned telephony service shall assist a deaf or
hard of hearing user in a spoken dialogue by providing text captions translating the incoming part of the conversation.

13.1.6

Speech to speech relay services

Where ICT is intended to provide a speech to speech relay service, the speech to speech relay service shall enablespeech or cognitively impaired telephone users and any other user to communicate by providing assistance between
them.

13.2

Access to relay services

Where ICT systems support two-way communication and a set of relay services for such communication is specified,access to those relay services shall not be prevented for outgoing and incoming calls.
NOTE 1: Two-way communication may include voice, real-time text, or video, singly or in combinations supported
by both the relay service and the ICT system.
NOTE 2: The purpose of this requirement is to achieve functionally equivalent communication access by persons
with disabilities.

ETSI

79
EN 301 549 V2.1.2 (2018-08)

13.3

Access to emergency services

Where ICT systems support two-way communication and a set of emergency services for such communication is
specified, access to those emergency services shall not be prevented for outgoing and incoming calls.
NOTE 1: Two-way communication may include voice, real-time text, or video, singly or in combinations supported
by both the emergency service and the ICT system.
NOTE 2: The purpose of this requirement is to achieve functionally equivalent communication access to theemergency service by persons with disabilities.

ETSI

80
EN 301 549 V2.1.2 (2018-08)

Annex A (informative):
Relationship between the present document and theessential requirements of Directive 2016/2102
The present document has been prepared under the Commission's standardisation request C(2017) 2585 final [i.27] toprovide one voluntary means of conforming to the essential requirements of Directive 2016/2102 [i.28] on theaccessibility of the websites and mobile applications of public sector bodies.
Once the present document is cited in the Official Journal of the European Union under that Directive, compliance with
the normative clauses of the present document given in tables A.1 and A.2 confers, within the limits of the scope of thepresent document, a presumption of conformity with the corresponding essential requirements of that Directive andassociated EFTA regulations.
The requirements listed in Table A.1 apply to web pages (as defined in clause 3.1) including:•documents that are web pages;•

documents that are embedded in web pages and that are used in the rendering or that are intended to berendered together with the web page in which they are embedded;•

software that is a web page; or•software 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.

The requirements listed in Table A.2 apply to mobile applications that provide a user interface including content that isin the software.
NOTE 1: According to Directive 2016/2102 [i.28]: "Content of websites and mobile applications includes textual aswell as non-textual information, downloadable documents and forms, and two-way interaction such as theprocessing of digital forms and the completion of authentication, identification and payment processes."
NOTE 2: Annex A is a required element in all Harmonised standards. Its purpose is to explain how the essential
requirements of a Directive can be met. Tables A.1 and A.2 are therefore restricted to those elements that
relate to the essential requirements of Directive 2016/2102 [i.28].
Key to Table A.1 and A.2 columns:
Requirement:No

A unique identifier for one row of the table which may be used to identify a requirement.

Essential requirements of Directive
Identification of article(s) defining the requirement in the Directive.
Clause(s) of the present document
Identification of clause(s) defining the requirement in the present document unless anotherdocument is referenced explicitly.
Requirement Conditionality:
U/C"U" indicates that compliance with the clause is unconditionally required.
"C" indicates that compliance with the clause is required only if the specified condition is met.

Condition

For conditional requirements this column describes the condition that has to be met for compliancewith the clause to be a requirement.

ETSI

81
EN 301 549 V2.1.2 (2018-08)

Assessment:
Indicates the clause of the present document that contains the relevant assessment method.
Presumption of conformity stays valid only as long as a reference to the present document is maintained in the list
published in the Official Journal of the European Union. Users of the present document should consult frequently thelatest list published in the Official Journal of the European Union.
Other Union legislation may be applicable to the product(s) falling within the scope of the present document.
Table A.1: Web Pages - relationship between the present document andthe essential requirements of Directive 2016/2102/EU
Requirement

Requirement conditionality

No.

Clause of the present
document

Perceivable

Operable

Understandable

RobustConditional or
Unconditional

Essential
requirements of
Directive

1

5.2 Activation of accessibility
features

✓

✓

✓

✓

C

2

5.3 Biometrics

Condition

Assessment

Clause of thepresent
document✓

C

Where ICT has documented accessibility
features
Where ICT uses biologicalcharacteristics
Where ICT converts information orcommunication
Where ICT has operable parts

✓

✓

C

Where ICT has operable parts

5.6.1 Tactile or auditory status

✓

✓

C

7

5.6.2 Visual status

✓

✓

C

8

5.7 Key repeat

✓

C

9

5.8 Double-strike key
acceptance

✓

C

10

5.9 Simultaneous user actions

✓

C

11

6.1 Audio bandwidth for speech

✓

C

12

6.2.1 RTT provision

✓

C

13

6.2.2 Display of Real-time Text

✓

C

14

6.2.3 Interoperability

✓

C

15

6.2.4 Real-time text
responsiveness

✓

C

16

6.3 Caller ID✓

17

6.5.2 Resolution item a)

✓

✓

C

18

6.5.3 Frame rate item a)

✓

✓

C

19

7.1.1 Captioning playback
7.1.2 Captioning
synchronization
7.1.3 Preservation of captioning✓

C

Where ICT uses simultaneous user
actions for its operation
Where ICT provides two-way voicecommunication
Where ICT supports two-way voicecommunication
Where ICT provides two-way voicecommunication
Where ICT provides two-way voicecommunication
Where ICT provides two-way voicecommunication
Where ICT provides two-way voicecommunication
Where ICT provides two-way voicecommunication
Where ICT provides two-way voicecommunication
Where ICT has video capabilities✓

C

Where ICT has video capabilities

C.7.1.2✓

C

Where ICT has video capabilities

C.7.1.3✓

5.4 Preservation of accessibility
information during conversion
5.5.1 Means of operation
5.5.2 Operable parts
discernibility

✓

6

3
4
5

20
21

C
✓

✓

✓

✓

✓

C

C

ETSI

Where ICT has a locking or toggle
control
Where ICT has a locking or toggle
control
Where ICT has a key repeat functionthat cannot be turned off
Where ICT has a keyboard or keypad

C.5.2
C.5.3
C.5.4
C.5.5.1
C.5.5.2
C.5.6.1
C.5.6.2
C.5.7
C.5.8
C.5.9
C.6.1
C.6.2.1
C.6.2.2
C.6.2.3
C.6.2.4
C.6.3
C.6.5.2
C.6.5.3
C.7.1.1

82
EN 301 549 V2.1.2 (2018-08)

Requirement conditionality

22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62

Assessment

Clause of thepresent
document✓

C

Where ICT has video capabilities

C.7.2.1✓

C

Where ICT has video capabilities

C.7.2.2✓

C

Where ICT has video capabilities

C.7.2.3

C

Where ICT has video capabilities

C.7.3

✓

✓

Robust7.2.1 Audio description
playback
7.2.2 Audio description
synchronization
7.2.3 Preservation of audio
description
7.3 User controls for captions
and audio description
9.1.1.1 Non-text content
9.1.2.1 Audio-only and videoonly (pre-recorded)
9.1.2.2 Captions (pre-recorded)
9.1.2.3 Audio description or
media alternative (prerecorded)
9.1.2.4 Captions (live)
9.1.2.5 Audio description (prerecorded)
9.1.3.1 Info and relationships
9.1.3.2 Meaningful sequence
9.1.3.3 Sensory characteristics
9.1.3.4 Orientation
9.1.3.5 Identify input purpose
9.1.4.1 Use of colour
9.1.4.2 Audio control
9.1.4.3 Contrast (minimum)
9.1.4.4 Resize text
9.1.4.5 Images of text
9.1.4.10 Reflow
9.1.4.11 Non-text contrast
9.1.4.12 Text spacing
9.1.4.13 Content on hover or
focus
9.2.1.1 Keyboard
9.2.1.2 No keyboard trap
9.2.1.4 Character key shortcuts
9.2.2.1 Timing adjustable
9.2.2.2 Pause, stop, hide
9.2.3.1 Three flashes or below
threshold
9.2.4.1 Bypass blocks
9.2.4.2 Page titled9.2.4.3 Focus Order
9.2.4.4 Link purpose (incontext)
9.2.4.5 Multiple ways
9.2.4.6 Headings and labels
9.2.4.7 Focus visible
9.2.5.1 Pointer gestures
9.2.5.2 Pointer cancellation
9.2.5.3 Label in name
9.2.5.4 Motion actuation

Operable

Clause of the present
document

Perceivable

No.

Understandable

Essential
requirements of
Directive

Conditional or
Unconditional

Requirement

Condition✓

U

C.9.1.1.1✓

U

C.9.1.2.1✓

U

C.9.1.2.2✓

U

C.9.1.2.3✓

U

C.9.1.2.4✓

U

C.9.1.2.5

✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓

✓

U
U
U
U
U
U
U
U
U
U
U
U
U

✓

U

C.9.1.3.1
C.9.1.3.2
C.9.1.3.3
C.9.1.3.4
C.9.1.3.5
C.9.1.4.1
C.9.1.4.2
C.9.1.4.3
C.9.1.4.4
C.9.1.4.5
C.9.1.4.10
C.9.1.4.11
C.9.1.4.12
C.9.1.4.13

✓
✓
✓
✓
✓

U
U
U
U
U

C.9.2.1.1
C.9.2.1.2
C.9.2.1.4
C.9.2.2.1
C.9.2.2.2✓

U

C.9.2.3.1

✓
✓
✓

U
U
U

C.9.2.4.1
C.9.2.4.2
C.9.2.4.3✓

U

C.9.2.4.4

✓
✓
✓
✓
✓
✓
✓

U
U
U
U
U
U
U

C.9.2.4.5
C.9.2.4.6
C.9.2.4.7
C.9.2.5.1
C.9.2.5.2
C.9.2.5.3
C.9.2.5.4

✓

✓
✓

ETSI

83
EN 301 549 V2.1.2 (2018-08)

Requirement conditionality

63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87

9.3.1.1 Language of page
9.3.1.2 Language of parts
9.3.2.1 On focus
9.3.2.2 On input
9.3.2.3 Consistent navigation
9.3.2.4 Consistent identification
9.3.3.1 Error identification
9.3.3.2 Labels or instructions
9.3.3.3 Error suggestion
9.3.3.4 Error prevention (legal,financial, data)
9.4.1.1 Parsing
9.4.1.2 Name, role, value
9.4.1.3 Status messages
11.6.2 No disruption ofaccessibility features
11.7 User preferences
11.8.1 Content technology
11.8.2 Accessible content
creation
11.8.3 Preservation ofaccessibility information intransformations
11.8.4 Repair assistance
11.8.5 Templates
12.1.1 Accessibility andcompatibility features
12.1.2 Accessible
documentation
12.2.2 Information onaccessibility and compatibility
features12.2.3 Effective communication
12.2.4 Accessible
documentation

RobustUnderstandable

Clause of the present
document

Operable

No.

Perceivable

Essential
requirements of
Directive

Conditional or
Unconditional

Requirement

✓
✓
✓
✓
✓
✓
✓
✓
✓

U
U
U
U
U
U
U
U
U

✓

U

Condition

Assessment

Clause of thepresent
document

C.9.3.1.1
C.9.3.1.2
C.9.3.2.1
C.9.3.2.2
C.9.3.2.3
C.9.3.2.4
C.9.3.3.1
C.9.3.3.2
C.9.3.3.3
C.9.3.3.4

✓

✓

✓

✓
✓
✓

✓

✓

✓

✓

U

✓
✓

✓
✓

✓
✓

✓
✓

U
C

Where ICT is an authoring tool

C.11.7C.11.8.1

✓

✓

✓

✓

C

Where ICT is an authoring tool

C.11.8.2

✓

✓

✓

✓

C

Where ICT is an authoring tool

C.11.8.3

✓
✓

✓
✓

✓
✓

✓
✓

C
C

Where ICT is an authoring tool
Where ICT is an authoring tool

C.11.8.4
C.11.8.5

✓

✓

✓

✓

U

C.12.1.1

✓

✓

✓

✓

U

C.12.1.2

✓

✓

✓

✓

U

C.12.2.2

U

C.12.2.3

U

C.12.2.4

✓
✓

✓
✓

✓

✓

U
U
U

C.4.1.1
C.4.1.2
C.4.1.3
C.11.6.2

ETSI

84
EN 301 549 V2.1.2 (2018-08)

Table A.2: Mobile Applications - relationship between the present document andthe essential requirements of Directive 2016/2102/EU
Requirement

Requirement conditionality

No.

Clause of the present
document

Perceivable

Operable

Understandable

RobustConditional or
Unconditional

Essential
requirements of
Directive

1

5.2 Activation of accessibility
features

✓

✓

✓

✓

C

2

5.3 Biometrics✓

C

Condition

Assessment

Clause of thepresent
document

Where ICT has documented accessibility
C.5.2
features
Where ICT uses biological
C.5.3
characteristics
Where ICT converts information or
C.5.4
communication

5.4 Preservation of accessibility
information during conversion
5.5.2 Operable parts
discernibility

✓
✓

✓

C

5

5.6.1 Tactile or auditory status

✓

✓

C

6

5.6.2 Visual status

✓

✓

C

7

5.7 Key repeat

✓

C

8

5.8 Double-strike key
acceptance

✓

C

9

5.9 Simultaneous user actions

✓

C

10

6.1 Audio bandwidth for speech

✓

C

11

6.2.1 RTT provision

✓

C

12

6.2.2 Display of Real-time Text

✓

C

13

6.2.3 Interoperability

✓

C

14

6.2.4 Real-time text
responsiveness

✓

C

15

6.3 Caller ID✓

16

6.5.2 Resolution item a)

✓

✓

C

17

6.5.3 Frame rate item a)

✓

✓

C

18

7.1.1 Captioning playback
7.1.2 Captioning
synchronization
7.1.3 Preservation of captioning
7.2.1 Audio description
playback
7.2.2 Audio description
synchronization
7.2.3 Preservation of audio
description
7.3 User controls for captions
and audio description
11.1.1.1.1 Non-text content(open functionality)
11.1.1.1.2 Non-text content(closed functionality)✓

C

Where ICT uses simultaneous user
actions for its operation
Where ICT provides two-way voicecommunication
Where ICT supports two-way voicecommunication
Where ICT provides two-way voicecommunication
Where ICT provides two-way voicecommunication
Where ICT provides two-way voicecommunication
Where ICT provides two-way voicecommunication
Where ICT provides two-way voicecommunication
Where ICT provides two-way voicecommunication
Where ICT has video capabilities✓

C

Where ICT has video capabilities

C.7.1.2✓

C

Where ICT has video capabilities

C.7.1.3✓

C

Where ICT has video capabilities

C.7.2.1✓

C

Where ICT has video capabilities

C.7.2.2✓

C

Where ICT has video capabilities

C.7.2.3

C

Where ICT has video capabilities

C.7.3

3
4

19
20
21
22
23
24
25
26

✓

✓

✓

✓

✓

✓

✓

C

C

Where ICT has operable parts
Where ICT has a locking or toggle
control
Where ICT has a locking or toggle
control
Where ICT has a key repeat functionthat cannot be turned off
Where ICT has a keyboard or keypad

C.5.5.2
C.5.6.1
C.5.6.2
C.5.7
C.5.8
C.5.9
C.6.1
C.6.2.1
C.6.2.2
C.6.2.3
C.6.2.4
C.6.3
C.6.5.2
C.6.5.3
C.7.1.1✓

U

C.11.1.1.1.1✓

U

C.11.1.1.1.2

ETSI

85
EN 301 549 V2.1.2 (2018-08)

Requirement conditionality

27

28
29
30

31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55

11.1.2.1.1 Audio-only andvideo-only (pre-recorded - open
functionality)
11.1.2.1.2 Audio-only andvideo-only (pre-recorded closed functionality)
11.1.2.2 Captions (prerecorded)
11.1.2.3.1 Audio description or
media alternative (pre-recorded- open functionality)
11.1.2.3.2 Audio description or
media alternative (pre-recorded- closed functionality)
11.1.2.4 Captions (live)
11.1.2.5 Audio description (prerecorded)
11.1.3.1.1 Info andrelationships (openfunctionality)
11.1.3.2.1 Meaningful
sequence (open functionality)
11.1.3.3 Sensory
characteristics
11.1.3.4 Orientation
11.1.3.5 Identify input purpose
11.1.4.1 Use of colour
11.1.4.2 Audio control
11.1.4.3 Contrast (minimum)
11.1.4.4.1 Resize text (openfunctionality)
11.1.4.4.2 Resize text (closed
functionality)
11.1.4.5.1 Images of text (openfunctionality)
11.1.4.10.1 Reflow (openfunctionality)
11.1.4.10.2 Reflow (closed
functionality)
11.1.4.11 Non-text contrast
11.1.4.12 Text spacing
11.1.4.13 Content on hover or
focus
11.2.1.1.1 Keyboard (openfunctionality)
11.2.1.1.2 Keyboard (closed
functionality)
11.2.1.2 No keyboard trap
11.2.1.4.1 Character key
shortcuts (open functionality)
11.2.1.4.2 Character key
shortcuts (closed functionality)
11.2.2.1 Timing adjustable

RobustUnderstandable

Clause of the present
document

Operable

No.

Perceivable

Essential
requirements of
Directive

Conditional or
Unconditional

Requirement

Condition

Assessment

Clause of thepresent
document✓

U

C.11.1.2.1.1✓

U

C.11.1.2.1.2✓

U

C.11.1.2.2✓

U

C.11.1.2.3.1✓

U

C.11.1.2.3.2✓

U

C.11.1.2.4✓

U

C.11.1.2.5✓

U

C.11.1.3.1.1✓

U

C.11.1.3.2.1✓

U

C.11.1.3.3

U
U
U
U

C.11.1.3.4
C.11.1.3.5
C.11.1.4.1
C.11.1.4.2
C.11.1.4.3✓

U

C.11.1.4.4.1✓

U

C.11.1.4.4.2✓

U

C.11.1.4.5.1

✓

U

✓

U

✓
✓
✓
✓
✓

✓

C.11.1.4.10.1
C.11.1.4.10.2

✓
✓

✓

U

C.11.1.4.11
C.11.1.4.12

✓

✓

U

C.11.1.4.13✓

U

C.11.2.1.1.1✓

U

C.11.2.1.1.2✓

U

C.11.2.1.2✓

U

C.11.2.1.4.1✓

U

C.11.2.1.4.2✓

U

C.11.2.2.1

ETSI

86
EN 301 549 V2.1.2 (2018-08)

Requirement conditionality

56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89

11.2.2.2 Pause, stop, hide
11.2.3.1 Three flashes or below
threshold11.2.4.3 Focus order
11.2.4.4 Link purpose (incontext)
11.2.4.6 Headings and labels
11.2.4.7 Focus visible
11.2.5.1 Pointer gestures
11.2.5.2 Pointer cancellation
11.2.5.3 Label in name11.2.5.4 Motion actuation
11.3.1.1.1 Language ofsoftware (open functionality)
11.3.1.1.2 Language ofsoftware (closed functionality)
11.3.2.1 On focus
11.3.2.2 On input
11.3.3.1.1 Error identification(open functionality)
11.3.3.1.2 Error Identification(closed functionality)
11.3.3.2 Labels or instructions
11.3.3.3 Error suggestion
11.3.3.4 Error prevention (legal,financial, data)
11.4.1.1.1 Parsing (openfunctionality)
11.4.1.2.1 Name, role, value(open functionality)
11.5.2.3 Use of accessibility
services
11.5.2.5 Object information
11.5.2.6 Row, column, andheaders
11.5.2.7 Values
11.5.2.8 Label relationships
11.5.2.9 Parent-childrelationships
11.5.2.10 Text
11.5.2.11 List of available
actions
11.5.2.12 Execution of available
actions
11.5.2.13 Tracking of focus andselection attributes
11.5.2.14 Modification of focus
and selection attributes
11.5.2.15 Change notification
11.5.2.16 Modifications ofstates and properties✓

RobustUnderstandable

Clause of the present
document

Operable

No.

Perceivable

Essential
requirements of
Directive

Conditional or
Unconditional

Requirement

Condition

Assessment

Clause of thepresent
document✓

U

C.11.2.2.2✓

U

C.11.2.3.1✓

U

C.11.2.4.3✓

U

C.11.2.4.4

✓
✓
✓
✓
✓
✓

U
U
U
U
U
U

C.11.2.4.6
C.11.2.4.7
C.11.2.5.1
C.11.2.5.2
C.11.2.5.3
C.11.2.5.4✓

U

C.11.3.1.1.1✓

U

C.11.3.1.1.2

✓
✓

U
U

C.11.3.2.1
C.11.3.2.2✓

U

C.11.3.3.1.1✓

U

C.11.3.3.1.2

✓
✓

U
U

C.11.3.3.2
C.11.3.3.3✓

U

C.11.3.3.4✓

U

C.11.4.1.1.1✓

U

C.11.4.1.2.1✓

U

C.11.5.2.3

✓

✓

✓

✓

U

C.11.5.2.5

✓

✓

U

C.11.5.2.6

✓
✓

✓
✓

U
U

C.11.5.2.7
C.11.5.2.8

✓

✓

U

C.11.5.2.9

✓

✓

U

C.11.5.2.10✓

U

C.11.5.2.11✓

U

C.11.5.2.12✓

U

C.11.5.2.13✓

U

C.11.5.2.14

U

C.11.5.2.15

U

C.11.5.2.16

✓
✓

✓

ETSI

87
EN 301 549 V2.1.2 (2018-08)

Requirement conditionality

90
91
92
93
94
95
96
97
98
99
100
101
102

11.5.2.17 Modifications ofvalues and text
11.6.2 No disruption ofaccessibility features
11.7 User preferences
11.8.1 Content technology
11.8.2 Accessible content
creation
11.8.3 Preservation ofaccessibility information intransformations
11.8.4 Repair assistance
11.8.5 Templates
12.1.1 Accessibility andcompatibility features
12.1.2 Accessible
documentation
12.2.2 Information onaccessibility and compatibility
features12.2.3 Effective communication
12.2.4 Accessible
documentation

RobustUnderstandable

Clause of the present
document

Operable

No.

Perceivable

Essential
requirements of
Directive✓

Conditional or
Unconditional

Requirement

Condition

Assessment

Clause of thepresent
document

U

C.11.5.2.17
C.11.6.2

✓

✓

✓

✓

U

✓
✓

✓
✓

✓
✓

✓
✓

U
C

Where ICT is an authoring tool

C.11.7C.11.8.1

✓

✓

✓

✓

C

Where ICT is an authoring tool

C.11.8.2

✓

✓

✓

✓

C

Where ICT is an authoring tool

C.11.8.3

✓
✓

✓
✓

✓
✓

✓
✓

C
C

Where ICT is an authoring tool
Where ICT is an authoring tool

C.11.8.4
C.11.8.5

✓

✓

✓

✓

U

C.12.1.1

✓

✓

✓

✓

U

C.12.1.2

✓

✓

✓

✓

U

C.12.2.2

U

C.12.2.3

U

C.12.2.4

✓
✓

✓
✓

✓

✓

ETSI

88
EN 301 549 V2.1.2 (2018-08)

Annex B (informative):
Relationship between requirements and functional
performance statements
B.1

Relationships between clauses 5 to 13 and the functional
performance statements

Table B.2 shows which of the requirements set out in clauses 5 to 13 support each of the functional performancestatements set out in clause 4.2.
To allow Table B.2 to fit the page, the abbreviations shown in Table B.1 have been used in the column headers ofTable B.2.
Table B.1: Key to the column header designations used in Table B.2
Clausenumber
4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
4.2.6
4.2.7
4.2.8
4.2.9
4.2.104.2.11

Column header
abbreviation
WV
LV
WPC
WH
LH
WVC
LMS
LR
PST
LC
P

Functional performance statement
Usage without vision
Usage with limited vision
Usage without perception of colour
Usage without hearing
Usage with limited hearing
Usage without vocal capability
Usage with limited manipulation or strength
Usage with limited reach
Minimize photosensitive seizure triggers
Usage with limited cognition
Privacy

The following abbreviations have been used to represent the relationship between the requirements in clauses 5 to 13
and the functional performance statements:•

P = Primary relationship. The requirement supports the functional performance statement.

•

S = Secondary relationship. The requirement provides partial support for the functional performance statement
because some users may use the feature in specific situations.
Table B.2: Requirements in clauses 5 to 13 supporting the accessibility needs
expressed in the functional performance statements
Requirements

5.1.2.1 Closed functionality
5.1.2.2 Assistive technology
5.1.3.1 General (belongs to
5.1.3 Non-visual access)5.1.3.2 Auditory output
delivery including speech
5.1.3.3 Auditory output
correlation
5.1.3.4 Speech output user
control
5.1.3.5 Speech output
automatic interruption
5.1.3.6 Speech output for
non-text content
5.1.3.7 Speech output forvideo information
5.1.3.8 Masked entry

4.2.1
WV
P
-

4.2.2
LV
P
-

4.2.3
WPC
P
-

4.2.4
WH
P
-

4.2.5
LH
P
-

4.2.6
WVC
P
-

4.2.7
LMS
P
-

4.2.8
LR
P
-

4.2.9
PST
P
-

4.2.10LCP-

4.2.11
P
P
S

P

S

-

-

-

-

-

-

-

S

-

P

S

-

-

-

-

-

-

-

S

-

-

P

-

-

-

-

-

-

-

S

-

P

S

-

-

-

-

-

-

-

S

-

P

S

-

-

-

-

-

-

-

S

-

P

S

-

-

-

-

-

-

-

S

-

P

S

-

-

-

-

-

-

-

S

-

P

S

-

-

-

-

-

-

-

S

P

ETSI

89
EN 301 549 V2.1.2 (2018-08)

Requirements
5.1.3.9 Private access topersonal data
5.1.3.10 Non-interfering audio
output5.1.3.11 Private listening
volume5.1.3.12 Speaker volume
5.1.3.13 Volume reset
5.1.3.14 Spoken languages
5.1.3.15 Non-visual error
identification
5.1.3.16 Receipts, tickets,and transactional outputs
5.1.4 Functionality closed totext enlargement
5.1.5 Visual output forauditory information
5.1.6.1 Operation without
keyboard interface (closed
functionality)
5.1.6.2 Operation without
keyboard interface (Input
focus)
5.2 Activation of accessibility
features
5.3 Biometrics
5.4 Preservation ofaccessibility information
during conversion
5.5.1 Means of operation
5.5.2 Operable partdiscernibility
5.6.1 Tactile or auditory
status
5.6.2 Visual status
5.7 Key repeat
5.8 Double-strike key
acceptance
5.9 Simultaneous user
actions
6.1 Audio bandwidth forspeech (informative
recommendation)
6.2.1.1 RTT communication
6.2.1.2 Concurrent voice andtext
6.2.2.1 Visually
distinguishable display
6.2.2.2 Programmaticallydeterminable send andreceive direction
6.2.3 Interoperability
6.2.4 Real-time text
responsiveness6.3 Caller ID
6.4 Alternatives to voicebased services
6.5.2 Resolution
6.5.3 Frame rate
6.5.4 Synchronization
between audio and video
6.6 Alternatives to videobased services

4.2.1
WV

4.2.2
LV

4.2.3
WPC

4.2.4
WH

4.2.5
LH

4.2.6
WVC

4.2.7
LMS

4.2.8
LR

4.2.9
PST

4.2.10LC

4.2.11
P

P

S

-

-

-

-

-

-

-

S

P

P

S

-

-

-

-

-

-

-

S

-

P

S

-

-

S

-

-

-

-

S

S

P
P
P

S
S
S

-

-

S
S
-

-

-

-

-

S
S
S

-

P

S

-

-

-

-

-

-

-

S

-

P

S

-

-

-

-

-

-

-

-

-

-

P

-

-

-

-

-

-

-

-

-

-

-

-

P

P

-

-

-

-

S

-

P

P

-

-

-

S

P

-

-

-

-

P

P

-

-

-

S

P

-

-

-

-

P

P

P

P

P

-

P

-

-

-

-

P

P

-

P

-

P

P

P

-

-

P

P

P

-

P

P

-

-

-

-

S

-

-

-

-

-

-

-

P

-

-

-

-

P

S

-

-

-

-

-

-

-

-

-

P

P

-

-

-

-

-

-

-

S

-

-

-

-

P
-

P
-

-

P
P

P
-

-

S
S

-

-

-

-

-

-

-

P

P

-

S

-

-

-

-

-

-

-

P

P

-

S

-

-

-

-

-

P

-

-

-

-

-

-

-

-

-

P

S

S

-

-

-

-

-

-

-

-

P

P

S

-

-

-

-

-

-

-

-

P

S

S

-

-

-

-

-

-

-

-

P

S

S

-

-

-

-

-

-

-

-

P

S

S

-

-

-

-

-

-

-

-

P

S

S

-

-

-

-

-

P

P

-

-

-

-

-

-

-

S

-

-

-

-

P

P

P

-

-

-

-

-

-

-

-

P
P

P
P

S
S

-

-

-

-

-

-

-

-

P

P

S

-

-

-

-

-

P

S

-

P

P

P

-

-

-

-

-

ETSI

90
EN 301 549 V2.1.2 (2018-08)

Requirements
7.1.1 Captioning playback
7.1.2 Captioning
synchronization
7.1.3 Preservation of
captioning
7.2.1 Audio description
playback
7.2.2 Audio description
synchronization
7.2.3 Preservation of audio
description
7.3 User controls for captions
and audio description
8.1.2 Standard connections
8.1.3 Colour
8.2.1.1 Speech volume range
8.2.1.2 Incremental volume
control
8.2.2.1 Fixed-line devices
8.2.2.2 Wirelesscommunication devices
8.3.2.1 Change in Level
8.3.2.2 Clear floor or groundspace
8.3.2.3.1 Approach - General
8.3.2.3.2 Forward Approach
8.3.2.3.3 Parallel Approach
8.3.2.4 Knee and Toe
clearance width
8.3.2.5 Toe Clearance
8.3.2.6 Knee Clearance
8.3.3.1.1 Unobstructed highforward reach
8.3.3.1.2 Unobstructed low
forward reach
8.3.3.1.3.1 Clear floor space
8.3.3.1.3.2 Obstructed(< 510 mm) forward reach
8.3.3.1.3.3 Obstructed(< 635 mm) forward reach
8.3.3.2.1 Unobstructed highside reach
8.3.3.2.2 Unobstructed low
side reach
8.3.3.2.3.1 Obstructed(≤ 255 mm) side reach
8.3.3.2.3.2 Obstructed(≤ 610 mm) side reach
8.3.4 Visibility
8.3.5 Installation instructions
8.4.1 Numeric keys
8.4.2.1 Means of operation of
mechanical parts
8.4.2.2 Force of operation of
mechanical parts
8.4.3 Keys, tickets and farecards
8.5 Tactile indication of
speech mode
9.1.1.1 Non-text content
9.1.2.1 Audio-only and videoonly (pre-recorded)

4.2.1
WV
-

4.2.2
LV
-

4.2.3
WPC
-

4.2.4
WH
P

4.2.5
LH
P

4.2.6
WVC
-

4.2.7
LMS
-

4.2.8
LR
-

4.2.9
PST
-

4.2.10LC
S

4.2.11
P
-

-

-

-

P

P

-

-

-

-

S

-

-

-

-

P

P

-

-

-

-

S

-

P

P

-

-

-

-

-

-

-

S

-

P

P

-

-

-

-

-

-

-

S

-

P

P

-

-

-

-

-

-

-

S

-

P

P

-

P

P

-

-

-

-

S

-

P
-

P
S
-

P
-

-

P
P

-

P
-

P
-

-

P
S
-

-

-

-

-

-

P

-

-

-

-

-

-

-

-

-

-

P

-

-

-

-

-

-

-

-

-

-

P

-

-

-

-

-

-

-

-

-

-

-

-

-

P

-

-

-

-

-

-

-

-

-

-

P

-

-

-

-

-

-

-

-

-

-

P
P
P

-

-

-

-

-

-

-

-

-

-

P

-

-

-

-

-

-

-

-

-

-

P
P

-

-

-

-

-

-

-

-

-

-

P

-

-

-

-

-

-

-

-

-

-

P

-

-

-

-

-

-

-

-

-

-

P

-

-

-

-

-

-

-

-

-

-

P

-

-

-

-

-

-

-

-

-

-

P

-

-

-

-

-

-

-

-

-

-

P

-

-

-

-

-

-

-

-

-

-

P

-

-

-

-

-

-

-

-

-

-

P

-

-

-

-

-

-

-

-

-

-

P

-

-

-

P

S

-

-

-

-

-

P
P
-

-

-

-

-

-

-

-

-

-

P

-

-

-

-

-

-

-

-

-

-

P

-

-

-

-

P

S

-

-

-

-

-

-

-

-

-

P

-

-

-

-

-

-

-

-

-

-

P

P

-

P

S

-

-

-

-

S

S

P

P

-

P

P

-

-

-

-

S

-

ETSI

91
EN 301 549 V2.1.2 (2018-08)

Requirements
9.1.2.2 Captions (prerecorded)
9.1.2.3 Audio description or
media alternative (prerecorded)
9.1.2.4 Captions (live)
9.1.2.5 Audio description(pre-recorded)
9.1.3.1 Info and relationships
9.1.3.2 Meaningful sequence
9.1.3.3 Sensory
characteristics
9.1.3.4 Orientation
9.1.3.5 Identify input purpose
9.1.4.1 Use of colour
9.1.4.2 Audio control
9.1.4.3 Contrast (minimum)
9.1.4.4 Resize text
9.1.4.5 Images of text
9.1.4.10 Reflow
9.1.4.11 Non-text contrast
9.1.4.12 Text spacing
9.1.4.13 Content on hover or
focus
9.2.1.1 Keyboard
9.2.1.2 No keyboard trap
9.2.1.4 Character key
shortcuts
9.2.2.1 Timing adjustable
9.2.2.2 Pause, stop, hide
9.2.3.1 Three flashes or
below threshold
9.2.4.1 Bypass blocks
9.2.4.2 Page titled9.2.4.3 Focus order
9.2.4.4 Link purpose(in context)
9.2.4.5 Multiple ways
9.2.4.6 Headings and labels
9.2.4.7 Focus visible
9.2.5.1 Pointer gestures
9.2.5.2 Pointer cancellation(SC 2.5.2)
9.2.5.3 Label in name
9.2.5.4 Motion actuation
9.3.1.1 Language of page
9.3.1.2 Language of parts
9.3.2.1 On focus
9.3.2.2 On Input
9.3.2.3 Consistent navigation
9.3.2.4 Consistentidentification
9.3.3.1 Error identification
9.3.3.2 Labels or instructions
9.3.3.3 Error suggestion
9.3.3.4 Error prevention(legal, financial, data)
9.4.1.1 Parsing
9.4.1.2 Name, role, value
9.4.1.3 Status messages
9.5 WCAG Conformancerequirements

4.2.1
WV

4.2.2
LV

4.2.3
WPC

4.2.4
WH

4.2.5
LH

4.2.6
WVC

4.2.7
LMS

4.2.8
LR

4.2.9
PST

4.2.10LC

4.2.11
P

-

-

-

P

P

-

-

-

-

S

-

P

S

-

-

-

-

-

-

-

S

-

-

-

-

P

P

-

-

-

-

S

-

P

S

-

-

-

-

-

-

-

S

-

P
P

S
S

-

-

-

-

-

-

-

S
S

-

P

P

P

P

P

-

-

-

-

S

-

P
P
-

P
P
P
P
P
P
P
P

P
P
P
P
-

-

P
-

-

P
S
-

P
-

-

S
S
S
S
S
S
P

-

-

P

-

-

-

-

-

-

-

P

-

P
P

P
P

-

-

-

S
S

P
P

-

-

-

-

-

-

-

-

-

-

P

P

-

S

-

P
P

P
P

-

P
P

P
P

-

P
P

-

-

P
P

-

-

-

-

-

-

-

-

-

P

-

-

P
P
P

P
P
P

-

S

-

S
-

P
P
P

-

-

P
P
P

-

P

P

-

-

-

S

P

-

-

P

-

P
P
P
-

P
P
P
-

-

S
-

-

S
S
S
-

P
P
P
P

P

-

P
P
P
P

-

-

P

-

-

-

-

P

P

-

P

-

S
P
P
P
P
P

S
S
S
P
P
P

-

S
S
-

S
S
-

-

P
P
P
P
-

P
P
-

-

S
S
S
S
P
P
P

-

S

P

-

-

-

-

-

-

-

P

-

P
P
P

P
P
P

P
-

-

-

S
S

S
S

-

-

P
P
P

-

P

P

-

-

-

-

S

-

-

P

-

P
P
P

S
P
P

P

P

P

S

S
P

P

P

P

-

P

P

P

P

P

S

P

P

P

P

S

ETSI

92
EN 301 549 V2.1.2 (2018-08)

Requirements
10.1.1.1 Non-text content
10.1.2.1 Audio-only andvideo-only (pre-recorded)
10.1.2.2 Captions (prerecorded)
10.1.2.3 Audio description or
media alternative (prerecorded)
10.1.2.4 Captions (live)
10.1.2.5 Audio description(pre-recorded)
10.1.3.1 Info andrelationships
10.1.3.2 Meaningful
sequence
10.1.3.3 Sensory
characteristics
10.1.3.4 Orientation
10.1.3.5 Identify input
purpose10.1.4.1 Use of colour
10.1.4.2 Audio control
10.1.4.3 Contrast (minimum)
10.1.4.4 Resize text
10.1.4.5 Images of text
10.1.4.10 Reflow
10.1.4.11 Non-text contrast
10.1.4.12 Text spacing
10.1.4.13 Content on hover or
focus
10.2.1.1 Keyboard
10.2.1.2 No keyboard trap
10.2.1.4 Character key
shortcuts
10.2.2.1 Timing adjustable10.2.2.2 Pause, stop, hide
10.2.3.1 Three flashes or
below threshold
10.2.4.2 Document titled10.2.4.3 Focus order
10.2.4.4 Link purpose(in context)
10.2.4.6 Headings and labels
10.2.4.7 Focus visible
10.2.5.1 Pointer gestures
10.2.5.2 Pointer cancellation
10.2.5.3 Label in name10.2.5.4 Motion actuation
10.3.1.1 Language of page
10.3.1.2 Language of parts
10.3.2.1 On focus
10.3.2.2 On input
10.3.3.1 Error identification
10.3.3.2 Labels or instructions
10.3.3.3 Error suggestion
10.3.3.4 Error prevention(legal, financial, data)
10.4.1.1 Parsing
10.4.1.2 Name, role, value
10.5 Caption positioning
10.6 Audio description timing

4.2.1
WV
P

4.2.2
LV
P

4.2.3
WPC
-

4.2.4
WH
P

4.2.5
LH
S

4.2.6
WVC
-

4.2.7
LMS
-

4.2.8
LR
-

4.2.9
PST
-

4.2.10LC
S

4.2.11
P
S

P

P

-

P

P

-

-

-

-

S

-

-

-

-

P

P

-

-

-

-

S

-

P

S

-

-

-

-

-

-

-

S

-

-

-

-

P

P

-

-

-

-

S

-

P

S

-

-

-

-

-

-

-

S

-

P

S

-

-

-

-

-

-

-

S

-

P

S

-

-

-

-

-

-

-

S

-

P

P

P

P

P

-

-

-

-

S

-

-

P

-

-

-

-

P
-

P
-

-

S
-

-

P
P
-

P
P
P
P
P
P
P

P
P
P
P
-

-

P
-

-

S
-

-

-

S
S
S
S
S
P

-

-

P

-

-

-

-

-

-

-

P

-

P
P

P
P

-

-

-

S
S

P
P

-

-

-

-

-

-

-

-

-

-

P

P

-

S

-

P
P

P
P

-

P
P

P
P

-

P
P

-

-

P
P

-

-

-

-

-

-

-

-

-

P

-

-

P
P

P
P

-

S

-

-

P
P

-

-

P
P

-

P

P

-

-

-

S

P

-

-

P

-

P
P
S
P
P
P
P
P
P
P

P
P
P
S
S
S
P
P
P
P
P

P
-

S
S
S
-

S
S
-

S
S
S
S

P
P
P
P
P
P
P
P
S
S

P
P
P
P
-

-

P
P
P
P
S
S
S
S
P
P
P
P
P

-

P

P

-

-

-

-

S

-

-

P

-

P
P
P

S
P
S

-

P
-

P
-

-

S
-

-

-

S
S

-

ETSI

93
EN 301 549 V2.1.2 (2018-08)

Requirements
11.1.1.1.1 Non-text content(open functionality)
11.1.1.1.2 Non-text content(closed functionality
11.1.2.1.1 Audio-only andvideo-only (pre-recorded open functionality)
11.1.2.1.2.1 Pre-recorded
audio-only (closed
functionality)
11.1.2.1.2.2 Pre-recorded
video-only (closed
functionality)
11.1.2.2 Captions(pre-recorded)
11.1.2.3.1 Audio description
or media alternative(pre-recorded - open
functionality)
11.1.2.3.2 Audio description
or media alternative(pre-recorded - closed
functionality)
11.1.2.4 Captions (live)
11.1.2.5 Audio description(pre-recorded)
11.1.3.1.1 Info andrelationships (openfunctionality)
11.1.3.1.2 Info andrelationships (closed
functionality)
11.1.3.2.1 Meaningful
sequence (open functionality)
11.1.3.2.2 Meaningful
sequence (closed
functionality)
11.1.3.3 Sensory
characteristics
11.1.3.4 Orientation
11.1.3.5 Identify input
purpose11.1.4.1 Use of colour
11.1.4.2 Audio control
11.1.4.3 Contrast (minimum)
11.1.4.4.1 Resize text (openfunctionality)
11.1.4.4.2 Resize text (closed
functionality)
11.1.4.5.1 Images of text
(open functionality)
11.1.4.5.2 Images of text
(closed functionality)
11.1.4.10.1 Reflow (openfunctionality)
11.1.4.10.2 Reflow (closefunctionality)
11.1.4.11 Non-text contrast
11.1.4.12 Text spacing
11.1.4.13 Content on hover or
focus
11.2.1.1.1 Keyboard (openfunctionality)

4.2.1
WV

4.2.2
LV

4.2.3
WPC

4.2.4
WH

4.2.5
LH

4.2.6
WVC

4.2.7
LMS

4.2.8
LR

4.2.9
PST

4.2.10LC

4.2.11
P

P

P

-

P

S

-

-

-

-

S

S

P

P

-

P

S

-

-

-

-

S

S

P

P

-

P

P

-

-

-

-

S

-

-

-

-

P

P

-

-

-

-

S

-

P

S

-

-

-

-

-

-

-

S

-

-

-

-

P

P

-

-

-

-

S

-

P

S

-

-

-

-

-

-

-

S

-

P

S

-

-

-

-

-

-

-

S

-

-

-

-

P

P

-

-

-

-

S

-

P

S

-

-

-

-

-

-

-

S

-

P

S

-

-

-

-

-

-

-

S

-

P

S

-

-

-

-

-

-

-

S

-

P

S

-

-

-

-

-

-

-

S

-

P

S

-

-

-

-

-

-

-

S

-

P

P

P

P

P

-

-

-

-

S

-

-

P

-

-

-

-

P
-

P
-

-

S
-

-

P
P
-

P
P

P
P

-

P
-

-

-

-

-

S
S
S

-

-

P

-

-

-

-

S

-

-

-

-

-

P

-

-

-

-

S

-

-

-

-

-

P

P

-

-

-

-

-

-

S

-

-

-

-

-

-

-

-

-

-

-

-

-

P

-

-

-

-

-

-

-

-

-

-

P

-

-

-

-

-

-

-

-

-

-

P
P

P
-

-

-

-

-

-

-

S
P

-

-

P

-

-

-

-

-

-

-

P

-

P

P

-

-

-

S

P

-

-

-

-

ETSI

94
EN 301 549 V2.1.2 (2018-08)

Requirements
11.2.1.1.2 Keyboard (closed
functionality)
11.2.1.2 No keyboard trap
11.2.1.4.1 Character key
shortcuts (open functionality)
11.2.1.4.2 Character key
shortcuts (closed
functionality)
11.2.2.1 Timing adjustable
11.2.2.2 Pause, stop, hide
11.2.3.1 Three flashes or
below threshold
11.2.4.3 Focus order
11.2.4.4 Link purpose(in context)
11.2.4.6 Headings and labels
11.2.4.7 Focus visible
11.2.5.1 Pointer gestures
11.2.5.2 Pointer cancellation
11.2.5.3 Label in name11.2.5.4 Motion actuation
11.3.1.1.1 Language ofsoftware (open functionality)
11.3.1.1.2 Language ofsoftware (closed functionality)
11.3.2.1 On focus
11.3.2.2 On input
11.3.3.1.1 Error identification(open functionality)
11.3.3.1.2 Error Identification(closed functionality)
11.3.3.2 Labels or instructions
11.3.3.3 Error suggestion
11.3.3.4 Error prevention(legal, financial, data)
11.4.1.1.1 Parsing (openfunctionality)
11.4.1.1.2 Parsing (closed
functionality)
11.4.1.2.1 Name, role, value(open functionality)
11.4.1.2.2 Name, role, value(closed functionality)
11.5.1 Closed functionality
11.5.2.1 Platform accessibility
service support for softwarethat provides a user interface
11.5.2.2 Platform accessibility
service support for assistive
technologies
11.5.2.3 Use of accessibility
services
11.5.2.4 Assistive technology
11.5.2.5 Object information
11.5.2.6 Row, column, andheaders
11.5.2.7 Values
11.5.2.8 Label relationships
11.5.2.9 Parent-childrelationships
11.5.2.10 Text

4.2.1
WV

4.2.2
LV

4.2.3
WPC

4.2.4
WH

4.2.5
LH

4.2.6
WVC

4.2.7
LMS

4.2.8
LR

4.2.9
PST

4.2.10LC

4.2.11
P

P

P

-

-

-

S

P

-

-

-

-

P

P

-

-

-

S

P

-

-

-

-

-

-

-

-

-

-

P

P

-

S

-

-

-

-

-

-

-

P

P

-

S

-

P
P

P
P

-

P
P

P
P

-

P
P

-

-

P
P

-

-

-

-

-

-

-

-

-

P

-

-

P

P

-

S

-

-

P

-

-

P

-

P

P

-

-

-

S

P

-

-

P

-

P
P
S

P
P
P
S

-

S
-

-

S
S
-

P
P
P
P
P
P

P
P
P
P

-

P
P
P
P
S
S

-

P

S

-

S

S

-

-

-

-

S

-

P

S

-

S

S

-

-

-

-

S

-

P
P

P
P

-

-

-

-

P
P

-

-

P
P

-

P

P

P

-

-

-

-

-

-

P

-

P

P

P

-

-

-

-

-

-

P

-

P
P

P
P

-

-

-

S
S

S
S

-

-

P
P

-

P

P

-

-

-

-

S

-

-

P

-

P

S

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

P

P

-

-

-

-

S

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

P

P

-

-

-

-

P

-

-

S

-

P

P

-

-

-

-

P

-

-

S

-

P

P

-

-

-

-

P

-

-

S

-

P
P

P
P

-

-

-

-

P
P

-

-

S
S

-

P

P

-

-

-

-

P

-

-

S

-

P
P

P
P

-

-

-

-

P
P

-

-

S
S

-

P

P

-

-

-

-

P

-

-

S

-

P

P

-

-

-

-

P

-

-

S

-

ETSI

95
EN 301 549 V2.1.2 (2018-08)

Requirements
11.5.2.11 List of available
actions
11.5.2.12 Execution ofavailable actions
11.5.2.13 Tracking of focus
and selection attributes
11.5.2.14 Modification of
focus and selection attributes
11.5.2.15 Change notification
11.5.2.16 Modifications ofstates and properties
11.5.2.17 Modifications ofvalues and text
11.6.1 User control ofaccessibility features
11.6.2 No disruption ofaccessibility features
11.7 User preferences
11.8.1 Content technology
11.8.2 Accessible content
creation
11.8.3 Preservation ofaccessibility information intransformations
11.8.4 Repair assistance
11.8.5 Templates
12.1.1 Accessibility andcompatibility features
12.1.2 Accessible
documentation
12.2.2 Information onaccessibility and compatibility
features12.2.3 Effective
communication
12.2.4 Accessible
documentation
13.1.2 Text relay services
13.1.3 Sign relay services
13.1.4 Lip-reading relay
services
13.1.5 Captioned telephonyservices
13.1.6 Speech to speech
relay services
13.2 Access to relay services
13.3 Access to emergency
services

4.2.1
WV

4.2.2
LV

4.2.3
WPC

4.2.4
WH

4.2.5
LH

4.2.6
WVC

4.2.7
LMS

4.2.8
LR

4.2.9
PST

4.2.10LC

4.2.11
P

P

P

-

-

-

-

P

-

-

S

-

P

P

-

-

-

-

P

-

-

S

-

P

P

-

-

-

-

P

-

-

S

-

P

P

-

-

-

-

P

-

-

S

-

P

P

-

-

-

-

P

-

-

S

-

P

P

-

-

-

-

P

-

-

S

-

P

P

-

-

-

-

P

-

-

S

-

P

P

P

P

P

-

P

-

-

-

-

P

P

P

P

P

-

P

-

-

-

-

P

P
P

P
P

P

P

S

P

P

P

S
P

S

P

P

P

P

P

S

P

P

P

P

S

P

P

P

P

P

S

P

P

P

P

S

P
P

P
P

P
P

P
P

P
P

S
S

P
P

P
P

P
P

P
P

S
S

P

P

P

P

P

-

P

-

-

S

-

P

P

P

P

P

S

P

P

P

P

S

P

P

P

P

P

-

P

-

-

S

-

-

-

-

P

P

P

-

-

-

S

-

P

P

P

P

P

S

P

P

P

P

S

-

-

-

P
P

P
P

P
P

-

-

-

S
-

-

-

-

-

P

P

P

-

-

-

-

-

-

-

-

P

P

P

-

-

-

-

-

-

-

-

-

-

-

-

-

-

P

-

-

-

-

P

P

P

-

-

-

S

-

-

-

-

P

P

P

-

-

-

S

-

ETSI

96
EN 301 549 V2.1.2 (2018-08)

Annex C (normative):
Determination of compliance
C.1

Introduction

This normative annex sets out the means necessary to determine compliance with the individual requirements set out inthe body of the present document.
All clauses except those in clause 12 are self-scoping. This means they are introduced with the phrase 'Where ICT<pre-condition>'. Compliance is achieved either when the pre-condition is true and the corresponding test (in Annex C)
is passed, or when the pre-condition is false (i.e. the pre-condition is not met or not valid).
To assist the reader, empty clauses are inserted in order to make the numbering of the annex reflect the clause numbersin the requirements.
ICT is often comprised of an assembly of two or more items of ICT. In some cases, two or more interoperable items of
ICT may together meet more requirements of the standard when one item complements the functionality of the otherand the sum together meets more of the accessibility requirements. However, combining two items of ICT, both ofwhich fail to meet any particular requirement, will not lead to a combined ICT system that meets that requirement.
The present document does not prioritize requirements. Prioritization of those requirements is left to the user of thepresent document.
Prioritization of those requirements that align with the targeted context of use may enhance accessibility in the case ofpartial compliance and the rationale for that prioritization, if used, should be stated.
Compliance should shall be reported in a form that:•makes clear whether there is compliance with all the applicable requirements or whether there is only
compliance with some requirements;•

notes the sampling and assessment techniques used to evaluate the ICT;•

notes whether equivalent accessible functionality exists in places where non-compliance was found; and•notes whether equivalent means were used that achieve the outcome envisioned, where technical noncompliance was found.

NOTE 1: In some circumstances, when the present document is used for purposes other than supporting
Directive 2016/2102 [i.28], user accessibility needs might be met by a subset of the requirements. For
example, where ICT is designed to be used by a specific individual, or in a well-defined usage scenario, aparticular functional performance statement in clause 4.2, and/or associated requirement of clauses 5 to13, could be omitted if such an omission will have no negative impact on the accessibility needs of theintended users in the planned context of use.
NOTE 2: Compliance with the accessibility requirements could be affected by subsequent implementation or
maintenance.
NOTE 3: Sampling is frequently required on complex ICT when there are too many instances of the object to betested. The present document cannot recommend specific ICT evaluation sampling techniques as these
are context specific.

C.2

Empty clauseThis clause is intentionally left empty.

ETSI

97
EN 301 549 V2.1.2 (2018-08)

C.3

Empty clauseThis clause is intentionally left empty.

C.4

Functional performance

Clause 4 is informative and does not contain requirements that require testing.

C.5

Generic requirements

C.5.1

Closed functionality

C.5.1.1

Introduction

Clause 5.1.1 is informative and does not contain requirements that require testing.

C.5.1.2
C.5.1.2.1

GeneralClosed functionality

ICT with closed functionality shall meet the requirements set out in clauses C.5.2 to C.13, as applicable.

C.5.1.2.2

Assistive technology

Type of assessment
Pre-conditions
Procedure

ResultC.5.1.3
C.5.1.3.1

Non-visual access
GeneralType of assessment
Pre-conditions
Procedure
ResultC.5.1.3.2

Testing
1. Visual information is needed to enable the use of those functions of the ICT that areclosed to assistive technology for screen reading.
1. Determine the functions of the ICT closed to screen reading.
2. Check that they are all operable using non-visual access.
Pass: Check 2 is true
Fail: Check 2 is false

Auditory output delivery including speechType of assessment
Pre-conditions
Procedure

ResultTesting
1. The ICT has closed functionality.
1. Determine the closed functions of the ICT.
2. Check that the tests C.5.1.3 to C.5.1.6 can be carried out without the attachment or
installation of any assistive technology except personal headsets or inductive loops.
Pass: Check 2 is true
Fail: Check 2 is false

Inspection
1. Auditory output is provided as non-visual access to closed functionality.
1. Check that the auditory output is delivered by a mechanism included in or provided
with the ICT.
2. Check that the auditory output is delivered by a personal headset that can beconnected through a 3,5 mm audio jack or an industry standard connection without
requiring the use of vision.
Pass: Check 1 or 2 is true
Fail: Checks 1 and 2 are false

ETSI

98
EN 301 549 V2.1.2 (2018-08)

C.5.1.3.3

Auditory output correlation

Clause 5.1.3.3 is informative only and contains no requirements requiring test.

C.5.1.3.4

Speech output user control

Type of assessment
Pre-conditions
Procedure

ResultC.5.1.3.5

Speech output automatic interruption

Type of assessment
Pre-conditions
Procedure

ResultC.5.1.3.6

ResultProcedure
ResultResultTesting
1. Pre-recorded video content is needed to enable the use of closed functions of ICT
2. Speech output is provided as non-visual access to non-text content displayed on
closed functionality.
1. Check that the speech output presents equivalent information for the pre-recorded
video content.
Pass: Check 1 is true
Fail: Check 1 is false

Masked entry

Type of assessment
Pre-conditions

Procedure

Testing
1. Non-text content is presented to users via speech output.
1. Check that speech output is provided as an alternative for non-text content.
2. Check that the non-text content is not pure decoration.
3. Check that the non-text content is not used only for visual formatting.
4. Check that the speech output follows the guidance for "text alternative" described in
WCAG 2.1 Success Criterion 1.1.1.
Pass: Checks 1 and 2 and 3 and 4 are true; or 1 and 2 are false; or 1 and 3 are false
Fail: Checks 1 is true and 2 false; or 1 is true and 3 false; or 1 and 2 and 3 are true and4 is false

Speech output for video information

Type of assessment
Pre-conditions

C.5.1.3.8

Inspection
1. Speech output is provided as non-visual access to closed functionality.
1. Determine the closed functions of the ICT.
2. Check that the speech output for each single function is interrupted on a user action.
3. Check that the speech output for each single function is interrupted when new
speech output begins.
Pass: Check 2 and 3 are true
Fail: Check 2 or 3 are false

Speech output for non-text content

Type of assessment
Pre-conditions
Procedure

C.5.1.3.7

Inspection
1. Speech output is provided as non-visual access to closed functionality.
1. Check that the speech output is capable of being interrupted when requested by theuser.
2. Check that the speech output is capable of being repeated when requested by theuser.
Pass: All checks are true
Fail: Any check is false

Testing
1. Auditory output is provided as non-visual access to closed functionality.
2. The characters displayed are masking characters.
3. The user does not explicitly choose to allow non-private auditory output.
1. Check that the auditory output is not a spoken version of the characters entered.
2. Check that the auditory output is known to be delivered only to a mechanism for
private listening.
3. If 1 and 2 are false, check that the user has explicitly chosen to allow non-private
auditory output.
Pass: Any check is true
Fail: All checks are false

ETSI

99
EN 301 549 V2.1.2 (2018-08)

C.5.1.3.9

Private access to personal data

Type of assessment
Pre-conditions

Procedure

ResultC.5.1.3.10

Non-interfering audio output

Type of assessment
Pre-conditions
Procedure
ResultC.5.1.3.11

Procedure
ResultProcedure

ResultResultInspection and measurement
1. The auditory output is provided as non-visual access to closed functionality.
2. The auditory output is delivered through speakers.
1. Check that a non-visual incremental volume control is provided.
2. Check that output amplification up to a level of at least 65 dBA (-29 dBPaA) isavailable.
Pass: Checks 1 and 2 are true
Fail: Check 1 or 2 is false

Volume reset

Type of assessment
Pre-conditions
Procedure

Inspection
1. The auditory output is provided as non-visual access to closed functionality.
2. The auditory output is delivered through a mechanism for private listening.
1. Check that there is at least one non-visual mode of operation for controlling thevolume.
Pass: Check 1 is true
Fail: Check 1 is false

Speaker volume

Type of assessment
Pre-conditions

C.5.1.3.13

Testing
1. Auditory output is provided as non-visual access to closed functionality.
2. The ICT automatically plays interfering audible output.
1. Check that the interfering audible output lasts no longer than three seconds.
Pass: Check 1 is true
Fail: Check 1 is false

Private listening volume

Type of assessment
Pre-conditions

C.5.1.3.12

Testing
1. Auditory output is provided as non-visual access to closed functionality.
2. The output contains data.
3. There is an applicable privacy policy which considers that data to be private.
1. Check that the auditory output is only delivered through a mechanism for private
listening.
2. Check that the mechanism for private listening can be connected without requiring
the use of vision.
3. Check that the auditory output is delivered through any other mechanism that can bechosen by the user.
Pass: Checks 1 and 2 or 3 are true
Fail: Checks 1 or 2 and 3 are false

Inspection and measurement
1. The auditory output is provided as non-visual access to closed functionality.
2. The ICT is not dedicated to a single user.
1. Check that a function that automatically resets the volume to be at a level of 65 dBAor less after every use is provided.
Pass: Check 1 is true
Fail: Check 1 is false

ETSI

100
EN 301 549 V2.1.2 (2018-08)

C.5.1.3.14

Spoken languages

Type of assessment
Pre-conditions

Procedure
ResultC.5.1.3.15

Non-visual error identification

Type of assessment
Pre-conditions
Procedure
ResultC.5.1.3.16

Procedure
ResultProcedure

ResultInspection and measurement
1. A functionality of the ICT is closed to enlargement features of platform or assistive
technology.
2. A viewing distance is specified by the supplier.
1. Measure the height of a capital letter H.
2. Check that it subtends an angle of at least 0,7 degrees at the specified viewing
distance.
Pass: Check 2 is true
Fail: Check 2 is false

Visual output for auditory information

Type of assessment
Pre-conditions
Procedure
ResultTesting
1. The ICT is closed to visual access.
2. The ICT provides receipts, tickets, or other outputs as a result of a self-service
transaction.
3. The information being checked is not printed copies of itineraries and maps.
1. Check that speech output is provided which includes all information necessary tocomplete or verify the transaction.
Pass: Check 1 is true
Fail: Check 1 is false

Functionality closed to text enlargement

Type of assessment
Pre-conditions

C.5.1.5

Testing
1. Speech output is provided as non-visual access to closed functionality.
2. An input error is automatically detected.
1. Check that speech output identifies the item that is in error.
2. Check that the speech output describes the item that is in error.
Pass: Checks 1 and 2 are true
Fail: Check 1 or check 2 false

Receipts, tickets and transactional outputs

Type of assessment
Pre-conditions

C.5.1.4

Testing
1. The speech output is provided as non-visual access to closed functionality.
2. The speech output is not proper names, technical terms, words of indeterminate
language, and words or phrases that have become part of the vernacular of theimmediately surrounding text.
3. The content is not generated externally and is under the control of the ICT vendor.
4. The displayed languages can be selected using non-visual access.
5. The user has not selected a speech language that is different from the language ofthe displayed content.
1. Check that the speech output is in the same human language of the displayedcontent provided.
Pass: Check 1 is true
Fail: Check 1 is false

Inspection
1. Pre-recorded auditory information is needed to enable the use of closed functions of
ICT.
1. Check that the visual information is equivalent to the pre-recorded auditory output.
Pass: Check 1 is true
Fail: Check 1 is false

ETSI

101
EN 301 549 V2.1.2 (2018-08)

C.5.1.6

Operation without keyboard interface

C.5.1.6.1

Closed functionality

Type of assessment
Pre-conditions
Procedure
ResultC.5.1.6.2

Input focus

Type of assessment
Pre-conditions
Procedure
ResultC.5.2

ResultType of assessment
Pre-conditions
Procedure
Result

Test 1
1. The ICT uses biological characteristic for user identification.
1. Check that more than one means can be used for user identification.
Pass: Check 1 is true
Fail: Check 1 is false
Test 2
1. The ICT uses biological characteristic for control of ICT.
1. Check that more than one means can be used for control of ICT.
Pass: Check 1 is true
Fail: Check 1 is false

Preservation of accessibility information during conversion

Type of assessment
Pre-conditions

Procedure
ResultInspection
1. The ICT has documented accessibility features to meet a specific need.
1. Check that it is possible to activate those accessibility features without relying on amethod that does not support that need.
Pass: Check 1 is true
Fail: Check 1 is false

Biometrics

Type of assessment
Pre-conditions
Procedure
ResultC.5.4

Inspection
1. ICT functionality is closed to keyboards or keyboard interfaces.
2. Input focus can be moved to a user interface element.
1. Check that it is possible to move the input focus away from that element using thesame mechanism.
Pass: Check 1 is true
Fail: Check 1 is false

Activation of accessibility features

Type of assessment
Pre-conditions
Procedure

C.5.3

Inspection
1. ICT functionality is closed to keyboards or keyboard interfaces.
1. Check that all functionality is operable without vision.
Pass: Check 1 is true
Fail: Check 1 is false

Inspection
1. The non-proprietary information provided for accessibility is documented.
2. The ICT converts information or communication.
3. The non-proprietary information provided for accessibility can be contained in thedestination format.
4. The non-proprietary information provided for accessibility can be supported by thedestination format.
1. Check that the non-proprietary information provided for accessibility is preserved
when the ICT converts information or communication.
Pass: Check 1 is true
Fail: Check 1 is false

ETSI

102
EN 301 549 V2.1.2 (2018-08)

C.5.5

Operable parts

C.5.5.1

Means of operation

Type of assessment
Pre-conditions

Testing
The ICT has operable parts that require grasping, pinching, or twisting of thewrist to operate.
1. Check that there is an accessible alternative means of operation that does
not require these actions.
Pass: Check 1 is true
Fail: Check 1 is false

Procedure
ResultC.5.5.2

Operable part discernibility

Type of assessment
Pre-conditions
Procedure

Testing
The ICT has operable parts.
1. Identify that there is a means to discern each operable part without vision.
2. Check that the action associated with the operable part has not been
performed when using the means to discern each operable part of step 1.
Pass: Checks 1 and 2 are true
Fail: Checks 1 or 2 are false

ResultC.5.6

Locking or toggle controls

C.5.6.1

Tactile or auditory status

Type of assessment
Pre-conditions
Procedure

ResultC.5.6.2

Visual status

Type of assessment
Pre-conditions
Procedure
ResultC.5.7

Inspection
1. The ICT has a locking or toggle control.
2. The locking or toggle control is presented to the user.
1. Check that there is at least one mode of operation where the status of all locking or
toggle controls can be visually determined when the control is presented.
Pass: Check 1 is true
Fail: Check 1 is false

Key repeat

Type of assessment
Pre-conditions
Procedure
ResultInspection
1. The ICT has a locking or toggle control.
2. The locking or toggle control is visually presented to the user.
1. Check that there is at least one mode of operation where the status of all locking or
toggle controls can be determined through touch without operating the control.
2. Check that there is at least one mode of operation where the status of all locking or
toggle controls can be determined through sound without operating the control.
Pass: Check 1 or 2 is true
Fail: Checks 1 and 2 are false

Testing
1. The ICT has a key repeat function A keyboard or keypad with key repeat is provided.
2. The key repeat cannot be turned off.
1. Check that the delay before key repeat can be adjusted to at least 2 seconds.
2. Check that the key repeat rate can be adjusted to 2 seconds per character.
Pass: Checks 1 and 2 are true
Fail: Check 1 or 2 is false

ETSI

103
EN 301 549 V2.1.2 (2018-08)

C.5.8

Double-strike key acceptanceType of assessment
Pre-conditions
Procedure

ResultC.5.9

Testing
1. The ICT has a keyboard or keypadA keyboard or keypad is provided.
1. Check that there is a mechanism that allows adjustment of the delay after any
keystroke, during which an additional key-press will not be accepted if it is identical tothe previous keystroke.
2. Adjust that mechanism to its maximum setting.
3. Press any key.
4. After a delay of 0,5 seconds press the same key as that pressed in step 3.
5. Check whether the keystroke of step 4 has been accepted.
Pass: Check 1 is true and check 5 is false
Fail: Check 1 is false or check 5 is true

Simultaneous user actions

Type of assessment
Pre-conditions
Procedure

Inspection
None.
1. If there are multiple modes of operation, select one mode of operation (see notes 1
and 2 of this table for guidance on the selection).
2. Determine all the user controllable functions of the ICT.
3. Check that each user controllable function can be operated with a single point ofcontact.
4. If there are multiple modes of operation and the test is not passed, repeat theprocedure until all modes of operation have been tested.
ResultPass: Check 3 is true
Fail: Check 3 is false for all modes of operation
NOTE 1: If there are multiple modes of operation, these should be tested until the compliance test is passed.
NOTE 2: Where it is claimed that a specific mode complies with clause 5.6, this mode should be tested first.

C.6

ICT with two-way voice communication

C.6.1

Audio bandwidth for speechType of assessment
Pre-conditions
Procedure
ResultC.6.2

Measurement
1. The ICT under test provides two-way voice communication.
1. Check that the ICT can encode and decode audio with a frequency range with an
upper limit of at least 7 000 Hz.
Pass: Check 1 is true
Fail: Check 1 is false

Real-Time Text (RTT) functionality

C.6.2.1
C.6.2.1.1

RTT provision
RTT communication

Type of assessment
Pre-conditions

Procedure
ResultInspection
1. The ICT system under test allows two-way voice communication.
2. A "reference" RTT-capable device compatible with the system is connected at theother end of the system.
1. Check that the ICT allows a user to communicate with the "reference" ICT by RTT.
Pass: Check 1 is true
Fail: Check 1 is false

ETSI

104
EN 301 549 V2.1.2 (2018-08)

C.6.2.1.2

Concurrent voice and text

Type of assessment
Pre-conditions
Procedure

ResultC.6.2.2
C.6.2.2.1

Inspection
1. The ICT supports two-way voice communication.
2. The ICT enables a user to communicate with another user by RTT.
1. Check that the ICT provides a mechanism to select a mode of operation whichallows concurrent voice and text.
2. Check that ICT allows the concurrent use of voice and text when in the mode ofoperation identified in step 1.
Pass: Checks 1 and 2 are true
Fail: Check 1 or 2 is false

Display of Real-Time Text
Visually distinguishable display

Type of assessment
Pre-conditions

Inspection
1. The ICT under test has RTT send and receive capabilities.
2. The ICT supports RTT mechanism(s).
3. A "reference" RTT-capable terminal using mechanisms supported by the ICT system
is connected at the other end of the system to the ICT under test.
Procedure
1. The ICT under test is connected to the ICT system terminated by the "reference"terminal.
2. The different elements of the ICT are in an operational status (the connection is
active and the terminals are in the relevant RTT mode) and the two terminals arecommunicating to each other.
3. A Short text sequence is sent by the ICT under test.
4. A Short text sequence is sent by the "reference" terminal.
5. Check, on the ICT under test, that displayed sent text is visually differentiated fromand separated from received text.
ResultPass: Check 5 is true
Fail: Check 5 is false
NOTE:
A "reference" terminal is a terminal having RTT send and receive capabilities that uses the RTT
mechanisms supported by the ICT system. This "reference" terminal is the responsibility of the test
laboratory.

C.6.2.2.2

Programmatically determinable send and receive direction

Type of assessment
Pre-conditions

Inspection
1. The ICT under test has RTT send and receive capabilities.
2. The RTT is open functionality.
3. A "reference" RTT-capable terminal using mechanisms supported by the ICT
network is connected at the other end of an ICT system to the ICT under test.
Procedure
1. The ICT under test is connected to the ICT system terminated by the "reference"terminal.
2. The different elements of the ICT are in an operational status (the connection is
active and the terminals are in the relevant RTT mode) and the two terminals arecommunicating to each other.
3. A Short text sequence is sent by the ICT under test.
4. A Short text sequence is sent by the "reference" terminal.
5. Check that the send/receive direction of transmitted text is programmaticallydeterminable.
ResultPass: Check 5 is true
Fail: Check 5 is false
NOTE:
A "reference" terminal is a terminal having RTT send and receive capabilities that uses the RTT
mechanisms supported by the ICT network. This "reference" terminal is the responsibility of the test
laboratory.

ETSI

105
EN 301 549 V2.1.2 (2018-08)

C.6.2.3

Interoperability

Type of assessment
Pre-conditions
Procedure

ResultC.6.2.4

Test
1. The ICT under test supports two-way voice communication.
2. The ICT under test has RTT functionality.
1. Check that the ICT interoperates over the Public Switched Telephone Network(PSTN), with other ICT that directly connects to the PSTN as described in
Recommendation ITU-T V.18 [i.23] or any of its annexes for text telephony signals at
the PSTN interface.
2. Check that the ICT interoperates with other ICT using VOIP with Session Initiation
Protocol (SIP) and using real-time text that conforms to IETF RFC 4103 [i.13].
3. Check that the ICT interoperates with other ICT using RTT that conforms with the IP
Multimedia Sub-System (IMS) set of protocols specified in ETSI TS 126 114 [i.10],
ETSI TS 122 173 [i.11] and ETSI TS 134 229 [i.12].
4. Check that the ICT interoperates with other ICT using a relevant and applicablecommon specification that is published and available.
5. Check that the common specification in check 4 includes a method for indicating
loss or corruption of characters.
Pass: Check 1 or 2 or 3 or both 4 and 5 are true
Fail: All of Checks 1, 2, 3 and at least one of 4 or 5 are false

Real-Time Text responsivenessType of assessment
Pre-conditions

Inspection of Measurement data or Test
1. The ICT under test has RTT send and receive capabilities.
2. A "reference" RTT-capable terminal using mechanisms supported by the ICT system
is connected at the other end of an ICT system to the ICT under test.
3. The ICT under test is connected to the ICT system terminated by the "reference"terminal.
4. The different elements of the ICT are in a working status (the connection is active
and the terminals are in the relevant RTT mode).
Procedure
1. A short sequence is input to the terminal under test.
2. Check the time at which input entry has occurred.
3. Check the period between input entry to the ICT terminal under test and the time
when the text is transmitted to the ICT network.
ResultPass: Check 3 is less than or equal to 1 second
Fail: Check 3 is greater than 1 second
NOTE:
As described in the notes to clause 6.2.4, the identification of when input entry has occurred mayvary according to the type of RTT system under test.

C.6.3

Caller ID

Type of assessment
Pre-conditions
Procedure

ResultC.6.4

Alternatives to voice-based services

Type of assessment
Pre-conditions
Procedure

ResultInspection
1. The ICT provides caller identification, or similar telecommunications functions areprovided.
1. Check that the information delivered by each function is available as text.
2. Check that the information delivered by each function is available in anothermodality.
Pass: Both Checks 1 and 2 are true
Fail: Check 1 or 2 is false

Inspection
1. The ICT provides real-time voice-based communication.
2. The ICT provides voice mail, auto-attendant, or interactive voice response facilities.
1. Check that the ICT offers users a means to access the information without the use ofhearing or speech.
2. Check that a user can carry out the tasks provided by the system without the use ofhearing or speech.
Pass: Checks 1 and 2 are true
Fail: Check 1 or 2 is false

ETSI

106
EN 301 549 V2.1.2 (2018-08)

C.6.5

Video communication

C.6.5.1

GeneralClause 6.5.1 is informative only and contains no requirements requiring test.

C.6.5.2

Resolution

Type of assessment
Pre-conditions
Procedure
ResultC.6.5.3

Frame rate

Type of assessment
Pre-conditions
Procedure
ResultC.6.5.4

Inspection
1. The ICT provides 2 way voice communication.
2. The ICT includes real-time video functionality.
1. Check that the video communication frame rate is equal to or higher than 12 frames
per second.
Pass: Check 1 is true
Fail: Check 1 is false

Synchronization between audio and video

Type of assessment
Pre-conditions
Procedure
ResultC.6.6

Inspection
1. The ICT provides 2 way voice communication.
2. The ICT includes real-time video functionality.
1. Check that the video communication resolution is QCIF resolution or better.
Pass: Check 1 is true
Fail: Check 1 is false

Measurement
1. The ICT provides 2 way voice communication.
2. The ICT includes real-time video functionality.
1. Check that the time difference between the speech and video presented to the user
is equal to or less than 100 ms.
Pass: Check 1 is true
Fail: Check 1 is false

Alternatives to video-based services

Clause 6.6 is advisory only and contains no requirements requiring test.

C.7

ICT with video capabilities

C.7.1

Caption processing technology

C.7.1.1

Captioning playback

Type of assessment
Pre-conditions
Procedure
ResultType of assessment
Pre-conditions
Procedure
Result

Test 1
1. The ICT displays or processes video with synchronized audio.
2. Captions are provided in the video.
1. Check that there is a mechanism to display the captions.
Pass: Check 1 is true
Fail: Check 1 is false
Test 2
1. The ICT displays or processes video with synchronized audio.
2. Closed captions are provided by the content.
1. Check that there is a mechanism to choose to display the captions.
Pass: Check 1 is true
Fail: Check 1 is false

ETSI

107
EN 301 549 V2.1.2 (2018-08)

C.7.1.2

Captioning synchronization

Type of assessment
Pre-conditions
Procedure
ResultC.7.1.3

Inspection
1. The ICT has a mechanism to display captions.
1. Check that the mechanism to display the captions preserves the synchronization
between the audio and corresponding captions.
Pass: Check 1 is true
Fail: Check 1 is false

Preservation of captioning

Type of assessment
Pre-conditions
Procedure
ResultInspection
1. The ICT transmits converts or records video with synchronized audio.
1. Check that the ICT preserves caption data such that it can be displayed in a mannerconsistent with clauses 7.1.1 and 7.1.2.
Pass: Check 1 is true
Fail: Check 1 is false

C.7.2

Audio description technology

C.7.2.1

Audio description playback

Type of assessment
Pre-conditions
Procedure

ResultC.7.2.2

Audio description synchronization

Type of assessment
Pre-conditions
Procedure
ResultC.7.2.3

ResultInspection
1. The ICT transmits converts or records video with synchronized audio.
1. Check that the ICT preserves audio description data such that it can be played in amanner consistent with clauses 7.2.1 and 7.2.2.
Pass: Check 1 is true
Fail: Check 1 is false

User controls for captions and audio description

Type of assessment
Pre-conditions
Procedure
ResultInspection
1. The ICT has a mechanism to play audio description.
1. Check that the synchronization between the audio/visual content and thecorresponding audio description is preserved.
Pass: Check 1 is true
Fail: Check 1 is false

Preservation of audio description

Type of assessment
Pre-conditions
Procedure

C.7.3

Inspection
1. The ICT displays video with synchronized audio.
1. Check that there is an explicit and separate mechanism for audio description.
2. Check that there is a mechanism to select and play the audio description to thedefault audio channel.
3. Check that the ICT enables the user to select and play several audio tracks.
Pass: Check 1 and 2 are true or 1 is false and 3 is true
Fail: Check 1 is true and 2 is false or 1 is false and 3 is false

Inspection
1. The ICT primarily display materials containing video with associated audio content.
1. Check that user controls to activate subtitling and audio descriptions are provided tothe user at the same level of interaction as the primary media controls.
Pass: Check 1 is true
Fail: Check 1 is false

ETSI

108
EN 301 549 V2.1.2 (2018-08)

C.8

Hardware

C.8.1

GeneralC.8.1.1

Generic requirements

Clause 8.1.1 contains no requirements requiring test.

C.8.1.2

Standard connections

Type of assessment
Pre-conditions
Procedure

Inspection
1. The ICT provides user input or output device connection points.
1. Check that one type of connection conforms to an industry standard non-proprietary
format.
2. Check that one type of connection conforms to an industry standard non-proprietary
format through the use of commercially available adapters.
Pass: Check 1 or 2 is true
Fail: Checks 1 and 2 are false
The connections may be physical or wireless connections.

ResultNOTE:

C.8.1.3

ColourType of assessment
Pre-conditions
Procedure
ResultC.8.2

Hardware products with speech output

C.8.2.1
C.8.2.1.1

Speech volume gain
Speech volume range

Type of assessment
Pre-conditions
Procedure

ResultC.8.2.1.2

Procedure

Inspection based on measurement data
1. The ICT hardware has speech output.
1. Check that the ICT is certified to meet ANSI/TIA-4965 [i.2].
2. Measure the level (in dB) of the speech output at the lowest volume setting.
3. Measure the level (in dB) of the speech output at the highest volume setting.
4. Check that the range between 1 and 2 is greater than or equal to 18 dB.
Pass: Check 1 or 4 is true
Fail: Check 1 and 4 are false

Incremental volume control

Type of assessment
Pre-conditions

ResultInspection
1. The hardware aspects of the ICT conveys visual information using colour coding asa means to indicate an action, to prompt a response, or to distinguish a visual element.
1. Check that an alternative form of visual coding is provided.
Pass: Check 1 is true
Fail: Check 1 is false

Inspection based on measurement data
1. The ICT hardware has speech output.
2. The volume control is incremental.
1. Measure the level (in dB) of the speech output at the lowest volume setting.
2. Check if one intermediate step provides a level 12 dB above the lowest volume levelmeasured in step 1.
Pass: Check 2 is true
Fail: Check 2 is false

ETSI

109
EN 301 549 V2.1.2 (2018-08)

C.8.2.2

Magnetic coupling

C.8.2.2.1

Fixed-line devices

Type of assessment
Pre-conditions

Procedure

ResultC.8.2.2.2

Wireless communication devices

Type of assessment
Pre-conditions
Procedure

ResultC.8.3

Inspection based on measurement data
1. The ICT hardware is a fixed line communication device with an audio output that isnormally held to the ear.
2. The ICT carries the "T" symbol.
1. Check that the ICT is certified to meet TIA-1083-A [i.24].
2. Measurements are made according to ETSI ES 200 381-1 [2] which prove that therequirements defined in that standard are fulfilled.
Pass: Check 1 or 2 is true
Fail: Checks 1 and 2 are false

Inspection based on measurement data
1. The ICT hardware is a wireless communication device which is normally held to theear.
1. Check that the ICT is certified to meet ANSI/IEEE C63.19 [i.1].
2. Check that the ICT provide a means of magnetic coupling to hearing technologies
which meets the requirements of ETSI ES 200 381-2 [3].
Pass: Check 1 or 2 is true
Fail: Checks 1 and 2 are false

Physical access to ICT

C.8.3.1

GeneralClause 8.3.1 is advisory only and contains no requirements requiring test.
The tests in clause C.8.3 are made available to support the recommendations in clause 8.3. They should be applied if therecommendations in clause 8.3 are being followed. However, tests in clause C.8.3 do not form part of the compliancerequirements and are not required in any compliance report.

C.8.3.2
C.8.3.2.1

Clear floor or ground space
Change in levela)Type of assessment
Pre-conditions
Procedure
ResultInspection and measurement
1. There is a change in level integral to the ICT.
1. Check that the change in level is ramped with a slope less than1:48.
If check 1 is true then this recommendation is followed.

Type of assessment
Pre-conditions

Inspection and measurement
1. There is a change in level integral to the ICT.
2. The change in level is less than or equal to 6,4 mm.
1. Check that the step is vertical or ramped.
If check 1 is true then this recommendation is followed.

b)

Procedure
Resultc)
Type of assessment
Pre-conditions
Procedure
ResultInspection and measurement
1. There is a change in level integral to the ICT.
2. The change in level is less than or equal to 13 mm.
1. Check that the ramp has a slope less than 1:2.
If check 1 is true then this recommendation is followed.

ETSI

110
EN 301 549 V2.1.2 (2018-08)

C.8.3.2.2

Clear floor or ground space

Type of assessment
Pre-conditions
Procedure

ResultInspection and measurement
1. The operating area is integral to the ICT.
1. Check that the operating area is a rectangle with minimum dimension on one edgeof 760 mm.
2. Check that the operating area is a rectangle with the minimum dimension on theother edge of 1 220 mm.
If check 1 is true then this recommendation is followed.

C.8.3.2.3

Approach

C.8.3.2.3.1

GeneralType of assessment
Pre-conditions
Procedure
ResultC.8.3.2.3.2

Forward Approach

Type of assessment
Pre-conditions

Procedure
ResultC.8.3.2.3.3

Procedure
ResultInspection and measurement
1. The operating area is inside an alcove integral to the ICT.
2. The depth of the alcove is greater than 380 mm.
3. A parallel approach is possible.
1. Check that the width of the access space is greater than 1 525 mm.
If check 1 is true then this recommendation is followed.

Knee and toe clearance widthType of assessment
Pre-conditions
Procedure
ResultC.8.3.2.5

Inspection and measurement
1. The operating area is inside an alcove integral to the ICT.
2. The depth of the alcove is greater than 610 mm.
3. A forward approach is necessary.
1. Check that the width of the alcove is greater than 915 mm.
If check 1 is true then this recommendation is followed.

Parallel Approach

Type of assessment
Pre-conditions

C.8.3.2.4

Inspection
1. Access space is integral to the ICT.
1. Check that one full side of the space is unobstructed.
If check 1 is true then this recommendation is followed.

Inspection and measurement
1. The space under an obstacle integral to the ICT is part of an access space.
1. Check that the width of the knee clearance is greater than 760 mm.
2. Check that the width of the toe clearance is greater than 760 mm.
If check 1 is true then this recommendation is followed.

Toe clearancea)Type of assessment
Pre-conditions

Procedure
ResultInspection and measurement
1. The ICT is free-standing.
2. There is a space under any obstacle integral to the ICT that is less than 230 mm
over the floor.
1. Check that the toe clearance does not extend more than 635 mm under the
obstacle.
If check 1 is true then this recommendation is followed.

b)
Type of assessment
Pre-conditions

Procedure
ResultInspection and measurement
1. The ICT is free-standing.
2. There is a space under any obstacle integral to the ICT that is less than 230 mm
over the floor.
1. Check that the toe clearance extends more than 430 mm under the whole obstacle.
If check 1 is true then this recommendation is followed.

ETSI

111
EN 301 549 V2.1.2 (2018-08)c)Type of assessment
Pre-conditions
Procedure
ResultC.8.3.2.6

Inspection and measurement
1. The ICT is free-standing.
2. There is an obstacle integral to the ICT at less than 230 mm over the floor.
1. Check that the toe clearance extends less than 150 mm under the obstacle.
If check 1 is true then this recommendation is followed.

Knee clearancea)Type of assessment
Pre-conditions
Procedure
ResultInspection and measurement
1. There is an obstacle that is integral to the ICT.
2. The obstacle is between 230 mm and 685 mm above the floor.
1. Check that there is a clearance less than 635 mm at a height of 230 mm.
If check 1 is true then this recommendation is followed.

b)
Type of assessment
Pre-conditions
Procedure
ResultInspection and measurement
1. There is an obstacle that is integral to the ICT.
2. The obstacle is between 230 mm and 685 mm above the floor.
1. Check that there is a clearance more than 280 mm at a height of 230 mm.
If check 1 is true then this recommendation is followed.

c)
Type of assessment
Pre-conditions
Procedure
ResultInspection and measurement
1. There is an obstacle that is integral to the ICT.
2. The obstacle is between 230 mm and 685 mm above the floor.
1. Check that there is a clearance more than 205 mm at a height of 685 mm
If check 1 is true then this recommendation is followed.

d)Type of assessment
Pre-conditions
Procedure
ResultInspection and measurement
1. There is an obstacle that is integral to the ICT.
2. The obstacle is between 230 mm and 685 mm above the floor.
1. Check that the reduction in depth of the clearance is no greater than 25 mm for each
150 mm in height.
If check 1 is true then this recommendation is followed.

C.8.3.3

Reach range for ICT

C.8.3.3.1

Forward reach

C.8.3.3.1.1
Type of assessment
Pre-conditions
Procedure
ResultC.8.3.3.1.2
Type of assessment
Pre-conditions
Procedure
ResultUnobstructed high forward reachInspection and measurement
1. The access space is integral to the ICT.
2. There is an unobstructed access to the controls.
1. Check that the height of the topmost essential control is no higher than 1 220 mmabove the floor contact of the ICT.
If check 1 is true then this recommendation is followed.

Unobstructed low forward reachInspection and measurement
1. The access space is integral to the ICT.
2. There is an unobstructed access to the controls.
1. Check that the height of the lowest essential control is no lower than 380 mm above
the floor contact of the ICT.
If check 1 is true then this recommendation is followed.

ETSI

112
EN 301 549 V2.1.2 (2018-08)

C.8.3.3.1.3

Obstructed reach

C.8.3.3.1.3.1

Clear floor space

Type of assessment
Pre-conditions
Procedure
ResultC.8.3.3.1.3.2

Obstructed (< 510 mm) forward reachType of assessment
Pre-conditions

Procedure
ResultC.8.3.3.1.3.3

Inspection and measurement
1. The access space is integral to the ICT.
2. There is an integral obstructed access to the controls.
3. The obstruction is less than 510 mm
1. Check that the height of the topmost essential control is no higher than 1 220 mmabove the floor contact of the ICT.
If check 1 is true then this recommendation is followed.

Obstructed (< 635 mm) forward reachType of assessment
Pre-conditions

Procedure
ResultC.8.3.3.2

Inspection and measurement
1. The access space is integral to the ICT.
2. There is an integral obstructed access to the controls.
1. Check that there is clear floor space greater than the required reach depth over the
obstruction.
If check 1 is true then this recommendation is followed.

Inspection and measurement
1. The access space is integral to the ICT.
2. There is an integral obstructed access to the controls.
3. The obstruction is between 510 mm and 635 mm.
1. Check that the height of the topmost essential control is no higher than 1 120 mmabove the floor contact of the ICT.
If check 1 is true then this recommendation is followed.

Side reach

C.8.3.3.2.1
Type of assessment
Pre-conditions

Procedure
ResultC.8.3.3.2.2
Type of assessment
Pre-conditions

Procedure
ResultUnobstructed high side reachInspection and measurement
1. The access space is integral to the ICT.
2. A parallel approach to the ICT is possible.
3. The side reach is unobstructed or obstructed by a part less than 255 mm wide.
1. Check that the height of the topmost essential control is less than or equal to
1 220 mm above the floor contact of the ICT.
If check 1 is true then this recommendation is followed.

Unobstructed low side reachInspection and measurement
1. The access space is integral to the ICT.
2. A parallel approach to the ICT is possible.
3. The side reach is unobstructed or obstructed by a part less than 255 mm wide.
1. Check that the height of the lowest essential control is greater than or equal to
380 mm above the floor contact of the ICT.
If check 1 is true then this recommendation is followed.

C.8.3.3.2.3

Obstructed side reach

C.8.3.3.2.3.1

Obstructed (< 255 mm) side reachType of assessment
Pre-conditions

Procedure
ResultInspection and measurement
1. The access space is integral to the ICT.
2. A parallel approach to the ICT is possible.
3. There is an obstacle integral to the ICT with a height less than 865 mm.
4. The side reach is obstructed by a part less than 255 mm wide.
1. Check that the height of the topmost essential control no higher than 1 220 mmabove the floor contact of the ICT.
If check 1 is true then this recommendation is followed.

ETSI

113
EN 301 549 V2.1.2 (2018-08)

C.8.3.3.2.3.2

Obstructed (< 610 mm) side reachType of assessment
Pre-conditions

Procedure
ResultC.8.3.4

Visibility

Type of assessment
Pre-conditions
Procedure
ResultC.8.3.5

ResultNumeric keys

Type of assessment
Pre-conditions
Procedure
ResultC.8.4.2
C.8.4.2.1

Inspection
1. The ICT has physical numeric keys arranged in a 12-key telephone keypad layout.
1. Check that the number five key is tactilely distinct from the other keys of the keypad.
Pass: Check 1 is true
Fail: Check 1 is false

Operation of mechanical parts
Means of operation of mechanical parts

Type of assessment
Pre-conditions
Procedure
ResultInspection
1. The ICT has operable parts that requires grasping, pinching, or twisting of the wrist
to operate.
1. Check that there is an accessible alternative means of operation that does not
require these actions.
Pass: Check 1 is true
Fail: Check 1 is false

Force of operation of mechanical parts

Type of assessment
Pre-conditions
Procedure
ResultInspection and measurement
1. The ICT is intended to be installed.
1. Check that instructions are made available which outline a method to install the ICT
in a manner that ensures that the dimensions of the integral spaces of the ICT conformto clauses 8.3.2 to 8.3.4.
If check 1 is true then this recommendation is followed.

Mechanically operable parts

C.8.4.1

C.8.4.2.2

Inspection and measurement
1. The operating area is integral to the ICT.
2. A display screen is provided.
1. Check that the screen is readable from a point located 40 inches (1 015 mm) above
the centre of the clear floor space.
If check 1 is true then this recommendation is followed.

Installation instructions

Type of assessment
Pre-conditions
Procedure

C.8.4

Inspection and measurement
1. The access space is integral to the ICT.
2. A parallel approach to the ICT is possible.
3. There is an obstacle integral to the ICT with a height less than 865 mm.
4. The side reach is obstructed by a part more than 255 mm and less than 610 mm
wide.
1. Check that the height of the topmost essential control is no higher than 1 170 mmabove the floor contact of the ICT.
If check 1 is true then this recommendation is followed.

Inspection and measurement
1. The ICT has a control which requires a force greater than 22,2 N to operate it.
1. Check that an accessible alternative means of operation is provided that requires aforce less than or equal to 22,2 N.
Pass: Check 1 is true
Fail: Check 1 is false

ETSI

114
EN 301 549 V2.1.2 (2018-08)

C.8.4.3

Keys, tickets and fare cards

Type of assessment
Pre-conditions
Procedure
ResultC.8.5

Inspection and measurement
1. ICT provides keys, tickets or fare cards, and their orientation is important for
further use.
1. Check that keys, tickets or fare cards have an orientation that is tactilely
discernible.
Pass: Check 1 is true
Fail: Check 1 is false

Tactile indication of speech mode

Type of assessment
Pre-conditions
Procedure
ResultInspection and measurement
1. The ICT is designed for shared use.
2. Speech output is available.
1. Check that a tactile indication of the means to initiate the speech mode ofoperation is provided.
Pass: Check 1 is true
Fail: Check 1 is false

C.9

Web

C.9.0

General (informative)

Clause 9.0 is informative only and contains no requirements requiring test.

C.9.1

Perceivable

C.9.1.1

Text alternatives

C.9.1.1.1

Non-text content

Type of assessment
Pre-conditions
Procedure
ResultC.9.1.2
C.9.1.2.1

Time-based media
Audio-only and video-only (pre-recorded)Type of assessment
Pre-conditions
Procedure
ResultC.9.1.2.2

Inspection
1. The ICT is a web page.
1. Check that the web page does not fail WCAG 2.1 Success Criterion 1.2.1 Audio-only
and Video-only (Prerecorded).
Pass: Check 1 is true
Fail: Check 1 is false

Captions (pre-recorded)Type of assessment
Pre-conditions
Procedure
ResultInspection
1. The ICT is a web page.
1. Check that the web page does not fail WCAG 2.1 Success Criterion 1.1.1 Non-text
content.
Pass: Check 1 is true
Fail: Check 1 is false

Inspection
1. The ICT is a web page.
1. Check that the web page does not fail WCAG 2.1 Success Criterion 1.2.2 Captions(Prerecorded).
Pass: Check 1 is true
Fail: Check 1 is false

ETSI

115
EN 301 549 V2.1.2 (2018-08)

C.9.1.2.3

Audio description or media alternative (pre-recorded)Type of assessment
Pre-conditions
Procedure
ResultC.9.1.2.4

Captions (live)

Type of assessment
Pre-conditions
Procedure
ResultC.9.1.2.5

ResultC.9.1.3.1

Info and relationships

ResultResultResultInspection
1. The ICT is a web page.
1. Check that the web page does not fail WCAG 2.1 Success Criterion 1.3.3 Sensory
Characteristics.
Pass: Check 1 is true
Fail: Check 1 is false

Orientation

Type of assessment
Pre-conditions
Procedure
ResultInspection
1. The ICT is a web page.
1. Check that the web page does not fail WCAG 2.1 Success Criterion 1.3.2
Meaningful Sequence.
Pass: Check 1 is true
Fail: Check 1 is false

Sensory characteristics

Type of assessment
Pre-conditions
Procedure

C.9.1.3.4

Inspection
1. The ICT is a web page.
1. Check that the web page does not fail WCAG 2.1 Success Criterion 1.3.1 Info andRelationships.
Pass: Check 1 is true
Fail: Check 1 is false

Meaningful sequenceType of assessment
Pre-conditions
Procedure

C.9.1.3.3

Inspection
1. The ICT is a web page.
1. Check that the web page does not fail WCAG 2.1 Success Criterion 1.2.5 Audio
Description (Prerecorded).
Pass: Check 1 is true
Fail: Check 1 is false

Adaptable

Type of assessment
Pre-conditions
Procedure

C.9.1.3.2

Inspection
1. The ICT is a web page.
1. Check that the web page does not fail WCAG 2.1 Success Criterion 1.2.4 Captions(Live).
Pass: Check 1 is true
Fail: Check 1 is false

Audio description (pre-recorded)Type of assessment
Pre-conditions
Procedure

C.9.1.3

Inspection
1. The ICT is a web page.
1. Check that the web page does not fail WCAG 2.1 Success Criterion 1.2.3 Audio
Description or Media Alternative (Prerecorded).
Pass: Check 1 is true
Fail: Check 1 is false

Inspection
1. The ICT is a web page.
1. Check that the web page does not fail WCAG 2.1 Success Criterion 1.3.4
Orientation.
Pass: Check 1 is true
Fail: Check 1 is false

ETSI

116
EN 301 549 V2.1.2 (2018-08)

C.9.1.3.5

Identify input purpose

Type of assessment
Pre-conditions
Procedure

Inspection
1. The ICT is a web page.
1. Check that the web page does not fail WCAG 2.1 Success Criterion 1.3.5 Identify
Input Purpose.
Pass: Check 1 is true
Fail: Check 1 is false

ResultC.9.1.4

Distinguishable

C.9.1.4.1

Use of colour

Type of assessment
Pre-conditions
Procedure

Inspection
1. The ICT is a web page.
1. Check that the web page does not fail WCAG 2.1 Success Criterion 1.4.1 Use ofColor.
Pass: Check 1 is true
Fail: Check 1 is false

ResultC.9.1.4.2

Audio control

Type of assessment
Pre-conditions
Procedure

Inspection
1. The ICT is a web page.
1. Check that the web page does not fail WCAG 2.1 Success Criterion 1.4.2 Audio
Control.
Pass: Check 1 is true
Fail: Check 1 is false

ResultC.9.1.4.3

Contrast (minimum)

Type of assessment
Pre-conditions
Procedure

Inspection
1. The ICT is a web page.
1. Check that the web page does not fail WCAG 2.1 Success Criterion 1.4.3 Contrast(Minimum).
Pass: Check 1 is true
Fail: Check 1 is false

ResultC.9.1.4.4

Resize text

Type of assessment
Pre-conditions
Procedure
ResultC.9.1.4.5

Inspection
1. The ICT is a web page.
1. Check that the web page does not fail WCAG 2.1 Success Criterion 1.4.4 Resize text.
Pass: Check 1 is true
Fail: Check 1 is false

Images of text

Type of assessment
Pre-conditions
Procedure
ResultC.9.1.4.6

Void

C.9.1.4.7

Void

C.9.1.4.8

Void

C.9.1.4.9

Void

Inspection
1. The ICT is a web page.
1. Check that the web page does not fail WCAG 2.1 Success Criterion 1.4.5 Images of
Text.
Pass: Check 1 is true
Fail: Check 1 is false

ETSI

117
EN 301 549 V2.1.2 (2018-08)

C.9.1.4.10

Reflow

Type of assessment
Pre-conditions
Procedure
ResultC.9.1.4.11

Non-text contrast

Type of assessment
Pre-conditions
Procedure
ResultC.9.1.4.12

ResultResultC.9.2.1
C.9.2.1.1

Keyboard accessible
Keyboard
Inspection
1. The ICT is a web page.
1. Check that the web page does not fail WCAG 2.1 Success Criterion 2.1.1 Keyboard.
Pass: Check 1 is true
Fail: Check 1 is false

No keyboard trap

Type of assessment
Pre-conditions
Procedure
ResultC.9.2.1.3

Inspection
1. The ICT is a web page.
1. Check that the web page does not fail WCAG 2.1 Success Criterion 1.4.13 Content
on Hover or Focus.
Pass: Check 1 is true
Fail: Check 1 is false

OperableType of assessment
Pre-conditions
Procedure
ResultC.9.2.1.2

Inspection
1. The ICT is a web page.
1. Check that the web page does not fail WCAG 2.1 Success Criterion 1.4.12 Text
spacing.
Pass: Check 1 is true
Fail: Check 1 is false

Content on hover or focus

Type of assessment
Pre-conditions
Procedure

C.9.2

Inspection
1. The ICT is a web page.
1. Check that the web page does not fail WCAG 2.1 Success Criterion 1.4.11 Non-text
Contrast.
Pass: Check 1 is true
Fail: Check 1 is false

Text spacing

Type of assessment
Pre-conditions
Procedure

C.9.1.4.13

Inspection
1. The ICT is a web page.
1. Check that the web page does not fail WCAG 2.1 Success Criterion 1.4.10 Reflow.
Pass: Check 1 is true
Fail: Check 1 is false

Inspection
1. The ICT is a web page.
1. Check that the web page does not fail WCAG 2.1 Success Criterion 2.1.2 No
Keyboard Trap.
Pass: Check 1 is true
Fail: Check 1 is false

Void

ETSI

118
EN 301 549 V2.1.2 (2018-08)

C.9.2.1.4

Character key shortcuts

Type of assessment
Pre-conditions
Procedure
ResultC.9.2.2

Inspection
1. The ICT is a web page.
1. Check that the web page does not fail WCAG 2.1 Success Criterion 2.1.4 Character
Key Shortcuts.
Pass: Check 1 is true
Fail: Check 1 is false

Enough time

C.9.2.2.1

Timing adjustable

Type of assessment
Pre-conditions
Procedure
ResultC.9.2.2.2

Inspection
1. The ICT is a web page.
1. Check that the web page does not fail WCAG 2.1 Success Criterion 2.2.1 Timing
Adjustable.
Pass: Check 1 is true
Fail: Check 1 is false

Pause, stop, hide

Type of assessment
Pre-conditions
Procedure
ResultInspection
1. The ICT is a web page.
1. Check that the web page does not fail WCAG 2.1 Success Criterion 2.2.2 Pause,
Stop, Hide.
Pass: Check 1 is true
Fail: Check 1 is false

C.9.2.3

Seizures and physical reactions

C.9.2.3.1

Three flashes or below threshold

Type of assessment
Pre-conditions
Procedure
ResultC.9.2.4

Inspection
1. The ICT is a web page.
1. Check that the web page does not fail WCAG 2.1 Success Criterion 2.3.1 Three
Flashes or Below Threshold.
Pass: Check 1 is true
Fail: Check 1 is false

Navigable

C.9.2.4.1

Bypass blocks

Type of assessment
Pre-conditions
Procedure
ResultC.9.2.4.2
Type of assessment
Pre-conditions
Procedure
ResultInspection
1. The ICT is a web page.
1. Check that the web page does not fail WCAG 2.1 Success Criterion 2.4.1 Bypass
Blocks.
Pass: Check 1 is true
Fail: Check 1 is false

Page titled
Inspection
1. The ICT is a web page.
1. Check that the web page does not fail WCAG 2.1 Success Criterion 2.4.2 Page Titled.
Pass: Check 1 is true
Fail: Check 1 is false

ETSI

119
EN 301 549 V2.1.2 (2018-08)

C.9.2.4.3

Focus OrderType of assessment
Pre-conditions
Procedure
ResultC.9.2.4.4

Link purpose (in context)

Type of assessment
Pre-conditions
Procedure
ResultC.9.2.4.5

ResultResultResultC.9.2.5.1

Pointer gestures

ResultInspection
1. The ICT is a web page.
1. Check that the web page does not fail WCAG 2.1 Success Criterion 2.5.1 Pointer
Gestures.
Pass: Check 1 is true
Fail: Check 1 is false

Pointer cancellation

Type of assessment
Pre-conditions
Procedure
ResultInspection
1. The ICT is a web page.
1. Check that the web page does not fail WCAG 2.1 Success Criterion 2.4.7 Focus
Visible.
Pass: Check 1 is true
Fail: Check 1 is false

Input modalities

Type of assessment
Pre-conditions
Procedure

C.9.2.5.2

Inspection
1. The ICT is a web page.
1. Check that the web page does not fail WCAG 2.1 Success Criterion 2.4.6 Headings
and Labels.
Pass: Check 1 is true
Fail: Check 1 is false

Focus visible

Type of assessment
Pre-conditions
Procedure

C.9.2.5

Inspection
1. The ICT is a web page.
1. Check that the web page does not fail WCAG 2.1 Success Criterion 2.4.5 Multiple
Ways.
Pass: Check 1 is true
Fail: Check 1 is false

Headings and labels

Type of assessment
Pre-conditions
Procedure

C.9.2.4.7

Inspection
1. The ICT is a web page.
1. Check that the web page does not fail WCAG 2.1 Success Criterion 2.4.4 Link
Purpose (In Context).
Pass: Check 1 is true
Fail: Check 1 is false

Multiple ways

Type of assessment
Pre-conditions
Procedure

C.9.2.4.6

Inspection
1. The ICT is a web page.
1. Check that the web page does not fail WCAG 2.1 Success Criterion 2.4.3 Focus
Order.
Pass: Check 1 is true
Fail: Check 1 is false

Inspection
1. The ICT is a web page.
1. Check that the web page does not fail WCAG 2.1 Success Criterion 2.5.2 PointerCancellation.
Pass: Check 1 is true
Fail: Check 1 is false

ETSI

120
EN 301 549 V2.1.2 (2018-08)

C.9.2.5.3

Label in name

Type of assessment
Pre-conditions
Procedure
ResultC.9.2.5.4

Motion actuation

Type of assessment
Pre-conditions
Procedure
ResultC.9.3
C.9.3.1
C.9.3.1.1

Inspection
1. The ICT is a web page.
1. Check that the web page does not fail WCAG 2.1 Success Criterion 2.5.4 Motion
Actuation.
Pass: Check 1 is true
Fail: Check 1 is false

Understandable
Readable
Language of pageType of assessment
Pre-conditions
Procedure
ResultC.9.3.1.2

Inspection
1. The ICT is a web page.
1. Check that the web page does not fail WCAG 2.1 Success Criterion 2.5.3 Label in
Name.
Pass: Check 1 is true
Fail: Check 1 is false

Inspection
1. The ICT is a web page.
1. Check that the web page does not fail WCAG 2.1 Success Criterion 3.1.1 Languageof Page.
Pass: Check 1 is true
Fail: Check 1 is false

Language of parts

Type of assessment
Pre-conditions
Procedure
ResultInspection
1. The ICT is a web page.
1. Check that the web page does not fail WCAG 2.1 Success Criterion 3.1.2 Languageof Parts.
Pass: Check 1 is true
Fail: Check 1 is false

C.9.3.2

Predictable

C.9.3.2.1

On focus

Type of assessment
Pre-conditions
Procedure
ResultC.9.3.2.2

Inspection
1. The ICT is a web page.
1. Check that the web page does not fail WCAG 2.1 Success Criterion 3.2.1 On Focus.
Pass: Check 1 is true
Fail: Check 1 is false

On input

Type of assessment
Pre-conditions
Procedure
ResultInspection
1. The ICT is a web page.
1. Check that the web page does not fail WCAG 2.1 Success Criterion 3.2.2 On Input.
Pass: Check 1 is true
Fail: Check 1 is false

ETSI

121
EN 301 549 V2.1.2 (2018-08)

C.9.3.2.3

Consistent navigation

Type of assessment
Pre-conditions
Procedure
ResultC.9.3.2.4

Consistent identification

Type of assessment
Pre-conditions
Procedure
ResultC.9.3.3
C.9.3.3.1

Error identification

ResultResultResultInspection
1. The ICT is a web page.
1. Check that the web page does not fail WCAG 2.1 Success Criterion 3.3.3 Error
Suggestion.
Pass: Check 1 is true
Fail: Check 1 is false

Error prevention (legal, financial, data)

Type of assessment
Pre-conditions
Procedure
ResultInspection
1. The ICT is a web page.
1. Check that the web page does not fail WCAG 2.1 Success Criterion 3.3.2 Labels or
Instructions.
Pass: Check 1 is true
Fail: Check 1 is false

Error suggestion

Type of assessment
Pre-conditions
Procedure

C.9.3.3.4

Inspection
1. The ICT is a web page.
1. Check that the web page does not fail WCAG 2.1 Success Criterion 3.3.1 Error
Identification.
Pass: Check 1 is true
Fail: Check 1 is false

Labels or instructions

Type of assessment
Pre-conditions
Procedure

C.9.3.3.3

Inspection
1. The ICT is a web page.
1. Check that the web page does not fail WCAG 2.1 Success Criterion 3.2.4 Consistent
Identification.
Pass: Check 1 is true
Fail: Check 1 is false

Input assistanceType of assessment
Pre-conditions
Procedure

C.9.3.3.2

Inspection
1. The ICT is a web page.
1. Check that the web page does not fail WCAG 2.1 Success Criterion 3.2.3 Consistent
Navigation.
Pass: Check 1 is true
Fail: Check 1 is false

Inspection
1. The ICT is a web page.
1. Check that the web page does not fail WCAG 2.1 Success Criterion 3.3.4 Error
Prevention (Legal, Financial, Data).
Pass: Check 1 is true
Fail: Check 1 is false

ETSI

122
EN 301 549 V2.1.2 (2018-08)

C.9.4

RobustC.9.4.1

Compatible

C.9.4.1.1

ParsingType of assessment
Pre-conditions
Procedure
ResultC.9.4.1.2

Name, role, value

Type of assessment
Pre-conditions
Procedure
ResultC.9.4.1.3

ResultInspection
1. The ICT is a web page.
1. Check that the web page does not fail WCAG 2.1 Success Criterion 4.1.3 Status
Messages.
Pass: Check 1 is true
Fail: Check 1 is false

WCAG 2.1 conformance requirements

Type of assessment
Pre-conditions
Procedure

ResultInspection
1. The ICT is a web page.
1. Check that the web page does not fail WCAG 2.1 Success Criterion 4.1.2 Name,
Role, Value.
Pass: Check 1 is true
Fail: Check 1 is false

Status messages

Type of assessment
Pre-conditions
Procedure

C.9.5

Inspection
1. The ICT is a web page.
1. Check that the web page does not fail WCAG 2.1 Success Criterion 4.1.1 Parsing.
Pass: Check 1 is true
Fail: Check 1 is false

Inspection
1. The ICT is a web page.
1. Check that the web page satisfies WCAG 2.1 [5] conformance requirement "1:
Conformance level" at Level AA.
2. Check that the web page satisfies WCAG 2.1 [5] conformance requirement "2:
Full pages".
3. Check that the web page satisfies WCAG 2.1 [5] conformance requirement "3:Complete processes".
4. Check that the web page satisfies WCAG 2.1 [5] conformance requirement "4:
Only Accessibility-Supported Ways of Using Technologies".
5. Check that the web page satisfies WCAG 2.1 [5] conformance requirement "5:
Non-interference".
Pass: All checks are true
Fail: Any check is false

C.10

Non-web documents

C.10.0General (informative)

Clause 10.0 is advisory only and contains no requirements requiring test.

ETSI

123
EN 301 549 V2.1.2 (2018-08)

C.10.1

Perceivable

C.10.1.1

Text alternatives

C.10.1.1.1

Non-text content

Type of assessment
Pre-conditions
Procedure
ResultC.10.1.2
C.10.1.2.1

Time-based media
Audio-only and video-only (pre-recorded)Type of assessment
Pre-conditions
Procedure
ResultC.10.1.2.2

ResultResultInspection
1. The ICT is a non-web document.
1. Check that the document does not fail WCAG 2.1 Success Criterion 1.2.3 Audio
Description or Media Alternative (Prerecorded).
Pass: Check 1 is true
Fail: Check 1 is false

Captions (live)

Type of assessment
Pre-conditions
Procedure
ResultInspection
1. The ICT is a non-web document.
1. Check that the document does not fail WCAG 2.1 Success Criterion 1.2.2 Captions(Prerecorded).
Pass: Check 1 is true
Fail: Check 1 is false

Audio description or media alternative (pre-recorded)Type of assessment
Pre-conditions
Procedure

C.10.1.2.4

Inspection
1. The ICT is a non-web document.
1. Check that the document does not fail WCAG 2.1 Success Criterion 1.2.1 Audio-only
and Video-only (Prerecorded).
Pass: Check 1 is true
Fail: Check 1 is false

Captions (pre-recorded)Type of assessment
Pre-conditions
Procedure

C.10.1.2.3

Inspection
1. The ICT is a non-web document.
1. Check that the document does not fail WCAG 2.1 Success Criterion 1.1.1 Non-text
content.
Pass: Check 1 is true
Fail: Check 1 is false

Inspection
1. The ICT is a non-web document.
1. Check that the document does not fail WCAG 2.1 Success Criterion 1.2.4 Captions(Live).
Pass: Check 1 is true
Fail: Check 1 is false

ETSI

124
EN 301 549 V2.1.2 (2018-08)

C.10.1.2.5

Audio description (pre-recorded)Type of assessment
Pre-conditions
Procedure
ResultC.10.1.3
C.10.1.3.1

Adaptable
Info and relationships

Type of assessment
Pre-conditions
Procedure
ResultC.10.1.3.2

ResultResultInspection
1. The ICT is a non-web document.
1. Check that the document does not fail WCAG 2.1 Success Criterion 1.3.3 Sensory
Characteristics.
Pass: Check 1 is true
Fail: Check 1 is false

Orientation

Type of assessment
Pre-conditions
Procedure
ResultC.10.1.3.5

Inspection
1. The ICT is a non-web document.
1. Check that the document does not fail WCAG 2.1 Success Criterion 1.3.2
Meaningful Sequence.
Pass: Check 1 is true
Fail: Check 1 is false

Sensory characteristics

Type of assessment
Pre-conditions
Procedure

C.10.1.3.4

Inspection
1. The ICT is a non-web document.
1. Check that the document does not fail WCAG 2.1 Success Criterion 1.3.1 Info andRelationships.
Pass: Check 1 is true
Fail: Check 1 is false

Meaningful sequenceType of assessment
Pre-conditions
Procedure

C.10.1.3.3

Inspection
1. The ICT is a non-web document.
1. Check that the document does not fail WCAG 2.1 Success Criterion 1.2.5 Audio
Description (Prerecorded).
Pass: Check 1 is true
Fail: Check 1 is false

Inspection
1. The ICT is a non-web document.
1. Check that the document does not fail WCAG 2.1 Success Criterion 1.3.4
Orientation.
Pass: Check 1 is true
Fail: Check 1 is false

Identify input purpose

Type of assessment
Pre-conditions
Procedure
ResultInspection
1. The ICT is a non-web document.
1. Check that the document does not fail WCAG 2.1 Success Criterion 1.3.5 Identify
Input Purpose.
Pass: Check 1 is true
Fail: Check 1 is false

C.10.1.4

Distinguishable

C.10.1.4.1

Use of colour

Type of assessment
Pre-conditions

Inspection
1. The ICT is a non-web document.

ETSI

125
EN 301 549 V2.1.2 (2018-08)

Procedure

1. Check that the document does not fail WCAG 2.1 Success Criterion 1.4.1 Use ofColor.
Pass: Check 1 is true
Fail: Check 1 is false

ResultC.10.1.4.2

Audio control

Type of assessment
Pre-conditions
Procedure
ResultC.10.1.4.3

Contrast (minimum)

Type of assessment
Pre-conditions
Procedure
ResultC.10.1.4.4

Inspection
1. The ICT is a non-web document.
1. Check that the document does not fail WCAG 2.1 Success Criterion 1.4.3 Contrast(Minimum).
Pass: Check 1 is true
Fail: Check 1 is false

Resize text

Type of assessment
Pre-conditions
Procedure
ResultC.10.1.4.5

Inspection
1. The ICT is a non-web document.
1. Check that the document does not fail the Success Criterion in Table 10.1.
Pass: Check 1 is true
Fail: Check 1 is false

Inspection
1. The ICT is a non-web document.
1. Check that the document does not fail WCAG 2.1 Success Criterion 1.4.4 Resize
text.
Pass: Check 1 is true
Fail: Check 1 is false

Images of text

Type of assessment
Pre-conditions
Procedure
ResultInspection
1. The ICT is a non-web document.
1. Check that the document does not fail WCAG 2.1 Success Criterion 1.4.5 Images of
Text.
Pass: Check 1 is true
Fail: Check 1 is false

C.10.1.4.6

Void

C.10.1.4.7

Void

C.10.1.4.8

Void

C.10.1.4.9

Void

C.10.1.4.10

Reflow

Type of assessment
Pre-conditions
Procedure
ResultInspection
1. The ICT is a non-web document.
1. Check that the document does not fail the Success Criterion in Table 10.2.
Pass: Check 1 is true
Fail: Check 1 is false

ETSI

126
EN 301 549 V2.1.2 (2018-08)

C.10.1.4.11

Non-text contrast

Type of assessment
Pre-conditions
Procedure
ResultC.10.1.4.12

Text spacing

Type of assessment
Pre-conditions
Procedure
ResultC.10.1.4.13

ResultC.10.2.1
C.10.2.1.1

Inspection
1. The ICT is a non-web document.
1. Check that the document does not fail WCAG 2.1 Success Criterion 1.4.13 Content
on Hover or Focus.
Pass: Check 1 is true
Fail: Check 1 is false

Operable
Keyboard accessible
Keyboard

Type of assessment
Pre-conditions
Procedure
ResultC.10.2.1.2

Inspection
1. The ICT is a non-web document.
1. Check that the document does not fail WCAG 2.1 Success Criterion 1.4.12 Text
spacing.
Pass: Check 1 is true
Fail: Check 1 is false

Content on hover or focus

Type of assessment
Pre-conditions
Procedure

C.10.2

Inspection
1. The ICT is a non-web document that does not have a fixed size content layout areathat is essential to the information being conveyed.
1. Check that the document does not fail WCAG 2.1 Success Criterion 1.4.11 Non-text
Contrast.
Pass: Check 1 is true
Fail: Check 1 is false

Inspection
1. The ICT is a non-web document.
1. Check that the document does not fail WCAG 2.1 Success Criterion 2.1.1 Keyboard.
Pass: Check 1 is true
Fail: Check 1 is false

No keyboard trap

Type of assessment
Pre-conditions
Procedure
ResultInspection
1. The ICT is a non-web document.
1. Check that the document does not fail the Success Criterion in Table 10.3.
Pass: Check 1 is true
Fail: Check 1 is false

C.10.2.1.3

Void

C.10.2.1.4

Character key shortcuts

Type of assessment
Pre-conditions
Procedure
ResultInspection
1. The ICT is a non-web document.
1. Check that the document does not fail WCAG 2.1 Success Criterion 2.1.4 Character
Key Shortcuts.
Pass: Check 1 is true
Fail: Check 1 is false

ETSI

127
EN 301 549 V2.1.2 (2018-08)

C.10.2.2
C.10.2.2.1

Enough time
Timing adjustable

Type of assessment
Pre-conditions
Procedure
ResultC.10.2.2.2

Inspection
1. The ICT is a non-web document.
1. Check that the document does not fail the Success Criterion in Table 10.4.
Pass: Check 1 is true
Fail: Check 1 is false

Pause, stop, hide

Type of assessment
Pre-conditions
Procedure
ResultInspection
1. The ICT is a non-web document.
1. Check that the document does not fail the Success Criterion in Table 10.5.
Pass: Check 1 is true
Fail: Check 1 is false

C.10.2.3

Seizures and physical reactions

C.10.2.3.1

Three flashes or below threshold

Type of assessment
Pre-conditions
Procedure
ResultInspection
1. The ICT is a non-web document.
1. Check that the document does not fail the Success Criterion in Table 10.6.
Pass: Check 1 is true
Fail: Check 1 is false

C.10.2.4

Navigable

C.10.2.4.1

Void

C.10.2.4.2

Document titledType of assessment
Pre-conditions
Procedure
ResultC.10.2.4.3

Focus orderType of assessment
Pre-conditions
Procedure
ResultC.10.2.4.4

Inspection
1. The ICT is a non-web document.
1. Check that the document does not fail the Success Criterion in Table 10.8.
Pass: Check 1 is true
Fail: Check 1 is false

Link purpose (in context)

Type of assessment
Pre-conditions
Procedure
ResultInspection
1. The ICT is a non-web document.
1. Check that the document does not fail the Success Criterion in Table 10.7.
Pass: Check 1 is true
Fail: Check 1 is false

Inspection
1. The ICT is a non-web document.
1. Check that the document does not fail WCAG 2.1 Success Criterion 2.4.4 Link
Purpose (In Context).
Pass: Check 1 is true
Fail: Check 1 is false

ETSI

128
EN 301 549 V2.1.2 (2018-08)

C.10.2.4.5

Void

C.10.2.4.6

Headings and labels

Type of assessment
Pre-conditions
Procedure
ResultC.10.2.4.7

Focus visible

Type of assessment
Pre-conditions
Procedure
ResultC.10.2.5
C.10.2.5.1

Pointer gestures

ResultInspection
1. The ICT is a non-web document.
1. Check that the document does not fail WCAG 2.1 Success Criterion 2.5.3 Label in
Name.
Pass: Check 1 is true
Fail: Check 1 is false

Motion actuation

Type of assessment
Pre-conditions
Procedure
ResultInspection
1. The ICT is a non-web document.
1. Check that the document does not fail the success criterion in Table 10.10
Pass: Check 1 is true
Fail: Check 1 is false

Label in name

Type of assessment
Pre-conditions
Procedure

C.10.2.5.4

Inspection
1. The ICT is a non-web document.
1. Check that the document does not fail the Success Criterion in Table 10.9
Pass: Check 1 is true
Fail: Check 1 is false

Pointer cancellation

Type of assessment
Pre-conditions
Procedure
ResultC.10.2.5.3

Inspection
1. The ICT is a non-web document.
1. Check that the document does not fail WCAG 2.1 Success Criterion 2.4.7 Focus
Visible.
Pass: Check 1 is true
Fail: Check 1 is false

Input modalities

Type of assessment
Pre-conditions
Procedure
ResultC.10.2.5.2

Inspection
1. The ICT is a non-web document.
1. Check that the document does not fail WCAG 2.1 Success Criterion 2.4.6 Headings
and Labels.
Pass: Check 1 is true
Fail: Check 1 is false

Inspection
1. The ICT is a non-web document.
1. Check that the document does not fail WCAG 2.1 Success Criterion 2.5.4 Motion
Actuation.
Pass: Check 1 is true
Fail: Check 1 is false

ETSI

129
EN 301 549 V2.1.2 (2018-08)

C.10.3C.10.3.1
C.10.3.1.1

Understandable
Readable
Language of document

Type of assessment
Pre-conditions
Procedure
ResultC.10.3.1.2

Inspection
1. The ICT is a non-web document.
1. Check that the document does not fail the Success Criterion in Table 10.11.
Pass: Check 1 is true
Fail: Check 1 is false

Language of parts

Type of assessment
Pre-conditions
Procedure
ResultInspection
1. The ICT is a non-web document.
1. Check that the document does not fail the Success Criterion in Table 10.12.
Pass: Check 1 is true
Fail: Check 1 is false

C.10.3.2

Predictable

C.10.3.2.1

On focus

Type of assessment
Pre-conditions
Procedure
ResultC.10.3.2.2

On input

Type of assessment
Pre-conditions
Procedure
ResultC.10.3.2.3

Void

C.10.3.2.4

Void

C.10.3.3
C.10.3.3.1

Error identification

ResultInspection
1. The ICT is a non-web document.
1. Check that the document does not fail WCAG 2.1 Success Criterion 3.3.1 Error
Identification.
Pass: Check 1 is true
Fail: Check 1 is false

Labels or instructions

Type of assessment
Pre-conditions
Procedure
ResultInspection
1. The ICT is a non-web document.
1. Check that the document does not fail WCAG 2.1 Success Criterion 3.2.2 On Input.
Pass: Check 1 is true
Fail: Check 1 is false

Input assistanceType of assessment
Pre-conditions
Procedure

C.10.3.3.2

Inspection
1. The ICT is a non-web document.
1. Check that the document does not fail WCAG 2.1 Success Criterion 3.2.1 On Focus.
Pass: Check 1 is true
Fail: Check 1 is false

Inspection
1. The ICT is a non-web document.
1. Check that the document does not fail WCAG 2.1 Success Criterion 3.3.2 Labels or
Instructions.
Pass: Check 1 is true

ETSI

130
EN 301 549 V2.1.2 (2018-08)

Fail: Check 1 is false

C.10.3.3.3

Error suggestion

Type of assessment
Pre-conditions
Procedure
ResultC.10.3.3.4

Error prevention (legal, financial, data)

Type of assessment
Pre-conditions
Procedure
ResultC.10.4Inspection
1. The ICT is a non-web document.
1. Check that the document does not fail WCAG 2.1 Success Criterion 3.3.3 Error
Suggestion [4].
Pass: Check 1 is true
Fail: Check 1 is false

Inspection
1. The ICT is a non-web document.
1. Check that the document does not fail the Success Criterion in Table 10.13.
Pass: Check 1 is true
Fail: Check 1 is false

RobustC.10.4.1

Compatible

C.10.4.1.1

ParsingType of assessment
Pre-conditions
Procedure
ResultC.10.4.1.2

Name, role, value

Type of assessment
Pre-conditions
Procedure
ResultC.10.4.1.3

C.10.5Inspection
1. The ICT is a non-web document.
1. Check that the document does not fail the Success Criterion in Table 10.14.
Pass: Check 1 is true
Fail: Check 1 is false

Inspection
1. The ICT is a non-web document.
1. Check that the document does not fail the Success Criterion in Table 10.15.
Pass: Check 1 is true
Fail: Check 1 is false

Void

Caption positioning

Clause 10.5 contains no requirements requiring test.

C.10.6

Audio description timing

Clause 10.6 contains no requirements requiring test.

C.11

SoftwareC.11.0GeneralClause 11.0 is advisory only and contains no requirements requiring test.

ETSI

131
EN 301 549 V2.1.2 (2018-08)

C.11.1

Perceivable

C.11.1.1

Text alternatives

C.11.1.1.1

Non-text content

C.11.1.1.1.1

Non-text content (screen reading supported open functionality)

Type of assessment
Pre-conditions
Procedure
ResultC.11.1.1.1.2

Non-text content (closed functionality)

Type of assessment
Pre-conditions

Procedure

ResultC.11.1.2
C.11.1.2.1

Audio-only and video-only (pre-recorded)Type of assessment
Pre-conditions

ResultTesting
1. The ICT is non-web software that provides a user interface.
2. The user interface is closed to assistive technologies for screen reading.
3. Non-text content is presented to users via speech output.
1. Check that speech output is provided as an alternative for non-text content.
2. Check that the non-text content is not pure decoration.
3. Check that the non-text content is not used only for visual formatting.
4. Check that the speech output follows the guidance for "text alternative" described in
WCAG 2.1 Success Criterion 1.1.1 Non-text Content.
Pass: Check (1 and 2 and 3 and 4 are true) or (1 and 2 are false) or (1 and 3 are false)
Fail: Checks (1 true and 2 false) or (1 true and 3 false) or (1 and 2 and 3 are true and 4
is false)

Time-based media

C.11.1.2.1.1

Procedure

Inspection
1. The ICT is non-web software that provides a user interface.
2. The software provides support to assistive technologies for screen reading.
1. Check that the software does not fail WCAG 2.1 Success Criterion 1.1.1 Non-textContent.
Pass: Check 1 is true
Fail: Check 1 is false

Audio-only and video-only (pre-recorded - open functionality)
Inspection
1. The ICT is non-web software that provides a user interface.
2. The software provides support to assistive technologies for screen reading.
3. Pre-recorded auditory information is not needed to enable the use of closed
functions of ICT.
1. Check that the software does not fail WCAG 2.1 Success Criterion 1.2.1 Audio-only
and Video-only (Prerecorded).
Pass: Check 1 is true
Fail: Check 1 is false

ETSI

132
EN 301 549 V2.1.2 (2018-08)

C.11.1.2.1.2

Audio-only and video-only (pre-recorded - closed functionality)

C.11.1.2.1.2.1

Pre-recorded audio-only (closed functionality)

Type of assessment
Pre-conditions

Procedure
ResultC.11.1.2.1.2.2

Pre-recorded video-only (closed functionality)

Type of assessment
Pre-conditions

Procedure
ResultC.11.1.2.2

ResultType of assessment
Pre-conditions
Procedure
ResultC.11.1.2.3.2
Type of assessment
Pre-conditions

ResultInspection
1. The ICT is non-web software that provides a user interface.
1. Check that the software does not fail WCAG 2.1 Success Criterion 1.2.2 Captions(Prerecorded).
Pass: Check 1 is true
Fail: Check 1 is false

Audio description or media alternative (pre-recorded)

C.11.1.2.3.1

Procedure

Inspection
1. ICT is non-web software that provides a user interface.
2. The user interface is closed to assistive technologies for screen reading.
3. Pre-recorded video content is needed to enable the use of closed functions of ICT.
4. Speech output is provided as non-visual access to non-text content displayed on
closed functionality.
1. Check that the speech output presents equivalent information for the pre-recorded
video content.
Pass: Check 1 is true
Fail: Check 1 is false

Captions (pre-recorded)Type of assessment
Pre-conditions
Procedure

C.11.1.2.3

Inspection
1. ICT is non-web software that provides a user interface.
2. The user interface is closed to assistive technologies for screen reading.
3. Pre-recorded auditory information is needed to enable the use of closed functions of
ICT.
1. Check that the visual information is equivalent to the pre-recorded auditory output.
Pass: Check 1 is true
Fail: Check 1 is false

Audio description or media alternative (pre-recorded - open functionality)
Inspection
1. The ICT is non-web software that provides a user interface.
2. The software provides support to assistive technologies for screen reading.
1. Check that the software does not fail WCAG 2.1 Success Criterion 1.2.3 Audio
Description or Media Alternative (Prerecorded).
Pass: Check 1 is true
Fail: Check 1 is false

Audio description or media alternative (pre-recorded - closed functionality)
Inspection
1. ICT is non-web software that provides a user interface.
2. The user interface is closed to assistive technologies for screen reading.
3. Speech output is provided as non-visual access to non-text content displayed on
closed functionality.
1. Check that the speech output presents equivalent information for the pre-recorded
video content.
Pass: Check 1 is true
Fail: Check 1 is false

ETSI

133
EN 301 549 V2.1.2 (2018-08)

C.11.1.2.4

Captions (live)

Type of assessment
Pre-conditions
Procedure
ResultC.11.1.2.5

Audio description (pre-recorded)Type of assessment
Pre-conditions
Procedure
ResultC.11.1.3
C.11.1.3.1

Inspection
1. The ICT is non-web software that provides a user interface.
1. Check that the software does not fail WCAG 2.1 Success Criterion 1.2.4 Captions(Live).
Pass: Check 1 is true
Fail: Check 1 is false

Inspection
1. The ICT is non-web software that provides a user interface.
1. Check that the software does not fail WCAG 2.1 Success Criterion 1.2.5 Audio
Description (Prerecorded).
Pass: Check 1 is true
Fail: Check 1 is false

Adaptable
Info and relationships

C.11.1.3.1.1

Info and relationships (open functionality)

Type of assessment
Pre-conditions
Procedure
ResultC.11.1.3.1.2

Inspection
1. The ICT is non-web software that provides a user interface.
2. The software provides support to assistive technologies for screen reading.
1. Check that the software does not fail WCAG 2.1 Success Criterion 1.3.1 Info andRelationships.
Pass: Check 1 is true
Fail: Check 1 is false

Info and relationships (closed functionality)

This clause is informative only and contains no requirements requiring test.

C.11.1.3.2

Meaningful sequence

C.11.1.3.2.1

Meaningful sequence (open functionality)

Type of assessment
Pre-conditions
Procedure
ResultC.11.1.3.2.2

Inspection
1. The ICT is non-web software that provides a user interface.
2. The software provides support to assistive technologies for screen reading.
1. Check that the software does not fail WCAG 2.1 Success Criterion 1.3.2 Meaningful
Sequence.
Pass: Check 1 is true
Fail: Check 1 is false

Meaningful sequence (closed functionality)

This clause is informative only and contains no requirements requiring test.

C.11.1.3.3

Sensory characteristics

Type of assessment
Pre-conditions
Procedure
ResultInspection
1. The ICT is non-web software that provides a user interface.
1. Check that the software does not fail WCAG 2.1 Success Criterion 1.3.3 Sensory
Characteristics.
Pass: Check 1 is true
Fail: Check 1 is false

ETSI

134
EN 301 549 V2.1.2 (2018-08)

C.11.1.3.4

Orientation

Type of assessment
Pre-conditions
Procedure
ResultC.11.1.3.5

Inspection
1. The ICT is non-web software that provides a user interface.
2. The software provides support to at least one assistive technology.
1. Check that the software does not fail WCAG 2.1 Success Criterion 1.3.4 Orientation.
Pass: Check 1 is true
Fail: Check 1 is false

Identify input purpose

Type of assessment
Pre-conditions
Procedure
ResultInspection
1. The ICT is non-web software that provides a user interface.
2. The software provides support to at least one assistive technology.
1. Check that the software does not fail WCAG 2.1 Success Criterion 1.3.5 Identify
Input Purpose.
Pass: Check 1 is true
Fail: Check 1 is false

C.11.1.4

Distinguishable

C.11.1.4.1

Use of colour

Type of assessment
Pre-conditions
Procedure
ResultC.11.1.4.2

Audio control

Type of assessment
Pre-conditions
Procedure
ResultC.11.1.4.3

ResultInspection
1. The ICT is non-web software that provides a user interface.
1. Check that the software does not fail WCAG 2.1 Success Criterion 1.4.3 Contrast(Minimum).
Pass: Check 1 is true
Fail: Check 1 is false

Resize text

C.11.1.4.4.1
Type of assessment
Pre-conditions

Procedure
ResultInspection
1. The ICT is non-web software that provides a user interface.
1. Check that the software does not fail the Success Criterion in Table 11.1.
Pass: Check 1 is true
Fail: Check 1 is false

Contrast (minimum)

Type of assessment
Pre-conditions
Procedure

C.11.1.4.4

Inspection
1. The ICT is non-web software that provides a user interface.
1. Check that the software does not fail WCAG 2.1 Success Criterion 1.4.1 Use ofColor.
Pass: Check 1 is true
Fail: Check 1 is false

Resize text (open functionality)
Inspection
1. The ICT is non-web software that provides a user interface.
2. The software provides support to enlargement features of platform or assistive
technology.
1. Check that the software does not fail WCAG 2.1 Success Criterion 1.4.4 Resize text.
Pass: Check 1 is true
Fail: Check 1 is false

ETSI

135
EN 301 549 V2.1.2 (2018-08)

C.11.1.4.4.2

Resize text (closed functionality)

Type of assessment
Pre-conditions

Inspection and measurement
1. ICT is non-web software that provides a user interface.
2. The user interface is closed to enlargement features of platform or assistive
technology.
3. A viewing distance is specified by the supplier.
1. Measure the height of a capital letter H.
2. Check that it subtends an angle of at least 0,7 degrees at the specified viewing
distance.
Pass: Check 2 is true
Fail: Check 2 is false

Procedure

ResultC.11.1.4.5

Images of text

C.11.1.4.5.1

Images of text (open functionality)

Type of assessment
Pre-conditions

Inspection
1. The ICT is non-web software that provides a user interface.
2. The software provides support to assistive technologies for screen reading.
1. Check that the software does not fail WCAG 2.1 Success Criterion 1.4.5 Images of
Text.
Pass: Check 1 is true
Fail: Check 1 is false

Procedure
ResultC.11.1.4.5.2

Images of text (closed functionality)

This clause is informative only and contains no requirements requiring test.

C.11.1.4.6

Void

C.11.1.4.7

Void

C.11.1.4.8

Void

C.11.1.4.9

Void

C.11.1.4.10

Reflow

C.11.1.4.10.1
Type of assessment
Pre-conditions
Procedure
ResultC.11.1.4.10.2
Type of assessment
Pre-conditions

Procedure

ResultReflow (open functionality)
Inspection
1. The ICT is non-web software that provides a user interface.
2. The software provides support to at least one assistive technology.
1. Check that the software does not fail the Success Criterion in Table 11.2
Pass: Check 1 is true
Fail: Check 1 is false

Reflow (closed functionality)
Inspection and measurement
1. The ICT is non-web software that provides a user interface.
2. A functionality of the ICT is closed to enlargement features of platform or assistive
technology.
3. A viewing distance is specified by the supplier.
1. Measure the height of a capital letter H.
2. Check that it subtends an angle of at least 0,7 degrees at the specified viewing
distance.
Pass: Check 2 is true
Fail: Check 2 is false

ETSI

136
EN 301 549 V2.1.2 (2018-08)

C.11.1.4.11

Non-text contrast

Type of assessment
Pre-conditions
Procedure
ResultC.11.1.4.12

Text spacing

Type of assessment
Pre-conditions
Procedure
ResultC.11.1.4.13

Procedure
ResultInspection
1. The ICT is non-web software that provides a user interface.
2. The software provides support to at least one assistive technology.
1. Check that the software does not fail WCAG 2.1 Success Criterion 1.4.13 Content
on hover or focus.
Pass: Check 1 is true
Fail: Check 1 is false

Operable

C.11.2.1
C.11.2.1.1

Keyboard accessible
Keyboard

C.11.2.1.1.1

Keyboard (open functionality)

Type of assessment
Pre-conditions
Procedure
ResultC.11.2.1.1.2

Inspection
1. The ICT is non-web software that provides a user interface.
2. The software provides support to keyboards or a keyboard interface.
1. Check that the software does not fail WCAG 2.1 Success Criterion 2.1.1 Keyboard.
Pass: Check 1 is true
Fail: Check 1 is false

Keyboard (closed functionality)

Type of assessment
Pre-conditions
Procedure
ResultC.11.2.1.2

Inspection
1. The ICT is non-web software that provides a user interface.
2. The software provides support to at least one assistive technology.
1. Check that the software does not fail the Success Criterion WCAG 2.1 Success
Criterion 1.4.12 Text spacing.
Pass: Check 1 is true
Fail: Check 1 is false

Content on hover or focus

Type of assessment
Pre-conditions

C.11.2

Inspection
1. The ICT is non-web software that provides a user interface.
2. The software provides support to at least one assistive technology.
1. Check that the software does not fail the Success Criterion WCAG 2.1 Success
Criterion 1.4.11 Non-text Contrast.
Pass: Check 1 is true
Fail: Check 1 is false

Inspection
1. ICT is non-web software that provides a user interface.
2. The user interface is closed to keyboards or keyboard interfaces.
1. Check that all functionality of the user interface is operable without vision.
Pass: Check 1 is true
Fail: Check 1 is false

No keyboard trap

Type of assessment
Pre-conditions
Procedure
ResultInspection
1. The ICT is non-web software that provides a user interface.
1. Check that the software does not fail the Success Criterion in Table 11.3.
Pass: Check 1 is true
Fail: Check 1 is false

ETSI

137
EN 301 549 V2.1.2 (2018-08)

C.11.2.1.3

Void

C.11.2.1.4

Character key shortcuts

C.11.2.1.4.1

Character key shortcuts (open functionality)

Type of assessment
Pre-conditions

Inspection
1. The ICT is non-web software that provides a user interface.
2. The software provides support to at least one assistive technology.
1. Check that the software does not fail WCAG 2.1 Success Criterion 2.1.4 Character
Key Shortcuts.
Pass: Check 1 is true
Fail: Check 1 is false

Procedure
ResultC.11.2.1.4.2

Character key shortcuts (closed functionality)

Type of assessment
Pre-conditions
Procedure
ResultC.11.2.2
C.11.2.2.1

Enough time
Timing adjustable

Type of assessment
Pre-conditions
Procedure
ResultC.11.2.2.2

Inspection
1. ICT functionality is closed to keyboards or keyboard interfaces.
1. Check that all functionality is operable without vision.
Pass: Check 1 is true
Fail: Check 1 is false

Inspection
1. The ICT is non-web software that provides a user interface.
1. Check that the software does not fail the Success Criterion in Table 11.4.
Pass: Check 1 is true
Fail: Check 1 is false

Pause, stop, hide

Type of assessment
Pre-conditions
Procedure
ResultInspection
1. The ICT is non-web software that provides a user interface.
1. Check that the software does not fail the Success Criterion in Table 11.5.
Pass: Check 1 is true
Fail: Check 1 is false

C.11.2.3

Seizures and physical reactions

C.11.2.3.1

Three flashes or below threshold

Type of assessment
Pre-conditions
Procedure
ResultInspection
1. The ICT is non-web software that provides a user interface.
1. Check that the software does not fail the Success Criterion in Table 11.6.
Pass: Check 1 is true
Fail: Check 1 is false

C.11.2.4

Navigable

C.11.2.4.1

Void

C.11.2.4.2

Void

C.11.2.4.3

Focus orderType of assessment
Pre-conditions
Procedure
ResultInspection
1. The ICT is non-web software that provides a user interface.
1. Check that the software does not fail the Success Criterion in Table 11.7.
Pass: Check 1 is true

ETSI

138
EN 301 549 V2.1.2 (2018-08)

Fail: Check 1 is false

C.11.2.4.4

Link purpose (in context)

Type of assessment
Pre-conditions
Procedure
ResultInspection
1. The ICT is non-web software that provides a user interface.
1. Check that the software does not fail WCAG 2.1 Success Criterion 2.4.4 Link
Purpose (In Context).
Pass: Check 1 is true
Fail: Check 1 is false

C.11.2.4.5

Void

C.11.2.4.6

Headings and labels

Type of assessment
Pre-conditions
Procedure
ResultC.11.2.4.7

Focus visible

Type of assessment
Pre-conditions
Procedure
ResultC.11.2.5
C.11.2.5.1

Pointer gestures

Procedure
ResultProcedure
ResultResultInspection
1. The ICT is non-web software that provides a user interface.
2. The software provides support to at least one assistive technology.
1. Check that the software does not fail the Success Criterion in Table 11.9.
Pass: Check 1 is true
Fail: Check 1 is false

Label in name

Type of assessment
Pre-conditions
Procedure

Inspection
1. The ICT is non-web software that provides a user interface.
2. The software provides support to at least one assistive technology.
1. Check that the software does not fail the Success Criterion in Table 11.8.
Pass: Check 1 is true
Fail: Check 1 is false

Pointer cancellation

Type of assessment
Pre-conditions

C.11.2.5.3

Inspection
1. The ICT is non-web software that provides a user interface.
1. Check that the software does not fail WCAG 2.1 Success Criterion 2.4.7 Focus
Visible.
Pass: Check 1 is true
Fail: Check 1 is false

Input modalities

Type of assessment
Pre-conditions

C.11.2.5.2

Inspection
1. The ICT is non-web software that provides a user interface.
1. Check that the software does not fail WCAG 2.1 Success Criterion 2.4.6 Headings
and Labels.
Pass: Check 1 is true
Fail: Check 1 is false

Inspection
1. The ICT is non-web software that provides a user interface.
2. The software provides support to at least one assistive technology.
1. Check that the software does not fail WCAG 2.1 Success Criterion 2.5.3 Label in
Name.
Pass: Check 1 is true
Fail: Check 1 is false

ETSI

139
EN 301 549 V2.1.2 (2018-08)

C.11.2.5.4

Motion actuation

Type of assessment
Pre-conditions

Inspection
1. The ICT is non-web software that provides a user interface.
2. The software provides support to at least one assistive technology.
1. Check that the software does not fail WCAG 2.1 Success Criterion 2.5.4 Motion
Actuation.
Pass: Check 1 is true
Fail: Check 1 is false

Procedure
ResultC.11.3

Understandable

C.11.3.1
C.11.3.1.1

Readable
Language of software

C.11.3.1.1.1

Language of software (open functionality)

Type of assessment
Pre-conditions

Inspection
1. The ICT is non-web software that provides a user interface.
2. The software provides support to assistive technologies for screen reading.
1. Check that the software does not fail the Success Criterion in Table 11.10.
Pass: Check 1 is true
Fail: Check 1 is false

Procedure
ResultC.11.3.1.1.2

Language of software (closed functionality)

Type of assessment
Pre-conditions

Procedure
ResultTesting
1. ICT is non-web software that provides a user interface.
2. The user interface is closed to assistive technologies for screen reading.
3. The speech output is provided as non-visual access to closed functionality.
4. The speech output is not proper names, technical terms, words of indeterminate.
language, and words or phrases that have become part of the vernacular of theimmediately surrounding text.
5. The content is not generated externally and is under the control of the ICT vendor.
6. The displayed languages can be selected using non-visual access.
7. The user has not selected a speech language that is different from the language ofthe displayed content.
1. Check that the speech output is in the same human language of the displayedcontent provided.
Pass: Check 1 is true
Fail: Check 1 is false

C.11.3.1.2

Void

C.11.3.2

Predictable

C.11.3.2.1

On focus

Type of assessment
Pre-conditions
Procedure
ResultC.11.3.2.2

Inspection
1. The ICT is non-web software that provides a user interface.
1. Check that the software does not fail WCAG 2.1 Success Criterion 3.2.1 On Focus.
Pass: Check 1 is true
Fail: Check 1 is false

On input

Type of assessment
Pre-conditions
Procedure
ResultInspection
1. The ICT is non-web software that provides a user interface.
1. Check that the software does not fail WCAG 2.1 Success Criterion 3.2.2 On Input.
Pass: Check 1 is true
Fail: Check 1 is false

ETSI

140
EN 301 549 V2.1.2 (2018-08)

C.11.3.2.3

Void

C.11.3.2.4

Void

C.11.3.3
C.11.3.3.1

Input assistance
Error identification

C.11.3.3.1.1

Error identification (open functionality)

Type of assessment
Pre-conditions
Procedure
ResultC.11.3.3.1.2

Error Identification (closed functionality)

Type of assessment
Pre-conditions

Procedure
ResultC.11.3.3.2

ResultInspection
1. The ICT is non-web software that provides a user interface.
1. Check that the software does not fail WCAG 2.1 Success Criterion 3.3.2 Labels or
Instructions.
Pass: Check 1 is true
Fail: Check 1 is false

Error suggestion

Type of assessment
Pre-conditions
Procedure
ResultC.11.3.3.4

Testing
1. ICT is non-web software that provides a user interface.
2. The user interface is closed to assistive technologies for screen reading.
3. Speech output is provided as non-visual access to closed functionality.
4. An input error is automatically detected.
1. Check that speech output identifies the item that is in error.
2. Check that the speech output describes the item that is in error.
Pass: Checks 1 and 2 are true
Fail: Check 1 or check 2 false

Labels or instructions

Type of assessment
Pre-conditions
Procedure

C.11.3.3.3

Inspection
1. The ICT is non-web software that provides a user interface.
2. The software provides support to assistive technologies for screen reading.
1. Check that the software does not fail WCAG 2.1 Success Criterion 3.3.1 Error
Identification.
Pass: Check 1 is true
Fail: Check 1 is false

Inspection
1. The ICT is non-web software that provides a user interface.
1. Check that the software does not fail WCAG 2.1 Success Criterion WCAG 2.1
Success Criterion 3.3.3 Error Suggestion.
Pass: Check 1 is true
Fail: Check 1 is false

Error prevention (legal, financial, data)

Type of assessment
Pre-conditions
Procedure
ResultInspection
1. The ICT is non-web software that provides a user interface.
1. Check that the software does not fail the Success Criterion in Table 11.11.
Pass: Check 1 is true
Fail: Check 1 is false

ETSI

141
EN 301 549 V2.1.2 (2018-08)

C.11.4

RobustC.11.4.1

Compatible

C.11.4.1.1

Parsing

C.11.4.1.1.1

Parsing (open functionality)

Type of assessment
Pre-conditions

Inspection
1. The ICT is non-web software that provides a user interface.
2. The software provides support to at least one assistive technology.
1. Check that the software does not fail the Success Criterion in Table 11.12.
Pass: Check 1 is true
Fail: Check 1 is false

Procedure
ResultC.11.4.1.1.2

Parsing (closed functionality)

Clause 11.4.1.1.2 contains no requirements requiring test.

C.11.4.1.2

Name, role, value

C.11.4.1.2.1

Name, role, value (open functionality)

Type of assessment
Pre-conditions

Inspection
1. The ICT is non-web software that provides a user interface.
2. The software provides support to at least one assistive technology.
1. Check that the software does not fail the Success Criterion in Table 11.13.
Pass: Check 1 is true
Fail: Check 1 is false

Procedure
ResultC.11.4.1.2.2

Name, role, value (closed functionality)

Clause 11.4.1.2.2 contains no requirements requiring test.

C.11.4.1.3

C.11.5C.11.5.1

VoidInteroperability with assistive technology
Closed functionality

Type of assessment
Pre-conditions
Procedure
ResultC.11.5.2
C.11.5.2.1

Inspection
1. The software has closed functionality.
1. Check that the closed functionality conforms to clause 5.1.
If check 1 is true, the software is not required to conform to clauses 11.5.2 to 11.5.17
If check 1 is false the software is required to conform to clauses 11.5.2 to 11.5.17

Accessibility services
Platform accessibility service support for software that provides a userinterface

Type of assessment
Pre-conditions
Procedure

ResultInspection
1. The software evaluated is platform software.
1. Check that the platform software documentation includes information about platform
services that may be used by software that provides a user interface to interoperatewith assistive technology.
Pass: Check 1 is true
Fail: Check 1 is false

ETSI

142
EN 301 549 V2.1.2 (2018-08)

C.11.5.2.2

Platform accessibility service support for assistive technologies

Type of assessment
Pre-conditions
Procedure

ResultC.11.5.2.3

Use of accessibility services

Type of assessment
Pre-conditions
Procedure

ResultC.11.5.2.4

ResultResultResultInspection
1. The software evaluated is software that provides a user interface.
1. Check that the user interface element's role is programmatically determinable byassistive technologies.
2. Check that the user interface element's state(s) is programmatically determinable byassistive technologies.
3. Check that the user interface element's boundary is programmatically determinable
by assistive technologies.
4. Check that the user interface element's name is programmatically determinable byassistive technologies.
5. Check that the user interface element's description is programmatically determinable
by assistive technologies.
Pass: Checks 1, 2, 3, 4 and 5 are true
Fail: Check 1 or 2 or 3 or 4 or 5 is false

Row, column, and headersType of assessment
Pre-conditions
Procedure

Inspection
1. The ICT is assistive technology.
1. Check that the assistive technology uses the documented platform accessibility
services.
Pass: Check 1 is true
Fail: Check 1 is false

Object information

Type of assessment
Pre-conditions
Procedure

C.11.5.2.6

Inspection
1. The software evaluated is software that provides a user interface.
1. Check that the software uses the applicable documented platform accessibility
services.
2. Check that the software can meet the applicable requirements 11.5.2.5 to 11.5.2.17
whilst using the documented platform accessibility services.
3. Check that the software can meet requirements 11.5.2.5 to 11.5.2.17 whilst using
the documented platform accessibility services and other documented services.
Pass: Check 1 is true and check 2 or check 3 is true
Fail: Check 1 or check 3 is false

Assistive technology

Type of assessment
Pre-conditions
Procedure

C.11.5.2.5

Inspection
1. The software evaluated is platform software.
1. Check that the platform software documentation includes information about platform
accessibility services that enables assistive technology to interoperate with softwarethat provides a user interface running on the platform software.
Pass: Check 1 is true
Fail: Check 1 is false

Inspection
1. The software evaluated is software that provides a user interface.
2. There are data tables in the user interface.
1. Select a data table in which the tests are to be performed.
2. Check that each cell's row is programmatically determinable by assistive
technologies.
3. Check that each cell's column is programmatically determinable by assistive
technologies.
4. Check that each cell's row header, if the row header exists, is programmaticallydeterminable by assistive technologies.
5. Check that each cell's column header, if the column header exists, isprogrammatically determinable by assistive technologies.
Pass: Checks 2, 3, 4 and 5 are true
Fail: Check 2 or 3 or 4 or 5 is false

ETSI

143
EN 301 549 V2.1.2 (2018-08)

C.11.5.2.7

ValuesType of assessment
Pre-conditions
Procedure

ResultC.11.5.2.8

Label relationships

Type of assessment
Pre-conditions
Procedure

ResultC.11.5.2.9

Inspection
1. The software evaluated is software that provides a user interface.
2. There are user interface elements that can have values.
1. Select a user interface element that can have a value.
2. Check that the current value is programmatically determinable by assistive
technologies.
3. If the user interface element conveys information about a range of values, check thatthe minimum value is programmatically determinable by assistive technologies.
4. If the user interface element conveys information about a range of values, check thatthe maximum value is programmatically determinable by assistive technologies.
Pass: Checks 2, 3 and 4 are true
Fail: Check 2 or 3 or 4 is false

Inspection
1. The software evaluated is software that provides a user interface.
2. There are user interface elements that are labels of other user interface elements.
1. Obtain the information of each user interface element.
2. Check that the user interface element's information includes the relationship with theuser interface element that is its label, if the current user interface element has a label,
and that this relationship is programmatically determinable by assistive technologies.
3. Check that the user interface element's information includes the relationship with theuser interface element that it is labelling, if the current user interface element is a label,
and that this relationship is programmatically determinable by assistive technologies.
Pass: Checks 2 or 3 are true
Fail: Check 2 and 3 are false

Parent-child relationships

Type of assessment
Pre-conditions

Inspection
1. The software evaluated is software that provides a user interface.
2. There are user interface elements that are parents of other user interface elements
in a hierarchical structure.
Procedure
1. For user interface elements that have a parent, check that the user interface
element's information includes the relationship with the user interface element that is its
parent.
2. Check that the user interface elements that are parents of the user interface element
selected in check 1, include the relationship with the user interface elements that are
its children in their information, and that this relationship is programmaticallydeterminable by assistive technologies.
3. For user interface elements that are a parent of other user interface elements, checkthat the user interface element's information includes the relationship with the userinterface elements that are its children, and that this relationship is programmaticallydeterminable by assistive technologies.
4. Check that the user interface elements that are a child of the user interface element
selected in check 3, include the relationship with the user interface elements that are
its parents in their information, and that this relationship is programmaticallydeterminable by assistive technologies.
ResultPass: Checks 1 or 2 is true and check 3 or 4 is true
Fail: Checks 1 and 2 are false or check 3 and 4 are false
NOTE:
For this requirement it is enough that one of the two directions of a parent-child relationship is
programmatically determinable. This is the reason why the requirement checks are in pairs and why
the requirement is met if one member of each pair is true.

ETSI

144
EN 301 549 V2.1.2 (2018-08)

C.11.5.2.10

Text

Type of assessment
Pre-conditions
Procedure

ResultC.11.5.2.11

List of available actions

Type of assessment
Pre-conditions

Procedure

ResultC.11.5.2.12

Procedure

ResultResultInspection and testing
1. The software evaluated is software that provides a user interface.
2. There are user interface elements that have actions that can be executed by theuser.
3. The security requirements permit assistive technology to programmatically executeuser actions.
1. Check that the user interface element's information includes the list of actions thatcan be executed by assistive technologies according to 11.5.2.11.
2. Check that all the actions in the list can successfully be executed by assistive
technologies.
Pass: Checks 1 and 2 are true
Fail: Check 1 or 2 is false

Tracking of focus and selection attributes

Type of assessment
Pre-conditions
Procedure

Inspection
1. The software evaluated is software that provides a user interface.
2. There are user interface elements that have actions that can be executed by theuser.
1. Check that the user interface element's information includes the list of actions thatcan be executed.
2. Check that this list is programmatically determinable by assistive technologies.
Pass: Checks 1 and 2 are true
Fail: Check 1 or 2 is false

Execution of available actions

Type of assessment
Pre-conditions

C.11.5.2.13

Inspection
1. The software evaluated is software that provides a user interface.
2. There is text rendered to the screen.
1. For instances of text rendered to the screen, check that the text's information
includes its text content, and that this information is programmatically determinable byassistive technologies.
2. For instances of text rendered to the screen, check that the text's information
includes its attributes, and that this information is programmatically determinable byassistive technologies.
3. For instances of text rendered to the screen, check that the text's information
includes its boundary, and that this information is programmatically determinable byassistive technologies.
Pass: Checks 1, 2 and 3 are true
Fail: Check 1 or 2 or 3 is false

Inspection and testing
1. The software evaluated is software that provides a user interface.
2. There are user interface elements that enable text editing.
1. Check that the user interface element's information includes mechanisms to track
focus, text insertion point and selection attributes.
2. Check that this information is programmatically determinable by assistive
technologies.
3. Activate those tracking mechanisms.
4. As a user, use the text editing functionality in the evaluated software product.
5. Check that the tracking of focus, text insertion point and selection attributes work.
Pass: Checks 2 and 5 are true
Fail: Check 1 or 5 is false

ETSI

145
EN 301 549 V2.1.2 (2018-08)

C.11.5.2.14

Modification of focus and selection attributes

Type of assessment
Pre-conditions

Procedure

ResultC.11.5.2.15

Change notification

Type of assessment
Pre-conditions
Procedure

ResultC.11.5.2.16

ResultInspection and testing
1. The software evaluated is software that provides a user interface.
1. Activate notifications of changes in the user interface elements.
2. Check that notifications about changes in object information (role, state, boundary,name and description) are sent to assistive technologies, if this information changes inthe software user interface.
3. Check that notifications about changes in row, column and headers of data tables
are sent to assistive technologies, if this information changes in the software.
4. Check that notifications about changes in values (current value, minimum value andmaximum value) are sent, if this information changes in the software.
5. Check that notifications about changes in label relationships are sent o assistive
technologies, if this information changes in the software.
6. Check that notifications about changes in parent-child relationships are sent toassistive technologies, if this information changes in the software.
7. Check notifications about changes in text (text contents, text attributes and theboundary of text rendered to the screen) are sent to assistive technologies, if thisinformation changes in the software.
8. Check that notifications about changes in the list of available actions are sent toassistive technologies, if this information changes in the software.
9. Check that notifications about changes in focus, text insertion point and selection
attributes are sent to assistive technologies, if this information changes in the software.
Pass: Checks 2, 3, 4, 5, 6, 7, 8 and 9 are true
Fail: Check 2, 3, 4, 5, 6, 7, 8 or 9 is false

Modifications of states and properties

Type of assessment
Pre-conditions

Procedure

Testing
1. The software evaluated is software that provides a user interface.
2. There are user interface elements that can receive focus or that enable text editing.
3. The security requirements permit platform software to programmatically modify
focus, text insertion point and selection attributes of user interface elements.
1. For user interface elements that can receive focus and where the focus can be
modified by a user without the use of assistive technology, check that the focus can be
programmatically modified by assistive technologies.
2. For user interface elements that enable text editing by a user without the use of
assistive technology, check that the position of the text insertion point can be
programmatically modified by assistive technologies.
3. For user interface elements that enable text editing, check that the selection
attributes can be programmatically modified by assistive technologies where they canbe modified by user without the use of assistive technology.
Pass: All checks are true
Fail: Any check is false

Testing
1. The software evaluated is software that provides a user interface.
2. There are user interface elements whose state or properties can be modified by auser without the use of assistive technology.
3. The security requirements permit assistive technology to programmatically modify
states and properties of user interface elements.
1. Check that the state of user interface elements, whose state can be modified by auser without the use of assistive technology, can be programmatically modified byassistive technologies.
2. Check the properties of user interface elements, whose properties can be modified
by a user without the use of assistive technologies, can be programmatically modified
by assistive technologies.
Pass: All checks are true
Fail: Any check is false

ETSI

146
EN 301 549 V2.1.2 (2018-08)

C.11.5.2.17

Modifications of values and text

Type of assessment
Pre-conditions

Procedure

ResultTesting
1. The software evaluated is software that provides a user interface.
2. There are user interface elements whose values or text can be modified by a user
without the use of assistive technology.
3. The security requirements permit assistive technology to programmatically modify
values and text of user interface elements.
1. Check that the values of user interface elements, whose values can be modified bya user without the use of assistive technology, can be modified by assistive
technologies using the input methods of the platform.
2. Check that the text of user interface elements, whose text can be modified by a user
without the use of assistive technology, can be modified by assistive technologies
using the input methods of the platform.
Pass: all checks are true
Fail: any check is false

C.11.6

Documented accessibility usage

C.11.6.1

User control of accessibility features

Type of assessment
Pre-conditions
Procedure

ResultC.11.6.2

No disruption of accessibility features

Type of assessment
Pre-conditions
Procedure

ResultC.11.7

Testing
1. There are platform features that are defined in the platform documentation as
accessibility features.
1. Check if software that provides a user interface disrupts normal operation of platform
accessibility features.
2. Check if the disruption was specifically requested or confirmed by the user.
Pass: Check 1 is false or both checks are true
Fail: Check 1 is true and check 2 is false

User preferences

Type of assessment
Pre-conditions
Procedure

ResultTesting
1. There are platform features that are defined in the platform documentation as
accessibility features intended for users.
1. Check that sufficient modes of operation exists where user control over platform
features, that are defined in the platform documentation as accessibility featuresintended for users, is possible.
Pass: Check 1 is true
Fail: Check 1 is false

Inspection and Testing
1. The software is software that provides a user interface.
1. Check if the software provides sufficient modes of operation that uses user
preferences for platform settings for colour, contrast, font type, font size, and focus
cursor.
2. Check that the software documentation indicates that the software is designed to beisolated from its underlying platform.
Pass: Check 1 is true or Check 1 is false and check 2 is true
Fail: Check 1 is false and check 2 is false

ETSI

147
EN 301 549 V2.1.2 (2018-08)

C.11.8

Authoring tools

C.11.8.1

Content technology

Type of assessment
Pre-conditions

Inspection and Testing
1. The software is an authoring tool.
2. The output format of the authoring tool supports information required foraccessibility.
Procedure
1. Check if the authoring tool conforms to 11.8.2 to 11.8.5 to the extent that information
required for accessibility is supported by the format used for the output of the authoringtool.
ResultPass: Check 1 is true
Fail: Check 1 is false
NOTE:
Where the output format of the authoring tool does not support certain types of information required
for accessibility, compliance with requirements that relate to that type of information is not required.

C.11.8.2

Accessible content creation

Type of assessment
Pre-conditions
Procedure
ResultC.11.8.3

Preservation of accessibility information in transformations

Type of assessment
Pre-conditions

Procedure

ResultC.11.8.4

ResultInspection and Testing
1. The software is an authoring tool.
2. The authoring tool provides restructuring transformations or re-coding
transformations.
1. For a restructuring transformation, check if the accessibility information is preservedin the output.
2. For a restructuring transformation, check if the content technology supports
accessibility information for the restructured form of the information.
3. For a re-coding transformation, check if the accessibility information is preserved in
the output.
4. For a re-coding transformation, check if the accessibility information is supported by
the technology of the re-coded output.
Pass: Check 1 is true or checks 1 and 2 are false or check 3 is true or checks 3 and 4
are false
Fail: Check 1 is false and check 2 is true

Repair assistanceType of assessment
Pre-conditions

Procedure

Inspection and Testing
1. The software is an authoring tool.
1. Check if the authoring tool has features that enable and guide the production ofcontent that conforms to clauses 9 (Web) and 10 (Non-web documents).
Pass: Check 1 is true
Fail: Check 1 is false

Inspection
1. The software is an authoring tool.
2. The accessibility checking functionality of the authoring tool can detect that content
does not meet a requirement of clauses 9 (Web) or 10 (Non-web documents) as
applicable.
1. The authoring tool provides repair suggestions when content does not meet arequirement of clauses 9 or 10 (as applicable).
Pass: Check 1 is true
Fail: Check 1 is false

ETSI

148
EN 301 549 V2.1.2 (2018-08)

C.11.8.5

Templates

Type of assessment
Pre-conditions

Inspection
1. The software is an authoring tool.
2. The authoring tool provides templates.
Procedure
1. Check that the authoring tool provides at least one template that supports thecreation of content that conforms to requirements of clauses 9 (Web content) or 10(Documents) as applicable.
2. Check that at least one template identified in step 1 is available and is identified asconforming to clauses 9 or 10 (as applicable).
ResultPass: Checks 1 and 2 are true
Fail: Check 1 or 2 is false
NOTE:
The identification as conforming to the requirements of clauses 9 or 10 (as applicable) described incheck 2 may be described in terms such as "Conformant to WCAG 2.1". Where the identification
does not explicitly state that all of the requirements identified in clauses 9 or 10 (as appropriate) arecovered, it may be necessary to use the template to create a web site or document and then test thatweb site or document according to the requirements of clauses 9 or 10 to provide full assurance thatthe template behaves as required.

C.12

Documentation and support services

C.12.1

Product documentation

C.12.1.1

Accessibility and compatibility features

Type of assessment
Pre-conditions
Procedure
ResultC.12.1.2

Accessible documentation

Type of assessment
Pre-conditions
Procedure
ResultC.12.2C.12.2.1

Inspection
1. Product documentation is supplied with the ICT.
1. Check that product documentation provided with the ICT lists and explains how to
use the accessibility and compatibility features of the ICT.
Pass: Check 1 is true
Fail: Check 1 is false

Inspection
1. Product documentation in electronic format is supplied with the ICT.
1. Check that product documentation in electronic format provided with the ICT
conforms to the requirements of clauses 9 or 10 as appropriate.
Pass: Check 1 is true
Fail: Check 1 is false

Support services
GeneralClause 12.2.1 is informative only and contains no requirements requiring test.

C.12.2.2

Information on accessibility and compatibility features

Type of assessment
Pre-conditions
Procedure
ResultInspection
1. ICT support services are provided.
1. Check that the ICT support services provide information on the accessibility andcompatibility features that are included in the product documentation.
Pass: Check 1 is true
Fail: Check 1 is false

ETSI

149
EN 301 549 V2.1.2 (2018-08)

C.12.2.3

Effective communication

Type of assessment
Pre-conditions
Procedure
ResultNOTE:

C.12.2.4

Inspection
1. ICT support services are provided.
1. Check that the ICT support services accommodate the communication needs ofindividuals with disabilities either directly or through a referral point.
Pass: Check 1 is true
Fail: Check 1 is false
The provision of any level of support for the communication needs of individuals with disabilities
constitutes a pass of this requirement. Suppliers may wish to provide further information about thelevel of support that is provided to enable the adequacy and quality of the support to be judged.

Accessible documentation

Type of assessment
Pre-conditions
Procedure
ResultInspection
1. Documentation is provided by the ICT support services.
1. Check that documentation in electronic format provided by the ICT support services
conforms to the requirements of clauses 9 or 10 as appropriate.
Pass: Check 1 is true
Fail: Check 1 is false

C.13

ICT providing relay or emergency service accessC.13.1

Relay service requirements

C.13.1.1

GeneralClause 13.1.1 is informative only and contains no requirements requiring test.

C.13.1.2

Text relay services

Type of assessment
Pre-conditions
Procedure
ResultC.13.1.3

Sign relay services

Type of assessment
Pre-conditions
Procedure
ResultC.13.1.4

Inspection
1. The service is a sign relay service.
1. Check that the service enables sign language users and speech users to interact byproviding conversion between the two modes of communication.
Pass: Check 1 is true
Fail: Check 1 is false

Lip-reading relay services

Type of assessment
Pre-conditions
Procedure
ResultInspection
1. The service is a text relay service.
1. Check that the service enables text users and speech users to interact by providing
conversion between the two modes of communication.
Pass: Check 1 is true
Fail: Check 1 is false

Inspection
1. The service is a lip-reading relay service.
1. Check that the service enables lip-readers and voice telephone users to interact byproviding conversion between the two modes of communication.
Pass: Check 1 is true
Fail: Check 1 is false

ETSI

150
EN 301 549 V2.1.2 (2018-08)

C.13.1.5

Captioned telephony services

Type of assessment
Pre-conditions
Procedure
ResultC.13.1.6

Speech to speech relay services

Type of assessment
Pre-conditions
Procedure
ResultC.13.2

Procedure
ResultInspection
1. The ICT system supports two-way communication.
2. A set of relay services for two-way communication is specified.
1. Check that the system does not prevent access to those relay services for incoming
and outgoing calls.
Pass: Check 1 is true
Fail: Check 1 is false

Access to emergency services

Type of assessment
Pre-conditions
Procedure
ResultInspection
1. The service is a speech to speech relay service.
1. Check that the service enables enable speech or cognitively impaired telephoneusers and any other user to communicate by providing assistance between them.
Pass: Check 1 is true
Fail: Check 1 is false

Access to relay services

Type of assessment
Pre-conditions

C.13.3

Inspection
1. The service is a captioned telephony service.
1. Check that the service assists a deaf or hard of hearing user in a spoken dialogue by
providing text captions translating the incoming part of the conversation.
Pass: Check 1 is true
Fail: Check 1 is false

Inspection
1. The ICT system supports two-way communication.
2. A set of emergency services for two-way communication is specified.
1. Check that the system does not prevent access to those emergency services foroutgoing and incoming calls.
Pass: Check 1 is true
Fail: Check 1 is false

ETSI

151
EN 301 549 V2.1.2 (2018-08)

Annex D (informative):
WCAG 2.1 AAA Success Criteria
Table D.1 lists the Level AAA Success Criteria from the W3C Web Content Accessibility Guidelines (WCAG 2.1) [5].
Table D.1: WCAG 2.1 Level AAA Success Criteria
No.

Guideline

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28

Time-based media
Time-based media
Time-based media
Time-based media
Adaptable
Distinguishable
Distinguishable
Distinguishable
Distinguishable
Keyboard Accessible
Enough time
Enough time
Enough time
Enough time
Seizures and physical reactions
Seizures and physical reactions
Navigable
Navigable
Navigable
Input modalities
Input modalities
Readable
Readable
Readable
Readable
Predictable
Input assistance
Input assistance

Success
Criterion
Number
1.2.6
1.2.7
1.2.8
1.2.9
1.3.6
1.4.6
1.4.7
1.4.8
1.4.9
2.1.3
2.2.3
2.2.4
2.2.5
2.2.6
2.3.2
2.3.3
2.4.8
2.4.9
2.4.10
2.5.5
2.5.6
3.1.3
3.1.4
3.1.5
3.1.6
3.2.5
3.3.5
3.3.6

ETSI

Success Criteria Name

Sign Language (Prerecorded)
Extended Audio Description (Prerecorded)Media Alternative (Prerecorded)
Audio-only (Live)
Identify Purpose
Contrast (Enhanced)
Low or No Background Audio
Visual Presentation
Images of Text (No Exception)
Keyboard (No Exception)
No Timing
Interruptions
Re-authenticating
Timeouts
Three Flashes
Animation form Interactions
Location
Link Purpose (Link Only)
Section Headings
Target Size
Concurrent Input Mechanisms
Unusual Words
Abbreviations
Reading Level
Pronunciation
Change on Request
Help
Error Prevention (All)152
EN 301 549 V2.1.2 (2018-08)

History
Document history
V1.1.1February 2014

Publication

V.1.1.2

April 2015

Publication

V2.1.1February 2018

EN Approval Procedure

AP 20180514:

2018-02-13 to 2018-05-14

V2.1.2June 2018

Vote

V20180824:

2018-06-25 to 2018-08-24

V2.1.2

August 2018

Publication

ETSI