Accessibility problems
These problems are due to failures to meet the accessibility (WCAG 1.0 or US508) guidelines:
| A | A | A |
| E800 | [WAI 1.1 (A), US-508-a] Provide a text equivalent for non-text items using 'alt' | When using <img>, specify a short text equivalent with the 'alt' attribute. See http://www.w3.org/TR/WCAG10-HTML-TECHS/#image-text-equivalent (displayed in new window), and http://www.section508.gov/index.cfm?FuseAction=Content&ID=12#Web (a) (displayed in new window). |
| E801 | [WAI 6.3 (A)] Put some content between the start and end tag to provide a text equivalent for non-text items | When using <object> or <applet> you should put some content between the start and end tag to a provide a text alternative. With the <applet> tag this is in addition to any 'alt' text you may have defined. See http://www.w3.org/TR/WCAG10-HTML-TECHS/#applet-text-equivalent (displayed in new window). |
| E802 | [WAI 1.1 (A)] The 'alt' attribute is for short descriptions. Use 'longdesc' for long ones | The 'alt' text you specified was at least 150 characters long. For long descriptions you should use the 'longdesc' attribute. See http://www.w3.org/TR/WCAG10-HTML-TECHS/#long-descriptions (displayed in new window). |
| E803 | [WAI 1.1 (A)] The 'alt' attribute is for short descriptions. Use a descriptive link for long ones | The 'alt' text you specified was at least 150 characters long. For long descriptions (when 'longdesc' is not supported) you should use a separate description link. See http://www.w3.org/TR/WCAG10-HTML-TECHS/#long-descriptions (displayed in new window). |
| E804 | [WAI 6.2 (A)] Do not use images as frame targets, always point to web pages | Rather than point directly to an image, embed the image in a web page. See http://www.w3.org/TR/WCAG10-HTML-TECHS/#frame-has-html-src (displayed in new window). |
| E805 | [WAI 12.1 (A), US-508-i] Add a 'title' attribute to facilitate identification and navigation | Title each frame to facilitate frame identification and navigation. See http://www.w3.org/TR/WCAG10-HTML-TECHS/#frame-names (displayed in new window), and http://www.section508.gov/index.cfm?FuseAction=Content&ID=12#Web (i) (displayed in new window). |
| E806 | [WAI 1.1 (A), US-508-a] Image buttons should have 'alt' text that describes them | When using image buttons, specify a short text equivalent with the 'alt' attribute. See http://www.w3.org/TR/WCAG10-HTML-TECHS/#forms-graphical-buttons (displayed in new window), and http://www.section508.gov/index.cfm?FuseAction=Content&ID=12#Web (a) (displayed in new window). |
| E807 | [WAI 1.1 (A), US-508-a] Provide a text equivalent for non-text items using 'alt' | When using <applet>, specify a short text equivalent with the 'alt' attribute. See http://www.w3.org/TR/WCAG10-HTML-TECHS/#applet-text-equivalent (displayed in new window), and http://www.section508.gov/index.cfm?FuseAction=Content&ID=12#Web (a) (displayed in new window). |
| E808 | [WAI 1.1 (A), US-508-a] Provide a text equivalent for non-text items using 'alt' | When using <area>, specify a short text equivalent with the 'alt' attribute. See http://www.w3.org/TR/WCAG10-HTML-TECHS/#client-side-text-equivs (displayed in new window), and http://www.section508.gov/index.cfm?FuseAction=Content&ID=12#Web (a) (displayed in new window). |
| W800 | [WAI 6.3 (A), US-508-l] Consider providing a <noscript> alternative after each <script> tag | This warning appears if you have defined a <script> and there is no <noscript> alternative following it. You should ensure that pages are usable when scripts are turned off or not supported. Using <noscript> is a common way of doing this, but if you have used an alternative mechanism you can ignore this warning. See http://www.w3.org/TR/WCAG10/#tech-scripts (displayed in new window), and http://www.section508.gov/index.cfm?FuseAction=Content&ID=12#Web (l) (displayed in new window). |
| W801 | [WAI 9.1 (A), US-508-f] If possible use a client-side instead of a server-side image map | Unless you are using regions that cannot be defined with an available geometric shape, you should use a client-side instead of a server-side image map. If you have to use a client-side map ensure that there is an accessible alternative available. See http://www.w3.org/TR/WCAG10/#tech-client-side-maps (displayed in new window), and http://www.section508.gov/index.cfm?FuseAction=Content&ID=12#Web (f) (displayed in new window). |
| W802 | [WAI 1.1 (A), US-508-a] Is the 'alt' text deliberately empty? | When using <img>, it is valid to have an empty 'alt' attribute for images that have no content; such as spacers and parts of larger images that have been broken up or used for other layout purposes. You may wish to check that in this case the alt-text has not simply been forgotten, in which case it would be a [WAI 1.1 (A), US-508-a] error. |
| AA | AA | AA |
| E820 | [WAI 3.2 (AA)] Add a <!DOCTYPE> tag to the page | Validating to a published formal grammar and declaring that validation at the beginning of a document lets the user know that the structure of the document is sound. See http://www.w3.org/TR/WCAG10-HTML-TECHS/#doctype (displayed in new window). |
| E821 | [WAI 3.3 (AA)] Use style sheets for presentation effects, use <em> or <strong> for emphasis | Validating to a published formal grammar and declaring that validation at the beginning of a document lets the user know that the structure of the document is sound. See http://www.w3.org/TR/WCAG10-HTML-TECHS/#doctype (displayed in new window). |
| E822 | [WAI 3.4 (AA)] Use relative, rather than absolute units | Using relative units helps the page to be rendered correctly at different resolutions and people with sight difficulties often 'zoom in' to pages to read them. See http://www.w3.org/TR/WCAG10/#tech-relative-units (displayed in new window). |
| E823 | [WAI 3.5 (AA)] Nest headings properly (H1 > H2 > H3) | Heading elements must be ordered properly. For example, in HTML H2 elements should follow H1 elements, H3 elements should follow H2 elements, etc. Developers should not skip levels (e.g., H1 directly to H3). Do not use headings to create font effects. See http://www.w3.org/TR/WCAG10-HTML-TECHS/#document-headers (displayed in new window). |
| E825 | [WAI 6.5 (AA)] Provide a <noframes> tag for user agents that do not support frames | A page which uses a frameset and which does not have a <noframes> alternative may be entirely unusable for some people. See http://www.w3.org/TR/WCAG10-HTML-TECHS/#noframes (displayed in new window). |
| E826 | [WAI 7.2 (AA)] Do not use this tag. Consider <em> or using CSS instead | Until user agents allow users to control blinking, avoid causing content to blink. See http://www.w3.org/TR/WCAG10-HTML-TECHS/#scripts-movement-blinking (displayed in new window). |
| E827 | [WAI 7.3 (AA)] Do not use this tag. Consider <em> or using CSS instead | Until user agents allow users to freeze moving content, avoid movement in pages. See http://www.w3.org/TR/WCAG10-CSS-TECHS/#style-text (displayed in new window). |
| E828 | [WAI 7.4 (AA)] Do not use 'refresh' to refresh or redirect pages | Until user agents provide the ability to stop the refresh, do not create periodically auto-refreshing pages. See http://www.w3.org/TR/WCAG10-CORE-TECHS/#auto-page-refresh (displayed in new window). |
| E829 | [WAI 9.3 (AA)] Do not use 'ondblclick' or 'onmousemove' as these do not have keyboard equivalents | For scripts, specify logical event handlers rather than device-dependent event handlers. ee http://www.w3.org/TR/WCAG10-HTML-TECHS/#directly-accessible-scripts (displayed in new window). |
| E830 | [WAI 10.1 (AA)] Do not use '_blank' targets with frames | Until user agents allow users to turn off spawned windows, do not cause pop-ups or other windows to appear. See http://www.w3.org/TR/WCAG10-HTML-TECHS/#no-new-windows (displayed in new window). |
| E831 | [WAI 12.4 (AA), US-508-n] Associate form controls with <label> tags using the 'id' attribute | Associate labels explicitly with their controls. See http://www.w3.org/TR/WCAG10-HTML-TECHS/#forms-labels (displayed in new window), and http://www.section508.gov/index.cfm?FuseAction=Content&ID=12#Web (n) (displayed in new window). |
| E831 | [WAI 12.4 (AA), US-508-n] No matching <label> tag could be found, or label is empty | Associate labels explicitly with their controls. See http://www.w3.org/TR/WCAG10-HTML-TECHS/#forms-labels (displayed in new window), and http://www.section508.gov/index.cfm?FuseAction=Content&ID=12#Web (n) (displayed in new window). |
| E831 | [WAI 12.4 (AA), US-508-n] Associate <label> tags with form controls using the 'for' attribute | Associate labels explicitly with their controls. See http://www.w3.org/TR/WCAG10-HTML-TECHS/#forms-labels (displayed in new window), and http://www.section508.gov/index.cfm?FuseAction=Content&ID=12#Web (n) (displayed in new window). |
| E831 | [WAI 12.4 (AA), US-508-n] Label text is missing | Associate labels explicitly with their controls. See http://www.w3.org/TR/WCAG10-HTML-TECHS/#forms-labels (displayed in new window), and http://www.section508.gov/index.cfm?FuseAction=Content&ID=12#Web (n) (displayed in new window). |
| E831 | [WAI 12.4 (AA), US-508-n] Associate labels with just one form control | Associate labels explicitly with their controls. See http://www.w3.org/TR/WCAG10-HTML-TECHS/#forms-labels (displayed in new window), and http://www.section508.gov/index.cfm?FuseAction=Content&ID=12#Web (n) (displayed in new window). |
| E833 | [WAI 13.1 (AA)] Clearly identify the target of each link with some text | Use text or an image to identify the target of links. See http://www.w3.org/TR/WCAG10-HTML-TECHS/#link-text (displayed in new window). |
| E834 | [WAI 13.1 (AA)] Link text should make sense when read out of context | Don't use link text such as 'click here'. See http://www.w3.org/TR/WCAG10-HTML-TECHS/#link-text (displayed in new window). |
| E835 | [WAI 13.1 (AA)] Use the 'title' attribute to distinguish between different links that use the same link text | This error appears when you have not used the 'title' attribute and have different links with the same link text. See http://www.w3.org/TR/WCAG10-HTML-TECHS/#link-text (displayed in new window). |
| E836 | [WAI 13.1 (AA)] Use different values for 'title' attributes with links that use the same link text | This error appears when you have used the same 'title' attribute for different links with the same link text. See http://www.w3.org/TR/WCAG10-HTML-TECHS/#link-text (displayed in new window). |
| E837 | [WAI 13.2 (AA)] Add a <title> tag to the page to describe it | You should provide metadata, such as the <title> tag, to add semantic information to pages and sites. See ttp://www.w3.org/TR/WCAG10-HTML-TECHS/#doc-title (displayed in new window). |
| W820 | [WAI 3.6 (AA)] Do not use this tag for layout | This warning appears if you have defined a <ul>, <ol>, or <dl> tag, without any list items within it. The assumption is that you are using these tags purely for layout purposes. If so see the following for help: http://www.w3.org/TR/WCAG10-HTML-TECHS/#identify-primary-lang (displayed in new window). |
| AAA | AAA | AAA |
| E854 | [WAI 4.3 (AAA)] Use the 'lang' or 'xml:lang' attribute to denote the primary language of the document | You should always identify the primary natural language of a document. See http://www.w3.org/TR/WCAG10-HTML-TECHS/#identify-primary-lang (displayed in new window). |
top