Skip to content

Developing a Keyboard Interface Practice: Editorial revision to note about pointer considerations #3366

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 1 commit into from
Sep 30, 2025
Merged

Developing a Keyboard Interface Practice: Editorial revision to note about pointer considerations #3366

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
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 @@ -379,7 +379,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
<p>This guidance focuses specifically on keyboard interaction. However, authors also need to consider pointer interactions, such as mouse clicks
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
Expand Down
Loading