This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
currently the image map section of the spec [http://dev.w3.org/html5/spec/the-canvas-element.html#image-maps] does not define the behaviour and requirements for setting and moving focus on image map regions. Please define specify this. ensuring that the behaviour is the same as the focus behaviour of all other elements.
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: Did Not Understand Request Change Description: no spec change Rationale: I don't understand. Could you elaborate? The focusing steps seem to handle <area>, and the definition of "focusable" handles <area> specially, so this all seems well-defined unless I'm missing something.
>Rationale: I don't understand. Could you elaborate? The focusing steps seem to > handle <area>, and the definition of "focusable" handles <area> specially, so > this all seems well-defined unless I'm missing something. While focus moves to the image map areas, if an area is out of the viewport when it recieves focus it is not moved into the viewport (this behaviour occurs with all other elements on the page no? so suggestion is to define this for area so the behaviour is not disadvantageous to keyboard only users. (In reply to comment #1) > 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: Did Not Understand Request > Change Description: no spec change > Rationale: I don't understand. Could you elaborate? The focusing steps seem to > handle <area>, and the definition of "focusable" handles <area> specially, so > this all seems well-defined unless I'm missing something.
The HTML Accessibility Task Force intends to track these issues, per the proposal at http://lists.w3.org/Archives/Public/public-html-a11y/2010Jan/0245.html.
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: Did Not Understand Request Change Description: no spec change Rationale: If you could help me a little more that would be great. Could you quote the text that applies to other elements which doesn't apply to <area> and which I should apply to <area> as well? I'm not sure I fully understand your request yet and I'd like to make sure I understand it before trying to make any changes. Thanks!
http://www.w3.org/2002/09/wbs/44061/20080513_bugs/results#xq7 Assign to Charles McCathieNevile with a deadline of 10 June 2010. Close after that if no proposal received. In other words, the A11Y TF accepts that this bug be closed without further action even though it's marked needsinfo.
(In reply to comment #5) > http://www.w3.org/2002/09/wbs/44061/20080513_bugs/results#xq7 > > Assign to Charles McCathieNevile with a deadline of 10 June 2010. Close after > that if no proposal received. Charles has a proposal: http://www.w3.org/html/wg/wiki/ChangeProposals/Map4NotAdom