Is Voice Access really this bad, or is my phone haunted?
Is Voice Access really this bad, or is my phone haunted?
if youre unfamiliar, its an accessibility app made by google, for controlling your phone with your voice. this is different to the “OK google” thing.
I’m disabled, and I avoided owning a phone for many years because they’re so painful to use. but this year I finally had to get one, so I got a samsung s10e. but this voice access app is just... terrible? its really buggy, struggles to understand me way worse than Talon (a PC voice control program), and loves to do things I don’t tell it to.
it also doesn’t even make my phone fully accessible, theres tons of gestures it just can’t do, and I can’t add custom ones.
basically... am I doing something wrong? is there some trick I don’t know about? or is android accessibility really this bad? is there anything I can do?
You're viewing a single thread.
I'm not a full time voice assistive tech user but I have a some experience in this area. Can you tell me which gestures you're missing / functions you're unable to activate and unexpected behaviour? Is it specific apps or websites, or all of them?
Voice Access does have a few settings which have helped me make it a little more reliable (it does not like my accent sometimes, especially if there's background noise) but without knowing more about the specifics it will be hard to tell whether there are some easy possible fixes or workarounds for the issues you're having.
the big issue is only being able to swipe left/right in the middle of the screen, I can’t scroll through pages of quick settings, the share dialog, or really anything that doesn’t appear in the middle. same issue with scrolling up and down, too, I have my font size bumped up a bit, so the “start screen recording” button needs to be scrolled down to, but you only scroll the button itself which voice access won’t do. theres some other examples but you get the idea.
occasionally if I say a command, it does it twice. I’ve had it happen on “tap X”, on saying numbers like in “show grid”, and sometimes (especially confusing) things like “send” sending a message and then typing the word send.
i also get lots of strange site specific bugs, like on mastodon I have to say my post in a single take, because saying a second sentence will clear what it already wrote. theres been way too many site specific bugs to list, but I run into them often.
also it understands me very poorly, I’m a native english speaker with an australian accent for context, and it really struggles with understanding me. short commands like “four” to tap label 4 are especially rough, but it takes me a few tries even with longer commands. theres not enough of a pattern to say its definitely an accent thing though. (talon does make some mistakes that are accent based, so its likely a factor. but it also makes way less mistakes than voice access with the same mic, so... shrug)
Ok yeah, I'm beginning to understand your problem.
Firstly, I haven't opened Voice Access in a while, but this is definitely worse than I remember. Some of it seems to be Android's fault, some of it seems to be Samsung's, but there is definitely some bad behaviour going on especially with magnification. It looks like Samsung's menu and overlay implementations are not working properly with Voice Access' magnifier, the show numbers and labels commands are all over the place. When using Voice Access' screen magnifier, they have also allowed for swiping to occur off-screen when zoomed in... so sometimes it swipes the wrong place because it's trying to do it from the centre of the edge, and sometimes you see nothing happen because that edge of the screen is out of view... Shonky work.
The good news is there's probably some workarounds for this. I'm constantly using grid mode ("show grid" / "hide grid" / "tap <square_number>" / "more squares" / "fewer squares" / "swipe <direction> <square_number>", "scroll <direction> from <square_number>" etc.), which reliably accounts for only gestures on the parts of the screen you can see and overrides most other menu, website and other interface items.
It looks also like the Phone Settings > Accessibility > Interaction and dexterity > Voice Access > Settings > More Options > Show Borders On might work a bit better for the "Show numbers" and "show labels" problems with screen magnification. It looks like I have to sometimes hide and then show them again after zooming in or out to get them to recalculate their positions, but it's better than trying to navigate with borders off.
duplicate commands
I did just have that happen. It looks like it might have to do with CPU or memory consumption, things seem to slow down while VA is going. You might have better luck if your apps that you're not actively using are fully closed, and you don't have 5000 chrome tabs like I do. This will definitely present issues for screen recording in addition to VA, along with other heavier tasks.
i also get lots of strange site specific bugs, like on mastodon I have to say my post in a single take, because saying a second sentence will clear what it already wrote. theres been way too many site specific bugs to list, but I run into them often.
Site specific bugs are usually because people are shit at accessibility. If you can send me an example link where I don't have to have an account or log in, i'll see if I can debug this one for you and get an issue opened if there's something they've done wrong. Site specific bugs can sometimes be worked around with a different browser though too, browsers are also shit.
also it understands me very poorly, I’m a native english speaker with an australian accent for context, and it really struggles with understanding me.
You're not fucking wrong, it keeps thinking i'm saying "Shore" instead of "show" and "top" instead of "tap". This was not this difficult previously, even in a noisier place. I am not sure what is going wrong here, but I can see that the settings for various language interace things are all over the place, it might be something buried deep in a menu somewhere. If you're able to speak really slowly and precisely, that will help, but I have no speech impediments and it's fucking driving me nuts. Make sure there's nothing rubbing against the mic or touching it too.
This is truly a painful UX experience, I'm sorry. Let me know if there's anything else I can maybe find an alternate action for that's more reliable, this is ludicrous.
this is super helpful, thank you. didn’t know about the “scroll <direction> from <number>”, thats genius.
also ill experiment with browsers, I’m using firefox since its what I use on my PC, but all the android browsers are haunted in their own ways. if I find anything consistently broken that doesn’t need a log in or credit card, ill give you a shout
No problem, you got lucky my brain is mostly working today and that this topic is in my very niche wheelhouse.
It also really grinds my gears that there is no documentation I have found for the actual full list of commands in VA and that I've had to trial and error discovery some of them. As though user interfaces weren't hard enough for people who use alternate input methods already. None of this should be this hard for anyone.