Re: hit regions Firefox support update

On Mon, Feb 17, 2014 at 10:30 AM, Jatinder Mann <jmann@microsoft.com> wrote:

>  On Fri, Feb 14, 2014 at 11:20 AM, Rik Cabanier wrote:
>
> >> On Fri, Feb 14, 2014 at 10:41 AM, Jay Munro <jaymunro@microsoft.com>
> wrote:
>
> >> We've already removed all the at risk features with the exception of
> drawFocusIfNeeded ,
> >> which was agreed upon in the A11y subgroup.
>
> >
>
> > We'll have to bring it back if we want a11y to work in canvas :-(
>
>
>
> If we don't have a 2nd implementation, I rather we leave Hit Regions
> specified in the Level 2 spec and not delay the Level 1 spec by bringing it
> back. The Level 1 spec will already have drawFocusIfNeeded() with two
> implementations
>

Unfortunately, we don't have 2 implementations of an a11y capable version
of drawFocusIfNeeded()
Firefox has a version with no a11y support and Chrome has stated that they
will not ship their version for now.


> and we have agreed in the past that this API will provide the minimum
> level of accessibility support that needs to be in the Level 1 spec. Of
> course, we should continue working on Hit Region implementations and
> coordinate feedback, I just don't think that discussion is precluded on
> bringing it to the Level 1 spec.
>

Yes, we keep pushing on these APIs but I don't think we will come to a
conclusion soon (It's been over 6 months now).


> *From:* Rik Cabanier [mailto:cabanier@gmail.com]
> *Sent:* Friday, February 14, 2014 11:20 AM
>
> *To:* Jay Munro
> *Cc:* Alexander Surkov; public-canvas-api@w3.org; Mark Sadecki
> *Subject:* Re: hit regions Firefox support update
>
>
>
>
>
>
>
> On Fri, Feb 14, 2014 at 10:41 AM, Jay Munro <jaymunro@microsoft.com>
> wrote:
>
>  We've already removed all the at risk features with the exception of drawFocusIfNeeded
> , which was agreed upon in the A11y subgroup.
>
>
>
> We'll have to bring it back if we want a11y to work in canvas :-(
>
>
>
>  *From:* Rik Cabanier [mailto:cabanier@gmail.com]
> *Sent:* Friday, February 14, 2014 10:15 AM
> *To:* Jay Munro
> *Cc:* Alexander Surkov; public-canvas-api@w3.org; Mark Sadecki
>
>
> *Subject:* Re: hit regions Firefox support update
>
>
>
>
>
>
>
> On Fri, Feb 14, 2014 at 9:40 AM, Jay Munro <jaymunro@microsoft.com> wrote:
>
> Do we have a 2nd implementation of hitRegions?
>
>
>
> We do not.
>
> They are listed as at-risk so we can still go to CR with them.
>
>
>
> We should probably update the at-risk list to state that *part* or all of
> hit regions might be removed.
>
>
>
>  *From:* Rik Cabanier [mailto:cabanier@gmail.com]
> *Sent:* Friday, February 14, 2014 9:33 AM
> *To:* Alexander Surkov
> *Cc:* public-canvas-api@w3.org; Mark Sadecki
> *Subject:* Re: hit regions Firefox support update
>
>
>
> I just requested that the patches are checked into firefox.
>
> If all goes well, this means that the upcoming nightly build will have
> basic support for hit regions.
>
>
>
> If people had earlier tests for drawFocusIfNeeded, they can simply update
> them as follows.
>
> old code:
>
>  ctx.drawFocusIfNeeded(element);
>
> new code:
>
>  ctx.drawFocusIfNeeded(element);
>
>  ctx.addHitRegion({control: element};
>
>
>
> Alex, how can we turns hit regions and focus rings on by default?
>
>
>
> On Thu, Feb 13, 2014 at 10:40 AM, Alexander Surkov <
> surkov.alexander@gmail.com> wrote:
>
> Hi. Here's an update of hit region implementation in Firefox in case if
> you're curious .
>
> This week we've got a prototype of hit regions which can be used to change
> accessible boundaries. The work hasn't been landed into Firefox Nightly yet
> but there's a try build [2].
>
> There's no plans to continue the work on drawFocusIfNeeded to fit it for
> accessible boundaries setting since hit regions looks promising. It's worth
> to notice though that drawFocusIfNeeded (used to draw the focus) is part of
> Firefox and there's no actions to undo this.
>
>
>
> You can follow hit regions work by watching Mozilla bug [1].
>
> Thanks.
> Alexander.
>
>
> [1] https://bugzilla.mozilla.org/show_bug.cgi?id=966591
> [2] https://tbpl.mozilla.org/?tree=Try&rev=a0775f0bf042
>
>
>
>
>
>
>