<h1>Web Accessibility</h1>
<h2>What Does It Mean?</h2>
Associate Professor of Economics
Webmaster, College of Liberal Arts
"Level Double-A"
Quick links on this page:
[ Highlights ]
[ Tables ]
[ Frames ]
[ Forms ]
[ Applets and scripts ]
[ Related topics ]
"A Web content developer should satisfy this checkpoint. Otherwise, one or more groups will find it difficult to access information in the document.
Satisfying this checkpoint will remove significant barriers to accessing Web documents."
(Source: "List of Checkpoints for Web Content Accessibility Guidelines 1.0")
Highlights:
- Ensure that foreground and background color combinations provide sufficient contrast when viewed by someone having color deficits or when viewed on a black and white screen.
[Priority 2 for images, Priority 3 for text].
- When an appropriate markup language exists, use markup rather than images to convey information.
- Create documents that validate to published formal grammars.
- Use style sheets to control layout and presentation.
- Use relative rather than absolute units in markup language attribute values and style sheet property values.
- Use header elements to convey document structure and use them according to specification.
- Mark up lists and list items properly.
- Mark up quotations. Do not use quotation markup for formatting effects such as indentation.
- Ensure that dynamic content is accessible or provide an alternative presentation or page.
- 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).
- Until user agents provide the ability to stop the refresh, do not create periodically auto-refreshing pages.
- Until user agents provide the ability to stop auto-redirect, do not use markup to redirect pages automatically. Instead, configure the server to perform redirects.
- 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.
- Use W3C technologies when they are available and appropriate for a task and use the latest versions when supported.
- Avoid deprecated features of W3C technologies.
- Divide large blocks of information into more manageable groups where natural and appropriate.
- Clearly identify the target of each link.
- Provide metadata to add semantic information to pages and sites.
- Provide information about the general layout of a site (e.g., a site map or table of contents).
- Use navigation mechanisms in a consistent manner.
If you use tables:
- Do not use tables for layout unless the table makes sense when organized in a linear order. Otherwise, if the table does not make sense, provide an alternative equivalent (which may be a linear version).
- If a table is used for layout, do not use any structural markup for the purpose of visual formatting.
If you use frames:
- Describe the purpose of frames and how frames relate to each other if it is not obvious by frame titles alone.
If you use forms:
- Until user agents support explicit associations between labels and form controls, for all form controls with implicitly associated labels, ensure that the label is properly positioned.
- Associate labels explicitly with their controls.
If you use applets and scripts:
- For scripts and applets, ensure that event handlers are input device-independent.
- Until user agents allow users to freeze moving content, avoid movement in pages.
- Make programmatic elements such as scripts and applets directly accessible or compatible with assistive technologies
[Priority 1 if functionality is important and not presented elsewhere, otherwise Priority 2].
- Ensure that any element that has its own interface can be operated in a device-independent manner.
- For scripts, specify logical event handlers rather than device-dependent event handlers.
Related topics
[ Workshop home ]
[ For Whom? ]
[ Why? ]
[ Overview ]
[ "Levels" ]
[ More information ]
[ Examples ]
[ ]
( Privacy Policy | Last saved August 17, 2004 )