WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Form Errors w/ ARIA Alert Help

for

From: Paul Adam
Date: Oct 18, 2011 8:06AM

Are you opposed to putting the errors directly in the label?

On Tue, Oct 18, 2011 at 10:00 AM, Vincent Young < <EMAIL REMOVED> >wrote:

> This is just a simple example. That will be covered thanks. What I'm
> looking for is a good way for all the errors to be read first on page load
> when the first form field should be focused.
> On Oct 18, 2011 4:40 AM, "Jeevan Reddy" < <EMAIL REMOVED> >
> wrote:
>
> > Hi vincent,
> > I think, you are just hiding some error definitions and showing the
> > hidden information once the user submit the form..This is not feasible
> > solution!
> > you can use Tooltip to describe the error fields, or associate the error
> > descriptions with the corresponding fields using ARIA-described by
> > property.
> > this will meet your business requirement..
> >
> >
> > On Tue, Oct 18, 2011 at 10:01 AM, Vincent Young < <EMAIL REMOVED>
> > >wrote:
> >
> > > I'm hoping I can get some help here. I'm trying to trigger an ARIA
> alert
> > > on
> > > form errors w/ the business requirement that the first errored input
> > needs
> > > to get focus. Problem is, errors come back after form submission (i.e.
> > no
> > > JS error handling). The only way I was able to get this to work cross
> > > browser is the ugly implementation below:
> > >
> > > http://www.webhipster.com/testing/accessibility/alert/
> > >
> > > Does anyone know of a better way to do this? I really hate showing
> then
> > > hiding the errors then sticking a random element inside all after a
> > > settimeout.
> > >
> > > Thanks all!
> > >
> > > --
> > > WebHipster Interactive, ltd.
> > > Vincent Young - Principal
> > > 33 E. Lincoln St.
> > > Columbus, OH 43215
> > > p: 614.607.3400
> > > f: 339-674-3400
> > > e: <EMAIL REMOVED>
> > > w: http://www.webhipster.com
> > >