[nfbcs] Seeking tips on advocating for an app to be more accessible

Vincenzo Rubano vincenzo.rubano at studio.unibo.it
Fri Feb 3 17:17:09 UTC 2017


I completely agree with Tracy. There are so many technologies for mobile app development out there that would be impossible for you to know how to implement accessibility support properly in each of them. And of course you cannot/don’t know the (many) implementation details of the application.

When reporting issues try to be as specific as possible. Make sure that for each issue you include:
- Exact steps to reproduce (detailed description);
- The outcome of the steps you performed;
- The outcome you would expect instead of the  actual one;
- Any information useful in order to give context (iOS version, device you are using, assistive technologies you use when the issue occurs, etc).

Also, do not assume that the person you are talking/writing to knows anything about VoiceOver and/or accessibility. Finally, including a reference to the iOS accessibility programming guide along with your issue report never hurts.


Vincenzo Rubano
Website:
https://www.nvapple.it/about-us
Personal website (italian only): http://www.titengodocchio.it

Il giorno 03 feb 2017, alle ore 17:22, Tracy Carcione via nfbcs <nfbcs at nfbnet.org<mailto:nfbcs at nfbnet.org>> ha scritto:

Speaking as an experienced programmer, I like it best when my users tell me
clearly what they want or what is not working well, preferably with very
recent examples.  I can then use my knowledge to make what they want happen.
I don't expect, or want, them to tell me how to do my job.
I would think it's the same for app programmers.  If you can tell them
clearly what you want, and perhaps point out resources for building
accessible apps, they should be able to do the rest.
HTH.
Tracy


-----Original Message-----
From: nfbcs [mailto:nfbcs-bounces at nfbnet.org] On Behalf Of Deborah Armstrong
via nfbcs
Sent: Friday, February 03, 2017 10:53 AM
To: nfbcs at nfbnet.org<mailto:nfbcs at nfbnet.org>
Cc: Deborah Armstrong
Subject: [nfbcs] Seeking tips on advocating for an app to be more accessible

I have discovered an absolutely wonderful iOS app that is only minimally
accessible.

I've posted everything on Applevis:

http://www.applevis.com/apps/ios/navigation/glympse#comment-68481

The app lets your friends track your location in realtime. This is a
wonderful idea if you are meeting up withsighted people in a location that
is unfamiliar to you. It's also great if you ride paratransit because your
family knows where you are, even if you don't!

Though location services are built in to iOS, if your friends are on Android
or at work with only a web browser,  they can't take advantage of this
ability to locate you.

Though I've programmed in Windows and DOS off and on for thirty years, I
know absolutely nothing about developing iOS apps.

What should I read so I can communicate more effectively with developers? I
don't want to read hundreds of pages on this subject; but I do want to study
enough so I sound informed and can give them effective tips.

Thanks.

--Debee

_______________________________________________
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/carcione%40access.net


_______________________________________________
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/vincenzo.rubano%40studio.unibo.it



More information about the NFBCS mailing list