Day 146

11 Oct 2022

If the user has Bold Text enabled, it will just work if you are using fonts based on text styles. If you have your own styles, or you are using a non-system font, you'll need to provide the bolder version of the font when the setting is on.

Some code shows how a single line is all you need for it to work with both Dynamic Type and Bold Text if you use preferred fonts for one of the pre-defined text styles. If you try to load a custom font, like Comic Sans, you then need to check if isBoldTextEnabled is true, and in that case, you need to load the bold version of the font. You can then retrieve the scaled font from UIFontMetrics, to have a similar behaviour to the system font, with the custom font.

You may also find interesting...

Day 147

Your iconography should support Bold Text too. One way of doing it is by creating custom symbols (and specifying weights for it) to work with them as you would with regular SF Symbols. How Creating custom symbols: https://developer.apple.com/videos/play/wwdc2021/10250/

Day 218

Make sure you support Dynamic Type up to the largest text size available. Take into account that there are five extra accessibility sizes available from the Accessibility Settings. It can make a huge difference for lots of users.

Day 112

With accessibilityRepresentation(representation:), you can create a custom component and it can be perceived by assistive technologies as the view you pass as representation. No need to manually configure accessibility attributes. It is one of the most interesting additions to SwiftUI to help you develop accessible UI components. If your custom component behaves similarly to a native one, this is the way to go. https://developer.apple.com/documentation/swiftui/view/accessibilityrepresentation(representation:)

Accessibility a11y

← Day 147

Day 145 →