This is by no means a revolutionary thought, but I wonder how often “accessibility user stories” are used in real-life projects:
accessibility user stories are just like any other user story and focus on the value and benefits a feature will provide to people who might use your product in different ways. Understanding how people will use your product or site using accessible personas makes it easier to understand how to bring those benefits to them, and to the buisness [sic].
Transforming accessibility requirements (as e.g. derived from WCAG or other norms) into bite-size user stories makes them more tangible, and enable easier implementation.
As the article by Leon Hampson illustrates: when an audit finds colour issues, a story like this is an actionable task for somebody to work on:
As a user who is colour blind, I want links to be distinguishable on the page so that I can find the links and navigate the site.