Repository navigation
|
How can a team catch Keyboard navigation and focus state support missing 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-KEYBOARDRead 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 text editors or complex navigation flows missing keyCommands, focusState, or focusable modifiers. The fix. Support physical keyboard navigation by utilizing keyCommands in UIKit or focusable() and @focusstate in SwiftUI. 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-KEYBOARDRead 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-KEYBOARDwith a coverage line and a proper exit code.What the hit means. Custom text editors or complex navigation flows missing keyCommands, focusState, or focusable modifiers.
The fix. Support physical keyboard navigation by utilizing keyCommands in UIKit or focusable() and @focusstate in Sw…