[wp-trac] [WordPress Trac] #47171: Incorrect cursor used on buttons
WordPress Trac
noreply at wordpress.org
Fri Sep 20 20:07:44 UTC 2019
#47171: Incorrect cursor used on buttons
-------------------------------------+-------------------------------------
Reporter: nrqsnchz | Owner: (none)
Type: defect (bug) | Status: assigned
Priority: normal | Milestone: 5.3
Component: Administration | Version:
Severity: normal | Resolution:
Keywords: has-screenshots needs- | Focuses: ui, accessibility,
design-feedback wpcampus-report | coding-standards
-------------------------------------+-------------------------------------
Comment (by melchoyce):
> That said, this ticket is interesting in that the W3C guideline goes
against what many users anticipate: if something is clickable, they expect
to see a pointer icon when hovering over it.
I agree with Kjell — as a user, I expect that any interactive element will
use the "pointer" cursor. Interactivity on the web has changed a lot in
the past decade, and people have been using pointers on anything that
looks like a button for so long (maybe because we started styling link
tags like button once CSS was mainstreamed, I don't know) that the
original intent has been superseded the learned behavior of "pointer = I
can click this."
Since the argument is around using consistent and relevant cursors as to
benefit users with cognitive disabilities, I'd actually argue that
WordPress dropping the pointer from buttons actually goes against the
intent of the spec, because we'd be using buttons inconsistently from much
of the web. Having a pointer also makes it more clear when a button is
''disabled'', because disabled buttons shouldn't have the pointer cursor.
I think this is a case where a browser default hasn't caught up with
modern web practices.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/47171#comment:18>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list