I thought a bit more about this and I realised perhaps a better option
would be to display the JS-injected messages and errors that a screen
reader could not read but upon submission of the form, reload the page
and provide all the messages and errors again (the form could not be
completed anyway due to the errors; where else would to send the user
to?). This way users browsing with an accessibility aid like a screen
reader would not see the injected errors which are a nifty feature but
still be presented with them upon submission of the form and the page
reload.
Why I didn’t think of this earlier is beyond me. D’oh.
—Pascal
On 20/01/2009, at 12:57 PM, james.duc...@gmail.com wrote:
after all it's impossible to tell those users using an
accessibility aid like a screen reader
from those who do not, and hey, the growing number of users who
purposefully disable
JavaScript won't see the glitzy JavaScript injected errors anyway.
Agreed, and any decent validation is going to be done server-side
validation anyway, so you're going to have to (or at least you should)
implement the server-side responses in any case.
- James
--
James Ducker
Web Developer
http://www.studioj.net.au
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
*******************************************************************
---
Simon Pascal Klein
Concept designer
(w) http://klepas.org
(e) kle...@klepas.org
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
*******************************************************************
