- From: <bugzilla@jessica.w3.org>
- Date: Fri, 05 Nov 2010 18:49:06 +0000
- To: public-html@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11238 Summary: Enable canvas to support accessible rich text editing Product: HTML WG Version: unspecified Platform: PC OS/Version: All Status: NEW Severity: major Priority: P2 Component: HTML5 spec (editor: Ian Hickson) AssignedTo: ian@hixie.ch ReportedBy: schwer@us.ibm.com QAContact: public-html-bugzilla@w3.org CC: mike@w3.org, public-html-wg-issue-tracking@w3.org, public-html@w3.org There is a clear use case for creating a profile whereby an author could only use <canvas> and JavaScript as part of the profile opening the doors for a whole plethora of applications that run cross platform through the availability of a common drawing capability. At the 2010 tech plenary a person from the TV community about HTML profiles and the person stated that a subset of HTML which contained <canvas> and HTML would "hit the sweet spot." A number of issues still remain that are not addressed to address this issue. They are: - Provide Access to the blink rate of the OS. - Synchronizing the caret position in a content editable <canvas> subtree to the screen position rendered on the canvas and convey that information to a magnifier. - Convey the persons current selection position when higlighting text to a screen reader and synchronize that with what is in the contenteditable area in the subtree for a screen reader. - Convey the location of grammatical and spelling errors in a contenteditable canvas subtree to an author so that the author may synchronize them with what is rendered on the visual canvas. - Assess what HTML elements in the canvas subtree are allowed in the subtree. For example, should an IFrame be allowed? -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
Received on Friday, 5 November 2010 18:49:10 UTC