·

Understanding WCAG SC 2.1.2 No Keyboard Trap

Avatar for Raghavendra Satish PeriAuthored By :Raghavendra Satish Peri Last Updated : Operable, WCAG
2.1.2 No Keyboard Trap
2.1.2 No Keyboard Trap

2.1.2 No Keyboard Trap: If keyboard focus can be moved to a component of the page using a keyboard interface, then focus can be moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or tab keys or other standard exit methods, the user is advised of the method for moving focus away. (Level A)

Note: Since any content that does not meet this success criterion can interfere with a user’s ability to use the whole page, all content on the Web page (whether it is used to meet other success criteria or not) must meet this success criterion.

WCAG SC 2.1.2 No Keyboard Trap

This success criterion requires that websites must not trap keyboard users in a particular portion of the page or on a form control. Keyboard users navigate the page using tab key. If the keyboard user is trapped in a particular location & is unable to move forward or backward using the navigational keys such as tab or shift+tab & user is forced to use a mouse to move keyboard focus then it fails this check point.

Points To Ponder

  • Make sure that users can tab to & away from all parts of the site.
  • If a user is trapped on a portion of the web page for a purpose, a clear instruction must be provided for the user to end that keyboard trap.
  • Check if all parts of the site is operable using only keyboard, test by unplugging the mouse.
  • Stick to standard navigation as much as possible like tab, shift+tab & arrow keys.
  • If custom keystrokes are provided to operate a control make sure hints are exposed to all users.
  • Make sure your third party widgets are accessible, most of the time they cause major keyboard operability issues.

Related Reads

Read Next: Understanding SC 2.1.4 Character Key Shortcuts
Explore our WCAG Checklist

Explore more on DigitalA11Y Insights

Share A11y Love
Avatar for Raghavendra Satish Peri

Raghavendra Satish Peri empowers enterprises with his expertise in digital accessibility and marketing. Through his impactful work, he collaborates with both small businesses and large enterprises, spearheading digital transformation initiatives. Raghavendra is the author behind the influential Accessibility Blog hosted at DigitalA11Y.com, where he delves into the intricate realm of digital accessibility and its significance.
Passionate about fostering change within the tech landscape, Raghavendra actively inspires local tech communities through engaging meetups and mentorship. He is the driving force behind HelloA11Y.com, a vibrant platform that unites accessibility professionals, developers, and enthusiasts, propelling the adoption of accessible practices.
Beyond the digital realm, Raghavendra seeks diverse experiences. You might find him exploring various cuisines at local cafes and restaurants or immersing himself in thought-provoking audio books. His insights and musings also find a home on his Personal Blog at raghava.in, where he shares his thoughts and experiences with a wider audience.

Similar Posts

WCAG Cheat Sheets & Checklists
|

WCAG Cheat Sheets & Checklists

Avatar for Raghavendra Satish PeriAuthored By :Raghavendra Satish Peri Last Updated On :
0 Comments

WCAG Cheat Sheets Web Content Accessibility Guidelines (WCAG) is developed through the W3C process in cooperation with individuals and organizations around the world, with a goal of proving a single shared standard for web content accessibility that meets the needs of individuals, organizations, and governments internationally. The WCAG documents explain how to make web content…

2.5.1 Pointer Gestures
|

Understanding WCAG SC 2.5.1 Pointer Gestures

Avatar for Sathish KumarAuthored By :Sathish Kumar Last Updated On :
0 Comments

All functionality that uses multipoint or path-based gestures for operation can be operated with a single pointer without a path-based gesture, unless a multipoint or path-based gesture is essential.This requirement applies to web content that interprets pointer actions (i.e. this does not apply to actions that are required to operate the user agent or assistive…

3.3.2 Labels & Instructions
|

Understanding SC 3.3.2 Labels or Instructions

Avatar for Raghavendra Satish PeriAuthored By :Raghavendra Satish Peri Last Updated On :
2 Comments

Success Criterion 3.3.2 Labels or Instructions (Level A): Labels or instructions are provided when content requires user input. The intention of this success criterion is to provide labels or instructions to form fields and controls which require user input. While the criterion asks for labels or instructions, it is important for the designers and content…

3.2.2 On Input
|

Understanding WCAG SC 3.2.2 On Input

Avatar for Raghavendra Satish PeriAuthored By :Raghavendra Satish Peri Last Updated On :
5 Comments

3.2.2 On Input: Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behavior before using the component. (Level A) This success criterion conveys that change of context should not occur while user is trying to input data. For example, if…

4.1.3 Status Messages
|

Understanding WCAG SC 4.1.3 Status messages

Avatar for Raghavendra Satish PeriAuthored By :Raghavendra Satish Peri Last Updated On :
0 Comments

Success Criterion 4.1.3 Status Messages (Level AA): In content implemented using markup languages, status messages can be programmatically determined through role or properties such that they can be presented to the user by assistive technologies without receiving focus. The modern web pages are so dynamic that many a times the results of user interactions are…

2.1.1 Keyboard
|

Understanding WCAG SC 2.1.1 Keyboard

Avatar for Raghavendra Satish PeriAuthored By :Raghavendra Satish Peri Last Updated On :
0 Comments

2.1.1 Keyboard: All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user’s movement and not just the endpoints. (Level A) Note 1: This exception relates to the underlying function, not the input…

Leave a Reply

Your email address will not be published. Required fields are marked *