Ross Mullen / Mastering Accessibility Acceptance Criteria for better user stories

Creating user stories with included accessibility information is hard. Do you cram so much detail into each story describing how a developer creates it? or just reference WCAG and hope that by luck the requirements appear in the finished feature?

Accessibility Acceptance Criteria are one solution.

They're broad accessibility criteria applied when user stories are created. They’re BA focused describing key behaviours a finished feature needs to display – an outcome, but don’t go so far as in specifying how to do it.

Instead, acting as guard rails they allow a developer the flexibility to implement the feature in any number of ways, if the outcome is met.

About the speaker

Ross is director of CANAXESS and works with private industry and government improving their accessibility efforts with auditing, training, and consulting. He presents and writes regularly on digital accessibility in current and emerging technology, creates digital accessibility courses for Udemy and Pluralsight, and likes to really unpick the true intent of WCAG success criteria.

https://inclusivedesign24.org/