- From: Alastair Campbell <alastc@gmail.com>
- Date: Thu, 4 Apr 2013 22:01:14 +0100
- To: Bryan Garaventa <bryan.garaventa@whatsock.com>
- Cc: WAI Interest Group <w3c-wai-ig@w3.org>
Received on Thursday, 4 April 2013 21:01:47 UTC
"I have a scrollable div. I have programmed it to be fully keyboard accessible." I'm interested to know what needed "programming" there, why wasn't it accessible to start with? With a simple test case, a scrollable div itself is fine with VoiceOver: http://alastairc.ac/testing/scrollable-div.html It does not scroll itself visibly, but VoiceOver reads all the content. "The only place it is not accessible is on iOS because of Voiceover, since > Voiceover doesn't read content that is scrolled off screen." > I'm not convinced that is the case, there must be something else going on. Have you got a URL you can share? > "So apparently, what I'm hearing here is that this is actually desirable, > because the potential of developers screwing things up is greater than the > actual benefit of providing accessible features. > > Sort of like saying, blind people are not allowed to use this feature, for > their convenience. > > Is this correct?" > No. What you are hearing is that *if* coded to (HTML) standards and (WCAG) guidelines, it would be better for VoiceOver to fix an issue than the developer. [1] However, I doubt that is the case. -Alastair 1] Worth checking out how the different guidelines fit together for understanding this aspect: http://www.w3.org/WAI/intro/components.php
Received on Thursday, 4 April 2013 21:01:47 UTC