- From: Frank Olivier <Frank.Olivier@microsoft.com>
- Date: Sat, 11 Feb 2012 22:06:04 +0000
- To: Frank Olivier <Frank.Olivier@microsoft.com>, Richard Schwerdtfeger <schwer@us.ibm.com>, Paul Cotton <Paul.Cotton@microsoft.com>, "Sam Ruby (rubys@intertwingly.net)" <rubys@intertwingly.net>
- CC: "public-html@w3.org" <public-html@w3.org>, "public-html-a11y@w3.org" <public-html-a11y@w3.org>
To clarify: We should split this issue into the following two issues: [a] Reading (static) text from a canvas element / defining how authors indicate where (static) text is on a canvas element Define what author guidance and methods should be used to enable users to find and read static text that has been rendered onto a canvas. This might include enabling caret browsing and text selection. http://www.w3.org/html/wg/wiki/ChangeProposals/FocusRingTextBaseline http://www.w3.org/wiki/Reading_text_in_canvas [b] Text editing in canvas Define what author guidance and methods should be used to create accessible text editors using canvas as a rendering surface. - or - Keep existing spec text that advised authors to not implement text editors using canvas as a rendering surface http://www.w3.org/html/wg/wiki/ChangeProposals/CaretSelectionRevised http://www.w3.org/wiki/No_edit_change_proposal_for_canvas_text_editing I've added the recent Change Proposals to the two individual issues. -----Original Message----- From: Frank Olivier [mailto:Frank.Olivier@microsoft.com] Sent: Friday, February 10, 2012 2:44 PM To: Richard Schwerdtfeger; Paul Cotton; Sam Ruby (rubys@intertwingly.net) Cc: public-html@w3.org; public-html-a11y@w3.org Subject: RE: Issue 131 Change Proposal Thanks for the feedback, Rich. I think that there are two issues in 131 (text editing in canvas, and reading static text rendered into a canvas element); I have filed change proposals for both. I think that, for the issue of reading text from a canvas, we should be able to achieve consensus, as you note below. For text editing, consensus seems less likely. I propose that we split 131 into separate issues. Thanks Frank -----Original Message----- From: Richard Schwerdtfeger [mailto:schwer@us.ibm.com] Sent: Friday, February 10, 2012 1:41 PM To: Frank Olivier Cc: public-html@w3.org; public-html-a11y@w3.org Subject: Re: Issue 131 Change Proposal Hi Frank, Thanks for submitting another solution Frank. I believe this would work provided we add some work under way related to ARIA 1.1. I am not sure everyone uses the subdom text cursor position. Another issue is that Macs, currently don't support caret browsing. If you would like me to discuss the work under way I would be happy to do that. In short, I believe this would work but we would need to do the other things. Note: to the chairs: This is not an alternative to the text baseline. That is another aspect for Issue 131 which would apply to either proposal for caret/selection tracking. Rich Rich Schwerdtfeger From: Frank Olivier <Frank.Olivier@microsoft.com> To: "public-html@w3.org" <public-html@w3.org>, Cc: "public-html-a11y@w3.org" <public-html-a11y@w3.org> Date: 02/10/2012 03:12 PM Subject: Issue 131 Change Proposal I would like to submit http://www.w3.org/wiki/Reading_text_in_canvas as a change proposal for this issue. This proposal defines author guidance that outlines a solution to the problem of reading text in canvas elements, improving accessibility. Thanks Frank
Received on Saturday, 11 February 2012 22:06:39 UTC