HTML and CSS Reference
In-Depth Information
WAI Guidelines
Priority
5.5 Provide summaries for tables.
3
5.6 Provide abbreviations for header labels.
3
6. Ensure that pages featuring new technologies transform gracefully
6.1 Organize documents so they may be read without style sheets. For example, when an
HTML document is rendered without associated style sheets, it must still be possible
to read the document.
1
1
6.2 Ensure that equivalents for dynamic content are updated when the dynamic content
changes.
6.3 Ensure that pages are usable when scripts, applets, or other programmatic objects
are turned off or not supported. If this is not possible, then provide equivalent infor-
mation on an alternative accessible page.
1
6.4 For scripts and applets, ensure that event handlers are input device-independent.
2
6.5 Ensure that dynamic content is accessible or provide an alternative presentation or page.
2
7. Ensure user control of time-sensitive content changes
7.1 Until user agents allow users to control flickering, avoid causing the screen to flicker.
1
2
7.2 Until user agents allow users to control blinking, avoid causing content to blink (i.e.,
change presentation at a regular rate, such as turning on and off).
7.3 Until user agents allow users to freeze moving content, avoid movement in pages.
2
7.4 Until user agents provide the ability to stop the refresh, do not create periodically
auto-refreshing pages.
2
7.5 Until user agents provide the ability to stop auto-redirect, do not use markup to redi-
rect pages automatically. Instead, configure the server to perform redirects.
2
8. Ensure direct accessibility of embedded user interfaces
8.1 Make programmatic elements such as scripts and applets directly accessible or com-
patible with assistive technologies [Priority 1 if functionality is important and not pre-
sented elsewhere, otherwise Priority 2.]
2
9. Design for device-independence
9.1 Provide client-side image maps instead of server-side image maps except where the
regions cannot be defined with an available geometric shape.
1
9.2 Ensure that any element with its own interface can be operated in a device-
independent manner.
2
9.3 For scripts, specify logical event handlers rather than device-dependent event handlers.
2
9.4 Create a logical tab order through links, form controls, and objects.
3
9.5 Provide keyboard shortcuts to important links (including those in client-side image
maps), form controls, and groups of form controls.
3
10. Use interim solutions
10.1 Until user agents allow users to turn off spawned windows, do not cause pop-ups or
other windows to appear and do not change the current window without informing
the user.
2
10.2 Until user agents support explicit associations between labels and form controls,
ensure that labels are properly positioned for all form controls with implicitly associ-
ated labels.
2
10.3 Until user agents (including assistive technologies) render side-by-side text correctly,
provide a linear text alternative (on the current page or some other) for all tables
that lay out text in parallel, word-wrapped columns.
3
10.4 Until user agents handle empty controls correctly, include default, place-holding char-
acters in edit boxes and text areas.
3
10.5 Until user agents (including assistive technologies) render adjacent links distinctly,
include nonlink, printable characters (surrounded by spaces) between adjacent links.
3
 
Search WWH ::




Custom Search