Guidelines for Web Accessibility - Priority 1
Following priority 1 will make it possible for all groups to use the site. For some groups, this is the basic requirement to enable them to access the information.
- 1.1 Provide a text equivalent for every non-text element
-
Explanation and help for non-text elements
- 1.2 Ensure that information does not rely on colour perception
-
Explanation and help for information conveyed with colour
- 1.3 Avoid causing the screen to flicker
-
Explanation and help for flickering and screen flicker
- 1.4 Provide an auditory description of the visual information in multimedia presentations
-
Explanation and help for multimedia and auditory description
- 1.5 For multimedia, ensure that timing of alternative descriptions is synchronised with the presentation
-
Explanation and help for multimedia and synchronised equivalent alternatives
- 1.6 Use the clearest and simplest language appropriate
-
Explanation and help for clear and simple language
- 1.7 Identify language changes in text
-
Explanation and help for natural language
- 1.8 Ensure that equivalents for dynamic content are updated when the dynamic content changes
-
Explanation and help for dynamic content equivalents
- 1.9 For data tables, identify row and column headers
-
Explanation and help for data tables with row and column headers
- 1.10 For complex data tables, use mark-up to associate data cells and header cells
-
Explanation and help for data tables with logical levels
- 1.11 Add titles to frames
-
Explanation and help for frames
- 1.12 Ensure that documents can be read without style sheets
-
Explanation and help for ensuring that documents can be read without style sheets
- 1.13 Provide text links to emulate server-side image maps
-
Explanation and help for images and image maps
- 1.14 Use client-side image maps rather than server-side image maps where possible
-
Explanation and help for client-side and server-side image maps
- 1.15 Ensure that scripts and applets that provide the only source of important functionality are directly accessible or compatible with assistive technologies
-
Explanation and help for Ensuring scripts and applets are accessible
- 1.16 Ensure that pages are usable without support for scripts, applets, or other programmatic objects
-
Explanation and help for ensuring pages are usable without programmatic objects
- 1.17 If you cannot make a page accessible, provide an equivalent accessible page
-
Explanation and help for alternative pages
