Kilotest: Diagnoses of button name not visible violation by HTML element 686 on Pacific Northwest Software Quality Conference page

Basics

About the page

• URL: https://pnsqc.org/
• Tested 14 days ago on 2026-09-25 at 22:47 by job 260925T2245-p1r
• Summary of results:
  • Rule engines:
    • Called: 12
    • Were able to test: 12
    • Reported any rule violations: 10
  • Violations: 957
  • Violators: 444
  • Issues: 30
• 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: 12
• Violators: 7

About the violator

• Tag name: DIV
• Text: RECENT PNSQC EVENTS … Through a live demo and discussion, you'll see how PLUS QA tackled this challenge by embed...
• Start tag: <div class="mt-4 flex items-center justify-center gap-2" role="group" aria-label="Recent events pagination" data-carousel-dots="">
• XPath: /html/body/main[1]/section[4]/div[1]/div[1]/div[2]/div[3]
• Bounding box: x = 992, y = 2794, width = 704, height = 10
• Reported by ASLint

Diagnoses

Here is how rule engines diagnose the button name not visible issue for HTML element 686 of the Pacific Northwest Software Quality Conference page.

1. The button should have a description, but the content is empty. Having only defined an attribute aria-label="Go to event 1" 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="Go to event 2" 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

3. The button should have a description, but the content is empty. Having only defined an attribute aria-label="Go to event 3" 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

4. The button should have a description, but the content is empty. Having only defined an attribute aria-label="Go to event 4" 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

5. The button should have a description, but the content is empty. Having only defined an attribute aria-label="Go to event 5" 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