WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Question about reporting aria elements


From: glen walker
Date: Oct 22, 2020 10:16AM

That depends what kind of testing and reporting you're doing.

If you are doing strict WCAG failures, then using ARIA instead of native
HTML is not a failure. The first rule of ARIA (
https://www.w3.org/TR/aria-in-html/#rule1) says to use native HTML if
possible, but even if that's not done, it's just a best practice and not a

If you find that the wrong ARIA attribute is used, for example,
aria-selected is set on a button, then that could be reported. It would be
a 4.1.2 issue because the state of the button will not be announced
properly (since aria-selected is not allowed on a button). Aria-pressed
was probably intended.

If aria-pressed is set on a button but the value is set to "yes" and "no"
instead of "true" and "false", that could also be a 4.1.2 failure because,
again, the state will not be reported correctly.

In those two examples, I would rather report it as a 4.1.1 parsing
failure. In fact, if you use the html parser (https://validator.w3.org/nu)
on the above examples, both fail. But 4.1.1 only lists four types of
parsing errors and using incorrect attributes or incorrect values for
attributes are not in that list. It might be nice if 4.1.1 were updated to
include those types of parsing errors.

On Thu, Oct 22, 2020 at 4:51 AM Всеволод Попов < <EMAIL REMOVED> >

> Hello everyone,
> Do I understand correctly that when reporting aria elements it's better
> to point that it's better to replace aria elements with html equivalents
> when and if possible?
> Usually I write that but there is one more question.
> In that cases In standards and guidelines section I usually insert the
> links on wcag that wave provides, but I am not sure if it is correct in
> that situation.
> Is it normal to insert wcag links or it's better to search the needed
> recommendations in aria and then insert them?
> Thank you in advance.
> --
> Best regardss,
> Vsievolod
> > > > >