Re: Tabindex on instructions

Sorry for the delayed response, but I couldn't access the link until now for
some strange reason (maybe ssa is finally going broke). I see where they
have implemented tabindex to tab through the page. I tend to agree with
Sailesh that the implementation is not good. Incorrect use of headers and
too many tabindexed elements. I could build my own example predicated on
this page. Am I correct that what you guys want to see from this example is
a tabindex on the headers and on the text paragraphs (which should be marked
up as <p>)? If so, we could modify the current example 2 from the proposed
technique to include tabindex on the <p> elements. Please let me know
exactly what you elements you think we should add tabindex to in the
example, or how to change the example.

Re: Jon's proposed example for tabindex, which is something like a tabs
control widget, I think tabs control headers should always have links in
them. The reason for this is that when one presses a tab header, he expects
to be taken to the content of that tab. I don't think we should present an
example of tabs control where links are not present in the headers, since
for this control there is a native html fix and no need to use aria here.
Please advise.

On Sun, Sep 4, 2011 at 2:54 AM, Sailesh Panchang <spanchang02@yahoo.com>wrote:

> Pardon me for jumping in but I looked at the Change of Address Form. I do
> see it uses tabindex=0 but even on the form title "Please enter your info"
> which is h1 and not an instruction. It does not have to be tab-navigable.
> (For S508 para (n) only requires instructions are available ... do not have
> to be ttabbable).
> Every piece of text in that form is marked up with h<n> tag  although they
> are not section headings. In fact instructions are marked up as off-screen
> labels for form controls and it reads a two line piece of text for a form
> label! Visible labels marked up as h3 are not marked up as labels .
> So a screen reader user is exposed to the same piece of text 2 or 3 times
> which is a big obstacle for efficient access and task performance.
>
> This page should not be cited as an example for anything except for the
> failure I have been encouraging the WCAG to consider for very long:
> incorrect application of accessibility techniques poses an  accessibility
> barrier and should be strongly discouraged.
>
> Thanks,
> Sailesh Panchang
>
>
> --- On Sat, 9/3/11, Bailey, Bruce <Bailey@Access-Board.gov> wrote:
>
>
> From: Bailey, Bruce <Bailey@Access-Board.gov>
> Subject: RE: Tabindex on instructions
> To: "Loretta Guarino Reid" <lorettaguarino@google.com>, "adam solomon" <
> adam.solomon2@gmail.com>, "David MacDonald" <david100@sympatico.ca>
> Cc: w3c-wai-gl@w3.org
> Date: Saturday, September 3, 2011, 7:42 AM
>
>
>
> SSA has been using @tabindex=0 to make instructional text on forms
> focusable for a while.
>
> Their guidance is available from here:
> http://www.ssa.gov/oag/acq/oagacq_508.htm
>
> SSA's Guide to Applying Section 508 Standards:
>
> http://www.ssa.gov/oag/info/SSA's%20Guide%20to%20Applying%20Section%20508%20Standards.pdf<http://www.ssa.gov/oag/info/SSA%27s%20Guide%20to%20Applying%20Section%20508%20Standards.pdf>
>
> The relevant bit is on page 49 in relation to testing against 1194.22(n).
>
> The simplest example I could find of @tabindex is their change of address
> form:
> https://secure.ssa.gov/apps6z/ICOA/main.html
>
> You have to select the OK button to get the actual form.  @tabindex=0 is
> set on a DIV and a couple SPANs.
>
>
> -----Original Message-----
> From: Loretta Guarino Reid [mailto:lorettaguarino@google.com]
> Sent: Thu 9/1/2011 5:19 PM
> To: Bailey, Bruce
> Cc: adam solomon; David MacDonald
> Subject: Tabindex on instructions
>
> This is the reminder email to send  a pointer to your pages with focusable
> instructions.
>
>
>
>
>
>