2 ms·
From a practical point, won't it be hard to know if the app is working if you can't see e.g. a field that the reader skips? It might be outweighted by that you
by rightbyte 4y ago
From a practical point, won't it be hard to know if the app is working if you can't see e.g. a field that the reader skips?
It might be outweighted by that you are good with the tools though.
- nkrisc 4y ago> From a practical point, won't it be hard to know if the app is working if you can't see e.g. a field that the reader skips? It wouldn’t be a very good test if they weren’t first provided with the expected outcome…
- Klathmon 4y agoCan't you say the same thing about a sighted tester who misses a field that the developer forgot to implement?
- blindprogrammer 4y agoThat's actually a good question, accessibility testing is meant for blind people, so what I will be testing is whether the component on the screen is readable by the screen reader. For example, one company that really makes all their apps accessible to the blind is Apple, every component, every gesture you could possible make sighted or otherwise is described by the screen reader (VoiceOVer). One company that has a poor accessibility, in other hand, is Chipotle. In my iPhone whenever I am using to order from the Chipotle app, I have to use the magnify the screen to see my remaining vision, otherwise VoiceOver won't tell me what the menu says. I am surprised Chipotle hasn't been sued for this since the app is straight up not accessible to totally blind people. One other fast food company that has a really good accessibility (at least in iOS) is Mcdonallds, every menu item is described extensively, and I could order anything blindfolded. Hey, Chipotle, follow McDonald's path and Apple, and make your app accessible, otherwise some blind guy will sue you in a federal court for not offering accessible shop for your restaurants.