WCAG Compliance

Non-Text Content

Provide text alternatives for non text content that serves the same purpose.

Acceptance Criteria

• Images must also include access to a text description for every language

• The interface will need to allow text to accompany images provided by users

• WCAG 2.1 Level A 1.1.1

• The interface will need to allow text to accompany images provide by users

Audio-only and Video-only Content

Provide an alternative to video-only and audio-only content

Acceptance Criteria

• Videos must also include access to a text description for every language

• The interface will need to allow text to accompany audio and video provided by users

• Videos should include SRT files for different languages or have them embedded in the video file

• WCAG 2.1 Level A 1.2.1

Captions for Video

Provide captions for videos with audio

Acceptance Criteria

• The interface will need to allow text to accompany video provided by users

• Videos must also include access to a text description. 

• Videos should include SRT files for different languages or have them embedded in the video file

• WCAG 2.1 Level A 1.2.2

Audio descriptions for Videos

Provide an alternative for videos with sounds

Acceptance Criteria

• Videos must also include access to a text description for every language

• Videos should include SRT files for different languages or have them embedded in the video file

• WCAG 2.1 Level A 1.2.3

Structure and relationships of content

Provide users with content that has clear structure and relationships

Acceptance Criteria

• Users should perceive structure of content using visual clues e.g.

• Headings in a larger, bold font separated from paragraphs by blank lines;

• list items are preceded by a bullet and perhaps indented;

• paragraphs are separated by a blank line;

• words that have special status are indicated by changing the font family and /or bolding, italicizing, or underlining them

• WCAG 2.1 Level A 1.3.1

Meaningful sequence of content

Present content in a meaningful order

Acceptance Criteria

• Provide a logical order to content

• WCAG 2.1 Level A 1.3.2

• usually top to bottom then left to right for multi column content

Sensory characteristics of content

Use more than one human sense for content e.g shape and color to guide the user to content. 

Acceptance Criteria

• Navigation items like buttons and links should have shape and colour rather than writing phrases like "to the left", see above or below

• WCAG 2.1 Level A 1.3.3

• People who are blind and people who have low vision may not be able to understand information if it is conveyed by shape and/or location. Providing additional information other than shape and/or location will allow them to understand the information conveyed by shape and/or alone

Use of Colour

Don't present material that only uses colour

Acceptance Criteria

• The information should be accessible in monochrome or similar visual ways

• WCAG 2.1 Level A 1.4.1

• Users with partial sight often experience limited color vision.

• Some older users may not be able to see color well.

• Users who have color-blindness benefit when information conveyed by color is available in other visual ways.

• People using text-only, limited color, or monochrome displays may be unable to access color-dependent information.

• Users who have problems distinguishing between colors can look or listen for text cues.

• People using Braille displays or other tactile interfaces can detect text cues by touch.

Audio Control

Don't play audio automatically

Acceptance Criteria

• A mechanism is available to pause or stop the audio

• WCAG 2.1 Level A 1.4.2

Keyboard Control

Accessible by keyboard only

Acceptance Criteria

• Allow access by keyboard only

• WCAG 2.1 Level A 2.1.1

• People who are blind (who cannot use devices such as mice that require eye-hand coordination)

• People with low vision (who may have trouble finding or tracking a pointer indicator on screen)

• Some people with hand tremors find using a mouse very difficult and therefore usually use a keyboard

No keyboard Trap

Don't trap keyboard users

Acceptance Criteria

• Ensure that that content does not "trap" keyboard focus within subsections of content on a Web page. 

• WCAG 2.1 Level A 2.1.2

• This is a common problem when multiple formats are combined within a page and rendered using plug-ins or embedded applications.

Character key shortcuts

Provide users with a way to turn off or remap character key shortcuts

Acceptance Criteria

• Avoid character key shortcuts

• WCAG 2.1 Level A 2.1.4

• This is a new requirement in 2.1 so there is little supporting information

Timing adjustable

Time limits have user controls

Acceptance Criteria

• Avoid using time limits

• WCAG 2.1 Level A 2.2.1

• People with physical disabilities often need more time to react, to type and to complete activities. People with low vision need more time to locate things on screen and to read

Pause, Stop, Hide

Provide user controls for moving content

Acceptance Criteria

• Allow users to pause and stop content

• WCAG 2.1 Level A 2.2.2

• The intent of this Success Criterion is to avoid distracting users during their interaction with a Web page

Three flashes or Below

No content flash more than three times per second

Acceptance Criteria

• All content not to flash more than 3 times per second

• WCAG 2.1 Level A 2.3.1

• The intent of this Success Criterion is to allow users to access the full content of a site without inducing seizures due to photosensitivity.

Bypass Blocks

Provide a "skip to content" link

Acceptance Criteria

• Provide a mechanism is available to bypass blocks of content that are repeated on multiple Web pages

• WCAG 2.1 Level A 2.4.1

Page Titled

Helpful and clear page title

Acceptance Criteria

• All web pages have titles that describe topic or purpose

• WCAG 2.1 Level A 2.4.2

• This criterion benefits all users in allowing users to quickly and easily identify whether the information contained in the Web page is relevant to their needs.

• People with visual disabilities will benefit from being able to differentiate content when multiple Web pages are open.

Focus order

Logical order for focus components on a web page

Acceptance Criteria

• If a web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability

• WCAG 2.1 Level A 2.4.3

Link Purpose

The purpose of every link is clear from its context

Acceptance Criteria

• The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general

• WCAG 2.1 Level A 2.4.4

• This Success Criterion helps people with motion impairment by letting them skip links that they are not interested in, avoiding the keystrokes needed to visit the referenced content and then returning to the current content.

• People with cognitive limitations will not become disoriented by multiple means of navigation to and from content they are not interested in.

• People with visual disabilities will be able to determine the purpose of a link by exploring the link's context

Pointer Gestures

Avoid or provide alternatives for multipoint or path-based gestures

Acceptance Criteria

• Avoid using multi finger gestures

• Avoid using swipe gestures

• WCAG 2.1 Level A 2.5.1

• This is a new requirement in 2.1 so there is little supporting information

Pointer Cancellation

Don't complete functions on the down-click of a pointer

Acceptance Criteria

• all actions are completed on the up-click of a pointer

• WCAG 2.1 Level A 2.5.2

• This is a new requirement in 2.1 so there is little supporting information

Label in Name

Where an element has a text label, present the same label in the accessible name

Acceptance Criteria

• provide the text label in the HTML accessible name

• WCAG 2.1 Level A 2.5.3

• This is a new requirement in 2.1 so there is little supporting information

Motion Actuation

Functions that are operated by motion can also be operated by interface

Acceptance Criteria

• Avoid functions operated by motion

• WCAG 2.1 Level A 2.5.4

• This is a new requirement in 2.1 so there is little supporting information

Language of Page

Page has a language assigned

Acceptance Criteria

• All pages have a language assigned

• WCAG 2.1 Level A 3.1.1

On focus

Elements do not change when they receive focus

Acceptance Criteria

• When any component receives focus, it does not initiate a change of context

• WCAG 2.1 Level A 3.2.1

On Input

Elements do not change when they receive input

Acceptance Criteria

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

• WCAG 2.1 Level A 3.2.2

Error Identification

Clearly identify input errors

Acceptance Criteria

• Help users avoid and correct mistakes

• WCAG 2.1 Level A 3.3.1

• Everyone makes mistakes. However, people with some disabilities have more difficulty creating error-free input. In addition, it may be harder for them to detect that they have made an error. Typical error indication methods may not be obvious to them because of a limited field of view, limited color perception, or use of assistive technology. This guideline seeks to reduce the number of serious or irreversible errors that are made, increase the likelihood that all errors will be noticed by the user, and help users understand what they should do to correct an error.

Labels or Instructions

Label elements and give instructions

Acceptance Criteria

• Labels or instructions are provided when content requires user input

• WCAG 2.1 Level A 3.3.2

Parsing

No major code errors

Acceptance Criteria

• Maximize compatibility with current and future user agents, including assistive technologies.

• Avoid deprecated features of W3C technologies

• WCAG 2.1 Level A 4.1.1

Name, role, value

Build all elements for accessibility

Acceptance Criteria

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

• WCAG 2.1 Level A 4.1.2

Additional scope 1

WACG: additional guidelines aside from Level A compliance as describe in Mobile Accessibility: How WCAG 2.0 and Other W3C/WAI Guidelines Apply to Mobile

• see points (3.1, 3.3, 3.4, 4.3, 4.6) applied (where relevant)

• see "practical best practices" included without compliance but as attention points

Additional scope 2

WACG: additional Level AA/AAA compliance as describe in as describe in Mobile Accessibility: How WCAG 2.0 and Other W3C/WAI Guidelines Apply to Mobile

• see points (2.2, 3.1, 4.3, 5.3) applied (where relevant)