Actions and auditing

Accessibility and inclusivity baseline

<aside> 👉🏼 Hint: these are the foundational pieces that need to be in place; they cover a combination of content, design, and code considerations.

</aside>

A combination of content, design, and code

• [ ] Interfaces designed and developed:
  • [ ] using semantic HTML structuring
• [ ] Content management affordances have been included and implemented:
  • [ ] alt tags
  • [ ] page titles
  • [ ] video captions
  • [ ] video transcripts
• [ ] Language and imagery consideration:
  • [ ] Language has been reviewed to align with audience knowledge and objectives
    • [ ] Copy has been proofread
  • [ ] Copy has been translated to:
    • [ ] Language:
    • [ ] Translations have been proofread
  • [ ] Imagery has been reviewed for considerations of inclusion and diversity representative of the audience

Manual testing

<aside> 👉🏼 Hint: this is what your technical team should be confirming.

</aside>

• [ ] Mobile phone:
  • [ ] test touch interactions
  • [ ] smaller screen sizes responsive review
• [ ] Desktop computer:
  • [ ] reviewed with a mouse and/or trackpad.
• [ ] Keyboard:
  • [ ] ensure a user can navigate and interact using only a keyboard
• [ ] Screen reader:
  • [ ] interface can be navigated and understood and interactions function correctly (or have a suitable alternative)
• [ ] Zooming:
  • [ ] the site can be zoomed in and that the layout responds in a way that ensures content is visible and readable at a large scale

Automated tools & testing

<aside> 👉🏼 Hint: your technical team should be able to show you these results.

</aside>

• [ ] The code has been tested with at least two of:
  • [ ] Deque’s AXE
  • [ ] TPGI’s Arc
  • [ ] IBM Equal Access Accessibility Checker
  • [ ] Other (Indicate tool name)
• [ ] Performance has been validated with at least one of:
  • [ ] Lighthouse
  • [ ] Pingdom
  • [ ] Other

Validation