Re: Tabindex on instructions

I took a quick look - and agree with the others NOT to follow techniques 
used on this site.

The reason you wern't hearing labels on form fields is that the 
associated labels have been hidden using display:none; which will also 
hide them from screen readers.

--James

On 9/6/2011 12:13 PM, David MacDonald wrote:
>
> I could access the form, but they don't have much of a sense of humour 
> about people testing their forms by putting in a random Social 
> security number, and my IP address was recorded and I was sent to a 
> not so nice page about having to go to an embassy to change my SS# 
> address ....
>
> In the bit of time I spent with it, System Access which is was what I 
> first surfed it with (before JAWS), didn't read out the form field 
> labels as I tabbed through it... (IE9).
>
> I didn't get a chance to look at the code or to test with other AT 
> before I got kicked out.
>
> I'm going to be very involved with a bunch of forms for the Canadian 
> government in the fall, and am glad to hear about the experience of 
> other governments and corporations, and to get better guidance in our 
> Techniques documents.
>
> Cheers
>
> David MacDonald
>
> www.eramp.com <http://www.eramp.com>
>
> *From:*w3c-wai-gl-request@w3.org [mailto:w3c-wai-gl-request@w3.org] 
> *On Behalf Of *Bailey, Bruce
> *Sent:* September-06-11 8:36 AM
> *To:* adam solomon
> *Cc:* w3c-wai-gl@w3.org; Sailesh Panchang
> *Subject:* RE: Tabindex on instructions
>
> Yes, portions of SSA site were unavailable for scheduled maintenance.  
> It looks to me like everything is up now.
>
> I cited SSA as evidence that the technique of having instructional 
> text in the tab order is used in the real world.  I don't think we can 
> point to the SSA forms, but mostly only because one has to "click 
> through" two pages to get to the demonstration.
>
> Yes, you are correct that what I wanted to see from your example is a 
> tabindex on instructional text paragraphs (which should be marked up 
> as P.  If we use tabindex on headers, I think that should be a 
> different example.
>