Kilotest: Diagnoses of button not named violation by HTML element 112 on Third Act page

Basics

About the Third Act page

• URL: https://thirdact.org/
• Tested 4 days ago by job wm0 on 2026-08-27 at 21:08

About HTML element 112

• Tag name: BUTTON
• Text: [not applicable]
• Start tag: <button class="search" type="button" data-bs-toggle="modal" data-bs-target="#searchModal">
• XPath: /html/body/div[2]/header[1]/div[1]/div[1]/div[1]/div[1]/div[2]/div[1]/button[1]
• Bounding box: x = 1521, y = 13, width = 57, height = 53

About the button not named issue

• Why it matters: User cannot get help explaining a button
• Priority: highest
• Related WCAG standard: 4.1.2

Diagnoses

Here is how rule engines diagnose the button not named issue for HTML element 112 of the Third Act page.

1. 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

2. 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

3. [failed] The test target doesn't have an accessible name, or it's empty ('').

   Tool: QualWeb (University of Lisbon)

   Rule: QW-ACT-R11

4. Empty button

   Tool: WAVE (Utah State University)

   Rule: button_empty