[NFBCS] Tips on Reporting Accessibility Issues to App Developers

Tina Hansen th404 at comcast.net
Sun Jun 12 23:41:58 UTC 2022


I'm not sure this is the right list, but I could use some advice on how to
report accessibility issues to app developers. I get frustrated when I see
an app that starts off strong, but accessibility faulters after an update.
In some apps, it's just the loss of clearly labeled buttons, but others take
a real sharp hit in the accessibility department and the buttons don't work.

 

I get frustrated, since it's likely they've never seen a blind customer, but
I sometimes fear that the only way to get these developers to take this
seriously is for a blind user to be looking over their shoulder at all
times, or for a user backed by automation, to hold these people accountable
somehow.

 

I'd love to see accessibility features somehow carry over as an app gets
updated, but short of some hard coding, how can that be done?

 

But I digress. I'm frustrated because I can see the problem, but I feel they
need to see what's going on so they can do something. I can send an e-mail
to report the problem, but I almost feel that graphics will do more than
descriptions alone.

 

So does anyone have any suggestions on how I might address this issue? I'm
stumped. Thanks.



More information about the NFBCS mailing list