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

[Bug 11238] Enable canvas to support accessible rich text editing

From: <bugzilla@jessica.w3.org>
Date: Sun, 02 Jan 2011 19:00:03 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1PZT9v-0004JW-MG@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11238

Rich Schwerdtfeger <schwer@us.ibm.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|INVALID                     |

--- Comment #3 from Rich Schwerdtfeger <schwer@us.ibm.com> 2011-01-02 19:00:02 UTC ---
It is a general view by people who work in accessibility that authors do no
adhere to the intent of a set of people. The do what, in their mind will
benefit them or their company. Consequently, provisions must be made to support
accessibility. Using accessibility as a vehicle to prevent authors from not
adhering to the intent of the original standard authors only leads to users
being excluded from using the technology.  

If you follow the technical plenary discussions you will find that this issue
is already well under way to being addressed by the canvas accessibility team. 

If you follow parts of the technical plenary you will find that some
participants, in the television industry felt they could live with limited HTML
profile that included only canvas and javascript. They referred to this as "the
sweet spot." This means that authors will want to have complete user drawn
applications as the accessibility team has predicted. That would include rich
text editing.

I am confused by your last comment about using JavaScript to abuse HTML when
your own company uses JavaScript and tables extensively in ways that were not
intended for HTML 4.01. Examples are gmail and Google docs.  

The canvas accessibility sub team will propose a solution,The final proposal
for rich text editing was not to be complete until Last Call. However, we seem
to be coming to a solution more rapidly that will make use of some API changes
but also ARIA with some minor enhancements. 

In the long run authors will be pleased that the designers of HTML had the
foresight to build accessibility features into the language to support use
cases like rich text editing.

-- 
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, 2 January 2011 19:00:06 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 2 January 2011 19:00:07 GMT