- From: Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com>
- Date: Thu, 30 Jun 2011 18:36:22 +0100
- To: Henri Sivonen <hsivonen@iki.fi>
- Cc: Sean Hayes <Sean.Hayes@microsoft.com>, "E.J. Zufelt" <everett@zufelt.ca>, Paul Bakaus <pbakaus@zynga.com>, "Tab Atkins Jr." <jackalmage@gmail.com>, John Foliot <jfoliot@stanford.edu>, Charles Pritchard <chuck@jumis.com>, Charles McCathieNevile <chaals@opera.com>, Richard Schwerdtfeger <schwer@us.ibm.com>, Cameron McCormack <cam@mcc.id.au>, Cynthia Shelly <cyns@microsoft.com>, "david.bolter@gmail.com" <david.bolter@gmail.com>, Frank Olivier <Frank.Olivier@microsoft.com>, "Mike@w3.org" <Mike@w3.org>, "public-canvas-api@w3.org" <public-canvas-api@w3.org>, "public-html@w3.org" <public-html@w3.org>, "public-html-a11y@w3.org" <public-html-a11y@w3.org>
On Wed, Jun 29, 2011 at 3:49 PM, Henri Sivonen <hsivonen@iki.fi> wrote: > On Wed, 2011-06-29 at 14:23 +0000, Sean Hayes wrote: >> It took me 5 minutes to find these examples of people "doing it wrong" >> http://www.ericom.com/AccessNow_FAQs.asp >> http://www.thinvnc.com/index.html > > These seem to be remote desktop clients that transfer the screen image > from another system. If <canvas> had the API Rich is proposing, would > you expect these apps to use the remote system accessibility API to > transfer the accessibility API state over? How does Microsoft Remote > Desktop and VNC deal with this with non-Web clients? AFAICT the canvas accessibility APIs proposed would not help the remote system access use-case. I tried to discuss this previously: http://lists.w3.org/Archives/Public/public-html-a11y/2011Jan/0164.html If this is incorrect could someone explain *how* they would help? -- Benjamin Hawkes-Lewis
Received on Thursday, 30 June 2011 17:36:50 UTC