Kilotest: Diagnoses of custom button keyboard-inoperable? violation by HTML element 640 on YMCA of Greater San Antonio page

Basics

About the YMCA of Greater San Antonio page

• URL: https://ymcasatx.org/
• Tested 46 days ago by job klv on 2026-06-05 at 05:41

About HTML element 640

• Tag name: DIV
• Text: “All the staff at the YMCA are so friendly and helpful! I love coming to the Y.” … Next
• Start tag: <div class="paragraph paragraph--type--bp-carousel paragraph--view-mode--default paragraph--id--547247 carousel slide paragraph--width--full" id="myCarousel-547247" data-interval="6000" data-ride="carousel">
• XPath: [not obtained]
• Bounding box: x = 790, y = 4614, width = 710, height = 309

About the custom button keyboard-inoperable? issue

• Why it matters: Custom item may prevent a keyboard-only user from operating it
• Priority: lowest
• Related WCAG standard: 2.1.1

Diagnoses

Here is how rule engines diagnose the custom button keyboard-inoperable? issue for HTML element 640 of the YMCA of Greater San Antonio page.

1. You have defined attribute <code>role="button"</code> on a <code><a></code> element. Make sure the user is able to activate it using the <kbd>ENTER</kbd> and <kbd>SPACE</kbd> keys.

   Tool: ASLint (eSSENTIAL Accessibility)

   Rule: link_button_space_key

2. You have defined attribute <code>role="button"</code> on a <code><a></code> element. Make sure the user is able to activate it using the <kbd>ENTER</kbd> and <kbd>SPACE</kbd> keys.

   Tool: ASLint (eSSENTIAL Accessibility)

   Rule: link_button_space_key