[wbs] response to 'ISSUE-131: Should we add a caret location API to canvas? - Straw Poll for Objections'

The following answers have been successfully submitted to 'ISSUE-131:
Should we add a caret location API to canvas? - Straw Poll for Objections'
(HTML Working Group) for Gregory Rosmaita.



---------------------------------
Objections to the Change Proposal to modify existing Canvas 2D API caret
and focus ring support to drive screen magnification
----
We have a Change Proposal to modify the existing Canvas 2D API caret and
focus ring support to drive screen magnification.  If you have strong
objections to adopting this Change Proposal, please state your objections
below.
Keep in mind, you must actually state an objection, not merely cite
someone else. If you feel that your objection has already been adequately
addressed by someone else, then it is not necessary to repeat it.
Objections: 





---------------------------------
Objections to the Change Proposal to have a single Canvas API for caret
positioning and focus ring support
----
We have a Change Proposal to have a single Canvas API for caret
positioning and focus ring support.  Keep in mind, you must actually state
an objection, not merely cite someone else. If you feel that your objection
has already been adequately addressed by someone else, then it is not
necessary to repeat it.
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; 

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:28:55 U.T.C.
by Gregory Rosmaita

Answers to this questionnaire can be set and changed at
http://www.w3.org/2002/09/wbs/40318/issue-131-objection-poll/ until
2011-03-31.

 Regards,

 The Automatic WBS Mailer

Received on Thursday, 31 March 2011 18:30:03 UTC