Skip to content

Conversation

Rich-Harris
Copy link
Member

fixes #320 — if you click into an editor, or type while it's focused, the tab key will then indent stuff. But if you tab into it and press again, the tab key will not indent stuff — instead, focus travels to the next focusable element.

This means we meet the no-keyboard-trap requirement of WCAG 2.1 https://www.w3.org/TR/WCAG21/#no-keyboard-trap

@Rich-Harris Rich-Harris merged commit 8a2f348 into main Oct 30, 2024
5 checks passed
@Rich-Harris Rich-Harris deleted the gh-320 branch October 30, 2024 16:35
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.

Editors should not intercept tab presses if they were focused because of a tab press
3 participants