Kilotest: Diagnoses of button not named
violation by HTML element 599 on Institute for Progress page
Here is how tools diagnose the button not named
issue for HTML element 599 of the Institute for Progress page.
Basics
- About the
button not named
issue- Why it matters: User cannot get help explaining a button
- Priority: highest
- Related WCAG standard: 4.1.2
- About the Institute for Progress page
- URL:
https://ifp.org/ - Tested on 2026-04-03 at 04:21
- URL:
- About HTML element 599
- Tag name:
BUTTON - Text: [not applicable]
- Start tag:
<button class="simple-swiper-controller__button simple-swiper-controller__button-right"> - XPath:
/html/body/main[1]/div[4]/div[1]/div[1]/div[2]/button[2] - Bounding box: x = 1580, y = 4070, width = 40, height = 40
- Tag name:
Diagnoses
- Buttons must have discernible text; Element does not have inner text that is visible to screen readers; aria-label attribute does not exist or is empty; aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty; Element has no title attribute; Element does not have an implicit (wrapped) <label>; Element does not have an explicit <label>; Element's default semantics were not overridden with role="none" or role="presentation"
Tool: Axe (Deque)
Rule:
button-name - This button element does not have a name available to an accessibility API. Valid names are: title attribute, element content, aria-label attribute, aria-labelledby attribute.
Tool: HTML CodeSniffer (Squiz Labs)
Rule:
E-WCAG2AAA.Principle4.Guideline4_1.4_1_2.H91.Button.Name - [failed] The test target doesn't have an accessible name, or it's empty ('').
Tool: QualWeb (University of Lisbon)
Rule:
QW-ACT-R11 - Empty button
Tool: WAVE (Utah State University)
Rule:
button_empty - This button element does not have a name available to an accessibility API. Valid names are: title , element content, aria-label , aria-labelledby , aria-description , aria-describedby .
Tool: WallyAX (Wally)