can be applied, as the markup languages: XML,
eXtensible Hypertext Markup Language (XHTML)
or Cascading Style Sheets (CSS).
Specifications about audiovisual accessibility can
be applied too, as the Synchronized Multimedia
Integration Language (SMIL) to synchronize audio
and video (see section 3.2); Scalable Vector
Graphics (SVG) to describe XML Graphics; or the
Web Accessibility Initiative (WAI) which develops
guidelines to accessibility for different components.
Multimedia and audiovisual contents are specially
treated in WCAG 1.0 (W3C, 1999a). Nowadays,
they are working in the WCAG 2.0 (W3C, 2006a), it
demands alternative contents (caption, audio
description, extended audio descriptions and sign
language interpretation) to achieve different levels
of accessibility.
Nowadays there exist a great number of tools
oriented to the development and support of
multimedia on the Web. In this way, authoring tools
help us to create audiovisual contents integrating
caption and/or audio description, or help us to edit
them so that prerecorded multimedia can be included
(NCAM, 2006).
Due to these possibilities (languages, players,
editors, etc.) are not always compatible some with
others that the task of making multimedia accessible
is sometimes really difficult, but it is not impossible.
3 ACCESS TO MULTIMEDIA
WEB CONTENTS
Going back to the accessibility definition, a
multimedia content is accessible when a user can
access that content, regardless whether his access
characteristics and context of use. Sometimes we
can find in Web-sites accessible contents (offering
alternatives as captions and/or audio description),
but non-accessible resources because they are
reproduced via a control that does not appear in
every navigator. Or vice-versa, sometimes it is
possible to access the multimedia resource, but the
resource’s content is not accessible because it does
not offer alternative contents. In conclusion, we need
to ensure two different requirements for
accessibility:
- That the multimedia content is accessible
- That the access to the multimedia resource is
accessible.
Moreover, we can not forgot the necessity of
integrate the multimedia contents in an accessible
and usable user interface (Web page, player, etc.).
Then, the contrast of colours, accessible buttons for
control (alternative texts), etc. in the interface must
be taken into account. Furthermore, the user should
be allowed to interact with every hypermedia
element in the interface, controlling them device-
independently.
4 CASE STUDY
The case of study has been carried out in “The
Spanish Centre of Captioning and Audio description
(CESyA)” (CESyA, 2005). One of the main goals of
this centre is to study how to integrate accessible
multimedia resources in the media. This paper
presents some experiments studying the best way to
integrate a multimedia resource (a video called
“Nicolás”) in Internet in an accessible way.
This section describes how to make accessible
the video’s content and how to integrate the video in
the Web interface maintaining the accessibility.
Making accessible the video’s content means to
follow the current Web Content Accessibility
Guidelines (WCAG) and to provide synchronized
alternative contents such as caption and audio
description. Two different options can be
implemented for making accessible the video:
1. Video with open audio description and
caption. This option permits to create accessible
videos, but it has a big inconvenience: the user will
have not possibility of controlling the resource
reproduction, choosing if s/he prefers or not to play
the video or audio means separately in each moment.
2. Video with closed audio description and
caption, separating audio and text. There are
different options to create and edit a resource in
different formats. In this case, the system provides
the control to the user, allowing to adapt the
reproduction of the video according to his/her
current necessities.
This second option is more usable, because it
provides more control of the video reproduction and
adapts better to the user necessities.
Our studies implement this option. We have used
SMIL (W3C, 2006c) for the implementation,
following the recommendations of W3C, and the
video edition has been performed. The first step of
the edition was to separate the soundtrack from the
video.
ACCESSIBILITY OF MULTIMEDIA RESOURCES IN WEB
471