View source for Fast-work-statement

We can start to draft FAST work statement here:
------------

'''DRAFT FAST Task Force (FAST TF) Work Statement'''

The Framework for Accessibility in the Specification of Technologies (FAST) Task Force (FAST TF) is a task force of the Accessible Platform Architectures (APA) Working Group. It assists this Working Group with the work identified below.

'''Status'''

The FAST Task Force is under exploration by the APA Working Group. The Task Force home page contains information about the proposed operation and resources of the group.

'''Objective'''

The objective of this TF is to develop the FAST to collect user and functional needs, develop guidance to meet those needs in technologies, and work with other groups to to develop this guidance for content developers.

The TF will also maintain the existing FAST Checklist, to support the horizontal review process.

'''Scope of Work'''

The FAST TF is to describe the features that web technologies should provide in order to ensure it is possible to create, communicate, transport etc., content that is accessible to users with disabilities. The full framework references an analysis of user requirements; describes how technologies, content authoring, and user agents work together to meet these needs; and provides comprehensive guidance to technology developers and other stakeholders. 

This Task Force will develop checklist extracts providing high-level information to aid in self-review of technologies and documents. Specification developers can use these to help ensure the technology will address issues likely to be raised during horizontal review.

'''Approach'''

The Task Force will work within the APA Working Group to develop and refine the FAST checklist. It will coordinate with other WAI and W3C groups, as appropriate.

'''Communication'''

FAST communications and discussions must be visible to the public. The task force home page details communication mechanisms in use. The task force will:

* Support synchronous (e.g., teleconferences, face-to-face meetings) and asynchronous (e.g., mailing list discussions, issue trackers, wiki, surveys, etc.) methods of communication;
* Use the procedures of the APA Working Group Decision Policy to make decisions;
* Provide updates and feedback to APA Working Group teleconferences, as appropriate. These liaisons are primarily the responsibility of the FAST Task Force Facilitators;
* Maintain information resulting from its activities (deliverables, participants, face-to-face meetings, teleconferences, etc.) on the FAST Task Force home page.
* Review minutes of meetings for mistakes and comment by email on any significant mistakes that need correction.

'''Participation'''

Any participant in the APA Working Group may participate in the FAST Task Force. Participants should expect to dedicate 3 to 4 hours per week for FAST Task Force work, which is considered part of the overall work commitment to the APA Working Group:
 
* Remain current on the FAST Task Force mailing list and respond to postings in a timely manner;
* Provide feedback to editors of specifications via email or by filing GitHub issues;
* Participate in weekly FAST Task Force teleconferences, or send regrets to the FAST Task Force mailing list. Participants are expected to attend at least 60% of the meetings.
* Participants may also join FAST Task Force sub-groups. Sub-groups take on specific assignments for the FAST Task Force.

'''Facilitation'''

Staff contacts from the APA Working Group oversee attention to W3C Process with respect to the chartered requirements of the Working Group. The Facilitators set agenda, lead meetings, determine consensus and are the primary liaison to the APA Working Group.

Facilitators: Fredrik Fischer
Staff Contact: Ruoxi Ran

'''Patent Policy'''

This Task Force is part of the APA Working Group Charter, which operates under the W3C Patent Policy (Version of 15 September 2020). W3C maintains a public list of any patent disclosures made in connection with the deliverables of the APA Working Group.