Repository navigation
|
How can a team catch Touch target sizes below 48dp 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-SCANNERRead 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. Clickable items or buttons defined with layout_width, layout_height, or padding that results in touch targets smaller than 48dp. The fix. Ensure all interactive elements have a minimum touch target area of 48dp x 48dp by using padding, minWidth, and minHeight. 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-SCANNERRead 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-SCANNERwith a coverage line and a proper exit code.What the hit means. Clickable items or buttons defined with layout_width, layout_height, or padding that results in touch targets smaller than 48dp.
The fix. Ensure all interactive elements have a minimum touch target area of 48dp x 48dp b…