Accessibility, HTML, CSS, Broken Links, Spell Check

[WCAG1 1.1 (A)] Provide a text equivalent for non-text items using alt

When using <img>, specify a short text equivalent with the alt attribute. See HTML Techniques for WCAG 1.0.

[WCAG1 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 HTML Techniques for WCAG 1.0.

[WCAG1 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 HTML Techniques for WCAG 1.0.

[WCAG1 1.1 (A)] Image buttons should have alt text that describes them

When using image buttons, specify a short text equivalent with the alt attribute. See HTML Techniques for WCAG 1.0.

[WCAG1 1.1 (A)] Provide a text equivalent for non-text items using alt

When using <applet>, specify a short text equivalent with the alt attribute. See HTML Techniques for WCAG 1.0.

[WCAG1 1.1 (A)] Provide a text equivalent for non-text items using alt

When using <area>, specify a short text equivalent with the alt attribute. See HTML Techniques for WCAG 1.0.

[WCAG1 1.1 (A)] Provide a text equivalent for non-text items using alt

When using <embed>, specify a short text equivalent with the alt attribute. See WCAG 1.0 Guideline 1.

[WCAG1 1.1 (A)] Provide a text equivalent by placing some text in this tag

When using <iframe>, specify a short text equivalent by placing some text within it. See WCAG 1.0 Guideline 1.

[WCAG1 1.1 (A)] When using a text alternative it must be meaningful

If the text in the 'text alternative' cannot be used in place of the non-text content without losing information or function then it fails because it is not, in fact, an alternative to the non-text content. See WCAG 1.0 Guideline 1.

[WCAG1 1.1 (A)] When using a text alternative it must not include ASCII art or smileys

If the text in the 'text alternative' when read aloud does not sound meaningful then it fails because it is not, in fact, an alternative to the non-text content. See WCAG 1.0 Guideline 1.

[WCAG1 1.1 (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 [WCAG1 1.1 (A)] error.

[WCAG1 1.1 (A)] The corresponding <noembed> element is missing or misplaced

For each <embed> element you should provide either a nested <noembed> element or a <noembed> element immediately following it. See WCAG 1.0 Guideline 1.

[WCAG1 5.1 (A)] For data tables identify row and column headers

No <th> tags where found in a table or they contain no text, suggesting that you have not clearly identified any row and column headers. See HTML Techniques for WCAG 1.0. If this is not a data table then this may be a [WCAG1 5.4 (AA)] error as there is a <caption> or summary present.

[WCAG1 5.2 (A)] For data tables use markup to associate data cells and header cells

For data tables you should use markup to associate data cells and header cells, and no such markup was found. See HTML Techniques for WCAG 1.0. If this is not a data table then this may be a [WCAG1 5.4 (AA)] error as there is a <caption> or summary present.

[WCAG1 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 HTML Techniques for WCAG 1.0.

[WCAG1 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 HTML Techniques for WCAG 1.0.

[WCAG1 6.3 (A)] Consider providing a <noscript> alternative after each <script> tag

This problem 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 problem. See WCAG 1.0 Guideline 6.

[WCAG1 9.1 (A)] 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 must use a server-side map ensure that there is an accessible alternative available. See WCAG 1.0 Guideline 9.

[WCAG1 12.1 (A)] Add a title attribute to facilitate identification and navigation

Title each <frame> and <frameset> to facilitate frame identification and navigation. See HTML Techniques for WCAG 1.0.

[WCAG1 12.1 (A)] Add a meaningful title attribute to facilitate identification and navigation

Title each <frame> and <frameset> to facilitate frame identification and navigation. See HTML Techniques for WCAG 1.0.

[WCAG1 3 (AA)] No HTML specification was selected

You should always select a HTML specification to ensure that the page does not have any issues which may prevent accessibility aids from properly representing the page. See WCAG 1.0 Guideline 3.

[WCAG1 3.2 (AA)] Add a <!DOCTYPE> tag to the page

Validating to a published formal grammar and declaring it at the beginning of a document lets the user know that the structure of the document is sound. See HTML Techniques for WCAG 1.0.

[WCAG1 3.3 (AA)] Use style sheets for presentation effects, use <em> or <strong> for emphasis

Validating to a published formal grammar and declaring it at the beginning of a document lets the user know that the structure of the document is sound. See HTML Techniques for WCAG 1.0.

[WCAG1 3.3 (AA)] The <fieldset> element should only be used within a form

Using a <fieldset> outside of a form usually indicates it is being used for presentation effects. Tags that create a visual presentation effect should not be used. You should use style sheets to control layout and presentation. See WCAG 1.0 Guideline 3.

[WCAG1 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 WCAG 1.0 Guideline 3.

[WCAG1 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 (for example, H1 directly to H3). Do not use headings to create font effects. See HTML Techniques for WCAG 1.0.

[WCAG1 3.5 (AA)] Heading with no content

Ensure that all headings contain informative content. This is necessary because users may navigate or search by headings. See WCAG 1.0 Guideline 3.

[WCAG1 3.5 (AA)] Use heading elements to convey structure

Many assistive technologies provide navigation using headings, including skipping navigational links. If your document has any structure you should use heading markup to convey the structure of the content. Even a single header will make it easier for users. See HTML Techniques for WCAG 1.0.

[WCAG1 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: HTML Techniques for WCAG 1.0.

[WCAG1 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 HTML Techniques for WCAG 1.0.

[WCAG1 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 HTML Techniques for WCAG 1.0.

[WCAG1 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 CSS Techniques for WCAG 1.0.

[WCAG1 7.4 (AA)] Do not create pages that refresh

Until user agents provide the ability to stop the refresh, do not create periodically auto-refreshing pages. See Core Techniques for WCAG 1.0.

[WCAG1 7.5 (AA)] You should not use a non-zero page redirect

Until user agents provide the ability to stop auto-redirect, do not use markup to redirect pages automatically. See HTML Techniques for WCAG 1.0.

[WCAG1 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. See HTML Techniques for WCAG 1.0.

[WCAG1 10.1 (AA)] Do not use _blank targets

Until user agents allow users to turn off spawned windows, do not cause pop-ups or other windows to appear. See HTML Techniques for WCAG 1.0.

[WCAG1 11.2 (AA)] Avoid deprecated elements

Elements that are deprecated should be avoided. In many cases CSS may be used instead. See WCAG 1.0 Guideline 11.

[WCAG1 11.2 (AA)] Avoid deprecated attributes

Attributes that are deprecated should be avoided. In many cases CSS may be used instead. See WCAG 1.0 Guideline 11.

[WCAG1 12.3 (AA)] The <fieldset> element should be used to group radio buttons and checkboxes

Because groups of radio buttons and checkboxes are multiple controls, it is particularly important that they are grouped semantically so they can be more easily treated as a single control. See WCAG 1.0 Guideline 12.

[WCAG1 12.3 (AA)] Each <fieldset> should have a <legend> element that includes a description of that group

The first element inside the <fieldset> should be a <legend>, which provides a label or instructions for the group. See WCAG 1.0 Guideline 12.

[WCAG1 12.4 (AA)] The value of the for attribute must match the id of a form control in the same form

Associate labels explicitly with their controls. See HTML Techniques for WCAG 1.0.

E831

[WCAG1 12.4 (AA)] No matching <label> tag could be found, or label is empty

Associate labels explicitly with their controls. See HTML Techniques for WCAG 1.0.

E831

[WCAG1 12.4 (AA)] Associate <label> tags with form controls using the for attribute

Associate labels explicitly with their controls. See HTML Techniques for WCAG 1.0.

E831

[WCAG1 12.4 (AA)] Label text is missing

Associate labels explicitly with their controls. See HTML Techniques for WCAG 1.0.

E831

[WCAG1 12.4 (AA)] Associate labels with just one form control

Associate labels explicitly with their controls. See HTML Techniques for WCAG 1.0.

[WCAG1 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 HTML Techniques for WCAG 1.0.

[WCAG1 13.1 (AA)] Link text should make sense when read out of context

Don't use link text such as 'click here'. See HTML Techniques for WCAG 1.0.

[WCAG1 13.1 (AA)] Use the title attribute to distinguish between different links that use the same link text. See matching tag on line: LINE NUMBER

This error appears when you have not used the title attribute and have different links with the same link text. See HTML Techniques for WCAG 1.0.

[WCAG1 13.1 (AA)] Use different values for title attributes with links that use the same link text. See matching tag on line: LINE NUMBER

This error appears when you have used the same title attribute for different links with the same link text. See HTML Techniques for WCAG 1.0.

[WCAG1 13.2 (AA)] Add a <title> tag to the page to describe it

You should provide meta data, such as the <title> tag, to add semantic information to pages and sites. See HTML Techniques for WCAG 1.0.

[WCAG1 13.2 (AA)] Add a concise, meaningful <title> tag to the page to describe it

The <title> should contain a concise, meaningful description, less than 150 characters long. See HTML Techniques for WCAG 1.0.

[WCAG1 2.2 (AAA)] Text within this element has a low contrast

Ensure that foreground and background colour combinations provide sufficient contrast when viewed by someone having colour deficits or when viewed on a black and white screen. Note that our contrast calculation does not account for background images, gradients or text shadows. See WCAG 1.0 Guideline 2.

[WCAG1 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 HTML Techniques for WCAG 1.0.

[WCAG1 4.3 (AAA)] Use a title attribute to indicate what the abbreviation or acronym means

Mark up abbreviations and acronyms with <abbr> and <acronym> using the title attribute to indicate what they mean. See HTML Techniques for WCAG 1.0.

[WCAG1 5.5 (AAA)] Provide a description for data tables

Provide either a <caption>, title or summary attributes to describe the table. This must be a proper description and not a terse one. See HTML Techniques for WCAG 1.0. If this is not a data table then this is a [WCAG1 5.4 (AA)] error as there is a <th> or summary present.

[WCAG1 5.5 (AAA)] Provide a descriptive summary for complex data tables

Provide a descriptive summary attribute for complex data tables. This must be a proper description and not a terse one. See HTML Techniques for WCAG 1.0. If this is not a data table then this is a [WCAG1 5.4 (AA)] error as there is a <th> or summary present.

[WCAG1 5.6 (AAA)] Provide abbreviations for long header labels in data tables

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. See HTML Techniques for WCAG 1.0. If this is not a data table then this is a [WCAG1 5.4 (AA)] error as there is a <th> or summary present.

[WCAG1 9.5 (AAA)] Using onchange with selections may prevent keyboard operation

Using onchange with selections may prevent keyboard operation, because the handler fires as the selection is changed using the keyboard. See WCAG 1.0 Guideline 9.

[WCAG1 13.6 (AAA)] Add title attribute to facilitate navigation

Ensure there is a title attribute with <map>. This allows users using screen readers to decide if they wish to bypass the links. See HTML Techniques for WCAG 1.0.

[WCAG1 13.6 (AAA)] Add a skip navigation link as the first link on the page

If your document has structure then you should add header elements and/or a skip navigation link to make it easier for accessible users to get to the page's content. See HTML Techniques for WCAG 1.0.

[WCAG1 13.6 (AAA)] Skip navigation links should be the first link on a page

A skip navigation link was detected but it was not the first link on the page. Unless it is the first link then it may defeat the point for users. See HTML Techniques for WCAG 1.0.

[WCAG1 13.6 (AAA)] Skip navigation links should not be hidden

Hidden skip navigation links are not accessible for keyboard users. You should consider replacing this with a visible link and using CSS to hide it until the tab key is used. See HTML Techniques for WCAG 1.0.