Tingtun Page Checker - Find Barriers in your Web Page

eAccessibility/
Page Checker

Checked page:

http://www.legislation.gov.uk/ukpga/2018/16/enacted/data.xht?view=snippet&wrap=true

>Check another page

Time:

2019-12-04T03:56:08Z

Applied Tests:

Total: 9066
Fail: 1638
Verify: 0
Pass: 7428

Score:

94.10

(where 100 is the best)

Link:

/en/pagecheck2.0/?uuid=16b8088f-1391-4e61-befa-fd521895b218

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.

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.

206 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]
163 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 Language of Parts [3.1.2]
1830 , 1638 Define ids for elements [4.1.1]
4587 Provide role name for div/span with event handler [4.1.2]
634 Use HTML form controls and links [4.1.2]

Select a test to display the details

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. (206 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: 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 (163 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: Use identical xml:lang and lang attributes (SC3-1-1-xml-lang)

(Test for Success Criterion 3.1.1: Language of Page)

Results
Test info

Same lang attributes available to xml:lang (1 occurrence): The value of the xml:lang attribute is equal to lang attribute of html element

About this Test

Checked Elements: html

This test checks the value of the xml:lang attribute.

Short Description

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

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 xml:lang you need to add lang with the same value as well.

The value of the lang and xml: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

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-xml-lang
Language Subtag Registry
Authoring HTML: Language declarations

WCAG 2.0

Principle 3: Understandable

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

(Test for Success Criterion 3.1.2: Language of Parts)

Results
Test info

Correct lang attributes (2 occurences): 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

Understanding Success Criterion 3.1.2: Language of Parts

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

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-2-lang
Language Subtag Registry
Authoring HTML: Language declarations

WCAG 2.0

Principle 3: Understandable

Test Detail: Language of Parts (SC3-1-2-xml-lang)

(Test for Success Criterion 3.1.2: Language of Parts)

Results
Test info

Element with equal lang and xml:lang (2 occurences): The element contains a lang attribute with the same value to xml:lang.

About this Test

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

This test checks the value of the xml:lang attributes.

Short Description

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 Parts

How to Repair

The language of an element can be specified by its lang and xml:lang(optional) attributes.
If you use xml:lang for a element you need to add lang attribute with the same value as well.

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-2-xml-lang
Language Subtag Registry
Authoring HTML: Language declarations

WCAG 2.0

Principle 3: Understandable

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

(Test for Success Criterion 4.1.1: Parsing)

Results
Test info

The id is not unique (1638 occurences): The ID of this element has occurred before on this page
The ID is valid (1830 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: 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 (4587 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 a name (634 occurences): The a[@href] element has an associated text.

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