Blog ·

axe-core 4.14 turned on a rule by default. Your count went up.

axe-core 4.14.0 enables label-content-name-mismatch by default, so your issue count may go up. Here's what the rule checks (WCAG 2.5.3 Label in Name) and how to fix a "Book now" button that fails it.

If your accessibility check reported more issues this month with no code changes, check your lockfile. axe-core 4.14.0 (released October 5, 2026) turns on label-content-name-mismatch by default. Before this release you had to enable it yourself.

The release notes warn about this directly: new rules "can cause the issue totals to go up from a previous version." Some false-positive fixes may pull the count down, so the net change varies by site.

The upgrade has good news too: Deque says runs should be 20% to 40% faster on most pages, and up to 15x faster on very large ones.

What the rule checks

label-content-name-mismatch maps to WCAG 2.5.3 Label in Name (Level A). If a control has visible text, its accessible name must contain that text.

This matters most for voice control users. Someone using Voice Control or Dragon looks at a button that says "Book now" and says "Click Book now." If the button's accessible name is something else, nothing happens.

The failing button

This is common on practice sites, often added by someone trying to "improve" accessibility:

<a href="/schedule" class="btn"
   aria-label="Schedule a consultation with our audiologists">
  Book now
</a>

Visible text: Book now. Accessible name: Schedule a consultation with our audiologists. The visible words aren't in the name, so a voice user saying "Click Book now" gets no response.

Representative axe output:

label-content-name-mismatch (serious)
Ensure that elements labelled through their content must have their visible text as part of their accessible name
  <a href="/schedule" class="btn" aria-label="Schedule a consultation with our audiologists">

Three fixes, best first

1. Remove the aria-label. The visible text already works as the name.

<a href="/schedule" class="btn">Book now</a>

2. If you need more context, start the name with the visible text.

<a href="/schedule" class="btn"
   aria-label="Book now: hearing consultation">
  Book now
</a>

The name starts with "Book now," so voice commands work, and screen reader users get the extra detail. WCAG doesn't require the visible text to come first, but putting it first is best practice.

3. Put the context in visually hidden text instead of an aria-label.

<a href="/schedule" class="btn">
  Book now<span class="sr-only"> a hearing consultation</span>
</a>

The name is now "Book now a hearing consultation." Translation tools and anything else that reads page content pick up the extra text too.

Finding these across a site

npx @axe-core/cli https://example.com --rules label-content-name-mismatch

Or in code, if you're pinned to an older version and want to preview the change:

const results = await axe.run(document, {
  rules: { 'label-content-name-mismatch': { enabled: true } },
});

Common places to look:

  • "Book now," "Learn more" and "Read more" links with long aria-labels
  • Icon buttons with visible tooltip text that doesn't match the label
  • Logo links where the visible wordmark doesn't match the label (for example, "Home" on a logo that reads "Ann Arbor Hearing")
  • CMS components that add aria-label automatically from a separate field

If you report numbers to clients

Write the axe-core version in every report. If last quarter's report said 12 issues and this one says 19, the client should hear "the tool got stricter" from you before they reach "the site got worse" on their own. Re-run the old baseline on 4.14 so you're comparing like with like.