Kilotest: Diagnoses of button not named violation by HTML element 1483 on Turrito page

Basics

About the Turrito page

• URL: https://www.turrito.com/
• Tested 44 days ago by job i2n on 2026-06-07 at 00:32

About HTML element 1483

• Tag name: DIV
• Text: [not applicable]
• Start tag: <div class="leaflet-marker-icon leaflet-div-icon leaflet-zoom-animated leaflet-interactive" tabindex="0" role="button" style="margin-left: -6px; margin-top: -6px; width: 12px; height: 12px; transform: translate3d(583px, 300px, 0px); z-index: 300;">
• XPath: [not obtained]
• Bounding box: x = 955, y = 10433, width = 12, height = 12

About the button not named issue

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

Diagnoses

Here is how rule engines diagnose the button not named issue for HTML element 1483 of the Turrito page.

1. ARIA commands must have an accessible name; Element does not have text that is visible to screen readers; aria-label attribute does not exist or is empty; aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty; Element has no title attribute

   Tool: Axe (Deque)

   Rule: aria-command-name

2. This element has role of "button" but does not have a name available to an accessibility API. Valid names are: element content, aria-label attribute, aria-labelledby attribute.

   Tool: HTML CodeSniffer (Squiz Labs)

   Rule: E-WCAG2AAA.Principle4.Guideline4_1.4_1_2.H91.Div.Name

3. [failed] The test target doesn't have an accessible name, or it's empty ('').

   Tool: QualWeb (University of Lisbon)

   Rule: QW-ACT-R11