Keyboard
2 posts
WCAG Success Criteriawcag-2.2-A
WCAG 2.1.1: Keyboard
WCAG 2.1.1 requires that all functionality available through a mouse or pointer is equally operable via a keyboard alone, with no specific timing required for keystrokes. This criterion is foundational for users who cannot use a mouse, ensuring they can navigate, interact with, and complete tasks on any website or application.
WCAG Success Criteriawcag-2.2-AAA
WCAG 2.1.3: Keyboard (No Exception)
WCAG 2.1.3 requires that every function of a web page or application be operable via a keyboard interface, with no exceptions whatsoever—not even for path-dependent or freehand drawing tasks. This AAA criterion closes the loophole present in WCAG 2.1.1 and ensures full keyboard access for users who cannot use a mouse.