Skip to main content


An accessible launch involves two practices. The first is Launch readiness, where the release manager coordinates with the test lead and an accessibility champion (at IBM, the accessibility focal point) to ensure the product’s accessibility has been properly tested and recorded. Then in Sustain and grow, they engage with the product manager to plan how to advance accessibility in future releases.

Accessibility activities in the Launch phase involve a broad set of disciplines and align with the accessibility goals set in the Plan phase. Nearly all the Verify tasks should be complete by the beginning of the Launch phase. The project team then transitions to the launch readiness tasks and sustains and grows its users, especially users who have disabilities.

Launch practices

Need help?

Submit a github issue and we’ll help you find what you need.

Submit an issue