Kilotest: Diagnoses of button name not visible violation by HTML element 880 on Virtual Science Teachers page

Basics

About the page

• URL: https://virtualscienceteachers.org/
• Tested 3 days ago on 2026-10-07 at 23:08 by job 261007T2305-1s9
• Summary of results:
  • Rule engines:
    • Called: 12
    • Were able to test: 12
    • Reported any rule violations: 12
  • Violations: 1118
  • Violators: 496
  • Issues: 47
• 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: 51
• Violators: 37

About the violator

• Tag name: DIV
• Text: "My students are very engaged while completing these activities. There's less non-academic talking and more on task communication among students." … Middle School Teacher
• Start tag: <div class="swiper-pagination swiper-pagination-clickable swiper-pagination-bullets swiper-pagination-horizontal">
• XPath: [not obtained]
• Bounding box: x = 577, y = 3292, width = 766, height = 27
• Reported by ASLint

Diagnoses

Here is how rule engines diagnose the button name not visible issue for HTML element 880 of the Virtual Science Teachers page.

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

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

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

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

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

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

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

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

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

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