WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Accessible Form Validation Errors

for

From: julian.rickards@ndm.gov.on.ca
Date: Sep 2, 2004 2:29PM

Just as much as Windows is popular for sighted users, Windows is popular for
JAWS users too. Furthermore, just as much as IE is popular for sighted
users, IE is popular for JAWS users too. Therefore, most people who need
screen reader technology use JAWS as a layer on top of IE and Windows. It is
my understanding that most JAWS users have not disabled JavaScript in IE
(although it is possible to do) and therefore, most JAWS users encounter
JavaScript. Therefore, it is not the screen readers that enable/disable
JavaScript but the underlying browser.

The question then is, can users of screen readers work with pop-ups and
other JS features. Not always, especially if the JS functions, such as
menus, require the use of a mouse. Pop-up alerts, such as those encountered
during form validation may not be problematic for screen reader users but I
would prefer someone with more experience to comment on that.

Jules

Jules

-----Original Message-----
From: darrel.austin [mailto: <EMAIL REMOVED> ]

> What about preforming error checking as one tabs from field to field?

Client side checking is on our to-do list. We're using .net and .net's built
in client side sripting isn't the most browser agnostic, so we've put that
on hold for later. Good idea, though, and I guess this is a general
accessibility issue...do folks that use assistive devices like screen
readers enable javascipt? There seems to be more annoying use of javascript
these days than good. ;o)