 |
|
|
|
Living Examples |
I have found through experience that, with more complicated issues such as
meaningful alternative text for images, the accessibility of Web-based forms, and the
navigability of complex data tables, the mere text of the 508
guidelines or explanations may simply not be enough to assist a
developer with ensuring their web sites are in compliance. And quite often, more experienced
developers who are already well versed in the guidelines are much more interested in seeing functioning
examples of these guidelines at work.
Thus, from these observations was born the idea for The "Living Examples" pages here.
Selecting a Section 508 checkpoint from the links below, you will find:
- the guideline from the U.S. Access Board,
- a brief explanation (taken from the Goddard ADB-developed checklist), and
- working code examples demonstrating the guideline.
In order to understand why following these guidelines is so important, it is sometimes helpful to see examples of both compliant and non-compliant code.
So, wherever possible, we will provide both compliant and non-compliant "living examples."
And of course, suggestions for additions and improvements are welcome, especially with regard to Web pages illustrating Section 508 compliance that can be added to the "Living Examples' section.
Please send any suggestions or questions to Courtney Smith, GSFC's Web Accessibility Coordinator.
|
| Living Examples List |
Text Equivalents for Non-text Elements
(a) A text equivalent for every non-text element shall be provided (e.g., via "alt",
"longdesc", or in element content). |
Tables Accessibility
(g) Row and column headers shall be identified for data tables.
(h) Markup shall be used to associate data cells and header cells for data tables
that have two or more logical levels of row or column headers. |
Electronic Forms
(n) When electronic forms are designed to be completed on-line, the form shall
allow people using assistive technology to access the information, field elements,
and functionality required for completion and submission of the form, including
all directions and cues. |
Multimedia Synchronization
(b) Equivalent alternatives for any multimedia
presentation shall be synchronized with the presentation |
Conveyed with Color
(c) Web pages shall be designed so that all information
conveyed with color is also available without
color, for example from context or markup. |
Accessibility Without Style
Sheets
(d) Documents shall be organized so they are readable
without requiring an associated style sheet. |
Server-Side Image Maps
(e) Redundant text links shall be provided for
each active region of a server-side image map. |
Client-Side Image Maps
(f) Client-side image maps shall be provided instead
of server-side image maps except where the regions
cannot be defined with an available geometric
shape. |
Frames Accessibility
(i) Frames shall be titled with text that facilitates
frame identification and navigation. |
Avoiding Flicker
(j) Pages shall be designed to avoid causing the
screen to flicker with a frequency greater than
2Hz and lower than 55 Hz. |
Scripting Languages
(l)When pages utilize scripting languages to display
content, or to create interface elements, the
information provided by the script will be identified
with functional text that can be read by assistive
technology. |
Applets and Plug-Ins
(m) When a web page requires that an applet, plug-in,
or other application be present on the client
system to interpret page content, the page must
provide a link to a plug-in or applet that complies
with §1194.21(a) through (l). |
Electronic Forms
(n) When electronic forms are designed to be completed
on-line, the form shall allow people using assistive
technology to access the information, field elements,
and functionality required for completion and
submission of the form, including all directions
and cues. |
Skipping Repetitive Navigation
(o) A method shall be provided that permits users
to skip repetitive navigation links. |
Timed Responses
(p) When a timed response is required, the user
shall be alerted and given sufficient time to
indicate more time is required. |
Text-Only Equivalent
(k) A text-only page, with equivalent information
or functionality, shall be provided to make a
web site comply with the provisions of this part,
when compliance cannot be accomplished in any
other way. The content of the text-only page
shall be updated whenever the primary page changes. |
|
|
|
|
