#365DaysIOSAccessibility

Day 118

React to any content size category

13 Sep 2022

Accessibilitya11y

By

Dani Devesa Derksen-Staats

You don't have to offer an alternative layout just for the accessibility category. You can actually compare content size categories. So you could tweak the UI already for anything equal to or larger than .extraExtraLarge, for example.

Apple Music app example. It shows how for the extra extra extra large size, it still shows the default layout but text is starting to wrap up way too early. It also shows the AX1 size, and how from there, the rows for the tracks allow more than one line of text for the labels. And it also shows it for the AX3 size, where the layout changes a bit more, moving the cover art so it comes before the text and not next to it, allowing more space for the text. The code compares the preferred content size category and if it is equal or more than accessibility medium, it allows for more lines of text, if it is more or equal than accessibility extra large, it changes the layout, else, it uses the default layout.

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...

Day 200

Don't miss visual cues in accessibility labels

There are details conveying important information that are shown visually with little icons, badges, progress bars, and similar cues that can be missed when they are not added as part of the accessibility label or accessibility value of a UI component.

Day 50

Labels, traits, and values for the same experience

A similar experience can sometimes be achieved in different ways using labels, traits, and values. Most times there are no right or wrong answers; it will be up to your users to say which approach they like the most. Two great pieces of advice though: > **@Sommer:** "Check and see how Apple's own apps handle similar scenarios. Not because our apps are perfect but rather to help build on consistent patterns." > > Tweet by @Sommer > **@dotjay:** "Meet the platform expectations, and give users control rather than prescribing what you think users want." > > Tweet by @dotjay

Day 224

We have one job: make our apps work

"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

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

← Day 119
Day 117 →