Myths

An aria-label on a div: why JAWS and NVDA ignore it, and what to use instead

8 min read
Mikhail ShaymardanovWeb Quality and Accessibility Expert

VoiceOver on a Mac reads an aria-label on a div. When the div holds text, the screen readers JAWS and NVDA read only that text. Nearly nine in ten respondents to WebAIM's 2026 survey mainly use one of those two on desktop. Without a role, ARIA doesn't allow a div or span to have a name. The name belongs in text, or on an element that accepts one.

Thirteen attributes on a record store's page


#Why an aria-label on a div doesn't work in every screen reader?

Only a few screen readers announce an aria-label on a div or span with no role attribute, and JAWS isn't one of them. The attribute sets an element's accessible name, the name a screen reader announces. A div with no role attribute, though, is a plain container with the generic role, and the ARIA specification doesn't allow a name on that role.

The silence hits the most widely used screen readers in WebAIM's 2026 survey. JAWS is the main desktop screen reader of 55.0% of respondents. NVDA, which also stays silent when the div holds text, comes second at 32.9%, far ahead of VoiceOver. Among European respondents, the two are nearly tied, at just over four in ten each.

At Red Groove, a demo record store, the “Arrivals” page carries 13 aria-label attributes. The block of new records has one, and each card has two, on its colored stock dot and on its format, shortened to 12" or 7". A JAWS user hears no name for the block, never comes across a dot, and hears each format only in its short form.

Screenshot: a record store's “This week's arrivals” page, six vinyl covers with red and black patterns, each with its artist, title, format, price and a green or orange dot.Marker 1. The “This week's arrivals” block, a div with an aria-label. Marker 2. The green dot on the first card, with no word beside it. Marker 3. The abbreviated format on the first card, 12 with an inch mark.
On the Arrivals page, the blockmarker 1, each dotmarker 2 and each formatmarker 3 carry an aria-label with no role attribute; on screen, the dot shows nothing but its color.

#What each screen reader reads, with or without text in the div?

In May 2026, accessibility specialist Manuel Matuzović tested eight pairings of screen reader and browser. Only three announce the name of an element that holds text.

With text in the div, three pairings out of eight announce the aria-label; on an empty element like the dot, NVDA reads it and JAWS skips it.
Screen reader and browserA div that holds textAn empty div
JAWS and ChromeText onlyNothing
NVDA and Chrome or FirefoxText onlyName
VoiceOver and Safari on a MacName and group roleName and empty group role
VoiceOver and Safari on an iPhoneText onlyNothing
TalkBack and ChromeName in place of the textName
TalkBack and FirefoxText onlyNothing
Narrator and ChromeName, group role and textNothing

#Why NVDA and JAWS don't read the aria-label on a div?

The browser does compute the name and hands it to the screen reader, which decides whether to announce it. Will a future version fix this? In 2018, NVDA added code to read these names, then pulled it two days later, saying too many sites misuse aria-label.

At Freedom Scientific, the company behind JAWS, the request to read empty elements named with aria-label carries the label “Not a JAWS bug”. Both vendors chose this silence, and the specification backs them, so the fix has to happen in the page's code.


#What to write in place of an aria-label on a div?

The fix depends on what the div was supposed to say.

For a page section, the name comes from the visible heading; everywhere else, text takes the attribute's place, on screen or visually hidden.
What the div was supposed to sayWhat to write in its place
Name a section of the pageA section with aria-labelledby pointing to its heading
Stand in for a visual with no textA visible word, or failing that a title attribute, not recommended
Spell out shortened textThe full text, hidden on screen

#How to name a section of the page?

A section with a name becomes a region, or landmark: a part of the page that screen readers let people jump to by keyboard. Without a name, it stays a generic container, like a div. On Red Groove's demo page, the block's div becomes a section tied to its heading with aria-labelledby.

With the div, JAWS and NVDA read the heading and the cards without announcing any region, and the axe testing engine put the block on its “needs review” list. With the section, we checked that Chrome turns the block into a region named “This week's arrivals” and that axe no longer flags its attribute.

Screenshot: the header of a record store's block, a large red 06 next to the heading “This week's arrivals” and the line “Arrived Thursday, November 5: six records, new and used.”, above three record covers.Marker 1. The visible heading “This week's arrivals”, which the div's aria-label repeats.
The heading “This week's arrivals”marker 1 is already on screen: the section takes it as its name through aria-labelledby, and nothing changes visually.

Avoid

<div class="arrivals" aria-label="This week's arrivals">
  <h2>This week's arrivals</h2>
  <p>Arrived Thursday, November 5: six records, new and used.</p>
  <ul class="grid">…</ul>
</div>

Correct

<section class="arrivals" aria-labelledby="arrivals-title">
  <h2 id="arrivals-title">This week's arrivals</h2>
  <p>Arrived Thursday, November 5: six records, new and used.</p>
  <ul class="grid">…</ul>
</section>

The name now comes from the visible heading, so it changes when someone renames the block.

#How to make a colored dot readable?

On each card, an empty dot shows availability: green with aria-label="In stock", orange with “Special order”. JAWS announces nothing, NVDA reads the name, and axe counts each dot as a violation.

Here, the look has to change, because availability is shown by color alone. WCAG success criterion 1.4.1 rules that out. So does the RGAA, the French public accessibility standard, in its criterion 3.1. In Europe, EN 301 549, the standard drafted as one voluntary way to meet the European Accessibility Act, repeats the WCAG criterion for web pages. The rule mainly protects people who see the page but have trouble telling green from orange and may use no assistive technology at all, so fixing the dot's name isn't enough.

#A visible word or a title attribute: which fix to choose

The word next to the dot, the fix we recommend. The dot becomes decoration. Pros: everyone sees the word, with a mouse, a keyboard or a finger, and screen readers read it without relying on any attribute. Cons: it takes up room. On Red Groove's cards it fits: “In stock” on four, “Special order” on two.

Avoid

Screenshot: a record card with a red and black cover, the artist Boreal Orchestra, the title Harbor Nights, the 12-inch format, a price of €26 and a green dot alone at the end of the line.Marker 1. The green dot, alone with no word beside it.
<span class="dot in-stock" aria-label="In stock"></span>

Correct

Screenshot: the same card, with the green dot followed by the words “In stock”.Marker 1. The green dot followed by the words “In stock”.
<span class="availability">
  <span class="dot in-stock"></span>In stock
</span>

Screen reader: « In stock »

With no word beside it, JAWS skips the dotmarker 1 and NVDA reads it as “In stock”; written next to it, “In stock”marker 1 is both seen and heard.

A title attribute on the dot: it passes the RGAA test, but we strongly advise against it. It shows an “In stock” tooltip on mouse hover, and the RGAA test method lists the presence of a title attribute among the other ways to get the information. Pros: until someone hovers it, the card keeps its look. Cons: keyboard and touch-screen users never see the tooltip, which is exactly why the HTML standard discourages relying on it. Screen readers don't support title uniformly either, notes Steve Faulkner, a former editor of the W3C's HTML specification. The RGAA allows it; we don't recommend it.

With this fix, add role="img" and aria-label="In stock": the dot becomes an information-carrying image, which Chrome reports as an image named “In stock” and axe stops flagging. Here the aria-label is read: with role="img", the dot is no longer a generic span but an image, which the ARIA specification lets you name. The title serves the mouse, the aria-label the screen reader.

<span class="dot in-stock" role="img" aria-label="In stock" title="In stock"></span>

#How to spell out an abbreviation like 12"?

The 12" format tag carries aria-label="12-inch" so screen readers say the full word. JAWS and NVDA read only the visible 12" anyway, and axe puts the tag on its “needs review” list.

Here, the screen doesn't change: 12" stays on the card, hidden from screen readers by aria-hidden="true". The full word goes into visually hidden text, a span with the sr-only class that only screen readers read.

Avoid

Screenshot: the text of a record card, Boreal Orchestra, Harbor Nights, then the format 12 with an inch mark in white on black, a price of €26 and the green dot followed by “In stock”.Marker 1. The abbreviated format, 12 with an inch mark.
<span class="format" aria-label="12-inch">12"</span>

Screen reader: « 12" »

Correct

Screenshot: the same card text, unchanged: the format still shows 12 with an inch mark.Marker 1. The format, 12 with an inch mark, unchanged on screen.
<span class="format">
  <span aria-hidden="true">12"</span><span class="sr-only">12-inch</span>
</span>

Screen reader: « 12-inch »

Despite its aria-label, JAWS and NVDA read only the short formatmarker 1; with the hidden text, the tag still shows the short formatmarker 1 and is read as “12-inch”.

The two screenshots are identical, and that's the point: nothing changes on screen.

The aria-label attribute: when to use it and how to word it

#How to find aria-label attributes that aren't allowed and check the fix?

The W3C HTML validator flags every one of these attributes as an error, with or without text. The axe testing engine counts only some as violations, and Chrome's Accessibility tab and a screen reader test both let some slip through.

#How to find these attributes on a page or in your code?

In axe, the rule aria-prohibited-attr reports them as violations on an empty element, and as “needs review” (incomplete) on an element that holds text.

When we ran Red Groove's demo page through axe, we got six violations, one per dot, and seven results to review: the block and the six formats. Some developers paste the first message below into Google word for word:

  • a violation, for a dot: aria-label attribute cannot be used on a span with no valid role attribute.
  • needs review, for the block: aria-label attribute is not well supported on a div with no valid role attribute.

Since axe 4.14, these messages say on "span" elements or on "div" elements.

A div full of text, the common case, never shows up among axe's violations, so always open the “needs review” list. In the code, this grep command finds these attributes, aria-labelledby included:

grep -rnoE '<(div|span)[^>]*aria-label' src/

On our demo files, it finds 13 attributes before the fix and none after. It also lists tags that already have a role, to sort by hand. It misses any attribute written on its own line, as is common in React's JSX.

#Why a single check isn't enough?

In Chrome's developer tools, the Accessibility tab of the Elements panel shows the block's Name line, “This week's arrivals”, and its role, generic. The browser did compute the name. For a generic div, though, neither that line nor listening with VoiceOver on a Mac shows whether JAWS and NVDA will announce it. To find out from a Mac, you can run NVDA in a Windows virtual machine.

Screenshot: Chrome DevTools, Elements panel, with the div of class arrivals selected and, in the Accessibility tab, its ARIA attributes and computed properties.Marker 1. The Name line, showing “This week's arrivals”. Marker 2. The Role line, showing generic.
For the block's div, Chrome shows the name “This week's arrivals”marker 1 and the role genericmarker 2: the name exists, and JAWS and NVDA still don't announce it.

Even a test with NVDA, the free screen reader we recommend for this check, gets fooled by the dot. Going by Manuel Matuzović's test, NVDA skips the block's name and the full format, yet reads “In stock” on the empty dot, where JAWS, the most widely used, says nothing.

The axe engine does the reverse: it flags the dots as violations and leaves the block and the formats under “needs review”. Each check lets through what the other one catches.

On the fixed page, neither axe's aria-prohibited-attr rule nor the grep search finds anything. The 13 aria-label attributes are replaced by a single aria-labelledby, on the section, an element allowed to have a name. “In stock”, which JAWS skipped, is now written on the card, and “12-inch”, which both readers ignored, comes through hidden text.

NVDA screen reader: how to install it, set it up and test a web page

On a live site, the Includdy scan lists a page's accessibility issues, including empty elements named with an aria-label, like Red Groove's dots. For each one, the guided fix suggests a corrected component, which you review before merging it.


Share this article

Frequently asked questions

Yes. The ARIA specification prohibits aria-labelledby on a div or span with no role, just as it prohibits aria-label. When the div contains the heading the attribute points to, the axe testing engine puts it on its “needs review” list.

On a section, the same attribute does the opposite: it gives the section a name, which turns it into a region, a landmark of the page.

It makes the attribute valid, with no guarantee that anyone hears it. Unless it is the direct child of a dl list, a div accepts any role, and group is not one of the roles that prohibit a name. MDN notes, though, that in practice aria-label is only supported on interactive elements, widgets, landmarks, images and iframes.

A group is none of those. To name a part of the page, a section tied to its heading is the safer choice; for a piece of information, visible text is.

The ones whose role prohibits a name: a div or span with no role, the paragraph element p, and text-level elements such as code, strong or em. Version 1.2 of the ARIA specification lists eleven roles of this kind, among them generic, paragraph, and the code, strong and emphasis roles of those text-level elements. Its companion specification for HTML marks the matching elements “Naming Prohibited”.

An li can take a name, but the W3C's naming guide advises against it, because assistive technologies don't support that name.