Don't put aria-label on generic elements like divs
The article discusses the improper use of aria-label on generic HTML elements like divs and spans. It highlights that labeling these elements is against ARIA specifications and can lead to inconsistent behavior across different screen readers. The author emphasizes that while there are exceptions for certain elements, using aria-label on generic elements should generally be avoided for better accessibility.
- ▪Using aria-label on generic elements like divs and spans is not allowed according to ARIA specifications.
- ▪Different screen readers handle labeled generic elements inconsistently, leading to confusion for users.
- ▪Exceptions exist for certain elements like sections and popovers, where labeling can be beneficial.
Opening excerpt (first ~120 words) tap to expand
Don't put aria-label on generic elements like divs posted on 22.05.2026 This post is part of a series called #WebAccessibilityFails, where I collect common issues I find in accessibility audits so that you can avoid them in the future. The title already tells most of the story, but here's why you must avoid labeling generic elements like divs or spans using aria-label or aria-labelledby. <div aria-label="News"> … </div> Don't do this Looking at the ARIA spec, you'll find section "5.2.8.6 Roles which cannot be named (Name prohibited)". It lists all roles that cannot be named. It includes “generic”, which is the default role of divs and spans.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Manuel Matuzovic.
Discussion
0 commentsMore from Manuel Matuzovic
