Initial commit

2025-12-22 00:21:10 -05:00
commit 2bd947dfe5
91 changed files with 3819 additions and 0 deletions
@@ -0,0 +1,39 @@
+[Back to 2 Operable index](index.md)
+
+# 2.4.3 Focus Order
+
+- Level: A
+- Guideline: 2.4 Navigable
+- Principle: 2 Operable
+
+## What it is
+
+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.
+
+## How to test
+
+- Check: 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.
+- Use the sufficient techniques below as acceptable methods when applicable.
+- Confirm none of the common failures apply.
+
+## Sufficient techniques (W3C)
+
+- G59: Placing the interactive elements in an order that follows sequences and relationships within the content
+- C27: Making the DOM order match the visual order
+- PDF3: Ensuring correct tab and reading order in PDF documents
+- SCR26: Inserting dynamic content into the Document Object Model immediately following its trigger element
+- H102: Creating modal dialogs with the HTML dialog element
+- SCR27: Reordering page sections using the Document Object Model
+
+## Common failures (W3C)
+
+- F44: Failure of Success Criterion 2.4.3 due to using tabindex to create a tab order that does not preserve meaning and operability
+- F85: Failure of Success Criterion 2.4.3 due to using dialogs or menus that are not adjacent to their trigger control in the sequential navigation order
+
+## Resources
+
+- WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#focus-order
+- Understanding: https://www.w3.org/WAI/WCAG22/Understanding/focus-order.html
+- Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#focus-order
+
+[Back to 2 Operable index](index.md)