Kilotest: Diagnoses of custom button keyboard-inoperable?
violation by HTML element 95 on Sightline Institute page
Basics
About the Sightline Institute page
- URL: https://www.sightline.org/
- Tested 29 days ago by job
wxvon 2026-05-03 at 17:04
About HTML element 95
- Tag name:
BODY - Text: [not applicable]
- Start tag:
<body class="home wp-singular page-template-default page page-id-95513 wp-custom-logo wp-embed-responsive wp-theme-generatepress wp-child-theme-gp-sightline post-image-aligned-center sticky-menu-fade sticky-enabled both-sticky-menu no-sidebar nav-float-right separate-containers header-aligned-left dropdown-hover full-width-content" itemtype="https://schema.org/WebPage" itemscope=""> - XPath:
/html/body - Bounding box: x = 0, y = 0, width = 1920, height = 3596
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 tools diagnose the custom button keyboard-inoperable?
issue for HTML element 95 of the Sightline Institute page.
- 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