Day 152

Takeaways from a11yTO for iOS developers

17 Oct 2022

Today and tomorrow I'll be learning at @a11yTO. There haven't been any talks about iOS specifically. But I thought I'd share in a thread some of today's learnings that I think still apply when developing accessible apps for iOS. #a11yTOconf

@a11yMel on continuous accessibility for quality at scale and reducing risks. Measure progress, but focus on people. When a measure becomes a target, it ceases to be a good measure. Accessibility is good for business but great for users.

Anna Cook talked about annotating designs for accessibility. Loved that she thinks of it as a communication and learning tool that can help bridge the gap between design and development. I'd give it a go and see if it works for your team.

Ann Mayer talked about writing accessible content. Technically compliant doesn't mean accessible. It is about being clear. The use of plain language principles, for example, is something that benefits everyone.

@DavidOfYork has shown how deceptive patterns harm people with anxiety and panic disorders. If you spot any of these in your app, call them out and raise awareness. We all suffer eventually from anxiety, accessibility is for everyone.

Michaela Peterhansl's practical guide for accessibility: Bring a11y to your daily work; you are not the only one responsible; ask questions; and find the people you can team-up with. "Don't forget: You can't do it alone", "Change is slow".

@DDame on how to get stakeholders to invest in accessibility through storytelling and data: I may have a disability, but my money doesn't. Do we want to exclude users? Offer them a bad experience? No. We will all be disabled one day.

Niki Ramesh gave useful tips to help you engage with a great a11y champions network. "Accessibility is not one person's job". Start informal/small, scale over time. Find representation across teams. Community, education, and recognition.

@ShellELittle talked about hiring accessible designers but touched on some points that apply to anyone working on accessibility. It can't be done by one person or you risk burnout.

Jennifer Payne on the importance of user research for building accessible products. Listen to users with disabilities. "Unless we consciously include, we unconsciously exclude".

@svinkle showed how important it is to shift accessibility to the left (early in the process) so you get more voices involved through ideation, prototyping, and design. And remember to prioritize progress over perfection.

Some of you have asked me how you can support what I do. This would really help, and would be hugely appreciated:

  • Find these posts useful? Share them at work, on social media, or with anyone that might find them interesting. Let's spread the word!

  • Check out any of my apps or games: Xarra!, RetroRapid!, or Mestre!.

    • A download and a review go a long way. They're free by default. On the App Store, ratings and reviews really help more people discover them.

    • Finding any of them useful? If so, and if you can afford it, purchasing lifetime access to all features or subscribing lets me buy the coffee that keeps me caffeinated. Caffeine keeps me going to maintain the apps, bring in new features that I hope you'll love, and keep writing.

You may also find interesting...

Second day of @a11yTO! And again, lots of talks with a ton of practical information. So here's a thread with some of my highlights. And very proud that @spotifydesign was one of the sponsors!

Once you learn some basic gestures with VoiceOver, it is very important to master he Rotor. It is very useful to also know some more power user gestures like the Magic Tap or the Escape gesture.

Reminder to enable Larger Accessibility Sizes, so you can pick from one of the five extra accessibility sizes when configuring text sizes. You can do it from Settings, Accessibility, Display & Text Size, and Larger Text.


Content © Daniel Devesa Derksen-Staats on Accessibility up to 11! is licensed under CC BY 4.0. License details