-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Site editor: Add a navigable region for content area of Library and Template views #51782
Conversation
This also seems to fix the 'Manage all templates' view, which uses the My search skills failed me initially, so I didn't realise edit: I've updated the PR description |
Size Change: +43 B (0%) Total Size: 1.42 MB
ℹ️ View Unchanged
|
Flaky tests detected in 7cf608296adea8f236514a6370df3b28310869d3. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/5342501276
|
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.
Nice improvement @talldan, thank you 👍
✅ Code changes look good
✅ Can navigate between regions on Library page
✅ Can navigate between regions on Templates/Manage all templates pages
🚢
7cf6082
to
b116b86
Compare
Is there a reason that this is set up as |
I don't have much history or context here, however, this PR didn't introduce the navigable region around the sidebar which includes navigation. It appears that the region in question was labelled "Navigation sidebar" originally and later renamed to "Navigation" in #49614. There might be some answers there. My guess for the reasoning behind using
This area isn't a strong suit of mine, so please take that with a grain of salt. If we need to make some changes, I think a dedicated issue would be the best course. |
What?
Adds a navigable region to the Library content area and the Template content area (when you navigate to 'Manage all templates')
Why?
It's a useful aid for keyboard/screenreader users to jump between parts of the screen
How?
There seems to be a
Page
component that look perfect for this purpose. It already receives atitle
, so I've used that for the navigable region label.Testing Instructions for Keyboard
Expected: There are two regions that are announced correctly, 'Navigation' and 'Library content'.
Expected: There are two regions that are announced correctly, 'Navigation' and 'Templates'.
Screenshots or screencast
There's no visible difference