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

Re: using a form field for terms & conditions

From: James Craig <work@cookiecrook.com>
Date: Fri, 15 Aug 2003 09:38:27 -0500
Message-ID: <3F3CF063.2040109@cookiecrook.com>
To: Lauke PH <P.H.Lauke@salford.ac.uk>
CC: "WAI Mailing list (E-mail)" <w3c-wai-ig@w3.org>

Lauke PH wrote:

> 1) obviously, screenreaders will announce that the user is currently
> in a form. The tc textarea will be announced as "Edit - Terms and Conditions".
> This can be slightly irritating. Moreover, the version of JAWS I used to test
> this (4.02) did not announce that it was in fact a read only edit box, so when
> entering the textarea, it will prompt the user to "type in text"...which obviously
> they can't. Not sure how other screenreaders handle this...

Does anyone else know if other screen readers notify a user that an edit 
field is disabled or read-only? If not, this seems like a problem with 
the readers, not the pages.

Just to clarify, I agree that the Terms content should be in a div, not 
a textarea. I am just wondering about legitimate uses of disabled and 
read-only form fields.

Thanks,
James Craig

-- 
http://www.cookiecrook.com/
Received on Friday, 15 August 2003 10:38:39 GMT

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