I don’t usually write about politics, but this one hurt a lot. Five years ago, this country shot itself in the foot. So tragic. It should have been a wake-up call that our choices as citizens matter, but I’m not so sure it was. Some choices can have long-lasting effects on society, if they’re reversible at all, as some of our friends in the US are attesting to right now too.
=> More informations about this toot | View the thread
I'm going to the Northernmost Apple Developers' conference: @ARCticConference!!! Who else is coming?! They’ve got a top-notch line-up of speakers!
And the best workshop selection I’ve ever seen at a conference! 😉
https://arcticonference.com
=> More informations about this toot | View the thread
We iOS engineers are increasingly finding ourselves becoming macOS developers too, thanks to how easy it has become to build multi-platform apps with Mac Catalyst or SwiftUI. This makes it even more important to understand how some of the assistive technologies we know from iOS also work on macOS.
Check out this fantastic post by @bas where he covers the basics of using VoiceOver on macOS!
https://www.basbroek.nl/macos-voiceover-first-time-huh
=> More informations about this toot | View the thread
Can’t believe it’s been 5 years since my book was published! Thank you to everyone who has read it and shared your kind words over the years. I’m humbled to think it might have contributed to making iOS apps a bit more accessible, thanks to your hard work.
[#]Accessibility
=> More informations about this toot | View the thread
Thanks for following along with the #adventOfiOSAccessibility series! Here's to building more accessible iOS apps in 2025! 🎉
If you’d like to revisit or share the series, I’ve compiled all the posts here: https://dadederk.github.io/post/2024-12-06-01/
=> More informations about this toot | View the thread
Day 24 - #adventOfIOSAccessibility. Test manually. Familiarise yourself with different assistive technologies. I find it useful to start with VoiceOver but check out Voice Control, Full Keyboard Access, and others... Remove friction, configuring shortcuts can help. Happy festive season everyone!
[#]365DaysIOSAccessibility
=> More informations about this toot | View the thread
Day 23 - #adventOfIOSAccessibility. Sometimes your UI will just not optimally scale for large text sizes. Simple changes, for accessibility sizes, like composing elements vertically instead of horizontally, reducing the number of columns, and allowing more lines of text, can do the trick most times.
[#]365DaysIOSAccessibility
=> More informations about this toot | View the thread
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
=> More informations about this toot | View the thread
Checkout UIKit's Accessibility Capabilities: https://developer.apple.com/documentation/uikit/accessibility-for-uikit#Capabilities
And SwiftUI's Accessibility environment variables: https://developer.apple.com/documentation/swiftui/environmentvalues#Accessibility
=> More informations about this toot | View the thread
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
=> More informations about this toot | View the thread
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.
UIKit: https://developer.apple.com/documentation/uikit/uiaccessibility/isreducemotionenabled
SwiftUI: https://developer.apple.com/documentation/swiftui/environmentvalues/accessibilityreducemotion
[#]365DaysIOSAccessibility
=> More informations about this toot | View the thread
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.
To know more about accessibilityUserInputLabels checkout: "Improving Accessibility: Voice Control" by @bas: https://basbroek.nl/improving-voice-control
[#]365DaysIOSAccessibility
=> More informations about this toot | View the thread
Day 18 - #adventOfIOSAccessibility. When building custom components, or if not relying on UIControl's attributes to configure state, it can be easy to forget to specify the right accessibility traits. These are indispensable for a good experience with VoiceOver, Switch Control, Voice Control, Full Keyboard Access...
[#]365DaysIOSAccessibility
=> More informations about this toot | View the thread
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
=> More informations about this toot | View the thread
Day 16 - #adventOfIOSAccessibility. A reminder that the more modes we use to convey important information, the more likely it is that all users will perceive it. Consider a combination. of color, icons, messages, sound, haptics, animations, etc.
[#]365DaysIOSAccessibility
=> More informations about this toot | View the thread
Day 15 - #adventOfIOSAccessibility. Touch target sizes are recommended to be at least 44 x 44 points for better usability. Buttons in the navigation bar (especially when not using nav bar button items), dismiss buttons, and custom toolbars, are common examples that often fall below this size.
[#]365DaysIOSAccessibility
=> More informations about this toot | View the thread
Day 14 - #adventOfIOSAccessibility. iOS and Xcode provide a wide variety of tools and options to deal with color, and help us providing good color contrast ratios. From system colors that automatically support Increase Contrast, to high contrast (and light and dark mode) color asset variants, automatic checks with the Audit feature in the Accessibility Inspector, and even a built-in contrast calculator.
[#]365DaysIOSAccessibility
=> More informations about this toot | View the thread
Day 13 - #adventOfIOSAccessibility. Sometimes, you may want to create a custom component, even if there is a similar one in UIKit or #SwiftUI because you want to style it in a way that the default one won't let you. Or add extra functionality. That's fine, but please take into account that you may need a bit of extra work to make it accessible.
[#]365DaysIOSAccessibility
=> More informations about this toot | View the thread
Day 12 - #adventOfIOSAccessibility. Sometimes we may fail to convey to the user 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 we might want to update on progress.
[#]365DaysIOSAccessibility
=> More informations about this toot | View the thread
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
=> More informations about this toot | View the thread
=> This profile with reblog | Go to dadederk@iosdev.space account This content has been proxied by September (3851b).Proxy Information
text/gemini