-
Notifications
You must be signed in to change notification settings - Fork 791
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
Enable best practices #612
Conversation
BREAKING CHANGE
BREAKING CHANGE: Skip-link rule no longer requires skip lins with a focusable target.
@WilcoFiers what was the rationale behind not requiring a focusable target? |
@dylanb Chrome used to have the issue that if you had a skiplink to a non-focusable element, it would just blur in place, and the next item in the focus order would just be whatever comes after the skiplink. Other browsers blurred on the target of the skiplink, so that the next focusable element would be the thing after the target of the skiplink. After some testing it looks like this issue has been resolved, so skiplinks now work everywhere, regardless of if the target is focusable or not. |
Excellent! Thank you all! |
Merge pull request #612 from dequelabs/bp-enabled BREAKING CHANGE: Skip-link rule no longer requires skip links with a focusable target. Enable best practices
I merged this into Oh crud, and I just saw the comment. I'll remove it in another commit. |
Closes #515. This should not be put in develop-2x
BREAKING CHANGE: Skip-link rule no longer requires skip links with a focusable target.