Kilotest: Diagnoses of button name not visible violation by HTML element 57 on Project InnerSpace page

Basics

About the page

• URL: https://projectinnerspace.org/
• Tested 3 days ago on 2026-10-07 at 22:13 by job 261007T2147-p1y
• Summary of results:
  • Rule engines:
    • Called: 12
    • Were able to test: 12
    • Reported any rule violations: 12
  • Violations: 260
  • Violators: 131
  • Issues: 36
• Download the full technical report (JSON)

About the issue

• Why it matters: User cannot get help explaining a button
• Priority: lowest
• Related WCAG standard: 4.1.2
• Reported by 1 rule engine (ASLint)
• Violations: 3
• Violators: 2

About the violator

• Tag name: DIV
• Text: About … DONATE
• Start tag: <div class="container-module--container--4123e header-module--container--f262c">
• XPath: /html/body/div[1]/div[1]/header[1]/div[1]
• Bounding box: x = 204, y = 0, width = 1512, height = 179
• Reported by ASLint

Diagnoses

Here is how rule engines diagnose the button name not visible issue for HTML element 57 of the Project InnerSpace page.

1. The button should have a description, but the content is empty. Having only defined an attribute aria-label="Open navigation" is not sufficient and it is recommended to have the content instead, e.g. at least visually hidden, but exposed to assisitve technologies. Some users are disabling styles for better readability, and also description from attribute is not available for automatic translators.

   Rule engine: ASLint (eSSENTIAL Accessibility)

   Rule: empty_button_description

2. The button should have a description, but the content is empty. Having only defined an attribute aria-label="Close Navigation" is not sufficient and it is recommended to have the content instead, e.g. at least visually hidden, but exposed to assisitve technologies. Some users are disabling styles for better readability, and also description from attribute is not available for automatic translators.

   Rule engine: ASLint (eSSENTIAL Accessibility)

   Rule: empty_button_description