WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: html 5 required

for

From: Birkir R. Gunnarsson
Date: Aug 5, 2017 6:10PM

Wow, crazy.
This is probably new to NVDA 2017.2. Iremember testing this with I
think 2016.2 and both were announced fine.

IN general, I agree with the recommendation.
For one thing, the browser default error message overrides any custom
message you have (unless yu plug into the browser validation method,
it is doable but it takes quite a bit of JavaScript).
You can use a CSS :required pseudo class to customize the appearance
of the invalid inputs (I think), but again, it's tricky.

IN some browsers the default required error message is only visible
for about 5 seconds. This is not good for e.g. people with cognitive
impairments (or really anybody, I think an error message should be
persistent, at least until you start interacting with the field
again).
Sad, because it is attributes like these that can really shift the
accessibility load from developers to browsers (which would make our
lives a lot easier).




On 8/5/17, Jonathan Avila < <EMAIL REMOVED> > wrote:
>> I am confused. The label is exposed isn´t it, the way you wrote it.
>
> I can confirm that with NVDA after a form is submitted and focus is moved to
> the field in error in some browsers NVDA only announces the error and not
> the label. If you open the speech viewer you will find the label is there
> -- which I believe indicates that the error message is being treated like an
> assertive live region and somehow interrupting the label from being
> announced.
>
> In our testing of the HTML required attribute in different browsers the
> supports varied between browsers with screen readers. In addition, some
> browsers use a red border to indicate the error state while only providing a
> mouse involked tooltip further complicated the use of the required attribute
> as it could be claimed color alone was used to communicate the error
> visually to people with color deficiency who were not using a screen
> reader.
>
> I would agree with Patrick that at this time if you need to support multiple
> browsers and multiple AT the support is not there yet to fully conform with
> this method alone. It's a shame because it's a simple method that should be
> better supported without requiring developers to implement more complex and
> costly solutions.
>
> Jonathan
>
> Jonathan Avila
> Chief Accessibility Officer
> Level Access, inc. (formerly SSB BART Group, inc.)
> (703) 637-8957
> <EMAIL REMOVED>
> Visit us online: Website | Twitter | Facebook | LinkedIn | Blog
> Looking to boost your accessibility knowledge? Check out our free webinars!
>
> The information contained in this transmission may be attorney privileged
> and/or confidential information intended for the use of the individual or
> entity named above. If the reader of this message is not the intended
> recipient, you are hereby notified that any use, dissemination, distribution
> or copying of this communication is strictly prohibited.
>
>