[Bug 11239] Canvas support accessible caret tracking independent of Focus Ring tracking

http://www.w3.org/Bugs/Public/show_bug.cgi?id=11239

--- Comment #30 from Rich Schwerdtfeger <schwer@us.ibm.com> 2011-05-01 23:52:14 UTC ---
- I accept the changes for caretBlinkPeriod. 
- I have not tried the code change the editor has made, when I see the full
change I will try it out. We had found defects in the prior code which did not
run and we added commments. Please refer to the change request adapted for the
chairs decision at it:
http://lists.w3.org/Archives/Public/public-html/2011Apr/0657.html
If the editor could adapt his changes to our code it would run and pick up the
performance issues addressed by the editor. 

The changes to drawFocusRing are still inaccurate for these reasons:

- DrawFocusRing must be able to draw a focus ring around an element with focus
or descendant of an element with focus. Often, in rich internet applications an
element with focus will managed visual rendering of focus for its children.
Examples of this are grids, radio groups, listboxes, and tree widgets. 

See the text in:
http://lists.w3.org/Archives/Public/public-html/2011Apr/0657.html

A note to the editor:
In the canvas subtree authors can use aria-activedescendant on one of these
element to convey the focus location of a descendant to an assistive
technology.

example: 
<table role="grid" aria-activedescendant="foo">
...
<tr role="row">
<td role="gridcell" id="foo"> ... </tr>
...
</table> 

- caretSelectionPos still has some problems. I don't have an issue with the
name change or the use of a path to produce the rectangle
-- The accessibility API mapping must step must be provided. 
-- The text does not address when the user agent window is moved or resized

Please see the steps in the change proposal:
http://lists.w3.org/Archives/Public/public-html/2011Apr/att-0657/canvascarseldecision20110426.html#caret-selection

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Sunday, 1 May 2011 23:52:17 UTC