WCAG 2.0
California State University, Los Angeles
U.S. Office for Civil
Rights
• WCAG 2.0 level AA will increasingly be set as the
standard by OCR
• Louisiana Tech University (2013)
• WCAG 2.0 AA compliance of all deployed
technology/course and web content
• Existing web content compliant by 12/2014
• Training of all instruction personnel and
administration
• Affirm role of Disability Services office
Section 508
• Federal Law
• Section 508 is a 1998 amendment to Rehabilitation
Act of 1973
• Eliminates barriers in IT
• Standards that establish minimum level of
accessibility
• Web based technology and info based on
guidelines from Web Accessibility Initiative of the
World Wide Web Consortium
• Is not specific, detailed, or testable
WCAG 2.0
• A – basic web accessibility features
• AA – biggest and most common barriers for disabled
users
• AAA – highest level of web accessibility, that many
websites cannot reach
WCAG 2.0
• Perceivable – Information and user interface components must be presentable to users in
ways they can perceive.
•
•
•
•
Guideline 1.1: Information and user interface components must be presentable to users in ways
they can perceive.
Guideline 1.2: Time-based Media: Provide alternatives for time-based media.
Guideline 1.3: Create content that can be presented in different ways (for example simpler layout)
without losing information or structure.
Guideline 1.4: Make it easier for users to see and hear content including separating foreground
from background.
• Operable – User interface components and navigation must be operable.
•
•
•
•
Guideline
Guideline
Guideline
Guideline
2.1: Make all functionality available from a keyboard.
2.2: Provide users enough time to read and use content.
2.3: Do not design content in a way that is known to cause seizures.
2.4: Provide ways to help users navigate, find content, and determine where they are.
• Understandable – Information and the operation of user interface must be understandable.
•
•
•
Guideline 3.1: Make text content readable and understandable.
Guideline 3.2: Make Web pages appear and operate in predictable ways.
Guideline 3.3: Help users avoid and correct mistakes.
• Robust – Content must be robust enough that it can be interpreted reliably by a wide variety
of user agents, including assistive technologies.
•
Guideline 4.1.: Maximize compatibility with current and future user agents, including assistive
technologies.
CSU
• CSU developed manual protocols based on WCAG
2.0 draft
• Compliance Sheriff/Deputy
• CSU stakeholders developed Checkpoints to be
used with Compliance Sheriff
• CSU accessible technology network tested the
checkpoints and CSUN supports them
• CSU Checkpoints mapped 508 to WCAG 2.0 to
make 508 testable
• CSU then added the manual protocol which goes
above and beyond 508
• Visual checks are required
• ati.calstate.edu/file.php/23/HiSoftware/CSU-ATIRequirements-Revised-09-17-14.docx
CSU
Description
Test Type:
Automated,
Visual
Possible
Result:
Pass/Fail,
Warn, Visual,
N/A
H24 Provide text
alternatives for the area
elements of image
maps (WCAG2)
Auto
Pass / Fail
N/A
H35 Provide text
alternatives on applet
elements (WCAG2)
Auto
Pass / Fail
H36 Use alt attributes
on images used as
submit buttons
(WCAG2)
Auto
Pass / Fail
Long Description
The objective of this technique is to
provide text alternatives that serve the
same purpose as the selectable regions of
an image map. An image map is an image
divided into selectable regions defined by
<code>area</code> elements. Each area is
a link to another Web page or another part
of the current Web page. The
<code>alt</code> attribute of each
<code>area</code> element serves the
same purpose as the selectable area of the
image.
Provide a text alternative for an applet by
using the alt attribute to label an applet
and providing the text alternative in the
body of the applet element. Both
mechanisms are required due to the
varying support of the alt attribute and
applet body text by user agents.
For input elements of type 'image', the
<code>alt</code> attribute of the
<code>input</code> element is used to
provide a functional label. This label
indicates the button's function, but does
not attempt to describe the image. The
label is especially important if there are
multiple submit buttons on the page that
each lead to different results.
Resources
http://www.w3.org/
TR/WCAG20TECHS/H24.html
http://www.csun.ed
u/universaldesignce
nter/webaccessibility-criteriaimage-map
http://www.w3.org/
TR/WCAG20TECHS/H35.html
http://www.w3.org/
TR/WCAG20TECHS/H36.html
Customizable
Cal State LA
• Using CSU Checkpoints with Compliance Sherriff and
now Compliance Deputy to test our web sites
• Training for manual checks and compliance
• Requirement for each division and college to perform
their own manual checks and fixes