W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > September 2009

[Bug 7740] Authoring advice for canvas is bad for accessibility

From: <bugzilla@wiggum.w3.org>
Date: Mon, 28 Sep 2009 09:39:58 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1MsCi6-000775-Q1@wiggum.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=7740


Henri Sivonen <hsivonen@iki.fi> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |hsivonen@iki.fi




--- Comment #1 from Henri Sivonen <hsivonen@iki.fi>  2009-09-28 09:39:58 ---
I'm not disputing the current state of affairs, and the prospective advice in
the spec doesn't work yet. However:

A while ago, adding more API surface to <canvas> was suggested as a solution to
the current accessibility defects of <canvas>. Such new API surface wouldn't be
supported in browsers that have already been shipped. Why is the solution put
forward in the spec being held to a different standard?

If <canvas> is inaccessible in shipped browsers, surely you are
overconstraining the problem if you require solutions to work in shipped
browser releases if there is no such solution.

Or are you just asking for a special note that this particular paragraph in the
spec is prospective at this time as opposed to being retrospective like some
other paragraphs of the spec? In general, the authoring advice in the spec is
written for the time when browsers implement the HTML5 spec.


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Monday, 28 September 2009 09:48:51 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:01 UTC