HTML Accessibility Task Force Work Statement
The objective of the HTML Accessibility TF is to identify the accessibility requirements and manage the progress of accessibility solutions in HTML5, while expanding participation and fostering collaboration between experts in HTML and Web Accessibility as a means to meet the requirements and goals of each group and to increase mutual understanding. This work is done as part of an effort to ensure accessibility of the W3C's Open Web Platform.
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). Accordingly, the HTML Accessibility TF operates under both the HTML WG charter and the PFWG charter.
The HTML Accessibility TF performs the following types of work in regards to accessibility in HTML5:
- review existing features;
- develop new features;
- propose solutions to identified issues;
- provide guidance to the HTML WG.
The HTML Accessibility TF will periodically review the HTML5 specification, especially during critical stages in the specification's lifecycle, in an attempt to identify issues that may impact the accessibility of implementations of the specification.
The HTML Accessibility TF will look for opportunities to improve the accessibility of the web by proposing and developing new features in the current HTML specification under development or through the publication of extension specifications.
The HTML Accessibility TF will review issues raised against the HTML5 and any related specifications and will propose solutions to issues which have an impact on accessibility. The HTML Accessibility TF will follow issues through to a resolution.
The HTML Accessibility TF will respond to requests from the HTML WG to provide expert feedback on accessibility related issues found in draft publications of the HTML5 specification and related extension specifications.
The HTML Accessibility TF will provide a forum for identification and discussion of accessibility issues in HTML5, such as, though not limited to, well integrated support for WAI-ARIA, accessibility of canvas content, and a robust set of tools for delivering alternative media in images, audio and video.
The primary tool for providing feedback to the HTML WG is Bugzilla. The HTML Accessibility TF will monitor new issues raised against HTML5 and related specifications and provide feedback on those that impact accessibility. The HTML Accessibility TF may also file new bugs and propose solutions to existing bugs.
Ideally, this collaborative process will result in edits to the HTML5 specification. The HTML Accessibility TF may create a proposal to change existing specification text to be processed in accordance with the HTML WG Decision Policy. Alternatively, the HTML Accessibility TF may propose and develop extension specifications. The HTML Accessibility TF will have decision authority over the contents of such extension specifications. An extension specification may be merged back into the baseline HTML5 specification if it meets the terms of Plan 2014 or may be published as an independent specification. Any such specifications must be approved by both Working Groups (WGs) and will be considered as publications of the HTML WG for purposes of W3C Publication. Members of either WG who have substantive comments on or objections to HTML Accessibility TF publications are expected to raise them in the context of the HTML Accessibility TF.
HTML Accessibility TF communications and discussions are visible to the public. The primary means of communication within the task force are:
- E-mail discussions taking place on the HTML Accessibility TF's W3C mailing list, public-html-a11y.
- Weekly (or less frequently, as needed) HTML Accessibility TF teleconferences with minutes distributed to HTML Accessibility TF mailing list (archive);
- Sub-group teleconferences with minutes distributed to HTML Accessibility TF mailing list;
- The HTML Accessibility TF Wiki.
- The HTML Accessibility TF may use Web-based surveys instead of email to poll group opinion.
In addition, 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 HTML Accessibility TF Facilitators.
- Issues identified as being relevant to the HTML Accessibility TF are tracked in Bugzilla and tagged with the keyword "a11ytf".
Members of the public who are not covered by the W3C Patent Policy (see Participation) can 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 HTML Accessibility TF. public-html-a11y is a moderated mailing list. Messages from non-participants may not be processed for 48 hours or more.
Any member of the HTML WG may participate in the HTML Accessibility TF. Members of the PFWG are also eligible to participate, providing they also become a member of the HTML WG and accept the W3C Patent Policy.
Participants should expect to dedicate 3 to 4 hours per week for HTML Accessibility TF work:
- Remain current on the HTML Accessibility TF mailing list and respond to postings in a timely manner;
- Provide feedback to editors of the HTML5 and any related extension specifications via email or by filing bugs;
- Participate in weekly HTML Accessibility TF teleconferences, or send regrets to the HTML Accessibility TF mailing list.
Participants may also join HTML Accessibility TF sub-groups. Sub-groups take on specific assignments for the HTML Accessibility TF. Currently active sub-groups are listed on the HTML Accessibility TF wiki.
If you are interested in becoming a participant of the HTML Accessibility TF or have any questions regarding its work, contact Liam Quin.
The following is a list of documents that are managed by the HTML Accessibility TF and jointly owned by the HTML WG and PFWG:
- Using WAI-ARIA in HTML - SteveF, Hans Hillen, DavidM editors
- HTML Accessibility API Mapping - SteveF, JasonK, Alex Surkov editors
- HTML5: Techniques for providing useful text alternatives - Liam, ShaneM eds
- Keyboard access, Focus management - Charles
- Transcripts - JohnF
- Tab-Panels Brian Kardell, Léonie, SteveF
- Footnotes - David McDonald
- If you want to propose a new item, please begin by adding it to the HTML wishlist page on our wiki: https://www.w3.org/WAI/PF/HTML/wiki/51wishlist
Staff contacts from the HTML WG and the PFWG oversee attention to W3C Process with respect to the chartered requirements of the respective WGs. The Facilitators set agenda, lead meetings, determine consensus, and are the primary liaison to the WGs.
- Charles McCathieNevile, Yandex
- Janina Sajka, Invited Expert
- HTML Accessibility TF Staff Contact:
- Liam Quin
- HTML WG Staff Contact:
- Michael Smith
- PFWG Staff Contact:
- Michael Cooper
The HTML Accessibility TF is part of the HTML WG and PFWG Charter. It operates under the HTML WG Patent Policy.