Re: Aria roles

?Hi Sarah,

The ARIA spec is your friend here
https://www.w3.org/TR/using-aria/#firstrule

It says:

If you can use a native HTML element [HTML51<https://www.w3.org/TR/using-aria/#bib-html51>] or attribute with the semantics and behavior you require already built in, instead of re-purposing an element and adding an ARIA role, state or property to make it accessible, then do so.

W3's emphasis, not mine (though I agree with it entirely).

So while sometimes a restrictive back-end will not allow a particular type of HTML in a location, and then perhaps ARIA is needed to bend the "wrong" HTML to the role, this is sad and clearly not ideal (a better back-end publishing system would be an improvement).

In a11y audits, generally I look for ARIA being used where there is not an HTML alternative; where it is adding to the HTML story rather than replacing it. For example, an open menu using aria-expanded="true" (etc) is a great addition to the semantics of a page.

I hope that's helpful and not too ARIA-101.

Regards,

Alan

-Alan Bristow
Web Programmer
Elections Canada
alan.bristow@elections.ca




From: Ms J <ms.jflz.woop@gmail.com>
Sent: Wednesday, April 7, 2021 8:51 AM
To: w3c-wai-ig@w3.org
Subject: Aria roles


Hi all


I was wondering if there was anything that specified whether aria roles should be applied to specific elements. For example, I have often seen websites implement a lot of their functionality using links, and then give the links new aria roles  such as 'button' or 'radio' to indicate their purpose rather than using the proper element in the first instance. Is this likely to cause any issues?


Thanks


Sarah


Get Outlook for iOS