Today starts the #WWDC22 . Apple announces what new APIs we'll be able to use to make more inclusive and accessible apps. There's also Labs, Digital Lounges and Sessions, for free.

Check out the schedule here:

https://developer.apple.com/wwdc25/topics/accessibility-inclusion/

Last year, Apple presented Audio Graphs to make graphs more accessible. This year, they introduced Swift Charts, that lets you build a wide variety of charts in SwiftUI and they have great VoiceOver support.

https://developer.apple.com/documentation/Charts

@dnlyong has a great thread going through lots of the new accessibility features presented this year.

https://x.com/dnlyong/status/1533897274274639873

As noted by @RobRWAPP and @mecid, Apple is tweaking the style of the SwiftUI accessibility modifiers.

https://x.com/RobRWAPP/status/1533900962615762945

Sessions this year include topics like gaming (with Unity), localisation and internationalisation. You can check these (as they get published during the week) and previous accessibility sessions here: https://developer.apple.com/videos/accessibility-inclusion/

SwiftUI lets you now add multiple accessibility actions at once and quick actions to be show by the system when active:

https://developer.apple.com/documentation/swiftui/view/accessibilityactions(:)?changes=latestminor

https://developer.apple.com/documentation/swiftui/view/accessibilityquickaction(style:content:)?changes=latestminor

You may also find interesting...

Apple recommends in their guidelines a minimum tappable area size of 44x44 points for all controls. A lot of times this can be corrected in an app without changing how it looks, but making it objectively easier to interact with for everyone.

If you want to know everything about how to "Tailor the VoiceOver experience in your data-rich apps" with the Accessibility Custom Content API, there is a WWDC21 session. https://developer.apple.com/videos/play/wwdc2021/10121/ When implementing accessibilityCustomContent, for any supplementary information, it returns an array that VoiceOver will announce in that given order. The value of the AXCustomContent first, then the label. Users can configure in VoiceOver's verbosity settings if it should say that there's more content available, or play a sound hinting that there is, or simply do nothing. So it should really be optional content as users might miss it.

"We have one job, and that's to make our apps work. And if you are not implementing accessibility features, you are forgetting about making it work for a lot of people" @NovallSwift Couldn't have said it better! https://x.com/novallswift/status/1328387659744505856

Created in Swift with Ignite.

Supporting Swift for Swifts