Proposed Change to HTML-A11Y TF Consensus Procedures


This is a proposal to amend the HTML-A11Y Task Force's current Consensus

PROPOSAL: Amend the TF's Consensus Procedures to expressly allow the TF
Co-Facilitators to request that PF and HTML-WG chairs conduct their working group Calls for Consensus on Task
Force consensus questions concurrently with the TF's CfC.

EXPLANATION: Our practice to date has been to conduct a CfC in the TF,
await a formal TF decision, then follow with requests to PF and HTML-WG
for working group CfCs on the same question. At a minimum this process
requires two weeks, and has frequently taken longer.

By not requiring concurrent consensus calls, the TF would remain free to
use the procedure as a tool for clarifying the Task Force's position.

However, where the TF Co-Facilitators believe that TF consensus is
evident, allowing concurrent consensus calls  would streamline the
process for agreeing to a course of action. 

EXAMPLE: A concurrent CfC might be conducted for the FPWD publication of
a joint deliverable, allowing publication to move forward in as little
as one week, as opposed to a minimum of two weeks.

Next Steps: Please respond on this thread with any comments. The TF will
also take up this agendum in a forthcoming regular teleconference.



Janina Sajka,	Phone:	+1.443.300.2200

Linux Foundation Fellow
Executive Chair, Accessibility Workgroup:

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Chair,	Protocols & Formats
	Indie UI

Received on Monday, 9 March 2015 17:07:43 UTC