Kilotest: Diagnoses of custom button keyboard-inoperable? violation by HTML element 322 on 350 Sacramento page

Here is how tools diagnose the custom button keyboard-inoperable? issue for HTML element 322 of the 350 Sacramento page.

Basics

• 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
• About the 350 Sacramento page
  • URL: https://350sacramento.org/
  • Tested on 2026-04-02 at 14:10
• About HTML element 322
  • Tag name: DIV
  • Text: CLIMATE JUSTICE, POWERED BY COMMUNITY … GET THE NEWSLETTER!2025 IMPACT REPORT
  • Start tag: <div class="wpb_wrapper">
  • XPath: [not obtained]
  • Bounding box: x = 363, y = 384, width = 1194, height = 242

Diagnoses

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