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: Fratkin, Mike
Date: Wed, Jan 10 2007 8:55 AM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: Slatin, John M: "Re: Gaps in Web requirements-error handlingtechniques"
- Previous message in thread: Brett, Thomas F: "Re: Gaps in Web requirements-error handlingtechniques"
- Messages sorted by: Author | Thread | Date
The point is that a mouse user can go directly to the field in error by
clicking in the field. The suggested error handling implementation
would be to provide a list of the errors at the top of the page (or
other easy keyboard access) and then when the error is selected, the
user would be placed in the error field. Subsequent errors would be
handled in the same manner.
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: Slatin, John M: "Re: Gaps in Web requirements-error handlingtechniques"
- Previous message in Thread: Brett, Thomas F: "Re: Gaps in Web requirements-error handlingtechniques"