Disclaimer

Please note that the automatic score is based on tests carried out automatically. About 20% of the conceivable tests can be automated, and the tool covers a part of these tests. The score from user tests are based on a limited set of questions and will also not cover all possible tests. Therefore, the evaluated pages may contain barriers not reported by any of the tools. For reference see the list of. currently implemented tests. Full disclaimer.

How to Repair

WCAG 2.0

Principle 1:
Perceivable

Information and user interface components must be presentable to users in ways they can perceive. WCAG 2.0: Principle 1

Guideline 1.1:
Text Alternatives

Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language.
Understanding Guideline 1.1

Success Criterion 1.1.1:
Non-text Content
(Level A)

Non-text Content: All non-text content that is presented to the user has a text alternative that serves the equivalent purpose, except for the situations listed below. (Level A).

Controls, Input: If non-text content is a control or accepts user input, then it has a name that describes its purpose. (Refer to Guideline 4.1 for additional requirements for controls and content that accepts user input.)

Time-Based Media: If non-text content is time-based media, then text alternatives at least provide descriptive identification of the non-text content. (Refer to Guideline 1.2 for additional requirements for media.)

Test: If non-text content is a test or exercise that would be invalid if presented in text, then text alternatives at least provide descriptive identification of the non-text content.

Sensory: If non-text content is primarily intended to create a specific sensory experience, then text alternatives at least provide descriptive identification of the non-text content.

CAPTCHA: If the purpose of non-text content is to confirm that content is being accessed by a person rather than a computer, then text alternatives that identify and describe the purpose of the non-text content are provided, and alternative forms of CAPTCHA using output modes for different types of sensory perception are provided to accommodate different disabilities.

Decoration, Formatting, Invisible: If non-text content is pure decoration, is used only for visual formatting, or is not presented to users, then it is implemented in a way that it can be ignored by assistive technology.

Test Detail: Use of Color (SC1-4-1-a)

Suitable difference between the attributes of link and the surrounding text.
(86 occurences)

There is a suitable difference between the background, font-weight, font-style, border, or text-decoration in computed style for the link and the surrounding text.

About this Test

Checked Elements:earl:automatic

This test checks if links within text are visually evident before they receive focus or are activated or the mouse is hovered over the link.

Short Description

The objective of this failure is to avoid situations in which people who cannot perceive color differences cannot identify links (when people with color vision can identify links). Link underlines or some other non-color visual distinction are required (when the links are discernible to those with color vision).
While some links may be visually evident from page design and context, such as navigational links, links within text are often visually understood only from their own display attributes. Removing the underline and leaving only the color difference for such links would be a failure because there would be no other visual indication (besides color) that it is a link.

Test Detail: Provide descriptive titles for web pages (F25)

Human input is necessary to verify, that the title describes the content of the page.

About this Test

Checked Elements:title

This test checks, whether the title of the web page identifies the contents or purpose of the page.

Short Description

It is important to provide a descriptive title for your web page. Titles should identify the content of the web page without requiring users to read or interpret the page. They are used in a variety of places like search results, bookmarks, title bar and tabs of user agent, or the browser history to identify the page.

How to Repair

Provide a descriptive title using the title element in the head of the page.
The title should always enable the user to distinguish different pages and identify their content.
Keep your titles simple, short and precise and
put the most specific information at the front (as the title might be cut off).

Keep your titles simple, short and precise and

put the most specific information at the front (as the title might be cut off).

Don't use same titles for more than one page and and avoid unclear titles.

Test Detail: Provide descriptive headings (G130)

Human input is necessary to verify, that the heading describes the section it belongs to.

About this Test

Checked Elements:h1-h6

This test checks, whether the headings identify their section of the content.

Short Description

It is important to provide a descriptive headings in your web page.
Descriptive headings give users an overview of the content and its organization, and help users find specific content and orient themselves within the web page. They identify sections of the content in relation both to the web page as a whole and to other sections of the same web page.

How to Repair

Provide text in the headings, that describes the section. If you need to use images as headings, provide an alternative text with the content of the heading in the alt attribute of the image.
Keep your headings short and succinct and try to putting the most important information at the beginning of each heading. This helps users “skim" the headings to locate the specific content they need, and is especially helpful when browsers or assistive technology allow navigation from heading to heading.Tips for making accessible headings

Test Detail: Primary language of page (SC3-1-1-html)

The primary language of the web content can be programmatically determined

About this Test

Checked Elements:html element

This test checks that the primary language of the web content can be programmatically determined.

Short Description

It is necessary to mark the primary language of a web page. This makes it possible for user agents and assistive technologies to present content correctly.
Screen readers can use the pronunciation rules of the language of the text. Visual browsers can display characters and scripts in appropriate ways. Furthermore automatic processing of the content like automatic translation or providing additional information using a dictionary are made possible.
If the html element has a lang attribute and the value of lang attribute is on the list of languages of BCP 47 the test would pass.
Otherwise, test would fail.
Autowcag test description: SC3-1-1-html

How to Repair

Use the lang and xml:lang attributes on the html element to specify the main language used in the web page.
If you use both attributes, their values have to be the same.

The value of the language attribute is composed from a sequence of one or more "subtags" divided by "-", each of which refines or narrows the range of language. It has to conform to BCP 47.
Examples of valid language tags are

Test Detail: Languages within the body (SC3-1-2-lang)

The lang attributes of elements within the body of the page are correct.

About this Test

Checked Elements:descendent-or-self::body[@lang]

This test checks that lang attributes within the body of a web page are correct

Short Description

This test is applied to all elements with lang attribute in the body of the web page (including the body element itself).
If the value of lang attribute is on the list of languages (BCP 47: http://www.rfc-editor.org/rfc/bcp/bcp47.txt) the test would pass. Otherwise, test would fail. Description: https://www.w3.org/community/auto-wcag/wiki/SC3-1-2-lang

How to Repair

The language of an element can be specified by its lang attributes.

The value of the lang is composed from a sequence of one or more "subtags" divided by "-", each of which refines or narrows the range of language. It has to conform to BCP 47.
Examples of valid language tags are

The human language of each passage or phrase in the content can be programmatically determined except for proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text. (Level AA)
Understanding: Success Criterion 3.1.2

Test Detail: Provide a submit button to initiate a change of context (H32)

Please check that implicit changes of context are described
(4 occurences)

Human input is necessary to verify, that the submit button is the only way to initiate a change of context with the form or that there is a description of the change before the initiating form control.

About this Test

Checked Elements:form elements

This test checks, if data in a form can be submitted explicitly by using submit buttons (input type="submit", input type="image", or button type="submit").

Short Description

Major changes in the content of the Web page can disorient users who are not able to view the entire page simultaneously, if they are made without user awareness. Using a button to submit data in a form explicitly is an appropriate control to use for causing a change of context.

Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behavior before using the component.
Understanding: Success Criterion 3.2.2

Test Detail: Provide descriptive labels (G131)

Human input is necessary to verify, that the label describes the purpose of the form control.

About this Test

Checked Elements:form

This test checks, whether the form control has an associated label that could be descriptive.

Short Description

It is important, that the label for any form control makes the control's purpose clear. Using the label element for associating labels with form control allows assistive technology to recognize the label and present it to the user.

How to Repair

Provide a label element with a descriptive text for the form control. Associate the label with the form control, by using the id of the control as the value for the for attribute of the label. Accessible HTML/XHTML Forms: Intermediate Level

Test Detail: Label groups of form elements (H71)

About this Test

Checked Elements:form elements, and input elements of type radio and checkbox, fieldset elements

This test checks:
if there are not more than 8 controls in a form, not grouped by fieldsets.
if related radio buttons and checkboxes are grouped by fieldsets.
if the fieldset has a descriptive label provided by the legend element.

Short Description

form elements
It is necessary to provide a semantic grouping for related form controls. This allows users to understand the relationship of controls and interact with the form more effectively.
Form controls that are logically related (e.g. address fields) should be grouped by enclosing them with a fieldset element. All controls within a given fieldset are then related.

input elements of type radio and checkbox
Grouping controls is most important for related radio buttons and checkboxes, so they can be more easily treated as a single control.

fieldset elements
The first element inside every fieldset should be a legend element, which provides a label or instructions for the group. Often, user agents will present the value of the legend before the label of each control, to remind users that the same group

How to Repair

For form elements
Add a fieldset element around every related group of form controls. Provide a descriptive legend element as the first element of the fieldset that states the meaning of, or instructions for the enclosed elements.

For input elements of type radio and checkbox
A set of radio buttons or checkboxes is related when they all submit values for a single named field. Such groups and other groups of logically related form controls must be grouped by a fieldset element.
Add a fieldset element around every related group of radio buttons and checkboxes. Provide a descriptive legend element as the first element of the fieldset that states the meaning of, or instructions for the enclosed elements.

Test Detail: Define ids for elements (SC4-1-1-id)

About this Test

Checked Elements:Elements with a defined id attribute

This test checks, if the values of the id attributes are unique.

Short Description

IDs have to be unique. When id attribute values are not unique, they are particularly problematic when referenced by labels, headers in data tables, or used as fragment identifiers, as user agents do not have enough information to determine essential relationships (i.e., to determine which label goes with which item).

In content implemented using markup languages, elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique, except where the specifications allow these features. Note: Start and end tags that are missing a critical character in their formation, such as a closing angle bracket or a mismatched attribute value quotation mark are not complete.
Understanding: Success Criterion 4.1.1

Test Detail: Reference elements (SC4-1-1-idref)

About this Test

Checked Elements:label[for], *[aria-activedescendant]

This test checks that each element refered to from an idref attribute exists.

Short Description

Select each label element with a for attribute and each element with a aria-activedescendant attribute. Take the attribute with the IDREF (for=""/aria-activedescendant) value as IdrefAttr. There must be an element with the same id with IdrefAttr on the page.

In content implemented using markup languages, elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique, except where the specifications allow these features. Note: Start and end tags that are missing a critical character in their formation, such as a closing angle bracket or a mismatched attribute value quotation mark are not complete.
Understanding: Success Criterion 4.1.1

Test Detail: Provide role name for div/span with event handler (F59)

Scripts are used on div or span controls where there is a role name for div or span

About this Test

Checked Elements:div or span elements

This test checks if event handlers to elements are attached to div and span, a role name is also defined for them.

Short Description

Assistive technologies rely on knowledge of the role and current state of a component in order to provide that information to the user. Many HTML elements have well defined roles, such as links, buttons, text fields, etc. Generic elements such as div and span do not have any predefined roles. When these generic elements are used to create user interface controls in HTML the assistive technology may not have the necessary information to describe and interact with the control. Attaching event handlers to elements that are not normally interactive, such as span and div, can be disorienting to users. Even if care is taken to provide keyboard access to such elements, users may have a difficult time discovering that there are interactive controls in the content or understanding what type of behavior to expect from them.

For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined ; states, properties, and values that can be set by the user can be programmatically set ; and notification of changes to these items is available to user agents , including assistive technologies . Note: This success criterion is primarily for Web authors who develop or script their own user interface components. For example, standard HTML controls already meet this success criterion when used according to specification. Understanding: Success Criterion 4.1.2

For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined ; states, properties, and values that can be set by the user can be programmatically set ; and notification of changes to these items is available to user agents , including assistive technologies . Note: This success criterion is primarily for Web authors who develop or script their own user interface components. For example, standard HTML controls already meet this success criterion when used according to specification. Understanding: Success Criterion 4.1.2

Test Detail: Accessible name for image links (F89)

About this Test

Checked Elements:a[@href] elements

This test checks, if a name for the link is provided by its title or content.

Short Description

The name of an a element is provided by the text associated with that element. This text provides a name for the link so users are able to understand the purpose of each link and can decide whether they want to follow it.
The text associatetd with a link is the value of the title attribute, the text within the a element and the alt attribute if the link contains an image.

For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined ; states, properties, and values that can be set by the user can be programmatically set ; and notification of changes to these items is available to user agents , including assistive technologies . Note: This success criterion is primarily for Web authors who develop or script their own user interface components. For example, standard HTML controls already meet this success criterion when used according to specification. Understanding: Success Criterion 4.1.2

For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined ; states, properties, and values that can be set by the user can be programmatically set ; and notification of changes to these items is available to user agents , including assistive technologies . Note: This success criterion is primarily for Web authors who develop or script their own user interface components. For example, standard HTML controls already meet this success criterion when used according to specification. Understanding: Success Criterion 4.1.2