WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: required field not being announced in Firefox/NVDA

for

From: Birkir R. Gunnarsson
Date: Oct 12, 2017 12:50PM

It's not valid HTML, just try to run it through the HTML Nu Checker:
https://validator.w3.org/nu/

It probably is not theculprit, but it's important to code HTML to standards.



On 10/12/17, Angela French < <EMAIL REMOVED> > wrote:
>
> We use required="true". Greg (my co-worker) says it does the same both
> ways. I guess that means it's a bug. I've never filed an NVDA bug. Surely
> it's been done before then? I tried search for it in the github list of
> issues, but perhaps I'm not searching correctly.
>
> Angela French
>
>
>
> -----Original Message-----
> From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf
> Of Birkir R. Gunnarsson
> Sent: Thursday, October 12, 2017 11:25 AM
> To: WebAIM Discussion List < <EMAIL REMOVED> >
> Subject: Re: [WebAIM] required field not being announced in Firefox/NVDA
>
> First of, you are just using "required" not "required="true") right?
> The required attribute can be provided without a value. I think
> required="true" is technically not valid HTML (where as aria-required has to
> have a value of "true").
>
> I doubt it makes a difference, but it's worth looking at.
>
> And I take it this problem comes up if user tries to submit a form with a
> required field that was left blank, the browser takes care of focusing the
> field.
>
> If all these assumptions are true, and if NVDA does not automatically read
> the label of that field, it is an NVDA bug and should be filed.
> It is not a complete user blocker, because the user can navigate away from
> the field and back to it to hear the label.
>
>
>
> On 10/12/17, Angela French < <EMAIL REMOVED> > wrote:
>> We are using the html required element (required="true") to indicate
>> required fields. The problem when testing with NVDA is that focus
>> goes to the required field but doesn't read the form label so the
>> screen reader user doesn't know which required field they missed.
>> The only way to find out, it seems, is to go back an element in the
>> form and then forward again so the label will be read. Is this a bug,
>> or are we doing something wrong? It works fine in Chrome. We've
>> given up on IE or Edge with NVDA,
>>
>> Thank you
>>
>> Angela French
>> Internet/Intranet Specialist
>> Washington State Board for Community and Technical Colleges
>> 360-704-4316
>> <EMAIL REMOVED> <mailto: <EMAIL REMOVED> >
>> www.sbctc.edu<;http://www.sbctc.edu/>;
>>
>> >> >> archives at http://webaim.org/discussion/archives
>> >>
>
>
> --
> Work hard. Have fun. Make history.
> > > http://webaim.org/discussion/archives
> > > > > >


--
Work hard. Have fun. Make history.