Evaluación Accesibilidad

EVALUACIÓN DE LA
ACCESSIBILIDAD DIGITAL
Dr. Cristian Rusu
Pontificia Universidad Católica de Valparaíso, Chile
cristian.rusu@pucv.cl
Dr. Toni Granollers El taller “Evaluando eXperiencias y habilidades:

U. de Lleida, Catalonia, Spain Usabilidad, Comunicabilidad, Accesibilidad, User
eXperience, Customer eXperience” ha sido impartido por
antoni.granollers@udl.cat Cristian Rusu y Toni Granollers en la ciudad de Popayán-
Colombia del 27 al 30 de Septiembre del 2016 durante el
11Congreso Colombiano de Computación.
Este material está sujeto a la licencia Creative Commons
Reconocimiento-NoComercial 4.0 Internacional License.
Índice
• Normativa legal y pautas de accesibilidad
• Metodología de evaluación
• Ejemplos y Buenas prácticas
Accesibilidad - 11CCC
Web Accessibility Initiative (WAI)
• Grupo de trabajo permanente del W3C (Word Wide Web
Consortium), organización internacional que trabaja en el
desarrollo de estándares web
• La WAI se encarga de velar

por la accesibilidad de los
contenidos web
http://www.w3.org/WAI
WAI (Web Accessibility Initiative)
• Grupo de trabajo permanente del W3C cuyos objetivos

principales son:
• Facilitar el acceso a la WEB a las personas con discapacidad
• Desarrollar pautas de accesibilidad (WCAG)
• Desarrollar y mejorar las herramientas de evaluación y de
reparación de la accesibilidad Web
• Formación y concienciación en relación del diseño accesible (design
for all, ...)
WAI. Pautas WCAG
http://www.w3.org/WAI/WCAG2-Conformance
• WCAG (Web Content Accessibility Guidelines)

• Pautas de accesibilidad que explican como hacer el
contenido Web accessible para personas con
discapacidades o de edad avanzada
• Tienen tres niveles de prioridad
• Simple(Nivel A) Doble (Nivel AA) Triple (Nivel AAA)
WAI. Pautas WCAG http://www.w3.org/TR/WCAG20
Ejemplo de las pautas
WAI. Pautas WCAG http://www.w3.org/TR/
UNDERSTANDING-
Entendiendo las pautas WCAG20
http://
www.w3.org/TR/UNDERS
TANDING-WCAG20/text-e
quiv.html
WAI. Pautas WCAG
Quick Reference http://www.w3.org/WAI/WCAG20/quickref
• Table of Contents
• WCAG 2.0 Quick Reference List
• 1.1 Text Alternatives
• 1.2 Time-based Media
• 1.3 Adaptable
• 1.4 Distinguishable
• 2.1 Keyboard Accessible
• 2.2 Enough Time
• 2.3 Seizures
• 2.4 Navigable
• 3.1 Readable
• 3.2 Predictable
• 3.3 Input Assistance
• 4.1 Compatible
W3C Web Content Accessibility Guidelines 2.0
Conformance Logos
• Place the icon for the appropriate conformance level using the
HTML source code from http://
www.w3.org/WAI/WCAG2-Conformance
<a href="http://www.w3.org/WAI/WCAG2A-
Conformance" title="Explanation of
WCAG 2.0 Level A Conformance">
<img height="32" width="88"
src="http://www.w3.org/WAI/wcag2A"
alt="Level A conformance, W3C WAI Web
Content Accessibility Guidelines 2.0">
</a>
http://www.w3.org/WAI/demos/bad/Overview.html
Estrategia Española sobre Discapacidad 2012-
2020
http://www.msssi.gob.es/ssi/discapacidad/informacion/
estrategiaEspanolaDiscapacidad.htm
Plan de Acción de la Estrategia Española sobre
Discapacidad 2014-2020
http://www.msssi.gob.es/ssi/discapacidad/informacion/planAccionEstrategiaEspanolaDiscapacidad.htm
https://ec.europa.eu/digital-agenda/en/web-accessibility
Legislación española
IM
PO
RT
AN
TE
• Real Decreto 1494/2007 de 12 de noviembre el 2007, por el que se aprueba el
“Reglamento sobre las condiciones básicas para el acceso de las personas con
discapacidad a las tecnologías, productos y servicios relacionados con la
Sociedad de la Información y medios de comunicación social”
• A parte de la web, trata acerca de la garantía de accesibilidad de la TDT para las personas con
discapacidad (contenidos + HW)
• Por ej.: Ergonomía en los receptores de televisión digital, así como en todos sus dispositivos asociados,
y, muy especialmente, en el diseño de los mandos a distancia.
• Plazos para las páginas de internet de las administraciones públicas o con

financiación pública:
• Las nuevas páginas web se tienen que ajustar al nivel 1 desde la entrada en vigor del reglamento 
el día siguiente al de su publicación en el BOE, es decir, 22/11/2007
• Las páginas web existentes se tienen que adaptar al nivel 1 en el plazo de 6 meses  22/05/2008
• Todas las páginas, actualmente existentes o de nueva creación, tienen que cumplir el nivel 2 a
partir del 31/12/2008R.D. 1494/2007: http://www.boe.es/boe/dias/2007/11/21/pdfs/A47567-47572.pdf
UNE 139803:2004: http://www.inteco.es/Accesibilidad/difusion/Normativa/Descarga/DescargaUNE_139803
• Los niveles mencionados son según la Norma UNE 139803:2004
ATENCIÓN !!: la norma UNE 139803:2004 es anulada por la UNE 139803:2012
Norma UNE 139803
• la Norma UNE 139803:2012 es equivalente a las WCAG 2.0
• Los requisitos de nivel A, AA y AAA son los criterios de conformidad de
nivel A, AA y AAA de las WCAG 2.0, a los que se referencia
directamente sin reescribirlos.
• Para cumplirlos se deberá tener en cuenta también el documento:
Techniques for WCAG 2.0. Techniques and Failures for Web Content
Accessibility Guidelines 2.0 (W3C Working Group Note 3 January 2012)
• http://www.w3.org/TR/WCAG20-TECHS
• Ampliar detalles:
• http://olgacarreras.blogspot.com.es/2012/07/nueva-version-de-la-norma-une-139803.html
Norma Técnica Colombiana (NTC) 5854
Enero 31 de 2012
• Comité de normalización
conformado por 15
entidades entre publicas,
privadas y de educación
• Objeto: establecer los
requisitos de accesibilidad
que se deben implementar
en las páginas web
nacionales en los niveles
de conformidad A, AA y
AAA del W3C.
• Esta norma es
equivalente a WCAG 2.0
Legislación en Colombia
• Colombia dispone de unas leyes y unas normas de las más
avanzadas en el área de Iberoamérica.
• ...
• El 20 de noviembre de 2013 se publicó la Ley No. 1680, por la
cual se garantiza a las personas ciegas y con baja visión, el
acceso a la información, a las comunicaciones, al conocimiento
y a las tecnologías de la información y de las comunicaciones.
• Ley 1712 de 6 de marzo de 2014, "por medio de la cual se crea
la Ley de Transparencia y del Derecho de Acceso a la
Información Pública Nacional y se dictan otras disposiciones“
• ARTÍCULO 8o. CRITERIO DIFERENCIAL DE ACCESIBILIDAD
Índice
Normativa legal y pautas de accesibilidad
• Metodología de evaluación
WCAG-EM Overview: http://www.w3.org/WAI/eval/conformance
Website Accessibility Conformance Evaluation
Methodology
• 5 main steps:
1. Define the scope of the evaluation - defining what is included in the
evaluation; the goal of the evaluation; and the WCAG conformance
level (A, AA, AAA).
2. Explore the website - identifying key web pages; key functionality;
types of web content, designs, functionality, etc.; required web
technologies.
3. Select a representative sample - guidance on structured and randomly
selected web pages when it is not feasible to evaluate every web page
on a website.
4. Evaluate the selected sample - determining successes and failures in
meeting WCAG 2.0; accessibility support for website features; and
recording evaluation steps.
5. Report the evaluation findings
Evaluating Websites for Accessibility
• These are particularly important resources that outline different

approaches for evaluating websites for accessibility:
• Easy Checks - A First Review of Web Accessibility
• Involving Users in Web Accessibility Evaluation
• Selecting Web Accessibility Evaluation Tools
• Reporting Template
Easy Checks - A First Review of Web
Accessibility
• checks for the following specific aspects of a web page

• Page title
• Image text alternatives ("alt text") in pictures, illustrations, charts, etc.
• Text:
• Headings
• Contrast ratio ("color contrast")
• Resize Text
• Interaction:
• Keyboard access and visual focus
• Forms, labels, and errors (including Search fields)
• General:
• Multimedia (video, audio) alternatives
• Basic Structure Check
Easy Checks - A First Review of Web Accessibility
Page titles
• Page titles are:
• shown in the window title bar in some browsers
• shown in browsers' tabs when there are multiple web
The first thing
pages open screen readers say
• shown in search engine results when the user
• used for browser bookmarks/favorites goes to a different
web page is the
• read by screen readers
page title
HTML: they are the <title> within the <head>
Image text alternatives ("alt text")
• Text alternatives ("alt text"):
• convey the purpose of an image (pictures, illustrations, charts, etc.)
• used by people who cannot see the image
• people who are blind and use screen readers can hear the alt text read out
• people who have turned off images to speed download or save bandwidth can
see the alt text
The text should be functional and

provide an equivalent user experience,
• Appropriate text alternative? not necessarily describe the image
• for a search button would be "search", not "magnifying glass“
• Automated tests can tell you if alt is missing. To determine if the
alternative text is appropriate, you need to see the image and judge
it in context
Image text alternatives ("alt text")
El paciente le dice al
medico: Doctor, hace una
semana que no como, no
duermo y no tomo agua.
¿Que cree que tengo?.
Y el doctor responde:
Pues, hambre, sueño y
sed
Imagen 1
Tíulo: Gráfica dehttp://
Fuente: evolución demográfica de Granada entre 1900 y 2013
Podemoswww.todacolombia.com/departamentos/departamentoscolombianos.html
ver que la población pasa de 75570 habitantes en 1900 a 255000
en 1991. A partir de aquí se estanca, aunque disminuye ligeramente.
Fuente: Wikipedia- Granada
Ejemplo: error difícil de encontrar
Ejemplo: error difícil de encontrar
Text: Headings
people can navigate to the

headings — including
people who cannot use a
mouse and use only the
keyboard, and people who
use a screen reader
• The heading hierarchy is meaningful. Ideally the

page starts with an "h1" — which is usually
similar to the page title — and does not skip
levels; however, these are not absolute
requirements.
Text: Headings
Text: color contrast
Some people cannot read text if Some people cannot read text if
there is not sufficient contrast there is not sufficient contrast
between the text and background between the text and background
High contrast is required by some people with visual impairments,

including many older people who lose contrast sensitivity from ageing
• While some people need high contrast, for others (by ex. people
with dyslexia) bright colors (high luminance) are not readable.
They need low luminance
Some people cannot read text if Some people cannot read text if
there is not sufficient contrast there is not sufficient contrast
between the text and background between the text and background
Web browsers should allow

people to change the color of
text and background, and web
pages need to work when
people change colors
• Some tools
http://
webaim.org/resou
rces/contrastchec
ker
Text: Resize
• Some people need
• to enlarge web content in order to read it
• to change other aspects of text display: font, space between lines, and more
• (most) browsers allow users to change text size through:
• text size settings (usually through Options or Preferences)
• text-only zoom
• page zoom (which also zooms images, buttons, etc.)
• BUT when pages are not designed properly, they can be

unusable when the text size is changed, especially when it is
changed through text-only zoom or text settings.
• Sometimes columns and sections overlap, the space between lines
disappears, lines of text become too long, or text disappears
Text: Resize
when text size is increased, the

heading overlaps the main text,
the main text overlaps the
sidebar text; and the sidebar text
is cut off at the bottom
Text: Resize
some of the larger text is not

visible without scrolling
horizontally
Most people cannot
effectively read text
that requires
normal-size text
horizontal scrolling,
and some
disabilities make
this impossible
larger text "wraps"

to fit the width
Interaction: Keyboard access and visual
focus
• Some people cannot use a mouse and rely on the keyboard to
interact with the Web.
• Some blind and people with mobility impairments rely on the
keyboard or on assistive technologies and strategies that
rely on keyboard commands, such as voice input.
• Websites need to enable people to access all content and

functionality — links, forms, media controls, etc. — through
a keyboard
focus
Keyboard focus should
be visible and should
follow a logical order
through the page
elements.
focus
• check for:
• Tab to all
• Tab away (A common problem is the keyboard focus gets caught in media controls and you
cannot get out; it's called the "keyboard trap")
• Tab order: logical reading order (e.g., for left-to-right languages: top to bottom, left to
right) in sequence
• Visual focus
• All functionality by keyboard: Check that you can do everything with the keyboard; that
is, you don't need the mouse to activate actions, options, visible changes, and other
functionality.
• A common problem is that some functionality is available only with mouse hover, and is not
available with keyboard focus
• Drop-down lists: Check that after you tab into a drop-down list, you can use the arrow keys
to move through all the options without triggering an action.
• A common problem for drop-downs used for navigation is that as soon as you arrow down, it
automatically selects the first item in the list and goes to a new page — you cannot get to other
items in the list.)
• Image links: when images are links, they have clear visual focus and can be activated using
the keyboard (usually by pressing the Enter key)
Interaction: Forms, labels, and errors
• Form fields and other form controls usually have visible labels
as the label for a text field.
When these labels are marked up
correctly, people can interact with them
using only the keyboard, using voice input,
and using screen readers.
<div>
<p id="namenewsletter" class="input">
<label for="mr">Mr. <input type="radio" name="t" id="mr" value="mr" title="title"></label>
<label for="mrs">Mrs. <input type="radio" name="t" id="mrs" value="mrs" title="title"></label>
<label for="n">Name: <input type="text" name="n" id="n" size="30"></label>
</p>
<p id="emailinput" class="input" style="width: 16em; float: left; margin-top: 0.5em;">
<label for="em">eMail Address: <br><input type="text" name="em" id="em" size="20"></label>
</p>
<p id="emailvalid" class="input" style="width: 16em; float: left; margin-top: 0.5em;">
<label for="ev">Retype eMail: <br><input type="text" name="ev" id="ev" size="20"></label>
</p>
</div>
Interaction: Forms, labels, and errors
• Error handling: try leaving required fields blank or entering

incorrectly-formatted information (such as telephone number or
e-mail address), then submitting the form.
• If you get errors, check that:
• clear and specific guidance is provided to help people understand and
fix the error.
• the errors are easily findable.
for some disabilities, this
• Generally it is best if the error is the only way of being
messages are before the form, able to link the error
message with the field
rather than after the form.
• the fields without errors are still populated with the data you entered.
• This is best practice, not a requirement. People should not have to re-enter all
the information in the form, except for some sensitive data such as credit card
numbers.
General: Multimedia alternatives
• Information in podcasts or other audio is not available
to people who are deaf or some people who are hard of
hearing, unless it is provided in an alternative format
such as captions (subtitles) and text transcripts.
• Visual information in videos is not available to people

who are blind or some people what have low vision,
unless it is provided in an alternative format such as
audio or text.
Text can be read by a
screen reader or Braille
display, or enlarged and
reformatted for people
http://www.videoaccessible.udl.cat/faq.html with low vision
General: Basic structure check
• Web pages are often designed with multiple columns, sections,
colors, and other visual aspects that help organize information
for people who see the page in its default display.
• However, some people do not see the page this way.
• People who are blind listen to the page with a screen reader or read it
from a Braille display.
• Some people with low vision and others change the way the page is
displayed so they can read it
• for example, change from multiple columns to one column, change the text
size, and more.
• An important issue is how the web page works when it is
"linearized" into one column and the presentation is changed.
"linearized"
into one
column
The order of the sections (e.g., navigation

at top or bottom or elsewhere) depends on
how the web page is developed — the
user usually cannot control the order
• What to do? Get a basic
structure view of the page:
• Turn off images and show the
text alternatives.
• Turn off style sheets (CSS),
which specifies how the page is
displayed with layout, colors, etc.
• Linearize the page or the tables
(depending on the toolbar).

 Easy Checks - A First Review of Web Accessibility
• Involving Users in Web Accessibility Evaluation
It’s enough validating WAG ??
Involving Users in Web Accessibility Evaluation
Combine User Evaluation
with Standards
• Range of User Evaluation
• Informal evaluation of a specific accessibility issue can be as simple as asking
someone you know who uses a screen reader, someone with other disabilities, or even
your grandmother, to find some data in an early draft of a data table that you are
developing, observing her interaction, and discussing issues.
• Formal usability testing of a website follows established protocols to gather
quantitative and qualitative data from representative users performing specific tasks.
• Formal usability tests can be optimized to focus on accessibility issues.
• What type of evaluation you do depends on factors such as the stage in your
project, for example, initial investigation of design ideas, testing specific
areas of prototypes, or reviewing final designs.
• Readings:
• http://www.w3.org/WAI/eval/users
• http://www.w3.org/WAI/users/involving

 Involving Users in Web Accessibility Evaluation
http://www.w3.org/WAI/eval/selectingtools
Selecting Web Accessibility Evaluation Tools
http://www.w3.org/WAI/ER/tools
Use at least 2 automàtic evaluators:
• http://www.tawdis.net
• http://www.examinator.ws
• http://wave.webaim.org/?lang=es
• http://achecker.ca/checker/index.php
• http://www.tenon.io
WARNIGS must be
manually reviewed
http://www.tawdis.net
• Toolbars
• Internet Explorer: Web Accessibility Toolbar For IE
• http://www.paciellogroup.com/resources/wat/ie
• Mozilla Firefox: Web Developer Toolbar
• https://addons.mozilla.org/es-ES/firefox/addon/60
• Wave toolbar: http://wave.webaim.org/toolbar
The WAVE Firefox Toolbar is no longer available ... We recommend that you
install the updated WAVE Chrome extension. [http://wave.webaim.org/toolbar]
• Tools: Chrome accessibility https://

chrome.google.com/webstore/search/accessibility
• Accessibility in
Wordpress

 Involving Users in Web Accessibility Evaluation
 Selecting Web Accessibility Evaluation Tools
Reporting Template
http://www.w3.org/WAI/eval/template.html
• 1. Executive Summary
• 2. Background about Evaluation
• 3. Web Site Reviewed
• 4. Reviewer(s)
• 5. Review Process
• 6. Results and Recommended Actions
• Interpretative summary of review results
• Detailed results, structured according to WCAG Checklist
• Describe or point to a suggested program of on-going monitoring of Web
site accessibility, re-evaluation of authoring tools, etc.
• 7. References
• 8. Appendices
Al campus virtual: [EXEMPLE] Informe_Avaluacio_Accessibilitat_PlantillesSPRL (Maig2010).pdf
Índice
Definiciones
Tecnología asistencial
Accesibilidad y documentos digitales
Normativa legal y pautas de accesibilidad
Metodología de evaluación
http://webaim.org/resources/
evalquickref/evalquickref.pdf
Buenas prácticas de diseño web
• 10 Quick Tips (http://www.w3.org/WAI/quicktips)
1. Images & animations: Use the alt attribute to describe the function of
each visual.
2. Image maps. Use the client-side map and text for hotspots.
3. Multimedia. Provide captioning and transcripts of audio, and descriptions of video.
4. Hypertext links. Use text that makes sense when read out of context. For example,
avoid "click here“.
5. Page organization. Use headings, lists, and consistent structure. Use CSS for layout
and style where possible.
6. Graphs & charts. Summarize or use the longdesc attribute.
7. Scripts, applets, & plug-ins. Provide alternative content in case active features are
inaccessible or unsupported.
8. Frames. Use the noframes element and meaningful titles.
9. Tables. Make line-by-line reading sensible. Summarize.
10. Check your work. Validate. Use tools, checklist, and guidelines at
http://www.w3.org/TR/WCAG
Simular discapacidades i altres eines
• Simulació discapacitats visuals

https://chrome.google.com/webstore/detail/see/dkihcccbkkakkbpikjmpnbamkgbjfdcn
• Visión (Visual Impairment Simulator): http://vis.cita.uiuc.edu/downld.php
• Simulació daltonisme
https://chrome.google.com/webstore/detail/chrome-daltonize/efeladnkafmoofnbagdbfaieab
mejfcf
• Nocoffee Visual impairment simulator (Chrome extension):

https://chrome.google.com/webstore/detail/nocoffee/jjeeggmbnhckmgdhmgdckeigabjfbddl
• NC state university palette accessibility evaluator:
http://accessibility.oit.ncsu.edu/tools/color-contrast/
• Contrast finder: http://contrast-finder.tanaguru.com/
• Per testejar les APIs d'accessibilitat
http://accessibility.linuxfoundation.org/a11yweb/util/accprobe/
• Valid XHTML YouTube embed code generator: http://
www.tools4noobs.com/online_tools/youtube_xhtml
• http://www.webaim.org/simulations/distractability-sim.html
Accessible and beautiful Web
designs http://www.csszengarden.com
http://webaim.org/resources/designers
Algunos proyectos
• In-TIC (Integración de las Tecnologías de la Información y las
Comunicaciones en los colectivos de personas con diversidad
funcional)
http://
www.proyectosfundacionorange
.es/intic/index.php
Algunos proyectos
• Tur4All Turismo para Todos
http://aspacenet.aspace.org/tabletas-
apps/item/tur4all-turismo-para-todos
¿Es suficiente?
algunas de las rampas para acceder a los pasos de
peatones tienen demasiada inclinación
se requiere aún de más empuje y mucha maña cuando

se trata de salvar pequeños socavones en el asfalto
en los que las ruedas quedan encalladas justo antes de
subir a la acera
Subir por las rampas de varios metros con la silla de

ruedas es toda una odisea
“Como discapacitados, cuestionamos la idoneidad de

las ayudas técnicas o de los arreglos que se han hecho
para hacer una zona accesible
 Diseño Centrado en el Usuario ???
Los semáforos son otros de los obstáculos … no por

cuestión de altura o pendiente, sino porque el tiempo
para cruzar es demasiado escaso y a menudo nos
quedamos en medio de la calzada cuando ya está en
rojo para los peatones
¿Es suficiente?
• Senior Friendly
• http://
www.nlm.nih.gov/pubs/checklist.
pdf
https://delicious.com/
Referecias destacadas tgranollers/accessibility
http://www.webaim.org/articles
http://accesibilidadenlaweb.blogspot.com.es
http://www.ilr.cornell.edu/edi/webaccesstoolkit/index.cfm
http://olgacarreras.blogspot.com.es/2009/04/dos-
anos-de-usable-y-accesible.html#accesibilidad
• Tecnología asistencial:
• http://www.taservicios.com
• http://www.tecnoaccesible.net
• Responsabilidades:
• http://www.w3.org/community/wai-engage/wiki/Accessibility_Responsibil
ity_Breakdown
• http://wet-boew.github.io/wet-boew/demos/arb-rra/arb-rra-en.html
Bibliografía
Edició Edició
n n
onlin onlin
e e
gratu gratu
ita ita
Henry, Shawn Lawton Thatcher, Jim Web Accessibility: Web

Just ask: integrating accessibility Standards and Regulatory Compliance.
throughout design, Friends of Ed: 2006, ISBN: 1590596382
February 2007 http://uiaccess.com/understanding.html

Language: English
ISBN-10: 1430319526
http://www.uiaccess.com/accessucd
Slatin, John M, Sharron Rush Maximum

accessibility : making your Web site more
Pro HTML5 Accessibility usable for everyone ; Boston : Addison-
Wesley, cop. 2003 xliv, 588 p. ISBN 0-201-
Professional Apress 77422-4
Joshue O Connor
March 26, 2012 | ISBN-10: 1430241942
Kara Pernice Coyne and Jakob

Nielsen Beyond ALT text: making the
Clark, Joe. Building Accessible Websites. web easy to use for users with
Indianapolis, Ind: New Riders, 2003. disabilities Fremont, CA : Nielsen
http://joeclark.org/book/sashay/serialization/
Norman Group, 2001
Bibliografía
Estudio de accesibilidad a la red

Informática y discapacidad: fundamento y
Romero Zúnica, Rafael, Francisco Alcantud aplicaciones
Marín, Antonio M. Ferrer Manchón México: Novedades Educativas, 2000
ISBN: 987-538-002-4
http://acceso.uv.es/accesibilidad/Estudio
Sánchez Montoya, Rafael Ordenador y

Guía de acceso al ordenador para discapacidad: Guía práctica de apoyo a las
personas con discapacidad Madrid personas con necesidades educativas
especiales Madrid:Cepe,2002
Candelos Arnao, Amparo, Manuel Lobato
Galindo http://www.ordenadorydiscapacidad.net/
IMSERSO, 1997 ISBN 84-88986-71-8
Strategic IT Accessibility: Enabling the Sloan, David Tangram Model For Web
Organization Accessibility, QA Focus briefing document no.
101, UKOLN,
Jeff Kline [http://www.ukoln.ac.uk/qa-focus/documents/b
riefings/briefing-101/]
Live Oak Book Company (August 18, 2011)
Toni Granollers
Escola Politècnica Superior
Gracias por su
Universitat de Lleida (UdL) atención !!!
C/ Jaume II, 69
25001 – Lleida

(+34) 973 702750
@ antoni.granollers@udl.cat
@DCU_MPIUA
slideshare.net/DCU_MPIUA

Evaluación Accesibilidad

Cargado por

Información del documento

Título original

Derechos de autor

Formatos disponibles

Compartir este documento

Compartir o incrustar documentos

Opciones para compartir

¿Le pareció útil este documento?

¿Este contenido es inapropiado?

Copyright:

Formatos disponibles

Evaluación Accesibilidad

Cargado por

Copyright:

Formatos disponibles

EVALUACIÓN DE LA

Dr. Toni Granollers El taller “Evaluando eXperiencias y habilidades:

• La WAI se encarga de velar

• Grupo de trabajo permanente del W3C cuyos objetivos

• WCAG (Web Content Accessibility Guidelines)

• Tienen tres niveles de prioridad

• Simple(Nivel A) Doble (Nivel AA) Triple (Nivel AAA)

• Plazos para las páginas de internet de las administraciones públicas o con

• These are particularly important resources that outline different

• checks for the following specific aspects of a web page

The text should be functional and

people can navigate to the

• The heading hierarchy is meaningful. Ideally the

High contrast is required by some people with visual impairments,

Web browsers should allow

• BUT when pages are not designed properly, they can be

when text size is increased, the

some of the larger text is not

larger text "wraps"

• Websites need to enable people to access all content and

• Error handling: try leaving required fields blank or entering

• Visual information in videos is not available to people

The order of the sections (e.g., navigation

• These are particularly important resources that outline different

• These are particularly important resources that outline different

Use at least 2 automàtic evaluators:

• Mozilla Firefox: Web Developer Toolbar

• Wave toolbar: http://wave.webaim.org/toolbar

• Tools: Chrome accessibility https://

• These are particularly important resources that outline different

• 10 Quick Tips (http://www.w3.org/WAI/quicktips)

• Simulació discapacitats visuals

• Nocoffee Visual impairment simulator (Chrome extension):

se requiere aún de más empuje y mucha maña cuando

Subir por las rampas de varios metros con la silla de

“Como discapacitados, cuestionamos la idoneidad de

Los semáforos son otros de los obstáculos … no por

Henry, Shawn Lawton Thatcher, Jim Web Accessibility: Web

February 2007 http://uiaccess.com/understanding.html

Slatin, John M, Sharron Rush Maximum

Kara Pernice Coyne and Jakob

Estudio de accesibilidad a la red

Sánchez Montoya, Rafael Ordenador y

IMSERSO, 1997 ISBN 84-88986-71-8

También podría gustarte