WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: ARIA and Label tags both for Error Messages

for

From: Susan Grossman
Date: Feb 13, 2014 6:03AM

On Thu, Feb 13, 2014 at 4:30 AM, Stanzel, Susan - FSA, Kansas City, MO <
<EMAIL REMOVED> > wrote:

> Good morning Listers,
>
> Okay, I understand placing the error at the top of the page. I thought
> JAWS should automatically speak the error. Is there something I can do to
> force that to happen?
>
> Susie Stanzel
>


Believe the ARIA alert role (role="alert") would do what you want. Think
that automatically triggers the "assertive" mode. For those with modern
versions.

Susan Grossman



>
> -----Original Message-----
> From: <EMAIL REMOVED> [mailto:
> <EMAIL REMOVED> ] On Behalf Of Don Mauck
> Sent: Wednesday, February 12, 2014 8:00 PM
> To: WebAIM Discussion List
> Subject: Re: [WebAIM] ARIA and Label tags both for Error Messages
>
> I think it should do both. That is, you should be informed of the error,
> then be able to find the error by looking for the H1 at the top of the
> page. After all, you need to hear that there is an error before you can go
> look for it if you didn't clearly hear it originally.
> -----Original Message-----
> From: Stanzel, Susan - FSA, Kansas City, MO [mailto:
> <EMAIL REMOVED> ]
> Sent: Wednesday, February 12, 2014 4:12 PM
> To: WebAIM Discussion List
> Subject: Re: [WebAIM] ARIA and Label tags both for Error Messages
>
> Hi Listers,
>
> I am coding Java Server pages to make them Section 508 compliant. I would
> like the application to behave in the following manner:
>
> The page is a form and after the user fills in the form the submit button
> is pushed. When I tested this application I found the errors were placed at
> the top of the page and to cause JAWS to tell them to me I have to go to
> the top of the page and hit "h" to go to the first heading. The sighted
> person likes this just fine because it is easy to look at the top of the
> page.
>
> Susie Stanzel
>
> What I would prefer is for the page to simply tell me the error. For those
> of you who might not know, a Java Server Page (JSP) is converted into
> actual html.
>
> -----Original Message-----
> From: <EMAIL REMOVED> [mailto:
> <EMAIL REMOVED> ] On Behalf Of Susan Grossman
> Sent: Tuesday, February 11, 2014 5:16 PM
> To: WebAIM Discussion List
> Subject: Re: [WebAIM] ARIA and Label tags both for Error Messages
>
> On Tue, Feb 11, 2014 at 2:34 PM, Hewitt,Susan (DSHS) <
> <EMAIL REMOVED> > wrote:
>
> > Do you mean you would include the error information within the label
> tag?
> > (Obviously you wouldn't to drop them completely.)
> >
>
>
> It's returning with an error state and we would:
> 1) append the error message to the label text in the existing label
> tag since the specification states one label to one form element
> 2) prepend an on-screen icon with alt text as error conditioner
> identifier
> 3) probably make the text red
> 4) They also want ARIA, though it looks like a consensus that we
> should push back on having both
>
>
> >
> > I agree with Yucca that this doesn't seem very semantic although I
> > think the case could be made that it's not forbidden. W3C spec says:
> > "The LABEL element may be used to attach information to controls." I
> > think that gives license to include error information within <label>
> > (after all, it's commonly used to provide formatting info and required
> > status after all.) I also don't think it's inappropriate to use
> > aria-describedby in this situation. But I would not use both methods.
> >
> > -----Original Message-----
> > From: <EMAIL REMOVED> [mailto:
> > <EMAIL REMOVED> ] On Behalf Of Susan Grossman
> > Sent: Tuesday, February 11, 2014 3:48 PM
> > To: WebAIM Discussion List
> > Subject: [WebAIM] ARIA and Label tags both for Error Messages
> >
> > We have been associating error messages to form fields using
> > aria-describedby, and the screen reader users who tested it thought it
> > worked well for them.
> >
> > We have gotten some push back from a federal agency saying that no
> > ARIA is supported well enough to rely on and that we must you both
> > aria and label tags to associate the error messages.
> >
> > My questions:
> >
> > 1) Do others agree that even aria-describedby (no Live Regions, etc.)
> > isn't supported enough to stand on it's own
> >
> > 2) Would the redundancy caused by both label tags and aria become too
> > much to hear for those who can utilize ARIA?
> >
> > 3) If yes to 1 and 2, does that leave us with just implementing the
> > association with label tags, or is there something else we should be
> > considering?
> >
> > Understand that we can still keep things like aria-required (or similar)
> > because they're a progressive enhancement - asterisk or (optional) is
> > still there in the form element label.
> >
> > Any help is appreciated - couldn't quite find this discussion in
> > archives
> >
> >
> > --
> > *Susan R. Grossman*
> > <EMAIL REMOVED>
> > > > > > list messages to <EMAIL REMOVED>
> > > > > > list messages to <EMAIL REMOVED>
> >
>
>
>
> --
> *Susan R. Grossman*
> <EMAIL REMOVED>
> > > messages to <EMAIL REMOVED>
>
>
>
>
>
> This electronic message contains information generated by the USDA solely
> for the intended recipients. Any unauthorized interception of this message
> or the use or disclosure of the information it contains may violate the law
> and subject the violator to civil or criminal penalties. If you believe you
> have received this message in error, please notify the sender and delete
> the email immediately.
>
> > > messages to <EMAIL REMOVED> > > messages to <EMAIL REMOVED>
>
>
> > > >



--
*Susan R. Grossman*
<EMAIL REMOVED>