We have a new technique project today, this time focusing on something you might not even have considered: accessibility. This is a measure of how well our app can be used by people with varying access needs – they might need larger text, they might need us to avoid certain colors to help them see things clearly, they might need our UI to be read out, and so on.
Too many developers completely ignore the importance of accessibility, which results in apps that are completely opaque to large numbers of people. Tony Fadell – the creator of the iPod at Apple – had this to say: “you are defined by what you do and also by what you don’t do.”
Sure, you can skip accessibility and 90% of people won’t notice, but do you want to be defined by that? I’d wager that the answer is no.
Today you have four topics to work through, in which you’ll learn about accessibility labels, values, hints, and more.
When you’re done, try using some other apps on your phone with VoiceOver turned on – can you find any that need some improvement?
Need help? Tweet me @twostraws!
SPONSORED Would you describe yourself as knowledgeable, but struggling when you have to come up with your own code? Fernando Olivares has a new book containing iOS rules you can immediately apply to your coding habits to see dramatic improvements, while also teaching applied programming fundamentals seen in refactored code from published apps.
Link copied to your pasteboard.