Hello, my name is Loïc Martínez Normand,
I'm a lecturer at the Escuela Técnica Superior de Ingenieros Informáticos
de la Universidad Politécnica de Madrid.
This video shows application examples
of the technical standard EN 301 549 Accessibility of ICT products
for public procurement.
This standard may be applied to any ICT product or service,
due to its structure organized by characteristics
and because the requirements include preconditions
that limit its applicability.
In this video we are going to see examples,
organised by chapters in the standard.
But before we start
it's important to know that every example that we are going to see
would also have to comply with other chapters in the standard.
We start by remembering the requirements structure.
Requirement 5.3, Biometrics, requires that an ICT product or service
offers alternatives to the use of biological characteristics,
such as fingerprint or iris recognition.
There are two parts to this requirement.
The precondition indicating that the requirement only applies
when the ICT product or service
relies on biological characteristics (or "biometrics").
And the requirement itself,
which requires that the ICT product or service
does not rely on a single biological characteristic.
Now let's look at several examples.
First, an ATM
and Chapter 5 on generic requirements.
An ATM has hardware and software.
It is a product with closed functionality,
since it does not allow a user install or add support products.
Therefore, the cash machine must include
a completely accessible interface, without external support.
This is collected in section 5.1 of the standard.
The cash machine must be able to be used without vision,
must be able to be used with low vision,
offer alternatives to sound outputs
and offer alternatives to using the keyboard.
In addition, it may need to meet other generic requirements:
activation of accessibility features,
alternatives to biometrics,
preservation of accessibility information
and accessibility of controls and keys.
Let's go to the next block, communication by voice systems,
with an application for videoconferencing.
An application of this type
allows communication by video or by voice only.
And it could be a mobile app or a computer application.
According to chapter 6 of the standard,
It has to provide good audio quality,
offer communication by text in real time or RTT,
offer accessible information on caller ID,
offer alternatives to voice services,
facilitate quality video communication with for signs
or lip recognition,
and offer alternatives to video services
And RTT communication
must meet certain quality and interoperability requirements.
The following example will be a streaming video service,
and chapter 7 of the standard.
These services
allow customers to watch movies or series
on different platforms, e.g., TV, mobile, computers...
First, the service must properly manage
subtitules for deaf people,
allowing their display, synchronization and preservation.
It also must manage properly
the audio description for people who can´t see the screen.
And finally, it should provide adequate controls
to activate and deactivate subtitles and audio description.
The next chapter is hardware,
and we will apply it to a mobile phone.
We are just going to analyze the hardware of the mobile phone.
This hardware must comply with
the requirements in Chapter 8 of the standard,
and also with other requirements mentioned previously.
The mobile phone should offer standard connections,
or wireless, such as Bluetooth, or physical, such as USB-C,
to allow the use of support products.
And their hardware design should not rely on colour
as the only visual medium to provide information.
In addition, it must allow to turn up the voice volume
above 18db,
allow to control various levels of volume
and it must be compatible with the magnetic loop standards.
And the mechanic phone buttons
must be able to be used without pinching or twisting the wrist
and without having to exercise an excessive force.
Other parts of Chapter 8 do not apply to mobile phones,
fundamentally those related to physical access
for wheelchair users.
We now turn to three chapters in the standard on software:
Web, documents and software.
Chapter 9 of the standard applies to any kind of web content.
As an example, let's see a web page.
The standard is compatible with the AA conformity level
of the WCAG 2.0 guidelines.
This includes 38 criteria for success and 5 compliance requirements.
In any case let's not forget
that other chapters of the standard would also apply,
depending on the functionality offered by the website.
Let's go to the documents on the web, like an ebook.
Chapter 10 of the standard
applies to documents electronic devices other than web pages
or that are not embedded in web pages.
As an example, we will see an ebook,
the file that can then be read on specific hardware
or through an application.
The digital book must meet requirements equivalent to WCAG AA,
but with a wording adapted to documents on the web.
In addition, there are four exceptions to criteria
which are not considered applicable outside the web.
On the other hand, there are two additional recommendations:
Place captions properly
and synchronize the audio description correctly
not to hide important content.
Let's go to the software,
with a mobile app programmed in native code.
This mobile app
also needs to meet with requirements based on WCAG 2.0,
although there are exceptions to criteria not applicable to software in general.
In addition, the mobile application
will have to be compatible with support products,
using its platform services
to provide information and allow assisted interaction.
The mobile app will also have to avoid interfering
with the accessibility characteristics
and the visual platform configuration
and, if it is an authoring tool,
it will have to facilitate creating accessible content.
The last chapters of the standard deal with documentation,
customer service and intermediation services.
In all these cases, there are accessibility requirements
focused on offering equal opportunities
for disabled users.
This is the end of the examples of this video.
Today we have seen that the requirements in standard EN 301 549
can be applied to ICT products of any kind,
and we have explained this with several examples.
But we must not forget
that all chapters can be applied to almost any product,
beyond the examples we have seen today.