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

http://www.w3.org/Bugs/Public/show_bug.cgi?id=7740





--- Comment #2 from steve faulkner <faulkner.steve@gmail.com>  2009-09-28 10:00:03 ---
hi henri,
I am not holding anything to a different standard,I am saying following this
authoring advice causes problems, this should be noted in the spec, so authors
don't who follow the advice think they are providing an accessible fallback or
the spec should be changed to better reflect how browsers support fallback.

I would hope that anywhere in the html5 spec where authoring advice results in
a demonstrably worse user experience be considered a bug.


(In reply to comment #1)
> 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 10:00:13 UTC