Skip to content

Keyboard navigation, focusing, and disclosure elements#306

Closed
ahamelers wants to merge 1 commit into
Authress-Engineering:release/2.4from
ahamelers:accessibility/keyboard-nav
Closed

Keyboard navigation, focusing, and disclosure elements#306
ahamelers wants to merge 1 commit into
Authress-Engineering:release/2.4from
ahamelers:accessibility/keyboard-nav

Conversation

@ahamelers

@ahamelers ahamelers commented Jul 14, 2026

Copy link
Copy Markdown
Contributor

See #305

According to accessibility auditors:

  • All clickable elements must also be navigable by keyboard.
  • When clicking an element changes the main page content, focus should move to that content.
  • Focus should never be lost.
  • Elements that are hidden visibly and contain focusable elements should also be hidden to screen readers, so the focus does not disappear inside them.
  • When clicking something hides or shows sections of content, aria-expanded should accurately reflect this.

I've handled some major elements (adding a treegrid and many tablists) in a couple separate pull requests. This one covers general keyboard navigation and accurate use of aria-controls and aria-expanded.

@wparad

wparad commented Jul 14, 2026

Copy link
Copy Markdown
Member

There are too many changes to review here. Please split the changes into individual PRS and one PR should be submitted at a time. Multiple PRs will be rejected. In each PR include what exactly the problem is, why the current implementation is insufficient and what must change t support it your needs.

I'm closing this PR as per the above and posting this same message on all other PRs.

Please focus on one PR until that PR is approved and merge. We cannot support reviewing multiple PRs at the same time.

@wparad wparad closed this Jul 14, 2026
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

Successfully merging this pull request may close these issues.

2 participants