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 11279 - the "assigned access key" section doesn't seem to know if it's a definition or a requirement. Should probably be rephrased to more correctly use RFC2119.
Summary: the "assigned access key" section doesn't seem to know if it's a definition o...
Status: RESOLVED FIXED
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: a11y
Depends on:
Blocks:
 
Reported: 2010-11-09 22:09 UTC by contributor
Modified: 2011-08-04 05:04 UTC (History)
6 users (show)

See Also:

Attachments

Description contributor 2010-11-09 22:09:44 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/editing.html?style=highlight
Section: http://www.whatwg.org/specs/web-apps/current-work/#processing-model-3

Comment:
the "assigned access key" section doesn't seem to know if it's a definition or
a requirement. Should probably be rephrased to more correctly use RFC2119.

Posted from: 216.239.45.4
Comment 1 Michael Cooper 2010-11-23 17:09:40 UTC 
Bug triage sub-team doesn't think this is a A11Y TF priority. It's not an HTML feature, just a spec clarity issue. Our understanding is there is a specific reason for the phrasing approach, and doesn't need task force involvement.
Comment 2 Ian 'Hixie' Hickson 2011-02-03 20:35:02 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: Accepted
Change Description: see diff given below
Rationale: Concurred with reporter's comments.
Comment 3 contributor 2011-02-03 20:35:26 UTC 
Checked in as WHATWG revision r5818.
Check-in comment: RFC2119ify the "assigned access key" section
http://html5.org/tools/web-apps-tracker?from=5817&to=5818
Comment 4 Michael[tm] Smith 2011-08-04 05:04:32 UTC 
mass-moved component to LC1