Loading…
12
I saw a blind user struggle with a voice app in a coffee shop test
The app had a 'tap to speak' button but no screen reader hint. I added a simple ARIA label saying 'double tap to activate' and it cut their error rate by half in our next round. Has anyone else found a small fix that made a big difference for screen reader users?
3 comments
Log in to join the discussion
Log In3 Comments
taylorknight5mo ago
How many times have we all seen that happen? I mean, it's crazy how one missing label can totally block someone. I had a similar thing with a form submit button that just said "go." Changed it to "submit application" and the support calls dropped. It feels so obvious after the fact, but you just don't know until you test it with real people.
1
grant.kevin5mo ago
What gets me is when the label is there but it's in the wrong place. Screen readers might not connect it to the field, so the user hears nothing useful. It looks fine to us, but the code says something else. That hidden mismatch is worse than no label at all because you think you fixed it.
8
jasonl845mo ago
Ever try to catch those hidden mismatches in testing, @grant.kevin?
3