Webform already adds the HTML5 required attribute, so it is redundant to add the aria-required attribute as well. It adds no additional meaning. ARIA contains many attributes which already exit natively in HTML. ARIA has these for when it is used with languages which do not have native attributes with the meaning.

Comments

Liam Morland’s picture

maki3000’s picture

Webform already adds the HTML5 required attribute, so it is redundant to add the aria-required attribute as well

I'm not so sure if that is the way it is.

Here they say some slightly different things:
http://www.deque.com/blog/accessible-client-side-form-validation-html5-w...
https://www.paciellogroup.com/blog/2010/04/html5-and-the-myth-of-wai-ari...

And also the Webform ARIA Module could manage other WAI-ARIA property that are not supported by HTML5 like aria-labelledby. That still makes this module very interessting!

Liam Morland’s picture

Yes, it is semantically redundant; adding @aria-required adds no additional information if @required is already there. However, due to a lack of browser support, it may be needed to include both for the time being.

opdavies’s picture

Status: Active » Closed (works as designed)

I think that it's best to leave it there for now.

Liam Morland’s picture

Agreed.