Bypassing Repetitive Content

A method should be provided that permits users to skip repetitive navigation links.

Many sites include a series of navigation links at the top, or down the side of the page, sometimes repeating on every subsequent or embedded page. These navigation links can be frustratingly repetitive for users of screen-readers since screen readers read from beginning to end and users do not always have the ability to ignore content unless a means is provided to bypass it.

You can create bypass links to reduce this unnecessary reading. One of the most common strategies is to include an "invisible" (transparent or matching the background color) 1pixel x 1pixel gif immediately before the content to be skipped and to anchor this image further down the page, past the unnecessary material. Although this image/link will probably go unnoticed by users deploying pointing devices and visual user-agents, users of screen readers will take note of this image and link. Like all images, the tag for this invisible gif should include alt text with something to the effect of "bypass navigation links" or "skip to main content."

The following example provides code for skipping over repetitive navigation:

<P><A href="#skipover"><IMG src="skipover.gif"
width="1" height="1" alt="skip to main content"> 
<a href="http://wwwnt.cwrl.utexas.edu/web/accessibility/guidelines/index.html">
</A></P>
<P><A href="http://www.lib.utexas.edu">Visit the Library</A></P>
<P><A href="http://www.utexas.edu">Home</A></P>

Using Keyboard Shortcuts

When software is designed to run on a system that has a keyboard, product functions shall be executable from a keyboard where the function itself or the result of performing a function can be discerned textually.

Unless you are developing your own software application, this requirement is probably not relevant for you. If you are developing software, make sure that there are keyboard shortcuts available for all the functions of your application and that these shortcuts are easy to find. The application should also be tab-navigable or implement some other keyboard navigation scheme. In other words, the user should be able to use and manipulate the software without using a mouse. The user should also be informed textually of the result of performing a function. For example, if he or she executes a "save changes" command with the keyboard, the resulting screen should include a textual message reading something like "document saved." This way, blind and visually impaired students using a voice application will be able to quickly verify that a given function has been performed. Other users will also benefit from such feedback.

If you are an instructor with keyboard-dependent students, make sure that the software used in your course is in compliance with this guideline.

For more info, search the NCAM (National Center for Accessible Media) website.