Skip to Main Content

Pelican Design System icon Pelican Design System Accessibility Checklist

Accessibility Checklist

A few things you can check to ensure you have basic accessibility covered.

Edit on GitHub

On this page:

Best Practices

The following checklists for are based on the WCAG 2.2 Level A and AA standards. The checklists are organized as sections for Perceiveable, Operable, Understandable, and Robust, or P.O.U.R. They will be updated as new information is available. It’s meant to assist product teams, including designers, developers, content creators, and purchasing agents, in creating and procuring accessible IT.

Perceivable

  • Do images have Alt text?
  • Does video have captions, transcripts, and audio description tracks?
  • Does audio have transcripts?
  • Does the page include proper headings, lists, ARIA landmarks, and other semantic HTML elements to communicate document structure?
  • Are the tab and read orders logical and intuitive?
  • Do form fields within pages have appropriately coded and connected labels?
  • Have you avoided using visual tactics to communicate information (e.g., “click the button on the right” or “required fields are in red”)?
  • Does the interface have WCAG-compliant contrast between text color and background color?
  • Does the content scale well when text is enlarged up to 200 percent?

Operable

  • Are all menus, links, buttons, and other controls usable by keyboard, to make them accessible to users who don’t use a mouse?
  • Does the web page include a visible focus indicator so all users, especially those using a keyboard, can easily know their current position?
  • Do features that scroll or update automatically (e.g., slideshows, carousels) have prominent accessible controls that enable users to pause or advance these features on their own?
  • Do pages that have time limits include mechanisms for adjusting those limits for users who need more time?
  • Have you avoided using content that flashes or flickers?
  • Does the web page or document have a title that describes its topic or purpose?
  • Are mechanisms in place that allow users to bypass blocks of content (e.g., a “skip to main content”?
  • Does the website include two or more ways of finding content, such as a navigation menu, search feature, or human-readable site map?
  • Do all links contain meaningful text, independent of context?
  • At 200% zoom or higher, all content and controls should still be accessed.

Understandable

  • Has the language of the web page or document (or individual parts of a multilingual document) been defined?
  • Have you avoided links, controls, or form fields that automatically trigger a change in context?
  • Does the website include consistent navigation?
  • Do online forms provide helpful, accessible error and verification messages?
  • At 200% zoom or higher, the user should only need to scroll in one direction.

Robust

  • Are you including human testing? Automated testing is useful, but not a replacement for human testing.
  • Are you using semantic HTML?
  • Is the web page coded using valid HTML (e.g., not using Javascript on a Div instead of a button or link)?
  • Do rich, dynamic, web interfaces, such as modal windows, drop-down menus, slideshows, and carousels, include ARIA markup?
  • Are you including proper ARIA on custom controls?
  • At 200% zoom or higher, the digital product should still function.

Resources

This checklist is heavily inspired by University of Washington’s Accessibility Checklist.

Previous
Page top