Track accessibility results over time
Problem to solve
Testing for accessibility issues enables teams to find and resolve issues early in the development process ensuring that their web app or web site will be accessible to all users.
Having a score or metric of accessibility issues and details of the issues gives developers context to fix issues as the happen and research issues in the existing code base. Developers and managers do not have an easy way within GitLab to track progress of those metrics though today.
- When Parker and Delaney are planning the roadmap, they want to see how their current strategy of making the app/site accessible is progressing, so they can confidently plan and present their strategy for accessibility improvements.
- Show a graph of the 3 counts coming from the Pa11y report graphed over time.
Permissions and Security
What does success look like, and how can we measure that?
What is the type of buyer?
Links / references
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.