W3C home > Mailing lists > Public > public-html-a11y@w3.org > February 2010

[Bug 8722] focus behaviour should be same for canvas regions as for elements

From: <bugzilla@wiggum.w3.org>
Date: Thu, 25 Feb 2010 02:37:50 +0000
To: public-html-a11y@w3.org
Message-Id: <E1NkTbq-0002Rx-SV@wiggum.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8722


Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|                            |NEEDSINFO




--- Comment #9 from Ian 'Hixie' Hickson <ian@hixie.ch>  2010-02-25 02:37:50 ---
I have no idea what this means.

> Unless a focus event is recognized by AT,

Do you mean a 'focus' event, a focus request by the user, a change of focus, a
call to element.focus(), a call to window.focus(), or something else?


> at the co-ordinates of the focus rectangle drawn on the canvas,

Do you mean a focus rectangle drawn by drawFocusRing(), a focus rectangle drawn
by script, or a focus rectangle drawn by a UA rendering a focus rectangle
around an actual control?


> then AT will not be able to move focus to the rectangle

By "move focus" do you mean the magnification focus? The OS focus? The UA
focus? The JS/DOM/CSS focus? Some other focus?


> as it effectively has no meaning other than a being a shape on the canvas.
> I understand that a focus event can be flagged by the use of standard
> APIs.

Do you mean OS APIs? AT APIs? ARIA? The canvas 2D APIs?


> Does the the spec currently require/recommend that such an event flag
> occurs when the focus rectangle is drawn? If not why not? 

I have no idea what this question means.


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?


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Thursday, 25 February 2010 02:57:51 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 04:42:02 GMT