W3C home > Mailing lists > Public > public-html-a11y@w3.org > September 2013

Re: update to at risk features in Canvas

From: Mark Sadecki <mark@w3.org>
Date: Thu, 26 Sep 2013 14:54:53 -0400
Message-ID: <524482FD.7060200@w3.org>
To: Richard Schwerdtfeger <schwer@us.ibm.com>
CC: dbolter@mozilla.com, Dominic Mazzoni <dmazzoni@chromium.org>, franko@microsoft.com, Rik Cabanier <cabanier@gmail.com>, HTML A11Y TF Public <public-html-a11y@w3.org>, Janina Sajka <janina@rednote.net>
On 9/26/13 12:50 PM, Richard Schwerdtfeger wrote:
> 
> Mark,
> 
> If that requires 2 implementations by the end of this year I cannot
> guarantee it.

We agreed to have a "clear path to implementation" for Custom focus rings by the end of the year, with testable implementations by end of Q1 2014.  Do you guys think this is achievable?

> 
> 1. They won't allow Safari to count as a second implementation and I have
> not heard of any webkit plans so even if they do implement it, it won't
> matter.
> 2. IE won't share anything that they are doing
> 3. Firefox does not have a person assigned yet.

Having a person assigned would count toward having a "clear path to implemenation" as long as there is a paper trail of progress being made.

In your opinion, does dropping support for Dashes[1], text metrics [2] or ellipse() [3] have a negative impact on accessibility.

We talked about pushing support for Path (or an alternative) to the next version of Canvas, but what about Hit Regions [4]?

[1] http://www.w3.org/html/wg/drafts/2dcontext/html5_canvas/#dom-context-2d-setlinedash
[2] http://www.w3.org/html/wg/drafts/2dcontext/html5_canvas/#textmetrics
[3] http://www.w3.org/html/wg/drafts/2dcontext/html5_canvas/#dom-context-2d-ellipse
[4] http://www.w3.org/html/wg/drafts/2dcontext/html5_canvas/#hit-regions

Best,

Mark

> 
> At this point we have drawSystemFocusRing fully implemented in Chrome
> Canary only. If Sam pushes canvas out the door without at least this then
> low vision users will be without access to canvas. I have done everything I
> can thus far to try to get these two implementations moving. W3C should not
> ship the canvas spec with out some means to provide location information.
> 
> Regards,
> 
> Rich
> 
> 
> Rich Schwerdtfeger
> 
> 
> 
> From:	Mark Sadecki <mark@w3.org>
> To:	Richard Schwerdtfeger/Austin/IBM@IBMUS,
> Date:	09/26/2013 11:36 AM
> Subject:	update to at risk features in Canvas
> 
> 
> 
> Hi Rich,
> 
> In the HTML WG telecon today, we became aware that the document we were
> asked to review regarding what was at risk in Canvas was not entirely
> accurate and that there are a couple of new sections that are also at risk.
> Could you review this and let me know if we should be concerned with any of
> these being dropped:
> 
> * Path object in Canvas
> * Hit regions
> * Dashes
> * Text metrics
> * Ellipse
> 
> http://www.w3.org/html/wg/wiki/HTML5.0AtRiskFeatures
> 
> We have asked to extend the time given to November to provide feedback.
> They are considering that request.
> 
> We also agreed to the following:
> 
> RubyS: the plan would then be to mark custom focus ring to be at risk at
> this time, seek plans in 4Q 2013 for implementations in 1Q2014.  If this
> function isn't implemented in 1Q2014, it will be removed at that time.
> 
> Please let me know if you have any questions regarding any of this.  Enjoy
> your vacation!
> 
> Mark
> 
> --
> Mark Sadecki
> Web Accessibility Engineer
> World Wide Web Consortium, Web Accessibility Initiative
> Telephone: +1.617.715.4017
> Email: mark@w3.org
> Web: http://w3.org/People/mark
> 
> 


-- 
Mark Sadecki
Web Accessibility Engineer
World Wide Web Consortium, Web Accessibility Initiative
Telephone: +1.617.715.4017
Email: mark@w3.org
Web: http://w3.org/People/mark
Received on Thursday, 26 September 2013 18:54:59 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:05:35 UTC