Incorrect cursor style in Tabs example

[ryo-manba]

In the Example of Tabs with Automatic Activation, the tabs are styled with cursor: pointer. However, according to the CSS2 spec, the pointer cursor indicates a link, but tabs are not links. It suggests cursor: default is more suitable for non-link tab elements.

References:

• Buttons shouldn't have a hand cursor – Adam Silver
• CSS 2.1 User Interface

[css-meeting-bot]

The ARIA Authoring Practices (APG) Task Force just discussed Correct CSS cursor property for tabs.

The full IRC log of that discussion

<jugglinmike> Topic: Correct CSS cursor property for tabs
<jugglinmike> github: https://github.com//issues/2951
<jugglinmike> Matt_King: This person is referencing the CSS specification
<jugglinmike> jongund: MDN says that the "pointing hand" image indicates a link
<jugglinmike> jongund: But there's nothing for buttons or forum controls
<jugglinmike> jongund: I would check with James on this because he's the one who suggested we adopt "cursor"
<jugglinmike> jugglinmike: The referenced spec is outdated, and it's not clear that the text is normative
<jugglinmike> Matt_King: It sounds like the consensus of the group is that we don't believe the proposed change is justified by the referenced specification.
<jugglinmike> Matt_King: Further, that if we were going to make a change (which would need to touch many more parts of the APG), we would need more conclusive and authoritative rationale
<jugglinmike> jongund: Then again, tabs look more like inline text, similar to links, and that's why using the hand pointer might seem appropriate.
<jugglinmike> Matt_King: It would be great to get perspective from the CSS working group
<jugglinmike> jugglinmike: The latest version of the relevant CSS spec addresses this
<jugglinmike> jugglinmike: https://drafts.csswg.org/css-ui/#cursor
<jugglinmike> jugglinmike: Its description of the value of "pointer" includes the following text: "Authors should use pointer on links and may use on other interactive elements."
<jugglinmike> Matt_King: Ah, I think that settles it, then

[ryo-manba]

Thanks for the discussion! However, it appears that the current CSS specification is still in the Editor's Draft stage. It will be some time before it becomes an official recommendation, but can we use this draft as a basis? This is my simple question.

[mcking65]

@ryo-manba asks:

Thanks for the discussion! However, it appears that the current CSS specification is still in the Editor's Draft stage. It will be some time before it becomes an official recommendation, but can we use this draft as a basis? This is my simple question.

For normative changes to the specification, we would not ordinarily base decisions on a draft that is early in the spec process. However, since this doesn't appear to be normative guidance and since it does not require user agent changes, then it seems safe, and likely best, to follow the guidance in the draft referenced by @jugglinmike.

If you find evidence that suggests a different course of action is better, please let us know by reopening this issue.