W3C logoWeb Accessibility initiative

WAI: Strategies, guidelines, resources to make the Web accessible to people with disabilities

HTML Accessibility Task Force Work Statement

Objectives

The objectives of the HTML Accessibility Task Force are:

Scope of Work

The HTML Accessibility TF is a joint task force of the HTML Working Group (HTML WG) and the Protocols and Formats Working Group (PFWG). It operates under both the HTML WG charter and the PFWG charter.

The Task Force performs the following types of work in regards to accessibility in HTML5:

Review existing features
Periodically review HTML specifications, especially during critical stages in the specification's lifecycle, to identify issues that may impact the accessibility of implementations.
Develop new features
Propose and develop new accessibility features for HTML through extension specifications
Propose solutions to identified issues
Review issues raised against HTML5 and any related specifications and will propose solutions to issues which have an impact on accessibility
Provide guidance to the HTML Working Group
Respond to requests from the HTML Working Group to provide expert feedback on accessibility

Approach

The HTML Accessibility Task Force will provide a forum for identification and discussion of accessibility issues in HTML.

The primary tool for providing feedback to the HTML Working Group is Bugzilla. The Task Force will monitor new issues raised against HTML5 and related specifications and provide feedback on those that impact accessibility. The Task Force may also file new bugs and propose solutions to existing bugs. Issues identified as being relevant to the Task Force are tracked in Bugzilla and tagged with the keyword "a11ytf"

The Task Force may propose changes to specifications, or propose and develop extension specifications. Any such specifications must be approved by both HTML and PF Working Groups, and will be considered as publications of the HTML Working Group for purposes of W3C Publication. Members of either Working Group who have substantive comments on or objections to Task Force publications are expected to raise them in the context of the Task Force.

Communication

HTML Accessibility Task Force communications and discussions are visible to the public. The primary means of communication within the task force are the W3C mailing list, public-html-a11y (archive).

Additionally, the Task Force may work through

To enable the group to work with the HTML and PF Working Groups: Updates and feedback will be provided HTML WG and PFWG teleconferences, as appropriate. These liaisons are primarily the responsibility of the Task Force Facilitators.

Members of the public who are not covered by the W3C Patent Policy (see Participation) may send input to the public-html-a11y mailing list. Messages should clearly indicate the deliverable to which they are related and only address issues that are relevant to the work of the Task Force. public-html-a11y is a moderated mailing list. Messages from non-participants may not be processed for 48 hours or more.

Participation

Any member of the HTML Working Group may participate in the HTML Accessibility Task Force. Members of the PF Working Group are also eligible to participate, providing they also become a member of the HTML Working Group and accept the W3C Patent Policy with respect to that group.

Participants should expect to dedicate 3 to 4 hours per week for Task Force work, including:

Participants may also join sub-groups that take on specific assignments. Currently active sub-groups are listed on the Task Force wiki.

If you are interested in becoming a participant of the HTML Accessibility Task Force or have any questions regarding its work, please contact Liam Quin.

Current Work

The following areas are under active development by the HTML Accessibility Task Force:

Using WAI-ARIA in HTML
Edited by Steve Faulkner, Hans Hillen and David McDonald. Work on this document also takes place in the HTML Working Group
HTML Accessibility API Mapping
Edited by Steven Faulkner, Jason Kiss and Alexander Surkov. Work on this document also takes place in the PF Working Group
HTML5: Techniques for providing useful text alternatives
This work led be Liam Quin and Shane McCarron aims to update the relevant parts of the HTML specification.
Keyboard access, Focus management
This work led by Charles McCathie Nevile may produce extension specifications and recommended changes to the HTML specification
Transcripts
This work led by John Foliot may produce extension specifications and recommended changes to the HTML specification
Tab-Panels
This work led by Brian Kardell, Léonie Watson and Steve Faulkner may produce extension specifications and recommended changes to the HTML specification
Footnotes
This work led by David McDonald may produce extension specifications and recommended changes to the HTML specification

If you want to propose a new item, please begin by adding it to the HTML wishlist page on our wiki, or volunteering through the mailing list to lead work on an item there not currently under active development

Facilitation

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

Facilitators:
Charles McCathieNevile, Yandex
Janina Sajka, Invited Expert
HTML Accessibility Task Force Staff Contact:
Liam Quin
HTML WG Staff Contact:
Michael Smith
PFWG Staff Contact:
Michael Cooper

Patent Policy

The HTML Accessibility Task Force is part of the HTML Working Group and PF Working Group Charter. It operates under the HTML Working Group Patent Policy.