.caretBlinkRate() can be wired up to GetCaretBlinkTime in Windows. See http://msdn.microsoft.com/en-us/library/ms648401(VS.85).aspx
.setCaretSelection can be wired up to SetCaretPos; MSDN has some good documentation on this.
SetFocus() http://msdn.microsoft.com/en-us/library/ms646312(VS.85).aspx can be used for focus management for .drawFocusRing; one approach would be to use a child window at the x,y coordinates.
Typo: >/p> in the setCaretSelectionPos(element, x, y) steps section.
From: Richard Schwerdtfeger [mailto:schwer@us.ibm.com]
Sent: Monday, May 10, 2010 1:43 PM
To: david.bolter@gmail.com; surkov.alexander@gmail.com; Frank Olivier; janina@rednote.net; mike@w3.org; mjs@apple.com; Canvas API; public-canvas-api-request@w3.org; HTML Accessibility Task Force; 'Maciej Stachowiak'; Cynthia Shelly
Subject: Re: HTML Canvas 2D Context API change proposal for magnifier focus and caret/selection tracking
I would like to have all user agent developers to please provide feedback/changes they would like to see made to the proposal by Monday so that I may make any necessary changes to the final draft for May 24, 2010 to submit for a straw pole vote on May 27 in the HTML accessibility task force.
Frank Olivier is going through the proposal with a fine tooth comb and will submit feedback on Thursday in terms of how these changes will map to the Windows accessibility API. These simple changes can all be made in MSAA as I see it so they will also be applicable to Firefox. That said, I would like both David and Alex to review the comments from Frank and submit them to the list. There seems to be a gap on Linux that we may need to fill. I am not aware of an ATK API to have a magnifier track the caret screen position. This may need to be added.
As for Apple I would ask Maciej to look the changes and say if it can be mapped in some way to the Mac OSX accessibility protocol either now or in the future and if there are any changes that need to be made to the proposal. I plan on wrapping this up next week.
Frank indicated that the HTML working group may wish to tweak the API or API parameter names. Personally, that is not an issue for me as long as they are well documented which given the feedback I have as of today the changes made the API modifications clearer. Changes reside between <ZZ> and </ZZ>
I know the HTML working group would like to wrap this all up quickly so I urge you all to review and provide feedback in the requested time frame. Here is the proposal with the attached changes in HTML format:
http://lists.w3.org/Archives/Public/public-canvas-api/2010AprJun/0021.html
There will be no Canvas Accessibility API meeting on Monday, May 17, 2010 as I am traveling but I will have access to email and look forward to your feedback.
Best Regards,
Rich
Rich Schwerdtfeger
CTO Accessibility Software Group