Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Pending code changes (auto-populated)
View issue level access limits(Press Alt + Right arrow for more information)
Request for new functionality
View staffing
Description
Compose+Android Studio provide a UI Check tool, which generates accessibility reports for Compose screens:
This tool is very manual, requiring developers to trigger it for each preview they're interested in, address any issues within that specific preview, and then move on to another.
The Espresso testing library includes an automated accessibility checker:
This can be included in standard Espresso tests, providing confidence that the screens and components covered by that test meet accessibility standards.
This does not work for Compose screens, however, as it acts at the View level.
To help ensure the accessibility of an app, it would be useful to be able to invoke the Compose UI Check either during automated tests, or as a separate lint tool.
Use Case:
Allow developers to automatically test that Compose screens and components meet accessibility requirements, such that these tests can be run by a CI pipeline or other automated build tool, giving developers additional confidence in both their own changes, and changes of others in their teams.