3 ms·
You've entirely missed the point of my post, it makes no difference if the tools are built in or how quick they are to activate. Have you personally actually tr
by SimonPStevens 9y ago
You've entirely missed the point of my post, it makes no difference if the tools are built in or how quick they are to activate. Have you personally actually tried turning these tools on and testing your app?
My point is that I believe that all the people claiming it's easy are only doing the 'best practise' implementation (which I agree, is easy and doesn't add much time) but without actually testing that it all works smoothly they haven't finished and are just part of the problem.
My point is that from my direct personal experience with similar tools, it does not take 5 minutes. It takes weeks of additional testing and bug fixes to get a large app working smoothly with accessibility tools, after you've followed the best practise for the initial implementation.
- robin_reala 9y agoYes, I test in VoiceOver and Talkback (although for websites, not apps to be fair). But I dispute the assertion that it takes weeks. It takes a small amount of time per feature to test, and certainly no more than testing on multiple versions of the OS or multiple screen sizes. If on the other hand you’re throwing untested features over the wall to a QA team, then yes, it’ll be inefficient. That’s the nature of the beast.