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 prime, the LED timer as large as potential within the heart and the part “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 potential when VoiceOver is energetic as a result of there you may pan over the display to rapidly get to the recent spots of interactive parts.
I solved this by having individually adjustable sub-elements for the minutes and seconds whereas the timer just isn’t working. This fashion you may 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 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 by accident altering them.
Within the common movement of issues, VoiceOver principally feedback on the centered factor 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 provide 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.
I’d say my implementation is 95% excellent. There are some edge circumstances nonetheless – which I can’t do a lot about – the place VoiceOver will insist of talking one thing that it wouldn’t must. Sadly there isn’t any method to inform Accessibility to “shut it” for sure instances when there’s something extra vital occurring.
It price 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, 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 printed on Medium.