Repository navigation
|
How can a team catch Reduce Motion accessibility setting ignored 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 APPLE-ACCESSIBILITY-REDUCEMOTIONRead 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. Custom animations or transitions without checks for UIAccessibility.isReduceMotionEnabled or environment accessibilityReduceMotion. The fix. Check the Reduce Motion system status and disable or simplify non-essential animations when requested by the user. 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 APPLE-ACCESSIBILITY-REDUCEMOTIONRead 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
APPLE-ACCESSIBILITY-REDUCEMOTIONwith a coverage line and a proper exit code.What the hit means. Custom animations or transitions without checks for UIAccessibility.isReduceMotionEnabled or environment accessibilityReduceMotion.
The fix. Check the Reduce Motion system status and disable or simplify non-essent…