A11y docs

An attempt to find a way to capture and document accessibility testing on a modular basis.

Content

• What to capture
• Possible integrations
• Release History
• License

---

What to capture

What should be captured to communicate the accessibility of an element?

• Screen-reader support list
• Screen-reader experience
  • Text spoken as text *
  • Text spoken as sound *
• Keyboard experience
  • Tabing order
  • Flow of functionality eg how to access certain functions with keyboard and what keys had to be used
  • Visual cues (outlines, active states)
• Web resilience
  • HTML validation errors/warnings *
  • No CSS
  • No JS
  • No images
  • No webfonts
• Design resilience
  • Color contrast *
  • Color contrast proximity (1.4.1 G183) *
  • Font sizes
  • Font weight
  • Animations
  • Logical order
• Dev resilience
  • Errors thrown *
  • Font zoom
  • Screen zoom
  • Browser testing *

* could be automated

⇪ back to top

---

Possible integrations

A list of possible API integrations for automation

• ...
• ...

⇪ back to top

---

Release history

• v0.1.0 - Initial specs

⇪ back to top

---

License

Copyright (c) Westpac. Licensed under the GNU GPLv3.

⇪ back to top

};