Auditing Your Website
For Compliance Under
The Equality Act 2010 .

1.1.1: Is there an alternative for all 'non-text' content?

1.2.1: Have you provided alternatives for time-based media?

1.2.2: Have you provided captions for all prerecorded audio content?

1.2.3: Have you provided an audio description or media alternative for video content?

1.3.1: Is information, structure and relationships conveyed through mark-up correctly?

1.3.2: Can the correct reading sequence of the content be programmatically determined?

1.3.3: Do instructions for understanding and operating content avoid using shape, size, visual location, orientation or sounds?

1.4.1: Have you avoided the use of colour alone to convey information?

1.4.2: Is it possible to pause or stop automatically playing audio?

2.1.1: Is all content and functionality operable through a keyboard?

2.1.2: Is it possible to move keyboard focus away from all components that can receive it?

2.1.4: Is it possible to turn off keyboard shortcuts?

2.2.1: Can any time limits on content be turned off, adjusted, extended or last longer than 20 hours?

2.2.2: Can any moving, blinking, scrolling or auto-updating content be paused, stopped or hidden?

2.3.1: Is flashing content kept to a minimum e.g. content does not flash more than three times a second?

2.4.1: Is a mechanism for bypassing blocks of content available?

2.4.2: Do all web pages have a title that describes topic and purpose?

2.4.3: Does the focus order follow a logical path preserving meaning and operability?

2.4.4: Is the purpose of each link clear when read in context?

​

2.5.1: Can content be operated using simple inputs on a wide range of pointing devices?

2.5.2: Are events triggered by clicks and taps using the 'up' event?

2.5.3: Is the accessible name of components included in the visible label?

2.5.4: Functionality can be used with motion?

3.1.1: Has the default human language of each page been included?

3.2.1: When a component receives focus, it does not initiate a change of context?

3.2.2: Changing the settings of any user interface component, such as an input, does not automatically cause a change of context?

3.3.1: Are errors identified and described to the user in the text?

3.3.2: Are labels or instructions provided when content requires user input?

4.1.1: Do all pages validate to W3C specifications?

4.1.2: Do all user input components, primarily custom-built scripts and components, conform to W3C specifications?

1.2.4: Are captions available for live audio content?

1.2.5: Have you provided an audio description for video content?

1.3.4: The orientation of the content is not locked.

1.3.5: Are relevant inputs identified with meta-data about the purpose?

1.4.3: Do foreground and background colour combinations meet the requirements for Level AA?

1.4.4: Can text be resized up to 200 per cent without loss of content or functionality?

1.4.5: Has the use of text within images been avoided where possible?

1.4.10: Can users zoom in 400% without causing scrolling in two directions?

1.4.11: Do components and graphics have a contrast ratio of 3:1?

​

1.4.12: Can text Spacing can be increased without loss of content or functionality?

2.2.3: Does any of your content depend on timing as an essential part of the event or activity presented by the content?

2.2.4: Can interruptions be postponed or suppressed by the user?

2.2.5: When an authenticated session expires, can the user re-authenticate and continue without the loss of any data?

2.2.6: Are users warned if timeouts could cause data loss?

2.3.3: Your web pages do not contain any flashing content?

2.3.3: Animation triggered by user interactions can be prevented.

2.4.8: Does each web page clearly indicate the user's location within the web site?

2.4.9: Is the purpose of each link clear when reading out of context?

2.4.10: Have section headings been used to organize content?

2.5.5: Are links and buttons at least 44 CSS pixels?

2.5.6: Content does not prevent different input mechanisms?

3.1.3: Is a mechanism available for identifying unusual words or phrases?

3.1.4: Is a mechanism available for identifying and expanding on abbreviations?

3.1.5: Is text written in a way that it can be understood by everyone and not just people with an advanced education?

3.1.6: Is there a tool for identifying specific pronunciation of ambiguous words?

3.2.5: Changes of context are initiated only by a user request or such changes can be turned off?

3.3.5: Is context-sensitive help available?

3.3.6: Can all data submitted be reversed, checked for errors or reviewed before submission?