Updated for Xcode 12.0
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 special 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 Are you tired of wasting time debugging your Swift app? Instabug’s SDK is here to help you minimize debugging time by providing you with complete device details, network logs, and reproduction steps with every bug report. All data is attached automatically, and it only takes a line of code to setup. Start your free trial now and get 3 months off exclusively for the Hacking with Swift Community.
Link copied to your pasteboard.