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

Re: Forms & Screen Readers

From: Patrick Burke <burke@ucla.edu>
Date: Wed, 15 Aug 2001 10:41:00 -0700
Message-Id: <5.0.0.25.2.20010815102924.02435eb0@pop.bol.ucla.edu>
To: Brooke Dine <dine@ncbi.nlm.nih.gov>, w3cwai <w3c-wai-ig@w3.org>
This *usually* works the way you describe. I.e., screen readers can read 
text in the input fields, status of radio buttons, etc.

The best way to handle form errors is a different topic.

The coolest thing would be to get a page with only the error fields listed. 
In other words:

"We're sorry, no data was entered in field(s) which is/are required for 
this form:

Zip Code: _____   "

This would be Much much more efficient for a screen reader user than having 
to hunt thru the entire form to try to figure out what went wrong.

On the other hand I can think of situations where one might want to read 
the full form in context. For that situation, maybe the fields with errors 
could be marked with a unique (text) character or string.

Patrick

At 10:06 AM 8/15/01, Brooke Dine wrote:
>Hello All:
>
>Can screen readesrs read inputted text that users insert into online 
>forms?  Specifically, once someone has entered information (personal, etc) 
>into the form, hit "Submit" and had the form returned with a "You haven't 
>filled out all of the required fields."  Would the screen reader read both 
>the field names and the text within the fields as the person scrolled 
>through the form to determine what is missing?
Received on Wednesday, 15 August 2001 13:41:13 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 19 July 2011 18:13:55 GMT