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

Basics

About the Pacific Northwest Software Quality Conference page

• URL: https://pnsqc.org/
• Tested 28 days ago by job owx on 2026-05-04 at 16:59

About HTML element 676

• Tag name: DIV
• Text: RECENT PNSQC EVENTS … "Testing the Future: From Testing Code to Testing Intelligence" with Premi Vinayagam fro...
• 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 = 2873, width = 704, height = 10

About the button name not visible issue

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

Diagnoses

Here is how tools diagnose the button name not visible issue for HTML element 676 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.

   Tool: 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.

   Tool: 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.

   Tool: 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.

   Tool: 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.

   Tool: ASLint (eSSENTIAL Accessibility)

   Rule: empty_button_description