A closer look at Apple’s Accessibility Nutrition Labels

A clearer picture of accessibility in the App Store

Until now, users downloading apps were in the dark if the app supported accessibility features on an iOS device. That's now changed with Accessibility Nutrition Labels introduced at Apple Worldwide Developer conference (WWDC) 2025.

These labels help users understand if an app will be accessible prior to downloading it. The system is currently voluntary and allows teams to show which accessibility features on the device their app supports including VoiceOver, Voice Control, and Captions.

Whilst optional to begin with, Apple has announced teams will have to provide accessibility support details when submitting new apps and app updates to the App Store. It won’t be a "set-and-forget" process. Labels will need to be reviewed and supported regularly to keep this information accurate and up to date.

Nutrition label location

The labels appear on an app’s product page in all countries and regions where the app is available and displays the labels specific to the device type. If a feature isn't specified for a device, the label shows "not indicated."

Labelling can be provided for each target iOS device, but it won't be one label for all. So, expect to plan for different devices having differing levels of accessibility support. Which potentially introduces a greater level of post deployment app management overhead.

As part of the labelling the option exists to provide an accessibility URL that links to a website where users can learn more about the app’s accessibility features.

This URL should correspond uniquely to the app and can include information such as other accessibility features. Could this URL theoretically correspond with the website accessibility statement? No, a statement is specific to the website. A separate accessibility page just for the app will also need to be created.

Searchable by feature

Starting from September 2025, users will be able to include Accessibility Nutrition Label features as part of their search query to make their results more relevant.

For example, a user could search for "VoiceOver note taking apps" or "exercise apps with Larger Text".

Planning for your response

When planning to implement accessibility labelling, it's crucial to ensure your app accurately conveys its accessibility support. If there is intentionally misleading labels, App Review will contact you and ask you to update the Accessibility Nutrition Labels.

The App Store has preset evaluation criteria you should meet before showing support in the Accessibility Nutrition Labels. You should assess your app on each of the targeted devices your app supports.

To show support for an accessibility feature in the Accessibility Nutrition Labels, users must be able to complete all the common tasks of your app using that feature. If you decided to provide a nutrition label for VoiceOver, then all common tasks of your app must then work with VoiceOver.

Identifying your app common tasks

Which segues into the question "what are my apps common tasks?".

For this compile a list of the common tasks that a user can perform in your app. These consist of the primary functions that you expect users to perform, plus functions that are fundamental to using the app. These could be first launch experience, login, purchase, and settings.

Remember to show support for an accessibility feature, a user should be able to perceive, operate, and understand all the primary functionality specific to your app while using the feature.

Summary

There's plenty to unpack, but Apple’s Accessibility Nutrition Labels improve how accessibility is communicated to users. While still voluntary for now, they signal a move toward greater transparency and accountability in app development.

For teams, this means planning, testing, and supporting accurate accessibility claims across all iOS devices and features. For users, it means more informed choices and a more inclusive App Store experience.

Start preparing now because come September 2025, accessibility won’t just be a feature, it’ll be a search filter.

This is the first post in our series on Apple's Accessibility Nutrition Labels, where we continue to explore what they mean in practice and what teams need to consider