3 ms·
May be worth pointing out for iOS devs doing automated testing - KIF (and maybe Frank, I'm less familiar with Frank) hijacks the accessibility labels on control
by potatolicious 12y ago
May be worth pointing out for iOS devs doing automated testing - KIF (and maybe Frank, I'm less familiar with Frank) hijacks the accessibility labels on controls in order to facilitate input injection.
This breaks a lot of the implicit/default blind accessibility behavior of the OS.
If you're using KIF, please make sure, even if you're not putting extra effort into accessibility, that at least you're not breaking the defaults with your testing framework.
- vanwesson 12y agoAt the other end of the spectrum, there's Subliminal[1], which relies on Apple's UIAutomation underneath, which in turn relies on the application's accessibility information as-is, rather than hijacking it. Building up tests using either UIAutomation or something that sits on top of it like Subliminal will actually help you improve your app's accessibility at the same time. [1] https://github.com/inkling/subliminal https://github.com/inkling/subliminal
- kinofcain 12y agoThis. One of the common stories in accessibility circles is "curb cuts", the ramps from streets to sidewalks that allow disabled people easier access than a stepped curb. They have utility for non-disabled persons towing roller luggage, pushing strollers, pulling hand-carts, etc. While they were put in place due to accessibility concerns, they benefit everyone. Accessibility facilities that enable UI automation are the "curb cuts" of software.