2.4.3 Focus Order: 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.
SC 2.4.3 Focus Order supports the Operable principle, which provides a method for users with disabilities to navigate information on a Web page (via the keyboard) sequentially and logically. Focus order is not the same thing as visible focus.
- Visible focus on the current focusable component is usually represented by a dotted rectangle, highlight, or a vertical bar in a text field. Focus visible was covered in the previous lesson for SC 2.4.7. Once an element receives focus, the focus is expected to also be visible.
- Focus order allows keyboard users to navigate the content in a logical manner that is consistent with the sequential reading order of a Web page, document, or native application. It applies to interactive interface elements that must receive visible focus when the user “lands” on them, such as links, form elements, menus, tables, interactive images, etc. However, it can also apply to focusable, non-interactive interface elements (i.e., focusable text instructions on a screen, warning or error messages, etc.).
Impact of Nonconformance with SC 2.4.3 Focus Order
| Type of Disability | Description of Impact |
|---|---|
| 302.1 Without Vision | Users who are blind cannot use a mouse to interact with electronic content and typically use an assistive technology, such as a screen reader, to get audible or other alternative output for the information represented visually. To be able to navigate the content, understand its structure and relationships, and understand the meaning of content represented in graphics and images, the content must provide textual and programmatic cues in addition to the content presented purely visually. |
| 302.2 With Limited Vision | Users with limited vision may have widely different visual perception. Individuals with limited vision may or may not use assistive technologies. Therefore, in addition to textual and programmatic cues necessary for assistive technologies, ICT must also present content consistently and predictably. Users who view content with magnifiers may not pick up alerts, warnings, or other content if such content is presented outside of a consistent and predictable navigation pattern or if the content is not itself viewable at large magnification. Content that becomes distorted when magnified can also prevent some users with limited vision from being able to understand or interact with the content. |
| 302.7 With Limited Manipulation | Some users may not be able to perform actions that require fine motor control (clicking and dragging), path dependent gestures (pattern-based passcodes), or simultaneous actions (Ctrl + Alt + Del). Providing alternative means to perform the same actions, such as entering the size specifications in an input field to resize an object or allowing sequential key entries, can enable users with limited manipulation to interact with the same content. |
| 302.8 With Limited Reach and Strength | Some users may lack sufficient strength to perform actions such as squeezing, grasping, or depressing a hardware control. Some users, including those in wheelchairs or of shorter stature, may not be able to reach controls that are placed too high or too far away from where a user would access the device controls or interface. ICT designers and developers must consider a broad range of statures, strength and dexterity limitations, and the needs of wheelchair users in order to provide interfaces that are operable with limited reach and/or strength. |
| 302.9 With Limited Language, Cognitive, and Learning Abilities | Some users require more time than average to process information while others may find complicated instructions difficult to follow. Furthermore, some ICT content can distract or overwhelm users, preventing them from being able to interact with or understand other ICT content. Designers and developers of ICT must consider a broad range of cognitive abilities in order to provide ICT that is simple and easy to use. |
Applicability of Success Criteria 2.4.3 Focus Order
| Technology | Applicability of SC 2.4.3 Focus Order |
|---|---|
| Web | Typically, Web browsers calculate focus order based on the sequential order in which content appears in the Document Object Model. When this order differs from the order that is presented visually on the screen AND if the sequence affects meaning or operation, then developers can directly modify the focus order for elements using the “tabindex” attribute. |
| Software | Software developers typically can modify focus order via a tabindex property (depending on the technology or code language being used) if the visual order differs from the focus order AND if the sequence affects meaning or operation. |
| Office documents | Focus order for most content in Office documents typically follows the standard reading order. However, when some objects are inserted in a document, their “position” and text wrapping properties can also affect the focus order of objects. In other Office documents, such as PowerPoint, the order in which an object is created determines its focus order or position. Depending on the authoring tool or document format, content authors and developers may use various toolbars or functions to ensure that the focus order of document content matches the intended presentation order. |
| PDF documents | Focus order in a PDF document is determined by the PDF tag structure. Depending on the PDF authoring tool, it is usually possible to modify the reading order or “Z” order of content to ensure that the focus order matches the intended presentation order. |
| Mobile Native | Mobile-native software developers typically can modify focus order via a tabindex property (depending on the technology or code language being used) if the visual order differs from the focus order AND if the sequence affects meaning or operation. |