Kilotest: Diagnoses of button not named violation by HTML element 82 on New_Public page

Basics

About the New_Public page

• URL: https://newpublic.org/
• Tested 20 days ago by job 40e on 2026-05-13 at 05:28

About HTML element 82

• Tag name: BUTTON
• Text: JOIN THE COMMUNITY
• Start tag: <button class="Header__burger">
• XPath: /html/body/div[1]/header[1]/button[1]
• Bounding box: x = 1800, y = 32, width = 80, height = 80

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 tools diagnose the button not named issue for HTML element 82 of the New_Public 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