Re: ISSUE-201: canvas-fallback - Chairs Solicit Alternate Proposals or Counter-Proposals

Hi ted,

as per my previous email

I would be appreciative if you could provide in your change proposal,
> rationale and any details of how this aspect of hixie's hitregion() may be
> implemented to hook up with accessibility APIs:
> An unbacked region description consists of the following:
> Optionally, a label.
> An ARIA role, which, if the unbacked region description<http://www.whatwg.org/specs/web-apps/current-work/multipage/the-canvas-element.html#hit-region%27s-unbacked-region-description> also
> has a label, could be the empty string.


no rationale is provided for this aspect.

I am not adverse to the additions to the canvas spec, but think it a
reasonable expectation that when asked for, an explanation of the reasoning
for a particular feature is provided. I also think that if no rationale for
something is provided it is reasonable to dispute the addition of the
feature.

regards
Stevef


On 12 April 2012 00:49, Edward O'Connor <eoconnor@apple.com> wrote:

> I wrote:
>
> > I volunteer to write an alternate Change Proposal for [ISSUE-201].
>
> Here it is:
>
>         http://www.w3.org/html/wg/wiki/User:Eoconnor/ISSUE-201
>
>
> Thanks,
> Ted
>
>


-- 
with regards

Steve Faulkner
Technical Director - TPG

www.paciellogroup.com | www.HTML5accessibility.com |
www.twitter.com/stevefaulkner
HTML5: Techniques for providing useful text alternatives -
dev.w3.org/html5/alt-techniques/
Web Accessibility Toolbar - www.paciellogroup.com/resources/wat-ie-about.html