- From: Janina Sajka <janina@rednote.net>
- Date: Wed, 28 Mar 2012 14:56:51 -0400
- To: James Nurthen <james.nurthen@oracle.com>, "Joshue O'Connor" <joshue.oconnor@cfit.ie>
- Cc: Protocols and Formats Working Group WG <w3c-wai-pf@w3.org>, w3c-wai-gl@w3.org, HTML Accessibility Task Force <public-html-a11y@w3.org>, John Foliot <john@foliot.ca>, Judy Brewer <jbrewer@w3.org>, Laura Carlson <laura.lee.carlson@gmail.com>
James, Joshue, and All:
The Text Subteam of the HTML-A11Y Task Force has been discussion the
on-screen behavior of tab accessible hidden data. We believe it would be
very helpful if the HTML Techniques TF could provide appropriate
guidance to authors regarding the UI implications of doing this.
I believe Laura Carlson is aware of problematic examples in the wild, so
I've cc'd her and request that she reply with a pointer or two.
Here's the relevant extract from our minutes at:
http://lists.w3.org/Archives/Public/public-html-a11y/2012Mar/0389.html
<begin excerpt>
JF - this *does* work, but with lousy UI interaction
if you place tab-focusable content off screen it breaks UI
behavior
so it *does* work, but it introducing contraventions to WCAG
reqs
and so for that reason is unacceptable
Janina - Josh and James have begun an HTML5 / WCAG
techniques Task Force (joint TF with PF)
JF - so this needs to be captured in that group as
well
<janina> x/co-chair/co-chair/
Janina - be sure to capture that a table with 6
rows, 6 columns would introduce 36 tab-stops off
screen
<end excerpt>
Thank you for your consideration on this issue.
Janina
--
Janina Sajka, Phone: +1.443.300.2200
sip:janina@asterisk.rednote.net
Chair, Open Accessibility janina@a11y.org
Linux Foundation http://a11y.org
Chair, Protocols & Formats
Web Accessibility Initiative http://www.w3.org/wai/pf
World Wide Web Consortium (W3C)
Received on Wednesday, 28 March 2012 18:57:29 UTC