W3C home > Mailing lists > Public > public-html-admin@w3.org > October 2014

PFWG Decision--CfC; Publish a heartbeat of the Text Alternatives document

From: <janina@rednote.net>
Date: Wed, 22 Oct 2014 14:53:54 -0400
To: W3C WAI Protocols & Formats <public-pfwg@w3.org>
Cc: HTML Accessibility Task Force <public-html-a11y@w3.org>, public-html-admin@w3.org
Message-ID: <20141022185354.GF1619@opera.rednote.net>
Colleagues:

No objections and several messages of support have been received to the
attached CfC. In addition the regular weekly PFWG teleconference has
recorded a resolution in support of this CfC at:

https://www.w3.org/2014/10/22-pf-minutes.html#item10


Therefore, this CfC is approved by PFWG.

Janina

Janina Sajka writes:
> Colleagues:
> 
> This is a Call for Consensus (CfC) to the Protocols and Formats Working
> Group to approve publication of an updated heartbeat draft of "HTML5:
> Techniques for providing useful text alternatives," according to the
> draft available at:
> 
> Tiny URL:
> http://tinyurl.com/kjvjqat
> 
> Direct URL:
> http://rawgit.com/w3c/alt-techniques/54c868254d49bac4ca1efa7d9907cc85bfa0a3cd/index.html
> 
> As discussed in the regular weekly HTML-A11Y Task Force teleconference
> of Thursday 16 October logged at:
> 
> http://www.w3.org/2014/10/16-html-a11y-minutes.html#item04
> 
> Two editorial corrections are anticipated by this Call for Consensus:
> 
> 1.)	An appropriate hyperlink in W3C web space will replace the place
> holder hyperlink, currently displaying as "XXXX," should this CfC pass
> and this heartbeat be published by W3C;
> 
> 2.)	The hyperlink referencing the HTML 5 specification will have its
> display text corrected to indicate the hyperlink points to the Proposed
> Recommendation version of the HTML 5 specification, and not the W3C Last
> Call version, as currently displayed.
> 
> In the interest of achieving publication of this heartbeat Working Draft
> ahead of the publication moratorium surrounding TPAC, a concurrent CfC
> is ongoing in the HTML-A11Y Task Force. HTML-WG process does not require
> a CfC for heartbeat publications.
> 	 
> ACTION TO TAKE
> 
> According to our agreed Consensus Procedures, this CfC is now open for
> objection, comment, as well as statements of support via email. Silence
> will be interpreted as support, though messages of support are certainly
> welcome.
> 
> If you object to this proposed action, or have comments concerning this
> proposal, please respond by replying on list to this message no later
> than 23:59 (Midnight) Boston Time on Tuesday 21 October.  As is
> customary, we will also entertain a resolution on this CfC during our
> regular weekly teleconference meeting this coming Wednesday.
> 
> Janina
> 
> 
> 
> 
> 
> -- 
> 
> 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/
> 
> -- 
> 
> 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/
> 

> Colleagues:
> 
> This is a Call for Consensus (CfC) to confirm the sufficiency and
> accuracy of guidance on the alternative text attribute for images as
> provided by the following two related HTML-WG documents. It is also a
> Call for Consensus regarding proposed next steps for each of these
> documents.
> 
> You will recall the relationship between these documents is that the
> first was initially created to elaborate criticisms against the
> sufficiency of alt guidance in the second. In other words, initially
> guidance in these two documents was different, and the two did not agree
> one with the other.
> 
> We believe that over the past few years these differences have been
> successfully resolved. This CfC tests this assertion. For the record we
> are requesting the HTML-A11Y Task Force confirm this understanding,
> or point out specific remaining insufficiencies.
> 
> 1.)	HTML5: Techniques for providing useful text alternatives
> 	http://rawgit.com/w3c/alt-techniques/master/index.html
> 
> This document was initially created to help remedy insufficiencies in
> early drafts of the HTML 5.0 specification. Over the past few years,
> guidance originally present in this document has been migrated to the
> HTML specification itself and removed from this document. However, it is
> believed that the remaining content in this document still provides
> valuable guidance to HTML authors.
> 
> Recent edits to this document can be seen in the W3C Bugzilla bugs shown
> at the following URI:
> 
> http://tinyurl.com/kjvj3bb
> 
> A permanent, though very long URI for these bugs is:
> 
> https://www.w3.org/Bugs/Public/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&component=CR%20alt%20techniques%20%28editor%3A%20Steven%20Faulkner%29&list_id=37965&product=HTML%20WG&query_format=advanced
> 
> QUESTION 1:	Does the Task Force
> 		a.)	Accept these identified changes to this document
> 		b.) Recommend that work on this document be terminated; and
> 		c.) Support publication of this document by the HTML-WG
> 		    as a W3C Note.
> 
> 2.)	HTML 5.0 Sec. 4.7.1.1 Requirements for providing text to act as
> 	an alternative for images
> 	http://www.w3.org/html/wg/drafts/html/master/embedded-content.html#alt
> 
> As noted above there have been significant edits to this section of the
> HTML 5.0 specification in order that this specification might best
> reflect current consensus guidance regarding alt. These changes are
> documented by the following W3C Bugzilla bugs:
> 
> {Insert Bug List Here}
> 
> QUESTION 2:	Does the Task Force:
> 		a.)	Accept these identified changes to this specification;
> 		b.) Recommend that work on this specification be terminated; and
> 		c.) Support publication of this section of this
> 		    specification  by the HTML-WG as part of W3C HTML 5.0.
> 
> ACTION TO TAKE
> 
> According to agreed HTML-A11Y Task Force Consensus Procedures [1], this
> CfC is now open for objection, comment, as well as statements of support
> via email. Silence will be interpreted as support, though messages of
> support are certainly welcome.
> 
> If you have objections to any part of the above two questions, or any
> comments concerning the proposed next steps for either of the above
> documents, please respond by replying on list to this message no later
> than midnight Boston Time, Wednesday 4 June.
> 
> Janina on behalf of the Task Force Facilitators
> 
> [1] http://www.w3.org/WAI/PF/HTML/consensus-procedures
> 
> -- 
> 
> 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/
> 


-- 

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 Wednesday, 22 October 2014 18:54:16 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:37:36 UTC