Repository navigation
|
How can a team catch Haptics tactile feedback missing on interactions 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-HAPTICSRead 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. Interactive elements, buttons, or custom controls lacking feedback generators or CoreHaptics calls. The fix. Add haptic feedback to buttons, toggles, and swipe actions using UIImpactFeedbackGenerator or selection feedback. 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-HAPTICSRead 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-HAPTICSwith a coverage line and a proper exit code.What the hit means. Interactive elements, buttons, or custom controls lacking feedback generators or CoreHaptics calls.
The fix. Add haptic feedback to buttons, toggles, and swipe actions using UIImpactFeedbackGenerator or selection feedback.
R…