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.
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Manuel Matuzovic |
| Canonical URL | https://www.matuzo.at/blog/2026/aria-label-generic-elements |
| Publication time | Fri, 22 May 2026 15:21:49 +0000 |
| Retrieval time | 2026-05-22T15:32:02.450Z |
| Last seen | 2026-05-22T15:32:02.450Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | 7tZn13hF7Bsb |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
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
