SwiftUI accessibility audit
Accessibility quality is broader than finding one missing label. Axint combines static review leads with task-based evidence so teams can see what was checked, what remains advisory, and what can support an App Store accessibility declaration.
local proof
$axint prove --dir /path/to/MyApp --advisorychecks
labels · focus · touch
store
common-task evidence
severity
advisory by default
01
The validator can flag controls whose visual treatment and interaction do not expose an equivalent accessibility contract, identifiers nested where tests cannot reach them, overlays likely to intercept touches, and custom gestures that may conflict with text selection.
02
A static rule cannot prove VoiceOver behavior. Accessibility leads remain advisory until simulator, UI test, or human evidence supports them. The report names the common task, evidence source, result, and remaining review item.
03
Common-task matrices give release teams a repeatable place to record VoiceOver, Voice Control, Larger Text, sufficient contrast, reduced motion, captions, and other applicable support instead of treating the store declaration as a last-minute checkbox.
common questions
No. It can find strong leads and contract gaps. Decisive accessibility proof requires runtime, assistive-technology, UI-test, and often human evaluation.
No. It creates a reviewable evidence report that can support the team's App Store Connect decisions.
continue