Marco ZeheFeb 26
Dani Devesa Derksen-Staats

Some people have been asking me to keep going with #365DaysIOSAccessibility, and I will! I promise!

But the other big ask was to have them all in one place. So here they are, in their new home:
https://accessibilityupto11.com/365-days-ios-accessibility/

#365DaysIOSAccessibility

A year-long journey exploring iOS accessibility, one day at a time, with practical tips and implementation ideas.

Accessibility up to 11!
Feb 26 at 9:36amWeb
Show threadDani Devesa Derksen-StaatsFeb 26

You can start from Day 1 and go through them in order:
https://accessibilityupto11.com/365-days-ios-accessibility/day-001/

Filter by topic, for example, all posts about the Accessibility Inspector:
https://accessibilityupto11.com/365-days-ios-accessibility/tag/accessibility-inspector/

You can subscribe to the RSS feed. And at the end of the post I suggest some related posts to keep learning about the topic.

If this can be useful to someone you know, please send it their way! And if you have a favorite tip, share it with everyone!

#iOSAccessibility #Accessibility #A11y

Day 1

UIAccessibility is the cornerstone of any accessible UIKit app. Among others, understanding what an accessibility label, value, trait or hint are, is key. This is an example of how they could be configured for a custom rating component. #GAAD2022

Accessibility up to 11!
Show threadMarco ZeheFeb 26
@dadederk This is so cool! And I see from the first entries that you also cover WatchOS, VisionOS and iPadOS. Do some of the posts also cross over to the Mac, e.g. when dealing with Catalyst apps? Or would that be so complex that it warranted its own series? Because I do see some major differences between Mac Catalyst apps and apps that are built on AppKit/traditional Mac-only native apps, when using both with VoiceOver. Especially with keyboard shortcuts and keyboard focus handling, it seems that in Catalyst apps developers need to do more heavy lifting than in traditional Mac apps.
Show threadDani Devesa Derksen-StaatsFeb 27
@marco Thanks, Marco! That's a really interesting point about the VoiceOver differences between Catalyst and AppKit apps. I wasn't aware of that. I'd love to cover macOS too, but my experience there is very limited (and always with SwiftUI), so I wouldn't want to speak to those specifics without doing a lot more research first. If you have any resources you'd recommend, I'd love to take a look!
Show threadMarco ZeheFeb 27
@dadederk I was speaking mostly from personal experience and also from talking to some indie developers who create apps for iOS and MacOS using catalyst and other techniques, and they told me how they often have to implement proper focus tracking when using controls with the keyboard, whereas native AppKit controls like tables and lists etc. give developers all that for free. And when you compare that to an iPad with a keyboard, keyboard focus tracking is virtually non-existent. So if you want it there, with all events and VoiceOver tracking the active element, you also have to do some heavy lifting, which then may or may not translate to the Mac Catalyst version. So this is quite a broad field still. But from usage, I immediately know whether the Mac app I'm using is native AppKit or Catalyst.