Updated for Xcode 14.0 beta 1
By default SwiftUI apps come with a remarkably high level of accessibility, which is no accident – it was planned into the framework from the earliest days, and unless you actively choose to work around the defaults you’ll find your apps do a good job of being accessible without much extra work from you.
The key to this behavior is the stack-based approach of SwiftUI’s layouts: everything has a natural order because we place things inside
VStack, so the system can understand roughly how our layout should flow. In comparison, UIKit and Auto Layout let us place things anywhere, so the system effectively had to make a best guess as to how things should be ordered.
SwiftUI also strongly encourages us to add labels to all our interactive controls, explicitly saying what everything is for. Yes, we can hide those labels, but even when they are hidden they are still used by the system as audio prompts for the screen reader and more.
So, SwiftUI gives us a lot of accessibility for free. However, it still gives us extra tools to provide a more enhanced experience: how should things be read by the screen reader? Does everything need to be read? What if the user prefers not to have fancy animations?
In this collection of chapters we’re going to look at these more advanced pieces of functionality, hopefully helping you build user interfaces that provide users with a comfortable experience regardless of their system preferences.
SPONSORED In-app subscriptions are a pain. The code can be hard to write, full of edge cases, and time-consuming to maintain. RevenueCat provides a backend and wrapper around StoreKit to make things simple so you can focus on building your app.
Link copied to your pasteboard.