Skip to content

Developing a Keyboard Interface Practice: Add note about pointer activation and roving tabindex/aria-activedescendant #3311

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mcking65 merged 4 commits into from
Sep 16, 2025
Merged

Developing a Keyboard Interface Practice: Add note about pointer activation and roving tabindex/aria-activedescendant #3311

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
8b98f2c
Markup cleanup - add `<code>...</code>` where relevant
patrickhlauke Jul 9, 2025
36cba93
Add initial draft note about avoiding mismatch for mixed input use
patrickhlauke Jul 9, 2025
d27966f
Merge branch 'main' into patrickhlauke-issue1710
patrickhlauke Jul 9, 2025
fa35300
Update content/practices/keyboard-interface/keyboard-interface-practi…
ariellalgilmore Sep 2, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Update content/practices/keyboard-interface/keyboard-interface-practi… 
…ce.html

Co-authored-by: Patrick H. Lauke <[email protected]>
  • Loading branch information
@ariellalgilmore @patrickhlauke
ariellalgilmore and patrickhlauke authored Sep 2, 2025
commit fa35300ce6a70f1af9088ea76bb8347beaec1727
2 changes: 1 addition & 1 deletion content/practices/keyboard-interface/keyboard-interface-practice.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -380,7 +380,7 @@ <h3>Managing Focus in Composites Using <code>aria-activedescendant</code></h3>
<div class="note">
<h4>Note</h4>
<p>This guidance focuses specifically on keyboard interaction. However, authors must of course also consider pointer interactions, such as mouse clicks
and touchscreen taps. In the case of components that don't "close" when an element is clicked/tapped,
and touchscreen taps. When a component is clicked/tapped,
authors should take the same steps to set the correct <code>tabindex</code> or <code>aria-activedescendant</code> for the element,
in the same way that they would for keyboard navigation. Otherwise, this could lead to a confusing experience for users that switch between pointer
and keyboard navigation, as it will lead to a mismatch.</p>
Expand Down
Loading