Accessibility :: Web Accessibility Criteria

Printer-friendly versionSend to friendPDF version

Below is a list of conditions every Humboldt State University website is required to meet in order to pass accessibility testing. If, after best efforts, any University website developer cannot create an accessible page, a link must be provided to an alternative page that is accessible, has equivalent information or functionality, and is updated as often as the inaccessible (original) page.

Text equivalency:

  • Provide a text equivalent for every non-text element using alt-text or other coding technique. Non-text elements are images, graphical representations of text (including symbols), image map regions, animations such as animated GIFs, applets and programmatic objects, ASCII art, frames, scripts, images used as list bullets, spacers, graphical buttons, sounds that can be played with or without user interaction, stand-alone audio files, audio tracks related to video, and video.
  • Until user agents can automatically read aloud the text equivalent of a video track, provide an audio description of the important information contained in the video track of a multimedia presentation.

Screen display:

  • Ensure that all information conveyed with color can also be understood without color, for example using context or markup.
  • Until user agents allow users to control flickering, avoid causing the screen to flicker.

Change management:

  • Clearly identify changes in the natural language of a document's text and any text equivalents such as captions.
  • Ensure that equivalents for dynamic content are updated whenever the dynamic content changes.

Document content and organization:

  • Organize documents so they may be read without style sheets. For example, it must still be possible to read an HTML document if it is rendered without associated style sheets.
  • Use the clearest and simplest language appropriate for a site's content.
  • Ensure that pages are usable when scripts, applets, or other programmatic objects are turned off or not supported. If this is not possible, provide the equivalent information on an alternative accessible page.
  • For any time-based multimedia presentation such as a movie or animation, synchronize equivalent alternatives including captions or audio descriptions of the video track with the presentation.

Server-side image maps:

  • Provide redundant text links for each active region of a server-side image map.
  • Provide client-side image maps instead of server-side image maps except where the regions cannot be defined with an available geometric shape.

Data tables:

  • Identify row and column headers.
  • For tables with two or more logical levels of row or column headers, use markup to associate data cells and header cells.

Navigation:

  • Title each frame to facilitate frame identification and navigation.
  • 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 that plug-in or applet.
  • Users must be able to skip repetitive navigation links.

Forms:

  • Forms designed to be completed on-line must allow those using assistive technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues.

Related Topics

Accessibility, Web
feedback