RE: Accessibility Task Force

On Sep 16, 2009, at 3:50 PM, Janina Sajka wrote:

> If the above is correct and acceptable, I will take on the task of
> editing the Draft TF Work Statement to reflect this understanding  
> and to
> incorporate the 8 points promolgated by the HTML Co-Chairs. I expect a
> new draft would be available early next week, in time for approval  
> by PF
> (Wednesday) and HTML (Thursday).

Since this has not yet occurred I will try to move this item along.
 
There seems to be consensus on the following points:

a) there should be an joint accessibility task force,
b) to avoid re-chartering the PF WG, the task force will be created as a HTML WG task force,
c) anyone wanting to participate in the task force should first be a member of the HTML WG,
d) the task force SHOULD have one or more people that can do editing to facilitate making revisions to the HTML5 specification,
d) we should create this task force as soon as possible so that it can deliver results before HTML5 enters Last Call.

Here is a revised proposal that takes these possible consensus points into considerations:

Joint PF WG and HTML WG Accessibility Task Force:
 1. Any HTML WG member can join the Accessibility Task Force (opt in model).
 2. Any PF WG member that wants to join the Accessibility TF should first join the HTML WG (see item 1).
 3. Any member of the Accessibility TF MUST be a member of the HTML WG.
    Note: We may want to figure out how to permit TF members to avoid receiving HTML WG email. 
 4. The Accessibility TF will use a separate email list for TF discussions (email address TBD).
 5. The Accessibility TF will have a separate weekly meeting slot (day and time TBD).
 6. The Accessibility TF will not make final decisions about its scope, work plan or work products. These decisions will be made by HTML WG in cooperation with the PF WG.
    Note: The HTML WG might decide at some future point in time to delegate more responsibility to the Accessibility TF.
 7. Facilitator(s) of the Accessibility TF will be selected by the HTML WG chairs and PF WG chairs.
 8. The Accessibility TF facilitator(s) will report back to the HTML and PF WGs on the work of the TF on a regular basis.
 9. The first task of the Accessibility TF will be to draft its scope and initial work plan.

/paulc

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

Received on Tuesday, 22 September 2009 22:39:27 UTC