The following checklists have been compiled using information provided by the W3C within their 'Checklist of Checkpoints for Web Content Accessibility Guidelines 1.0'.

Priority Level 1: Checklist

• 1. If you can't make a page accessible, construct an alternate accessible version.
  - All pages are accessible.
• 2. If style sheets are ignored or unsupported, are pages still readable and usable?
  - Style sheets have been disabled for testing. All pages have proved to be usable.
• 3. If you use color to convey information, make sure the information is also represented another way.
  - Color is used for graphics and links. Graphics have alt tags while links have title tags. Links outside the primary navigation are easily recognisable because they are underlined, hence, colour-independent.
• 4. If an image conveys important information beyond what is in its alternative text, provide an extended description.
  - Images that show important information have been given an extended description.
• 5. If a table has two or more rows or columns that serve as headers, use structural markup to identify their hierarchy and relationship.
  - All tables have headers and use structural markup to identify them.
• 6. Identify any changes in the document's language.
  - There are no changes in the document's language.
• 7. Use the simplest and most straightforward language that is possible.
  - The text is readable as it was intended for anyone interested in the subject.
• 8. Provide redundant text links for each active region of an image map.
  - a. All image maps have been given alternative text links for users who have trouble using the map.
  - b. The ‘Where to Donate’ pages that include a Google Map to display a session’s postcode, also have the postcode provided as plain text on the page.
• 9. Ensure thats pages are usable when scripts, applets, or other programatic objects are turned off or not supported.
  - No scripts or applets are essential to use this website.
• 10. Use ‘onclick’ for JavaScript functions not ‘href’.
  - a. The ‘Where to Donate: Session by Region’ pages use ‘onclick’ to enable the table columns to be sorted by the user if required.  This function is an additional feature so is, therefore, not necessary to access the page’s information.
  - b. The ‘Where to Donate Search Results’ page uses ‘onclick’ to reveal the available sessions for a location.  These sessions are available in an alternative format on the region pages.

Priority Level 2: Checklist

• 1. Is the user made aware that there will be pop-up windows or changes in the active window?
  - Not applicable.
• 2. If scripts create pop-up windows or change the active window, make sure that the user is aware this is happening.
  - Not applicable.
• 3. Make sure header elements are not used only for bold text.
  - Headings h1, h2 have been used to define document structure.
• 4. Check that the foreground and background colours contrast sufficiently with each other.
  - Two contrasting colours dominate the graphics (white for background and dark grey, red for text).
• 5. Mark up any quotations with the Q and BLOCKQUOTE elements.
  - Not Applicable.
• 6. If this gif image is animated, make sure it does not contain fast or distracting motion.
  - Not applicable.
• 7. If this table is used for layout only, do not use structural markup to achieve formatting effects.
  - Tables have been used for layout, however this is being updated for the future when inline-table styles become a deprecated feature.
• 8. Explicitly associate form controls and their labels with the LABEL element.
  - Form elements have been labelled.
• 9. Make sure that all link phrases make sense when read out of context.
  - a. Link text is descriptive.
  - b. The link phrase ‘Available Sessions’ could appear multiple times within the ‘Where to Donate Search Results’ page, however it is always after a session location name and address.
• 10. Is there a site map or table of contents, a description of the general layout of the site, the access features used, and how to use them?
  - A site map has been provided.
• 11. Make sure your document validates to formal published grammars.
  - All pages validate XHTML 1.0 Transitional.
• 12. Group related elements when possible.
  - All related elements are grouped.
• 13. Is there a clear, consistent navigation structure?
  - Yes. There are primary and secondary navigation.
• 14. Use the latest technology specification available whenever possible.
  - All pages are XHTML.
• 15. Where it's possible to mark up content (for example mathematical equations) instead of using images, use a markup language (such as MathML).
  - Not applicable.
• 16. Until user agents allow users to control blinking, avoid causing content to blink.
  - Not applicable.
• 17. Until user agents provide the ability to stop the refresh, do not periodically auto-refresh pages.
  - Not applicable.
• 18. make sure event handlers do not require use of a moue.
  - a. Event handlers do not need a mouse.
• - b. Within the search page 'Where to Donate' the event handler which enables the search facility is unusable without a mouse however, a text alternative search method has been provided in the right-hand sidebar.

Priority Level 3: Checklist

• 1. If this document is part of a collection, provide metadata that identifies this document's location in the collection.
  - Not applicable.
• 2. Consider specifying a logical tab order among form controls, links and objects.
  - Forms have been given a logical tab order.
• 3. Use the ABBR and ACRONYM elements to denote and expand any abbreviations and acronyms that are present.
  - Not applicable.
• 4. If you have grouped links, is there a link at the beginning to bypass the group?
  - Not applicable. The site uses CSS layout and navigation is always bypassed.
• 5. If there are logical groups of links, have they been identified?
  - CLASS element has been used for identification of link groups.
• 6. Consider adding keyboard shortcuts to frequently used links.
  - The Accesskey element has been used.
• 7. Is there distinguishing information at the beginning of headings, paragraphs, lists, etc.?
  - Yes
• 8. If there is a search feature, are there different types of searches for different skill levels and preferences?
  - There are alternative ways to use the search feature.
• 9. Are there navigation bars for easy access to the navigation structure?
  - Yes.
• 10. Do you allow users to customize their experience of the web page?
  - Not applicable.
• 11. Is there a consistent style of presentation between pages?
  - Yes.
• 12. Provide summaries for tables.
  - All tables have been given summaries of their content.
• 13. Until user agents handle empty controls correctly, include default, place-holding characters in edit boxes and text areas.
  - a. Any editable text areas have been provided with default characters.
• - b. Apart from on the 'Where to Donate' page, where place-holders would obstruct from searching without having to specify a date.