Skip to main content
Tick PowerMapper
 Try it now

Keyboard handler without tabindex Accessibility Checkpoint

Description

key handlers on static elements like div and span cannot be triggered unless tabindex is set.

Help

Keyboard handlers cannot be activated from the keyboard unless the user can tab to the element. By default only links and form controls can be tabbed to. Set tabindex=0 on the static element to allow the user to tab to it.

Applicable standards

  • WCAG 2.0 (Success Criteria: 2.1.1 level A, 2.1.3 level A)
  • WCAG 2.1 (Success Criteria: 2.1.1 level A, 2.1.3 level A)
  • WCAG 2.2 (Success Criteria: 2.1.1 level A, 2.1.3 level A)
  • Section 508 (2017) (Success Criteria: 2.1.1 level A, 2.1.3 level A)
  • EN 301 549 (Success Criteria: 2.1.1 level A, 2.1.3 level A)

Note: Section 508 Refresh (2017) checkpoints are equivalent to WCAG 2.0 level A and level AA checkpoints. EN 301 549 checkpoints are equivalent to WCAG 2.1 level A and level AA checkpoints.

Impact on users

  • JAWS Users cannot tab to the control to activate the onkey handler.
  • NVDA Users cannot tab to the control to activate the onkey handler.
  • VoiceOver Users cannot tab to the control to activate the onkey handler.
  • Keyboard Users cannot tab to the control to activate the onkey handler.

Change history

  • 6.47 Dec 2022 Improved event handler detection.
  • 5.35 Oct 2019 Fixed false negative.
  • 5.5 May 2014 Added.

This page describes a web site issue detected in HTML documents by SortSite Desktop and OnDemand Suite.

Rule ID: AccWcag2-2.1.1-1