iOS Accessibility Labels
This blog was inspired by Jeff Watkins’ series of blogs on UIButton. UIButton is a fundamental part of building interfaces on iOS. So much so, that it probably doesn’t get the love it deserves. But it’s also really powerful and customisable when used correctly.
Accessibility labels on iOS I feel are very similar. They’re fundamental to how accessibility works on iOS, yet I think they suffer from a few PR issues. Firstly, Apple has done such a good job with them that we often don’t give the humble accessibility label the consideration it deserves, instead relying on the Apple default behaviour. Secondly, they’re just some text, right? Who can get excited about just a boring old label? Well, I’m sure this won’t surprise you, but I can.
What’s an Accessibility Label?
When iOS presents your app’s interface to assistive technologies such as VoiceOver, Voice Control or Switch Control, it’s not passing your app’s screen, but a representation of the screen in what’s known as an accessibility tree, or accessible user interface as Apple often call it. Your customer’s chosen assistive technology will then handle how to present your interface in the way that best suits your customer. But assistive technologies need something to present, and their first port of call is your element’s accessibility label. VoiceOver will read it, braille…
