Thread Subject: Re: Gaps in Webrequirements -error handlingtechniques
Note
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: David Poehlman
Date: Sat, Jan 20 2007 5:00 AM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: None
- Previous message in thread: Andi Snow-Weaver: "Re: Gaps in Webrequirements -errorhandlingtechniques"
- Messages sorted by: Author | Thread | Date
why not just prresent the errors and not the entire form?
On Jan 10, 2007, at 11:20 AM, Sean Hayes wrote:
The mouse user still has to locate the error field, which isn't
always easy in a big form; although granted it is probably easier
than having a screen reader re-read the entire form.
I like the idea of creating a set of in page links to the errors,
this would benefit all users. Although I'm not sure you can link
directly into an input field (nor indeed if you would actually want
to), you could certainly get close by linking to the label in front
of the input field.
Sean Hayes
Standards and Policy Team
Accessible Technology Group
Microsoft
Phone:
mob +44 7977 455002
office +44 117 9719730
-----Original Message-----
From: = EMAIL ADDRESS REMOVED = [mailto:teitac-
= EMAIL ADDRESS REMOVED = ] On Behalf Of Fratkin, Mike
Sent: 10 January 2007 15:54
To: TEITAC Web/Software Subcommittee
Subject: Re: [teitac-websoftware] Gaps in Web requirements -error
handlingtechniques
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.
Mike Fratkin
SSA
[Sean wrote:]
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.
Sean Hayes
Standards and Policy Team
Accessible Technology Group
Microsoft
Phone:
mob +44 7977 455002
office +44 117 9719730
- Next message in Thread: None
- Previous message in Thread: Andi Snow-Weaver: "Re: Gaps in Webrequirements -errorhandlingtechniques"
WebAIM is an initiative of:
