Hello! I'm adding a new section for sun events to my weather app (Please Don't Rain) and can't decide what the best approach would be for VoiceOver.
There are going to be multiple rows. Which do you feel I should do for a row?
Option A - sentence
"Sunrise at 7:53am with a duration of 8 hours and 21 minutes until sunset at 4:14pm."
Option B - combined data
"sunrise 7:53am, duration 8 hours 21 minutes, sunset 4:14pm"
Option C - something else
Thank you for any assistance!
Comments
Option B, definitely.
It’s much more structured/ clear, the first option I had to think about for a minute, the second I didn’t.
Thank you
Thank you very much for the input! I implemented option A but then started second guessing myself. I'm glad I asked.
I like option a
I prefer option a.
votes
I wish I could make a poll. :)
Phrasing
Probably will not make everyone happy. If you could, I'd add a setting to allow the user to chose either of those options.
For myself and what I advise my clients, for an app that will be used a lot as presumably this one would, I am looking for the most efficient presentation of data. Unnecessary words, repeated helpful hints that can't be turned off, in the long run slow down the user.
So I would choose option B presentation.
Sunrise, sunset followed by the duration
That is what I would prefer.
Option B
Definitely option B for me, although I’d put the sunset before the duration as it’s the more useful piece of information.
Sunrise, Sunset, Duration
Sunrise, sunset, duration makes the most sense to me.
simplified presentation
Option B for me. Blind end users will need to read the entire line of text so keeping it as short and simple as possible is important for quick comprehension and usability.
Thank you
Thank you for the input everyone!
Table layout?
If it visually appears as a table, why not implement it as a table in the app?
Grid
It's going to be a grid with rows of sun events such as civil dawn/dusk and the duration on each row.
Table
It'd depend on the table/grid and the significance of each element if you'd want a full VoiceOver table navigation. Where each cell is an individual swipe.
And if there are headers each corresponding header would get announced. I am guessing for this app this is not desirable and a swipe for entire line/row will be more efficient. We're all kind of guessing of course and if the developer isn't a native VoiceOver user putting some live examples in the hands of users is always best. It is great to see someone considering it though, VoiceOver is forgotten about a lot!
Thank You!
Thank you, I take my accessibility support really seriously and I'm always trying to improve it.
That's a great point about trying it. I just submitted a TestFlight so that people can try it but it might take a while for it to get approved for testing because of the holidays.
Option B
Option b, though you could provide a setting to switch depending on the user's verbosity preference.
Setting
A setting to be more/less verbose is a really interesting idea. I'm going to experiment with it.
TestFlight
Apple approved my TestFlight. Here's a link that will let you experience what I've been referring to:
https://testflight.apple.com/join/KzfJ8nHU
The title of the section that I added is "Sun Events" and it has an accessibility trait of being a header for VoiceOver. It's currently doing Option A.
FYI, this is an odd weather app. Its goal is to keep track of the weather for a day that's important to you. You enter a day and a location and it will start monitoring the weather for that day.
New Setting
I just uploaded version 5.20.10 to TestFlight. Under Settings, accessibility there is a new section called "VoiceOver Verbosity" that lets you choose between "more verbose" and "less verbose".