#365DaysIOSAccessibility
Day 10 - #adventOfIOSAccessibility. Toggles or UISwitches are often found separated from the label that precedes (and describes) them; with an unclear label; missing a value, trait, or hint; or even not being actionable at all.

#365DaysIOSAccessibility
December 10, 2024 at 6:25 AM
Day 20 - #adventOfIOSAccessibility. There is an option for the user to request an experience with Reduce Motion, and we should honor it. If your app has animations, make sure to check if the user has this setting on. Here are three examples where Apple does a great job.

#365DaysIOSAccessibility
December 20, 2024 at 8:16 AM
Day 16 - #adventOfIOSAccessibility. A reminder that the more modes we use to convey important information, the more sure we'll be that it will be perceived by all our users. Consider a combination. of color, icons, messages, sound, haptics, animations, etc.

#365DaysIOSAccessibility
December 16, 2024 at 7:19 AM
Day 17 - #adventOfIOSAccessibility. Check the traversal order of elements in your app. Sometimes the default top-left to bottom-right order might not be the most logical one. Sometimes you may consciously want to tweak the order. Other times, grouping is the answer.

#365DaysIOSAccessibility
December 17, 2024 at 7:24 AM
Day 5 - #adventOfIOSAccessibility. Images should either be decorative or have a proper accessibility label or alt text that describes them. If they're decorative you can make it so they get skipped by assistive tech so it doesn't get in the way of the experience.

#365DaysIOSAccessibility
December 5, 2024 at 9:34 AM
Day 3 - #adventOfIOSAccessibility. Anything representing a heading in the app should have the header trait. It allows for a faster way of exploring a screen and quickly jumping to the part of the app you are interested in. Screens should also start with a header. #365DaysIOSAccessibility
December 3, 2024 at 7:32 AM
Day 9 - #adventOfIOSAccessibility. With interactions that are hidden, or require complex gestures to be performed, or that may conflict with VoiceOver, you need to provide alternative ways of executing these actions. Custom actions can help a lot of times, but not always.

#365DaysIOSAccessibility
December 9, 2024 at 9:22 AM
Day 8 - #adventOfIOSAccessibility. If a view has isAccessibilityElement to true, assistive tech won't look for any of its subviews. That means that if there are any buttons inside, they won't be accessible. You can add custom actions to be able to 'interact' with them.

#365DaysIOSAccessibility
December 8, 2024 at 10:33 AM
Day 19 - #adventOfIOSAccessibility. Accessibility labels might not be the best input labels, used for example to find or interact with elements with Voice Control or Full Keyboard Access. In those cases, you can provide accessibility user input labels.

#365DaysIOSAccessibility
December 19, 2024 at 7:44 AM
Day 11 - #adventOfIOSAccessibility. Have you ever seen VoiceOver randomly focusing on elements of the previous view when presenting a custom modal view? That can be fixed by letting the system know that the presented view is modal in terms of accessibility.

#365DaysIOSAccessibility
December 11, 2024 at 10:05 AM
Day 7 - #adventOfIOSAccessibility. Grouping elements when it makes sense can make a huge impact on easing navigation with some assistive technologies like VoiceOver, Switch Control, or Full Keyboard Access. It also helps on reducing redundancy.

#365DaysIOSAccessibility
December 7, 2024 at 9:50 AM
Day 1 - #adventOfIOSAccessibility. One of the accessibility issues I see more often in iOS apps, believe it or not, is unlabelled elements. This happens especially for buttons with an icon but no title. In those cases, you need to configure an accessibility label manually.

#365DaysIOSAccessibility
December 1, 2024 at 2:20 PM
Day 12 - #adventOfIOSAccessibility. Sometimes we may fail to update users of things changing on the screen in a perceivable way. Toasts and similar should be announced. We may want to make clear that some content on the screen changed or to update on a task's progress.

#365DaysIOSAccessibility
December 12, 2024 at 11:28 AM
Day 21 - #adventOfIOSAccessibility. There are a few accessibility settings you can check for, or get notifications in case these preferences change. This is especially important when developing custom components as they will mostly work with UIKit and SwiftUI controls.

#365DaysIOSAccessibility
December 21, 2024 at 11:51 AM
Day 5 - #adventOfIOSAccessibility. Ensure images are either decorative or have descriptive accessibility labels to enhance user experience. #365DaysIOSAccessibility
December 5, 2024 at 6:38 PM
Day 22 - #adventOfIOSAccessibility. 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.

#365DaysIOSAccessibility
December 22, 2024 at 9:10 AM
Day 4 - #adventOfIOSAccessibility. Important information is often conveyed visually through icons, badges, or progress bars... These details can easily be overlooked. Please make sure they're part of your UI's components' accessibility labels or values.

#365DaysIOSAccessibility
December 4, 2024 at 10:11 AM
Day 2 - #adventOfIOSAccessibility. Some recommendations for improving your accessibility labels: don't add the element type, avoid redundancy and verbosity, localize...

#365DaysIOSAccessibility
December 2, 2024 at 9:06 AM