-
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
Small improvements for the Document Overview labelling #49555
Conversation
Size Change: -20 B (0%) Total Size: 1.34 MB
ℹ️ View Unchanged
|
Flaky tests detected in 126afa7. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/4605502206
|
@afercia Wow, coming after me with the close button. :) I think I changed this at one point when the region labeling was not totally clear. Makes sense to shorten it now. It is always a battle of too much context vs. not enough. I am sure your changes broke a ton of E2E tests though, let me know if you need assistance fixing all of them. |
Also, do not forget that there are other sidebars to edit.
Other than the tests and other sidebars, this tests well for me. Thanks. |
Tanks @alexstine ❤️ Sure. Thinking it would be good to run an audit of the labelling of several parts of the UI. It's pretty inconsistent. See verbs vs. names for controls in the same component, use of spatial references, use of the verb toggle, lack of context ot too much context, etc. |
70f4966
to
126afa7
Compare
What?
I'd like to propose two quick, small improvements for the Document Overview labelling:
1
Remove a redundant aria-label. Labelling a
div
element that isn't interactive or doesn't have a labelable ARIA role is a bit pointless. Thearia-label
highlighted in the screenshot below doesn't do anything:2
The close button
aria-label
(and tooltip) is way too long. A simpleClose
is enough to communicate the functionality ina meaningful way. Context is already provided by the labeled ARIA region. Shorter is better for speech recognition software users. Also, text that is mostly provided for blind screen reader users should preferably avoid spatial terminology such as 'sidebar': as a blind user, I wouldn't mind whether this region is visually placed on the side, top, bottom or in any other spot of the screen.Why?
See above.
How?
Testing Instructions
Testing Instructions for Keyboard
X
close button.Close
.Screenshots or screencast