In accessibility, which practice supports keyboard navigation?

In accessibility, which practice supports keyboard navigation?

• A. Relying solely on mouse interactions.
• B. Ensuring all interactive elements are reachable via keyboard and logically ordered.
• C. Hiding all focus indicators.
• D. Only providing accessibility for screen readers.

Answer: (B)

Supporting keyboard navigation means ensuring all interactive elements can be reached and activated using the keyboard, and that the focus moves in a logical order that matches the page or component layout. This lets users who can’t or don’t want to use a mouse move through controls, understand which element is focused, and activate it with Enter or Space. A predictable focus sequence also helps screen reader users because the order of focus aligns with the reading order, making navigation coherent. If an element isn’t reachable by keyboard or the focus order is jumbled, keyboard users can miss controls or get lost. Conversely, relying solely on a mouse, hiding focus indicators, or limiting accessibility to screen readers fails to support keyboard operability and visible focus cues.

Supporting keyboard navigation means ensuring all interactive elements can be reached and activated using the keyboard, and that the focus moves in a logical order that matches the page or component layout. This lets users who can’t or don’t want to use a mouse move through controls, understand which element is focused, and activate it with Enter or Space. A predictable focus sequence also helps screen reader users because the order of focus aligns with the reading order, making navigation coherent. If an element isn’t reachable by keyboard or the focus order is jumbled, keyboard users can miss controls or get lost. Conversely, relying solely on a mouse, hiding focus indicators, or limiting accessibility to screen readers fails to support keyboard operability and visible focus cues.