WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: JAWS issue for mandatory fields

for

From: Steve Green
Date: Apr 16, 2018 5:05AM


Which browsers are behaving correctly in respect of this? And is there any indication the others intend to fix their behaviour?

I find that developers are very keen on this technique for some reason, and there are often no ARIA attributes for the information they want to convey.

Steve

-----Original Message-----
From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of Steve Faulkner
Sent: 16 April 2018 11:17
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: Re: [WebAIM] JAWS issue for mandatory fields

IE does not expose CSS before:/after: content in the accessibility tree, other browsers do, which is why you are experiencing the difference. Use of CSS to indicate state is not a robust method.

Suggest using aria-required="true" as this exposes the state in accessibility APIs.
https://www.w3.org/TR/wai-aria-1.1/#aria-required



--

Regards

SteveF
Current Standards Work @W3C
<http://www.paciellogroup.com/blog/2015/03/current-standards-work-at-w3c/>;

On 16 April 2018 at 11:06, Kakarla Meharoon < <EMAIL REMOVED> >
wrote:

> Hi,
>
> JAWS does not recognize the required field (*) in IE browser. If * is
> coded using Pseudo elements.
>
> But i checked in Chrome and FF * is read by JAWS but in IE browser
> only its not reading while tabbing as well as arrow key navigation.
> > > archives at http://webaim.org/discussion/archives
> >