Skip to content
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.

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

Ambiguity on keyboard support for Page Up, Page Down keys #2861

Open
rahimabdi opened this issue Nov 14, 2023 · 1 comment
Open

Ambiguity on keyboard support for Page Up, Page Down keys #2861

rahimabdi opened this issue Nov 14, 2023 · 1 comment
Assignees

Comments

@rahimabdi
Copy link

Hello 👋🏾

Upon investigating the menu button keyboard requirement (or optionality) to support Page Up and Page Down keys, it appears this is not specified in the APG's Menu and Menubar Pattern. After testing the provided menubar and menu button examples:

  • When focus is in a menubar, pressing the Page Up or Page Down key moves focus respectively to the first or last top-level menu item
  • When focus is in a submenu, pressing the Page Up or Page Down key moves focus respectively to the first or last submenu item

It appears that several patterns include Page Up/Page Down guidance such as slider, treegrid, spinbutton, etc. so my concern is the lack of consistency on how these keys should be handled in other patterns that could support them.

My questions:

  • IIRC Page Up/Down were optional for menu buttons/bars in terms of expected keyboard operability for previous APG versions; is this still true? If yes, should these keys be included in the "Keyboard Interaction" section for menu button, menubar?
  • Is there a particular reason the Tabs pattern does not support Page Up/Page Down? This question also applies to the Combobox pattern which does not present Page Up/Down guidance across all variants.
  • For the Listboxes pattern (rearrangeable options), Page Up/Page Down moves an item's position to the previous or subsequent position however, this behavior is undocumented; should it be explicitly stated under "Keyboard Support" (as optional)?
@css-meeting-bot
Copy link
Member

The ARIA Authoring Practices (APG) Task Force just discussed Inconsistencies in Page Up and Page Down guidance.

The full IRC log of that discussion <jugglinmike> Topic: Inconsistencies in Page Up and Page Down guidance
<jugglinmike> github: https://github.com//issues/2861
<jugglinmike> Matt_King: This person is pointing out that many of our examples do a lot of different things with "Page up" and "page down"
<jugglinmike> Matt_King: Those buttons behavior differently on macOS and Windows
<jugglinmike> Matt_King: There are three questions here
<jugglinmike> Matt_King: Even though this issue is generally about "page up" and "page down", I'm not sure if there's one answer here. The best way to triage may be to break it up into multiple issues
<jugglinmike> CoryJoseph: I can share some feedback on the issue (though I may need a few weeks)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants