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.
Fail, Verify and Pass results are not displayed.
12
Use alt on img elements [1.1.1]
69
Use of Color [1.4.1]
1
Provide descriptive titles for web pages [2.4.2]
1
Provide links to navigate to related Web pages [2.4.5]
52
Provide descriptive headings [2.4.6]
1
Primary language of page [3.1.1]
1
Use identical xml:lang and lang attributes [3.1.1]
2
Languages within the body [3.1.2]
2
,
2
Language of Parts [3.1.2]
1
Provide a submit button to initiate a change of context [3.2.2]
4
Provide descriptive labels [3.3.2]
1
Label groups of form elements [3.3.2]
388
,
117
Define ids for elements [4.1.1]
4
Reference elements [4.1.1]
471
Provide role name for div/span with event handler [4.1.2]
89
,
2
Use HTML form controls and links [4.1.2]
11
Accessible name for image links [4.1.2]
1
Use the title for frame and iframe elements [4.1.2]
Select a test to display the details
(Test for Success Criterion 1.1.1: Non-text Content:)
img has alt
(12 occurences)
Images have alt attribute
Checked Elements: img
This test checks to see that all images actually have alt-tags.
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:In development. This information will be added shortly
(Test for Success Criterion 1.4.1: Use of Color)
Suitable difference between the attributes of link and the surrounding text.
(69 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.
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.
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 ColorIn development. This information will be added shortly
(Test for Success Criterion 2.4.2: Page Titled)
Please check the title of the page
(1 occurrence)
Human input is necessary to verify, that the title describes the content of the page.
Checked Elements: title
This test checks, whether the title of the web page identifies the contents or purpose of the page.
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 TitledProvide 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).
(Test for Success Criterion 2.4.5: Multiple Ways)
G125-pass1
(1 occurrence)
G125-pass1
Checked Elements: all
In development. This information will be added shortly
In development. This information will be added shortly
Understanding Success Criterion 2.4.5: Multiple WaysIn development. This information will be added shortly
(Test for Success Criterion 2.4.6: Headings and Labels)
Please check the heading
(52 occurences)
Human input is necessary to verify, that the heading describes the section it belongs to.
Checked Elements: h1-h6
This test checks, whether the headings identify their section of the content.
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 LabelsProvide 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 for Success Criterion 3.1.1: Language of Page)
Primary language detected correctly
(1 occurrence)
The primary language of the web content can be programmatically determined
Checked Elements: html element
This test checks that the primary language of the web content can be programmatically determined.
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
Use the
If you use both attributes, their values have to be the same.
(Test for Success Criterion 3.1.1: Language of Page)
Same lang attributes available to xml:lang
(1 occurrence)
The value of the xml:lang attribute is equal to lang attribute of html element
Checked Elements: html
This test checks the value of the xml:lang attribute.
If element contains an xml:lang attribute exists on a page, it should contain also a lang attribute with the same value.
Understanding Success Criterion 3.1.1: Language of Page
Use the
If you use
(Test for Success Criterion 3.1.2: Language of Parts)
Correct lang attributes
(2 occurences)
The lang attributes of elements within the body of the page are correct.
Checked Elements: descendent-or-self::body[@lang]
This test checks that lang attributes within the body of a web page are correct
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
Understanding Success Criterion 3.1.2: Language of PartsThe language of an element can be specified by its lang attributes.
(Test for Success Criterion 3.1.2: Language of Parts)
No lang is specified
(2 occurences)
The xml:lang is specified for the element but no lang attribute found
Code
<span xml:lang="" id="Copyright_Statement">
Code
<div id="viewLegContents" xml:lang="en">
Element with equal lang and xml:lang
(2 occurences)
The element contains a lang attribute with the same value to xml:lang.
Checked Elements: descendent-or-self::body[@xml:lang]
This test checks the value of the xml:lang attributes.
If an element has xml:lang attribute, it should also contains a lang attribute with the same value.
Understanding Success Criterion 3.1.2: Language of PartsThe language of an element can be specified by its lang and xml:lang(optional) attributes.
If you use
(Test for Success Criterion 3.2.2: On Input)
Please check that implicit changes of context are described
(1 occurrence)
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.
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").
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 InputIn development. This information will be added shortly
(Test for Success Criterion 3.3.2: Labels or Instructions)
Please check the label
(4 occurences)
Human input is necessary to verify, that the label describes the purpose of the form control.
Checked Elements: form
This test checks, whether the form control has an associated label that could be descriptive.
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 InstructionsProvide 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 for Success Criterion 3.3.2: Labels or Instructions)
The form seems to be structured correctly
(1 occurrence)
There are no more than 8 form controls not grouped by fieldsets.
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.
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
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
(Test for Success Criterion 4.1.1: Parsing)
The id is not unique
(117 occurences)
The ID of this element has occurred before on this page
Code
<span class="LegDS LegLHS LegP3No" id="schedule-2-paragraph-9-1-b">
Code
<span class="LegDS LegLHS LegP3No" id="schedule-2-paragraph-9-1-a">
Code
<span class="LegDS LegLHS LegP3No" id="schedule-2-paragraph-7-2-c">
Code
<span class="LegDS LegLHS LegP3No" id="schedule-2-paragraph-7-2-b">
Code
<span class="LegDS LegLHS LegP3No" id="schedule-2-paragraph-7-2-a">
Code
<span class="LegDS LegLHS LegP3No" id="schedule-2-paragraph-7-1-b">
Code
<span class="LegDS LegLHS LegP3No" id="schedule-2-paragraph-7-1-a">
Code
<span class="LegDS LegLHS LegP3No" id="schedule-2-paragraph-5-1-b">
Code
<span class="LegDS LegLHS LegP3No" id="schedule-2-paragraph-5-1-a">
Code
<span class="LegDS LegLHS LegP3No" id="schedule-2-paragraph-4-2-b">
Code
<span class="LegDS LegLHS LegP3No" id="schedule-2-paragraph-4-2-a">
Code
<span class="LegDS LegLHS LegP3No" id="schedule-2-paragraph-4-1-b">
Code
<span class="LegDS LegLHS LegP3No" id="schedule-2-paragraph-4-1-a">
Code
<span class="LegDS LegLHS LegP3No" id="schedule-2-paragraph-3-6-b">
Code
<span class="LegDS LegLHS LegP4No" id="schedule-2-paragraph-3-6-a-iii">
Code
<span class="LegDS LegLHS LegP4No" id="schedule-2-paragraph-3-6-a-ii">
Code
<span class="LegDS LegLHS LegP4No" id="schedule-2-paragraph-3-6-a-i">
Code
<span class="LegDS LegLHS LegP3No" id="schedule-2-paragraph-3-6-a">
Code
<span class="LegDS LegLHS LegP3No" id="schedule-2-paragraph-3-4-b">
Code
<span class="LegDS LegLHS LegP3No" id="schedule-2-paragraph-3-4-a">
Code
<span class="LegDS LegLHS LegP3No" id="schedule-2-paragraph-3-3-b">
Code
<span class="LegDS LegLHS LegP3No" id="schedule-2-paragraph-3-3-a">
Code
<span class="LegDS LegLHS LegP4No" id="schedule-2-paragraph-2-5-c-ii">
Code
<span class="LegDS LegLHS LegP4No" id="schedule-2-paragraph-2-5-c-i">
Code
<span class="LegDS LegLHS LegP3No" id="schedule-2-paragraph-2-5-c">
Code
<span class="LegDS LegLHS LegP3No" id="schedule-2-paragraph-2-5-b">
Code
<span class="LegDS LegLHS LegP3No" id="schedule-2-paragraph-2-5-a">
Code
<span class="LegDS LegLHS LegP3No" id="schedule-2-paragraph-2-3-g">
Code
<span class="LegDS LegLHS LegP3No" id="schedule-2-paragraph-2-3-f">
Code
<span class="LegDS LegLHS LegP3No" id="schedule-2-paragraph-2-3-e">
Code
<span class="LegDS LegLHS LegP3No" id="schedule-2-paragraph-2-3-d">
Code
<span class="LegDS LegLHS LegP3No" id="schedule-2-paragraph-2-3-c">
Code
<span class="LegDS LegLHS LegP3No" id="schedule-2-paragraph-2-3-b">
Code
<span class="LegDS LegLHS LegP3No" id="schedule-2-paragraph-2-3-a">
Code
<span class="LegDS LegLHS LegP3No" id="schedule-2-paragraph-2-2-c">
Code
<span class="LegDS LegLHS LegP3No" id="schedule-2-paragraph-2-2-b">
Code
<span class="LegDS LegLHS LegP3No" id="schedule-2-paragraph-2-2-a">
Code
<span class="LegDS LegLHS LegP3No" id="schedule-2-paragraph-13-3-d">
Code
<span class="LegDS LegLHS LegP3No" id="schedule-2-paragraph-13-3-c">
Code
<span class="LegDS LegLHS LegP3No" id="schedule-2-paragraph-13-3-b">
Code
<span class="LegDS LegLHS LegP3No" id="schedule-2-paragraph-13-3-a">
Code
<span class="LegDS LegLHS LegP3No" id="schedule-2-paragraph-13-2-b">
Code
<span class="LegDS LegLHS LegP3No" id="schedule-2-paragraph-13-2-a">
Code
<span class="LegDS LegLHS LegP4No" id="schedule-2-paragraph-13-1-b-iii">
Code
<span class="LegDS LegLHS LegP4No" id="schedule-2-paragraph-13-1-b-ii">
Code
<span class="LegDS LegLHS LegP4No" id="schedule-2-paragraph-13-1-b-i">
Code
<span class="LegDS LegLHS LegP3No" id="schedule-2-paragraph-13-1-b">
Code
<span class="LegDS LegLHS LegP3No" id="schedule-2-paragraph-13-1-a">
Code
<span class="LegDS LegLHS LegP3No" id="schedule-2-paragraph-10-3-b">
Code
<span class="LegDS LegLHS LegP3No" id="schedule-2-paragraph-10-3-a">
Code
<span class="LegDS LegLHS LegP3No" id="schedule-2-paragraph-10-2-c">
Code
<span class="LegDS LegLHS LegP3No" id="schedule-2-paragraph-10-2-b">
Code
<span class="LegDS LegLHS LegP3No" id="schedule-2-paragraph-10-2-a">
Code
<span class="LegDS LegLHS LegP3No" id="schedule-2-paragraph-1-3-h">
Code
<span class="LegDS LegLHS LegP3No" id="schedule-2-paragraph-1-3-g">
Code
<span class="LegDS LegLHS LegP3No" id="schedule-2-paragraph-1-3-f">
Code
<span class="LegDS LegLHS LegP3No" id="schedule-2-paragraph-1-3-e">
Code
<span class="LegDS LegLHS LegP3No" id="schedule-2-paragraph-1-3-d">
Code
<span class="LegDS LegLHS LegP3No" id="schedule-2-paragraph-1-3-c">
Code
<span class="LegDS LegLHS LegP3No" id="schedule-2-paragraph-1-3-b">
Code
<span class="LegDS LegLHS LegP3No" id="schedule-2-paragraph-1-3-a">
Code
<span class="LegDS LegLHS LegP3No" id="schedule-2-paragraph-1-2-b">
Code
<span class="LegDS LegLHS LegP3No" id="schedule-2-paragraph-1-2-a">
Code
<span class="LegDS LegLHS LegP3No" id="schedule-2-paragraph-1-1-b">
Code
<span class="LegDS LegLHS LegP3No" id="schedule-2-paragraph-1-1-a">
Code
<span class="LegDS LegLHS LegP3No" id="regulation-9-1-d">
Code
<span class="LegDS LegLHS LegP3No" id="regulation-9-1-c">
Code
<span class="LegDS LegLHS LegP3No" id="regulation-9-1-b">
Code
<span class="LegDS LegLHS LegP3No" id="regulation-9-1-a">
Code
<span class="LegDS LegLHS LegP3No" id="regulation-8-9-c">
Code
<span class="LegDS LegLHS LegP3No" id="regulation-8-9-b">
Code
<span class="LegDS LegLHS LegP3No" id="regulation-8-9-a">
Code
<span class="LegDS LegLHS LegP3No" id="regulation-8-8-b">
Code
<span class="LegDS LegLHS LegP3No" id="regulation-8-8-a">
Code
<span class="LegDS LegLHS LegP3No" id="regulation-8-7-c">
Code
<span class="LegDS LegLHS LegP3No" id="regulation-8-7-b">
Code
<span class="LegDS LegLHS LegP3No" id="regulation-8-7-a">
Code
<span class="LegDS LegLHS LegP3No" id="regulation-8-5-d">
Code
<span class="LegDS LegLHS LegP3No" id="regulation-8-5-c">
Code
<span class="LegDS LegLHS LegP3No" id="regulation-8-5-b">
Code
<span class="LegDS LegLHS LegP3No" id="regulation-8-5-a">
Code
<span class="LegDS LegLHS LegP3No" id="regulation-8-4-b">
Code
<span class="LegDS LegLHS LegP3No" id="regulation-8-4-a">
Code
<span class="LegDS LegLHS LegP3No" id="regulation-8-3-d">
Code
<span class="LegDS LegLHS LegP3No" id="regulation-8-3-c">
Code
<span class="LegDS LegLHS LegP3No" id="regulation-8-3-b">
Code
<span class="LegDS LegLHS LegP3No" id="regulation-8-3-a">
Code
<span class="LegDS LegLHS LegP3No" id="regulation-7-4-b">
Code
<span class="LegDS LegLHS LegP3No" id="regulation-7-4-a">
Code
<span class="LegDS LegLHS LegP3No" id="regulation-7-1-b">
Code
<span class="LegDS LegLHS LegP3No" id="regulation-7-1-a">
Code
<span class="LegDS LegLHS LegP3No" id="regulation-5-b">
Code
<span class="LegDS LegLHS LegP3No" id="regulation-5-a">
Code
<span class="LegDS LegLHS LegP3No" id="regulation-3-1-b">
Code
<span class="LegDS LegLHS LegP3No" id="regulation-3-1-a">
Code
<span class="LegDS LegLHS LegP3No" id="regulation-2-6-b">
Code
<span class="LegDS LegLHS LegP3No" id="regulation-2-6-a">
Code
<span class="LegDS LegLHS LegP3No" id="regulation-2-2-b">
Code
<span class="LegDS LegLHS LegP3No" id="regulation-2-2-a">
Code
<span class="LegDS LegLHS LegP3No" id="regulation-15-2-d">
Code
<span class="LegDS LegLHS LegP3No" id="regulation-15-2-c">
Code
<span class="LegDS LegLHS LegP3No" id="regulation-15-2-b">
Code
<span class="LegDS LegLHS LegP3No" id="regulation-15-2-a">
Code
<span class="LegDS LegLHS LegP3No" id="regulation-15-1-b">
Code
<span class="LegDS LegLHS LegP3No" id="regulation-15-1-a">
Code
<span class="LegDS LegLHS LegP3No" id="regulation-11-5-f">
Code
<span class="LegDS LegLHS LegP3No" id="regulation-11-5-e">
Code
<span class="LegDS LegLHS LegP3No" id="regulation-11-5-d">
Code
<span class="LegDS LegLHS LegP3No" id="regulation-11-5-c">
Code
<span class="LegDS LegLHS LegP3No" id="regulation-11-5-b">
Code
<span class="LegDS LegLHS LegP3No" id="regulation-11-5-a">
Code
<span class="LegDS LegLHS LegP3No" id="regulation-10-3-d">
Code
<span class="LegDS LegLHS LegP3No" id="regulation-10-3-c">
Code
<span class="LegDS LegLHS LegP3No" id="regulation-10-3-b">
Code
<span class="LegDS LegLHS LegP3No" id="regulation-10-3-a">
Code
<span class="LegDS LegLHS LegP3No" id="regulation-10-1-b">
Code
<span class="LegDS LegLHS LegP3No" id="regulation-10-1-a">
The ID is valid
(388 occurences)
The value of the id attribute is unique and syntactically correct.
Checked Elements: Elements with a defined id attribute
This test checks, if the values of the id attributes are unique.
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
IDs are assigned to an element with the
Take care, to also update all references to the old ID.
(Test for Success Criterion 4.1.1: Parsing)
Element referenced correctly
(4 occurences)
Element referenced correctly
Checked Elements: label[for], *[aria-activedescendant]
This test checks that each element refered to from an idref attribute exists.
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: ParsingIn development. This information will be added shortly
(Test for Success Criterion 4.1.2: Name, Role, Value)
div or span has role name
(471 occurences)
Scripts are used on div or span controls where there is a role name for div or span
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.
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, ValueIn development. This information will be added shortly
(Test for Success Criterion 4.1.2: Name, Role, Value)
The link has no name
(2 occurences)
The link has no contents and no title.
Code
<a href="#" />
Code
<a href="http://www.nationalarchives.gov.uk"><span /></a>
H91-pass6
(89 occurences)
H91-pass6
Checked Elements: all
In development. This information will be added shortly
In development. This information will be added shortly
Understanding Success Criterion 4.1.2: Name, Role, ValueIn development. This information will be added shortly
(Test for Success Criterion 4.1.2: Name, Role, Value)
Link name is provided
(11 occurences)
The name of the link can be derived from the image
Checked Elements: a[@href] elements
This test checks, if a name for the link is provided by its title or content.
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, ValueIn development. This information will be added shortly
(Test for Success Criterion 4.1.2: Name, Role, Value)
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.
Code
<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-TWB7339" height="0" width="0" style="display:none;visibility:hidden" />
Checked Elements: frame,iframe
In development. This information will be added shortly
In development. This information will be added shortly
Understanding Success Criterion 4.1.2: Name, Role, ValueIn development. This information will be added shortly