2016/2102/EU - 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.

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 a
form that is suitable for use in public procurement within Europe. The present document might be useful for other
purposes such as procurement in the private sector.
The relationship between the present document and the essential requirements of Directive 2016/2102 on the
accessibility 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 is
clear. The test descriptions and evaluation methodology included in the present document are elaborated to a level of
detail 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 '. 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).
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 user
interaction.
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.