Testing checklist for Web Accessibility

This is a complete listing of the NDA accessibility guidelines for web sites and online applications, in order of priority. These are the Web Content Accessibility Guidelines (version 1.0) from the Web Accessibility Initiative (WAI) but with simplified statements and a different numbering system.

This checklist is designed to support assessment tasks carried out by people in the roles of Planning and Procurement and Testing, Assessment and Quality Assurance.

Minimum accessibility requirements (Priority 1)

Following priority 1 will make it possible for all groups to use the site. For some groups, this is the basic requirement to enable them to access the information.

1.1 Provide a text equivalent for every non-text element WAI Checkpoint 1.1 Yes No N/A 1.2 Ensure that information does not rely on colour perception WAI Checkpoint 2.1 Yes No N/A 1.3 Avoid causing the screen to flicker WAI checkpoint 7.1 Yes No N/A 1.4 Provide an auditory description of the visual information in multimedia presentations WAI checkpoint 1.3 Yes No N/A 1.5 For multimedia, ensure that timing of alternative descriptions is synchronised with the presentation WAI checkpoint 1.4 Yes No N/A 1.6 Use the clearest and simplest language appropriate WAI checkpoint 14.1 Yes No N/A 1.7 Identify language changes in text WAI checkpoint 4.1 Yes No N/A 1.8 Ensure that equivalents for dynamic content are updated when the dynamic content changes WAI checkpoint 6.2 Yes No N/A 1.9 For data tables, identify row and column headers WAI checkpoint 5.1 Yes No N/A 1.10 For complex data tables, use mark-up to associate data cells and header cells WAI checkpoint 5.2 Yes No N/A 1.11 Add titles to frames WAI checkpoint 12.1 Yes No N/A 1.12 Ensure that documents can be read without style sheets WAI checkpoint 6.1 Yes No N/A 1.13 Provide text links to emulate server-side image maps WAI Checkpoint 1.2 Yes No N/A 1.14 Use client-side image maps rather than server-side image maps where possible WAI checkpoint 9.1 Yes No N/A 1.15 Ensure that scripts and applets that provide the only source of important functionality are directly accessible or compatible with assistive technologies WAI checkpoint 8.1 Yes No N/A 1.16 Ensure that pages are usable without support for scripts, applets, or other programmatic objects WAI Checkpoint 6.3 Yes No N/A 1.17 If you cannot make a page accessible, provide an equivalent accessible page WAI checkpoint 11.4 Yes No N/A

Additional accessibility requirements (Priority 2)

Following priority 2 will remove significant barriers for one or more groups.

2.1 Ensure that images have sufficient contrast for people with colour deficient vision WAI checkpoint 2.2 Yes No N/A 2.2 Avoid causing content to blink WAI checkpoint 7.2 Yes No N/A 2.3 Avoid movement in content WAI checkpoint 7.3 Yes No N/A 2.4 Ensure that dynamic content is accessible or provide an alternative presentation or page WAI checkpoint 6.5 Yes No N/A 2.5 Use style sheets to control layout and presentation WAI Checkpoint 3.3 Yes No N/A 2.6 Use relative rather than absolute units WAI Checkpoint 3.4 Yes No N/A 2.7 Use header elements to convey structure WAI checkpoint 3.5 Yes No N/A 2.8 Break up large blocks of information where appropriate WAI checkpoint 12.3 Yes No N/A 2.9 Ensure that information laid out using tables make sense when linearised, or provide an alternative equivalent WAI checkpoint 5.3 Yes No N/A 2.10 Do not use structural mark-up to format information laid out using tables WAI checkpoint 5.4 Yes No N/A 2.11 Describe the purpose of frames and how they relate to each other if it is not obvious by their titles alone WAI checkpoint 12.2 Yes No N/A 2.12 Clearly identify the target of each link WAI checkpoint 13.1 Yes No N/A 2.13 Provide information about pages and sites in metadata WAI checkpoint 13.2 Yes No N/A 2.14 Provide information about the general layout of a site WAI checkpoint 13.3 Yes No N/A 2.15 Use navigation mechanisms consistently WAI checkpoint 13.4 Yes No N/A 2.16 Associate labels explicitly with their controls WAI checkpoint 12.4 Yes No N/A 2.17 Properly position the labels of form controls WAI checkpoint 10.2 Yes No N/A 2.18 Ensure that user interfaces are device-independent WAI checkpoint 9.2 Yes No N/A 2.19 Use logical event handlers in scripts WAI checkpoint 9.3 Yes No N/A 2.20 Use input device-independent event handlers in scripts and applets WAI checkpoint 6.4 Yes No N/A 2.21 Ensure that scripts and applets are accessible WAI checkpoint 8.1 Yes No N/A 2.22 When an appropriate markup language exists, use markup rather than images to convey information WAI Checkpoint 3.1 Yes No N/A 2.23 Create documents that validate to published formal grammars WAI Checkpoint 3.2 Yes No N/A 2.24 Mark up lists and list items using the proper HTML tags WAI checkpoint 3.6 Yes No N/A 2.25 Use quotation mark-up for quotations, but not for formatting WAI checkpoint 3.7 Yes No N/A 2.26 Where possible, use appropriate W3C technologies of the latest supported versions WAI checkpoint 11.1 Yes No N/A 2.27 Avoid deprecated features of W3C technologies WAI checkpoint 11.2 Yes No N/A 2.28 Do not periodically auto-refresh pages WAI checkpoint 7.4 Yes No N/A 2.29 Do not use mark-up to redirect pages automatically WAI checkpoint 7.5 Yes No N/A 2.30 Do not generate pop-ups or other windows and do not change the current window without informing the user WAI checkpoint 10.1 Yes No N/A

Additional accessibility requirements (Priority 3)

Following priority 3 will improve access for one or more groups.

3.1 Ensure that text and background have sufficient contrast for people with colour deficient vision WAI Checkpoint 2.2 Yes No N/A 3.2 Provide text links to emulate client-side image maps WAI Checkpoint 1.5 Yes No N/A 3.3 Expand the first occurrence of any abbreviation or acronym WAI Checkpoint 4.2 Yes No N/A 3.4 Identify the primary language of the document text WAI Checkpoint 4.3 Yes No N/A 3.5 Place distinguishing information at the beginning of headings, paragraphs, lists, etc. WAI Checkpoint 13.8 Yes No N/A 3.6 Supplement text with graphic or auditory presentations where they will facilitate comprehension WAI Checkpoint 14.2 Yes No N/A 3.7 Provide summaries for tables WAI checkpoint 5.5 Yes No N/A 3.8 Provide abbreviations for table header labels WAI checkpoint 5.6 Yes No N/A 3.9 Identify groups of related links and provide a way to bypass them WAI checkpoint 13.6 Yes No N/A 3.10 Provide a linear alternative for parallel, word-wrapped columns of text WAI checkpoint 10.3 Yes No N/A 3.11 Create a logical tab order through links, form controls, and objects WAI Checkpoint 9.4 Yes No N/A 3.12 Provide keyboard shortcuts to important links, form controls, and groups of form controls WAI Checkpoint 9.5 Yes No N/A 3.13 Separate adjacent links with non-link, printable characters surrounded by spaces WAI Checkpoint 10.5 Yes No N/A 3.14 Provide navigation bars WAI Checkpoint 13.5 Yes No N/A 3.15 If search functions are provided, enable different types of searches for different skill levels and preferences WAI Checkpoint 13.7 Yes No N/A 3.16 Provide information about documents comprising multiple pages WAI Checkpoint 13.9 Yes No N/A 3.17 Provide a means to skip over multi-line ASCII art WAI checkpoint 13.10 Yes No N/A 3.18 Create a style of presentation that is consistent across pages WAI Checkpoint 14.3 Yes No N/A 3.19 Include default text in form text boxes WAI checkpoint 10.4 Yes No N/A 3.20 Provide information to enable users to receive documents according to their preferences WAI Checkpoint 11.3 Yes No N/A