Kilotest: Diagnoses of button name not visible violation by HTML element 162 on Textbox Digital page

Basics

About the Textbox Digital page

• URL: https://www.textboxdigital.com/
• Tested 36 days ago by job 7ez on 2026-04-27 at 03:45

About HTML element 162

• Tag name: LI
• Text: ASPIRE
• Start tag: <li id="comp-j6c1udky5" data-direction="ltr" data-listposition="center" data-data-id="dataItem-jz1fhvo8" data-state="menu false link" data-index="5" class="L3ZIQx wixui-dropdown-menu__item pr7XQM" data-original-gap-between-text-and-btn="10" aria-hidden="false" style="width: 149px; height: 62px; position: relative; box-sizing: border-box; overflow: visible; visibility: inherit;">
• XPath: [not obtained]
• Bounding box: x = 1179, y = 236, width = 149, height = 62

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 162 of the Textbox Digital page.

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