Re: 48-Hour Call for Consensus (CfC): Publish heartbeat of "Using ARIA in HTML"

Colleagues:

The CfC below resulted in several email responses with suggested edits.
However, each commenter noted their suggested edits should not delay
this heartbeat. Therefore, this CfC is agreed by both the HTML-A11Y Task
Force and by the PFWG, and publication will now proceed.

Janina



Janina Sajka writes:
> Colleagues:
> 
> This is a Call for Consensus (CfC) to the Protocols and Formats Working
> Group (PFWG) approve publication of a heartbeat draft of "Using ARIA in
> HTML," as requested by the document editor in:
> 
> http://lists.w3.org/Archives/Public/public-html-a11y/2014Jun/0026.html
> 
> A concurrent CfC is ongoing in the HTML-A11Y Task Force.
> 
> Background Information
> 
> Thanks to Mark Sadecki for gathering the following relevant background
> data on this publication request.
> 
> Stabilized Heartbeat Draft:
> http://www.w3.org/WAI/PF/HTML/aria-in-html/2014-06-24-HB-draft.html
> 
> Bugs resolved since last publication:
> http://j.mp/1l2o6XI
> OR
> https://www.w3.org/Bugs/Public/buglist.cgi?bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=CLOSED&chfieldfrom=2013-10-03&chfieldto=2014-06-10&component=+Using%20ARIA%20in%20HTML&list_id=39139&product=HTML%20WG&query_format=advanced
> 
> Diff since last publication:
> http://www.w3.org/WAI/PF/HTML/aria-in-html/CH-aria-in-html-20140624.html
> 
> ## Notable Additions
> 
> * Fourth rule of ARIA use
>     * Do not use role="presentation" or aria-hidden="true" on a
>     * focusable element.
> * Fifth rule of ARIA use
>     * All interactive elements must have an accessible name.
>     * Clarifications to 2.11  Using ARIA role=application
> 	 
> ACTION TO TAKE
> 
> According to agreed PFWG 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 Close of Business Boston Time, Tuesday 17 June.
> 
> 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 Tuesday, 24 June 2014 11:53:10 UTC