-
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
Incorrect cursor used on buttons #15343
Comments
Worth noting this is a "feature" used across all the WordPress admin. Gutenberg uses its own |
Does this need changing or are we sticking with the pattern established in WP Core? |
For full compliance, it should be changed. I guess it needs be discussed by the accessibility and design teams. |
That's interesting! I've never known this was specifically against a11y guidelines. In general on the web, I tend to expect that most "clickable" elements use a pointer cursor (take the buttons here on GitHub for instance, which have a |
Interesting issue, indeed. I don't think this is explicitly mentioned anywhere in the WCAG (I may be wrong). However, it has more to do with operating systems / browsers default: they shouldn't be changed unless there are very, very, good reasons to do so. The native cursor style for buttons is The W3C spec (CSS 2.2) linked above clearly states:
Same for CSS3 UI: https://www.w3.org/TR/css-ui-3/#cursor The rationale is that After some software archeology, turns out some of the related changes are very ancient:
|
Discussed today during the design's team Gutenberg triage in Slack. Created Trac ticket: https://core.trac.wordpress.org/ticket/47171 for follow up. |
I'm going to close this in favor of a more holistic Core approach. Thanks for creating a ticket in Trac, @enriquesanchez! |
Incorrect cursor used on buttons
Issue description
Buttons throughout the application use the pointer cursor instead of the
default.
The use of consistent and relevant cursors may be important for users
who have a cognitive disability, since cursors give a visual clue as to
an element's functionality. Using the pointer cursor for elements which
do not typically show that cursor may be confusing or counter-intuitive
for users.
Issue Code
Remediation Guidance
Only controls that navigate users to new pages/views should have the
cursor set to
pointer
, while controls performing push-button typeactions use
default
.Recommended Code
References
https://www.w3.org/TR/CSS22/ui.html#cursor-props
Note: This issue may be a duplicate with other existing accessibility-related bugs in this project. This issue comes from the Gutenberg accessibility audit, performed by Tenon and funded by WP Campus. This issue is GUT-9 in Tenon's report
The text was updated successfully, but these errors were encountered: