←back to thread

No ARIA is better than bad ARIA

(www.w3.org)
125 points robin_reala | 1 comments | 03 Dec 25 08:39 UTC | HN request time: 0s | source
Show context
gampleman ◴[09 Dec 25 10:27 UTC] No.46203385[source]▶
Is this really true? Messaging like this will cause a lot of developers to just give up. Most places I've worked at did accessibility at best as a best effort sort of thing. After reading this, there will be no attempts made to improve the state of affairs.

Perhaps that will be an improvement? I don't know.

replies(5): >>46203428 #>>46203474 #>>46203552 #>>46203918 #>>46204092 #
austin-cheney ◴[09 Dec 25 10:48 UTC] No.46203474[source]▶
ARIA is often a compensating technology more than a primary solution. I try to not use ARIA in my own code aside from the role attribute. I instead rely on the clear navigation and order HTML content and events as my primary solutions.
replies(1): >>46206230 #
no_wizard ◴[09 Dec 25 15:48 UTC] No.46206230[source]▶
Using the right elements (like button instead of a div) will take you very, very, very fair with little to no additional work.
replies(1): >>46207567 #
1. tracker1 ◴[09 Dec 25 17:15 UTC] No.46207567[source]▶
+1 here... <button> vs <a> in particular... if it's programmatic behavior, use a styled button if you want it to look like a link, and vice-versa for navigation behaviors.

I will add that a good component library should also handle some of this for you... in particular menu navigation, popouts/drawers etc. That said, can't say how many sites/apps have really broken behavior with this.