1465 barriers found on the web page

Checked page:
http://www.legislation.gov.uk/anaw/2016/3
>Check another page
Time: 2019-12-04T03:56:08Z
Applied Tests:
- Total: 8226
- Fail: 1465
- Verify: 0
- Pass: 6761
Score:
92.95 (where 100 is the best)
Link: /en/pagecheck2.0/?uuid=3f35c9c4-c369-433e-81fd-8080b8cf25a6

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

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 alt (20 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. (98 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.

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.

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

Test Detail: Provide descriptive headings (G130)

(Test for Success Criterion 2.4.6: Headings and Labels)

Results
Test info

Please check the heading (228 occurences): Human input is necessary to verify, that the heading describes the section it belongs to.

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:

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

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 (3 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:

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

No lang is specified (2 occurences): The xml:lang is specified for the element but no lang attribute found
Element with equal lang and xml:lang (3 occurences): The element contains a lang attribute with the same value to xml:lang.

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

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.

Test Detail: Provide descriptive labels (G131)

(Test for Success Criterion 3.3.2: Labels or Instructions)

Results
Test info

Please check the label (4 occurences): Human input is necessary to verify, that the label describes the purpose of the form control.

Test Detail: Label groups of form elements (H71)

(Test for Success Criterion 3.3.2: Labels or Instructions)

Results
Test info

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 not unique (1452 occurences): The ID of this element has occurred before on this page