[ad_1]
Now you can absolutely function SpeakerClock with no or low imaginative and prescient. We gave SpeakerClock the complete Accessibility therapy. On this article I describe a few of the issues I discovered including accessibility options to SpeakerClock, now that it’s absolutely written in SwiftUI.
SpeakerClock’s UI is split into 3 sections, the presets on the prime, the LED timer as huge as doable within the heart and the part “site visitors gentle” on the backside.
The primary interplay gesture is to horizontally swipe over the LED digits to alter the timer. This type of gesture just isn’t doable when VoiceOver is lively as a result of there you’ll be able to pan over the display to rapidly get to the new spots of interactive components.
I solved this by having individually adjustable sub-elements for the minutes and seconds whereas the timer just isn’t operating. This manner you’ll be able to swipe vertically to regulate the minutes and seconds individually.
There are three sorts of ordinary gestures for Voice-Over which I made full use of:
- double-tap with single finger to pick out a component
- double-tap with two fingers to carry out a “magic faucet”
- draw a Z with two fingers to “escape”
I used #1 for the single-tap operate of the preset and talking part buttons. #2 substitutes for the lengthy press. The rationale is that you must consciously faucet with two fingers as a substitute of 1 to change the presets, as to forestall you from unintentionally altering them.
Within the common movement of issues, VoiceOver mainly feedback on the targeted factor and after a brief pause additionally reads out the accessibility trace that tells the person what interactions are doable. I additionally used VoiceOver’s announcement notifications to present audio suggestions on some interactions.
The cherry on prime is that sure timer values get purple out aloud. Within the yellow and inexperienced phases you get a voice immediate each minute. The part transitions get introduced as nicely. Within the purple part there may be an announcement very 15 seconds, with the ultimate 10 seconds being accompanied by beeps.
That felt like an affordable quantity of voice suggestions for starters. I’d add some configuration choices at a later level.
On this video I’m demonstrating all that we mentioned.
Conclusion
I’d say my implementation is 95% good. There are some edge instances nonetheless – which I can’t do a lot about – the place VoiceOver will insist of talking one thing that it wouldn’t have to. Sadly there isn’t a solution to inform Accessibility to “shut it” for sure occasions when there’s something extra necessary happening.
It value me plenty of experimenting and the higher a part of a day to get to this stage. I’m anxious to listen to from precise customers of SpeakerClock, particularly those that are visually impaired and may need use for a timer. And a few common customers additionally requested about acoustic suggestions. What kind of configuration choices associated to sounds may make sense?
Additionally revealed on Medium.
Associated
Classes: Updates
[ad_2]
