Focus Order

About

Version:	WCAG 2.0 and up
Number:	2.4.3
Level:	A
Applicability:	Audio Controls Inputs Interactive Content Links Tables Video
Requirement:	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.
Guidance:	Understanding Success Criterion 2.4.3 How to meet Success Criterion 2.4.3
Techniques:	C27: Making the DOM order match the visual order G59: Placing the interactive elements in an order that follows sequences and relationships within the content H4: Creating a logical tab order through links, form controls, and objects SCR26: Inserting dynamic content into the Document Object Model immediately following its trigger element SCR27: Reordering page sections using the Document Object Model SCR37: Creating Custom Dialogs in a Device Independent Way

Purpose

The purpose of this success criterion is to ensure that as readers tab through a document the order in which they encounter content is consistent with understanding its purpose and meaning (i.e., to prevent confusion).

How to Meet

For native HTML controls that users can tab to, authors only need to ensure that the order of elements makes logical sense. For example, if practice questions are laid out in columns, tabbing should not jump the user back and forth between the columns (i.e., the questions should be reached in sequential order).

For custom controls and widgets, the author also needs to ensure that all the controls are in the tab order and in sequence. Misuse of the HTML tabindex attribute, for example, could cause readers to jump to unexpected destinations.

Additional Information

The following knowledge base pages provide more information about how to address this success criterion for publishing content:

Tab Order