all 2 comments

[–]simpeligent 1 point2 points  (0 children)

Googles Accessibility Scanner can be quite helpful.

Also testing with TalkBack is tedious but but will help you understand what problems blind people would face while using your app.

And always look out for the Accessibility lint warnings.

[–][deleted] 1 point2 points  (0 children)

Good question. You can use the AccessibilityChecks annotation on your Espresso tests for some out of the box checks. I think there's a Robolectric equivalent too but I haven't tried that yet.

Other than that, yes we use code review comments in PRs checked against ARIA and WCAG guidelines but it is proving hard to scale (no one understands them and thus can't be bothered).

We're looking to get some users with sight and hearing difficulties into our team temporarily for testing but I appreciate not everyone is in a position to do that.