Skip to main content

If something isn’t accessible it isn’t done

In Agile software development the definition of done sets a shared standard for when work is complete. Accessibility must be part of that standard.

If something isn’t accessible it isn’t done.

Releasing a service that excludes users risks not only a poor experience but also legal consequences. 

Accessibility should be built into the workflow — not left to the end. That means running automated and manual checks, and making sure all user-facing elements, including documents, meet accessibility standards.

A clear definition of done for accessibility might include:

  • automated accessibility tests pass

  • manual checks are completed by test and developers

  • basic usability confirmed with a screen reader

  • basic usability confirmed with a screen magnifier

  • basic usability confirmed with speech recognition

  • accessibility statement reviewed and updated

Was this page helpful?