| a |
Potential |
Sound file must have a text transcript. |
17 |
| a |
Potential |
Link text is meaningful when read out of context. |
19 |
| a |
Potential |
The <code>title</code> attribute of all source <code>a</code> (anchor) elements describes the link destination. |
191 |
| a |
Potential |
All source anchors contain text that identifies the link destination. |
197 |
| a |
Potential |
Text alternative for multimedia file tells the same story and presents the same information as the multimedia file. |
240 |
| address |
Potential |
<code>address</code> of page author must be valid. |
144 |
| all elements |
Potential |
All <code>ondblclick</code> event handlers have corresponding keyboard-specific functions. |
103 |
| all elements |
Potential |
All <code>onmousemove</code> event handlers have corresponding keyboard-specific functions. |
105 |
| all elements |
Potential |
Change of context occurs only by user activation unless a warning is provided. |
274 |
| applet |
Potential |
<code>applet</code> should not use color alone. |
21 |
| applet |
Potential |
<code>applets</code> cause screen flicker. |
22 |
| applet |
Potential |
<code>applet</code> contains a text equivalent in the <code>alt</code> attribute of the <code>applet</code>. |
23 |
| applet |
Potential |
Text equivalents for <code>applet</code> must be updated if <code>applet</code> changes. |
24 |
| applet |
Potential |
<code>applet</code> contains a text equivalent in the body of the <code>applet</code>. |
25 |
| applet |
Potential |
<code>applet</code> user interface must be accessible. |
26 |
| applet |
Potential |
<code>applet</code> provides a keyboard mechanism to return focus to the parent window. |
258 |
| area |
Potential |
Alt text for all <code>area</code> elements identifies the link destination. |
65 |
| area |
Potential |
Alt text for all <code>area</code> elements contains all non decorative text in the image area. |
194 |
| blockquote |
Potential |
<code>blockquote</code> must not be used for indentation. |
100 |
| body |
Potential |
A "skip to content" link appears on all pages with blocks of material prior to the main document. |
28 |
| body |
Potential |
Abbreviations must be marked with <code>abbr</code> element. |
98 |
| body |
Potential |
Acronyms must be marked with <code>acronym</code> element. |
99 |
| body |
Potential |
Words and phrases not in the document's primary language are marked. |
110 |
| body |
Potential |
Use the <code>blockquote</code> element to mark up block quotations. |
131 |
| body |
Potential |
Provide a reference to a glossary. |
179 |
| body |
Potential |
Sites must have a site map. |
184 |
| body |
Potential |
The reading direction of all text is correctly marked. |
235 |
| body |
Potential |
Table markup is used for all tabular information. |
241 |
| body |
Potential |
All visual lists are marked. |
248 |
| body |
Potential |
Semantic markup is used to indicate emphasized or special text. |
249 |
| body |
Potential |
All text references do not use shape, size, or relative position alone. |
250 |
| body |
Potential |
Each section of content is marked with a <code>header</code> element. |
261 |
| body |
Potential |
All groups of links with a related purpose are marked. |
262 |
| body |
Potential |
The document contains a breadcrumb trail if it is part of a collection. |
266 |
| body |
Potential |
Unicode right-to-left marks or left-to-right marks are used whenever the HTML bidirectional algorithm produces undesirable results. |
270 |
| body |
Potential |
All changes in text direction are marked using the <code>dir</code> attribute. |
271 |
| body |
Potential |
Loading the web page does not cause a new window to open. |
275 |
| body |
Potential |
Repeated components appear in the same relative order each time they appear. |
276 |
| caption |
Potential |
Table captions identify the table. |
242 |
| embed |
Potential |
<code>embed</code> provides a keyboard mechanism to return focus to the parent window. |
260 |
| form |
Potential |
All <code>form</code> fields that are required are indicated to the user as required. |
246 |
| form |
Potential |
The tab order specified by <code>tabindex</code> attributes follows a logical order. |
265 |
| form |
Potential |
All form submission error messages identify any empty required fields. |
267 |
| form |
Potential |
All form submission error messages provide assistance in correcting the error. |
268 |
| form |
Potential |
Form submission data is presented to the user before final acceptance for all irreversable transactions. |
269 |
| form |
Potential |
Information deleted using a web page can be recovered. |
272 |
| frame |
Potential |
All <code>frame</code> <code>titles</code> identify the purpose or function of the <code>frame</code>. |
32 |
| frame |
Potential |
The source for each <code>frame</code> is accessible content. |
33 |
| frame |
Potential |
All <code>frame</code> <code>titles</code> do not contain placeholder text. |
202 |
| frameset |
Potential |
Repeated blocks of content appear in the same <code>frame</code> within the <code>frameset</code>. |
263 |
| h1 |
Potential |
All <code>h1</code> elements are not used for formatting. |
42 |
| h2 |
Potential |
All <code>h2</code> elements are not used for formatting. |
43 |
| h3 |
Potential |
All <code>h3</code> elements are not used for formatting. |
44 |
| h4 |
Potential |
All <code>h4</code> elements are not used for formatting. |
45 |
| h5 |
Potential |
All <code>h5</code> elements are not used for formatting. |
46 |
| h6 |
Potential |
All <code>h6</code> elements are not used for formatting. |
47 |
| head |
Potential |
Document uses <code>link</code> element to describe navigation if it is within a collection. |
147 |
| head |
Potential |
Document should use LINK for alternate content. |
148 |
| img |
Potential |
A long description is used for each <code>img</code> element that does not have Alt text conveying the same information as the image. |
8 |
| img |
Potential |
All <code>img</code> elements have associated images that do not flicker. |
10 |
| img |
Potential |
Alt text for all <code>img</code> elements contains all text in the image unless the image text is decorative or appears elsewhere in the document. |
11 |
| img |
Potential |
For all <code>img</code> elements, text does not refer to the image by color alone. |
14 |
| img |
Potential |
Alt text for all <code>img</code> elements used as source anchors identifies the destination of the link. |
15 |
| img |
Potential |
Alt text for all <code>img</code> elements is the empty string ("") if the image is decorative. |
16 |
| img |
Potential |
All active areas in all server-side image maps have duplicate text links in the document. |
132 |
| img |
Potential |
All <code>img</code> elements with images containing math expressions have equivalent MathML markup. |
135 |
| img |
Potential |
Alt text for all <code>img</code> elements that are not used as source anchors conveys the same information as the image. |
178 |
| img |
Potential |
Server-side image maps are not used except when image map regions cannot be defined using an available geometric shape. |
196 |
| img |
Potential |
<code>title</code> attribute for all <code>img</code> elements is absent or the empty string ("") if the image is decorative. |
239 |
| img |
Potential |
The luminosity contrast ratio between text and background color in all images is at least 5:1. |
251 |
| img |
Potential |
The luminosity contrast ratio between text and background color in all images is at least 10:1. |
253 |
| input |
Potential |
<code>input</code> should not use color alone. |
55 |
| input |
Potential |
Alt text for all <code>input</code> elements with a <code>type</code> attribute value of "image" identifies the purpose or function of the image. |
59 |
| input |
Potential |
All <code>input</code> elements, <code>type</code> of "password", have a label that is positioned close to the control. |
122 |
| input |
Potential |
All <code>input</code> elements, <code>type</code> of "checkbox", have a label that is positioned close to the control. |
123 |
| input |
Potential |
All <code>input</code> elements, <code>type</code> of "file", have a label that is positioned close to the control. |
124 |
| input |
Potential |
All <code>input</code> elements, <code>type</code> of "radio", have a label that is positioned close to the control. |
125 |
| input |
Potential |
Each label describes its asssociated <code>input</code> element. |
189 |
| input |
Potential |
Alt text for all <code>input</code> elements with a <code>type</code> attribute value of "image" contains all non decorative text in the image. |
193 |
| input |
Potential |
All <code>input</code> elements, <code>type</code> of "file", have a <code>label</code> that describes the purpose or function of the control. |
205 |
| input |
Potential |
All <code>input</code> elements, <code>type</code> of "text", have a label that is positioned close to the control. |
211 |
| input |
Potential |
All <code>input</code> elements, <code>type</code> of "password", have a <code>label</code> that describes the purpose or function of the control. |
217 |
| input |
Potential |
All <code>input</code> elements, <code>type</code> of "text", have a <code>label</code> that describes the purpose or function of the control. |
218 |
| input |
Potential |
All <code>input</code> elements, <code>type</code> of "checkbox", have a <code>label</code> that describes the purpose or function of the control. |
219 |
| input |
Potential |
All <code>input</code> elements, <code>type</code> of "radio", have a <code>label</code> that describes the purpose or function of the control. |
220 |
| legend |
Potential |
<code>legend</code> text describes the group of choices. |
198 |
| link |
Potential |
Document must be readable when stylesheets are not applied. |
97 |
| noembed |
Potential |
<code>noembed</code> must have equivalent content. |
164 |
| noframes |
Potential |
NOFRAMES section must contain text equivalent of FRAMES section. |
36 |
| object |
Potential |
All <code>objects</code> do not flicker. |
30 |
| object |
Potential |
<code>object</code> must not use color alone. |
73 |
| object |
Potential |
Text equivalents for <code>object</code> should be updated if <code>object</code> changes - (codebase). |
74 |
| object |
Potential |
Content must be usable when <code>object</code> are disabled. |
75 |
| object |
Potential |
<code>object</code> user interface must be accessible - (codebase). |
76 |
| object |
Potential |
<code>object</code> link to multimedia file must have text transcript. |
77 |
| object |
Potential |
All <code>objects</code> contain a text equivalent of the <code>object</code>. |
80 |
| object |
Potential |
Text equivalents for <code>object</code> should be updated if <code>object</code> changes - (classid). |
127 |
| object |
Potential |
Content must be usable when <code>object</code>s are disabled. |
128 |
| object |
Potential |
<code>object</code> user interface must be accessible - (classid). |
129 |
| object |
Potential |
<code>object</code> link to multimedia file require equivalent alternatives (e.g., captions or auditory descriptions of the visual track). |
146 |
| object |
Potential |
<code>object</code> may require a long description. |
160 |
| object |
Potential |
<code>object</code> provides a keyboard mechanism to return focus to the parent window. |
259 |
| ol |
Potential |
Link group <code>title</code> must describe the link group. |
157 |
| ol |
Potential |
CSS must be used to hide link groups. |
158 |
| pre |
Potential |
<code>pre</code> element should not be used to create tabular layout. |
154 |
| script |
Potential |
Color alone should not be used in the <code>script</code>. |
86 |
| script |
Potential |
<code>script</code> should not cause screen flicker. |
87 |
| script |
Potential |
Content must be accessible when <code>script</code> is disabled. |
88 |
| script |
Potential |
User interface for <code>script</code> must be accessible. |
89 |
| select |
Potential |
All <code>select</code> elements have a label that is positioned close to the control. |
209 |
| select |
Potential |
All <code>select</code> elements have a label that describes the purpose or function of the control. |
210 |
| table |
Potential |
All complex data tables have a summary. |
111 |
| table |
Potential |
All layout <code>tables</code> make sense when linearized. |
133 |
| table |
Potential |
All data tables contain <code>th</code> elements. |
136 |
| table |
Potential |
All layout tables do not contain <code>th</code> elements. |
137 |
| table |
Potential |
All data tables contain a <code>caption</code> unless the table is identified within the document. |
151 |
| table |
Potential |
All data table summaries describe navigation and structure of the table. |
203 |
| table |
Potential |
Use <code>thead</code> to group repeated table headers, <code>tfoot</code> for repeated table footers, and <code>tbody</code> for other groups of rows. |
230 |
| table |
Potential |
Use <code>colgroup</code> and <code>col</code> elements to group columns. |
231 |
| textarea |
Potential |
All <code>textarea</code> elements have a label that is positioned close to control. |
96 |
| textarea |
Potential |
All <code>textarea</code> elements have a <code>label</code> that describes the purpose or function of the control. |
214 |
| title |
Potential |
<code>title</code> describes the document. |
54 |
