This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 11959 - Hi, user agents are "encouraged" to make it possible to view tooltips without the use of a pointing device (it means while browsing with the keyboard for instance). Why don't we make this an obligation instead of an encouragement ? If we don't make it a "
Summary: Hi, user agents are "encouraged" to make it possible to view tooltips without...
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML5 spec (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-02 14:14 UTC by contributor
Modified: 2011-08-04 05:03 UTC (History)
5 users (show)

See Also:

Attachments

Description contributor 2011-02-02 14:14:09 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/rendering.html
Section: http://www.whatwg.org/specs/web-apps/current-work/#the-title-attribute-0

Comment:
Hi, user agents are "encouraged" to make it possible to view tooltips without
the use of a pointing device (it means while browsing with the keyboard for
instance). Why don't we make this an obligation instead of an encouragement ?
If we don't make it a "must", web developpers are still gonna re-develop this
tooltip using javascript (certainly in a bad and inaccessible way...) ?

Posted from: 83.145.100.34
Comment 1 Ian 'Hixie' Hickson 2011-03-03 23:23:55 UTC 
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Rejected
Change Description: no spec change
Rationale: 

Whether we make this MUST or SHOULD won't make any difference to what browser vendors or Web developers do, in practice.

In theory, it's a SHOULD because there are times where you can't do it. For example, suppose that you are writing a Web browser for someone whose only possible way of interacting with the page is using a pointing device controlled by blinking their left eyelid. There's no point requiring that the writer of this Web browser also provide a keyboard, since it won't be useful to the user.
Comment 2 Michael[tm] Smith 2011-08-04 05:03:11 UTC 
mass-moved component to LC1