Accessibility checklist

This accessibility checklist has been created to aid in testing a websites level of compliance with Aviva‘s accessibility policy. These check points must all be adhered to, in order to comply with Aviva‘s accessibility policy.

Atmosphere

Colour

Foreground and background colour combinations must provide sufficient contrast

Guideline 1.4.3 complies with WCAG AA. WGAG guideline 1.4.3

Any background used must be simple enough to not impair the legibility of content overlayed upon it

Guideline 1.4.3 complies with WCAG AA. WGAG guideline 1.4.3

Colour must not be solely relied on to present information, indicate actions or visually distinguish elements

Guideline 1.4.1 complies with WCAG A. WGAG guideline 1.4.1

Ensure foreground and background colours are able to be overridden by the user

Guideline 1.4.8 complies with WCAG AAA. WGAG guideline 1.4.8

Content

A text equivalent must be provided for every non–text element conveying what is important or relevant about the element. This can be achieved using the alt attribute for images.

Guideline 1.1.1 complies with WCAG A. WGAG guideline 1.1.1

Instructions must not rely upon shape, size or visual location

Guideline 1.3.3 complies with WCAG A. WGAG guideline 1.3.3

Always specify the primary language of the HTML document

Guideline 3.1.1 complies with WCAG A. WGAG guideline 3.1.1

Identify any changes in the natural language of the content using the lang attribute

Guideline 3.1.2 complies with WCAG AA. WGAG guideline 3.1.2

If abbreviations or acronyms are used the full expansion must be displayed where it is first documented

Guideline 3.1.4 complies with WCAG AAA. WGAG guideline 3.1.4

More understandable content must be provided for content that has a more advanced reading age of roughly nine years

Guideline 3.1.5 complies with WCAG AAA. WGAG guideline 3.1.5

A mechanism should be available for identifying specific pronunciation of words where meaning cannot be determined without pronunciation

Guideline 3.1.6 complies with WCAG AAA. WGAG guideline 3.1.6

All the content on the page must be marked up in the appropriate semantic elements, structural mark–up must not be used purely for visual effects

Guideline 4.1.1 complies with WCAG A. WGAG guideline 4.1.1

Deprecated elements such as <font> and <applet> must not be used, instead use CSS or the latest versions if applicable

Guideline 4.1.1 complies with WCAG A. WGAG guideline 4.1.1

iframes must not be used.

Guideline 4.1.1 complies with WCAG A. WGAG guideline 4.1.1

ARIA states, properties and live regions should be used on scripted content and components

Guideline 4.1.2 complies with WCAG A. WGAG guideline 4.1.2

Headings and labels, where they exist, should describe the content within the following section; this refers to text content rather than within the code

Guideline 2.4.6 complies with WCAG AA. WGAG guideline 2.4.6

Appropriate headings should be used to organise different sections of content on a page; this refers to actual topic or chapter titles within the content rather than within the code

Guideline 2.4.10 complies with WCAG AAA. WGAG guideline 2.4.10

Specialist or technical words and phrases should be used sparingly and explained in clear language when necessary; this includes any use of non-native words or phrases within a page

Guideline 3.1.3 complies with WCAG AAA. WGAG guideline 3.1.3

Input devices

The user must be able to navigate and interact with the content on the web page using only a keyboard or keyboard emulator

Guideline 2.1.1 complies with WCAG A. WGAG guideline 2.1.1

If a user can focus on a part of the web page using the keyboard they must also be able to move away using the keyboard. If the user cannot use standard exit methods, you need to include instructions on how to do so

Guideline 2.1.2 complies with WCAG A. WGAG guideline 2.1.2

Page elements such as buttons, links etc. must require a click, tap or keyboard stroke in order to trigger an event

Guideline 3.2.1 complies with WCAG A. WGAG guideline 3.2.1

Atoms, molecules and organisms

Layout

A valid HTML doctype must always be declared at the beginning of the document

Guideline 4.1.1 complies with WCAG A. WGAG guideline 4.1.1

All elements, in particular navigation and form elements, must be in a logical and intuitive order that will make sense without any visual styling

Guideline 1.3.2 complies with WCAG A. WGAG guideline 1.3.2

Any sizes specified, other than for imagery, must use relative units so that elements scale to their content. Also allowing for the user to scale the content or change the font size — fixed heights must not be used

Guideline 1.4.4 complies with WCAG AA. WGAG guideline 1.4.4

The page must be readable, functional and not require horizontal scrolling if the text is doubled in size

Guideline 1.4.9 complies with WCAG AAA. WGAG guideline 1.4.9

Typography

Fonts must always be chosen so as to be of a clear and legible type

Guideline 1.4 complies with WCAG A. WGAG guideline 1.4

Relative font sizes must be used so that the font size can be scaled

Guideline 1.4.4 complies with WCAG AA. WGAG guideline 1.4.4

Headings must be used appropriately and nested correctly, only using a capital letter for the first word

Guideline 2.4.6 complies with WCAG AA. WGAG guideline 2.4.6

Blocks of text must be no more than 80 characters wide, not be fully justified and have adequate line spacing (at least ½ height of text) and paragraph spacing (at least 1½ the line spacing)

Guideline 1.4.8 complies with WCAG AAA. WGAG guideline 1.4.8

Navigation

Skip links must be provided to bypass chunks of content and/or navigation

Guideline 2.4.1 complies with WCAG A. WGAG guideline 2.4.1

Always use consistent styling and positioning of key elements on each page, eg elements appearing on multiple pages such as site search and navigation must appear in the same place

Guideline 3.2.3 complies with WCAG AA. WGAG guideline 3.2.3

All pages must have a link back to the homepage to assist users if they become lost

Guideline 3.2.3 complies with WCAG AA. WGAG guideline 3.2.3

Always add ARIA landmark roles to appropriate sections of the page

Guideline 3.2.4 complies with WCAG AA. WGAG guideline 3.2.4

The opening of new windows or tabs must not be used, any non HTML content must have appropriate headers served to instruct the browser to download the file rather than opening it within the browser

Guideline 3.2.5 complies with WCAG AAA. WGAG guideline 3.2.5

Mark–up for redirects or periodically refreshing pages must not be used, this must be done server–side

Guideline 3.2.5 complies with WCAG AAA. WGAG guideline 3.2.5

Any time limits must be able to be turned off, adjusted or extended unless longer than 20 hours or changing the time limit would invalidate the activity

Guideline 2.2.1 complies with WCAG A. WGAG guideline 2.2.1

JavaScript must not be used to emulate links. Anchor tags must be used in all circumstances, so that all assistive technologies can recognise them

Guideline 2.1.1 complies with WCAG A. WGAG guideline 2.1.1

All buttons and links must be clearly worded indicating their function, making it clear to the user what will happen when the button/link is selected

Guideline 2.4.4 complies with WCAG A. WGAG guideline 2.4.4

Indication of whether a link is to something other than an HTML page, eg. a PDF, by including the file format and size within or immediately after the link must be provided

Guideline 2.4.4 complies with WCAG A. WGAG guideline 2.4.4

External links (links taking the user out of the current site) must be indicated to the user. This must be implemented by the use of appropriate title text and possibly through a visual indication

Guideline 2.4.4 complies with WCAG A. WGAG guideline 2.4.4

All links must contain enough useful information about their destination to make sense on their own, without surrounding text or graphics

Guideline 2.4.9 complies with WCAG AAA. WGAG guideline 2.4.9

The user must be provided with information that informs them where they are in the process or structure, such as a breadcrumb

Guideline 2.4.8 complies with WCAG AAA. WGAG guideline 2.4.8

Multiple ways to find other web pages on the site must be available; such as site map

Guideline 2.4.5 complies with WCAG AA. WGAG guideline 2.4.5

For large sites a sitemap must be provided

Guideline 2.4.5 complies with WCAG AA. WGAG guideline 2.4.5

Colour alone must not be used to distinguish a link from surrounding text, additional differentiation must be applied when the link is hovered over or receives focus

Guideline 1.4.1 complies with WCAG A. WGAG guideline 1.4.1

Tabs, tables and other page elements should be ordered logically so that they can be easily navigated one after another while using a keyboard

Guideline 2.4.3 complies with WCAG A. WGAG guideline 2.4.3

Interactive page elements should change visually to indicate that they can trigger an event using the keyboard

Guideline 2.4.7 complies with WCAG AA. WGAG guideline 2.4.7

Page elements

In data tables row and column headers must be identified (td for data and th for headers)

Guideline 1.3.1 complies with WCAG A. WGAG guideline 1.3.1

More complex relationships between data in tables must be described using thead, tfoot, tbody to group rows and col and colgroup to group columns

Guideline 1.3.1 complies with WCAG A. WGAG guideline 1.3.1

All information, structure and relationships between elements that is shown through presentation of the page also be available as plain text

Guideline 1.3.1 complies with WCAG A. WGAG guideline 1.3.1

All tags should be completely formed, elements should be correctly nested without duplicate attributes and all IDs should be unique

Guideline 4.1.1 complies with WCAG A. WGAG guideline 4.1.1

Forms

All form controls must have implicitly associated labels using mark–up and be positioned close to the element that they refer too

Guideline 3.3.2 complies with WCAG A. WGAG guideline 3.3.2

Any fields that are mandatory or optional need to be clearly marked using an asterisk or similar marker

Guideline 3.3.2 complies with WCAG A. WGAG guideline 3.3.2

Instructions and cues in context to help in form completion and submission must be provided

Guideline 3.3.5 complies with WCAG AAA. WGAG guideline 3.3.5

Error messages must be clear and concise and give the user some help as to what they need to do next

Guideline 3.3.1 complies with WCAG A. WGAG guideline 3.3.1

There must be clear indication of which form field generated the error and error messages must be placed next to the relevant field

Guideline 3.3.1 complies with WCAG A. WGAG guideline 3.3.1

If a certain format is required for the field an example of the format and specific suggestions for fixing a particular error must be included in the error message

Guideline 3.3.3 complies with WCAG AA. WGAG guideline 3.3.3

If a user can submit information the submission must be reversible, verified or confirmed

Guideline 3.3.6 complies with WCAG AAA. WGAG guideline 3.3.6

The cursor must not be automatically moved between fields during data entry

Guideline 3.2.2 complies with WCAG A. WGAG guideline 3.2.2

When using a dropdown list it must not activate a change of context by a single mouse click

Guideline 3.2.2 complies with WCAG A. WGAG guideline 3.2.2

Any interruptions such as alerts and page updates must be postponed or suppressible by the user

Guideline 2.2.4 complies with WCAG AAA. WGAG guideline 2.2.4

If an authenticated session expires the user must be able to re–authenticate and continue without losing any data from the current task

Guideline 2.3.5 complies with WCAG A. WGAG guideline 2.3.5

Where CAPTCHA is used you must provide non-visual alternatives to accommodate different disabilities

Guideline 1.1.1 complies with WCAG A. WGAG guideline 1.1.1

Events and activities on a web page should not include a countdown or time limit. This allows users the time they require to look over content

Guideline 2.2.3 complies with WCAG AAA. WGAG guideline 2.2.3

Media

A text transcript of important information within any audio or video content must be provided

Guideline 1.2.1 complies with WCAG A. WGAG guideline 1.2.1

Timed captions for audio content must be provided

Guideline 1.2.2 complies with WCAG A. WGAG guideline 1.2.2

An audio description of video content should be provided

Guideline 1.2.3 complies with WCAG A. WGAG guideline 1.2.3

Audio content should not contain background sounds, have the ability to turn off any background sounds, or have background sounds at least 20 decibels lower than the foreground audio content, with the exception of occasional sound effect

Guideline 1.4.7 complies with WCAG AAA. WGAG guideline 1.4.7

Any audio that automatically plays on a web page for longer than 3 seconds must have a controller that allows the user to stop the audio and to adjust the volume independent of the overall system volume

Guideline 1.4.2 complies with WCAG A. WGAG guideline 1.4.2

Imagery and icons

All imagery that is not decorative must have a text alternative that serves an equivalent purpose

Guideline 1.1.1 complies with WCAG A. WGAG guideline 1.1.1

If any images or graphs are updated dynamically the changes must also be reflected in the descriptive text

Guideline 1.1.1 complies with WCAG A. WGAG guideline 1.1.1

Any cosmetic graphics that are purely for visual effect must have an alt attribute that has been left blank

Guideline 1.1.1 complies with WCAG A. WGAG guideline 1.1.1

Using images to represent text must be avoided, instead text and style sheets should be used

Guideline 1.4.5 complies with WCAG AA. WGAG guideline 1.4.5

Motion

Descriptive text for animated content, such as alt text, must convey the same information as contained within the animated element

Guideline 1.1.1 complies with WCAG A. WGAG guideline 1.1.1

The user must have the ability to pause, stop or hide any moving, blinking, scrolling or refreshing content that lasts longer than five seconds

Guideline 2.2.2 complies with WCAG A. WGAG guideline 2.2.2

Content must not flash more than three times a second

Guideline 2.3.2 complies with WCAG AAA. WGAG guideline 2.3.2

Metadata and microdata

Every page must have a unique and meaningful title

Guideline 2.4.2 complies with WCAG A. WGAG guideline 2.4.2

Other

Do not use bright or flashing colours

A table title must be descriptive and there must be text on the page that introduces the table or provides a summary

Only use ampersands where necessary, such as in brand names, trademarks, formal titles or in logotypes

Minimise the use of capital letters and use BLOCK CAPITALS only for abbreviations

Any functionality provided by scripting must also have a version available that fulfills the user goals and provides equivalent content without it

Any scripts must be device independent and be produced to the same accessibility standards as HTML

All links, especially graphical links, must have sufficient spacing between them

Ensure the log in link is one of the first to be accessed within the tab order

Access key‘s (keyboard shortcuts) must not be used as many now clash with shortcuts within various browsers. If shortcuts are used ensure that they are tested across the main browsers

Style sheets must be used to set layout, visual formatting and style of the page

Always specify the width and height of an image unless a responsive layout is being used

Thumbnail graphics must be avoided as they can be difficult to target for people with fine motor impairment

If the element is essentially functional the text equivalent must convey its function

Do not crowd page elements together, always provide sufficient white space

The user must have the ability to override the styles and colour scheme therefore !important must not be used

Words that are not hyperlinks must not be underlined as this can be confusing to users

Do not over use bold text and never use it for an entire paragraph

Italic text must not be used for more than one sentence of text as this can appear ‘wobbly’ on screen making it difficult to read

Never use bold italic text

PDFs must be titled and tagged correctly and not use images to display textual information

Always provide a link to software to enable the use of PDFs on pages that contain them

No more than one animated element must be used on the page at once as this may cause problems for epileptic users

Moving or blinking text must be avoided

Multimedia must not automatically start playing

If a form has a number of stages, wording such as 'continue' must be used rather than 'send' or 'confirm'

All example text must appear before the item to be filled in

The user must be informed when they have been logged out either deliberately or due to a timeout and must be provided with a link to log back in

Only use text (and images) to provide examples of how to fill a field in

Do not use browser detection