W3C home > Mailing lists > Public > public-html@w3.org > December 2011

Re: Request to re-open issue 131

From: Charles Pritchard <chuck@jumis.com>
Date: Sun, 18 Dec 2011 09:59:03 -0800
Message-Id: <129DCF2A-C25F-4258-A94E-F9D34A1760AD@jumis.com>
Cc: Jonas Sicking <jonas@sicking.cc>, Sam Ruby <rubys@intertwingly.net>, david bolter <david.bolter@gmail.com>, Richard Schwerdtfeger <schwer@us.ibm.com>, Cynthia Shelly <cyns@microsoft.com>, "dbolter@mozilla.com" <dbolter@mozilla.com>, "franko@microsoft.com" <franko@microsoft.com>, Maciej Stachowiak <mjs@apple.com>, Paul Cotton <Paul.Cotton@microsoft.com>, "public-canvas-api@w3.org" <public-canvas-api@w3.org>, "public-html@w3.org" <public-html@w3.org>, "public-html-a11y@w3.org" <public-html-a11y@w3.org>
To: Steve Faulkner <faulkner.steve@gmail.com>
The HTML5 Editors draft uses scrollPathIntoView to accomplish the same thing as setCaretSelectionRect but with a broader goal and semantic. I've not been able to get its author to speak up on the issue...  They are both intended to fill in the caret tracking interfaces present at the OS level. These are used by zoom apps, but can also be used by heuristics in screen readers.

The HTML5 editor did not use the caretBlinkRate semantic. I have mixed feelings here. The blink rate is used by some screen readers as part of their heuristics. It's also managed by user preferences set on the OS level. It may be used to return a rate that's relatively safe for viewers that may otherwise suffer if the blink rate set by an author is too high. This semantic  is still useful for caret style navigation and indicators of where keyboard focus is, beyond a simple focus ring. But, it's difficult to generalize it further, as it seems the HTML5 editor would require.

If there are any ideas on how to salvage consensus on this maxFlashRate concept, it'd be nice to hear them. This is different than requestAnimationFrame use cases. This max flash rate is intended for on-screen position and progress indicators to help authors stay on the path to WCAG.



These APIs are based on system accessibility Apis for UI components of all types. There's no need to focus on text entry. There is a need to keep text legibility and tracking in mind.



On Dec 18, 2011, at 2:15 AM, Steve Faulkner <faulkner.steve@gmail.com> wrote:

> Are the methods proposed designed to facilitate the building of text
> editors in canvas? I think not, but clarification from Rich/Charles
> would be useful.
Received on Sunday, 18 December 2011 17:59:33 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:17:42 GMT