Web developers must satisfy this item. These guidelines
represent more complex accessibility features that must be addressed
in web page design. Generally, these items would be addressed after
satisfying Priority 1 items.
Priority 2 Item 1
When an appropriate markup language exists, use markup rather
than graphics to convey information. For example, use MathML to mark
up mathematical equations instead of using graphics to represent symbols.
Priority 2 Item 2
Create pages that use the transitional or the strict document
type declaration (e.g., <!DOCTYPE HTML PUBLIC "-//W3C//DTD
HTML 4.01 Transitional//EN"> or <!DOCTYPE HTML PUBLIC "-//W3C//DTD
HTML 4.01//EN">) and include the appropriate declaration as
the first line of every HTML page.
Priority 2 Item 3
Use style sheets to control layout and presentation.
Priority 2 Item 4
Use relative rather than absolute units of measure (e.g.,
for margins, font sizes, borders, etc.).
Priority 2 Item 5
Use navigation mechanisms in a consistent manner.
Priority 2 Item 6
Specify the expansion of each abbreviation or acronym in
a document where it first occurs. Providing the expansion in the main
body of the document also helps document usability.
Priority 2 Item 7
Do not cause pop-ups or other windows to appear and do not
change the current window without informing the user. If a new window
is absolutely necessary, provide an alternative, accessible means
for conveying or gathering information.
Priority 2 Item 8
Provide metadata for every page.
Priority 2 Item 9
Provide information about the general layout of a site (e.g.,
a site map or table of contents).
Priority 2 Item 10
Do not use tables for layout unless the table makes sense
when linearized.
Priority 2 Item 11
Create a logical tab order through links, form controls,
and objects.
Priority 2 Item 12
Describe the purpose of frames and how frames relate to each
other if it is not obvious by frame titles alone.
Priority 2 Item 13
Until user agents provide the ability to stop auto-redirect,
do not use markup to redirect pages automatically. Instead, configure
the server to perform redirects. If necessary to re-direct a page
and configuring the server is not possible, label the action and allow
the user to invoke the link to the new page.