Now you can totally function SpeakerClock with no or low imaginative and prescient. We gave SpeakerClock the complete Accessibility remedy. On this article I describe a number of the issues I realized including accessibility options to SpeakerClock, now that it’s totally written in SwiftUI.
SpeakerClock’s UI is split into 3 sections, the presets on the high, the LED timer as huge as potential within the middle and the part “visitors gentle” on the backside.
The principle interplay gesture is to horizontally swipe over the LED digits to alter the timer. This sort of gesture isn’t potential when VoiceOver is lively as a result of there you may pan over the display screen to shortly 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 isn’t operating. This manner you may swipe vertically to regulate the minutes and seconds individually.
There are three varieties 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 it’s a must to consciously faucet with two fingers as a substitute of 1 to switch the presets, as to stop you from by chance altering them.
Within the common movement of issues, VoiceOver mainly feedback on the centered ingredient and after a brief pause additionally reads out the accessibility trace that tells the consumer what interactions are potential. I additionally used VoiceOver’s announcement notifications to offer audio suggestions on some interactions.
The cherry on high 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 properly. 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 would add some configuration choices at a later level.
On this video I’m demonstrating all that we mentioned.
I’d say my implementation is 95% good. There are some edge instances nonetheless – which I can not do a lot about – the place VoiceOver will insist of talking one thing that it wouldn’t have to. Sadly there is no such thing as a strategy to inform Accessibility to “shut it” for sure occasions when there’s something extra essential occurring.
It value me lots 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, specifically those that are visually impaired and might 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.