HTML Tidy Accessibility Checker

(Download all testfiles here)

Accessibility Checks Performed:

Error number [1.1.1.1] - Priority 1
All images -- including transparent gifs -- must have "alt" text. Alternate text should be concise (i.e. 10-12 words maximum). For transparent images and spacers, use alt="" (NULL), alt=" " (spaces are acceptable), or alt="blank". Any words depicted in the image should also appear in the "alt" text description.

Testfile 1.1.1.f1: <img> missing "alt" text
View testfile source
Testfile

Warning number [1.1.1.2] - Priority 1
All images require text equivalents but "alt" text must also meet certain criteria otherwise it may be considered suspicious. For example, "alt" text may be deemed unacceptable if filenames and/or image file extensions (i.e. alt="xmas_tree.gif") are used in place of an actual text equivalent.

Testfile 1.1.1.f2: suspicious "alt" text (filename)
View testfile source
Testfile

Warning number [1.1.1.3] - Priority 1
All images require text equivalents but "alt" text must also meet certain criteria otherwise it may be considered suspicious. For example, "alt" text may be considered unacceptable if it is used to convey file size information (i.e. alt="650 bytes").

Testfile 1.1.1.f3: suspicious "alt" text (file size)
View testfile source
Testfile

Warning number [1.1.1.4] - Priority 1
All images require text equivalents but "alt" text must also meet certain criteria otherwise it may be considered suspicious. For example, using placeholder text (i.e. alt="image goes here") in place of an actual text equivalent is considered unacceptable.

Testfile 1.1.1.f4: suspicious "alt" text (placeholder)
View testfile source
Testfile

Warning number [1.1.1.10] - Priority 1
All images require text equivalents but "alt" text must also meet certain criteria otherwise it may be considered suspicious. If "alt" text exceeds 150 characters, use the "longdesc" attribute along with a descriptive link (d-link) to describe the image.

Testfile 1.1.1.f10: suspicious "alt" text (too long)
View testfile source
Testfile

Warning number [1.1.1.11] - Priority 1
All images require text equivalents including those used to identify items in a list. If an image is used as a bullet, it should include the following "alt" text: alt="*" or alt="bullet".

Testfile 1.1.1.f11: <img> missing "alt" text (bullet)
View testfile source
Testfile

Warning number [1.1.1.12] - Priority 1
All images require text equivalents including those used to indicate breaks within a web page. If an image is used as a horizontal rule, it should include the following "alt" text: alt="*" or alt="horizontal rule".

Testfile 1.1.1.f12: <img> missing "alt" text (horizontal rule)
View testfile source
Testfile

Warning number [1.1.2.1] - Priority 1
If "alt" text cannot adequately describe an image's function or purpose, provide access to a more complete description via the "longdesc" attribute. Note you must also add a d-link (descriptive link) because many current browsers do not support the "longdesc" attribute. The advantage of including "longdesc" in current web documents is that the description will remain accessible when newer browsers deprecate d-links.

Testfile 1.1.2.f1: <img> missing "longdesc" and d-link.
View testfile source
Testfile

Warning number [1.1.2.2] - Priority 1
If "alt" text cannot adequately explain an image's function or purpose you must provide access to a more complete description. Because many current browsers do not support the "longdesc" attribute, including a d-link (descriptive link) ensures longer descriptions are accessible to all users.

Testfile 1.1.2.f2: <img> missing "longdesc" and d-link.
View testfile source
Testfile

Warning number [1.1.2.3] - Priority 1
If "alt" text cannot adequately describe an image's function or purpose, provide access to a more complete description via the "longdesc" attribute. Note you must also add a d-link (descriptive link) because many current browsers do not support the "longdesc" attribute. The advantage of including "longdesc" in current web documents is that the description will remain accessible when newer browsers deprecate d-links.

Testfile 1.1.2.f3: <img> missing "longdesc" and d-link.
View testfile source
Testfile

Warning number [1.1.3.1] - Priority 1
If an image is used as a button, it must include "alt" text. Do not describe the image itself but rather the destination or purpose of the link.

Testfile 1.1.3.f1: <img> (button) missing "alt" text.
View testfile source
Testfile

Error number [1.1.4.1] - Priority 1
Applets must include alternate content to ensure the information is available to those who cannot access graphics. The alternate content should contain essentially the same information or serve a similar purpose as the applet itself. It may even be useful to describe the visual content or the sound effects accompanying the applet. You can either provide a link to a description or insert it directly into the document.

Testfile 1.1.4.f1: <applet> missing alternate content.
View testfile source
Testfile

Error number [1.1.5.1] - Priority 1
Objects must include alternate content to ensure that the information is available to those who cannot access graphics. The alternate content should contain essentially the same information or serve a similar purpose to the object itself. You can either provide a link to a description or insert it directly into the document.

Testfile 1.1.5.f1: <object> missing alternate content.
View testfile source
Testfile

Error number [1.1.6.1] - Priority 1
Web documents that contain audio files must also provide a text transcript that describes the sound or reproduces the content contained in the file. If the audio file contains an extensive amount of information, establish a link within the document that points to a complete text transcript of the sound file. This technique is suitable for reproducing song lyrics and excerpts from speeches.

Testfile 1.1.6.f1: audio missing text transcript (wav)
View testfile source
Testfile

Error number [1.1.6.2] - Priority 1
Web documents that contain audio files must also provide a text transcript that describes the sound or reproduces the content contained in the file. If the audio file contains an extensive amount of information, establish a link within the document that points to a complete text transcript of the sound file. This technique is suitable for reproducing song lyrics and excerpts from speeches.

Testfile 1.1.6.f2: audio missing text transcript (au)
View testfile source
Testfile

Error number [1.1.6.3] - Priority 1
Web documents that contain audio files must also provide a text transcript that describes the sound or reproduces the content contained in the file. If the audio file contains an extensive amount of information, establish a link within the document that points to a complete text transcript of the sound file. This technique is suitable for reproducing song lyrics and excerpts from speeches.

Testfile 1.1.6.f3: audio missing text transcript (aiff)
View testfile source
Testfile

Error number [1.1.6.4] - Priority 1
Web documents that contain audio files must also provide a text transcript that describes the sound or reproduces the content contained in the file. If the audio file contains an extensive amount of information, establish a link within the document that points to a complete text transcript of the sound file. This technique is suitable for reproducing song lyrics and excerpts from speeches.

Testfile 1.1.6.f4: audio missing text transcript (snd)
View testfile source
Testfile

Error number [1.1.6.5] - Priority 1
Web documents that contain audio files must also provide a text transcript that describes the sound or reproduces the content contained in the file. If the audio file contains an extensive amount of information, establish a link within the document that points to a complete text transcript of the sound file. This technique is suitable for reproducing song lyrics and excerpts from speeches.

Testfile 1.1.6.f5: audio missing text transcript (ra)
View testfile source
Testfile

Error number [1.1.6.6] - Priority 1
Web documents that contain audio files must also provide a text transcript that describes the sound or reproduces the content contained in the file. If the audio file contains an extensive amount of information, establish a link within the document that points to a complete text transcript of the sound file. This technique is suitable for reproducing song lyrics and excerpts from speeches.

Testfile 1.1.6.f6: audio missing text transcript (rm)
View testfile source
Testfile

Warning number [1.1.8.1] - Priority 1
If a frame cannot be adequately described in its title, include the "longdesc" attribute within the frame element to provide a link to additional information. The "longdesc" attribute can also be useful in helping to explain relationships between frames.

Testfile 1.1.8.f1: <frame> may require "longdesc"
View testfile source
Testfile

Error number [1.1.9.1] - Priority 1
You must include "alt" text for each <area> element within an image map. The "alt" text should indicate the destination of each link rather than provide a description of the image itself.

Testfile 1.1.9.f1: <area> missing "alt" text.
View testfile source
Testfile

Error number [1.1.10.1] - Priority 1
A text equivalent must be provided for all scripts. Adding the <noscript> element to documents that include scripts ensures the information will be available in a text format if the client's browser does not support scripts.

Testfile 1.1.10.f1: <script> missing <noscript> section.
View testfile source
Testfile

Error number [1.1.12.1] - Priority 1
Replace ascii art (illustrations created using keyboard symbols and characters) with actual images whenever possible. If the ascii artwork cannot be replaced, you must include an equivalent description to ensure the information is accessible to users who rely on audio-based and text-only browsers. A text equivalent is not required if the ascii image is explained in the document's content.

Testfile 1.1.12.f1: ascii art requires description
View testfile source
Testfile

Error number [1.2.1.1] - Priority 1
All server-side image maps must include redundant text links. Alt text is not available with server-side image maps unless redundant text links have been created. Redundant text links should describe the destination of each link (i.e. Home Page, Search Engine, etc.) rather than the actual image. If the map itself requires a explanation, use the "longdesc" attribute (and accompanying d-link) to provide a more detailed description.

Testfile 1.2.1.f1: image map (server-side) requires text links.
View testfile source
Testfile

Error number [1.4.1.1] - Priority 1
All time-based multimedia presentations (i.e. movie clips, animations, slide shows) must include synchronized text equivalents for both the audio and visual content. If captions and visual descriptions are not synchronized with the main presentation, content can become confusing and potentially meaningless.

Testfile 1.4.1.f1: multimedia requires synchronized text equivalents.
View testfile source
Testfile

Warning number [1.5.1.1] - Priority 3
Client-side image maps also include redundant text links to ensure users will be able to navigate through a site. When creating redundant text links for image maps, create text that identifies the destination of each link (i.e. Home Page, Search Engine, etc.)

Testfile 1.5.1.f1: image map (client-side) missing text links.
View testfile source
Testfile

Warning number [2.1.1.1] - Priority 1
When information is conveyed using color, that information must also be made available through alternate means either through the context in which the information is presented or its markup properties. Ensure there is sufficient contrast between images and the background color.

Testfile 2.1.1.1: ensure information not conveyed through color alone (image).
View testfile source
Testfile

Warning number [2.1.1.2] - Priority 1
When information is conveyed using color, that information must also be made available through alternate means either through the context in which the information is presented or its markup properties. Ensure there is sufficient contrast between images and the background color.

Testfile 2.1.1.2: ensure information not conveyed through color alone (applet).
View testfile source
Testfile

Warning number [2.1.1.3] - Priority 1
When information is conveyed using color, that information must also be made available through alternate means either through the context in which the information is presented or its markup properties. Ensure there is sufficient contrast between images and the background color.

Testfile 2.1.1.3: ensure information not conveyed through color alone (object).
View testfile source
Testfile

Warning number [2.1.1.4] - Priority 1
When information is conveyed using color, that information must also be made available through alternate means either through the context in which the information is presented or its markup properties. Ensure there is sufficient contrast between images and the background color.

Testfile 2.1.1.4: ensure information not conveyed through color alone (script).
View testfile source
Testfile

Warning number [2.1.1.5] - Priority 1
When information is conveyed using color, that information must also be made available through alternate means either through the context in which the information is presented or its markup properties. Ensure there is sufficient contrast between images and the background color.

Testfile 2.1.1.5: ensure information not conveyed through color alone (input).
View testfile source
Testfile

Warning number [2.2.1.1] - Priority 3
Ensure there is sufficient contrast between text and background colors for individuals with a color deficiency.

Testfile 2.2.1.1: poor color contrast (text).
View testfile source
Testfile

Warning number [2.2.1.2] - Priority 3
Ensure there is sufficient contrast between text and background colors for individuals with a color deficiency.

Testfile 2.2.1.2: poor color contrast (link).
View testfile source
Testfile

Warning number [2.2.1.3] - Priority 3
Ensure there is sufficient contrast between text and background colors for individuals with a color deficiency.

Testfile 2.2.1.3: poor color contrast (active link).
View testfile source
Testfile

Warning number [2.2.1.4] - Priority 3
Ensure there is sufficient contrast between text and background colors for individuals with a color deficiency.

Testfile 2.2.1.4: poor color contrast (visited link).
View testfile source
Testfile

Error number [3.2.1.1] - Priority 2
All documents must begin with a Document Type Declaration <doctype> or DTD. The informs a validator which version of HTML to use when verifying a document's syntax. The most commonly used DTD is HTML 4.01 Transitional.

Testfile 3.2.1.1: <doctype> missing.
View testfile source
Testfile

Warning number [3.3.1.1] - Priority 2
Use Cascading Style Sheets (CSS) to apply stylistic effects (i.e. font color, font size, paragraph indentation, etc.) and control positioning of content (i.e. page layout) within web documents.

Testfile 3.3.1.1: use style sheets to control presentation.
View testfile source
Testfile

Error number [3.5.1.1] - Priority 2
Organize or "nest" headers in an ordered and logical fashion. Headers that are not structured in sequential order or those used to apply font effects can creating difficulties in navigation and comprehension for the visually impaired.

Testfile 3.5.1.1: headers improperly nested.
View testfile source
Testfile

Warning number [3.5.2.1] - Priority 2
If a lead sentence or paragraph is italicized consider converting it into a header. If a text element occurs within a paragraph and the paragraph is less than ten words containing only text items or formatting elements it is also potentially a header.

Testfile 3.5.2.1: potential header (bold).
View testfile source
Testfile

Warning number [3.5.2.2] - Priority 2
If a lead sentence or paragraph is italicized consider converting it into a header. If a text element occurs within a paragraph and the paragraph is less than ten words containing only text items or formatting elements it is also potentially a header.

Testfile 3.5.2.2: potential header (italics).
View testfile source
Testfile

Warning number [3.5.2.3] - Priority 2
If a lead sentence or paragraph is underlined consider converting it into a header. If a text element occurs within a paragraph and the paragraph is less than ten words containing only text items or formatting elements it is also potentially a header.

Testfile 3.5.2.3: potential header (underline).
View testfile source
Testfile

Warning number [3.6.1.1] - Priority 2
Avoid using list markup to create formatting effects. Do not use 'ul' (unordered list) to indent text, use Cascading Style Sheets (CSS) instead.

Testfile 3.6.1.1: list usage invalid <ul>.
View testfile source
Testfile

Warning number [3.6.1.2] - Priority 2
Avoid using list markup to create formatting effects. Do not use 'ol' (ordered list) to indent text, use Cascading Style Sheets (CSS) instead.

Testfile 3.6.1.2: list usage invalid <ol>.
View testfile source
Testfile

Warning number [3.6.1.4] - Priority 2
Avoid using list markup to create formatting effects. Do not use 'li' (list item) to indent text, use Cascading Style Sheets (CSS) instead.

Testfile 3.6.1.4: list usage invalid <li>.
View testfile source
Testfile

Error number [4.1.1.1] - Priority 1
Indicate changes in the primary language of a document through HTML markup. If changes in language are not marked, a speech synthesizer will attempt to pronounce a foreign word or phrase in the document's original primary language. Encapsulate short words or phrases with 'span lang="(indicate language here)" ' and use 'Q lang="(indicate language here)"' for quotes.

Testfile 4.1.1.1: indicate changes in language.
View testfile source
Testfile

Error number [4.3.1.1] - Priority 3
Identify the primary language of each document to ensure that clients automatically retrieve web pages in their preferred language. Language can be specified either through http headers or html markup (i.e. 'html lang="en"').

Testfile 4.3.1.1: language not identified.
View testfile source
Testfile

Error number [4.3.1.2] - Priority 3
Ensure the language specified in either the http header or html markup (i.e. 'html lang="en"') is valid.

Testfile 4.3.1.2: language attribute invalid.
View testfile source
Testfile

Error number [5.1.2.1] - Priority 1
Data tables must include headers for each row and column. Use the "headers" attribute to attach labels to table rows and columns via the "id" attribute. This creates a link between headings and their associated data cells.

Testfile 5.1.2.1: data <table> missing row/column headers (all).
View testfile source
Testfile

Error number [5.1.2.2] - Priority 1
Data tables must include headers for each row and column. Use the "headers" attribute to attach labels to table rows and columns via the "id" attribute. This creates a link between headings and their associated data cells.

Testfile 5.1.2.2: data <table> missing row/column headers (1 col).
View testfile source
Testfile

Error number [5.1.2.3] - Priority 1
Data tables must include headers for each row and column. Use the "headers" attribute to attach labels to table rows and columns via the "id" attribute. This creates a link between headings and their associated data cells.

Testfile 5.1.2.3: data <table> missing row/column headers (1 row).
View testfile source
Testfile

Warning number [5.2.1.1] - Priority 1
If a data table has two or more logical levels of row or column headings, use html markup to link data cells with their corresponding headers. To identify groups of rows, use the 'thead', 'tfoot', and 'tbody' elements. To group columns, use 'col' and 'colgroup'.

Testfile 5.2.1.1: data <table> may require markup (column headers).
View testfile source
Testfile

Warning number [5.2.1.2] - Priority 1
If a data table has two or more logical levels of row or column headings, use html markup to link data cells with their corresponding headers. To identify groups of rows, use the 'thead', 'tfoot', and 'tbody' elements. To group columns, use the 'col' and 'colgroup' elements.

Testfile 5.2.1.2: data <table> may require markup (row headers).
View testfile source
Testfile

Warning number [5.3.1.1] - Priority 2
If tables are used for layout purposes ensure the content remains intelligible when the table is linearized (i.e. the content is converted into standard paragraphs). When tables are used to present text in word-wrapped, parallel columns the information may become jumbled when rendered by a screen reader.

Testfile 5.3.1.1: verify layout talbes linearize properly.
View testfile source
Testfile

Warning number [5.4.1.1] - Priority 2
Avoid using structural markup to apply style to text within data cells in tables used for layout purposes. Use Cascading Style Sheets (CSS) to format text, instead.

Testfile 5.4.1.1: invalid markup used in layout <table>.
View testfile source
Testfile

Error number [5.5.1.1] - Priority 3
Tables must include a "summary" attribute in the table element. The summary should describe the relationship among table cells and cells that span multiple columns and/or rows. It is also useful in describing how the information contained in the table relates to other information in the document.

Testfile 5.5.1.1: <table> missing summary.
View testfile source
Testfile

Error number [5.5.1.2] - Priority 3
Table summaries must include an actual value (i.e. summary="" or null is not acceptable). The summary should describe the relationship among table cells and cells that span multiple columns and/or rows. It is also useful in describing how the information contained in the table relates to other information in the document.

Testfile 5.5.1.2: <table> summary invalid (null).
View testfile source
Testfile

Error number [5.5.1.3] - Priority 3
Table summaries must contain an actual value (i.e. summary=" " with spaces is not acceptable). The summary should describe the relationship among table cells and cells that span multiple columns and/or rows. It is also useful in describing how the information contained in the table relates to other information in the document.

Testfile 5.5.1.3: <table> summary invalid (spaces).
View testfile source
Testfile

Error number [5.5.1.6] - Priority 3
Table summaries must contain an actual description. Placeholder text (i.e. summary="table summary") is not acceptable. The summary should describe the relationship among table cells and cells that span multiple columns and/or rows. It is also useful in describing how the information contained in the table relates to other information in the document.

Testfile 5.5.1.6: <table> summary invalid (placeholder text).
View testfile source
Testfile

Error number [5.5.2.1] - Priority 2
Captions are used to describe the nature of the table in one to three sentences. Insert the caption below the table element. A caption is not always necessary. If a caption is not provided, use the "title" attribute to briefly describe the purpose of a table.

Testfile 5.5.2.1: <table> summary <caption>.
View testfile source
Testfile

Warning number [5.6.1.1] - Priority 3
Provide abbreviations for table headers to reduce useless repetition and reading time for those relying on screen readers and other speech technologies. Include the "abbr" attribute in the table's 'th' element and condense the heading to one or two key words.

Testfile 5.6.1.1: <table> may require header abbreviations.
View testfile source
Testfile

Warning number [5.6.1.2] - Priority 3
Abbreviations for table headers must contain an actual value (i.e. 'th abbr=""' is not acceptable). Condense the heading to one or two key words.

Testfile 5.6.1.2: <table> header abbreviations invalid (null).
View testfile source
Testfile

Warning number [5.6.1.3] - Priority 3
Abbreviations for table headers must contain an actual value (i.e. 'th abbr=" "' is not acceptable). Condense the heading to one or two key words.

Testfile 5.6.1.3: <table> header abbreviations invalid (spaces).
View testfile source
Testfile

Warning number [6.1.1.1] - Priority 1
If style sheets are used for formatting content and/or controlling page layout, be sure the information remains accessible when style sheets are disabled or not supported. Include a non-visual method of presenting the information and organize style sheets logically.

Testfile 6.1.1.1: style sheets require testing (link).
View testfile source
Testfile

Warning number [6.1.1.2] - Priority 1
If style sheets are used for formatting content and/or controlling page layout, be sure the information remains accessible when style sheets are disabled or not supported. Include a non-visual method of presenting the information and organize style sheets logically.

Testfile 6.1.1.2: style sheets require testing (style element).
View testfile source
Testfile

Warning number [6.1.1.3] - Priority 1
If style sheets are used for formatting content and/or controlling page layout, be sure the information remains accessible when style sheets are disabled or not supported. Include a non-visual method of presenting the information and organize style sheets logically.

Testfile 6.1.1.3: style sheets require testing (style attribute).
View testfile source
Testfile

Error number [6.2.1.1] - Priority 1
Make the source of each frame a valid html document. If an image file is used as the source of a frame, you will not be able to include "alt" text with the graphic. Also, do not use the "title" attribute to describe the contents of a frame. If the content changes, the "title" will no longer be applicable.

Testfile 6.2.1.1: <frame> source invalid.
View testfile source
Testfile

Warning number [6.2.2.1] - Priority 1
Whenever dynamic content changes, text equivalents must also be updated. If an applet is used to generate dynamic content, provide a text equivalent between the opening and closing applet elements or via the "alt" attribute.

Testfile 6.2.2.1: text equivalents require updating (applet).
View testfile source
Testfile

Warning number [6.2.2.2] - Priority 1
Whenever dynamic content changes, text equivalents must also be updated. If a script is used to generate dynamic content, provide a text equivalent by including a <noscript> section in the document.

Testfile 6.2.2.2: text equivalents require updating (script).
View testfile source
Testfile

Warning number [6.2.2.3] - Priority 1
Whenever dynamic content changes, text equivalents must also be updated. If 'object' is used to generate dynamic content, include a text equivalent between the open and closing object elements.

Testfile 6.2.2.3: text equivalents require updating (object).
View testfile source
Testfile

Warning number [6.3.1.1] - Priority 1
Verify content remain accessible when programmatic objects are disabled or not supported. If a script is used to generate content, provide a text equivalent by including a <noscript> section in the document. Another option is to use server-side rather than client-side scripts. As a last resort, create a text-based alternative for the entire document.

Testfile 6.3.1.1: programmatic objects require testing (script).
View testfile source
Testfile

Warning number [6.3.1.2] - Priority 1
Verify content remain accessible when programmatic objects are disabled or not supported. If <object> is used to generate content, provide a text equivalent between the opening and closing object elements.

Testfile 6.3.1.2: programmatic objects require testing (object).
View testfile source
Testfile

Warning number [6.3.1.3] - Priority 1
Verify that content remains accessible when programmatic objects are disabled or not supported. This element allows different data types (i.e. movies, audio files, etc.) to be embedded in an html document. Regardless the data type, an appropriate text equivalent must also be included.

Testfile 6.3.1.3: programmatic objects require testing (embed).
View testfile source
Testfile

Warning number [6.3.1.4] - Priority 1
Verify content remain accessible when programmatic objects are disabled or not supported. If an applet is used to generate dynamic content, provide a text equivalent between the opening and closing applet elements or via the "alt" attribute.

Testfile 6.3.1.1: programmatic objects require testing (applet).
View testfile source
Testfile

Error number [6.5.1.1] - Priority 2
Each <frameset> must include a valid <noframes> section which has at least one word of text or accessible html code and all links required to navigate the site. Do not use the <noframes> section to inform users that they must upgrade to a browser that supports frames.

Testfile 6.5.1.1: <frameset> missing <noframes> section.
View testfile source
Testfile

Error number [6.5.1.2] - Priority 2
A valid <noframes> section includes at least one word of text or accessible html code and all links required to navigate the site. Do not use the <noframes> section to inform users that they must upgrade to a browser that supports frames.

Testfile 6.5.1.2: <noframes> section invalid (no value).
View testfile source
Testfile

Error number [6.5.1.3] - Priority 2
Do not use the <noframes> section to inform users that they must upgrade to a browser that supports frames. A valid <noframes> section includes at least one word of text or accessible html code and all links required to navigate the site.

Testfile 6.5.1.3: <noframes> section invalid (content).
View testfile source
Testfile

Error number [6.5.1.4] - Priority 2
All links must be enclosed in the <noframes> section. A valid <noframes> section has at least one word of text or accessible html code. In addition, <noframes> should not be used to inform users that they must upgrade to a browser that supports frames. Testfile 6.5.1.4: <noframes> section invalid (link).
View testfile source
Testfile

Warning number [7.1.1.1] - Priority 1
Ensure scripts do not cause on-screen flickering. It can trigger epileptic seizures in people with photosensitive epilepsy. At present, browsers do not allow screen flicker to be disabled by the user.

Testfile 7.1.1.1: remove flicker (script).
View testfile source
Testfile

Warning number [7.1.1.2] - Priority 1
Ensure objects do not cause on-screen flickering. It can trigger epileptic seizures in people with photosensitive epilepsy. At present, browsers do not allow screen flickering to be disabled by the user.

Testfile 7.1.1.2: remove flicker (object).
View testfile source
Testfile

Warning number [7.1.1.3] - Priority 1
Ensure embedded items such as movies, audio files, etc. do not cause on-screen flickering. It can trigger epileptic seizures in people with photosensitive epilepsy. At present, browsers do not allow screen flickering to be disabled by the user.

Testfile 7.1.1.3: remove flicker (embed).
View testfile source
Testfile

Warning number [7.1.1.4] - Priority 1
Ensure applets do not cause on-screen flickering. It can trigger epileptic seizures in people with photosensitive epilepsy. At present, browsers do not allow screen flickering to be disabled by the user.

Testfile 7.1.1.4: remove flicker (applet).
View testfile source
Testfile

Warning number [7.1.1.5] - Priority 1
Ensure that animated gifs do not flicker. On-screen flickering can trigger epileptic seizures in people with photosensitive epilepsy. At present, browsers do not allow screen flickering to be disabled by the user.

Testfile 7.1.1.5: remove flicker (animated gif).
View testfile source
Testfile

Warning number [7.2.1.1] - Priority 2
Both <blink> and <marquee> are non-standard elements and should not be used in html documents. Use style sheets to emphasize content with special formatting (i.e. bold, italics, capitalization, underline, etc.)

Testfile 7.2.1.1: remove blink/marquee.
View testfile source
Testfile

Warning number [7.4.1.1] - Priority 2
Until browser agents allow clients to stop documents from automatically refreshing, avoid creating p ages that reload without a request from the user. Allow visitors to refresh or reload pages at their own discretion.

Testfile 7.4.1.1: remove auto-refresh.
View testfile source
Testfile

Warning number [7.5.1.1] - Priority 2
Avoid using markup that automatically redirects visitors to other web documents. People with limited vision or cognitive disabilities often don't have sufficient time to read a document that includes an auto-redirect command. Instead, create a link within the document that allows clients to advance to the next page at their own discretion.

Testfile 7.5.1.1: remove auto-redirect.
View testfile source
Testfile

Warning number [8.1.1.1] - Priority 1
Ensure pages are functional when programmatic objects such as scripts are disabled or not supported. Make scripts directly accessible or compatible with assistive technologies when functionality is important. Include a <noscript> section in the document and specify logical rather than device-dependent event handlers. As a last resort, provide equivalent content on an alternative page.

Testfile 8.1.1.1: ensure programmatic objects are accessible (script).
View testfile source
Testfile

Warning number [8.1.1.2] - Priority 1
Ensure pages are functional when programmatic objects are turned off or not supported. Use application-level triggers rather than user interaction-level event triggers. If device-dependent attributes must be used, provide redundant input mechanisms (i.e. specify two handlers for the same element). As a last resort, provide equivalent information on an alternative page.

Testfile 8.1.1.2: ensure programmatic objects are accessible (object).
View testfile source
Testfile

Warning number [8.1.1.3] - Priority 1
Ensure pages are functional when programmatic objects such as applets are disabled or not supported. Make applets directly accessible or compatible with assistive technologies when functionality is important. Provide either a link to a description or insert a text equivalent directly into the document and use event handlers that are input device-independent. As a last resort, provide equivalent information on an alternative page.

Testfile 8.1.1.3: ensure programmatic objects are accessible (applet).
View testfile source
Testfile

Warning number [8.1.1.4] - Priority 1
Ensure pages are functional when programmatic objects are disabled or not supported. Make embedded objects such as movies or audio files directly accessible or compatible with assistive technologies when functionality is important. Provide a text equivalent via "alt" and "longdesc" attributes or in element content. As a last resort, provide equivalent information on an alternative page.

Testfile 8.1.1.4: ensure programmatic objects are accessible (embed).
View testfile source
Testfile

Warning number [9.1.1.1] - Priority 1
Convert server-side image maps to client-side maps whenever possible. Client-side image maps are preferable because, unlike server-side maps, they can be accessed by individuals who either cannot view images, have chosen to use a non-graphical browser, or are unable to use traditional pointing devices (such as a mouse).

Testfile 9.1.1.1: image map (server-side) requires conversion.
View testfile source
Testfile

Error number [9.3.1.1] - Priority 2
Include a redundant mechanism (such as keyboard input) if device dependent event handlers are used to invoke a script. The onMouseDown event handler should be paired and included in the same element with "onKeyDown".

Testfile 9.3.1.1: <script> not keyboard accessible (onMouseDown).
View testfile source
Testfile

Error number [9.3.1.2] - Priority 2
Include a redundant mechanism (such as keyboard input) if device dependent event handlers are used to invoke a script. The onMouseUp event handler should be paired and included in the same element with "onKeyUp".

Testfile 9.3.1.2: <script> not keyboard accessible (onMouseUp).
View testfile source
Testfile

Error number [9.3.1.3] - Priority 2
Include a redundant mechanism (such as keyboard input) if device dependent event handlers are used to invoke a script. The onMouseUp event handler should be paired and included in the same element with "onKeyPress".

Testfile 9.3.1.3: <script> not keyboard accessible (onClick).
View testfile source
Testfile

Error number [9.3.1.4] - Priority 2
Always include a keyboard equivalent with a device dependent event handler such as a mouse. Avoid using event handlers that rely on mouse coordinates since this precludes device independent input. Scripts that accept keyboard input are generally accessible to those using speech input or a command line interface.

Testfile 9.3.1.4: <script> not keyboard accessible (onMouseOver).
View testfile source
Testfile

Error number [9.3.1.5] - Priority 2
Always include a keyboard equivalent with a device dependent event handler such as a mouse. Avoid using event handlers that rely on mouse coordinates since this precludes device independent input. Scripts that accept keyboard input are generally accessible to those using speech input or a command line interface.

Testfile 9.3.1.5: <script> not keyboard accessible (onMouseOut).
View testfile source
Testfile

Error number [9.3.1.6] - Priority 2
Always include a keyboard equivalent with a device dependent event handler such as a mouse. Avoid using event handlers that rely on mouse coordinates since this precludes device independent input. Scripts that accept keyboard input are generally accessible to those using speech input or a command line interface.

Testfile 9.3.1.6: <script> not keyboard accessible (onMouseMove).
View testfile source
Testfile

Warning number [10.1.1.1] - Priority 2
Do not cause pop-ups or other windows to appear and do not change the current window without informing the user. Avoid using target attributes such as "_new" or "_blank" in anchor elements. Use the existing window as the target. Links that open new windows can be disorienting to people with cognitive and visual disabilities.

Testfile 10.1.1.1: new windows require warning (_new).
View testfile source
Testfile

Warning number [10.1.1.2] - Priority 2
Do not cause pop-ups or other windows to appear and do not change the current window without informing the user. Avoid using target attributes such as "_blank" or "_new" in anchor elements. Use the existing window as the target. Links that open new windows can be disorienting to people with cognitive and visual disabilities.

Testfile 10.1.1.2: new windows require warning (_blank).
View testfile source
Testfile

Error number [10.2.1.1] - Priority 2
Create a clear association between a form control and its label by ensuring labels are positioned properly within html markup. Do not separate a label from its form control with additional text, images, etc. If there are two or more controls on a single line, labels should be placed immediately before its corresponding control or place each label and control on a separate line.

Testfile 10.2.1.1: <label> needs repositioning (<label> before <input>)
View testfile source
Testfile

Error number [10.2.1.2] - Priority 2
Create a clear association between a form control and its label by ensuring labels are positioned properly within html markup. Do not separate a form control from its label with additional text, images, etc. If there are two or more controls on a single line, labels should be placed immediately after its corresponding control or place each label and control on a separate line.

Testfile 10.2.1.2: <label> needs repositioning (<label> after <input>)
View testfile source
Testfile

Error number [10.4.1.1] - Priority 3
Include default text for all <input> form controls. Placing default text in form fields enables keyboard users to insert a cursor into placeholder text or characters and enter their own data.

Testfile 10.4.1.1: form control requires default text.
View testfile source
Testfile

Error number [10.4.1.2] - Priority 3
Default text for all <input> form controls must include an actual value. Null (i.e. value="") is not valid default text but using placeholder characters (i.e. value="****") is acceptable. Placing default text in form fields enables keyboard users to insert a cursor into placeholder text and enter their own data.

Testfile 10.4.1.2: form control default text invalid (null).
View testfile source
Testfile

Error number [10.4.1.3] - Priority 3
Default text for all <input> form controls must include an actual value. Including spaces (i.e. value=" ") in default text is not allowed but using placeholder characters (i.e. value="****") is acceptable. Placing default text in form fields enables keyboard users to insert a cursor into placeholder text and enter their own data.

Testfile 10.4.1.3: form control default text invalid (spaces).
View testfile source
Testfile

Warning number [11.2.1.1] - Priority 2
Replace deprecated html elements and attributes to ensure their web pages remain compliant with the most current browser technologies. Applet (and all its attributes) has been deprecated in favor of <object>.

Testfile 11.2.1.1: replace deprecated html <applet>.
View testfile source
Testfile

Error number [11.2.1.2] - Priority 2
Replace deprecated html elements and attributes to ensure web pages remain compliant with the most current browser technologies. The <basefont> element is deprecated. Use Cascading Style Sheets (CSS) to set font size.

Testfile 11.2.1.2: replace deprecated html <basefont>.
View testfile source
Testfile

Error number [11.2.1.3] - Priority 2
Replace deprecated html elements and attributes to ensure web pages remain compliant with the most current browser technologies. The <center> element is deprecated. Use Cascading Style Sheets (CSS) to position text.

Testfile 11.2.1.3: replace deprecated html <center>.
View testfile source
Testfile

Error number [11.2.1.4] - Priority 2
Replace deprecated html elements and attributes to ensure web pages remain compliant with the most current browser technologies. The <dir> element has been deprecated in favor of <ul> (unordered list).

Testfile 11.2.1.4: replace deprecated html <dir>.
View testfile source
Testfile

Error number [11.2.1.5] - Priority 2
Replace deprecated html elements and attributes to ensure web pages remain compliant with the most current browser technologies. The <font> element is deprecated. Use Cascading Style Sheets (CSS) to set font size and color.

Testfile 11.2.1.5: replace deprecated html <font>.
View testfile source
Testfile

Error number [11.2.1.6] - Priority 2
Replace deprecated html elements and attributes to ensure web pages remain compliant with the most current browser technologies. The <isindex> element (which creates a single-line text input control) has been deprecated. Use <input> to create text input controls instead.

Testfile 11.2.1.6: replace deprecated html <isindex>.
View testfile source
Testfile

Error number [11.2.1.7] - Priority 2
Replace deprecated html elements and attributes to ensure web pages remain compliant with the most current browser technologies. The <menu> element has been deprecated in favor of <ul> (unordered list).

Testfile 11.2.1.7: replace deprecated html <menu>.
View testfile source
Testfile

Error number [11.2.1.8] - Priority 2
Replace deprecated html elements and attributes to ensure web pages remain compliant with the most current browser technologies. The <s> element (used to render strike-through style text) has been deprecated. Use Cascading Style Sheets (CSS) to apply font effects to text.

Testfile 11.2.1.8: replace deprecated html <s>.
View testfile source
Testfile

Error number [11.2.1.9] - Priority 2
Replace deprecated html elements and attributes to ensure web pages remain compliant with the most current browser technologies. The <strike> element (used to render strike-through style text) has been deprecated. Use Cascading Style Sheets (CSS) to apply font effects to text.

Testfile 11.2.1.9: replace deprecated html <striket>.
View testfile source
Testfile

Error number [11.2.1.10] - Priority 2
Replace deprecated html elements and attributes to ensure web pages remain compliant with the most current browser technologies. The <u> element (which renders underlined text) has been deprecated. Use Cascading Style Sheets (CSS) to apply font effects to text.

Testfile 11.2.1.10: replace deprecated html <u>.
View testfile source
Testfile

Error number [12.1.1.1] - Priority 1
Provide a title for each <frame> or <iframe> within a document. Frame titles must be meaningful (i.e. identify content and/or navigational links). Do not use filenames (e.g. title="frame1.html") or placeholder text (i.e. "insert frame title here") as a title.

Testfile 12.1.1.1: <frame> missing title.
View testfile source
Testfile

Error number [12.1.1.2] - Priority 1
Frame titles must be meaningful (i.e. identify content and/or navigational links). Null (i.e. title="") is not an acceptable title. In addition, do not use filenames (e.g. title="frame1.html") or placeholder text (i.e. "insert frame title here") as a title.

Testfile 12.1.1.2: <frame> title invalid (null).
View testfile source
Testfile

Error number [12.1.1.3] - Priority 1
Frame titles must be meaningful (i.e. identify content and/or navigational links). Spaces in a title (i.e. title=" ") are not acceptable. In addition, do not use filenames (e.g. title="frame1.html") or placeholder text (i.e. "insert frame title here") as a title.

Testfile 12.1.1.3: <frame> title invalid (spaces).
View testfile source
Testfile

Error number [12.4.1.1]< - Priority 2
The "for" and "id" attributes explicitly associate a label with its matching form control. The value of the "for" attribute must be identical to the "id" attribute. More than one label may be associated with the same control by creating multiple references through the "for" attribute.

Testfile 12.4.1.1: associate labels explicitly with form controls.
View testfile source
Testfile

Error number [12.4.1.2] - Priority 2
The "for" attribute must accompany the "id" attribute to explicitly associate a label with its matching form control. The value of the "for" and "id" attributes must be identical. More than one label may be associated with the same control by creating multiple references via the "for" attribute.

Testfile 12.4.1.2: associate labels explicitly with form controls (for).
View testfile source
Testfile

Error number [12.4.1.3] - Priority 2
The "id" attribute must accompany the "for" attribute to explicitly associate a label with its matching form control. The value of the "for" and "id" attributes must be identical. More than one label may be associated with the same control by creating multiple references via the "for" attribute.

Testfile 12.4.1.3: associate labels explicitly with form controls (id).
View testfile source
Testfile

Error number [13.1.1.1] - Priority 2
Create link text that remains meaningful even when read out of context. Identify the purpose or target of each link (i.e. describe the destination of the link) and keep the text concise.

Testfile 13.1.1.1: link text not meaningful.
View testfile source
Testfile

Error number [13.1.1.2] - Priority 2
Create link text that remains meaningful even when read out of context. Identify the purpose or target of each link (i.e. describe the destination of the link) and keep the text concise.

Testfile 13.1.1.2: link text missing.
View testfile source
Testfile

Error number [13.1.1.3] - Priority 2
Keep link text concise. Create links that remain meaningful even when read out of context by clearly identifying the purpose or target of each link (i.e. describe the destination of the link).

Testfile 13.1.1.3: link text too long .
View testfile source
Testfile

Error number [13.1.1.4] - Priority 2
Avoid ambiguous link text such as "click here". In addition, the term "click" suggests the link is only accessible via a mouse or other similar pointing device. Create link text that remains meaningful even when read out of context. Identify the purpose or target of each link (i.e. describe the destination of the link)and keep the text concise.

Testfile 13.1.1.4: link text not meaningful (click here).
View testfile source
Testfile

Error number [13.1.1.5] - Priority 2
Avoid ambiguous link text such as "more". Create link text that remains meaningful even when read out of context. Identify the purpose or target of each link (i.e. describe the destination of the link) and keep the text concise.

Testfile 13.1.1.5: link text not meaningful (more).
View testfile source
Testfile

Error number [13.1.1.6] - Priority 2
Avoid ambiguous link text such as "follow this". Create link text that remains meaningful even when read out of context. Identify the purpose or target of each link (i.e. describe the destination of the link)and keep the text concise.

Testfile 13.1.1.6: link text not meaningful (follow this).
View testfile source
Testfile

Error number [13.2.1.1] - Priority 2
Metadata should describe or provide specific information about individual web documents. Metadata is commonly used to list keywords so that search engines can conduct a more accurate and refined search. It can also include: content ratings, author information, site maps, stream channel definitions, a document's primary language, and digital library collections.

Testfile 13.2.1.1: Metadata missing.
View testfile source
Testfile

Error number [13.2.1.2] - Priority 2
If metadata is specified via the link element its value should be a URI. It should not be used to access style sheets. Use metadata to describe or provide specific information about individual web documents. Metadata often includes a list of keywords enabling search engines to conduct a more accurate and refined search. It can also contain content ratings, author information, site maps, stream channel definitions, a document's primary language, and digital library collections.

Testfile 13.2.1.2: Metadata missing (link element).
View testfile source
Testfile

Error number [13.2.1.3] - Priority 2
Do not use the metadata element to refresh or redirect web pages automatically. Use metadata to describe or provide specific information about individual web documents. Metadata often includes a list of keywords enabling search engines to conduct a more accurate and refined search. It can also contain content ratings, author information, site maps, stream channel definitions, a document's primary language, and digital library collections.

Testfile 13.2.1.3: Metadata missing (redirect/auto-refresh).
View testfile source
Testfile

Error number [13.10.1.1] - Priority 3
Provide a means to skip over multi-line ascii art. Avoid ascii art (character illustrations) whenever possible. If ascii art must be used, provide a link to bypass the graphic. For ascii art 20 characters or less use the element with the "title" attribute.

Testfile 13.10.1.1: skip over ascii art.
View testfile source
Testfile