Menu

1 / 2

5 ARIA mistakes that make accessibility worse, not better

DEV Community·a11ySolutions·6 months ago
#GsXUH6A8
#a11y#webdev#html#software#aria
Reading 0:00
15s threshold

There's a rule in accessibility that doesn't get enough attention:

No ARIA is better than bad ARIA.

Adding ARIA attributes without understanding them doesn't help assistive tech, it actively misleads it. Here are the mistakes I find most often in real audits:

1. role="button" on a div — without keyboard support

If you give something a button role, screen readers announce it as a button.

Users expect to activate it with Space or Enter.

If your div only handles onClick, keyboard users get announced a button they can't press. Use <button> . That's what it's there for.

2. aria-label that duplicates visible text — badly

<button aria-label="Click here to submit the form">Submit</button>

Screen readers read the aria-label, ignoring "Submit". Now your button is "Click here to submit the form", verbose, inconsistent, and confusing in a list of controls.

If the visible label is accurate, you don't need aria-label.

3.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.