- From: Karl Dubost <karld@opera.com>
- Date: Wed, 6 Jul 2011 14:38:08 -0400
- To: "Tab Atkins Jr." <jackalmage@gmail.com>
- Cc: Charles McCathieNevile <chaals@opera.com>, Henri Sivonen <hsivonen@iki.fi>, "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>
Le 1 juil. 2011 à 15:15, Tab Atkins Jr. a écrit :
> On Fri, Jul 1, 2011 at 7:41 AM, Charles McCathieNevile <chaals@opera.com> wrote:
>> Why would you believe for a moment that nobody would make such a decision?
>
> Because it's *really* hard. *Much* harder than just using HTML.
It depends on what you want to do. As soon as Macromedia created a tool to draw circles, triangles, and shiny things, it was a **lot easier** for Print/Animation designers to produce content put on the Web through flash.
As soon as "Export as canvas" will be softwares, the people who have no clue will use it.
You are addressing the wrong crowd. The crowd who will use Canvas will not be Web developers, but people who Motion Graphics Designer, Artistic Director, doing exactly the same mistakes that were done with flash, using motion graphics for the wrong thing.
NOW, the interesting question is
Would "creating accessibility hooks in Canvas" (whatever it means) help solve accessibility issues for users of content developed with these tools used by designers.
DESIGNERS ---> TOOLS ---> CONTENT ---> BROWSERS ---> USERS
(canvas)
--
Karl Dubost - http://dev.opera.com/
Developer Relations & Tools, Opera Software
Received on Wednesday, 6 July 2011 18:38:50 UTC