Business Analyst

As a Business Analyst in an agile team, you’re involved in the critical parts where accessibility is often overlooked. Your role is often a facilitating role, to make sure user stories and conversations always include accessibility.

Things to consider as a Business Analyst

Definition of ready

When writing user stories, we outline criteria for when they are ready to build. This is usually when it’s been through usability testing and the acceptance tests have been defined. But these discussions should also include accessibility.

As part of the stories definition of ready, make sure the team have discussed how the proposed design can be made accessible, and include important content in the story such as page titles and URLs as these can affect accessibility.

Work with an Interaction Designer and a Content Designer to understand which parts of the service might be tricky to build, for example things which do not exist already and will need to be built from scratch. These will require more testing.

An example of accessibility considerations in a definition of done:

  • Error messages, page titles and URLs agreed with Content Designer
  • Content reviewed by team and accessibility considerations discussed
  • Design reviewed by team and accessibility considerations discussed

Definition of done

Like the definition of ready, the definition of done is a list of criteria which need to be met in order to consider a story to be finished.

We can’t deploy code which is not accessible, otherwise we are breaking the law. So if it’s not accessible it’s not done. As part of your definition of done, the service should be checked for accessibility using both automated and manual tests.

An example of accessibility considerations in a definition of done:

  • Automated accessibility tests passed using AxeCore
  • Manual accessibility tests passed using Accessibility Insights
  • Manually checked usability using only a keyboard
  • Manually checked usability using a screenreader
  • Manually checked usability using a screen magnifier
  • Manually checked usability using speech recognition