Accessibility Nutrition Labels are a section on App Store product pages, introduced by Apple in 2025, that shows which accessibility features an app supports, such as VoiceOver, Voice Control, Larger Text, Sufficient Contrast, Dark Interface, Differentiate Without Color Alone, Reduced Motion, Captions, and Audio Descriptions. Developers declare support in App Store Connect per device. Evaluate support honestly against Apple's criteria, fix gaps in common tasks, and treat accessibility as a way to reach more users.
What the labels show
Apple introduced Accessibility Nutrition Labels to help users understand, before downloading, whether an app supports the accessibility features they rely on. The labels appear on product pages and list supported features for each device type, such as iPhone or iPad.
Features include VoiceOver, Voice Control, Larger Text, Sufficient Contrast, Dark Interface, Differentiate Without Color Alone, Reduced Motion, Captions, and Audio Descriptions. Apple provides criteria for what counts as supporting each feature.
How declarations work
Developers declare supported features in App Store Connect. Apple's guidance asks that apps support a feature across the common tasks users perform, not just in isolated screens. Apple initially made declarations voluntary and indicated they would become required over time, so check current requirements.
Treat declarations like privacy labels: they must be accurate. Overstating support misleads users who depend on these features, and leads to negative reviews and potential review issues. Our privacy labels and Data safety guide explains a similar accuracy-first approach.
Evaluate support honestly
Test common tasks with each feature enabled: VoiceOver navigation and labels, Voice Control commands, Dynamic Type at large sizes, contrast, dark mode, color independence, reduced motion, and captions or audio descriptions for media. Include users with disabilities in testing where possible.
Document results per device and feature. If support is partial, decide whether to fix gaps before declaring or to leave the feature undeclared until it meets the criteria.
Why accessibility matters for growth
A significant share of people have disabilities or situational needs, such as reading in bright sunlight or using a phone one-handed. Accessible apps reach more users and often provide a better experience for everyone. Labels make accessibility visible at the decision point, which can influence conversion for users who rely on these features.
Accessibility also supports ratings: users who can use your app comfortably are more likely to stay and leave positive reviews. Our app store conversion rate optimization guide covers other factors on the product page.
Common gaps to fix
Frequent issues include unlabeled buttons for VoiceOver, layouts that break with large text, low-contrast text, information conveyed only by color, animations without reduced motion support, and videos without captions. Many of these are inexpensive to fix once identified.
Apple's accessibility documentation and Xcode tools such as the Accessibility Inspector help identify issues. Build accessibility checks into development rather than auditing once.
Accessibility in store creative
Store creative itself should be accessible: legible captions with sufficient contrast, and clear visuals. Screenshots with tiny, low-contrast text are hard for many users to read. Mention key accessibility features in the description if they are strong.
Our screenshot caption copywriting guide encourages short, legible captions, which also improves accessibility.
Google Play and Android
Google Play does not have an identical label, but Android has accessibility features such as TalkBack, font scaling, and color correction, and Google provides accessibility guidelines and tools. Play Console's pre-launch report flags some accessibility issues.
Maintain accessibility on both platforms and mention support in your Google Play description where relevant.
Process and ownership
Assign ownership for accessibility, include it in design reviews, and test with assistive technologies before releases. Keep declarations up to date as features change, and review them when redesigning flows.
Our ASO audit checklist can include accessibility label accuracy as a recurring item.
Legal and market context
Accessibility is increasingly a legal expectation, not only a best practice. The European Accessibility Act applies to many digital products and services in the EU from 2025, and other regions have accessibility laws that can apply to apps in sectors such as banking, commerce, and transport. Requirements vary, so check which rules apply to your app and markets.
Building accessibility into the product protects you against these risks while expanding your audience. Accurate labels then communicate that investment to users at the moment they choose an app, supporting the trust signals discussed in social proof in store creatives.
Common accessibility label mistakes
Declaring features that are only partially supported is the most serious mistake. Another is ignoring accessibility until labels become required. Teams also forget to update declarations after redesigns.
Inaccessible store creative undermines the message of accessibility support.
A worked example: a banking app
A banking app audits accessibility and finds unlabeled buttons in the transfer flow and layouts that break at large text sizes. The team fixes labels and adjusts layouts, tests with VoiceOver and Dynamic Type users, and declares VoiceOver, Larger Text, Dark Interface, and Sufficient Contrast support.
Reviews from users who rely on these features improve, and the team mentions accessibility in its description. Ongoing accessibility checks become part of each release.
How to do it, step by step
- Review Apple's criteriaRead the definitions for each accessibility feature label.
- Test common tasksUse each feature across key flows on each device type.
- Fix gapsAddress labels, text scaling, contrast, color, motion, and captions.
- Declare accuratelyDeclare only features that meet the criteria in App Store Connect.
- Maintain and updateInclude accessibility in releases and update declarations when flows change.
Before and after examples
Illustrative examples written for a generic app in this category, not client results. Swap in your own product, audience, and data.
Declare VoiceOver because the home screen works.
Declare VoiceOver after testing all common tasks.
Why it works: Labels must reflect support across common tasks.
Icon button with no accessibility label.
Icon button labeled Send money.
Why it works: Labels make VoiceOver usable.
Light gray text on a pastel background.
Dark text with sufficient contrast.
Why it works: Legible creative is accessible creative.
Action plan
- Read Apple's label criteria
- Test common tasks with assistive features
- Fix common accessibility gaps
- Declare only genuine support
- Keep store creative legible
- Review declarations every release
Metrics to monitor
- Features declared versus tested
- Accessibility issues found per release
- Reviews mentioning accessibility
- Conversion trend after labels
- Pre-launch report accessibility warnings
Record the baseline, release date, audience, markets, and external changes before interpreting movement. Rankings and conversion are useful signals, but a decision is stronger when activation, retention, and business value confirm that the page attracted the right users.
Frequently asked questions
What are Accessibility Nutrition Labels?
A section on App Store product pages showing which accessibility features an app supports, declared by the developer.
Which features can be declared?
Features include VoiceOver, Voice Control, Larger Text, Sufficient Contrast, Dark Interface, Differentiate Without Color Alone, Reduced Motion, Captions, and Audio Descriptions.
Are accessibility labels required?
Apple introduced them as voluntary and indicated they would become required over time. Check current requirements.
Do accessibility labels affect ASO?
They can influence conversion for users who rely on accessibility features, and accessible apps tend to earn better reviews.
Does Google Play have accessibility labels?
Not identical labels, but Android has accessibility features and Play Console reports some accessibility issues.
Keep reading
More in Policy and Compliance
Browse all 7 Policy and Compliance guides
Work with ASOWin
Primary sources
Platform capabilities and limits can change. Verify current requirements in these official resources:
