Thread Subject: Re: Gaps in Web requirements -error handlingtechniques
This archival content is maintained by WebAIM and NCDAE on behalf of TEITAC and the U.S. Access Board . Additional details on the updates to section 508 and section 255 can be found at the Access Board web site.
From: Sean Hayes
Date: Wed, Jan 10 2007 8:30 AM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: Gregg Vanderheiden: "Re: Gaps in Web requirements -error handlingtechniques"
- Previous message in thread: None
- Messages sorted by: Author | Thread | Date
[quote: Mike Fratkin]The WCAG 2.0 provides some very good direction and techniques. However, the part that is missing from WCAG 2.0 is the ability to productively navigate to the error field in question. Pop-up messages are fine but when errors are identified at the top of the screen and when fields are flagged, there needs to be a way for the user to go directly to the field in error to correct the problem.
I don't necessarily disagree with you, but I would note that "going directly to the field in error" is a facility often not offered to the general user population either, and so might be considered a usability rather than an accessibility issue. Furthermore in a field filling exercise, there is often more than one field in error.
Standards and Policy Team
Accessible Technology Group
mob +44 7977 455002
office +44 117 9719730
- Next message in Thread: Gregg Vanderheiden: "Re: Gaps in Web requirements -error handlingtechniques"
- Previous message in Thread: None