|
|
Accessibility Resources:
W3C Content Accessibility Guidelines 1.0
508 requirements
Federal Web Design and Usability Guidelines
Usability.gov (Links to Tools)
Summary: Text Equivalents - Provide a text equivalent for every non-text element (e.g., via "alt", "longdesc", or in element content). This includes: images, graphical representations of text (including symbols), image map regions, animations (e.g., animated GIFs), applets and programmatic objects, ascii art, frames, scripts, images used as list bullets, spacers, graphical buttons, sounds (played with or without user interaction), stand-alone audio files, audio tracks of video, and video.
- Provide redundant text links for each active region of a server-side image map.
- Provide an auditory description of the important information of the visual track of a multimedia presentation
- For any time-based multimedia presentation (e.g., a movie or animation), synchronize equivalent alternatives (e.g., captions or auditory descriptions of the visual track) with the presentation. |
Use of Color - Ensure that all information conveyed with color is also available without color |
Natural Language - Clearly identify changes in the natural language of a document's text and any text equivalents (e.g., captions). |
Create tables that transform gracefully - For data tables, identify row and column headers
- For data tables that have two or more logical levels of row or column headers, use markup to associate data cells and header cells. |
Ensure that pages are accessible even when newer technologies are not supported or are turned off. - Organize documents so they may be read without style sheets
- Ensure that equivalents for dynamic content are updated when the dynamic content changes
- Ensure that pages are usable when scripts, applets, or other programmatic objects are turned off or not supported. If this is not possible, provide equivalent information on an alternative accessible page. |
Ensure that moving, blinking, scrolling, or auto-updating objects or pages may be paused or stopped
- avoid causing the screen to flicker
|
When an embedded object has its "own interface", the interface -- like the interface to the browser itself -- must be accessible. If the interface of the embedded object cannot be made accessible, an alternative accessible solution must be provided. |
Use features that enable activation of page elements via a variety of input devices
- Provide client-side image maps instead of server-side image maps except where the regions cannot be defined with an available geometric shape.
|
Alternative Pages
If, after best efforts, you cannot create an accessible page, provide a link to an alternative page that uses W3C technologies, is accessible, has equivalent information (or functionality), and is updated as often as the inaccessible (original) page.
|
Provide context and orientation information Grouping elements and providing contextual information about the relationships between elements can be useful for all users. Complex relationships between parts of a page may be difficult for people with cognitive disabilities and people with visual disabilities to interpret.
- Title each frame to facilitate frame identification and navigation
|
Use the clearest and simplest language appropriate for a site's content.
|
Additional 508 requirements
- When electronic forms are designed to be completed on-line, the form shall allow people using assertive technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues.
- A method shall be provided that permits users to skip repetitive navigation links.
- When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required.
|
Submit page information for a load test of your most frequently used pages and applications |
|