-
Notifications
You must be signed in to change notification settings - Fork 17.2k
fix(a11y): WCAG 2.4.7 — ensure visible keyboard focus on all interactive elements #39242
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
base: master
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -62,8 +62,8 @@ const ControlContainer = styled.div<{ | |||||
|
|
||||||
| &:focus > div { | ||||||
|
||||||
| &:focus > div { | |
| &:focus-visible > div { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The global
*:focus-visiblerule uses!importantforoutline/outline-offset, but several components updated in this PR rely on settingoutline: 2px solid transparenton:focus-visibleto avoid a double focus ring while usingbox-shadowas the visible indicator. With!importanthere, those component-level outline declarations cannot override the global outline, so users will likely see both the global outline and the component box-shadow. Consider removing!important(or, if you truly need it, ensure component overrides also use!importantwhere they intentionally make the outline transparent).