RE: HTML Canvas 2D Context progress is stalled; time to drop features? (resending)

Adrian,

I appreciate Microsoft's position about not commenting on future product
releases. That said, the accessibility space involves an intricate set of
dependencies involving assistive technologies, API mappings, special
accessibility test tools, and a commitment from engineers to an area where
many authors see accessibility enablement as a burden. We wrestle with this
inside and outside our companies every day.

When companies don't operate in a more open way it creates barriers to
access. When I commit my time to work with another browser vendor in this
space it is expected that both parties have the intent of implementing the
work. Otherwise, involvement in the creation of a specification is
misleading and brings into question the commitment of other contributor's
time on the effort.

The canvas spec. was pulled back from forward advancement a while ago
because Microsoft objected to the content of the accessibility features.
Changes were made with your team to address those concerns and the result
is no implementation by the party that objected. If Microsoft felt so
strongly about it that it would want to pull back the efforts to make
changes there is an expectation that your company would implement those
changes that you worked so hard to put in place.

Two implementations are required to push a spec. over the goal line. I am
asking for your help.

Best,

Rich


Rich Schwerdtfeger



From: Adrian Bateman <adrianba@microsoft.com>
To: Richard Schwerdtfeger/Austin/IBM@IBMUS, Paul Cotton
            <Paul.Cotton@microsoft.com>
Cc: Judy Brewer <jbrewer@w3.org>, Mark Sadecki
            <mark.sadecki@gmail.com>, "public-canvas-api@w3.org"
            <public-canvas-api@w3.org>, Sam Ruby <rubys@intertwingly.net>
Date: 02/11/2015 09:23 PM
Subject: RE: HTML Canvas 2D Context progress is stalled; time to drop
            features? (resending)



Microsoft engineers worked as spec editors meaning that they implemented
the consensus position of the working group into the specs. Yes, they were
also involved in the engineering discussions, didn’t object and were part
of that consensus, but those are two different things.

We have no timeframe for when we might implement these features. They are
under consideration but we do not have engineers working on them and I
don’t know when we might. You can track the status of Canvas focus ring
here: https://status.modern.ie/canvasfocusring


From: Richard Schwerdtfeger [mailto:schwer@us.ibm.com]
Sent: Wednesday, February 11, 2015 1:32 PM
To: Paul Cotton
Cc: Judy Brewer; Mark Sadecki; public-canvas-api@w3.org; Sam Ruby; Richard
Schwerdtfeger
Subject: RE: HTML Canvas 2D Context progress is stalled; time to drop
features? (resending)



Paul,

We had advanced to CR with two Microsoft engineers working as spec. editors
meaning they would have approved the contents of the spec. I think it is
valid to ask what is Microsoft's plan to implement the canvas accessibility
features in your browser.

Is Microsoft planning to implement those features you helped edit into the
spec. and sign off on? For Firefox we are very close to having hit region
accessibility support done.

Rich


Rich Schwerdtfeger

Inactive hide details for Richard Schwerdtfeger---02/11/2015 02:49:57
PM---I worked with Steve Faulkner and he has given this dRichard
Schwerdtfeger---02/11/2015 02:49:57 PM---I worked with Steve Faulkner and
he has given this defect to another person at Google working on acc

From: Richard Schwerdtfeger/Austin/IBM@IBMUS
To: Paul Cotton <Paul.Cotton@microsoft.com>
Cc: Judy Brewer <jbrewer@w3.org>, Mark Sadecki <mark.sadecki@gmail.com>, "
public-canvas-api@w3.org" <public-canvas-api@w3.org>, Sam Ruby <
rubys@intertwingly.net>
Date: 02/11/2015 02:49 PM
Subject: RE: HTML Canvas 2D Context progress is stalled; time to drop
features? (resending)




I worked with Steve Faulkner and he has given this defect to another person
at Google working on accessibility defects at this moment.


Rich Schwerdtfeger

Inactive hide details for Paul Cotton ---02/05/2015 01:31:23 PM---> I will
follow up with browser vendors In your original emaiPaul Cotton
---02/05/2015 01:31:23 PM---> I will follow up with browser vendors In your
original email you implied there was more than one b

From: Paul Cotton <Paul.Cotton@microsoft.com>
To: Mark Sadecki <mark.sadecki@gmail.com>
Cc: Richard Schwerdtfeger/Austin/IBM@IBMUS, Sam Ruby <
rubys@intertwingly.net>, "public-canvas-api@w3.org" <
public-canvas-api@w3.org>, Judy Brewer <jbrewer@w3.org>
Date: 02/05/2015 01:31 PM
Subject: RE: HTML Canvas 2D Context progress is stalled; time to drop
features? (resending)




> I will follow up with browser vendors

In your original email you implied there was more than one browser vendor
to contact.  Can you provide a status report on any other browser vendor
blocking bugs?

Paul Cotton, Microsoft Canada
17 Eleanor Drive, Ottawa, Ontario K2E 6A3
Tel: (425) 705-9596 Fax: (425) 936-7329

From: Mark Sadecki [mailto:mark.sadecki@gmail.com]
Sent: Thursday, February 05, 2015 10:59 AM
To: Paul Cotton
Cc: Richard Schwerdtfeger; Sam Ruby; public-canvas-api@w3.org; Judy Brewer
Subject: Re: HTML Canvas 2D Context progress is stalled; time to drop
features? (resending)

There is currently one bug open in Chrome on drawFocusIfNeeded() [1]. There
has been no movement since it was opened on 2014-10-14 I left a comment
requesting an update today [2]

[1] https://code.google.com/p/chromium/issues/detail?id=425149

[2] https://code.google.com/p/chromium/issues/detail?id=425149#c2

I will send dominic a follow-up email as well.
Mark

On Wed, Jan 28, 2015 at 5:44 PM, Paul Cotton <Paul.Cotton@microsoft.com>
wrote:
Can you please add your browser contacts directly to this thread so the
progress is clear?

Sent from my Windows Phone


From: Mark Sadecki
Sent: 28/01/2015 5:17 PM
To: Richard Schwerdtfeger
Cc: Sam Ruby; public-canvas-api@w3.org; Paul Cotton; Judy Brewer
Subject: Re: HTML Canvas 2D Context progress is stalled; time to drop
features? (resending)

I will follow up with browser vendors with regards to any defects on
drawFocusIfNeeded()
Mark

On Wed, Jan 28, 2015 at 4:45 PM, Richard Schwerdtfeger <schwer@us.ibm.com>
wrote:


all the tests for drawFocusIfNeeded are done.

addHitRegion is the implementations have too long to go whereas
drawFocusIfNeeded has some minor bugs that need to be fixed in the
browsers.

Mark has agreed to finish these getting those bugs fixed with the browser
manufacturers.

Rich Schwerdtfeger

Inactive hide details for Sam Ruby ---01/28/2015 02:36:15 PM---Background:
HTML Canvas 2D Context is in Candidate RecommendatioSam Ruby ---01/28/2015
02:36:15 PM---Background: HTML Canvas 2D Context is in Candidate
Recommendation:    http://www.w3.org/TR/2dcontext


From: Sam Ruby <rubys@intertwingly.net>
To: "public-canvas-api@w3.org" <public-canvas-api@w3.org>
Date: 01/28/2015 02:36 PM
Subject: HTML Canvas 2D Context progress is stalled; time to drop features?





Background: HTML Canvas 2D Context is in Candidate Recommendation:

http://www.w3.org/TR/2dcontext/


The plan, as of September 2014, was to have "All tests will be written
and run by the end of the month":


https://lists.w3.org/Archives/Public/public-canvas-api/2014JulSep/0033.html


The status, as of January 2015, is that a number of tests have yet to be
written (search for TODO):

 https://www.w3.org/wiki/HTML/Canvas_Task_Force/CR-Test


Additionally, many of the tests that are currently written are failing.

After discussions with my co-chair (Paul Cotton) and the W3C domain lead
(PLH), the time has come to recommend that features for which we don't
have passing tests be deferred to HTML Canvas level 2.

I encourage everybody who would like to propose an alternate plan do so
now.

- Sam Ruby