W3C home > Mailing lists > Public > public-html-a11y@w3.org > December 2011

Re: Request to re-open issue 131

From: Sam Ruby <rubys@intertwingly.net>
Date: Thu, 15 Dec 2011 13:42:46 -0500
Message-ID: <4EEA3FA6.1040206@intertwingly.net>
To: Jonas Sicking <jonas@sicking.cc>
CC: david bolter <david.bolter@gmail.com>, Richard Schwerdtfeger <schwer@us.ibm.com>, chuck@jumis.com, Cynthia Shelly <cyns@microsoft.com>, dbolter@mozilla.com, franko@microsoft.com, Maciej Stachowiak <mjs@apple.com>, Paul Cotton <Paul.Cotton@microsoft.com>, public-canvas-api@w3.org, public-html@w3.org, public-html-a11y@w3.org, rob@robweir.com
On 12/14/2011 05:02 PM, Jonas Sicking wrote:
> I am personally not at all interested in implementing APIs that are
> there solely for building text editors in canvas. I simply don't think
> that people can build good accessible text editors in canvas. Sure, we
> can slap a few APIs on there to improve certain aspects of it, but I
> don't believe anyone has ever proposed an API which will allow a
> *good* text editor to be written.

I got the following from Rob Weir, and he gave me permission to repost 
it here:

     One thing to consider:  editors are more than word processor style
     text editors.  Presentation editors are more likely to use Canvas,
     and that would bring a mix of integrated text and graphics, e.g.,
     text boxes.   It is not just text, but things like arrows and
     connectors, where there is semantic content implied by the
     placement of graphical objects.   IBM did a lot of work in this
     area with ODF 1.1.

- Sam Ruby
Received on Thursday, 15 December 2011 18:43:23 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:05:25 UTC