- From: Alastair Campbell <acampbell@nomensa.com>
- Date: Mon, 5 Sep 2016 13:31:58 +0000
- To: Jonathan Avila <jon.avila@ssbbartgroup.com>
- CC: "public-mobile-a11y-tf@w3.org" <public-mobile-a11y-tf@w3.org>
Jonathan wrote: > “We should determine what is necessary to provide comparable access to people with disabilities. What platform vendors recommend may not take into account our target audience of users with disabilities even if they overall have a good track record. So, our recommendation should be based on research and evidence and simply not on any platform’s recommendation. “ Agreed, but all the evidence in the wiki [1] is based on platform standards or regular use, is there any research for people with mobility/dexterity issues? > “If our recommendation and the platforms happen to overlap or be close – great.“ If they match, it is a whole lot easier to deal with, promote, sell, and train people on. I’d go as far as saying it is like recommending a user-agent change, build it into the user-agent (documentation) because then it is the default. If the target should be bigger, make it bigger everywhere. Otherwise it will be something that requires significant design changes, and it will get pushed to triple-A and/or ignored. Sidenote: When we get people with mobility issues in for usability testing, they generally have a large phone. Historically an android phone set to use a lower resolution, or recently it could be an iPhone 6+ set to the iPhone 6 or 5s size (so everything is bigger). All the other points came down to making the guideline for people with disabilities, which I agree with, but we don’t seem to have any evidence about the differences. Perhaps (like with zoom issues) people have adaptations or other input methods to use with their devices that enable the use of standard-sized controls? Cheers, -Alastair 1] https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/Proposed_SC_Target_Size
Received on Monday, 5 September 2016 13:32:28 UTC