WCAG

Understanding SC 2.4.3 Focus Order

Authored By :Raghavendra Satish Peri Last Updated :June 20, 2022 WCAG

If a Web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability. (Level A)

Intent of this Success Criterion

The intent of this Success Criterion is to ensure that when users navigate sequentially through content, they encounter information in an order that is consistent with the meaning of the content and can be operated from the keyboard. This helps the users to construct a mental model of the content thereby reduces confusion.

Different logical orders

Based on the arrangement of the content, there may be different logical orders that would convey the relationships. For example, when traversing within a table, the order of elements could be determined either by column to column or row to row. One of these will pass this criterion but a mixture of this would fail.

Who benefits?

People with motor disabilities who use keyboard would need a logical and usable focus order
People who have reading disorders would need a logical focus order as if the focus jumps or is lost, they would be disoriented
People who are blind and who rely on screen reader and keyboard would benefit out of a logical order as if the focus jumps unexpectedly, they would be confused
People with low vision who rely on magnifiers would benefit out of this criterion as a logical order would prevent improper association of contents during magnification

Examples

In a login page, when the focus is forcefully set on the first field, then the subsequent tabs must take the users to the next form controls and then to the next section below or beside the form depending on the logical order of the page. The focus must not jump to the header after the last element of the form.
When a modal opens:
- The focus is set on the modal (first element)
- The focus is trapped within the modal (cycles between the elements inside the modal)
- The focus is returned to the element that triggered the modal
On a page with megamenu with submenus:
- The users encounter only one tab focus for the entire menu
- The users use right/left arrow keys to navigate between main menus
- The users use down/up arrow keys to expand/ a main menu and navigate down the submenus.

Points to Ponder

Avoid using tabindex values that are >1 to manage focus order as they may supersede logical tab order
Align the focus order with the reading order as much as possible in order to maintain a logical and intuitive navigation of the content. Too much deviation would put a lot of users with disabilities into confusion

Useful A11Y Resources on Focus Order

References

Understanding Success Criterion 2.4.3

Explore our WCAG Checklist

Raghavendra Satish Peri

Raghavendra Satish Peri is a digital Transformation specialist working with small & large enterprises in the areas of digital accessibility & digital marketing. He authors an Accessibility Blog at DigitalA11Y.com & is galvanizing the adoption of accessibility by inspiring the local tech community with meetups and mentorship. He propelled this thought by founding HelloA11y.com, a community of accessibility professionals, developers, and enthusiasts. When away from his computer, Raghava can be found at local cafes & restaurants sampling cuisines, attending local meetups, listening to audio books, or writing on his Personal Blog at raghava.in.