W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > January to March 2012

RE: abindex technique

From: Adam Solomon <adam.solomon2@gmail.com>
Date: Tue, 31 Jan 2012 21:29:25 +0200
To: "'Sailesh Panchang'" <spanchang02@yahoo.com>, "'WCAG'" <w3c-wai-gl@w3.org>
Message-ID: <4f284120.c9840e0a.37d3.ffff8046@mx.google.com>
1. Agree - if you can provide a specific example (maybe something from an existing site) that would be great.
2. the script in example 3 (namely "$('#divDialog').show();") will turn display:none into display:block.

-----Original Message-----
From: Sailesh Panchang [mailto:spanchang02@yahoo.com] 
Sent: Tuesday, January 31, 2012 5:19 PM
To: 'WCAG'
Subject: Re: abindex technique

Two points:
1. I too believe adding tabindex=0 to paragraphs is not a good idea ... simply to make them tab-navigable, like the one in example#2. 
Yet, it may be useful for  a line or two of instructions placed between form controls with tabindex=0.  Non-sighted AT users might not skip over the instructions then.
2. In example#3, is it not important to turn off display:none when the alert-dialog is activated? This instruction is omitted in the example I think. 
Refer: <div id="divDialog" style="display: none">
Sailesh Panchang

--- On Tue, 1/31/12, Adam Solomon <adam.solomon2@gmail.com> wrote:

From: Adam Solomon <adam.solomon2@gmail.com>
Subject: FW: tabindex technique
To: "'WCAG'" <w3c-wai-gl@w3.org>
Date: Tuesday, January 31, 2012, 8:28 AM

One other point – example 2  in the technique document got bad reviews – most felt that we shouldn’t be adding tabindex to paragraphs. Would it better to use a series of headers and their corresponding content, and adding tabindex to each header? If not, can you suggest any others good examples with tabindex.

From: Adam Solomon [mailto:adam.solomon2@gmail.com] 
Sent: Tuesday, January 31, 2012 2:40 PM
To: 'WCAG'
Cc: 'Loretta Guarino Reid'
Subject: tabindex technique
As promised (better late than never), this email will hopefully begin a discussion of the proposed html5 technique we discussed at the meeting a few weeks back. Here is the link:
A number of issues were brought up:
1.       First and foremost is the question of whether this technique will be integrated with the html4 tabindex technique. I think we need to answer this question before any of the others. Has there been a consensus of whether to integrate html4 and html5 techniques (and just draw the distinction in the technology notes)? Personally I think all the html techniques, 4 or 5 should be a common set , and the distinction being in the technology notes (and perhaps some additional markup to draw attention to the fact that it is an html5 technique). I think integrating will make the whole process faster and easier for us. The issue was brought up at the task force meetings – was there a decision?
2.       How specific should we get about explaining how to implement tabindex (for instance, in the description currently there is a brief discussion about the different values (-,0,+) the tabindex attribute can have). Is this too verbose? How helpful should we be to developers in our explanations?
3.       Should the negative tabindex be included in this technique at all? The example of the light box is important, yet some felt it wasn’t relevant to this criterion (2.4.3).
Any responses appreciated
Received on Tuesday, 31 January 2012 19:30:05 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 16 January 2018 15:34:09 UTC