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

RE: correct and incorrect uses of canvas

From: Frank Olivier <Frank.Olivier@microsoft.com>
Date: Thu, 14 Jul 2011 19:07:32 +0000
To: Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com>, Charles Pritchard <chuck@jumis.com>
CC: Canvas <public-canvas-api@w3.org>, Steve Faulkner <faulkner.steve@gmail.com>, HTMLWG WG <public-html@w3.org>, "Richard Schwerdtfeger" <schwer@us.ibm.com>, Cynthia Shelly <cyns@microsoft.com>, "David Singer" <singer@apple.com>, Tab Atkins Jr. <jackalmage@gmail.com>, "Edward O'Connor" <hober0@gmail.com>
Message-ID: <91175A762AB48840AF1473514B26B47534F640A9@TK5EX14MBXC263.redmond.corp.microsoft.com>
" Accessibility for web-based remote system access is most practically approached using remote AT, just as it's currently approached with native remote system access."

Very much agree. At the protocol level, only keyboard+mouse events and simple bitmaps/graphic primitives are transported over the wire. There is no a11y information to hand off to the client AT. The client only represents the remote AT information.

http://msdn.microsoft.com/en-us/library/aa383015(VS.85).aspx
http://en.wikipedia.org/wiki/RFB_protocol



-----Original Message-----
From: Benjamin Hawkes-Lewis [mailto:bhawkeslewis@googlemail.com]
Sent: Tuesday, July 12, 2011 2:08 PM
To: Charles Pritchard
Cc: Canvas; Steve Faulkner; HTMLWG WG; Frank Olivier; Richard Schwerdtfeger; Cynthia Shelly; David Singer; Tab Atkins Jr.; Edward O'Connor
Subject: Re: correct and incorrect uses of canvas

On Tue, Jul 12, 2011 at 8:38 PM, Charles Pritchard <chuck@jumis.com<mailto:chuck@jumis.com>> wrote:
> There was some debate about remote access being a reasonable use case,
> as well as debate about whether the rendering of other non-web/legacy
> formats qualified as a reasonable use case.

If you're talking about me here (?), my argument was *not* that remote access is not a "reasonable use case".

My position was:

1. Use cases can be desirable without being practical to solve.

2. Although the trend towards cloud-computing may make it increasingly irrelevant, remote system access remains a desirable use case to solve for now and could make a practical difference in terms of the employability of people with disabilities.

3. Accessibility for web-based remote system access is most practically approached using remote AT, just as it's currently approached with native remote system access.

You did raise a remote application access use case, but I asked for real-world examples of this and none were forthcoming, so it's very hard to evaluate the use case or suggested approaches.

> Is the support of legacy code an acceptable use case?
> https://github.com/kripken/emscripten/wiki

>
> emscripten runs LLVM byte code, and -necessarily- uses Canvas for
> painting output.

If you're talking about a web application providing a sort of emulator, I think that situation is essentially the same as with remote system access: most practically approached by running AT inside the emulation.

--
Benjamin Hawkes-Lewis


Received on Thursday, 14 July 2011 19:08:13 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:17:36 GMT