Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

False postive Buttons must have discernible text

See original GitHub issue

Expectation: I expect both of this items to be considered as identical

<button id="btn1" title="Delete">
	<span class="fa fa-trash"></span>
</button>

<button id="btn2" title="Delete"><span class="fa fa-trash"></span></button>

Actual: btn1 will cause a violation Buttons must have discernible text btn2 will pass without violations

Motivation: Not sure if this is a bug or expected behavior from the spec. Checking the rule code it seem that halting on the first whitespace only value and ignoring the rest is intentional https://github.com/dequelabs/axe-core/blob/a84431ab3c37eccf43c3065506af3ad8097e981d/lib/commons/text/accessible-text-virtual.js#L53


axe-core version: 3.2.2
axe-webdriver.js version: 2.2.0

Issue Analytics

State:
Created 4 years ago
Comments:6 (5 by maintainers)

Top GitHub Comments

1reaction

strakercommented, Jul 9, 2019

Just so you’re aware, we released axe v3.3.0 yesterday and will soon be updating the integrations. I’ll let you know when webdriver is updated with the latest version.

1reaction

strakercommented, Jun 25, 2019

Yep. We have a release coming up for axe v3.3.0. Once that’s released, we’ll go around to the different integrations and update the version. Hopefully that should happen within a week or two after the release.

Top Results From Across the Web

Buttons must have discernible text | Axe Rules | Deque Systems

Rule Description Buttons must have discernible text that clearly describes the destination, purpose, function, or action for screen reader users.

508/Accessibility Rules for (1) Links Must Have Discernible ...

If your icons, graphics, buttons, or links execute some action you need to provide some text alternative to screen readers that describes ...

Accessibility rule: Buttons must have discernible text

For screen reader users, buttons must include recognizable text that specifies the destination, purpose, function, or action.

Buttons must have discernible text · Issue #613 - GitHub

Say something like, item-name--attribute='aria-label="thing" , this would output the item name as a aria-label and then in the child element, it ...

Buttons must have discernible text

Buttons must have discernible text that clearly describes the destination, purpose, function, or action for screen reader users. The input-button-name rule ...