WBS comments objecting to CP to have single Canvas API for caret positioning and focus ring support

aloha!

in case anyone else was considering responding to the survey on HTML
WG Issue 131 located at:

http://www.w3.org/2002/09/wbs/40318/issue-131-objection-poll/

since my comments are not-yet reflected in:

http://www.w3.org/2002/09/wbs/40318/issue-131-objection-poll/results#xkeepnew

but are logged in:

http://lists.w3.org/Archives/Public/www-archive/2011Mar/0039.html

i thought i would post the comments i submitted, objecting to the 
Change Proposal to have a single Canvas API for caret positioning 
and focus ring support

QUOTE cite="http://lists.w3.org/Archives/Public/www-archive/2011Mar/0039.html"

Objections: 

i object to this change proposal because:

1. the change proposal produced by the Canvas Subgroup of the HTML
Accessibility Task Force under the leadership and editorship of Richard
Schwerdtfeger, was developed in close consultation with screen reader,
screen magnification and other AT developers, who provided crucial
information as to what specifically is needed to make the contents and full
functionality of a CANVAS object available to accessibility APIs, and,
thereby, to assistive technologies, enabling use of CANVAS content by
persons using assistive technology;

2. the precise wording of the change proposal produced by the Canvas
Subgroup of the HTML Accessibility Task Force under the leadership and
editorship of Richard Schwerdtfeger provides actual assistive technology
developers precisely what they requested and need in order to make CANVAS
function with screen magnification programs, screen readers, other
assistive technologies, and -- crucially -- the various combinations of
assistive technologies (e.g. magnification with supplemental speech, access
to a refreshable braille display, etc.) which provide as equivalent a
computing experience as possible to actual users today and into the future;

3. the technical errors and insufficiencies in this change proposal would
undo all of the work and effort put into the change proposal produced by
the Canvas Subgroup of the HTML Accessibility Task Force under the
leadership and editorship of Richard Schwerdtfeger, in partnership and
close co-operation with developers of assistive technology; the dialogue
between the Canvas Subgroup, the assistive technology community and the web
developer community serves as a model of how and why the HTML Accessibility
Task Force's participation in the drafting of HTML5 is essential, as the
Canvas Subgroup solicited and received feedback from the larger community,
and thereby succeeded in providing spec-ready text that addresses the
issues identified by those who develop assistive technologies, CANVAS
applications and accessibility APIs; the evidence of this close cooperation
is reflected in the archive for the public-canvas-api list (which is the
subgroup's primary forum for accessibility work on Canvas)

http://lists.w3.org/Archives/Public/public-canvas-api

THEREFORE, i strongly urge the chairs to adopt the change proposal
contained in:

http://www.w3.org/html/wg/wiki/ChangeProposals/CaretSelection

and object to the change proposal contained in:

http://lists.w3.org/Archives/Public/public-html/2011Mar/0521.html

These answers were last modified on 31 March 2011 at 18:32:21 U.T.C.
by Gregory Rosmaita
UNQUOTE

-----------------------------------------------------------------
Accessibility, Internationalization, and Interoperability are not
"features", "overlays" or "add-ons".  Rather, they are core 
components of any architecture -- programmatic or otherwise.
-----------------------------------------------------------------
     Gregory J. Rosmaita, gregory@linux-foundation.org
Vice-Chair, WebMaster & Listmaster, Open Accessibility Workgroup
http://a11y.org/                                http://a11y/specs
-----------------------------------------------------------------

Received on Thursday, 31 March 2011 18:43:58 UTC