1. Overview

The earlier lessons showed what to build. This one shows how to prove it works, and how to tell people. Testing has two layers. Automated checks run fast and catch the same problems every time. Manual checks with VoiceOver and the other features catch the rest.

No tool can tell whether a label makes sense. No tool can tell whether the reading order keeps the meaning. So automated checks are a floor, not a finish line.

Shipping has two layers too. On the App Store, Accessibility Nutrition Labels tell people which features your app supports. In the EU, the European Accessibility Act and EN 301 549 set what the app of a covered service must meet. Both depend on the same test evidence.

Standards covered: EN 301 549 V4.1.1 clause 11, clause 12.1 and the Annex C test procedures · WCAG 2.2 Levels A and AA as applied to software through the W3C's WCAG2ICT guidance · European Accessibility Act Article 13 and Annex I Section III(c) · Apple's App Store Connect Help: Accessibility Nutrition Labels and their evaluation criteria.

Unlock the rest of this lesson

You have read the free preview of Testing and shipping accessible iOS apps in Module 5: iOS accessibility. The full lesson, its knowledge check and the module certificate come with a plan, bought here on the web.

Buy a plan here with a card and the rest of the course unlocks. You will sign in first, with Apple or Google, which is what the plan is attached to. No iPhone or Mac needed.

Free with no account: the first lesson, Why accessibility, and who it is for, the European Accessibility Act flashcards and the overview of every lesson.

Sources