Re: html5 editor responds to Canvas accessibility related bugs

Hi Ian,
Yeah I have seen these before,
The does not answer anything, you are making assertions on how difficult and
useless it would be, then asking me to run off and prove you wrong, sorry
doesn't work that way for me.
I responded to the email you just cited:

http://lists.w3.org/Archives/Public/public-html/2010Jun/0542.html:
http://lists.w3.org/Archives/Public/public-html/2010Jun/0545.html


(it's on the wrong side
>of the 80/20 rule)

merely invoking the 80/20 rule without providing any data means nothing.

>and it has a vastly higher implementation cost than is justified by the
authoring benefit derived.

At least one browser vendor (Opera) has suggested that part of the appeal is
that the implementaion costs are minimal. apple have indicated that would
implement and microsoft support it, Firefox accessibility people indicated
support for the idea.

So where is the pushback from?

>Furthermore, because this would get used so rarely, browser vendors
>would likely fail to prioritise this when fixing bugs, and we'd end up
>with this feature being perennially buggy.

how do you back up your claim it would be used "so rarely"?

I also provided a real world example in the next email in the thread (you
never responded)

Use case example:

http://caimansys.com/painter/index.html
on the right had side are 3 widgets built using canvas
color widget
brush size widget
playback toolbar

It would be trivial for all 3 to be made keyboard accessible using an image
map and have ARIA attached to the area elements to expose the semantics
(roles, states and properties) of the interface elements.

so how about responding now instead of attempting to palm me off?

regards
stevef
On 27 September 2010 09:27, Ian Hickson <ian@hixie.ch> wrote:

> On Mon, 27 Sep 2010, Steven Faulkner wrote:
> >
> > you wrote:
> > "Absolutely, image maps are a terrible solution to making <canvas>
> > accessible."
> >
> > can you elaborate, sting its terrible , as you have said previously,
> > without providing any explanation, is not helpful.
>
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=9061#c2
>
> I encourage you to try writing a usemap-based fallback for a real-world
> interactive canvas. Find a real-world use of <canvas>, and then try to
> make it accessible using an image map. The problems I describe will very
> quickly become quite apparent. (Bonus points if you find a canvas where
> the interaction is dynamic or animated, or where the painting code uses
> transforms, both of which increase the difficulty even further.)
>
> --
>  Ian Hickson               U+1047E                )\._.,--....,'``.    fL
> http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
> Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
>



-- 
with regards

Steve Faulkner
Technical Director - TPG Europe
Director - Web Accessibility Tools Consortium

www.paciellogroup.com | www.wat-c.org
Web Accessibility Toolbar -
http://www.paciellogroup.com/resources/wat-ie-about.html