[NFBCS] Tips on Reporting Accessibility Issues to App Developers

[Lewis Wood]

When submitting feedback, explain what is lacking and how recent updates
have taken a step backwards.
Tell them how you have been enjoying using their app and recent changes are
disenfranchising you. Perhaps your developer simply overlooked this and your
quality control team faild as well. So here I am notifying you.

Good luck, perhaps someone has that link handy. If you cannot find it, I
will look for .

If it looks a bit legal the support staff are more likely to pass it up the
food chain.

Just for your convenience I am sending the the ADA compliancy specifications
link.  Something that all developers and companies should strive to comply
with.
Lewis Wood
lewislwood at gmail.com



-----Original Message-----
From: NFBCS <nfbcs-bounces at nfbnet.org> On Behalf Of Tina Hansen via NFBCS
Sent: Sunday, June 12, 2022 6:42 PM
To: nfbcs at nfbnet.org
Cc: Tina Hansen <th404 at comcast.net>
Subject: [NFBCS] Tips on Reporting Accessibility Issues to App Developers

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.

_______________________________________________
NFBCS mailing list
NFBCS at nfbnet.org
http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
To unsubscribe, change your list options or get your account info for NFBCS:
http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/lewislwood%40gmail.com