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 145

In iOS' Settings you can specify your preference to use bold text. This can be checked in code in a couple ways: 1. isBoldTextEnabled in UIAccessibility: https://developer.apple.com/documentation/uikit/uiaccessibility/isboldtextenabled 2. legibilityWeight from UITraitCollection: https://developer.apple.com/documentation/uikit/uitraitcollection/legibilityweight

Day 157

Manual testing is crucial. And therefore, reducing friction to let you start your testing process can be a huge help. Selecting some accessibility shortcuts will do that, putting most of iOS' accessibility features at a triple-click of a button.

Accessibility a11y

Day 61

To capture the gesture, you can override the accessibilityPerformEscape() function. In there you can dismiss your view, and return true if you could successfully handle it. https://developer.apple.com/documentation/objectivec/nsobject-swift.class/accessibilityperformescape()

Accessibility a11y

← Day 147

Day 145 →