RE: CfC: Approve overview of Canvas testing in view of permissive CR exit criteria

Hi Sam,

this wiki has the list of at-risk features that we composed last year: http://www.w3.org/html/wg/wiki/HTML5.0AtRiskFeatures

Since then, support for setLineDash has been implemented by various browsers so this can be removed.

One of the features we missed was support for focus rings. 
I've been working with various implementors and I'm hopeful that it will land shortly. If not, they will be put on the at-risk list too.
(If someone from WebKit wants to implement this, I filed https://bugs.webkit.org/show_bug.cgi?id=122177)

Rik
________________________________________
From: Sam Ruby [rubys@intertwingly.net]
Sent: Tuesday, October 01, 2013 1:51 PM
To: public-html-admin@w3.org
Cc: HTML Accessibility Task Force
Subject: Re: CfC: Approve overview of Canvas testing in view of permissive  CR exit criteria

Current status.

Original call:
http://lists.w3.org/Archives/Public/public-html-admin/2013Jun/0033.html

In September, we received the following feedback, containing three points:

http://lists.w3.org/Archives/Public/public-html-admin/2013Sep/0013.html

One point seems unrelated to the specification in question, leading to
the following query which never received a response:

http://lists.w3.org/Archives/Public/public-html-admin/2013Sep/0038.html

The remaining two questions relate to the implementation status of
features the Canvas editors consider to be at Risk.  The editor's list
of features they consider at risk didn't match the list of features that
were indicated as at risk at the time the Last Call document was
published, and this needs to be rectified.

Additionally, there seems to be honest disagreement as to what features
are at Risk.

One thing that there is agreement on is that the current document
doesn't color items at risk correctly, and that this should be corrected.

tl;dr: we need the Canvas editors to work with implementors and the A11y
TF to come to consensus as to what features are at risk; and then to
update BOTH the specification and the testing overview document to match.

- Sam Ruby

On 07/16/2013 02:26 PM, Paul Cotton wrote:
> This is a Call for Consensus (CfC) to approve the following document
> that indicates which parts of the Canvas  specification can be
> considered interoperable as per the permissive CR exit criteria [1].
> The items subject to this CfC are marked "Considered interoperable" and
> color coded in green in the document:
>
> http://dev.w3.org/html5/misc/canvas-implementation.html
>
> Silence will be taken to mean there is no objection, but positive
> responses are encouraged.   Objections should be made to specific
> entries in the document.  Objections of the form "features in Section
> 4.a LineWidth are not currently interoperable" MUST be accompanied with
> specific evidence of non-interoperability, otherwise such objections
> will not be accepted by the Chairs.
>
> If there are no objections by 16 Aug 2013, this resolution will carry.
>
> /paulc
>
> HTML WG co-chair
>
> [1]
> http://dev.w3.org/html5/decision-policy/public-permissive-exit-criteria.html
>
> Paul Cotton, Microsoft Canada
>
> 17 Eleanor Drive, Ottawa, Ontario K2E 6A3
>
> Tel: (425) 705-9596 Fax: (425) 936-7329
>

Received on Wednesday, 2 October 2013 04:38:45 UTC