eAccessibility/
Page Checker

442 barriers found on the web page

Checked page:
http://www.dohabank.com.qa/1/en/MediaCenter/PressRoom/tabid/631/articleType/ArticleView/articleId/226/Doha-Bank-Attracts-Qatari-Nationals-at-the-Career-Fair.aspx
>Check another page
Time: 2016-01-25T18:49:30Z
Applied Tests:
- Total: 1391
- Fail: 442
- Verify: 0
- Pass: 949
Score:
75.99 (where 100 is the best)
Link: /en/pagecheck2.0/?uuid=a4c0a5bb-df95-4883-bc2a-09310f622afd

Disclaimer

Please note that the scores are only based on tests carried out automatically. About 20% of the conceivable tests can be automated, and the Tingtun Checker tool covers a part of these tests. Therefore, the evaluated pages may contain barriers not found by the Tingtun checkers. For reference see the list of currently implemented tests, and the list of specified tests. Full disclaimer.

Result Details

Applied Automatic Tests
Occurrences
WCAG 2.0 context

Show

Fail Verify Pass

Applied Automatic Tests

Fail, Verify and Pass results are not displayed.

69 , 278 Use alt on img elements [1.1.1]
31 Use of Color [1.4.1]
3 , 156 Use of pointing-device-specific only event handlers [2.1.1]
1 Provide descriptive titles for web pages [2.4.2]
1 Provide links to navigate to related Web pages [2.4.5]
2 Provide descriptive headings [2.4.6]
1 Primary language of page [3.1.1]
1 Provide a submit button to initiate a change of context [3.2.2]
1 Submit forms without submit buttons [3.2.2]
5 , 2 Provide descriptive labels [3.3.2]
1 , 1 Label groups of form elements [3.3.2]
678 Define ids for elements [4.1.1]
5 Reference elements [4.1.1]
98 Provide role name for div/span with event handler [4.1.2]
46 , 1 Use HTML form controls and links [4.1.2]
1 Accessible name for image links [4.1.2]
2 Title attribute to identify controls [4.1.2]
1 , 1 Use the title for frame and iframe elements [4.1.2]
5 Use label elements to associate text labels with form controls [4.1.2]

Select a test to display the details

Test Detail: Use alt on img elements (H37)

(Test for Success Criterion 1.1.1: Non-text Content:)

Results
Test info

img has no alt (278 occurences): Images have not alt attribute
img has alt (69 occurences): Images have alt attribute

About this Test

Checked Elements: img

This test checks to see that all images actually have alt-tags.

Short Description

For each img element a short and descriptive text alternative (alt text) with the alt attribute should be specified.

Understanding Success Criterion 1.1.1: Non-text Content:

How to Repair

In development. This information will be added shortly

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.)
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.

Understanding: Success Criterion 1.1.1

Techniques

H37: Using alt attributes on img elements

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

(Test for Success Criterion 1.4.1: Use of Color)

Results
Test info

Suitable difference between the attributes of link and the surrounding text. (31 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.

Understanding Success Criterion 1.4.1: Use of Color

How to Repair

In development. This information will be added shortly

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.4: Distinguishable:

Make it easier for users to see and hear content including separating foreground from background.
Understanding Guideline 1.4

Success Criterion 1.4.1: Use of Color (Level A)

Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.
Understanding: Success Criterion 1.4.1

Techniques

F73: Failure of Success Criterion 1.4.1 due to creating links that are not visually evident without color vision
G183: Using a contrast ratio of 3:1 with surrounding text and providing additional visual cues on focus for links or controls where color alone is used to identify them

Test Detail: Use of pointing-device-specific only event handlers (F54)

(Test for Success Criterion 2.1.1: Keyboard)

Results
Test info

Using only pointing-device-specific event handlers for a function (156 occurences): Pointing-device-specific event handlers are the only means to invoke scripting functions
(In development. This information will be added shortly) (3 occurences): (In development. This information will be added shortly)

About this Test

Checked Elements: all

Using only pointing-device-specific event handlers for a function

Short Description

If an element has attributes among: "onclick", "ondblclick", "onmousedown", "onmousemove", "onmouseover", "onmouseout", "onmouseup"
then the element should have one of attributes among "onkeypress", "onkeyup", "onkeydown", "onfocus", "onblur".
Otherwise the test would fail.

Understanding Success Criterion 2.1.1: Keyboard

How to Repair

In development. This information will be added shortly

WCAG 2.0

Principle 2: Operable

User interface components and navigation must be operable.
WCAG 2.0: Principle 2

Guideline 2.1: Keyboard

Make all functionality available from a keyboard.
Understanding Guideline 2.1

Success Criterion 2.1.1: Keyboard (Level A)

All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints. (Level A)
Note 1: This exception relates to the underlying function, not the input technique. For example, if using handwriting to enter text, the input technique (handwriting) requires path-dependent input but the underlying function (text input) does not.
Note 2: This does not forbid and should not discourage providing mouse input or other input methods in addition to keyboard operation.
Understanding: Success Criterion 2.1.1

Technique

F54: Failure of Success Criterion 2.1.1 due to using only pointing-device-specific event handlers (including gesture) for a function

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

(Test for Success Criterion 2.4.2: Page Titled)

Results
Test info

Please check the title of the page (1 occurrence): 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.

Understanding Success Criterion 2.4.2: Page Titled

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.
Writing Better Web Page Titles

WCAG 2.0

Principle 2: Operable

User interface components and navigation must be operable. WCAG 2.0: Principle 2

Guideline 2.4: Navigable

Provide ways to help users navigate, find content, and determine where they are. Understanding Guideline 2.4

Success Criterion 2.4.2: Page Titled (Level A)

Web pages have titles that describe topic or purpose. Understanding: Success Criterion 2.4.2

Technique

F25 - Failure of Success Criterion 2.4.2 due to the title of a Web page not identifying the contents

Test Detail: Provide links to navigate to related Web pages (G125)

(Test for Success Criterion 2.4.5: Multiple Ways)

Results
Test info

G125-pass1 (1 occurrence): G125-pass1

About this Test

Checked Elements: all

In development. This information will be added shortly

Short Description

In development. This information will be added shortly

Understanding Success Criterion 2.4.5: Multiple Ways

How to Repair

In development. This information will be added shortly

WCAG 2.0

Principle 2: Operable

User interface components and navigation must be operable. WCAG 2.0: Principle 2

Guideline 2.4: Navigable

Provide ways to help users navigate, find content, and determine where they are. Understanding Guideline 2.4

Success Criterion 2.4.5: Multiple Ways (Level AA)

More than one way is available to locate a Web page within a set of Web pages except where the Web Page is the result of, or a step in, a process. Understanding: Success Criterion 2.4.5

Techniques

G125 - Providing links to navigate to related Web pages

Test Detail: Provide descriptive headings (G130)

(Test for Success Criterion 2.4.6: Headings and Labels)

Results
Test info

Please check the heading (2 occurences): 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.

Understanding Success Criterion 2.4.6: Headings and Labels

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

WCAG 2.0

Principle 2: Operable

User interface components and navigation must be operable. WCAG 2.0: Principle 2

Guideline 2.4: Navigable

Provide ways to help users navigate, find content, and determine where they are. Understanding Guideline 2.4

Success Criterion 2.4.6: Headings and Labels (Level AA)

Headings and labels describe topic or purpose. Understanding: Success Criterion 2.4.6

Technique

G130 - Providing descriptive headings

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

(Test for Success Criterion 3.1.1: Language of Page)

Results
Test info

Primary language detected correctly (1 occurrence): 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

Understanding Success Criterion 3.1.1: Language of Page

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

nb – for Norwegian Bokmal
nn – for Norwegian Nynorsk
en – for English
en-US – for English as used in the USA

Further Information:

Test description SC3-1-1-html
Language Subtag Registry
Authoring HTML: Language declarations

WCAG 2.0

Principle 3: Understandable

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

(Test for Success Criterion 3.2.2: On Input)

Results
Test info

(In development. This information will be added shortly) (1 occurrence): (In development. This information will be added shortly)

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.

Understanding Success Criterion 3.2.2: On Input

How to Repair

In development. This information will be added shortly

WCAG 2.0

Principle 3: Understandable

Information and the operation of user interface must be understandable.
WCAG 2.0: Principle 3

Guideline 3.3: Input Assistance

Help users avoid and correct mistakes. Understanding Guideline 3.3

Success Criterion 3.2.2: On Input (Level A)

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

Techniques

H32: Providing submit buttons

Test Detail: Submit forms without submit buttons (G13)

(Test for Success Criterion 3.2.2: On Input)

Results
Test info

The form can not be submitted accessibly (1 occurrence): A submit button is missing.

About this Test

Checked Elements: forms without submit buttons

This test checks, if the submission of forms without submit buttons is accessible and predictable.

Short Description

It is necessary to provide a submit button for forms with multiple controls or forms containing other controls than radio buttons, checkboxes or select boxes. If such forms don't have a submit button, changes to controls may lead to unintended submissions and it is difficult to impossible for people using assistive technologies to submit the form.

Understanding Success Criterion 3.2.2: On Input

How to Repair

Add a submit button (input type="submit", input type="image", or button type="submit") to the form.
Make sure that the action specified for the form performs the desired action. Also make sure, that any changes to form elements within the form do not cause a change of context or that any such changes are described before the initiating control.

WCAG 2.0

Principle 3: Understandable

Information and the operation of user interface must be understandable.
WCAG 2.0: Principle 3

Guideline 3.3: Input Assistance

Help users avoid and correct mistakes. Understanding Guideline 3.3

Success Criterion 3.2.2: On Input (Level A)

Techniques

G13 - Describing what will happen before a change to a form control that causes a change of context to occur is made

Test Detail: Provide descriptive labels (G131)

(Test for Success Criterion 3.3.2: Labels or Instructions)

Results
Test info

There is no label to identify the purpose of the form control (2 occurences): There is no label for the form control that could identify its purpose and the alternatively usable title is also missing
Please check the label (5 occurences): 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.

Understanding Success Criterion 3.3.2: Labels or Instructions

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

WCAG 2.0

Principle 2: Operable

User interface components and navigation must be operable. WCAG 2.0: Principle 2

Guideline 2.4: Navigable

Provide ways to help users navigate, find content, and determine where they are. Understanding Guideline 2.4

Success Criterion 2.4.6: Headings and Labels (Level AA)

Headings and labels describe topic or purpose. Understanding: Success Criterion 2.4.6

Technique

G131 - Providing descriptive labels

Test Detail: Label groups of form elements (H71)

(Test for Success Criterion 3.3.2: Labels or Instructions)

Results
Test info

The radio buttons or checkboxes need grouping (1 occurrence): There are related radio buttons or checkboxes (the radio buttons or checkboxes have the same name), that have to be grouped by fieldsets.
The form seems to be structured correctly (1 occurrence): There are no more than 8 form controls not grouped by fieldsets.

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

Understanding Success Criterion 3.3.2: Labels or Instructions

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.

For fieldset elements
Provide a descriptive legend element as the first element of the fieldset. Further information: Accessible Forms using WCAG 2.0

WCAG 2.0

Principle 3: Understandable

Information and the operation of user interface must be understandable.
WCAG 2.0: Principle 3

Guideline 3.3: Input Assistance

Help users avoid and correct mistakes. Understanding Guideline 3.3

Success Criterion 3.3.2: Labels or Instructions (Level A)

Labels or instructions are provided when content requires user input (Level A).
Understanding: Success Criterion 3.3.2

Techniques

H71: Providing a description for groups of form controls using fieldset and legend elements

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

(Test for Success Criterion 4.1.1: Parsing)

Results
Test info

The ID is valid (678 occurences): The value of the id attribute is unique and syntactically correct.

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).

Understanding Success Criterion 4.1.1: Parsing

How to Repair

IDs are assigned to an element with the id attribute. If an ID is not unique, assign a new, unique ID, having the following syntax: ID tokens.

HTML5

id must contain at least one character.
may not contain any space characters.

Others

must begin with a letter ([A-Za-z]) and
may be followed by

any number of letters,
digits ([0-9]),
hyphens ("-"),
underscores ("_"),
colons (":"), and
periods (".").

Take care, to also update all references to the old ID.

WCAG 2.0

Principle 4: Robust

Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies.
WCAG 2.0: Principle 4

Guideline 4.1: Compatible

Maximize compatibility with current and future user agents, including assistive technologies.
Understanding Guideline 4.1

Success Criterion 4.1.1: Parsing (Level A)

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

Techniques

H93: Ensuring that id attributes are unique on a Web page
F77: Failure of Success Criterion 4.1.1 due to duplicate values of type ID

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

(Test for Success Criterion 4.1.1: Parsing)

Results
Test info

Element referenced correctly (5 occurences): Element referenced correctly

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.

Understanding Success Criterion 4.1.1: Parsing

How to Repair

In development. This information will be added shortly

WCAG 2.0

Principle 4: Robust

Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies.
WCAG 2.0: Principle 4

Guideline 4.1: Compatible

Maximize compatibility with current and future user agents, including assistive technologies.
Understanding Guideline 4.1

Success Criterion 4.1.1: Parsing (Level A)

Techniques

H93: Ensuring that id attributes are unique on a Web page
F17 - Failure of Success Criterion 1.3.1 and 4.1.1 due to insufficient information in DOM to determine one-to-one relationships (e.g., between labels with same id) in HTML

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

(Test for Success Criterion 4.1.2: Name, Role, Value)

Results
Test info

div or span has role name (98 occurences): 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.

Understanding Success Criterion 4.1.2: Name, Role, Value

How to Repair

In development. This information will be added shortly

WCAG 2.0

Principle 4: Robust

Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies.
WCAG 2.0: Principle 4

Guideline 4.1: Compatible:

Maximize compatibility with current and future user agents, including assistive technologies.
Understanding Guideline 4.1

Success Criterion 4.1.2: Name, Role, Value (Level A)

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

Techniques

F59: Failure of Success Criterion 4.1.2 due to using script to make div or span a user interface control in HTML without providing a role for the control

Test Detail: Use HTML form controls and links (H91)

(Test for Success Criterion 4.1.2: Name, Role, Value)

Results
Test info

The link has no name (1 occurrence): The link has no contents and no title.
H91-pass6 (46 occurences): H91-pass6

About this Test

Checked Elements: all

In development. This information will be added shortly

Short Description

In development. This information will be added shortly

Understanding Success Criterion 4.1.2: Name, Role, Value

How to Repair

In development. This information will be added shortly

WCAG 2.0

Principle 4: Robust

Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies.
WCAG 2.0: Principle 4

Guideline 4.1: Compatible:

Maximize compatibility with current and future user agents, including assistive technologies.
Understanding Guideline 4.1

Success Criterion 4.1.2: Name, Role, Value (Level A)

Techniques

H91: Using HTML form controls and links

Test Detail: Accessible name for image links (F89)

(Test for Success Criterion 4.1.2: Name, Role, Value)

Results
Test info

Link name is provided (1 occurrence): The name of the link can be derived from the image

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.

Understanding Success Criterion 4.1.2: Name, Role, Value

How to Repair

In development. This information will be added shortly

WCAG 2.0

Principle 4: Robust

Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies.
WCAG 2.0: Principle 4

Guideline 4.1: Compatible:

Maximize compatibility with current and future user agents, including assistive technologies.
Understanding Guideline 4.1

Success Criterion 4.1.2: Name, Role, Value (Level A)

Techniques

F89 - Failure of Success Criteria 2.4.4, 2.4.9 and 4.1.2 due to using null alt on an image where the image is the only content in a link

Test Detail: Title attribute to identify controls (H65)

(Test for Success Criterion 4.1.2: Name, Role, Value)

Results
Test info

The form control has no name (2 occurences): The input element of type radio, checkbox, file, text or password, the select element or the textarea has no title and no associated label.

About this Test

Checked Elements: input[@type='radio'], input[@type='checkbox'], input[@type='file'], input[@type='text'], input[@type='password'], select or textarea elements

This test checks, if a name for the form control is provided by an associated label or its title attribute.

Short Description

The name of an input element of type radio, checkbox, file, text or password, a select element or a textarea is provided by its associated label element or its title attribute. This text provides a name for the form control so users are able to understand its purpose and can decide what to insert or select.

Understanding Success Criterion 4.1.2: Name, Role, Value

How to Repair

Add a label element and associate it with the form control by referencing the id of the control as the value of the for attribute of the label.

The text of the label should describe the purpose of the contol unambiguously. For radio buttons and checkboxes place the label after the form control, for all others place the label before the form control.

Further information: Accessible HTML/XHTML Forms: Intermediate Level

Note: It is also possible to name form controls with their title attribute, but this practice is not recommended and should only be applied if there is no room for a label element in the layout.

WCAG 2.0

Principle 3: Understandable

Information and the operation of user interface must be understandable.
WCAG 2.0: Principle 3

Guideline 3.3: Input Assistance

Help users avoid and correct mistakes. Understanding Guideline 3.3

Success Criterion 3.3.2: Labels or Instructions (Level A)

Labels or instructions are provided when content requires user input (Level A).
Understanding: Success Criterion 3.3.2

Techniques

H65 - Using the title attribute to identify form controls when the label element cannot be used

Test Detail: Use the title for frame and iframe elements (H64)

(Test for Success Criterion 4.1.2: Name, Role, Value)

Results
Test info

The name of the frame is missing (1 occurrence): The name of the frame or iframe is not defined, because the title attribute is missing.
Please check the name of the frame (1 occurrence): Human input is necessary to verify, that the title of the frame or iframe describes its contents.

About this Test

Checked Elements: frame,iframe

In development. This information will be added shortly

Short Description

In development. This information will be added shortly

Understanding Success Criterion 4.1.2: Name, Role, Value

How to Repair

In development. This information will be added shortly

WCAG 2.0

Principle 4: Robust

Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies.
WCAG 2.0: Principle 4

Guideline 4.1: Compatible:

Maximize compatibility with current and future user agents, including assistive technologies.
Understanding Guideline 4.1

Success Criterion 4.1.2: Name, Role, Value (Level A)

Techniques

H64: Using the title attribute of the frame and iframe elements

Test Detail: Use label elements to associate text labels with form controls (H44)

(Test for Success Criterion 4.1.2: Name, Role, Value)

Results
Test info

Please check the name of the form control is set correctly (5 occurences): The label for the input element of type radio, checkbox, file, text or password, the select element or the textarea is at a position which needs to be checked.

About this Test

Checked Elements: all

This test check if label for the input element of type radio, checkbox, file, text or password, the select element or the textarea is at a correct position.

Short Description

The objective of this technique is to use the label element to explicitly associate a form control with a label. This test check if label for the input element of type radio, checkbox, file, text or password, the select element or the textarea is at a correct position.

Understanding Success Criterion 4.1.2: Name, Role, Value

How to Repair

In development. This information will be added shortly

WCAG 2.0

Principle 4: Robust

Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies.
WCAG 2.0: Principle 4

Guideline 4.1: Compatible:

Maximize compatibility with current and future user agents, including assistive technologies.
Understanding Guideline 4.1

Success Criterion 4.1.2: Name, Role, Value (Level A)

Techniques

H44: Using label elements to associate text labels with form controls