RE: Updating our work statement

> The TF has not resolved the disagreement of the Co-Facilitators whether the ARIA related deliverables are, or are not, TF work items.

If the Co-Facilitators cannot decide I suggest you ask the Chairs of HTML WG and PF WG to make the decision for the TF.

/paulc

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

-----Original Message-----
From: 'Janina Sajka' [mailto:janina@rednote.net] 
Sent: Tuesday, March 03, 2015 8:54 AM
To: Paul Cotton
Cc: Charles McCathie Nevile (chaals@yandex-team.ru); 'HTML Accessibility Task Force'
Subject: Re: Updating our work statement

Paul Cotton writes:
> What is the status of updating the A11Y "work statement"?
> 
The TF has not resolved the disagreement of the Co-Facilitators whether the ARIA related deliverables are, or are not, TF work items.

The list of deliverables is to be pulled from the WS and separately published so that we can update the deliverables list without reauthorizing the WS.
http://lists.w3.org/Archives/Public/public-html-a11y/2015Feb/0053.html

The WS is otherwise unchanged.

I will be proposing an amendment to the Consensus Policy to allow for concurrent CfCs, rather than sequential CfCs, as heretofore. Expect that email this week to TF, PF, and HTML-Admin.

Janina

> /paulc
> 
> PS:  This thread started at 
> http://lists.w3.org/Archives/Public/public-html-a11y/2015Jan/0050.html
> 
> Paul Cotton, Microsoft Canada
> 17 Eleanor Drive, Ottawa, Ontario K2E 6A3
> Tel: (425) 705-9596 Fax: (425) 936-7329
> 
> 
> -----Original Message-----
> From: Léonie Watson [mailto:lwatson@paciellogroup.com]
> Sent: Tuesday, February 03, 2015 3:07 AM
> To: 'Liam R E Quin'; 'Shane McCarron'
> Cc: 'Janina Sajka'; 'HTML Accessibility Task Force'
> Subject: RE: Updating our work statement
> 
> > From: Liam R E Quin [mailto:liam@w3.org]
> > Sent: 03 February 2015 04:24
> > Is the wiki OK for *reading* from an accessibility point of view?
> > 
> 
> Wiki content tends to be basic, so providing all the usual good things happen (headings, link text, clear language etc.) it should be usable for most people. More specifically it's no bother (editing or consuming) with a screen reader.
> 
> Léonie.
> 
> 
> --
> Senior Accessibility Engineer, TPG
> @LeonieWatson @PacielloGroup
> 
> 
> 

-- 

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, 3 March 2015 19:40:56 UTC