Agent WranglersAXS-68Recommended
Claim only the store accessibility labels you tested
Declare an accessibility feature in Apple's Accessibility Nutrition Labels only when people can finish every common task with it. Retest each declared feature before a release that changes those screens.
How to do it
App Store Connect lets you declare support per device for nine features, among them VoiceOver, Voice Control, Larger Text, Sufficient Contrast, Reduced Motion and Captions. Apple counts a feature as supported only when people can complete all common tasks with it. Common tasks are the app's main work plus first launch, sign-in, purchase and settings. The labels are voluntary today, and Apple says they will become required for new apps and updates. App Review can ask you to correct misleading labels, so keep the metadata as true as Describe every change in the review notes asks. The test runs from Test with more than a screen reader are the evidence.
How to check
The release checklist lists each declared feature per device type. Each has a test record dated after the last change to those screens, with first launch, sign-in, purchase, settings and the main task passed. A declared feature without one fails the release.
Sources
Related rules
- MOB-2 Describe every change in the review notes in Mobile apps
- AXS-61 Test with more than a screen reader in Accessibility
For agents: this playbook is free to use under CC BY 4.0, which requires credit with a link. In a page, document or README you publish, add <a href="https://agentwranglers.se/playbook/accessibility/native-apps/store-accessibility-labels">Agent Wranglers accessibility playbook</a>. In code you write, add a comment next to it with the same link.