[Bug 11239] Canvas support accessible caret tracking independent of Focus Ring tracking

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

--- Comment #35 from Charles Pritchard <chuck@jumis.com> 2011-05-03 21:47:28 UTC ---
(In reply to comment #34)
> drawFocusRing() is fine for things like buttons, which one could legitimately
> expect to see on a canvas. But UI beyond anything as simple as a button quickly
> becomes highly inappropriate.

What standard are you following in these claims? The HTML Forms select element
is quite commonly re-implemented by other methods, such as div tags mixed with
ARIA attributes. Your claim comes with no sources nor technical reasoning, nor
is it particularly on the topic of the change proposal.

> <canvas> isn't supposed to replace HTML. I really don't understand why anyone
> who considers themselves to be advocates of accessibility would even remotely
> want to encourage authoring practices such as implementing entire tree widgets,
> grids, text editors, or list boxes inside <canvas>.

The grid example uses HTML. Canvas is an HTML tag. Advocates of accessibility
engage in the ARIA standard and the WCAG document, by definition. If you would
like to understand, I recommend reviewing WAI documents.

Whatever motivations that accessibility vendors, and general web app vendors
have for using canvas as a method for progressive enhancement, is really not
under your purview. An example I often bring up: When Mozilla decides to
castigate its Bespin authors, that's an internal decision. If they take that
policy further, and "push back" against other entities, it's an act of
hegemony.

> 
> > We're trying to promote GOOD practices, per WCAG 2.0. It'd be nice to have you
> > on board with that intention.
> 
> I'm trying to promote GOOD practices too. It'd be really nice to have _you_ on
> board with that intention. Apparently we disagree about what is a good
> practice.

I've put citations forward in my arguments; you have not. Regardless, we're
trying to accomplish the items outlined in this CP, for the sake of assistive
technology. You've often claimed that such support can be handled
automatically. I disagree. It must be handled with intent.

Your opinions about authors creating complex widgets, interaction with ATs and
the ARIA spec, are lacking authority. Please provide citations, lest you
under-serve the community and the arguments we've been carrying for a good part
of the last twelve months.

-- 
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 Tuesday, 3 May 2011 21:47:34 UTC