←back to thread

125 points robin_reala | 2 comments | | HN request time: 0s | source
1. burningChrome ◴[] No.46207069[source]
Interesting as a developer coming into accessibility, I was repeatedly told, "The first rule of ARIA is not to use ARIA."

It feels like we've gone so far away from semantical code that ARIA is now being used a crutch to replace semantical approaches to coding.

replies(1): >>46207508 #
2. tracker1 ◴[] No.46207508[source]
Can't +1 this enough... I've found that in practice, outside of images, menu pop/flyout and dialogs/trays, there really isn't too much need for additional aria attributes. Most component libraries should already be configured out of the box imo.

ARIA should only be needed relatively sparingly assuming you're using appropriate semantic elements. Testing with keyboard only navigation can reveal a lot as well.

Related, and one I experience a lot are issues on mobile devices with text/display cranked up... too many modal interactions with buttons off-screen.