Kansas WCAG :: Priority 2 Index

Web developers may satisfy this item. These guidelines represent accessibility features that offer the broadest level of accessibility to web pages.

Priority 3 Item 1
Identify the primary natural language of a document.

Priority 3 Item 2
Provide keyboard shortcuts to important links (including those in client-side image maps), form controls, and groups of form controls.

Priority 3 Item 3
Until user agents (including assistive technologies) render adjacent links distinctly, include non-link, printable characters (surrounded by spaces) between adjacent links.

Priority 3 Item 4
Provide information so that users may receive documents according to their preferences (e.g., language, content type, etc.)

Priority 3 Item 5
Provide a group of navigation links to highlight and give access to the navigation mechanism.

Priority 3 Item 6
If search functions are provided, enable different types of searches for different skill levels and preferences.

Priority 3 Item 7
Place distinguishing information at the beginning of headings, paragraphs, lists, etc.

Priority 3 Item 8
Provide information about document collections (i.e., documents comprising multiple pages.).

Priority 3 Item 9
If ASCII art cannot be avoided, provide a means to skip over multi-line ASCII art.

Priority 3 Item 10
Provide terse substitutes for header labels with the abbr attribute on th. These will be particularly useful for future speaking technologies that can read row and column labels for each cell. Abbreviations cut down on repetition and reading time.

Priority 3 Item 11
Supplement text with graphic or auditory presentations where they will facilitate comprehension of the page.

[ Return to the Top of the page ]