- From: Gregg Vanderheiden <gv@trace.wisc.edu>
- Date: Thu, 07 Jan 2010 10:36:51 -0600
- To: Andi Snow-Weaver <andisnow@us.ibm.com>
- Cc: WCAG <w3c-wai-gl@w3.org>
- Message-id: <3E3013E5-B7E1-4723-A060-DF37C4C142E9@trace.wisc.edu>
Do you mean a form where nobody knows which fields are required until after the fail to fill some in? if no-one knows then I would think it was a usability issue (bad design) (very bad design) if most people know-- then how did they know? That information needs to be accessible to all. Gregg ----------------------- Gregg Vanderheiden Ph.D. Director Trace R&D Center Professor Industrial & Systems Engineering and Biomedical Engineering University of Wisconsin-Madison On Jan 7, 2010, at 10:31 AM, Andi Snow-Weaver wrote: > A member of my team has raised a question about the techniques for 3.3.2. > > Specifically, in bullet 1, why is G83 allowed? This technique is saying that it's okay to have required form fields that are not identified until after the user has failed to enter any data. We have an HTML technique (H90) that includes an example of including text in the <label> element to indicate required fields. And we have a failure technique (F81) that says you can't use color only to indicate the required fields. But we apparently have nothing that requires required fields to be identified before the user tries to submit a form. > > Was this intentional or did we miss something? I guess you could rationalize that if the required fields are not identified at all, then it's not an accessibility issue. It's a usability issue for everyone. So maybe that's why we don't require it. > > Thanks, > Andi >
Received on Thursday, 7 January 2010 16:37:28 UTC