Kilotest: Diagnoses of button name not visible violation by HTML element 653 on International Consortium of Investigative Journalists page

Here is how tools diagnose the button name not visible issue for HTML element 653 of the International Consortium of Investigative Journalists page.

Basics

• 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
• About the International Consortium of Investigative Journalists page
  • URL: https://www.icij.org/
  • Tested on 2026-04-03 at 03:59
• About HTML element 653
  • Tag name: DIV
  • Text: Damascus Dossier … Shadow Diplomats
  • Start tag: <div class="swiper-pagination swiper-pagination-clickable swiper-pagination-bullets swiper-pagination-horizontal swiper-pagination-bullets-dynamic" style="width: 200px;">
  • XPath: /html/body/div[1]/main[1]/div[5]/div[1]/div[1]/div[1]/div[1]/div[1]/div[1]/div[1]/div[1]/div[2]
  • Bounding box: x = 860, y = 3014, width = 200, height = 32

Diagnoses

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.

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

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

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

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

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

   Tool: ASLint (eSSENTIAL Accessibility)

   Rule: empty_button_description