508
Checklist
The checklist below is meant to be a user-friendly
interpretation of Section 508 's sixteen Web accessibility standards
(a-p). If you would like to read the actual law, visit the Official
Section 508 Web site.
Click on the 
if you would like a more detailed explanation of a checkpoint.
(a) IMAGES
All photos, images and graphics-as-text must have equivalent
alt tags.
If necessary, create long descriptions of your images
using the longdesc attribute. |
(b) MULTIMEDIA
OR STREAMING MEDIA
If you have video clips, be sure they are captioned.
If you have audio files, be sure they are accompanied
by text transcriptions. |
(c) COLOR
USAGE & CONTRAST
Information conveyed with color must be understood without
color.
Text color must be in high contrast to the page’s
background color or background image. |
(d) CASCADING
STYLE SHEETS (CSS)
Websites that use CSS must still be understandable when
the Style Sheet is turned off. |
(e &
f) IMAGE MAPS
Use client side image maps, not server side image maps.
Image map regions must have alternate text. |
(g &
h) DATA TABLES
Provide a text summary of all data tables.
Identify column and row table headers.
Associate all rows and columns with their headers (HTML).
|
(i) FRAMES
If you use frames, be sure to choose a descriptive label
for each frame (HTML) |
(j) SCREEN
FLICKER
No flashing or blinking multimedia.
No scrolling or blinking text. |
(k) PAGE
ALTERNATIVES
A text only version of a web page should be created only
when there is no other way to make the content accessible.
|
(l) SCRIPTING
LANGUAGES
All scripts (i.e. JavaScript pop boxes, rollover buttons,
etc.) must be accessible to assistive technologies or
have text alternatives provided within the scripts themselves. |
(m) LINKS
TO PLUG-INS
If something on your site requires third-party software
or a plug-in, provide a link to the download site.
|
(n) FORMS
If you use forms, provide clear directions on how to use
them.
Each form element must have a text label associated through
HTML code. |
(o) NAVIGATION
Provide a link to skip over repetitive navigation links.
Use clear and consistent navigation throughout your site.
|
(p) TIMED
RESPONSE
When a timed response is required, the user shall be alerted
and given sufficient time to indicate more time is required. |
|
Assignment: WebAIM's Section
508 Checklist itemizes each guideline and details
what passes and what fails. Read this checklist and print
it out for future reference. It is a good companion to
the user-friendly checklist above.
|
Wait, Aren't There Other Standards For Accessibility Besides
Section 508?
As stated in the previous section, we are legally
responsible for ensuring that all SCC Web sites are Section
508 compliant. However, there are other standards
for Web accessibility, such as the World
Wide Web Consortium's (W3C) Web
Accessibility Initiative (WAI).
The W3C's Web
Content Accessibility Guidelines 1.0 (WCAG) are divided
into 3 levels of accessibility:
Priority 1 (A Web content developer must
satisfy this checkpoint)
Priority 2 (A Web content developer should
satisfy this checkpoint)
Priority 3 (A Web content developer may address
this checkpoint)
Section 508 guidelines includes all Priority
1 checkpoints, as well as a couple from Priority 2 and 3. At
a minimum, SCC Web sites should be Section 508 compliant, but
if you feel like making your site even more accessible,
check out the WCAG!
April, 2006: The W3C has created a working draft of WCAG 2.0.
>> Continue to the next section: Manila
|
