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

Re: FW: Overview of testing in view of CR exit

From: Janina Sajka <janina@rednote.net>
Date: Tue, 9 Jul 2013 17:21:43 -0400
To: Paul Cotton <Paul.Cotton@microsoft.com>
Cc: "public-html-a11y@w3.org" <public-html-a11y@w3.org>
Message-ID: <20130709212143.GA7901@concerto.rednote.net>
Thanks, Paul, for the pointer.

I would want Rich participating in our TF review re testing canvas. I'll
ask his availability during the PF call Wednesday and report back
whether we can look at it during Thursday's TF call.


Janina

Paul Cotton writes:
> Please note that the Canvas editorial team has provided the HTML WG with a document this describes the level of interoperability of the Canvas features.  See below and:
> http://lists.w3.org/Archives/Public/public-html/2013Jul/0000.html 
> 
> I will join the A11Y TF meeting this week if the TF wants to discuss this document.
> 
> /paulc
> 
> Paul Cotton, Microsoft Canada
> 17 Eleanor Drive, Ottawa, Ontario K2E 6A3
> Tel: (425) 705-9596 Fax: (425) 936-7329
> 
> 
> -----Original Message-----
> From: Paul Cotton [mailto:Paul.Cotton@microsoft.com] 
> Sent: Wednesday, July 03, 2013 12:30 PM
> To: HTML WG (public-html@w3.org)
> Cc: Eliot Graff; Rik Cabanier (cabanier@adobe.com); Jay Munro; Tom Wiltzius; Robin Berjon (robin@w3.org)
> Subject: RE: Overview of testing in view of CR exit
> 
> > I've made a pass over the ToC to reflect the notions we had about what is considered stable on its own (as per exit criteria), what requires testing, and in the latter set what has implementations and/or tests 
> 
> The Canvas editors have prepared a document that does this for the HTML Canvas 2D Context CR specification [1].
> 
> See:
> 
>      http://dev.w3.org/html5/misc/canvas-implementation.html
> 
> Comments are welcome on this document.
> 
> After a suitable initial comment period the Chairs plan to run a CfC on this document as we have for the main HTML5 specification [2].
> 
> /paulc
> HTML WG co-chair
> 
> [1] http://www.w3.org/TR/2012/CR-2dcontext-20121217/ 
> [2] http://lists.w3.org/Archives/Public/public-html-admin/2013Jun/0033.html 
> 
> Paul Cotton, Microsoft Canada
> 17 Eleanor Drive, Ottawa, Ontario K2E 6A3
> Tel: (425) 705-9596 Fax: (425) 936-7329
> 
> 
> -----Original Message-----
> From: Robin Berjon [mailto:robin@w3.org] 
> Sent: Tuesday, May 14, 2013 10:39 AM
> To: HTML WG (public-html@w3.org)
> Subject: Overview of testing in view of CR exit
> 
> Hi,
> 
> based on the discussion we had at the face to face, I've made a pass over the ToC to reflect the notions we had about what is considered stable on its own (as per exit criteria), what requires testing, and in the latter set what has implementations and/or tests (I took a conservative approach to flagging that and will be refining it to add more).
> 
> This provides the basic information from which to start planning the CR exit. All the parts that are flagged as needing testing but not having tests will need to have tests written, and once we have tests for all of them they will need to be run through two implementations to produce an implementation report.
> 
> See:
> 
>      http://www.w3.org/html/wg/tests-cr-exit.html
> 
> Comments welcome,
> 
> --
> Robin Berjon - http://berjon.com/ - @robinberjon
> 
> 
> 
> 
> 
> 

-- 

Janina Sajka,	Phone:	+1.443.300.2200
			sip:janina@asterisk.rednote.net
		Email:	janina@rednote.net

Linux Foundation Fellow
Executive Chair, Accessibility Workgroup:	http://a11y.org

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Chair,	Protocols & Formats	http://www.w3.org/wai/pf
	Indie UI			http://www.w3.org/WAI/IndieUI/
Received on Tuesday, 9 July 2013 21:22:07 UTC

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