W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > July to September 2002

RE: auto set focus and accessibility

From: Geoff Deering <gdeering@acslink.net.au>
Date: Wed, 7 Aug 2002 10:21:50 +1000
To: "Lisa Seeman" <seeman@netvision.net.il>, "W3c-Wai-Gl@W3.Org \(E-mail\)" <w3c-wai-gl@w3.org>
Message-ID: <NBBBJPNFCLNLAADCLFJBKEMLDJAA.gdeering@acslink.net.au>
Interesting issue.  What about the issue of client side form validation…
when the form is validated and, say, the third field contains invalid data,
in that case, is it assisting usability to put the focus on the first field
where the data needs to be edited?  How should this be handled?  Just ignore
using focus?

Geoff Deering
P.S.  I’ve been missing in action on these lists for a while, but hope to be
able to contribute again (whilst I have the time and opportunity).


-----Original Message-----
From: w3c-wai-gl-request@w3.org [mailto:w3c-wai-gl-request@w3.org]On Behalf
Of Lisa Seeman
Sent: Wednesday, 7 August 2002 3:52 AM
To: W3c-Wai-Gl@W3.Org (E-mail); W3c-Wai-Pf@W3.Org (E-mail)
Subject: auto set focus and accessibility

I came across something new as I was Jaws browsing along, and that is the
auto focused of the page had been set to a text box mid way down the page
(you can see it at
http://www.Amazon.com/exec/obidos/subst/home/home.html/002-5628707-8901611)

this made the screen reader start from the text box and miss the info above
it.
It stumped me how they had managed to do this, but then I found in their
code
onLoad="document.searchform.elements[1].focus()"
That did it.

Did I miss this in WCAG ?  it seems an accessibility issue.
It also may be an issue for the DOM object model - allowing a script to move
and control the focus and bounce you around the page without your knowledge.
All the best,
Lisa Seeman
UnBounded Access
Widen the World Web
http://www.UBaccess.com
Received on Wednesday, 7 August 2002 19:16:00 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:47:19 GMT