-
Notifications
You must be signed in to change notification settings - Fork 808
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
Instant Search: improve accessibility of close button #17294
Conversation
Caution: This PR has changes that must be merged to WordPress.com |
Scheduled Jetpack release: November 3, 2020. E2E results is available here (for debugging purposes): https://jetpack-e2e-dashboard.herokuapp.com/pr-17294 Thank you for the great PR description! When this PR is ready for review, please apply the |
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.
Looks good overall. I left a question and a suggestion inline.
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.
aria-hidden
changes look good, but I discovered another strange behavior: hoving over the close button nudges it down and to the right:
It looks like we have a lot of styles being applied to .jetpack-instant-search__overlay-close
from both modules/search/instant-search/components/search-results.scss
and modules/search/instant-search/components/overlay.scss
. Perhaps consolidating these styles will help us avoid these styling bugs?
How curious. What theme and what browser is it @jsnmoon? I'm not seeing it in TwentyTwenty on Safari, FF or Chrome. Good call on consolidating the styles. Possibly a case for splitting close button into its own component? |
Strange, I'm no longer able to reproduce. I was using TwentyTwenty with Chrome 85 when I took the screencap.
I think consolidating the styles into |
Due to the changes we've introduced to the Gridicon block, we'll also need to update Travis is failing due to this discrepancy. |
Good spot! I've updated the Jest snapshot. I used:
|
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.
🚢
Changes proposed in this Pull Request:
<button>
to support the associated keyboard events.References:
Does this pull request change what data or activity we track or use?
No.
Testing instructions:
Test the overlay in a selection of themes and check that the visual appearance of the close button has not changed.
Inspect the button with your browser's accessibility tools and ensure that you can see the correct label:
Proposed changelog entry for your changes:
Not required.