[csswg-drafts] [css-ui-4] Change the pointer cursor to indicate any interactive element.

kizu has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-ui-4] Change the pointer cursor to indicate any interactive element. ==
For years and years [the definition](https://drafts.csswg.org/css-ui-4/#valdef-cursor-pointer) of the `pointer` cursor in specs did not change:

> _**'pointer'**_
> The cursor is a pointer that indicates a link.

But that definition is clearly outdated: today (and for years) this value was used by designers and developers not only for the “links” but for any other interactive element that did not have any other cursor defined for them, for example, for buttons. And there are a lot of new interactive elements in the modern web that are often somewhere between links and buttons.

For some reason, I often find articles in support for this legacy definition, but I yet to see any objective argument on why it should be like that. I myself wrote [an article with most of my arguments](http://kizu.ru/en/issues/cursor-pointer/) in January 2013.

I propose to change this definition to something like that:

> _**'pointer'**_
> The cursor is a pointer that indicates an interactive element, clicking or tapping on which would result in any action (for example links and buttons).

I understand that that is a somewhat controversial topic, but if you'd look at the websites in the real world, you would see that probably most of them use the `pointer` for buttons. And its unlikely they would change it, so it would make sense for the specification to change in favor of a better definition that would make the web more accessible.


Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1936 using your GitHub account

Received on Saturday, 4 November 2017 10:41:10 UTC