Repository navigation
|
How can a team catch TalkBack support missing or disabled automatically before a build goes to review? |
Replies: 1 comment
|
The quick check. Run this from the project root and read what it prints. python3 scripts/accessibility-audit.py . --rule ANDROID-ACCESSIBILITY-TALKBACKRead the result honestly. This is a heuristic. A match is something to inspect, not proof of a violation, and an empty result means nothing was found, not that the app is compliant. For CI, run the full guard, which reports this as What the hit means. Views or graphic components missing contentDescription or setting importantForAccessibility inappropriately. The fix. Provide meaningful contentDescription values for all informative images and interactive views, and ensure importantForAccessibility is set correctly. Recipe source. data/detection-recipes.json This is a maintainer FAQ for app-store-compliance, an open playbook and pre-submission guard for App Store and Google Play review. Run |
The quick check. Run this from the project root and read what it prints.
python3 scripts/accessibility-audit.py . --rule ANDROID-ACCESSIBILITY-TALKBACKRead the result honestly. This is a heuristic. A match is something to inspect, not proof of a violation, and an empty result means nothing was found, not that the app is compliant. For CI, run the full guard, which reports this as
ANDROID-ACCESSIBILITY-TALKBACKwith a coverage line and a proper exit code.What the hit means. Views or graphic components missing contentDescription or setting importantForAccessibility inappropriately.
The fix. Provide meaningful contentDescription values for all informative images and interactive views, and …