4 ms·

How would iOS fix the seat selection example they gave?

• zepto 5y ago
  > for sure, you can build a custom UI that is inaccessible Provide a non custom UI alongside the custom one. Use tabs to offer ‘graphical’ and ‘list’ views. The comment I replied to said this: > In theory, yes, but in practice it's probably a very bad experience unless actively worked on It’s also not even clear that the UI they described was that bad for blind people. The voiceover information is relevant to making a selection, and the blind person can’t see that data so it needs to be read to them at some point. Of course it’s not as easy to use as if you can see it. They describe a search function, and I propose a plain list, but there isn’t a lot of evidence that either would require less interaction.
  • WastingMyTime89 5y ago
    > It’s also not even clear that the UI they described was that bad for blind people. Obviously it's bad. Becoming blind doesn't magically make you infinitely patient. Having to listen to a whole listing of airplane seats one by one with unnecessary details when you just want to book a place would probably make you crazy. Well it's the same for your blind users.
    • zepto 5y ago
      They shouldn’t need to listen to every seat. Voiceover doesn’t have to read everything - just what you touch.
      • albertsondev 5y ago
        So how does a blind user distinguish between each seat's offerings, then? How might they quickly skim those offerings to get a decent idea of what their options are in a way even remotely similar to the speed and efficacy of, say, icons?
        • zepto 5y ago
          > How might they quickly skim those offerings to get a decent idea of what their options are in a way even remotely similar to the speed and efficacy of, say, icons? They don’t. Why would you expect them to be able to?