Re: Aria roles

First rule of aria: don’t use aria.

Like you Said: It’s just to fix problems that actually should not exist in the first place.

Of course this rule does not apply to cases where you need aria like aria-current, live regions and others without a html-element providing this kind of information implicitly. So in these cases you need it.

For maintaining and accessibility purposes I highly recommend to respect the intended separation of concerns.

Every full stack developer nowadays underestimates html. It’s a pity that the web is such a mess, because people just don’t respect best practices and principles like progressive enhancement, clean and lean code, small media, mobile first, HTML5 and CSS like it’s designed (markup your documents and use the cascade - it’s even in the name for gods sake!)...

Sorry, but the web turned in a bloated click baiting mess - for a developer it’s a pain to see what it has become.

You really have to search for well build websites like for a needle in the haystack.

--
Mit freundlichen Grüßen

Marc Haunschild
https://Accessibility.Consulting


Am 07.04.2021 um 14:56 schrieb Ms J <ms.jflz.woop@gmail.com>:


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<https://aka.ms/o0ukef>