diff --git a/pages/about/groups/agwg.md b/pages/about/groups/agwg.md index 368ba87c3fb..0fa56293081 100644 --- a/pages/about/groups/agwg.md +++ b/pages/about/groups/agwg.md @@ -1,9 +1,13 @@ --- -title: Accessibility Guidelines Working Group (AGWG) -nav_title: 'AGWG: Accessibility Guidelines WG' +title: Accessibility Guidelines Working Group +nav_title: 'Accessibility Guidelines WG' lang: en permalink: /about/groups/agwg/ ref: /about/groups/agwg/ +redirect_from: + - /about/groups/agwg/participate/ + - /about/groups/agwg/communication/ + - /about/groups/agwg/task-forces/ github: label: wai-groups --- @@ -12,9 +16,7 @@ github: {% include box.html type="start" title="Summary" class="" %} {:/} -The mission of the Accessibility Guidelines Working Group is to develop specifications to support making implementations of web technologies accessible for people with disabilities, and to develop and maintain implementation support materials. - -Some information on this page is also shown on, and may be more current in, the automatically generated [Accessibility Guidelines Working Group page](https://www.w3.org/groups/wg/ag/). +Find out about the activities of the Accessibility Guidelines (AG) Working Group and how you can contribute to its mission. {::nomarkdown} {% include box.html type="end" %} @@ -33,67 +35,89 @@ Some information on this page is also shown on, and may be more current in, the {% include_cached toc.html type="end" %} {:/} -## Announcements +## Mission + +The mission of the AG Working Group is to develop and maintain specifications for making web content accessible to people with disabilities, along with support materials for implementing the Web Content Accessibility Guidelines (WCAG). + +## Charter -No announcements at the moment. +To learn about the group’s focus, scope and deliverables, see the [AG Working Group Charter](https://www.w3.org/WAI/GL/charter). -## Current Work -The Working Group maintains a comprehensive list of [publications and current timelines](https://www.w3.org/WAI/GL/wiki/Timelines). +## Current work -The [Project Plan](https://www.w3.org/WAI/GL/wiki/Timelines) details intended timeline and milestones for this work. A [list of publications](https://www.w3.org/TR/tr-groups-all#tr_Web_Content_Accessibility_Guidelines_Working_Group) on the W3C Technical Reports page includes completed deliverables that are no longer worked on by the Working Group. +For details of the current work, see the [AG Working Group wiki](https://www.w3.org/WAI/GL/wiki/Main_Page). ### WCAG 3 -Work on W3C Accessibility Guidelines 3 takes place in many task forces and subgroups of the Working Group. Information about projects and timelines is available on the [WCAG 3 Project Plan](https://github.com/w3c/silver/wiki). +Work on developing WCAG 3 takes place in many task forces and subgroups of the AG Working Group. For information about the WCAG 3 timelines and publication plan, see [WCAG 3 Timeline](https://www.w3.org/WAI/GL/wiki/WCAG_3_Timeline). ### WCAG 2.2 -The Working Group is processing comments from wide review and preparing for Candidate Recommendation. Current work is shown in [WCAG issues](https://github.com/w3c/wcag/issues/). +The [WCAG 2.x Backlog Task Force](/about/groups/task-forces/wcag2x-backlog) maintains WCAG 2.x (WCAG versions 2.0, 2.1, and 2.2) for the AG Working Group. This includes reviewing public comments on WCAG 2.x and improving the following supporting documents: + +* [Understanding WCAG 2.2](https://www.w3.org/WAI/WCAG22/Understanding/) +* [Techniques for WCAG 2.2](https://www.w3.org/WAI/WCAG22/Techniques/) + +For current outstanding WCAG 2.x issues, see [WCAG issues — GitHub](https://github.com/w3c/wcag/issues/). + +## Contribute to the work + +W3C and the AG Working Group welcome input on WCAG work from the global accessibility community. + +### Contribute without joining the group + +There are ways you can contribute without being a member of the working group: -### Task Forces +* **Comment on publications:** During development, the group publishes working drafts for public comment — these are announced on the [WAI News pages](/news/) and on the [WAI Interest Group mailing lists](/about/groups/waiig/#mailinglist). +* **Raise, comment on, or propose fixes to WCAG issues:** If you’re aware of an issue with any of the published WCAG 2.x resources, W3C welcomes you to [raise a new issue on GitHub](https://github.com/w3c/wcag/issues/) — you can also comment on and, even better, propose solutions for existing issues. +* **Contribute to WCAG 3 discussions:** As WCAG 3 develops, many topics are being discussed — to contribute your views, see the list of [open WCAG 3 discussions in GitHub](https://github.com/w3c/wcag3/discussions) and [mailing list discussions](https://lists.w3.org/Archives/Public/w3c-wai-gl/). +* **Participate in a community group:** W3C hosts a small number of active community groups that focus on digital accessibility issues — for details, search for ‘accessibility’ on [Current Groups — W3C Community and Business Groups](https://www.w3.org/community/groups). -The AG WG uses [task forces](task-forces) to focus work on specific projects in addition to the work above. Task Forces are described on the related page. Some task forces form sub-groups to further divide the work. +### Become a participant in the group -## How to Comment, Contribute, and Participate +Joining the AG Working Group enables you to participate fully in the development of the work and influence the deliverables. You and your organization will also be listed as contributors, where appropriate. -The Accessibility Guidelines Working Group engages with stakeholders in a variety of ways. See the following resources for information on: +Being a participant involves commitment to support the work of the group in the following ways: -* [How to contribute to the Working Group and file comments](https://www.w3.org/WAI/WCAG20/comments/); -* [How to contribute to the source repository directly](https://github.com/w3c/wcag/); -* [How to participate in (join) the Working Group](/about/groups/agwg/participate/). +* Engage actively with other participants in the working group using the group’s communication channels. +* Keep up with weekly tasks and the progress of the work — for example, via the minutes of past meetings, mailing list discussions, and GitHub issue comments. +* Give your input promptly, when it’s needed. -## Meetings and Communication +See [Instructions for joining the Accessibility Guidelines Working Group](https://www.w3.org/groups/wg/ag/instructions/). -The AG WG conducts its work using a variety of synchronous and asynchronous tools. The [communication page](/about/groups/agwg/communication/) provides details about: +## Group members and task forces -* Teleconferences of the Working Group and its task forces (also see [upcoming agendas](/WAI/GL/wiki/Upcoming_agendas), meeting minutes); -* Face to face meetings (also see face-to-face [meeting pages](https://www.w3.org/WAI/GL/wiki/Meetings)); -* Email lists; -* [Wiki](https://www.w3.org/WAI/GL/wiki/); -* [Web-Based Surveys (WBS)](https://www.w3.org/2002/09/wbs/35422/); -* [WCAG 2 source repository issue tracker](https://github.com/w3c/wcag/issues). +* [Chairs](https://www.w3.org/groups/wg/ag/participants/#chairs) +* [Current participants](https://www.w3.org/groups/wg/ag/participants/#participants) +* [Task forces](https://www.w3.org/groups/wg/ag/task-forces/) that support the AG Working Group -These tools are used by participants of the Working Group. For ways non-participants can contribute, see [How to contribute to the Working Group and file comments](https://www.w3.org/WAI/WCAG20/comments/). +## Communications and decisions -### Meeting Minutes +* [Calendar of meetings](https://www.w3.org/groups/wg/ag/calendar/) +* [Minutes from previous meetings](https://www.w3.org/WAI/GL/minutes-history) +* [Mailing list archive](https://lists.w3.org/Archives/Public/w3c-wai-gl/) +* [Record of decisions](https://www.w3.org/WAI/GL/wiki/Decisions) +* [Decision policy](/about/groups/agwg/decision-policy/) -[Minutes from previous meetings](https://www.w3.org/WAI/GL/minutes-history) are available. +## GitHub repositories -## Administrative Information +The AG Working Group maintains the following GitHub repositories: -Work of the AG WG is in accordance with the [W3C Process](https://www.w3.org/2023/Process-20231103/). AG WG work is funded in part by the [WAI Core 2015 Project](https://www.w3.org/WAI/about/projects/wai-core-2015/). The work of this group does not necessarily reflect the views or policies of the funders. +* [Accessibility Conformance Testing](https://github.com/w3c/wcag-act/) +* [Cognitive and Learning Disabilities Accessibility](https://github.com/w3c/coga/) +* [Mobile Accessibility](https://github.com/w3c/Mobile-A11y-TF-Note/) +* [Web Content Accessibility Guidelines](https://github.com/w3c/wcag/) +* [WCAG2ICT](https://github.com/w3c/wcag2ict/) -The chairs of the AG WG, responsible for overall leadership and management, are Chuck Adams, Alastair Campbell, and Rachael Montgomery. The staff contact, responsible for W3C Process and general support, is [Kevin White](https://www.w3.org/People/kevin/). Administrative inquiries may be sent to [group-ag-chairs@w3.org](mailto:group-ag-chairs@w3.org). +## Publications and copyright -Work on WCAG 3 is additionally led by Shawn Lauriat and Jeanne Spellman, task force co-facilitators, and Wilco Fiers, WCAG 3 Project Manager. Inquiries about WCAG 3 should be sent to [group-ag-plan@w3.org](mailto:group-ag-plan@w3.org) to reach these people as well as the chairs. +[List of technical reports published by the AG Working Group](https://www.w3.org/groups/wg/ag/publications/). -The AG WG maintains the following operational resources: +W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group — for details, see [Intellectual property rights — AG Working Group](https://www.w3.org/groups/wg/ag/ipr/). -* [Decision policy](decision-policy); -* [Record of decisions made by the WG](https://www.w3.org/WAI/GL/wiki/Decisions); -* [meeting minutes](https://www.w3.org/WAI/GL/minutes-history). +There are also instructions for [How to Make a Patent Disclosure](https://www.w3.org/groups/wg/ag/ipr/#discl-howto). -W3C maintains a [public list of any patent disclosures](https://www.w3.org/groups/wg/ag/ipr/) made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. +## Contact the chairs -[Current participants in the AGWG](https://www.w3.org/groups/wg/ag/participants/). \ No newline at end of file +If you have a question for the AG Working Group’s chairs or the W3C staff contact, email [group-ag-chairs@w3.org](mailto:group-ag-chairs@w3.org). \ No newline at end of file diff --git a/pages/about/groups/agwg/communication.md b/pages/about/groups/agwg/communication.md deleted file mode 100644 index 177c3000a77..00000000000 --- a/pages/about/groups/agwg/communication.md +++ /dev/null @@ -1,82 +0,0 @@ ---- -title: Meetings and Communication -permalink: /about/groups/agwg/communication/ -ref: /about/groups/agwg/communication/ -lang: en -github: - label: wai-groups ---- - -{::options toc_levels="2..3" /} - -{::nomarkdown} -{% include_cached toc.html type="start" title="Page Contents" %} -{:/} - -- TOC is created automatically. -{:toc} - -{::nomarkdown} -{% include_cached toc.html type="end" %} -{:/} - -The Accessibility Guidelines Working Group uses the following tools and procedures to perform its work. - -## Teleconferences - -The AG WG and its task forces participate in the following teleconferences. Unless otherwise mentioned, times are given in Boston time because the UTC time floats with U.S. Daylight Savings Time changes. Follow the link to convert to local time. Meetings take place on [WebEx](https://www.w3.org/2006/tools/wiki/Category:WebEx), using the link given or by dial-in to +1-617-324-0000. If using the web interface to WebEx, the meeting password must be obtained in advance from the chair or staff contact. [IRC](#irc) is used for text chat and [minute taking](http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm?content-type=text/html). It is not expected that participants will join all meetings; instead please strive to be a regular participant in the meeting(s) of greatest relevance to your work in the group. - -- **[Accessibility Guidelines Working Group](https://www.w3.org/events/meetings/fad52978-dc63-4427-90b9-e64dd31b0566/)**: Tuesdays at 11:00 until 13:00 Boston time -- **[AG Facilitators](https://www.w3.org/events/meetings/eaacc8a7-94d4-4a66-83d5-5ded358d69cc/)**: Every second Monday at 13:00 until 13:30 Boston time -- **[AG Planning](https://www.w3.org/events/meetings/b39eb1f4-7daf-48e0-8102-b2e590e37651/)**: Wednesdays and Fridays at 10:00 until 11:00 Boston time -- **[AG Chairs](https://www.w3.org/events/meetings/eda3021b-cb28-46af-8f2d-f7af7a664496/)**: Fridays at 10:00 until 11:00 Boston time -- **[COGA Coordination](https://www.w3.org/2017/08/telecon-info_coga-plan)**: Tuesdays at 7:30 until 8:00 Boston time -- **[Cognitive and Learning Disabilities Accessibility Task Force](https://www.w3.org/2017/08/telecon-info_coga)**: Mondays at 11:00 until 12:00 Boston time -- **[Low Vision Accessibility Task Force](https://www.w3.org/2017/08/01-lvtf-info.html)**: Thursdays at 11:00 until 12:00 Boston time -- **[Mobile Accessibility Task Force](https://www.w3.org/2017/08/telecon-info_matf)**: Mondays at 15:00 until 16:00 Boston time -- **[Silver Plan](https://www.w3.org/2017/08/telecon-info_silver-plan)**: Mondays at 10:00 until 11:00 Boston time -- **[Silver Task Force](https://www.w3.org/2017/08/telecon-info_silver-fri)**: Fridays at 10:00 until 11:00 Boston time -- **[Silver Task Force](https://www.w3.org/2017/08/telecon-info_silver-tue)**: Tuesdays at 9:30 until 10:30 Boston time - -[Minutes of past teleconferences](https://www.w3.org/WAI/GL/minutes-history) are available. - -## Face to Face Meetings - -The Working Group holds occasional face-to-face meetings. These are usually listed in the [meetings wiki](https://www.w3.org/WAI/GL/wiki/Meetings). - -## Email lists - -- **[w3c-wai-gl@w3.org](mailto:w3c-wai-gl@w3.org)** - Working Group discussion list; public archive ([w3c-wai-gl archives](http://lists.w3.org/Archives/Public/w3c-wai-gl/)); -- **[public-agwg-comments@w3.org](mailto:public-agwg-comments@w3.org)** - For WG to receive public comments on publications; public archive; anyone may post; only editors subscribe ([public-agwg-comments archives](https://lists.w3.org/Archives/Public/public-agwg-comments/)); -- **[group-ag-chairs@w3.org](mailto:group-ag-chairs@w3.org)** - for private input to the AG chairs from the public; anyone may post; only editors subscribe; -- **[group-ag-plan@w3.org](mailto:group-ag-plan@w3.org)** – for private input to AG leadership team; anyone may post; only  editors, staff contacts, and project manager subscribe; -- **[public-ag-admin@w3.org](mailto:public-ag-admin@w3.irg)** - Working Group consensus tracking list; public archive ([public-ag-admin archives](http://lists.w3.org/Archives/Public/public-ag-admin/)). - -The AG Admin list will be used to approve WCAG 3 issues. Proposed resolutions will be discussed in the relevant subgroup before coming to the group via email on this list. When proposed resolutions are brought to the list, the group will have 7 days to vote. - -- If all responses are  +1, 0 or no response is provided then the issue will be resolved; -- If -1 responses can be quickly resolved via email, we will do so; -- If -1 responses require discussion they will be queued up for Tuesday meetings. - -## Source repository - -Publications under development are maintained in the [WCAG 2 GitHub repository](https://github.com/w3c/wcag/). This distributed source control system allows multiple people to edit simultaneously, public view of changes as they are committed, and "pull requests" to enable people without direct commit access to suggest contributions. Publication editors are designated by the WG chair and have direct commit access. Editors commit to execute the group consensus, request review of non-editorial changes, process conflicting input (from issues, pull requests, and discussions) in a neutral manner, and maintain document quality. - -## IRC - -W3C Working Groups use [IRC](https://www.w3.org/wiki/IRC) for synchronous text chat and, with the aid of some IRC bots, to record minutes of teleconferences. The ARIA WG uses the following IRC channels. They are available at any time but are only routinely logged during teleconferences. - -- [#ag](irc://irc.w3.org/aria) for the main Working Group. -- [#wcag-act](irc://irc.w3.org/wcag-act) for the Accessibility Conformance Testing Task Force. -- [#coga](irc://irc.w3.org/coga) for the Cognitive Accessibility Task Force. -- [#mobile-a11y](irc://irc.w3.org/mobile-a11y) for the Mobile Accessibility Task Force. -- [#lvtf](irc://irc.w3.org/lvtf) for the Low Vision Accessibility Task Force. -- [#silver](irc://irc.w3.org/silver) for the Silver Task Force. - -## Other - -The ARIA WG uses the following web-based resources as well: - -- [Wiki](https://www.w3.org/WAI/GL/wiki/), to develop or record content not immediately intended for formal publication. This is writeable by WG members and publicly readable. -- [Web-Based Surveys (WBS)](https://www.w3.org/2002/09/wbs/35422/), to measure aggregate group opinion. These can be completed by WG members with publicly readable results. -- [WCAG 2 GitHub Issues](https://github.com/w3c/wcag/issues) to track issues for publications maintained in the GitHub repository. Users with a [GitHub account](https://github.com/) can file or comment on issues, and issues are publicly readable. \ No newline at end of file diff --git a/pages/about/groups/agwg/decision-policy.md b/pages/about/groups/agwg/decision-policy.md index 3a3d64cd38b..e7f08c28fae 100644 --- a/pages/about/groups/agwg/decision-policy.md +++ b/pages/about/groups/agwg/decision-policy.md @@ -1,5 +1,5 @@ --- -title: Decision Policy +title: Accessibility Guidelines Working Group Decision Policy permalink: /about/groups/agwg/decision-policy/ ref: /about/groups/agwg/decision-policy/ lang: en @@ -7,7 +7,7 @@ github: label: wai-groups --- -This document explains the decision process of the [AG Working Group](https://www.w3.org/groups/wg/ag/). It was [accepted by the Working Group 15 September 2015](https://www.w3.org/2015/09/15-wai-wcag-minutes#item02). It was updated editorially 27 January 2017 to change the name of the WG to "Accessibility Guidelines Working Group" and to add links to referenced resources. [A substantive update was approved 20 November 2018](https://lists.w3.org/Archives/Public/w3c-wai-gl/2018OctDec/0095.html). [Substantive changes to support WCAG 3 work were approved 5 August 2022](https://lists.w3.org/Archives/Public/w3c-wai-gl/2022JulSep/0153.html). +This document explains the decision process of the [Accessibility Guidelines (AG) Working Group](https://www.w3.org/groups/wg/ag/). It was [accepted by the Working Group 15 September 2015](https://www.w3.org/2015/09/15-wai-wcag-minutes#item02). It was updated editorially 27 January 2017 to change the name of the WG to "Accessibility Guidelines Working Group" and to add links to referenced resources. [A substantive update was approved 20 November 2018](https://lists.w3.org/Archives/Public/w3c-wai-gl/2018OctDec/0095.html). [Substantive changes to support WCAG 3 work were approved 5 August 2022](https://lists.w3.org/Archives/Public/w3c-wai-gl/2022JulSep/0153.html). The Working Group follows the [W3C Process Document](https://www.w3.org/Consortium/Process/#Consensus) regarding decisions. This document provides additional detail about the consensus decision-making process. The Working Group updates this policy as needed, using the procedures of this policy to ratify the update. diff --git a/pages/about/groups/agwg/participate.md b/pages/about/groups/agwg/participate.md deleted file mode 100644 index a49435f9435..00000000000 --- a/pages/about/groups/agwg/participate.md +++ /dev/null @@ -1,55 +0,0 @@ ---- -title: Participating in the Accessibility Guidelines Working Group (AGWG) -permalink: /about/groups/agwg/participate/ -ref: /about/groups/agwg/participate/ -lang: en -github: - label: wai-groups ---- - -{::options toc_levels="2..3" /} - -{::nomarkdown} -{% include_cached toc.html type="start" title="Page Contents" %} -{:/} - -- TOC is created automatically. -{:toc} - -{::nomarkdown} -{% include_cached toc.html type="end" %} -{:/} - -This page explains the requirements and procedures for becoming a participant in the AG WG. It also explains how non-participants may contribute to the Working Group by subscribing to the group's mailing list, monitoring the group's progress, and contributing on that list. See also [Participating in WAI](http://www.w3.org/WAI/participation) for broader participation options throughout the Web Accessibility Initiative (WAI). - -## Review drafts - -Working Drafts are updated periodically and are available for your review. W3C Working Drafts provide opportunities for public comment during the development of a specification. Please follow the [Instructions for Commenting on WCAG 2.0 Documents](https://www.w3.org/WAI/WCAG20/comments/) (preferred) or send mail to the public comments mailing list: [public-comments-wcag20@w3.org](mailto:public-comments-wcag20@w3.org). [The archive for the public comments mailing list](http://lists.w3.org/Archives/Public/public-comments-wcag20/) is available. - -## Review the mailing list - -The [AG WG mailing list archives](http://lists.w3.org/Archives/Public/w3c-wai-gl/) are publicly available and can be read by anyone. - -## Become a participant - -Participation enables you to influence the development of the deliverables, and you and your organization will be listed as contributors to the deliverables of the AG WG where appropriate. Participant status, however, requires a commitment on your behalf to support the work of the group. Participation in [task forces](/about/groups/agwg/task-forces/) counts towards overall participation expectations for the Working Group as a whole. - -Participants should: - -- Engage actively with the Working Group via any of the communication mechansims available; -- Provide input in a timely fashion. -- Maintain familiarity with the progress of the Working Group via minutes of past meetings, mailing list discussion, issue comments, etc. - -Participating in the Working Group requires a W3C account; you can [create an account](https://www.w3.org/accounts/request) if you do not already have one. Before applying to join, please read the [AG WG Charter](https://www.w3.org/WAI/GL/charter) to review the activity and commitments. When you join the group, you are automatically added to the mailing lists and provide access to the WG [communication tools](/about/groups/agwg/communication/). - -[Current participants in the AG WG](https://www.w3.org/2000/09/dbwg/details?group=35422&public=1). - -## Employees of Member organizations - -Employees of Member organizations automatically have the right to participate. To join, ask your [W3C Advisory Committee (AC) Representative](https://www.w3.org/Member/ACList) to [nominate you to the Working Group](http://www.w3.org/2004/01/pp-impl/35422/join). You can also use available public contribution channels, above, without joining the group if you or your employer prefer. - -## Individuals - -If you do **not** work for a [W3C Member organization](https://www.w3.org/Consortium/Member/List), but you feel you have the expertise and availability to participate, you should first use public contribution channels, above, to familiarize yourself with the work and make yourself known to the group. If your contribution suggests a higher level of participation is warranted, you can be invited to join the group as an Invited Expert. Please [contact the WG chairs](mailto:group-ag-chairs@w3.org) to discuss this. If you work for an organization whose business is related to that of the W3C, we may instead ask your organization to join and nominate you as a Member representative. - -If the chairs support it, you may complete the [invited expert application](https://www.w3.org/ieapp/new) form, indicating the Accessibility Guidelines WG as the group you wish to join. Make sure you have read and accepted the policies referenced from that form, and include details about your relevant expertise, interest in the work, and your employer. _If you have not made yourself known to the chairs, or your application does not provide information about your expertise and expected contribution, it may be rejected._ diff --git a/pages/about/groups/agwg/task-forces.md b/pages/about/groups/agwg/task-forces.md deleted file mode 100644 index 1ca492e6682..00000000000 --- a/pages/about/groups/agwg/task-forces.md +++ /dev/null @@ -1,53 +0,0 @@ ---- -title: Task Forces -permalink: /about/groups/agwg/task-forces/ -ref: /about/groups/agwg/task-forces/ -lang: en -github: - label: wai-groups ---- - -{::options toc_levels="2..3" /} - -{::nomarkdown} -{% include_cached toc.html type="start" title="Page Contents" %} -{:/} - -- TOC is created automatically. -{:toc} - -{::nomarkdown} -{% include_cached toc.html type="end" %} -{:/} - -The Accessibility Guidelines Working Group conducts some of its work via the following task forces. See each task force page for details about specific work and how to join. - -Task force facilitators [meet the first Wednesday of the month](https://www.w3.org/2017/08/telecon-info_ag-facilitators) for coordination (also see [AG facilitators minutes](https://www.w3.org/WAI/GL/WCAG3/minutes/?channel_id=ag-facilitators)). Task force coordination is maintained in the [AG Facilitators wiki](https://www.w3.org/WAI/GL/wiki/AG_Facilitators). - -## Accessibility Conformance Testing (ACT) Task Force - -The [Accessibility Conformance Testing Task Force](/about/groups/task-forces/conformance-testing/) will develop a framework and repository of test rules, to promote a unified interpretation of WCAG 2.0 among different web accessibility test tools. The framework will also allow the development of custom test rules to meet company requirements and best practices. While this framework will add a layer of implemention for tool developers, it provides more consistency and comparability of the resulting test rules. - -## Cognitive and Learning Disabilities Accessibility Task Force - -The [Cognitive and Learning Disabilities Accessibility Task Force](/about/groups/task-forces/coga/) will develop draft proposed guidance and techniques to make web content, content authoring, and user agent implementation accessible and more useable by people with cognitive and learning disabilities. - -## WCAG 2.x Backlog Task Force - -The objective of the [WCAG 2.x Backlog Task Force](/about/groups/task-forces/wcag2x-backlog/) is to maintain up-to-date versions of the normative and informative materials associated with versions 2.0, 2.1, and 2.2 of the Web Content Accessibility Guidelines, and to document considerations for WCAG 3.0 which cannot be readily addressed within the existing normative language of the 2.x specification. - -## Low Vision Accessibility Task Force - -The [Low Vision Accessibility Task Force](/about/groups/task-forces/low-vision-a11y-tf/) will identify issues and specify solutions to web accessibility issues specific to users with low vision via WCAG 2.0 techniques, understanding and guidance documents, and as needed to produce extensions to WCAG 2.0. - -## Mobile Accessibility Task Force - -The [Mobile Accessibility Task Force](/about/groups/task-forces/matf/) produce techniques, understanding and guidance documents as well as updates to existing related W3C / WAI material that addresses the mobile space. - -## Silver Task Force - -The [Silver Task Force](/about/groups/task-forces/silver/) will perform preliminary development of a new version of Accessibility Guidelines following a research-focused, user-centered design methodology to produce the most effective and flexible outcome. These guidelines will address the process of making content and functionality accessible to people with disabilities, including the roles of content authoring, user agent support, and authoring tool support. These guidelines will address current technological and cultural web accessibility requirements and provide a base for continued evolution of the guidelines. Also see the related [Silver Community Group](https://www.w3.org/community/silver/). - -## WCAG2ICT Task Force - -The objective of the [WCAG2ICT Task Force](/about/groups/task-forces/wcag2ict/) is to develop documentation describing how WCAG 2.1 and 2.2 and its principles, guidelines, and success criteria could apply to non-Web Information and Communications Technologies (ICT). \ No newline at end of file diff --git a/pages/about/groups/apawg.md b/pages/about/groups/apawg.md index 1367ddab334..81c274bd2c7 100644 --- a/pages/about/groups/apawg.md +++ b/pages/about/groups/apawg.md @@ -1,9 +1,16 @@ --- -title: Accessible Platform Architectures (APA) Working Group -nav_title: 'APA: Accessible Platform WG' +title: Accessible Platform Architectures Working Group +nav_title: 'Accessible Platform Architectures WG' lang: en permalink: /about/groups/apawg/ ref: /about/groups/apawg/ +redirect_from: + - /about/groups/apawg/communication/ + - /about/groups/apawg/contribute/ + - /about/groups/apawg/deliverables/ + - /about/groups/apawg/participate/ + - /about/groups/apawg/task-forces/ + - /about/groups/apawg/video-examples/ github: label: wai-groups --- @@ -12,9 +19,7 @@ github: {% include box.html type="start" title="Summary" class="" %} {:/} -The mission of the Accessible Platform Architectures Working Group (APA WG) is to ensure W3C specifications provide support for accessibility to people with disabilities. The group advances this mission through review of W3C specifications, development of technical support materials, collaboration with other Working Groups, and coordination of harmonized accessibility strategies within W3C. - -Some information on this page is also shown on, and may be more current in, the automatically generated [Accessible Platform Architectures Working Group page](https://www.w3.org/groups/wg/apa/). +Find out about the activities of the Accessible Platform Architectures (APA) Working Group and how you can contribute to its mission. {::nomarkdown} {% include box.html type="end" %} @@ -33,75 +38,78 @@ Some information on this page is also shown on, and may be more current in, the {% include_cached toc.html type="end" %} {:/} +## Mission -## Announcements +The mission of the APA Working Group is to ensure W3C specifications support accessibility for people with disabilities through the following activities: reviewing specifications; developing new specifications and technical support materials; collaborating with other W3C working groups on technology accessibility; and coordinating harmonized accessibility strategies within W3C that include security, privacy, and internationalization. -No announcements at the moment. +## Charter -## Current Work +To learn about the group’s focus, scope and deliverables, see the [APA Working Group Charter](https://www.w3.org/2023/07/apa-wg-charter). -The APA WG is engaged on the following work: +## Current work -- Publications: The Working Group maintains a comprehensive list of publications and status](/about/groups/apawg/deliverables/), which include: - - Several [Accessibility User Requirements](https://www.w3.org/TR/?filter-tr-name=accessibility+user+requirements) guides for specific technologies; - - [Framework for Accessible Specification of Technologies](https://w3c.github.io/apa/fast/) plus [FAST checklist](https://w3c.github.io/apa/fast/checklist.html), - - [Inaccessibility of CAPTCHA](https://w3c.github.io/apa/captcha/), - - [Spoken Presentation technology](https://www.w3.org/TR/?filter-tr-name=spoken+presentation) to provide for proper pronunciation in HTML content when using text to speech (TTS) synthesis, - - [WAI-Adapt technology](https://www.w3.org/TR/?filter-tr-name=WAI-Adapt) to enable design of sites in a way that they can be personalized to the needs of each user allows more optimal accessibility. -- Specification reviews: input is solicited on the [WAI Interest Group mailing list](http://lists.w3.org/Archives/Public/w3c-wai-ig/), tracked in the [APA specification review wiki pages](https://www.w3.org/WAI/APA/wiki/Category:Spec_Review)and comments are copied to the [public-apa mailing list](https://lists.w3.org/Archives/Public/public-apa/). -- Community groups: the Working Group maintains a [list of community groups to track](https://www.w3.org/WAI/APA/wiki/Community_Groups). +For details of the current work, see the [APA Working Group wiki](https://www.w3.org/WAI/APA/wiki/). -The [APA Project Plan](/about/groups/apawg/deliverables/) details intended timeline and milestones for this work. +## Contribute to the work -## Horizontal Review +W3C and the APA Working Group welcome input on APA work from the global accessibility community. -The APA Working Group performs [accessibility horizontal review](https://www.w3.org/wiki/DocumentReview) of other technologies under development by W3C. Documents reviewed from 2015 to present are shown in the [Specification Review list](https://www.w3.org/WAI/APA/wiki/Category:Spec_Review). Active reviews under way are shown in the [Accessibility Review Comment Tracker](https://w3c.github.io/horizontal-issue-tracker/?repo=w3c/a11y-review). The group also reviews [charters of groups](https://github.com/w3c/strategy/issues?q=is%3Aissue+is%3Aopen+label%3A%22Horizontal+review+requested%22%22) to check that deliverables and liaisons reflect accessibility needs. +### Contribute without joining the group -To request review of a GitHub issue from the APA, add the "a11y-tracker" label to the issue. If the APA files an issue or agrees to comment on an issue, the label will be changed to "a11y-needs-resolution". To request review outside of a GitHub issue context, send email to [group-apa-chairs@w3.org](mailto:group-apa-chairs@w3.org). +There are ways you can contribute without being a member of the working group: -## Task Forces +* **Comment on publications:** During development, the group publishes working drafts for public comment — these are announced on the [WAI News pages](/news/) and on the [WAI Interest Group mailing lists](/about/groups/waiig/#mailinglist). +* **Raise, comment on, or propose fixes to APA issues:** If you’re aware of an issue with any of the published APA resources, W3C welcomes you to [raise a new issue on GitHub](https://github.com/w3c/apa/issues) — you can also comment on and, even better, propose solutions for existing issues. +* **Contribute to APA discussions:** You may contribute your views to the APA Working Group's [mailing list discussions](https://lists.w3.org/Archives/Public/public-apa/). -The APA WG uses [task forces](/about/groups/apawg/task-forces/) to focus work on specific projects. Task Forces are described on the related page. +### Become a participant in the group -## How to Comment, Contribute, and Participate +Joining the APA Working Group enables you to participate fully in the development of the work and influence the deliverables. You and your organization will also be listed as contributors, where appropriate. -The APA Working Group engages with stakeholders in a variety of ways. See the following resources for information on: +Being a participant involves commitment to support the work of the group in the following ways: -- [How to contribute to the Working Group and file comments](/about/groups/apawg/contribute/); -- [How to contribute to the source repository directly](https://github.com/w3c/apa/); -- [How to participate in (join) the Working Group](/about/groups/apawg/participate/). +* Engage actively with other participants in the working group using the group’s communication channels. +* Keep up with weekly tasks and the progress of the work — for example, via the minutes of past meetings, mailing list discussions, and GitHub issue comments. +* Give your input promptly, when it’s needed. -## Meetings and Communication +See [Instructions for joining the Accessible Platform Architectures Working Group](https://www.w3.org/groups/wg/apa/instructions/). -The APA WG conducts its work using a variety of synchronous and asynchronous tools. The [communication](/about/groups/apawg/communication/) page provides details about: +## Group members and task forces -- Teleconferences of the Working Group and its task forces (also see [meeting minutes](https://www.w3.org/WAI/APA/minutes)); -- Face to face meetings (also see face to face [meeting pages](https://www.w3.org/WAI/APA/wiki/Meetings)); -- Email lists; -- [apa source repository](https://github.com/w3c/apa/); -- [Wiki](https://www.w3.org/WAI/APA/wiki/); -- [Web-Based Surveys (WBS)](https://www.w3.org/2002/09/wbs/83907/); -- [apa source repository issue tracker](https://github.com/w3c/apa/issues). +* [Chairs](https://www.w3.org/groups/wg/apa/participants/#chairs) +* [Current participants](https://www.w3.org/groups/wg/apa/participants/#participants) +* [Task forces](https://www.w3.org/groups/wg/apa/task-forces/) that support the APA Working Group -These tools are used by participants of the Working Group. For ways non-participants can contribute, see [how to contribute to the Working Group and file comments](/about/groups/apawg/contribute/). +## Communications and decisions -### Meeting Minutes +* [Calendar of meetings](https://www.w3.org/groups/wg/apa/calendar/) +* [Minutes from previous meetings](https://www.w3.org/WAI/APA/minutes) +* [Mailing list archive](https://lists.w3.org/Archives/Public/public-apa/) +* [Record of decisions](https://www.w3.org/WAI/APA/wiki/Decisions) +* [Decision policy](/about/groups/apawg/decision-policy/) -[Minutes from previous meetings](https://www.w3.org/WAI/APA/minutes) are available. +## GitHub repositories +The APA Working Group maintains the following GitHub repositories: -## Administrative Information +* [Accessible Platform Architectures](https://github.com/w3c/apa/) +* [Accessible Platform Architectures Review](https://github.com/w3c/apa-review/issues/) +* [Accessibility Maturity Model](https://github.com/w3c/maturity-model/) +* [Accessibility Request](https://github.com/w3c/a11y-request/) +* [Accessibility Review](https://github.com/w3c/a11y-review/) +* [Cognitive and Learning Disabilities Accessibility](https://github.com/w3c/coga/) +* [Framework for Accessible Specification of Technologies](https://github.com/w3c/fast) +* [Pronunciation](https://github.com/w3c/pronunciation/) +* [Research Questions](https://github.com/w3c/rqtf/) +* [WAI-Adapt](https://github.com/w3c/adapt/) -Work of the APA WG is in accordance with the [W3C Process](https://www.w3.org/2023/Process-20231103/). APA work is funded in part by the [WAI Core 2015 Project](http://www.w3.org/WAI/Core2015/). The work of this group does not necessarily reflect the views or policies of the funders. +## Publications and copyright -The chairs of the APA WG, responsible for overall leadership and management, are [Matthew Atkinson](mailto:m.atkinson@samsung.com) and [Janina Sajka](mailto:janina@rednote.net). The staff contact, responsible for [W3C Process](http://www.w3.org/Consortium/Process/) and general support, is [Ruoxi (Roy) Ran](http://www.w3.org/People/Roy/). Administrative inquiries may be sent to [group-apa-chairs@w3.org](mailto:group-apa-chairs@w3.org). +[List of technical reports published by the APA Working Group](https://www.w3.org/groups/wg/apa/publications/). -The Accessible Platform Architectures maintains the following operational resources: +W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group — for details, see [Intellectual property rights — APA Working Group](https://www.w3.org/groups/wg/apa/ipr/). -- [Decision policy](/about/groups/apawg/decision-policy/); -- [Record of decisions made by the WG](https://www.w3.org/WAI/APA/wiki/Decisions); -- [Archives of past activity](https://www.w3.org/WAI/APA/archive); -- [meeting minutes](https://www.w3.org/WAI/APA/minutes). +There are also instructions for [How to Make a Patent Disclosure](https://www.w3.org/groups/wg/apa/ipr/#discl-howto). -W3C maintains a [public list of any patent disclosures](https://www.w3.org/groups/wg/apa/ipr/) made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. +## Contact the chairs -[Current participants in the APA WG](https://www.w3.org/groups/wg/apa/participants/). +If you have a question for the APA Working Group’s chairs or the W3C staff contact, email [group-apa-chairs@w3.org](mailto:group-apa-chairs@w3.org). \ No newline at end of file diff --git a/pages/about/groups/apawg/communication.md b/pages/about/groups/apawg/communication.md deleted file mode 100644 index 57ac176d920..00000000000 --- a/pages/about/groups/apawg/communication.md +++ /dev/null @@ -1,58 +0,0 @@ ---- -title: Communication -permalink: /about/groups/apawg/communication/ -ref: /about/groups/apawg/communication/ -lang: en -github: - label: wai-groups ---- - -The APA Working Group uses the following tools and procedures to perform its work. - -## Teleconferences - -The APA WG and its task forces participate in the following teleconferences. Unless otherwise mentioned, times are given in Boston time because the UTC time floats with U.S. Daylight Savings Time changes. Follow the link to convert to local time. Meetings take place on [Zoom](https://www.w3.org/2017/08/telecon-info_apa), using the link given on the meeting name. [IRC](https://www.w3.org/wiki/IRC) is used for text chat and [minute taking](http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm?content-type=text/html). It is not expected that participants will join all meetings; instead please strive to be a regular participant in the meeting(s) of greatest relevance to your work in the group. - -- **[Accessible Platform Architectures Working Group](https://www.w3.org/2017/08/telecon-info_apa)**: Wednesdays at 10:00 until 11:00 Boston time -- **[APA Plan](https://www.w3.org/2017/08/telecon-info_apa-plan)**: Tuesdays at 8:00 until 9:00 Boston time -- **[COGA Coordination](https://www.w3.org/2017/08/telecon-info_coga-plan)**: Tuesdays at 7:30 until 8:00 Boston time -- **[Cognitive and Learning Disabilities Accessibility Task Force](https://www.w3.org/2017/08/telecon-info_coga)**: Mondays at 11:00 until 12:00 Boston time -- **[Maturity Model Task Force](https://www.w3.org/2017/08/telecon-info_maturity-model)**: Wednesdays at 11:00 until 12:00 Boston time -- **[Spoken Presentation Task Force](https://www.w3.org/2017/08/telecon-info_pronunciation)**: Mondays at 11:00 until 12:00 Boston time -- **[Research Questions Task Force](https://www.w3.org/2017/08/telecon-info_rqtf)**: Wednesdays at 9:00 until 10:00 Boston time -- **[WAI-Adapt](https://www.w3.org/2017/08/telecon-info_adapt)**: Mondays at 10:00 until 11:00 Boston time -- **[WAI-Adapt Plan](https://www.w3.org/2017/08/telecon-info_adapt-plan)**: Tuesdays at 10:00 until 10:30 Boston time - -[Minutes of past teleconferences](https://www.w3.org/WAI/APA/minutes) are available. - -## Face to Face Meetings - -[Previous meetings](https://www.w3.org/WAI/APA/wiki/Meetings) of the APA WG are available. - -## Email lists - -- **public-apa@w3.org** - Working Group discussion list; public archive; public can post; inquire to subscribe ([public-apa archives](http://lists.w3.org/Archives/Public/public-apa/)). -- **public-apa-admin@w3.org** - Working Group decision list; public archive; must be WG member to post or subscribe ([public-apa-admin archives](http://lists.w3.org/Archives/Public/public-apa-admin/)). - -## Source repository - -Publications under development are maintained in the [APA GitHub repository](https://github.com/w3c/apa/). This distributed source control system allows multiple people to edit simultaneously, public view of changes as they are committed, and "pull requests" to enable people without direct commit access to suggest contributions. Publication editors are designated by the WG chair and have direct commit access. Editors commit to execute the group consensus, request review of non-editorial changes, process conflicting input (from issues, pull requests, and discussions) in a neutral manner, and maintain document quality. - -## IRC - -W3C Working Groups use [IRC](https://www.w3.org/wiki/IRC) for synchronous text chat and, with the aid of some IRC bots, to record minutes of teleconferences. The APA WG uses the following IRC channels. They are available at any time but are only routinely logged during teleconferences. - -- [#apa](irc://irc.w3.org/apa) for the main Working Group. -- [#adapt](irc://irc.w3.org/adapt) for the WAI-Adapt Task Force. -- [#coga](irc://irc.w3.org/coga) for the Cognitive Accessibility Task Force. -- [#maturity](irc://irc.w3.org/maturity) for the Maturity Model Task Force. -- [#pronunciation](irc://irc.w3.org/maturity) for the Spoken Presentation Task Force. -- [#rqtf](irc://irc.w3.org/rqtf) for the Research Questions Task Force. - -## Other - -The APA WG uses the following web-based resources as well: - -- [Wiki](https://www.w3.org/WAI/APA/wiki/), to develop or record content not immediately intended for formal publication. This is writeable by WG members and publicly readable. -- [Web-Based Surveys (WBS)](http://www.w3.org/2002/09/wbs/83907/), to measure aggregate group opinion. These can be completed by WG members with publicly readable results. -- [GitHub Issues](https://github.com/w3c/apa/issues), to track issues for publications maintained in the GitHub repository. Users with a [GitHub account](https://github.com/) can file or comment on issues, and issues are publicly readable. diff --git a/pages/about/groups/apawg/contribute.md b/pages/about/groups/apawg/contribute.md deleted file mode 100644 index a08ff20b242..00000000000 --- a/pages/about/groups/apawg/contribute.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -title: How to Contribute -permalink: /about/groups/apawg/contribute/ -ref: /about/groups/apawg/contribute/ -lang: en -github: - label: wai-groups ---- - -There are a number of ways non-participants in the APA WG can contribute to the work. If you wish to be an active contributer, however, you should [join the Working Group](/about/groups/apawg/participate/). - -## Public comments - -The APA WG accepts public comments on publications on the [public-apa](http://lists.w3.org/Archives/Public/public-apa/) list. This is primarily used for input on formal publications. - -## Github issues and pull requests - -Much of the technical work is done in the [W3C APA WG repository on GitHub](https://github.com/w3c/apa/). A [GitHub account](http://github.com/) is required for the following functionality. In addition to using the comments list described above to submit input, you may: - -- [Watch the repository](https://help.github.com/articles/watching-repositories/); -- [File issues](https://guides.github.com/features/issues/); -- Submit [pull requests](https://help.github.com/articles/using-pull-requests/). - -## Mailing list discussions - -If you would like to monitor the work of the APA WG and contribute on-line, you may subscribe to the following mailing lists. You will not be considered a formal participant but may comment and contribute. The APA WG uses the following mailing lists: - -- The [WAI Interest Group](http://www.w3.org/WAI/IG/) and its mailing lists is used for announcements of WG activity and to coordinate specification review. -- [public-apa@w3.org](http://lists.w3.org/Archives/Public/public-apa/) is used for technical discussion of the WG. -- [public-apa-admin@w3.org](http://lists.w3.org/Archives/Public/public-apa-admin/) is used for administrative coordination of the WG. diff --git a/pages/about/groups/apawg/decision-policy.md b/pages/about/groups/apawg/decision-policy.md index 77697f0ffb8..db426e4e477 100644 --- a/pages/about/groups/apawg/decision-policy.md +++ b/pages/about/groups/apawg/decision-policy.md @@ -1,5 +1,5 @@ --- -title: Decision Policy +title: Accessible Platform Architectures Working Group Decision Policy permalink: /about/groups/apawg/decision-policy/ ref: /about/groups/apawg/decision-policy/ lang: en @@ -7,7 +7,7 @@ github: label: wai-groups --- -This document explains the decision process of the Accessible Platform Architectures Working Group. +This document explains the decision process of the [Accessible Platform Architectures (APA) Working Group](https://www.w3.org/groups/wg/apa/). There are often divergent opinions on issues. It is important that all views are expressed and considered, but it is critical to Working Group function that it can come to conclusions. The procedures set out here describe how the WG discusses a topic and forms a decision, preferably by [consensus](https://www.w3.org/Consortium/Process/#Consensus). These procedures are designed to ensure that input is considered, whether in teleconferences or using asynchronous communication tools. diff --git a/pages/about/groups/apawg/deliverables.md b/pages/about/groups/apawg/deliverables.md deleted file mode 100644 index 15f284d6478..00000000000 --- a/pages/about/groups/apawg/deliverables.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -title: APA Project Plan -permalink: /about/groups/apawg/deliverables/ -ref: /about/groups/apawg/deliverables/ -lang: en -github: - label: wai-groups ---- - -## Updated Milestones - -The [Working Group charter](https://www.w3.org/2015/10/apa-charter.html#milestones) proposed initial milestones for Recommendation-track deliverables. Updates to those milestones are provided here. Deliverables with an asterisk at the beginning are considered critical to the success of the Working Group. - -**This content is being migrated** to [https://www.w3.org/WAI/APA/wiki/Project](https://www.w3.org/WAI/APA/wiki/Project). - -| Specification | Status (12 April 2021) | Projection | -| --- | --- | --- | -| FPWD | CR | PR | Rec | -| --- | --- | --- | --- | -| [WAI-Adapt: Symbols Module]([WAI-Adapt: Symbols Module](https://w3c.github.io/adapt/symbols/)) | FPWD published by ARIA WG; IP being transferred to APA. | - | Feb 2019 | Jun 2019 | Sep 2019 | -| [WAI Adapt: Help and Support Module](https://w3c.github.io/adapt/help/) | FPWD planned Q3 2018 | Oct 2018 | Nov 2019 | Apr 2020 | Dec 2020 | -| [WAI Adapt: Tools Module](https://w3c.github.io/adapt/tools/) | FPWD planned Q3 2018 | Oct 2018 | Nov 2020 | Apr 2021 | Dec 2021 | diff --git a/pages/about/groups/apawg/participate.md b/pages/about/groups/apawg/participate.md deleted file mode 100644 index 4d1b798e699..00000000000 --- a/pages/about/groups/apawg/participate.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -title: APA Participation -permalink: /about/groups/apawg/participate/ -ref: /about/groups/apawg/participate/ -lang: en -github: - label: wai-groups ---- - -This page explains the requirements and procedures for becoming a participant in the APA WG. See also [Participating in WAI](http://www.w3.org/WAI/participation) for broader participation options throughout the Web Accessibility Initiative (WAI). Participation enables you to influence the development of the deliverables, and you and your organization will be listed as contributors to the deliverables of the APA WG where appropriate. Participant status, however, requires a commitment on your behalf to support the work of the group. - -Participating in the Working Group requires a W3C account; you can [create an account](https://www.w3.org/accounts/request) if you do not already have one. Before applying to join, please read the [APA WG Charter](https://www.w3.org/WAI/APA/charter) to review the activity and commitments. When you join the group, you are automatically added to the [mailing lists](/about/groups/apawg/contribute/#lists) and provide access to the WG [communication tools](/about/groups/apawg/communication/). - -[Current participants in the APA WG](https://www.w3.org/groups/wg/apa/participants/). - -## Employees of Member organizations - -Employees of Member organizations automatically have the right to participate. To join, ask your [W3C Advisory Committee (AC) Representative](https://www.w3.org/Member/ACList) to [nominate you to the Working Group](http://www.w3.org/2004/01/pp-impl/83907/join). You can also use available [public contribution channels](/about/groups/apawg/contribute/) without joining the group if you or your employer prefer. - -## Individuals - -If you do **not** work for a [W3C Member organization](http://www.w3.org/Consortium/Member/List), but you feel you have the expertise and availability to participate, you should first use [public contribution channels](/about/groups/apawg/contribute/) to familiarize yourself with the work and make yourself known to the group. If your contribution suggests a higher level of participation is warranted, you can be invited to join the group as an Invited Expert. Please [contact the WG chairs](mailto:group-apa-chairs@w3.org) to discuss this. If you work for an organization whose business is related to that of the W3C, we may instead ask your organization to join and nominate you as a Member representative. - -If the chairs support it, you may complete the [invited expert application](https://www.w3.org/ieapp/new) form, indicating the Accessible Platform Architectures WG as the group you wish to join. Make sure you have read and accepted the policies referenced from that form, and include details about your relevant expertise, interest in the work, and your employer. _If you have not made yourself known to the chairs, or your application does not provide information about your expertise and expected contribution, it may be rejected._ diff --git a/pages/about/groups/apawg/task-forces.md b/pages/about/groups/apawg/task-forces.md deleted file mode 100644 index 09c384da9ad..00000000000 --- a/pages/about/groups/apawg/task-forces.md +++ /dev/null @@ -1,44 +0,0 @@ ---- -title: Task Forces -nav_title: Task Forces -permalink: /about/groups/apawg/task-forces/ -ref: /about/groups/apawg/task-forces/ -lang: en -github: - label: wai-groups ---- - -{::options toc_levels="2..3" /} - -{::nomarkdown} -{% include_cached toc.html type="start" title="Page Contents" %} -{:/} - -- TOC is created automatically. -{:toc} - -{::nomarkdown} -{% include_cached toc.html type="end" %} -{:/} - -The APA Working Group conducts accessibility review of W3C specifications, and further work via the following task forces. See each task force page for details about specific work and how to join. - -## Cognitive and Learning Disabilities Accessibility Task Force - -The [Cognitive and Learning Disabilities Accessibility Task Force](/about/groups/task-forces/coga/) will develop draft proposed guidance and techniques to make web content, content authoring, and user agent implementation accessible and more usable by people with cognitive and learning disabilities. - -## WAI-Adapt Task Force - -The work of [WAI-Adapt Task Force](/about/groups/task-forces/adapt/) enables users to use adaptive widgets and user preferences to customize their user experience. It enables content authors to provide a default design and enable user adaptation with minimal work. - -## Research Questions Task Force - -The [Research Questions Task Force (RQTF)](/about/groups/task-forces/research-questions/) works to identify accessibility knowledge gaps and barriers in emerging and future web technologies, and to identify research findings, researchers, and research opportunities to inform and fill those gaps where possible. - -## Spoken Presentation Task Force - -The [Spoken Presentation Task Force](/about/groups/task-forces/pronunciation/) will develop normative specifications and best practices guidance collaborating with other W3C groups as appropriate, to provide for proper pronunciation in HTML content when using text to speech (TTS) synthesis. - -## Maturity Model Task Force - -The [Maturity Model Task Force](/about/groups/task-forces/maturity-model/) is to create an Accessibility Maturity Model (AMM) narrative and assessment tool in support of W3C standards and other related guidance, such as Web Content Accessibility Guidelines (WCAG) and Accessibility Rich Internet Applications (ARIA), in consultation with the APA Working Group. The Accessibility Maturity Model will assist organizations in building capacity to develop, and maintain, accessible products or services. \ No newline at end of file diff --git a/pages/about/groups/apawg/video-examples.md b/pages/about/groups/apawg/video-examples.md deleted file mode 100644 index 34d0d47af05..00000000000 --- a/pages/about/groups/apawg/video-examples.md +++ /dev/null @@ -1,65 +0,0 @@ ---- -title: APA Video Examples -permalink: /about/groups/apawg/video-examples/ -ref: /about/groups/apawg/video-examples/ -lang: en -github: - label: wai-groups ---- - -The following videos highlight the work being performed in APA and within our task forces. - -## WAI-Adapt Video Example - -The [WAI-Adapt Task Force](/about/groups/task-forces/adapt/) created a video to demonstrate a semantic overlay approach to enable user driven personalization, eg. the association of user-preferred symbols with elements having those semantics. - -### Video Recording - -**Web Support for People with Cognitive and Learning Disabilities** - - - -## Pronunciation Video Example - -The [Spoken Presentation Task Force](/about/groups/task-forces/pronunciation/) created a video to demonstrate proposed approaches for controlling pronunciation in spans of web content. - -### Video Recording - -**Pronunciation Matters** - - - - -## CSS Media Queries 5 and Personalization - March 10, 2021 - -A special presentation by Niklaus Schildhauer on **CSS Media Queries 5 Opportunities for Personalization and Implementation as Polyfill**. This was Nicklaus' Bachelor thesis for Mobile Media at the [Stuttgart Media University.](https://www.hdm-stuttgart.de/en) He was advised by Professor Dr. Gottfried Zimmermann. - -### Video Recording - - - -### Materials - -- Niklaus has shared his work via gitlab at [https://gitlab.mi.hdm-stuttgart.de/ns107/ba-mq5](https://gitlab.mi.hdm-stuttgart.de/ns107/ba-mq5) -- [Download his PowerPoint Presentation](https://gitlab.mi.hdm-stuttgart.de/ns107/ba-mq5/-/blob/master/docs/1_Presentation/20201118_Common_Terms.pptx) from the gitlab site. -- Links to Examples: - - [Video Streaming Website](https://gpii.eu/mq-5/example/video/) - - [Text Website Example](https://gpii.eu/mq-5/example/text/) - - [Registration Example](https://gpii.eu/mq-5/example/registration/) - -Note: Adopting Niklaus' additional Media Queries features will require us to resolve [CSS Issue 3488](https://github.com/w3c/csswg-drafts/issues/3488). diff --git a/pages/about/groups/ariawg.md b/pages/about/groups/ariawg.md index 3167a4a16a3..9c415099c62 100644 --- a/pages/about/groups/ariawg.md +++ b/pages/about/groups/ariawg.md @@ -1,9 +1,19 @@ --- -title: Accessible Rich Internet Applications (ARIA) Working Group -nav_title: 'ARIA: Accessible Rich Internet Applications WG' +title: ARIA Working Group +nav_title: 'ARIA WG' lang: en permalink: /about/groups/ariawg/ ref: /about/groups/ariawg/ +redirect_from: + - /about/groups/ariawg/communication/ + - /about/groups/ariawg/contribute/ + - /about/groups/ariawg/deliverables/ + - /about/groups/ariawg/editors/ + - /about/groups/ariawg/participate/ + - /about/groups/ariawg/planning/ + - /about/groups/ariawg/roadmap/ + - /about/groups/ariawg/task-forces/ + - /about/groups/ariawg/workflow/ github: label: wai-groups --- @@ -12,9 +22,7 @@ github: {% include box.html type="start" title="Summary" class="" %} {:/} -The mission of the Accessible Rich Internet Applications Working Group (ARIA WG) is to develop technologies that enhance accessibility of web content for people with disabilities. This includes continued development of the Accessible Rich Internet Applications (WAI-ARIA) suite of technologies and other technical specifications when needed to bridge known gaps. - -Some information on this page is also shown on, and may be more current in, the automatically generated [ARIA Working Group page](https://www.w3.org/groups/wg/aria/). +Find out about the activities of the Accessible Rich Internet Applications (ARIA) Working Group and how you can contribute to its mission. {::nomarkdown} {% include box.html type="end" %} @@ -33,66 +41,114 @@ Some information on this page is also shown on, and may be more current in, the {% include_cached toc.html type="end" %} {:/} -## Announcements +## Mission + +The mission of the ARIA Working Group is to enhance the accessibility of web content through developing supplemental attributes that can be applied to native host language interactive elements and exposed via platform accessibility application programming interfaces (APIs). + +## Charter + +To learn about the group’s focus, scope and deliverables, see the [ARIA Working Group Charter](https://www.w3.org/2025/01/aria-charter). + +## Current work + +For details of the current work, see the [ARIA Working Group README on GitHub](https://www.github.com/w3c/aria/#readme). + +The ARIA Working Group follows a set process for developing ARIA guidelines and resolving ARIA issues — for details, see [ARIA Working Group Process Document](https://github.com/w3c/aria/blob/main/documentation/process.md). + +### WAI-ARIA + +The [WAI-ARIA specification](https://www.w3.org/TR/wai-aria/) defines roles, states, and properties that can be used in a variety of host languages to enhance the accessibility of user interfaces. + +### WAI-ARIA modules + +The ARIA modules extend the roles, states, and properties for specific host languages, such as: + +* [Digital Publishing](https://www.w3.org/TR/dpub-aria-1.1/) +* [Graphics](https://www.w3.org/TR/graphics-aria-1.0/) +* [HTML](https://www.w3.org/TR/html-aria/) + +### ARIA Core Accessibility API Mappings + +The ARIA [Core Accessibility API Mappings](https://www.w3.org/TR/core-aam-1.2/) describe how user agents should expose semantics of web content languages to accessibility APIs. The mappings apply broadly to multiple technologies. In addition, the ARIA Working Group develops specific mappings for: + +* CSS +* [Digital Publishing](https://www.w3.org/TR/dpub-aam-1.1/) +* [Graphics](https://www.w3.org/TR/graphics-aam/) +* [HTML](https://www.w3.org/TR/html-aam-1.0/) +* MathML +* PDF +* [SVG](https://www.w3.org/TR/svg-aam-1.0/) + +### WAI-ARIA Authoring Practices + +The [ARIA Authoring Practices Guide](https://www.w3.org/WAI/ARIA/apg/) describes how to apply accessibility semantics to common design patterns and widgets, and provides overall guidance on how to use ARIA. -No announcements at the moment. +## Contribute to the work -## Current Work +W3C and the ARIA Working Group welcome input on ARIA work from the global accessibility community. -The Working Group has established a [road map](roadmap) for upcoming work. This road map is executed via [publications and status](deliverables), which include: +### Contribute without joining the group -- WAI-ARIA 1.3, -- WAI-ARIA modules for Digital Publishing and Graphics, -- Accessibility API Mappings for ARIA, Digital Publishing, HTML, and SVG, and -- WAI-ARIA Authoring Practices. +There are ways you can contribute without being a member of the working group: -The [ARIA Project Plan](/about/groups/ariawg/planning/) details intended timeline and milestones for this work and proceeds according to the [ARIA Working Group Work Flow](/about/groups/ariawg/workflow/). +* **Comment on publications:** During development, the group publishes working drafts for public comment — these are announced on the [WAI News pages](/news/) and on the [WAI Interest Group mailing lists](/about/groups/waiig/#mailinglist). +* **Raise, comment on, or propose fixes to ARIA issues:** If you’re aware of an issue with any of the published ARIA resources, W3C welcomes you to raise a new issue on GitHub, or you can also comment on and, even better, propose solutions for existing issues — see the list of [repositories maintained by the ARIA Working Group below](#github-repositories). +* **Contribute to ARIA discussions:** You may contribute your views to the ARIA Working Group's [open ARIA discussions in GitHub](https://github.com/w3c/aria/discussions) and [mailing list discussions](https://lists.w3.org/Archives/Public/public-aria/). -## Task Forces +### Become a participant in the group -The ARIA WG uses [task forces](task-forces) to focus work on specific projects. Current task forces include: +Joining the ARIA Working Group enables you to participate fully in the development of the work and influence the deliverables. You and your organization will also be listed as contributors, where appropriate. -- ARIA Authoring Practices Task Force: focuses on ARIA Authoring Practices. -- CSS Accessibility Task Force; focuses on accessibility of CSS, ARIA role is to explore ARIA and accessibility API mapping features. +Being a participant involves commitment to support the work of the group in the following ways: -## How to Comment, Contribute, and Participate +* Engage actively with other participants in the working group using the group’s communication channels. +* Keep up with weekly tasks and the progress of the work — for example, via the minutes of past meetings, mailing list discussions, and GitHub issue comments. +* Give your input promptly, when it’s needed. -The ARIA Working Group engages with stakeholders in a variety of ways. See the following resources for information on: +See [Instructions for joining the Accessible Rich Internet Applications Working Group](https://www.w3.org/groups/wg/aria/instructions/). -- [How to contribute to the Working Group, file comments, and contribute to the source code repositories](contribute); -- [How to participate in (join) the Working Group](https://www.w3.org/groups/wg/aria/instructions/). +## Group members and task forces -## Meetings and Communication +* [Chairs](https://www.w3.org/groups/wg/aria/participants/#chairs) +* [Current participants](https://www.w3.org/groups/wg/aria/participants/#participants) +* [Task forces](https://www.w3.org/groups/wg/aria/task-forces/) that support the ARIA Working Group -The ARIA WG conducts its work using a variety of synchronous and asynchronous tools. The [communication](/about/groups/ariawg/communication/) page provides details about: +## Communications and decisions -- Teleconferences of the Working Group and its task forces (also see [meeting minutes](https://www.w3.org/WAI/ARIA/minutes)); -- Face to face meetings (also see face to face [meeting pages](https://www.w3.org/WAI/ARIA/wiki/Meetings)); -- Email lists; -- [ARIA source repository](https://github.com/w3c/aria/); -- [Wiki](https://www.w3.org/WAI/ARIA/wiki/); -- [Web-Based Surveys (WBS)](https://www.w3.org//2002/09/wbs/83726/); -- [Issue Tracker](https://github.com/w3c/aria/issues); -- [ARIA source repository issue tracker](https://github.com/w3c/aria/issues). +* [Calendar of meetings](https://www.w3.org/groups/wg/aria/calendar/) +* [Minutes from previous meetings](https://www.w3.org/WAI/ARIA/minutes) +* [Mailing list archive](https://lists.w3.org/Archives/Public/public-aria/) +* Record of decisions (mainly in GitHub pull request reviews) +* [Decision policy](/about/groups/ariawg/decision-policy/) -These tools are used by participants of the Working Group. For ways non-participants can contribute, see [how to contribute to the Working Group and file comments](/about/groups/ariawg/contribute/). +## GitHub repositories -### Meeting Minutes +The ARIA Working Group maintains the following GitHub repositories: -[Minutes from previous meetings](https://www.w3.org/WAI/ARIA/minutes) are available. +- [Accessible Name and Description Computation](https://github.com/w3c/accname/) +- [ARIA](https://github.com/w3c/aria/) — for spec development +- [Core Accessibility API Mappings](https://github.com/w3c/core-aam/) +- [CSS Accessibility API Mappings](https://github.com/w3c/css-aam/) +- [Digital Publishing Accessibility API Mappings](https://github.com/w3c/dpub-aam/) +- [Digital Publishing WAI-ARIA Module](https://github.com/w3c/dpub-aria/) +- [Graphics Accessibility API Mappings](https://github.com/w3c/graphics-aam/) +- [HTML Accessibility API Mappings](https://github.com/w3c/html-aam/) +- [MathML Accessibility API Mappings](https://github.com/w3c/mathml-aam/) +- [PDF Accessibility API Mappings](https://github.com/w3c/pdf-aam) +- [SVG Accessibility API Mappings](https://github.com/w3c/svg-aam/) +- [WAI-ARIA Authoring Practices](https://github.com/w3c/aria-practices/) +- [WAI-ARIA Graphics Module](https://github.com/w3c/graphics-aria/) -## Administrative Information +## Publications and copyright -Work of the ARIA WG is in accordance with the [W3C Process](https://www.w3.org/Process). ARIA WG work is funded in part by the [WAI Core 2015 Project](https://www.w3.org/WAI/Core2015/). The work of this group does not necessarily reflect the views or policies of the funders. +* [List of technical reports published by the ARIA Working Group](https://www.w3.org/groups/wg/aria/publications/) +* [WAI-ARIA Authoring Practices Guide](https://www.w3.org/WAI/ARIA/apg/) -The chairs of the ARIA WG, responsible for overall leadership and management, are James Nurthen and Valerie Young. The staff contact, responsible for [W3C Process](https://www.w3.org/Process/) and general support, is [Daniel Montalvo](https://www.w3.org/staff#dmontalvo). +W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group — for details, see [Intellectual property rights — ARIA Working Group](https://www.w3.org/groups/wg/aria/ipr/). -The Accessible Rich Internet Applications Working Group maintains the following operational resources: +There are also instructions for [How to Make a Patent Disclosure](https://www.w3.org/groups/wg/aria/ipr/#discl-howto). -- [Decision policy](/about/groups/ariawg/decision-policy/); -- [Record of decisions made by the WG](https://www.w3.org/WAI/ARIA/wiki/Decisions); -- [meeting minutes](https://www.w3.org/WAI/ARIA/minutes). -W3C maintains a [public list of any patent disclosures](http://www.w3.org/2004/01/pp-impl/83726/status) made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. +## Contact the chairs -[Current participants in the ARIA WG](https://www.w3.org/groups/wg/aria/participants/). +If you have a question for the ARIA Working Group’s chairs or the W3C staff contact, email [group-aria-chairs@w3.org](mailto:group-aria-chairs@w3.org). \ No newline at end of file diff --git a/pages/about/groups/ariawg/communication.md b/pages/about/groups/ariawg/communication.md deleted file mode 100644 index 5fef7241df0..00000000000 --- a/pages/about/groups/ariawg/communication.md +++ /dev/null @@ -1,76 +0,0 @@ ---- -title: ARIA Communication -permalink: /about/groups/ariawg/communication/ -ref: /about/groups/ariawg/communication/ -lang: en -github: - label: wai-groups ---- - -{::nomarkdown} -{% include box.html type="start" title="Summary" class="" %} -{:/} - -The ARIA Working Group uses the following tools and procedures to perform its work. - -{::nomarkdown} -{% include box.html type="end" %} -{:/} - -{::options toc_levels="2..3" /} - -{::nomarkdown} -{% include_cached toc.html type="start" title="Page Contents" %} -{:/} - -- TOC is created automatically. -{:toc} - -{::nomarkdown} -{% include_cached toc.html type="end" %} -{:/} - -## Teleconferences - -The ARIA WG and its task forces participate in the following teleconferences. Unless otherwise mentioned, times are given in Boston time because the UTC time floats with U.S. Daylight Savings Time changes. Follow the link to convert to local time. Meetings take place on [Zoom](https://zoom.us), using the link given on the meeting name. [IRC](https://www.w3.org/wiki/IRC) is used for text chat and [minute taking](http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm?content-type=text/html). It is not expected that participants will join all meetings; instead please strive to be a regular participant in the meeting(s) of greatest relevance to your work in the group. - -- **[ARIA Authoring Practices](https://www.w3.org/groups/tf/aria-practices/calendar)**: Tuesdays at 14:00 until 15:00 Boston time -- **[ARIA Editors](https://www.w3.org/groups/tf/aria-editors/calendar)**: alternate Mondays at 12:00 until 12:30 Boston time -- **ARIA Plan**: Tuesdays at 13:00 until 14:00 Boston time -- **[ARIA Working Group](https://www.w3.org/groups/wg/aria/calendar)**: Thursdays at 12:00 until 14:00 Boston time - -[Minutes of past teleconferences](https://www.w3.org/WAI/ARIA/minutes) are available. - -## Face to Face Meetings - -[Previous meetings](https://www.w3.org/WAI/ARIA/wiki/Meetings) of the ARIA WG are available. - -## Email lists - -- **public-aria@w3.org** - Working Group discussion list; public archive; public can post; inquire to subscribe ([public-aria archives](http://lists.w3.org/Archives/Public/public-aria/)). -- **public-aria-admin@w3.org** - Working Group decision list; public archive; must be WG member to post or subscribe ([public-aria-admin archives](http://lists.w3.org/Archives/Public/public-aria-admin/)). -- **public-aria-test@w3.org** - Public discussion list for people working on ARIA testing; anyone may post or subscribe ([public-aria-test archives](http://lists.w3.org/Archives/Public/public-aria-test/)). -- **wai-xtech@w3.org** - Public discussion list on technical topics in web accessibility and where specification review announcements and submissions are copied; public archive; anyone may post or subscribe ([wai-xtech archives](http://lists.w3.org/Archives/Public/wai-xtech/)). -- **w3c-wai-ig@w3.org** - Announcements only Working Group activities; public archive; anyone may post or subscribe ([w3c-wai-ig archives](http://lists.w3.org/Archives/Public/w3c-wai-ig/)). - -## Source repository - -Publications under development are maintained in the [ARIA GitHub repository](https://github.com/w3c/aria/). This distributed source control system allows multiple people to edit simultaneously, public view of changes as they are committed, and "pull requests" to enable people without direct commit access to suggest contributions. Publication editors are designated by the WG chair and have direct commit access. Editors commit to execute the group consensus, request review of non-editorial changes, process conflicting input (from issues, pull requests, and discussions) in a neutral manner, and maintain document quality. - -## IRC - -W3C Working Groups use [IRC](https://www.w3.org/wiki/IRC) for synchronous text chat and, with the aid of some IRC bots, to record minutes of teleconferences. The ARIA WG uses the following IRC channels. They are available at any time but are only routinely logged during teleconferences. - -- [#aria](irc://irc.w3.org/aria) for the main Working Group. -- [#aria-apg](irc://irc.w3.org/aria-apg) for the ARIA Practices Task Force. -- [#aria-editors](irc://irc.w3.org/aria-editors) for the ARIA Editors Task Force. - -## Other - -The ARIA WG uses the following web-based resources as well: - -- [Wiki](https://www.w3.org/WAI/ARIA/wiki/), to develop or record content not immediately intended for formal publication. This is writeable by WG members and publicly readable. -- [Web-Based Surveys (WBS)](http://www.w3.org/2002/09/wbs/83726/), to measure aggregate group opinion. These can be completed by WG members with publicly readable results. -- [Issue Tracker](https://www.github.com/w3c/aria/issues/), to track issues and action items. This is maintainable by WG members and publicly readable. -- [Bugzilla](https://www.w3.org/Bugs/Public/), to track issues specific to publications. This shared tool allows some collaboration with other W3C groups, but in general is not actively used by the WG. Users with a [W3C Bugzilla account](https://www.w3.org/Bugs/Public/createaccount.cgi) can file or comment on issues, and bugs are publicly readable. -- GitHub Issues, to track issues for publications maintained in the [GitHub repositories](/about/groups/ariawg/contribute/#github). Users with a [GitHub account](https://github.com/) can file or comment on issues, and issues are publicly readable. \ No newline at end of file diff --git a/pages/about/groups/ariawg/contribute.md b/pages/about/groups/ariawg/contribute.md deleted file mode 100644 index 5a5d7003b6a..00000000000 --- a/pages/about/groups/ariawg/contribute.md +++ /dev/null @@ -1,73 +0,0 @@ ---- -title: ARIA Contribution -permalink: /about/groups/ariawg/contribute/ -ref: /about/groups/ariawg/contribute/ -lang: en -github: - label: wai-groups ---- - -{::nomarkdown} -{% include box.html type="start" title="Summary" class="" %} -{:/} - -There are a number of ways non-participants in the ARIA WG can contribute to the work. If you wish to be an active contributer you should [join the Working Group](https://www.w3.org/groups/wg/aria/instructions/). - -{::nomarkdown} -{% include box.html type="end" %} -{:/} - -{::options toc_levels="2,3,4" /} - -{::nomarkdown} -{% include_cached toc.html type="start" title="Page Contents" %} -{:/} - -- TOC is created automatically. -{:toc} - -{::nomarkdown} -{% include_cached toc.html type="end" %} -{:/} - - - -## Public Comments - -The ARIA WG accepts public comments on publications on the [public-aria](http://lists.w3.org/Archives/Public/public-aria/) list. This is primarily used for input on formal publications. - -## Github Issues and pull requests - -Technical work is done in a set of GitHub repositories. Pull Requests are open to the main w3c/aria repository. Issues are open to the child spec repos. See below for details. - -Work follows the [ARIA Process](https://github.com/w3c/aria/blob/main/documentation/process.md) document. - -Repositories maintained by the ARIA Working Group include: - -- [w3c/aria](https://github.com/w3c/aria/) for spec development; -- [w3c/core-aam](https://github.com/w3c/core-aam/) for issues related to Core Accessibility API Mappings; -- [w3c/accname](https://github.com/w3c/accname/) for issues related to Accessible Name and Description Computation; -- [w3c/dpub-aria](https://github.com/w3c/dpub-aria/) for issues related to Digital Publishing WAI-ARIA Module; -- [w3c/dpub-aam](https://github.com/w3c/dpub-aam/) for Digital Publishing Accessibility API Mappings; -- [w3c/graphics-aria](https://github.com/w3c/graphics-aria/) for issues related to WAI-ARIA Graphics Module; -- [w3c/graphics-aam](https://github.com/w3c/graphics-aam/) for issues related to Graphics Accessibility API Mappings; -- [w3c/svg-aam](https://github.com/w3c/svg-aam/) for issues related to SVG Accessibility API Mappings, now developed by the [SVG Working Group](http://www.w3.org/Graphics/SVG/WG/); -- [w3c/html-aam](https://github.com/w3c/html-aam/) for issues related to HTML Accessibility API Mappings, now developed by the [Web Platform Working Group](http://www.w3.org/WebPlatform/WG/); -- [w3c/css-aam](https://github.com/w3c/css-aam/) for issues related to CSS Accessibility API Mappings, with the [CSS Accessibility Task Force](/about/groups/task-forces/css-a11y/); -- [w3c/aria-practices](https://github.com/w3c/aria-practices/) for WAI-ARIA Authoring Practices, with the [ARIA Authoring Practices Task Force](/about/groups/task-forces/practices/); -- [w3c/aria-at](https://github.com/w3c/aria-at/) for Assistive Technology ARIA Experience Assessment, with the [ARIA and Assistive Technologies Community Group](https://www.w3.org/community/aria-at/); - -A [GitHub account](http://github.com/) is required for the following functionality. In addition to using the comments list described above to submit input, you may: - -- [Watch the repository](https://help.github.com/articles/watching-repositories/); -- [File issues](https://guides.github.com/features/issues/); -- Submit [pull requests](https://help.github.com/articles/using-pull-requests/). - -## Mailing list discussions - -If you would like to monitor the work of the ARIA WG and contribute on-line, you may subscribe to the following mailing lists. You will not be considered a formal participant but may comment and contribute. The ARIA WG uses the following mailing lists: - -- **public-aria@w3.org** - Working Group discussion list; public archive; public can post; inquire to subscribe ([public-aria archives](http://lists.w3.org/Archives/Public/public-aria/)). -- **public-aria-practices@w3.org** - discussion list for Authoring Practices Task Force; anyone may post or subscribe ([public-aria-practices archives](http://lists.w3.org/Archives/Public/public-aria-practices/)) -- **public-aria-test@w3.org** - Public discussion list for people working on ARIA testing; anyone may post or subscribe ([public-aria-test archives](http://lists.w3.org/Archives/Public/public-aria-test/)). -- **w3c-wai-ig@w3.org** - Announcements only Working Group activities; public archive; anyone may post or subscribe ([w3c-wai-ig archives](http://lists.w3.org/Archives/Public/w3c-wai-ig/)). \ No newline at end of file diff --git a/pages/about/groups/ariawg/decision-policy.md b/pages/about/groups/ariawg/decision-policy.md index fa79c60eddb..74831421188 100644 --- a/pages/about/groups/ariawg/decision-policy.md +++ b/pages/about/groups/ariawg/decision-policy.md @@ -1,5 +1,5 @@ --- -title: ARIA Decision Policy +title: ARIA Working Group Decision Policy permalink: /about/groups/ariawg/decision-policy/ ref: /about/groups/ariawg/decision-policy/ lang: en @@ -7,7 +7,7 @@ github: label: wai-groups --- -This document explains the decision process of the Accessible Rich Internet Applications Working Group. +This document explains the decision process of the [Accessible Rich Internet Applications (ARIA) Working Group](https://www.w3.org/groups/wg/aria/). There are often divergent opinions on issues. It is important that all views are expressed and considered, but it is critical to Working Group function that it can come to conclusions. The procedures set out here describe how the WG discusses a topic and forms a decision, preferably by [consensus](https://www.w3.org/Consortium/Process/#Consensus). These procedures are designed to ensure that input is considered, whether in teleconferences or using asynchronous communication tools. diff --git a/pages/about/groups/ariawg/deliverables.md b/pages/about/groups/ariawg/deliverables.md deleted file mode 100644 index aa7ab94856e..00000000000 --- a/pages/about/groups/ariawg/deliverables.md +++ /dev/null @@ -1,154 +0,0 @@ ---- -title: "Deliverables" -permalink: /about/groups/ariawg/deliverables/ -ref: /about/groups/ariawg/deliverables/ -lang: en -github: - label: wai-groups ---- - -WAI-ARIA, the Accessible Rich Internet Applications Suite, defines a way to make Web content and Web applications more accessible to people with disabilities. It especially helps with dynamic content and advanced user interface controls developed with Ajax, HTML, JavaScript, and related technologies. The [ARIA Project Plan](project) details intended timeline and milestones for this work. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
DeliverableDescriptionStatusEditors' DraftFormal Version
ARIA Core Specifications
Accessible Rich Internet Applications (WAI-ARIA) 1.1This specification provides an ontology of roles, states, and properties that set out an abstract model for accessible interfaces and can be used to improve the accessibility and interoperability of Web Content and Applications. This information can be mapped to accessibility frameworks that use this information to provide alternative access solutions. Similarly, this information can be used to change the rendering of content dynamically using different style sheet properties. The result is an interoperable method for associating behaviors with document-level markup.In Working Drafts; Approaching readiness for CREditors' draft of Accessible Rich Internet Applications (WAI-ARIA) 1.1Formal published version of Accessible Rich Internet Applications (WAI-ARIA) 1.1
Core Accessibility API Mappings 1.1Describes how user agents should map WAI-ARIA features to platform accessibility APIs. Other Accessibility API Mappings specifications depend on and extend this Core specification for specific technologies, including native techology features and WAI-ARIA extensions.In Working Drafts; Approaching readiness for CREditors' draft of Core Accessibility API Mappings 1.1Formal published version of Core Accessibility API Mappings 1.1
Accessible Name and Description: Computation and API Mappings 1.1Describes how user agents determine names and descriptions of accessible objects from web content languages and expose them in accessibility APIs.In Working Drafts; Approaching readiness for CREditors' draft of Accessible Name and Description: Computation and API Mappings 1.1Formal published version of Accessible Name and Description: Computation and API Mappings 1.1
Accessible Rich Internet Applications (WAI-ARIA) 2.0Work to begin after ARIA 1.1 wraps up
ARIA Extensions
Digital Publishing WAI-ARIA Module 1.0Defines a WAI-ARIA module encompassing an ontology of roles, states and properties specific to the digital publishing industry. This allows an author to convey user interface behaviors and structural information to assistive technologies and to enable semantic navigation, styling and interactive features used by readers. It is expected this will complement HTML5.In Working DraftsEditors' draft of Digital Publishing WAI-ARIA Module 1.0Formal published version of Digital Publishing WAI-ARIA Module 1.0
Graphics WAI-ARIA Module 1.0Defines a WAI-ARIA module of roles, states, and properties specific to web graphics. These semantics allow an author to convey user interface behaviors and structural information to assistive technologies and to enable semantic navigation, styling and interactive features used by readers. It is expected this will complement HTML5 and SVG2.In Editors' Drafts, FPWD anticipated soonEditors' draft of Graphics WAI-ARIA Module 1.0Formal published version of WAI-ARIA Graphics Module 1.0
Cognitive WAI-ARIA Module 1.0Work not yet begun
WAI-ARIA Interaction Module 1.0Work not yet begun
Accessibility API Mapping Extensions
Digital Publishing Accessibility API Mappings 1.1This document describes how user agents maps digital publishing markup to platform accessibility APIs based on the Core Accessibility API Mappings specification for user agents.In Editors' DraftsEditors' draft of Digital Publishing Accessibility API Mappings 1.0Formal published version of Digital Publishing Accessibility API Mappings 1.0
HTML Accessibility API Mappings 1.1This document describes how user agents map HTML5.1 [[!HTML51]] elements and attributes to platform accessibility API roles, states and properties on a variety of platforms, based on the Core Accessibility API Mappings specification for user agents. This document is designed to leverage these core mappings for the HTML5.1 host language.In Working DraftsEditors' draft of HTML Accessibility API Mappings 1.0Formal published version of HTML Accessibility API Mappings 1.0
SVG Accessibility API Mappings 1.1This document describes how user agents maps SVG2 markup to platform accessibility APIs based on the Core Accessibility API Mappings specification for user agents.In Working DraftsEditors' draft of SVG Accessibility API Mappings 1.0Formal published version of SVG Accessibility API Mappings 1.0
ARIA Support Resources
Requirements for Accessible Rich Internet Applications 1.1This roadmap that describes the problem, what W3C specifications will be used to correct the problem, and the timeline for the new specifications.Work not yet begunEditors' draft of Requirements for Accessible Rich Internet Applications 1.1
WAI-ARIA Authoring Practices 1.1Provides recommended approaches to create accessible Web content using WAI-ARIA roles, states, and properties to make widgets, navigation, and behaviors accessible. Also describes considerations that might not be evident to most implementors from the WAI-ARIA specification alone.in Working DraftsEditors' draft of WAI-ARIA Authoring Practices 1.1Formal published version of WAI-ARIA Authoring Practices 1.1
Using WAI-ARIA in HTMLPractical guide for developers on how to add accessibility information to HTML elements using the WAI-ARIA 1.1 in HTML 5.1, which especially helps with dynamic content and advanced user interface controls developed with Ajax, HTML, JavaScript, and related technologies.In Working DraftsEditors' draft of Using WAI-ARIA in HTMLFormal published version of Using WAI-ARIA in HTML
User Context Properties
User Context Properties 1.0defines a set of preferences that users can choose to expose to web applications. Web applications can use this information to optimize the presentation without a requirement to target a specific device, operating system, or locale.Handover from IndieUI WG not yet completed
- -Also see the [WAI-ARIA Overview Page](/WAI/intro/aria). Editors' sources for the above specifications are maintained in the [W3C ARIA GitHub repository](https://github.com/w3c/aria/). GitHub users can watch this repository and send pull requests. diff --git a/pages/about/groups/ariawg/editors.md b/pages/about/groups/ariawg/editors.md deleted file mode 100644 index e3e0404682c..00000000000 --- a/pages/about/groups/ariawg/editors.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -title: ARIA Editors -permalink: /about/groups/ariawg/editors/ -ref: /about/groups/ariawg/editors/ -lang: en -github: - label: wai-groups ---- - -Editors of specifications for the ARIA Working Group coordinate using resources detailed here. - -## Mailing lists - -ARIA editors use the public-aria-editors@w3.org mailing list ([mailing list archives](http://lists.w3.org/Archives/Public/public-aria-editors/)) for email discussion. Participants are added to this list when appointed as editor of an ARIA WG deliverable. - -## Teleconferences - -- **[ARIA Editors](https://www.w3.org/groups/tf/aria-editors/calendar/)**: Second and fourth Wednesdays at 12:00 until 12:30 Boston time - -## Meeting minutes - -[Minutes from previous meetings](https://www.w3.org/WAI/ARIA/editors/minutes) are available. - -## Style guides - -The ARIA editors use the following resources to ensure the quality of technical specifications: - -- [QA Checklist](https://www.w3.org/WAI/PF/editors/qa) (old resource) - a list of the points we attend to to ensure quality of the ARIA specifications. -- [Editorial style guide](https://www.w3.org/WAI/PF/editors/style_editorial) (old resource) - guidelines to ensure editorial consistency. -- [Technical style guide](https://github.com/w3c/aria/#user-content-editorial-documentation) in the aria repository readme - coding practices to support document automation. \ No newline at end of file diff --git a/pages/about/groups/ariawg/participate.md b/pages/about/groups/ariawg/participate.md deleted file mode 100644 index d7a1a80a4b2..00000000000 --- a/pages/about/groups/ariawg/participate.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -title: APA Participation -permalink: /about/groups/ariawg/participate/ -ref: /about/groups/ariawg/participate/ -lang: en -github: - label: wai-groups ---- - -This page explains the requirements and procedures for becoming a participant in the ARIA WG. See also [Participating in WAI](http://www.w3.org/WAI/participation) for broader participation options throughout the Web Accessibility Initiative (WAI). Participation enables you to influence the development of the deliverables, and you and your organization will be listed as contributors to the deliverables of the ARIA WG where appropriate. Participant status, however, requires a commitment on your behalf to support the work of the group. - -Participating in the Working Group requires a W3C account; you can [create an account](https://www.w3.org/accounts/request) if you do not already have one. Before applying to join, please read the [ARIA WG Charter](https://www.w3.org/WAI/ARIA/charter) to review the activity and commitments. When you join the group, you are automatically added to the [mailing lists](/about/groups/ariawg/contribute/#mailing-list-discussions) and provide accessed to the WG [communication tools](/about/groups/ariawg/communication/). - -[Current participants in the ARIA WG](https://www.w3.org/2000/09/dbwg/details?group=83726&public=1). - -## Employees of Member organizations - -Employees of Member organizations automatically have the right to participate. To join, ask your [W3C Advisory Committee (AC) Representative](https://www.w3.org/Member/ACList) to [nominate you to the Working Group](http://www.w3.org/2004/01/pp-impl/83726/join). You can also use available [public contribution channels](/about/groups/ariawg/contribute/) without joining the group if you or your employer prefer. - -## Individuals - -If you do **not** work for a [W3C Member organization](http://www.w3.org/Consortium/Member/List), but you feel you have the expertise and availability to participate, you should first use [public contribution channels](/about/groups/ariawg/contribute/) to familiarize yourself with the work and make yourself known to the group. If your contribution suggests a higher level of participation is warranted, you can be invited to join the group as an Invited Expert. Please [contact the WG chairs](mailto:group-aria-chairs@w3.org) to discuss this. If you work for an organization whose business is related to that of the W3C, we may instead ask your organization to join and nominate you as a Member representative. - -If the chairs support it, you may complete the [invited expert application](https://www.w3.org/ieapp/new) form, indicating the Accessible Rich Internet Applications WG as the group you wish to join. Make sure you have read and accepted the policies referenced from that form, and include details about your relevant expertise, interest in the work, and your employer. _If you have not made yourself known to the chairs, or your application does not provide information about your expertise and expected contribution, it may be rejected._ \ No newline at end of file diff --git a/pages/about/groups/ariawg/planning.md b/pages/about/groups/ariawg/planning.md deleted file mode 100644 index 3ad17d4ab0d..00000000000 --- a/pages/about/groups/ariawg/planning.md +++ /dev/null @@ -1,171 +0,0 @@ ---- -title: ARIA Project Plan -permalink: /about/groups/ariawg/planning/ -ref: /about/groups/ariawg/planning/ -lang: en -github: - label: wai-groups ---- - -The [Working Group charter](https://www.w3.org/WAI/ARIA/charter#milestones) proposed initial milestones. Updates to those milestones are provided here. Deliverables with an asterisk at the beginning are considered critical to the success of the Working Group. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Milestones -
- Specification - - Status (22 September 2023) - - Projection -
- FPWD - - CRD - - CRS - - PR - - Rec -
- * WAI-ARIA 1.2 [WAI-ARIA Editors' Draft] - - W3C Recommendation - - 19 July 2018 - - 8 Dec 2021 - - 28 March 2023 - - 6 June 2023 -
- * Core Accessibility API Mappings [Core-AAM Editors' Draft] - - Living Standard - - 19 July 2018 - - 22 November 2022 - - Q3 2023 -
- * Accessible Name and Description: Computation and API Mappings 1.1 [AccName-AAM Editors' Draft] - - Living standard -- Waiting on changes needed for ARIA 1.3 - - 11 July 2019 - - Q2 2023 -
- HTML Accessibility API Mappings [HTML-AAM Editors' Draft] - - Living standard - - 7 April 2015 - - Q2 2023 -
- Digital Publishing WAI-ARIA module [DPub ARIA Editors' Draft] - - 26 August 2021 - - Q3 2023 -
- Digital Publishing WAI-ARIA Accessibility API Mappings [DPub-AAM Editors' Draft] - - Living standard - - 30 November 2021 - - Q3 2023 -
- SVG Accessibility API Mappings [SVG-AAM Editors' Draft] - - Living standard - - 26 February 2015 - - Q3 2023 -
\ No newline at end of file diff --git a/pages/about/groups/ariawg/roadmap.md b/pages/about/groups/ariawg/roadmap.md deleted file mode 100644 index 0d5ceaaf424..00000000000 --- a/pages/about/groups/ariawg/roadmap.md +++ /dev/null @@ -1,54 +0,0 @@ ---- -title: ARIA Working Group Road Map -permalink: /about/groups/ariawg/roadmap/ -ref: /about/groups/ariawg/roadmap/ -lang: en -github: - label: wai-groups ---- - -## Introduction - -This road map describes the current and planned work to be accomplished by the ARIA Working Group. The targets found herein are based on the version of the relevant specification. In order to determine the intended delivery date, please see the [ARIA Project Plan](/about/groups/ariawg/planning/). - -## Achieve Parity with Native Host Language Semantics - -There is currently not complete parity between ARIA modules and native host languages used on the web. Where this parity is lacking, authors find it quite challenging to _efficiently_ create the accessible experience afforded by the native host language sementics. Because some authors prefer to create their own custom interfaces rather than use the corresponding host language, the ARIA Working Group believes it is important to address this need. Work in this area will also be needed to implement accessibility support for custom elements. Parity between the native host language and ARIA also makes it possible for the associated native host language's Accessibility API Mappings specification to map its attributes to those from ARIA. This in turn leads to a more consistent experience for end users, for whom the underlying native host language is largely (if not entirely) irrelevant. - -- Add new roles to achieve parity with HTML elements (Target: ARIA 1.2) -- Add new states and properties to achieve parity with HTML attributes (Target: ARIA 1.3) -- Evaluate the need for parity with additional host languages and implement as appropriate (Target: Ongoing) - -## Provide Support for the Accessibility Object Model - -The [Accessibility Object Model](https://wicg.github.io/aom/) (AOM) is a JavaScript API to allow developers to interact with the accessibility tree associated with web content. As stated in the [Explainer](https://wicg.github.io/aom/explainer.html): "This API is will be primarily of interest to the relatively small number of developers who create and maintain the JavaScript frameworks and widget libraries that power the vast majority of web apps... This API is also aimed at developers of large flagship web apps that push the boundaries of the web platform. These apps tend to have large development teams who look for unique opportunities to improve performance using low-level APIs like Canvas." - -The ARIA Working Group agreed at TPAC 2017 to support this effort by adding features to ARIA needed by AOM. This support will include: - -- Add ARIA property string reflection on Element (Target: ARIA 1.2) -- Other items to be determined as work on AOM progresses (Target: Ongoing) - -## Develop and Maintain Additional ARIA Features for Authors and End Users - -In addition to the work described above, the ARIA Working Group will continue developing, maintaining, and documenting ARIA features authors can use to make their content more accessible to end users. Much of this work will be done on an ad-hoc basis based on feedback from authors and implementors. As such, work in this area will not be itemized here unless it entails a significant amount of effort. Generally speaking, however, the Working Group will: - -- Add and/or modify ARIA features based on feedback from authors (Target: Ongoing) -- Map new and modified features to platform accessibility APIs (Target: Ongoing) -- Update platform accessibility API mappings specifications maintained by this Working Group when the platform APIs change (Target: Ongoing) -- Write authoring guidance for new and modified features (Target: Ongoing) -- Collaborate with user agent implementors and assistive technology developers to maximize interoperability (Target: Ongoing) - -Specific items that the Working Group plans to accomplish, which will entail a non-trivial amount of effort include: - -- Develop an alternative solution to replace the now-deprecated ARIA drag-and-drop features (Target: 1.4) -- Add support for annotations (Target: 1.4) -- Add control patterns that enable programmatic declaration of interaction methods supported by a widget. (Target: 2.0) -- Create means to set ARIA attribute values through platform accessibility APIs (Target: 2.0) - -## Ensure Consistency in Platform Accessibility API Mappings - -The Working Group believes a consistent (host-language-independent) user experience is desirable. The simplest way to achieve that is to ensure elements are exposed to assistive technologies in a consistent fashion regardless of the native host language chosen by the author. Exposure to assistive technologies is defined in the platform Accessibility API Mappings specifications, not all of which are developed and maintained by the ARIA Working Group. In order to maximize the likelihood of a consistent user experience, the Working Group will: - -- Review Accessibility API Mapping specifications produced by other Working Groups (Target: Ongoing) -- Create and maintain solutions for automated accessibility API-based testing of the exposure of roles, states, and properties of elements in native host languages (Target: Ongoing) -- Identify host languages for which there are no associated Accessibility API Mappings specification and collaborate with the Working Group that maintains that language to determine what solution, if any, is appropriate (Target: Ongoing) \ No newline at end of file diff --git a/pages/about/groups/ariawg/task-forces.md b/pages/about/groups/ariawg/task-forces.md deleted file mode 100644 index 66fe021135c..00000000000 --- a/pages/about/groups/ariawg/task-forces.md +++ /dev/null @@ -1,44 +0,0 @@ ---- -title: ARIA Task Forces -permalink: /about/groups/ariawg/task-forces/ -ref: /about/groups/ariawg/task-forces/ -lang: en -github: - label: wai-groups ---- - -{::options toc_levels="2..3" /} - -{::nomarkdown} -{% include_cached toc.html type="start" title="Page Contents" %} -{:/} - -- TOC is created automatically. -{:toc} - -{::nomarkdown} -{% include_cached toc.html type="end" %} -{:/} - -The ARIA Working Group conducts some of its work via the following task forces. See each task force page for details about specific work and how to join. - -## ARIA Authoring Practices Task Force - -The [ARIA Authoring Practices task force](/about/groups/task-forces/practices/) to develop WAI-ARIA Authoring Practices, which describes considerations that might not be evident to most authors from the WAI-ARIA specification alone and recommends approaches to make widgets, navigation, and behaviors accessible using WAI-ARIA roles, states, and properties. - - -## WAI-Adapt Task Force - -The [WAI-Adapt Task Force](/about/groups/task-forces/adapt/) has been moved to the APA Working Group. - -## WAI-ARIA User Agent Implementation Task Force - -The WAI-ARIA User Agent Implementation Task Force has closed. - -## SVG Accessibility Task Force - -This task force has closed. - -## Digital Publishing ARIA Task Force - -This task force has closed. diff --git a/pages/about/groups/ariawg/workflow.md b/pages/about/groups/ariawg/workflow.md deleted file mode 100644 index 35ec453e3ed..00000000000 --- a/pages/about/groups/ariawg/workflow.md +++ /dev/null @@ -1,54 +0,0 @@ ---- -title: ARIA Working Group Work Flow -permalink: /about/groups/ariawg/workflow/ -ref: /about/groups/ariawg/workflow/ -lang: en -github: - label: wai-groups ---- - -## Introduction - -Historically, the ARIA Working Group placed its primary focus on defining all of the features intended for authors, leaving platform accessibility API mappings, implementations, testing, and authoring guidance as tasks to be completed after those features had been defined and the associated specification entered Candidate Recommendation. This approach proved problematic: - -- Discovering disconnects between what the feature developers want and what implementors want after the specification(s) had entered Candidate Recommendation. -- Discovering critical bugs blocking implementation after the specification(s) had entered Candidate Recommendation. -- Discovering mapping errors after the specification(s) had entered Candidate Recommendation. -- Failing to achieve the milestones defined in the Working Group's charter. -- Failing to ensure the Working Group has "buy in" from all stakeholders, including authors, user agent implementors, and assistive technology developers. - -In order to minimize the occurrence of such problems in the future, the ARIA Working Group agreed to adopt a work flow proposed at TPAC 2017 designed to see each proposed feature through to completion, with ARIA features, mappings, implementation, testing, and authoring guidance happening together. That agreed-upon work flow is described in this document. - -## Work flow - -For each ARIA feature: - -1. Create / modify a single ARIA feature in a working branch of the specification repository. -2. Obtain platform mappings for that feature from platform mapping maintainers and add in a working branch of the mappings repository. -3. Create test file(s) for that feature and add to the [web-platform-tests repository](https://github.com/w3c/web-platform-tests). -4. Execute tests and obtain test results for that feature and add to the [test-results repository](https://github.com/w3c/test-results). -5. If tests report failures, double-check that the mapping, test file, and test methodology are correct. If so, file bugs against user agents for that feature and track progress via periodic retesting. -6. Solicit assistive technology implementations for that feature. -7. Write authoring guidance for that feature in a working branch of the authoring practices repository. -8. When a feature meets the [criteria for readiness](#criteria-for-readiness-of-an-aria-feature), merge working branch related to the feature into the stable branch of the respective repositories. - -## Criteria for "Readiness" of an ARIA Feature - -- Positive confirmation of acceptance by a sufficient number of user agent implementors in the form of a passing test result or a comment in a public issue tracker that they intend to implement as described in the specifications. "Sufficient" will depend on the anticipated exit criteria of the associated specification(s). -- Positive confirmation of acceptance by multiple assistive technology vendors in the form of implementing support, or a comment in a public issue tracker that they intend to implement support. -- Confirmation by the Authoring Practices task force that there are no unanticipated problems with the feature. - -## Implications of the Work Flow on Drafts and Branches - -Specifications and Notes should, as a general rule, follow this approach to including features and maintaining branches: - -- Features still in development with respect solely to the document in which they are contained should be committed to a feature-specific branch in the repository for that document. -- Features which are complete with respect solely to the document in which they are contained should be committed to the "master" branch in the repository for that document. The "master" branch serves as the source for Editor's Draft snapshots. -- Features which are "ready" (as defined above) should be cherry-picked from the "master" branch to the "stable" branch in each of the relevant repositories (e.g. ARIA, Accessibility API Mappings, and Authoring Practices). The "stable" branch serves as the source for publishing Working Draft revisions. -- When a given document becomes feature frozen due to entering Candidate Recommendation or becoming a Note, a branch for the version (e.g. "1.1") should be created so that work can continue on the next dot release of that document. - -## Version Completion and Advancement to Candidate Recommendation - -- The specification is ready to transition to Candidate Recommendation when all in-scope features have been completed OR a target milestone deadline has been reached. -- The Candidate Recommendation will contain all features that have been incorporated into the stable branch at the time of transition. -- Unless implementation problems are discovered during the Candidate Recommendation that were not caught in the initial development and testing workflow, the group will request transition to Proposed Recommendation after approximately 45 days. \ No newline at end of file diff --git a/pages/about/groups/ig.md b/pages/about/groups/ig.md index 10115185220..dc79dc692f5 100644 --- a/pages/about/groups/ig.md +++ b/pages/about/groups/ig.md @@ -1,6 +1,6 @@ --- -title: WAI Interest Group (WAI IG) -nav_title: 'WAI IG: WAI Interest Group' +title: Web Accessibility Initiative Interest Group +nav_title: 'WAI Interest Group' lang: en permalink: /about/groups/waiig/ ref: /about/groups/waiig/ @@ -8,6 +8,16 @@ github: label: wai-groups --- +{::nomarkdown} +{% include box.html type="start" title="Summary" class="" %} +{:/} + +The WAI Interest Group is a public forum with mailing lists for sharing information and exchanging ideas about W3C’s digital accessibility work. + +{::nomarkdown} +{% include box.html type="end" %} +{:/} + {::options toc_levels="2,3" /} {::nomarkdown} @@ -21,145 +31,100 @@ github: {% include_cached toc.html type="end" %} {:/} -## Introduction - -The Web Accessibility Initiative (WAI) Interest Group (IG) promotes awareness of, and engagement in, accessibility work throughout the World Wide Web Consortium (W3C). More details are in [About WAI IG below](#about-wai-ig). - -**Other Interest Group Pages:** - -- [Charter](/WAI/IG/20200804) -- [Discussion E-mail List Archives](http://lists.w3.org/Archives/Public/w3c-wai-ig/) -- [Announcements E-mail List Archives](http://lists.w3.org/Archives/Public/public-wai-announce/) - -## Mailing Lists {#mailinglist} - -There are two mailing lists: -1. **Announcements list (public-wai-announce)** — for WAI announcements only. -2. **Discussion list (w3c-wai-ig)** — for WAI announcements and public discussion. All e-mails sent to the Announcements list will also go to this Discussion list, so you don't need to subscribe to both lists. If you want to send messages to the list, you must send them from an e-mail address that is subscribed to the list. - -Details are below. - -### Announcements List - Subscribing and Unsubscribing - -* To subscribe, send e-mail to public-wai-announce-request@w3.org with subject: “subscribe”. -* To unsubscribe, send e-mail to public-wai-announce-request@w3.org with subject: “unsubscribe”. - -You can also see the [Announcements List Archives](http://lists.w3.org/Archives/Public/public-wai-announce/). - -### Using the Discussion List - -[Discussion List Archives](http://lists.w3.org/Archives/Public/w3c-wai-ig/) are useful for -searching for past messages and getting a feel for the list. - -- E-mail messages should **contribute to a comfortable, constructive - exchange** of ideas to advance web accessibility. Before you send - an e-mail, think about how it will come across to the people around the world who are on the list and who can read your publicly-archived message. - - **Be respectful.** Be positive. Be open to different perspectives. - - **Provide constructive information.** Focus on developing potential solutions, rather than just complaining. - - Focus on ideas, not participants. Avoid personal attacks, naming calling, and such. - - Explain the issue clearly. Provide sufficient background information. - - **See additional guidancce in W3C's Code of Ethics and Professional Conduct: [Positive Work Environment at W3C: Code of Ethics and Professional Conduct](https://www.w3.org/Consortium/cepc/)** -- Make sure e-mails are related web accessibility and are appropriate - for the WAI IG list. - - If you have questions about whether or not a message is - appropriate for the WAI IG list, contact - **[Shawn](http://w3.org/People/Shawn/)**. - - When your comments are not useful for the entire list, **reply - off-list** — that is, reply directly to the sender and do not - send the message to the list. - - No soliciting. -- Formatting messages: - - Use a Subject line that describes the topic well. If you change - topics, change the Subject. This is usually handled as follows:
- `New Topic XYZ [was: Old Topic]` - - Keep your reply comments near the top of a message, and only - quote essential parts of a previous message at the top — so - there are few quote markings for readers to wade through. - - If you use a vacation auto-responder, exclude responses to mail - with w3c-wai-ig@w3.org in any header.
-- **Send any questions about the WAI IG mailing list to - **, not to the whole list. - -### Subscribing and Unsubscribing to the Discussion List - -- **To subscribe** to the list, send e-mail to w3c-wai-ig-request@w3.org with subject: “subscribe”. -- **To unsubscribe** from the list, send e-mail to w3c-wai-ig-request@w3.org with subject: “unsubscribe”. - -**Please note**: The subscription e-mail addresses are different from -the e-mail address to send an e-mail message, which is in the next -section. - -### Sending Messages to the Discussion List - -To send a message to the list, first subscribe to the list (instructions -above), then send your message to -[w3c-wai-ig@w3.org](mailto:w3c-wai-ig@w3.org) - -**The first time you send a message to a public W3C mailing list**, you -will get a reply e-mail asking if you will give permission for your -message to be distributed to the list and thus go into the public -archive. There is an option to do this once and then you don't have to -do it again in the future. - -## About WAI IG - -The mission of the WAI Interest -Group (WAI IG) is to provide a -forum for reviewing, discussing, and providing input into deliverables -being developed by WAI Working Groups, including accessibility aspects -of specification reviews, research topics identified during -accessibility reviews, and educational materials development; also for -exploring web accessibility issues and solutions, and sharing -information about web accessibility activities around the world.
-The [scope of the WAI IG](/WAI/IG/20200804#scope) -includes: - -- reviewing and discussing deliverables being developed by [WAI - Working Groups](/about/groups/) -- providing input into specification reviews, research topics, and - educational materials development -- exploring web accessibility issues and solutions -- sharing information and exchanging ideas about web accessibility - activities around the world.
- -Work of the WAI IG is in accordance with the [W3C -Process](http://www.w3.org/2015/Process-20150901/). WAI IG work is -funded in part by the [WAI-Core Project](http://www.w3.org/WAI/Core2015/) and [WAI -Sponsors](http://www.w3.org/WAI/Sponsor). - -### Chair and Contacts - -- The WAI IG Chair is Ashley Abaragu (Knowbility) -- The W3C Staff Contact is [Shawn Lawton - Henry](http://www.w3.org/People/Shawn/) - -### Charter - -- [WAI IG - Charter](/WAI/IG/20200804) - -### Past WAI IG Meetings - -- March 19, 2005, Los Angeles, California, USA -- March 19, 2004, Los Angeles, California, USA -- March 22, 2003, Los Angeles, California, USA -- March 25, 2002, Los Angeles, California, USA -- November 14, 2001, Melbourne, Australia -- [March 24, 2001, Los Angeles, California, - USA](http://www.w3.org/WAI/IG/2001/03-agenda.html) -- [March 25, 2000, Los Angeles, California, - USA](http://www.w3.org/WAI/2000/03/agenda#ig) -- [July 19, 1999, Sophia, - France](http://www.w3.org/WAI/1999/07/agenda.htm) -- [May 15 1999, Toronto Canada](http://www.w3.org/WAI/1999/05/agenda) -- [March 20, 1999](http://www.w3.org/WAI/1999/03/agenda.htm) -- [July, 1998, Peterborough, - UK](http://www.w3.org/WAI/1998/07/agenda.html) -- [April, 1998, Brisbane, - Australia](http://www.w3.org/WAI/1998/04/agenda.html) -- [March, 1998, Los Angeles, California, - USA](http://www.w3.org/WAI/1998/03/agenda.html) -- November, 1997, Austin, Texas, USA -- [August, 1997, Boston, Massachusetts, - USA](http://www.w3.org/WAI/group/970805/agenda) -- [May, 1997, Nice, France](http://www.w3.org/WAI/min22) +## Charter + +The WAI Interest Group is chartered until December 2024. + +To learn about the group’s scope, participants and deliverables, see the [WAI Interest Group’s Charter](https://www.w3.org/WAI/IG/20200804). + +## Participate in digital accessibility discussions + +W3C and the WAI Interest Group welcome input on W3C’s digital accessibility work from the global accessibility community. + +The WAI Interest Group is open to the public with no minimum requirements for participation in the group. + +The group provides frequent opportunities for you to give input on digital accessibility work at W3C: + +* **Comment on WAI publications:** During development, the group publishes working drafts of [WAI working groups](/about/groups/)’ deliverables, with options for public comment — these are announced on the WAI Interest Group mailing lists. +* **Contribute to digital accessibility discussions:** Contribute your views to the WAI Interest Group’s mailing list discussions. + +## WAI Interest Group mailing lists {#mailinglist} + +The WAI Interest Group has two mailing lists. + +### Announcements List + +The Announcements List is for WAI announcements only — see the [Announcement List Mail Archive](http://lists.w3.org/Archives/Public/public-wai-announce/). + +If you want to send a message to this list, you must send it from an email address that is subscribed to the list. + +**Note:** Emails to the Announcement List will also go to the Discussion List. + +#### Subscribe or unsubscribe to the Announcements List + +* To **subscribe**, send an email to with the subject line ‘Subscribe’ to [public-wai-announce-request@w3.org](mailto:public-wai-announce-request@w3.org?subject=subscribe). +* To **unsubscribe**, send an email with the subject line ‘Unsubscribe’ to [public-wai-announce-request@w3.org](mailto:public-wai-announce-request@w3.org?subject=unsubscribe). + +### Discussion List + +The Discussion List is for public discussion as well as WAI announcements — see the [Discussion List Mail Archive](https://lists.w3.org/Archives/Public/w3c-wai-ig/). + +If you want to send a message to this list, you must send it from an email address that is subscribed to the list. + +#### Subscribe or unsubscribe to the Discussion List + +* To **subscribe** to the list, send an email with the subject line ’Subscribe’ to [w3c-wai-ig-request@w3.org](mailto:w3c-wai-ig-request@w3.org?subject=subscribe). +* To **unsubscribe** from the list, send an email with the subject line ‘Unsubscribe’ to [w3c-wai-ig-request@w3.org](mailto:w3c-wai-ig-request@w3.org?subject=unsubscribe). + +#### Using the Discussion List + +##### Find discussion topics + +You can use the [Discussion List Mail Archive](https://lists.w3.org/Archives/Public/w3c-wai-ig/) to search for accessibility topics that participants have raised for discussion. + +##### Email the Discussion List + +Once you are subscribed, you can message the Discussion List by emailing [w3c-wai-ig@w3.org](mailto:w3c-wai-ig@w3.org). + +**Note:** The first time you email this public W3C mailing list, you will get an email asking you to give permission for your message to be sent to the group and be listed in the public mail archive. + +When emailing the Discussion List: + +* Use a Subject line that describes the topic well. +* If you change topics, change the Subject line to include both the new and old topics, as follows: ‘[New Topic] was: [Old Topic]’. + +##### Code of conduct for discussions + +Make sure your email is related to digital accessibility and is appropriate for the WAI Interest Group. Your message should contribute to a **comfortable, constructive exchange of ideas** to advance digital accessibility. + +* If you have questions about whether a message is appropriate for the Discussion List, email the [W3C Staff Contact for the WAI Interest Group](https://www.w3.org/groups/ig/wai/participants/#staff). +* No soliciting. +* Be respectful, positive, and open to different perspectives. +* Focus on ideas, not people — avoid personal attacks. +* Explain the issue clearly and provide sufficient contextual information. + +In summary, before you send an email, think about how it will come across to the people around the world who are on the list and who can read your publicly archived message. + +See additional guidance in [Positive Work Environment at W3C: Code of Conduct](https://www.w3.org/Consortium/cepc/). + +##### Asking about vendors or products + +W3C is vendor neutral and therefore we do not recommend specific vendors or products. + +**Important:** If asking about vendors or products, include the following wording in your message: + +‘Please reply to me directly and not to the whole list, so that specific vendor or product information is not discussed on the list.’ + +##### Receiving messages from the Discussion List + +If you use auto-reply (out of office), exclude your automatic responses to emails from w3c-wai-ig@w3.org. + +##### Replying to a message in the Discussion List + +* When your comments are not useful for all participants in the Discussion List, reply directly to the sender. +* Keep your reply comments near the top of your email. +* Quote the previous content in the email chain that you are commenting on, so that readers can quickly and easily understand what your reply is referring to. + +## Contact the chairs + +If you have a question about the WAI Interest Group, email the [chair](https://www.w3.org/groups/ig/wai/participants/#chairs) or the [W3C staff contact](https://www.w3.org/groups/ig/wai/participants/#staff). \ No newline at end of file diff --git a/pages/about/groups/index.md b/pages/about/groups/index.md index 7fb8c551476..2c91089bb1a 100644 --- a/pages/about/groups/index.md +++ b/pages/about/groups/index.md @@ -1,48 +1,55 @@ --- nav_title: "Overview" -title: WAI Working Groups and Interest Groups +title: WAI Working Groups, Task Forces, and Interest Groups lang: en permalink: /about/groups/ ref: /about/groups/ +redirect_from: + - /about/groups/task-forces/ github: label: wai-groups --- -WAI has Working Groups developing accessibility guidelines and related -work, and Interest Groups providing a forum for discussing Web -accessibility issues. **[Participating in WAI](/get-involved/)** -describes generally how to participate in WAI work. To find out more -about participating in a specific WAI group, see the group's home page -linked below. WAI working groups often have Task Forces operating under -them; see Task Force link below. - -[Accessibility Guidelines Working Group (AG WG)](/about/groups/agwg/) *(formerly WCAG WG)* -: AG WG develops guidelines to make web content accessible for people -with disabilities, and develops implementation support materials for -the Web Content Accessibility Guidelines. - -[Accessible Platform Architectures (APA)](/about/groups/apawg/) -: APA reviews specifications, develops technical support materials, -collaborates with other Working Groups on technology accessibility, -and coordinates harmonized accessibility strategies within W3C. - -[Accessible Rich Internet Applications (ARIA)](/about/groups/ariawg/) -: ARIA develops the Accessible Rich Internet Applications (WAI-ARIA) -suite of technologies and other technical specifications when needed -to bridge known gaps. - -[WAI Interest Group (WAI IG)](/about/groups/waiig/) -: WAI IG is a public group with a mailing list for general discussion -on Web accessibility. - -Previous Groups: -- [Education and Outreach Working Group (EOWG)](/about/groups/eowg/) -- Authoring Tool Accessibility Working Group ([AUWG](https://www.w3.org/WAI/AU/Overview.html)) -- Evaluation and Repair Tools Working Group ([ERT WG](https://www.w3.org/WAI/ER/Overview.html)) -- Research and Development Working Group ([RDWG](https://www.w3.org/WAI/RD/Overview.html)) -- User Agent Accessibility Working Group ([UAWG](https://www.w3.org/WAI/UA/Overview.html)) - -See also: - -- [**Task Forces**](/about/groups/task-forces/) - Lists some active Task Forces that operate under WAI Working Groups, and/or jointly between WAI groups and other W3C groups. -- **[Participating in WAI](/about/participating/)** - Describes participation opportunities ranging from volunteering to implement, promote, and review guidelines, to occasional participation in an interest group, to dedicated participation in a working group. +The Web Accessibility Initiative (WAI)’s working groups develop digital accessibility guidelines and related materials — the working groups are supported by task forces that operate under them, and contributions from accessibility discussions in the WAI Interest Group. + +## Accessibility Guidelines Working Group + +The mission of the [Accessibility Guidelines (AG) Working Group](/about/groups/agwg/) and its task forces is to develop and maintain specifications for making web content accessible to people with disabilities, along with support materials for implementing the Web Content Accessibility Guidelines (WCAG). + +The AG Working Group is supported by the: + + - [Accessibility Conformance Testing Task Force](/about/groups/task-forces/conformance-testing/) + - [Cognitive and Learning Disabilities Accessibility Task Force](/about/groups/task-forces/coga/) + - [Low Vision Accessibility Task Force](/about/groups/task-forces/low-vision-a11y-tf/) + - [Mobile Accessibility Task Force](/about/groups/task-forces/matf/) + - [WCAG 2.x Backlog Task Force](/about/groups/task-forces/wcag2x-backlog/) + - [WCAG2ICT Task Force](/about/groups/task-forces/wcag2ict/) + +## Accessible Platform Architectures Working Group + +The mission of the [Accessible Platform Architectures (APA) Working Group](/about/groups/apawg/) and its task forces is to ensure W3C specifications support accessibility for people with disabilities through the following activities: reviewing specifications; developing new specifications and technical support materials; collaborating with other W3C working groups on technology accessibility; and coordinating harmonized accessibility strategies within W3C that include security, privacy, and internationalization. + +The APA Working Group is supported by the: + + - [Framework for Accessible Specification of Technologies Task Force](/about/groups/task-forces/fast/) + - [Maturity Model Task Force](/about/groups/task-forces/maturity-model/) + - [Research Questions Task Force](/about/groups/task-forces/research-questions/) + - [Spoken Presentation Task Force](/about/groups/task-forces/pronunciation/) + - [WAI-Adapt Task Force](/about/groups/task-forces/adapt/) + +## ARIA Working Group + +The mission of the [Accessible Rich Internet Applications (ARIA) Working Group](/about/groups/ariawg/) and its task forces is to enhance the accessibility of web content through developing supplemental attributes that can be applied to native host language interactive elements and exposed via platform accessibility application programming interfaces (APIs). + +The ARIA Working Group is supported by the: + + - [Authoring Practices Guide Task Force](/about/groups/task-forces/practices/) + - [Portable Document Format Accessibility APIs Mapping Task Force](/about/groups/task-forces/pdf-aam/) + +## WAI Interest Group + +The [WAI Interest Group](/about/groups/waiig/) is a public forum with mailing lists for sharing information and exchanging ideas about W3C’s digital accessibility work. + +## Previous groups + +See details for [closed working groups and task forces](/about/groups/previous-groups/). \ No newline at end of file diff --git a/pages/about/groups/previous-groups.md b/pages/about/groups/previous-groups.md new file mode 100644 index 00000000000..fda3e6a0093 --- /dev/null +++ b/pages/about/groups/previous-groups.md @@ -0,0 +1,46 @@ +--- +title: Previous groups +nav_title: 'Previous groups' +lang: en +permalink: /about/groups/previous-groups/ +ref: /about/groups/previous-groups/ +github: + label: wai-groups +--- + +{::nomarkdown} +{% include box.html type="start" title="Summary" class="" %} +{:/} + +See details for working groups and task forces that have now closed. + +{::nomarkdown} +{% include box.html type="end" %} +{:/} + +{::options toc_levels="2..3" /} + +{::nomarkdown} +{% include_cached toc.html type="start" title="Page Contents" %} +{:/} + +- TOC is created automatically. +{:toc} + +{::nomarkdown} +{% include_cached toc.html type="end" %} +{:/} + +## Previous working groups + +* [Authoring Tool Accessibility Working Group](https://www.w3.org/groups/wg/atag/) — group closed in 2015 +* [Education and Outreach Working Group](https://www.w3.org/groups/wg/eowg/) — group closed in 2024 +* [Evaluation and Repair Tools Working Group](https://www.w3.org/groups/wg/ertwg/) — group closed in 2017 +* [Research and Development Working Group](https://www.w3.org/groups/wg/wai-rd/) — group closed in 2015 +* [User Agent Accessibility Working Group](https://www.w3.org/groups/wg/uaag/) — group closed in 2016 + +## Previous task forces + +* [CSS Accessibility Task Force](https://www.w3.org/groups/tf/css-a11y/) +* [Silver Task Force](https://www.w3.org/groups/tf/silver-tf/) + diff --git a/pages/about/groups/task-forces.md b/pages/about/groups/task-forces.md deleted file mode 100644 index c3643db3014..00000000000 --- a/pages/about/groups/task-forces.md +++ /dev/null @@ -1,94 +0,0 @@ ---- -title: Group Task Forces -lang: en -permalink: /about/groups/task-forces/ -ref: /about/groups/task-forces/ -github: - label: wai-groups ---- - -Task Forces operate under specific Working Groups. - -**[Accessibility Conformance Testing (ACT) Task Force](/about/groups/task-forces/conformance-testing/)** under the [AG Working Group](/about/groups/agwg/) - -: Develop a framework and repository of test rules, to promote a - unified interpretation of WCAG 2.0 among different web accessibility - test tools. The framework will also allow the development of custom - test rules to meet company requirements and best practices. While - this framework will add a layer of implemention for tool developers, - it provides more consistency and comparability of the resulting test - rules. - -**[Cognitive and Learning Disabilities Accessibility Task Force](/about/groups/task-forces/coga/)** (Cognitive A11Y TF) under the [APA Working Group](/about/groups/apawg/) and the [AG Working Group](/about/groups/agwg/) - -: Assisting Working Groups to produce techniques, understanding, and - guidance documents, as well as updates to existing related W3C - material that addresses the cognitive space. - -**[Low Vision Accessibility Task Force](/about/groups/task-forces/low-vision-a11y-tf/)** (LVTF) under the [AG Working Group](/about/groups/agwg/) - -: Assisting Working Groups to address web accessibility issues - specific to people with low vision. - -**[Mobile Accessibility Task Force](/about/groups/task-forces/matf/)** under the [AG Working Group](/about/groups/agwg/) - -: Assisting Working Groups to produce techniques, understanding, and - guidance documents, as well as updates to existing related W3C - material that addresses the mobile space. - -**[Silver Task Force](/about/groups/task-forces/silver/)** under the [AG Working Group](/about/groups/agwg/) - -: Perform preliminary development of a new version of Accessibility - Guidelines following a research-focused, user-centered design - methodology to produce the most effective and flexible outcome. - These guidelines will address the process of making content and - functionality accessible to people with disabilities, including the - roles of content authoring, user agent support, and authoring tool - support. These guidelines will address current technological and - cultural web accessibility requirements and provide a base for - continued evolution of the guidelines. - -**[WCAG2ICT Task Force](/about/groups/task-forces/wcag2ict/)** under the [AG Working Group](/about/groups/agwg/) - -: The WCAG2ICT Task Force develops documentation - describing how WCAG 2.x and its principles, guidelines, and success - criteria could apply to non-Web Information and Communications - Technologies (ICT). - -**[WCAG 2.x Backlog Task Force](/about/groups/task-forces/wcag2x-backlog/)** under the [AG Working Group](/about/groups/agwg/) - -: The WCAG 2.x Backlog Task Force maintains up-to-date versions of the normative and informative materials associated with versions 2.0, 2.1, and 2.2 of the Web Content Accessibility Guidelines, and documents considerations for WCAG 3.0 which cannot be readily addressed within the existing normative language of the 2.x specification. - - -**[ARIA Authoring Practices Task Force](/about/groups/task-forces/practices/)** under the [ARIA Working Group](/about/groups/ariawg/) - -: Develop WAI-ARIA Authoring Practices Guide (APG), which describes considerations that might - not be evident to most authors from the WAI-ARIA specification alone and recommends - approaches to make widgets, navigation, and behaviors accessible using WAI-ARIA roles, - states, and properties. - -**[Research Question Task Force](/about/groups/task-forces/research-questions/)** under the [APA Working Group](/about/groups/apawg/) - -: Identify accessibility knowledge gaps and barriers in emerging and - future web technologies, and to identify research findings, - researchers, and research opportunities to inform and fill those - gaps where possible. - -**[Spoken Presentation Task Force](/about/groups/task-forces/pronunciation/)** under the [APA Working Group](/about/groups/apawg/) - -: The Spoken Presentation Task Force has been exploring technical options for content authors to provide pronunciation information. - -**[WAI-Adapt Task Force](/about/groups/task-forces/adapt/)** under the [APA Working Group](/about/groups/apawg/) - -: WAI-Adapt specifications enable users to personalize how content is presented in order to meet their needs and preferences. - -**[Maturity Model Task Force](/about/groups/task-forces/maturity-model/)** under the [APA Working Group](/about/groups/apawg/) - -: The Maturity Model Task Force (MMTF) aims to create an Accessibility Maturity Model (AMM) narrative and assessment tool in support of W3C standards and other related guidance, such as Web Content Accessibility Guidelines (WCAG) and Accessibility Rich Internet Applications (ARIA). The Accessibility Maturity Model will assist organizations in building capacity to develop, and maintain, accessible products or services. - -If you would like to learn about participating in a Task Force, see: -- [Participating in WAI](/about/participating/) for general - information -- The Task Force's home page linked above, and the "How to Join - (Participation)" link in the navigation area of the Working Group's - home page diff --git a/pages/about/groups/task-forces/adapt.md b/pages/about/groups/task-forces/adapt.md index c01d8eb15db..31ba15c3cb0 100644 --- a/pages/about/groups/task-forces/adapt.md +++ b/pages/about/groups/task-forces/adapt.md @@ -1,5 +1,5 @@ --- -title: WAI-Adapt Task Force of the APA WG +title: WAI-Adapt Task Force permalink: /about/groups/task-forces/adapt/ ref: /about/groups/task-forces/adapt/ lang: en @@ -13,9 +13,7 @@ redirect_from: {% include box.html type="start" title="Summary" class="" %} {:/} -The WAI-Adapt Task Force is a task force of the [Accessible Platform Architectures Working Group](/about/groups/apawg/). - -Some information on this page is also shown on, and may be more current in, the [WAI Adapt Task Force page](https://www.w3.org/groups/tf/personalization-tf/). +Find out about the activities of the WAI-Adapt Task Force and how you can contribute to its objectives. {::nomarkdown} {% include box.html type="end" %} @@ -34,79 +32,73 @@ Some information on this page is also shown on, and may be more current in, the {% include_cached toc.html type="end" %} {:/} -## Announcements - -No announcements at the moment. +## Objectives -## WAI-Adapt Overview +The objective of the WAI-Adapt Task Force is to develop normative specifications and best practices guidance to support enhanced and personalized web content delivery that better meets the diverse requirements of people with disabilities — it does this by making fuller use of underused features already specified in HTML, and by proposing new markup elements and attributes, as needed. -[WAI-Adapt Overview](https://www.w3.org/WAI/adapt/) provides an overview of the overall WAI-Adapt technique in W3C. +## Work statement -## WAI-Adapt Video +To learn about the focus, scope and deliverables of the task force, see the [WAI-Adapt Task Force Work Statement](/about/groups/task-forces/adapt/work-statement/). -There is also a short [WAI-Adapt technical video](https://ln.sync.com/dl/04f8c9330/6wk4ff4v-77wd78s5-ge6wc24s-vm3iwxwm) available, it demonstrates a semantic overlay approach to enable user driven personalization, eg. the association of user-preferred symbols with elements having those WAI-Adapt semantics. +## Overview of the WAI-Adapt work -## Meetings and Communication +* [WAI-Adapt Overview](https://www.w3.org/WAI/adapt/) — an overview of W3C’s WAI-Adapt technique +* [WAI-Adapt video {% include_cached external.html %}](https://ln.sync.com/dl/04f8c9330/) — a technical demonstration of a semantic overlay approach that enables user-driven personalization, employing user-preferred symbols for text that has had WAI-Adapt semantics added to it -The WAI-Adapt Task Force conducts its work using a variety of synchronous and asynchronous tools. This section provides details about: +## Current work -- Teleconferences of the Working Group and its task forces (also see [meeting minutes](https://www.w3.org/WAI/APA/task-forces/adapt/minutes)); -- Face to face meetings; -- [Email lists](/about/groups/task-forces/adapt/#mailing-lists); -- IRC discussion on the [#adapt](irc://irc.w3.org/adapt) IRC channel, used largely for minute-taking; -- [WAI-Adapt source repository](https://github.com/w3c/adapt/); -- [Wiki](https://github.com/w3c/adapt/wiki); -- [Web-Based Surveys (WBS)](https://www.w3.org/2002/09/wbs/101569/); -- [WAI-Adapt source repository issue tracker](https://github.com/w3c/adapt/issues). +The WAI-Adapt Task Force supports the deliverables of the [Accessible Platform Architectures (APA) Working Group](/about/groups/apawg/). -These tools are used by participants of the Task Force. For ways non-participants can contribute, see [how to contribute to the Working Group and file comments](/about/groups/apawg/contribute/). +For details of the current work, see the [WAI-Adapt Task Force wiki](https://github.com/w3c/adapt/wiki). -### Teleconferences +## Contribute to the work -- **[WAI-Adapt](https://www.w3.org/2017/08/telecon-info_adapt)**: Mondays at 10:00 until 11:00 Boston time -- **[WAI-Adapt Plan](https://www.w3.org/2017/08/telecon-info_adapt-plan)**: Tuesdays at 10:00 until 10:30 Boston time +The WAI-Adapt Task Force welcomes input from the global accessibility community on the work to enable content and interface personalization for people with cognitive and learning disabilities. -### Meeting Minutes +### Contribute without joining the task force -[Minutes from previous meetings](https://www.w3.org/WAI/APA/task-forces/adapt/minutes) are available. +You can contribute to the work without being a member of the task force in the [WAI-Adapt GitHub repository](https://github.com/w3c/adapt/issues): -### Mailing Lists +* If you’re aware of an issue with any of the published WAI-Adapt resources, raise a new issue. +* Comment on or propose solutions for open WAI-Adapt issues. -The WAI-Adapt Task Force uses the public-adapt@w3.org mailing list ([mailing list archives](http://lists.w3.org/Archives/Public/public-adapt/)) for email discussion. Participants are automatically added to the mailing list when they become a participant of the Task Force. +### Become a participant in the task force -## Current Work +Joining the WAI-Adapt Task Force enables you to participate fully in the development of the work and influence the deliverables. You and your organization will also be listed as contributors, where appropriate. -[See the wiki for current planning and draft documents](https://github.com/w3c/adapt/wiki). +Being a participant involves commitment to support the work of the task force in the following ways: -## Publications +* Engage actively in the work using the task force’s communication channels. +* Keep up with weekly tasks and the progress of the work — for example, via the minutes of past meetings, mailing list discussions, and GitHub issue comments. +* Give your input promptly, when it’s needed. -The WAI-Adapt Task Force published four documents as follow: +To become a participant in the WAI-Adapt Task Force, you must first be a member of the APA Working Group — see [Instructions for joining the Accessible Platform Architectures Working Group](https://www.w3.org/groups/wg/apa/instructions/). -- [WAI-Adapt Explainer](https://www.w3.org/TR/adapt/) (Working Draft Note) is the core introductory document that explains general use cases, vocabulary, and anticipated uses. -- [WAI-Adapt: Content Module](https://www.w3.org/TR/adapt-content/) (Working Draft specification) is the technical specification that provides terms authors can use to enhance web content with information about controls, symbols, and user interface elements. -- [WAI-Adapt: Help and Support Module](https://www.w3.org/TR/adapt-help/) (Working Draft) lists examples of the personalized help and support properties. -- [WAI-Adapt: Tools Module](https://www.w3.org/TR/adapt-tools/) (Working Draft) lists examples of the personalized tools properties. -- [Requirements for WAI-Adapt Specifications](https://www.w3.org/TR/adapt-requirements/) (First Public Working Draft Note) includes user stories, specific use cases, and requirements for WAI-Adapt. +Once you are a member of the APA Working Group, email the [W3C staff contact for the WAI-Adapt Task Force](https://www.w3.org/groups/tf/personalization-tf/participants/#staff) to let them know you’d like to join the task force. -See also the [WAI-Adapt Task Force GitHub repository](https://github.com/w3c/adapt/). +**Note:** As a participant in one of the APA Working Group’s task forces, you can choose to focus your time exclusively on the task force deliverables and you do not have to contribute to the working group’s other activities. -## How to Comment, Contribute, and Participate +## Task force members -To join the WAI-Adapt Task Force, individuals must be participants of the [APA WG](/about/groups/apawg/). Participants are expected to [actively contribute](/about/groups/task-forces/adapt/work-statement/#participation) to the work of the Task Force. If you are interested in participating in the WAI-Adapt Task Force, please send e-mail to: [Lionel Wolberger](mailto:lionel@userway.org?subject=WAI-Adapt%20Task%20Force%20Enquiry) and include a little bit about what you’re interested in and how you think that you may be able to contribute to the Task Force. Then follow the [APA Working Group participation](/about/groups/apawg/participate/) procedures to join the Working Group, and once you have joined ask [Ruoxi Ran (Roy)](mailto:ran@w3.org) to add you to the task force. +* [Chair](https://www.w3.org/groups/tf/personalization-tf/participants/#chairs) +* [Current participants](https://www.w3.org/groups/tf/personalization-tf/participants/#participants) -To contribute without joining the task force, see the [APA Working Group contribute page](/about/groups/apawg/contribute/) for general instructions. To contribute to documents under development, see [how to contribute to the source repository directly](https://github.com/w3c/adapt/). +## Communications -[Current participants in the WAI-Adapt Task Force](https://www.w3.org/2000/09/dbwg/details?group=101569&public=1). +* [Calendar of meetings](https://www.w3.org/groups/tf/personalization-tf/calendar/) +* [Minutes from previous meetings](https://www.w3.org/WAI/APA/task-forces/adapt/minutes) +* [Mailing list archive](https://lists.w3.org/Archives/Public/public-adapt/) -## Administrative Information - -The WAI-Adapt Task Force is a Task Force of the [Accessible Platform Architectures (APA) Working Group](https://www.w3.org/WAI/about/groups/apawg/). It assists this Working Group to mature WAI-Adapt and to incubate WAI-Adapt as an approach to meeting accessibility user requirements across W3C. +## Publications -### Facilitator and Contacts +The WAI-Adapt Task Force develops and maintains the following resources for the APA Working Group: -- **Facilitators:** [Lionel Wolberger](mailto:lionel@userway.org) -- **Staff Contact:** [Ruoxi Ran](https://www.w3.org/People/roy/) +* [Requirements for WAI-Adapt specification — 2022 Group Draft Note](https://www.w3.org/TR/adapt-requirements/) — user stories, specific use cases, and requirements for WAI-Adapt +* [WAI-Adapt: Tools Module — 2022 Group Draft Note]() — examples of the personalized tools properties +* [WAI-Adapt: Help and Support Module — 2022 Working Draft](https://www.w3.org/TR/adapt-help/) — examples of the personalized help and support properties +* [WAI-Adapt: Symbols Module — 2023 Candidate Recommendation Snapshot](https://www.w3.org/TR/adapt-symbols/) — technical specification providing terms authors can use to enhance web content with information about controls, symbols, and user interface elements +* [WAI-Adapt Explainer — 2023 Group Draft Note](https://www.w3.org/TR/adapt/) — introductory document explaining general use cases, vocabulary, and anticipated uses -### Work Statement +## Contact the chair -The [WAI-Adapt Task Force Work Statement](/about/groups/task-forces/adapt/work-statement/) defines the initial objective, scope, approach, and participation of the Task Force. \ No newline at end of file +If you have a question for the WAI-Adapt Task Force, email the [chair](https://www.w3.org/groups/tf/personalization-tf/participants/#chairs) or the [W3C staff contact](https://www.w3.org/groups/tf/personalization-tf/participants/#staff). \ No newline at end of file diff --git a/pages/about/groups/task-forces/adapt/work-statement.md b/pages/about/groups/task-forces/adapt/work-statement.md index 4e8e204c42b..2d14fc1caf2 100644 --- a/pages/about/groups/task-forces/adapt/work-statement.md +++ b/pages/about/groups/task-forces/adapt/work-statement.md @@ -44,7 +44,7 @@ As the nature of web technology broadens in scope and reach, and understanding o ## Approach -The task force will work within the APA Working Group to develop and refine WAI-Adapt. It will coordinate with other stakeholders, such as the [Cognitive and Learning Disabilities Task Force](/about/groups/task-forces/coga/), the [Digital Publishing Working Group](https://www.w3.org/publishing/groups/publ-wg/), [IMS Global Learning Consortium](https://www.imsglobal.org/), etc. It will prepare content for WAI-Adapt, which will be reviewed and published upon approval by the APA Working Group. It may archive features for consideration in a future version in order to maintain an achievable scope for the current version. +The task force will work within the APA Working Group to develop and refine WAI-Adapt. It will coordinate with other stakeholders, such as the [Cognitive and Learning Disabilities Task Force](/about/groups/task-forces/coga/), the [Digital Publishing Working Group](https://www.w3.org/publishing/groups/publ-wg/), [IMS Global Learning Consortium {% include_cached external.html %}](https://www.imsglobal.org/), etc. It will prepare content for WAI-Adapt, which will be reviewed and published upon approval by the APA Working Group. It may archive features for consideration in a future version in order to maintain an achievable scope for the current version. In addition to the features defined in WAI-Adapt, other work also addresses the broader topic of personalization to enhance accessibility. [CSS](https://www.w3.org/Style/CSS/) provides many features to allow content to adapt to aspects of the user environment; [RDFa](https://www.w3.org/TR/rdfa-core/) and [HTML Microdata](https://www.w3.org/TR/microdata/) provide ways to add semantics to content that can aid user adaptation; some [Accessibility Guidelines](https://www.w3.org/TR/WCAG21/) can be met by enabling personalization. The task force will seek to develop a common vision for personalization approaches, coordinating with other groups as needed. The task force will engage the [Accessible Platform Architectures Working Group](/about/groups/apawg/) to help harmonize this coordination with other accessibility activity. @@ -69,7 +69,7 @@ Participants may also join WAI-Adapt Task Force sub-groups. Sub-groups take on s If you are interested in becoming a participant of the WAI-Adapt Task Force or have any questions regarding its work, contact the task force facilitators. -[Current WAI-Adapt Task Force participants](https://www.w3.org/2000/09/dbwg/details?group=101569&public=1) +[Current WAI-Adapt Task Force participants](https://www.w3.org/groups/tf/personalization-tf/participants/) ## Facilitation @@ -80,4 +80,4 @@ Staff contacts from the APA Working Groups oversee attention to W3C Process with ## Patent Policy -This Task Force is part of the [APA Working Group Charter](https://www.w3.org/WAI/APA/charter), which operates under the [W3C Patent Policy](https://www.w3.org/Consortium/Patent-Policy-20040205/) (5 February 2004 Version). W3C maintains a public list of any patent disclosures made in connection with the deliverables of the [APA Working Group](https://www.w3.org/2004/01/pp-impl/83907/status). \ No newline at end of file +This Task Force is part of the [APA Working Group Charter](https://www.w3.org/WAI/APA/charter), which operates under the [W3C Patent Policy](https://www.w3.org/policies/patent-policy/20200915/) (15 September 2020 Version). W3C maintains a public list of any patent disclosures made in connection with the deliverables of the [APA Working Group](https://www.w3.org/2004/01/pp-impl/83907/status). \ No newline at end of file diff --git a/pages/about/groups/task-forces/css-a11y.md b/pages/about/groups/task-forces/archive/css-a11y.md similarity index 98% rename from pages/about/groups/task-forces/css-a11y.md rename to pages/about/groups/task-forces/archive/css-a11y.md index 173e6fac7e5..16921703ac0 100644 --- a/pages/about/groups/task-forces/css-a11y.md +++ b/pages/about/groups/task-forces/archive/css-a11y.md @@ -5,6 +5,9 @@ ref: /about/groups/task-forces/css-a11y/ lang: en github: label: wai-groups +doc-note-type: archived +doc-note-message-md: | + The CSS Accessibility Task Force has closed. --- {::options toc_levels="2..3" /} diff --git a/pages/about/groups/task-forces/css-a11y/work-statement.md b/pages/about/groups/task-forces/archive/css-a11y/work-statement.md similarity index 98% rename from pages/about/groups/task-forces/css-a11y/work-statement.md rename to pages/about/groups/task-forces/archive/css-a11y/work-statement.md index ddfc4788050..55ea9f6c710 100644 --- a/pages/about/groups/task-forces/css-a11y/work-statement.md +++ b/pages/about/groups/task-forces/archive/css-a11y/work-statement.md @@ -32,7 +32,7 @@ The CSS Accessibility Task Force (CSS A11Y TF) is a Task Force of the [Accessibl ## Status -This work statement work statement has been approved by the sponsoring Working Groups. The task force is now active. +This work statement has been approved by the sponsoring Working Groups. The task force is now active. ## Objective diff --git a/pages/about/groups/task-forces/silver.md b/pages/about/groups/task-forces/archive/silver.md similarity index 98% rename from pages/about/groups/task-forces/silver.md rename to pages/about/groups/task-forces/archive/silver.md index 1b7041cc3a1..5157ece853b 100644 --- a/pages/about/groups/task-forces/silver.md +++ b/pages/about/groups/task-forces/archive/silver.md @@ -5,6 +5,9 @@ ref: /about/groups/task-forces/silver/ lang: en github: label: wai-groups +doc-note-type: archived +doc-note-message-md: | + The Silver Task Force has closed. --- {::nomarkdown} diff --git a/pages/about/groups/task-forces/silver/work-statement.md b/pages/about/groups/task-forces/archive/silver/work-statement.md similarity index 100% rename from pages/about/groups/task-forces/silver/work-statement.md rename to pages/about/groups/task-forces/archive/silver/work-statement.md diff --git a/pages/about/groups/task-forces/coga.md b/pages/about/groups/task-forces/coga.md index 86e014142e8..e2edbadbdbc 100644 --- a/pages/about/groups/task-forces/coga.md +++ b/pages/about/groups/task-forces/coga.md @@ -1,5 +1,5 @@ --- -title: Cognitive and Learning Disabilities Accessibility Task Force (COGA) +title: Cognitive and Learning Disabilities Accessibility Task Force permalink: /about/groups/task-forces/coga/ ref: /about/groups/task-forces/coga/ lang: en @@ -11,10 +11,7 @@ github: {% include box.html type="start" title="Summary" class="" %} {:/} -The Cognitive and Learning Disabilities Accessibility Task Force (Cognitive A11Y TF) is a joint Task Force of the [Accessible Platform Architectures (APA) Working Group](/about/groups/apawg/) and the [Web Content Accessibility Guidelines Working Group (AG WG)](/about/groups/agwg/). It assists these Working Groups to produce techniques, understanding, and guidance documents, as well as updates to existing related W3C material that addresses the cognitive space. - - -Some information on this page is also shown on, and may be more current in, the [automatically generated Cognitive and Learning Disabilities Accessibility Task Force page](https://www.w3.org/groups/tf/cognitive-a11y-tf). +Find out about the activities of the Cognitive and Learning Disabilities Accessibility (COGA) Task Force and how you can contribute to its objectives. {::nomarkdown} {% include box.html type="end" %} @@ -33,80 +30,74 @@ Some information on this page is also shown on, and may be more current in, the {% include_cached toc.html type="end" %} {:/} +## Objectives -## Facilitator and Contacts +The objective of the COGA Task Force is to develop guidance and techniques for content authoring and user agent implementation in order to make web content accessible to people with cognitive and learning disabilities. -- **Task Force facilitators:** - - [Rain Breaw Michaels](https://www.w3.org/users/129114) - - [Lisa Seeman](https://www.w3.org/users/16320) -- **Staff Contacts:** - - [Roy Ran](https://www.w3.org/People/Roy/) +## Work statement +To learn about the focus, scope and deliverables of the task force, see the [COGA Task Force Work Statement](/about/groups/task-forces/coga/work-statement/). -## Announcements and Meetings +## Current work -No announcements at the moment. +The COGA Task Force supports the deliverables of two W3C working groups: -## Meetings and Communication +* [Accessibility Guidelines (AG) Working Group](/about/groups/agwg/) +* [Accessible Platform Architectures (APA) Working Group](/about/groups/apawg/) -The Coga TF conducts its work using a variety of synchronous and asynchronous tools. Most work is done via email and issues as shown below, supplemented by occasional teleconferences. +For details of the current work, see the [COGA Task Force wiki](https://www.w3.org/WAI/GL/task-forces/coga/wiki). -- [Email lists](#email); -- [wiki](https://www.w3.org/WAI/GL/task-forces/coga/wiki/); -- [Coga GitHub repository](https://github.com/w3c/coga/); -- IRC discussion on the [#coga](irc://irc.w3.org/coga) IRCchannel, used largely for minute-taking; -- [Web-Based Surveys (WBS)](https://www.w3.org/2002/09/wbs/67703/); -- Teleconferences of the task force (also see [meeting minutes](https://www.w3.org/WAI/GL/task-forces/coga/minutes)); -- Face to face meetings; +## Contribute to the work -These tools are used by participants of the Task Force. For ways non-participants can contribute, see how to [participate in the Working Group](/about/groups/agwg/participate/) and [file comments](https://www.w3.org/WAI/WCAG20/comments/). +The COGA Task Force welcomes input from the global accessibility community on cognitive and learning accessibility work. -### Meeting Minutes +### Contribute without joining the task force -[Minutes from previous meetings](https://www.w3.org/WAI/GL/task-forces/coga/minutes) are available. +You can contribute to the work without being a member of the task force in the [COGA GitHub repository](https://github.com/w3c/coga/issues): +* If you’re aware of an issue with any of the published COGA resources, raise a new issue. +* Comment on or propose solutions for open COGA issues. -### Mailing Lists +### Become a participant in the task force -The Coga TF uses the public-cognitive-a11y-tf@w3.org mailing list ([mailing list archives](http://lists.w3.org/Archives/Public/public-cognitive-a11y-tf/)) for email discussion; members of the public can post to this list to send input to the task force. The TF uses the public-cognitive-a11y-tf@w3.org mailing list [mailing list archives](http://lists.w3.org/Archives/Public/public-cognitive-a11y-tf/) for administrative discussion that is specific to participants in the task force. Participants are automatically subscribed to these mailing lists when they become a participant of the Task Force. +Joining the COGA Task Force enables you to participate fully in the development of the work and influence the deliverables. You and your organization will also be listed as contributors, where appropriate. -## Current Work +Being a participant involves commitment to support the work of the task force in the following ways: -Current Task Force work includes: +* Engage actively in the work using the task force’s communication channels. +* Keep up with weekly tasks and the progress of the work — for example, via the minutes of past meetings, mailing list discussions, and GitHub issue comments. +* Give your input promptly, when it’s needed. -- Develop proposed [Success Criteria for WCAG 2.1](https://github.com/w3c/wcag21/issues?q=is%3Aissue+is%3Aopen+label%3ACOGA); -- Develop [Cognitive Accessibility User Research](https://w3c.github.io/coga/user-research/) to serve as a repository of related research into cognition and disabilities; -- Develop [Issue Papers for the The Cognitive and Learning Disabilities Accessibility Task Force](https://w3c.github.io/coga/issue-papers/) as a use case repository to describe different cognitive disabilities and scenarios for how persons with atypical ability profiles use technology successfully or unsuccessfully; -- Develop [Cognitive Accessibility Roadmap and Gap Analysis](https://w3c.github.io/coga/gap-analysis/); -- Identify related work inside and outside of the W3C; -- Review existing techniques and propose new features where needed; -- Gather information on different related technologies and techniques including where techniques in support of cognitive and learning disabled users may conflict with what is needed for other users; -- Make predictions of where technology is headed; -- Identify stakeholders, from whom the task force can solicit ongoing feedback; -- Document business cases and identify areas of resistance, risks and opportunities. +To become a participant in the COGA Task Force, you must first be a member of one of the working groups the task force supports: +* AG Working Group — see [Instructions for joining the Accessibility Guidelines Working Group](https://www.w3.org/groups/wg/ag/instructions/) +* APA Working Group — see [Instructions for joining the Accessible Platform Architectures Working Group](https://www.w3.org/groups/wg/apa/instructions/) -[See the wiki for current planning and draft documents](https://www.w3.org/WAI/GL/task-forces/coga/wiki/). +Once you are a member of either the AG or APA working groups, email the [W3C staff contact for the COGA Task Force](https://www.w3.org/groups/tf/cognitive-a11y-tf/participants/#staff) to let them know you’d like to join the task force. -## Publications +**Note:** As a participant in one of the AG or APA working groups’ task forces, you can choose to focus your time exclusively on the task force deliverables and you do not have to contribute to the working group’s other activities. -- [Cognitive Accessibility User Research](https://w3c.github.io/coga/user-research/); -- [Issue Papers for the The Cognitive and Learning Disabilities Accessibility Task Force](https://w3c.github.io/coga/issue-papers/); -- [Cognitive Accessibility Roadmap and Gap Analysis](https://w3c.github.io/coga/gap-analysis/); +## Task force members -The [task force wiki](https://www.w3.org/WAI/GL/task-forces/coga/wiki/) contains more comprehensive information about deliverables. +* [Chair](https://www.w3.org/groups/tf/cognitive-a11y-tf/participants/#chairs) +* [Current participants](https://www.w3.org/groups/tf/cognitive-a11y-tf/participants/#participants) +## Communications -### Work Statement +* [Calendar of meetings](https://www.w3.org/groups/tf/cognitive-a11y-tf/calendar/) +* [Minutes from previous meetings](https://www.w3.org/WAI/GL/task-forces/coga/minutes) +* [Mailing list archive](http://lists.w3.org/Archives/Public/public-cognitive-a11y-tf/) -**[Cognitive and Learning Disabilities Accessibility Task Force Work Statement](/about/groups/task-forces/coga/work-statement/)** defines the initial objective, scope, approach, and participation of the Task Force. - -### Participation +## Publications -To join the Cognitive A11Y TF, individuals must be participants of either the [Accessible Platform Architectures (APA) Working Group](/about/groups/apawg/) or the [Web Content Accessibility Guidelines Working Group (AG WG)](/about/groups/agwg/). Participants are expected to actively contribute to the work of the Task Force, including: +The COGA Task Force has developed the following resources for the AG and APA working groups: -- Minimum 4 hours per week of Cognitive A11Y TF work (this time also counts towards the individual's participation requirement in the sponsoring WG through which they have joined); -- Remain current on the Cognitive and Learning Disabilities Accessibility Task Force mailing list and respond in a timely manner to postings; -- Participate in Cognitive and Learning Disabilities Accessibility Task Force telephone meetings, or send regrets to the Task Force mailing list. +* [Cognitive Accessibility Guidance](https://www.w3.org/WAI/WCAG2/supplemental/#cognitiveaccessibilityguidance) +* [Cognitive Accessibility User Research — 2015 Working Draft](https://w3c.github.io/coga/user-research/) +* [Cognitive Accessibility User Research — 2024 Editor’s Draft](https://www.w3.org/TR/coga-user-research/) +* [Making Content Usable for People with Cognitive and Learning Disabilities — 2018 Working Draft](https://www.w3.org/TR/2018/WD-coga-usable-20181211/) +* [Making Content Usable for People with Cognitive and Learning Disabilities — 2021 Working Group Note](https://www.w3.org/TR/coga-usable/) +* [Cognitive Accessibility Roadmap and Gap Analysis — 2024 Working Draft](https://w3c.github.io/coga/gap-analysis/) +* [Cognitive Accessibility Issue — 2024 Editor’s Draft](https://w3c.github.io/coga/issue-papers/) -If you are interested in participating in the COGA TF, please send e-mail to: [Ruoxi (Roy) Ran](mailto:roy@w3.org) and include a little bit about what you’re interested in and how you think that you may be able to contribute to the Task Force. +## Contact the chair -[Participants in the Cognitive and Learning Disabilities Accessibility Task Force](https://www.w3.org/2000/09/dbwg/details?group=67703&public=1) lists current participants. \ No newline at end of file +If you have a question for the COGA Task Force, email the [chair](https://www.w3.org/groups/tf/cognitive-a11y-tf/participants/#chairs) or the [W3C staff contact](https://www.w3.org/groups/tf/cognitive-a11y-tf/participants/#staff). \ No newline at end of file diff --git a/pages/about/groups/task-forces/coga/work-statement.md b/pages/about/groups/task-forces/coga/work-statement.md index 0c947585c88..1cebdbccd33 100644 --- a/pages/about/groups/task-forces/coga/work-statement.md +++ b/pages/about/groups/task-forces/coga/work-statement.md @@ -1,5 +1,5 @@ --- -title: Cognitive and Learning Disabilities Accessibility Task Force (Coga TF) Work Statement +title: Cognitive and Learning Disabilities Accessibility Task Force Work Statement permalink: /about/groups/task-forces/coga/work-statement/ ref: /about/groups/task-forces/coga/work-statement/ lang: en @@ -46,7 +46,7 @@ The objective of the Cognitive and Learning Disabilities Accessibility Task Forc - intellectual disabilities, - age-related memory loss, - a subset of mental health conditions that have clear research that can be integrated into Making Content Usable, -- and specific learning disabilities (SLD). \[[Making Content Usable 2.4, Language Use](#References)\] +- and specific learning disabilities (SLD). \[[Making Content Usable 2.4, Language Use](#references)\] **Our work includes:** diff --git a/pages/about/groups/task-forces/conformance-testing.md b/pages/about/groups/task-forces/conformance-testing.md index ee97255756a..00cc35b59b7 100644 --- a/pages/about/groups/task-forces/conformance-testing.md +++ b/pages/about/groups/task-forces/conformance-testing.md @@ -1,5 +1,5 @@ --- -title: Accessibility Conformance Testing (ACT) +title: Accessibility Conformance Testing Task Force permalink: /about/groups/task-forces/conformance-testing/ ref: /about/groups/task-forces/conformance-testing/ lang: en @@ -11,9 +11,7 @@ github: {% include box.html type="start" title="Summary" class="" %} {:/} -The WCAG Accessibility Conformance Testing (ACT) Task Force (ACT) is a Task Force of the [Accessibility Guidelines (AG) Working Group](/about/groups/agwg/). It assists the AG WG to produce specific deliverables as specified in the [work statement](/about/groups/task-forces/conformance-testing/work-statement/). - -Some information on this page is also shown on, and may be more current in, the [automatically generated Accessibility Conformance Testing (ACT) Task Force page](https://www.w3.org/groups/tf/wcag-act). +Find out about the activities of the Accessibility Conformance Testing (ACT) Task Force and how you can contribute to its objectives. {::nomarkdown} {% include box.html type="end" %} @@ -32,86 +30,66 @@ Some information on this page is also shown on, and may be more current in, the {% include_cached toc.html type="end" %} {:/} -## Facilitator and Contacts - -- **Task Force co-facilitators:** - - Wilco Fiers, Deque Systems - - Kathy Eng, Access Board -- **Staff Contact:** [Daniel Montalvo](https://www.w3.org/People/#dmontalvo) +## Objectives -## Announcements +The objective of the ACT Task Force is to develop and maintain a repository of ACT Rules for WCAG 2 in order to promote a unified interpretation across different web accessibility test tools and methodologies. -No announcements at the moment. +## Work statement -## Meetings and Communication +To learn about the focus, scope and deliverables of the task force, see the [ACT Task Force Work Statement](/about/groups/task-forces/conformance-testing/work-statement/). -### Weekly Teleconferences +## Current work -ACT TF meets weekly on **[Thursdays from 09:00 to 10:00 AM ET](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20230330T09&p1=43&ah=1)**: +The ACT Task Force supports the deliverables of the [Accessibility Guidelines (AG) Working Group](/about/groups/agwg/). -- Meeting materials - - [Meeting minutes](https://www.w3.org/WAI/GL/task-forces/conformance-testing/wiki/Meeting_Minutes) - - [Availability for ACT TF Teleconferences](https://www.w3.org/2002/09/wbs/93339/availability/) - - [Scribe rotation list](https://www.w3.org/WAI/GL/task-forces/conformance-testing/wiki/Scribe_Rotation_List) -- IRC options - - [Join IRC channel](http://irc.w3.org/?channels=#wcag-act) (online using your browser) - - Server: irc.w3.org; Port 6665, 6667, 21, or 994; Channel: #wcag-act +For details of the current work, see the [ACT Task Force wiki](https://www.w3.org/WAI/GL/task-forces/conformance-testing/wiki/). -### Meeting Minutes +## Contribute to the work -[Minutes from previous meetings](https://www.w3.org/WAI/GL/task-forces/conformance-testing/wiki/Meeting_Minutes) are available. +The ACT Task Force welcomes input from the global accessibility community on the ACT Rules work. -### Mailing Lists +### Contribute without joining the task force -The ACT TF uses the public-wcag-act@w3.org mailing list ([mailing list archives](http://lists.w3.org/Archives/Public/public-wcag-act/)) for email discussion. Participants are automatically added to the mailing list when they become a participant of the Task Force. +You can contribute to the work without being a member of the task force in the [ACT GitHub repository](https://github.com/w3c/wcag-act/issues/): +* If you’re aware of an issue with any of the published ACT resources, raise a new issue. +* Comment on or propose solutions for open ACT issues. -### Tools and Information +### Become a participant in the task force -- [ACT TF Work Statement](/about/groups/task-forces/conformance-testing/work-statement/) -- [Wiki main page](https://www.w3.org/WAI/GL/task-forces/conformance-testing/wiki/) - - [ACT Overview](https://www.w3.org/WAI/GL/task-forces/conformance-testing/wiki/ACT_Overview_-_What_is_ACT) - - [Meeting minutes](https://www.w3.org/WAI/GL/task-forces/conformance-testing/wiki/Meeting_Minutes) (also see [automatically collected minutes](https://www.w3.org/WAI/GL/task-forces/conformance-testing/minutes)) - - [Availability for ACT TF Teleconferences](https://www.w3.org/2002/09/wbs/93339/availability/) -- [Mailing list archive](http://lists.w3.org/Archives/Public/public-wcag-act/) -- [Teleconference logistics](https://www.w3.org/WAI/GL/task-forces/conformance-testing/wiki/Teleconference_Logistics) - - [Zoom and IRC setup](https://www.w3.org/WAI/GL/task-forces/conformance-testing/wiki/Zoom_and_IRC_Setup) - - [Scribing instructions](https://www.w3.org/WAI/GL/task-forces/conformance-testing/wiki/Scribing_Instructions) - - [Scribe rotation list](https://www.w3.org/WAI/GL/task-forces/conformance-testing/wiki/Scribe_Rotation_List) -- [Face-to-face meetings](https://www.w3.org/WAI/GL/task-forces/conformance-testing/wiki/Face-to-Face_Meetings) -- GitHub repositories - - [ACT Spec (main)](https://github.com/w3c/wcag-act/) - - [ACT Rules](https://github.com/w3c/wcag-act-rules/) -- [Web-based surveys (WBS)](https://www.w3.org/2002/09/wbs/93339/) +Joining the ACT Task Force enables you to participate fully in the development of the work and influence the deliverables. You and your organization will also be listed as contributors, where appropriate. -## Current Work +Being a participant involves commitment to support the work of the task force in the following ways: -See the [wiki for current planning and draft documents](https://www.w3.org/WAI/GL/task-forces/conformance-testing/wiki/). +* Engage actively in the work using the task force’s communication channels. +* Keep up with weekly tasks and the progress of the work — for example, via the minutes of past meetings, mailing list discussions, and GitHub issue comments. +* Give your input promptly, when it’s needed. -## Publications +To become a participant in the ACT Task Force, you must first be a member of the AG Working Group. See [Instructions for joining the Accessibility Guidelines Working Group](https://www.w3.org/groups/wg/ag/instructions/). -**Accessibility Conformance Testing (ACT) Rules Format 1.0** +Once you are a member of the AG Working Group, email the [W3C Staff Contact for the ACT Task Force](https://www.w3.org/groups/tf/wcag-act/participants/#staff) to let them know you’d like to join the task force. -- W3C Standard: [https://www.w3.org/TR/act-rules-format/](https://www.w3.org/TR/act-rules-format/) -- Errata: [https://www.w3.org/WAI/GL/task-forces/conformance-testing/errata](https://www.w3.org/WAI/GL/task-forces/conformance-testing/errata) +**Note:** As a participant in one of the AG Working Group’s task forces, you can choose to focus your time exclusively on the task force deliverables and you do not have to contribute to the working group’s other activities. -**Accessibility Conformance Testing (ACT) Rules Format 1.1** +## Task force members -- First Public Working Draft: [https://www.w3.org/TR/act-rules-format-1.1/](https://www.w3.org/TR/act-rules-format-1.1/) -- Editor draft: [https://w3c.github.io/wcag-act/act-rules-format.html](https://w3c.github.io/wcag-act/act-rules-format.html) +* [Chairs](https://www.w3.org/groups/tf/wcag-act/participants/#chairs) +* [Current participants](https://www.w3.org/groups/tf/wcag-act/participants/#participants) -**Accessibility Conformance Testing (ACT) Rules Repository** +## Communications -- Published rules: [https://www.w3.org/WAI/standards-guidelines/act/#act-rules-repository](https://www.w3.org/WAI/standards-guidelines/act/#act-rules-repository) -- GitHub repository: [https://github.com/w3c/wcag-act-rules/](https://github.com/w3c/wcag-act-rules/) +* [Calendar of meetings](https://www.w3.org/groups/tf/wcag-act/calendar/) +* [Minutes from previous meetings](https://www.w3.org/WAI/GL/task-forces/conformance-testing/minutes) +* [Mailing list archive](http://lists.w3.org/Archives/Public/public-wcag-act/) -## How to Comment, Contribute, and Participate - -To join the ACT TF, individuals must be participants of the AG WG. Participants are expected to [actively contribute](/about/groups/task-forces/conformance-testing/work-statement/#participation) to the work of the Task Force. If you are interested in participating in the ACT TF, please send e-mail to: [Daniel Montalvo](mailto:dmontalvo@w3.org?subject=ACT%20TF%20Enquiry) and include a little bit about what you're interested in and how you think that you may be able to contribute to the Task Force. Then follow the [AG Working Group participation](/about/groups/agwg/participate/) procedures to join the Working Group, and once you have joined ask [Daniel Montalvo](mailto:dmontalvo@w3.org) to add you to the task force. +## Publications -To contribute without joining the task force, see the [AG Working Group contribute page](/about/groups/agwg/#how-to-comment-contribute-and-participate) for general instructions. To contribute to documents under development, see [GitHub repository](https://github.com/w3c/wcag-act/) directly. +The ACT Task Force develops and maintains the following resources for the AG Working Group: -[Current participants in the ACT TF](https://www.w3.org/2000/09/dbwg/details?group=93339&public=1). +* [Accessibility Conformance Testing (ACT) Rules Format 1.0 — 2019 W3C Recommendation](https://www.w3.org/TR/act-rules-format/) +* [Accessibility Conformance Testing (ACT) Rules Format 1.1 — 2024 First Public Working Draft](https://www.w3.org/TR/act-rules-format-1.1/) +* [ Accessibility Conformance Testing (ACT) Rules Format 1.1 — 2024 Editor’s Draft](https://w3c.github.io/wcag-act/act-rules-format.html) +* [Repository of published Accessibility Conformance Testing (ACT) Rules](https://www.w3.org/WAI/standards-guidelines/act/rules/) -### Work Statement +## Contact the chairs -The [Accessibility Conformance Testing (ACT) Task Force Work Statement](/about/groups/task-forces/conformance-testing/work-statement/) defines the initial objective, scope, approach, and participation of the Task Force. \ No newline at end of file +If you have a question for the ACT Task Force, email the [chairs](https://www.w3.org/groups/tf/wcag-act/participants/#chairs) or the [W3C staff contact](https://www.w3.org/groups/tf/wcag-act/participants/#staff). \ No newline at end of file diff --git a/pages/about/groups/task-forces/conformance-testing/work-statement-2020.md b/pages/about/groups/task-forces/conformance-testing/work-statement-2020.md index cbf5842526d..065b22ab01e 100644 --- a/pages/about/groups/task-forces/conformance-testing/work-statement-2020.md +++ b/pages/about/groups/task-forces/conformance-testing/work-statement-2020.md @@ -1,7 +1,7 @@ --- title: Accessibility Conformance Testing (ACT) Work Statement (2020) -permalink: /about/groups/task-forces/conformance-testing/work-statement/ -ref: /about/groups/task-forces/conformance-testing/work-statement/ +permalink: /about/groups/task-forces/conformance-testing/work-statement-2020/ +ref: /about/groups/task-forces/conformance-testing/work-statement-2020/ lang: en github: label: wai-groups diff --git a/pages/about/groups/task-forces/conformance-testing/work-statement-2024.md b/pages/about/groups/task-forces/conformance-testing/work-statement.md similarity index 81% rename from pages/about/groups/task-forces/conformance-testing/work-statement-2024.md rename to pages/about/groups/task-forces/conformance-testing/work-statement.md index 9b652d572e7..22a4a9a51c6 100644 --- a/pages/about/groups/task-forces/conformance-testing/work-statement-2024.md +++ b/pages/about/groups/task-forces/conformance-testing/work-statement.md @@ -1,17 +1,19 @@ --- -title: Accessibility Conformance Testing (ACT) Work Statement (2024) -permalink: /about/groups/task-forces/conformance-testing/work-statement-2024/ -ref: /about/groups/task-forces/conformance-testing/work-statement-2024/ +title: Accessibility Conformance Testing Task Force Work Statement +permalink: /about/groups/task-forces/conformance-testing/work-statement/ +ref: /about/groups/task-forces/conformance-testing/work-statement/ +redirect_from: + - /about/groups/task-forces/conformance-testing/work-statement-2024/ lang: en github: label: wai-groups --- -The [Accessibility Conformance Testing Task Force (ACT TF)](/about/groups/task-forces/conformance-testing/) is a task force of the [Accessibility Guidelines Working Group (AG WG)](/about/groups/agwg/). It assists this Working Group with the work identified below. +The [Accessibility Conformance Testing (ACT) Task Force](/about/groups/task-forces/conformance-testing/) is a task force of the [Accessibility Guidelines Working Group (AG WG)](/about/groups/agwg/). It assists this Working Group with the work identified below. ## Status -This Work Statement was proposed to AG WG on xx xx 2024 and will be active if approved. The prior [2020 work statement](/about/groups/task-forces/conformance-testing/work-statement-2020work-statement-2020) is available. The [Task Force home page](/about/groups/task-forces/conformance-testing/) contains information about the operation and resources of this group. +This Work Statement was approved by the AG Chairs on 31 January 2025 and is now active. The prior [2020 work statement](/about/groups/task-forces/conformance-testing/work-statement-2020/) is available. The [Task Force home page](/about/groups/task-forces/conformance-testing/) contains information about the operation and resources of this group. Objective --------- @@ -22,6 +24,7 @@ ACT TF's objective is to evolve and maintain a repository of ACT Rules for [Web The work of the Accessibility Conformance Testing (ACT) Task Force includes: +* **ACT Rules Format:** Update the [ACT Rules Format](https://www.w3.org/TR/act-rules-format/) to version 1.1 * **Repository of ACT Rules:** Review ACT Rules contributed to W3C, such as from [Accessibility Conformance Testing Rules Community Group (ACT-R CG)](https://act-rules.github.io/), and maintain a repository of rules approved by W3C Working Groups, including AG and ARIA * **Implementations Monitoring:** Encourage and gather implementation reports from accessibility test tools and methodologies for ACT Rules published by AG WG * **Specification Maintenance:** Maintain [Errata](https://www.w3.org/WAI/GL/task-forces/conformance-testing/errata) for [ACT Rules Format 1.0 specification](https://www.w3.org/TR/act-rules-format/), and gather feature requests for future versions of this specification @@ -39,10 +42,10 @@ ACT TF will continue to gather implementation experience, including of the [ACT The Accessibility Conformance Testing (ACT) Task Force depends on: * [AG WG](/about/groups/agwg/) to ensure accurate interpretation and representation of WCAG requirements; -* [ARIA WG](/about/groups/aria/) to ensure accurate interpretation and representation of WAI-ARIA requirements; +* [ARIA WG](/about/groups/ariawg/) to ensure accurate interpretation and representation of WAI-ARIA requirements; * [ACT Rules Community Group](https://act-rules.github.io/) to utilize this group's contribution on conformance testing. -The Accessibility Conformance Testing (ACT) Task Force will also coordinate with relevant W3C groups and activities on testing and quality assurance. This may include groups such as [Browser Testing and Tools Working Group](https://www.w3.org/testing/browser/). The Task Force may also coordinate with the [Education and Outreach Working Group (EOWG)](/about/groups/eo/) where necessary to improve the writing, presentation, and educational value of the developed materials. +The Accessibility Conformance Testing (ACT) Task Force will also coordinate with relevant W3C groups and activities on testing and quality assurance. This may include groups such as [Browser Testing and Tools Working Group](https://www.w3.org/groups/wg/browser-tools-testing/). ## Communication @@ -67,7 +70,7 @@ Participants may also join Accessibility Conformance Testing Task Force sub-grou If you are interested in becoming a participant of the Accessibility Conformance Testing Task Force or have any questions regarding its work, contact the task force facilitators. -[Current participants in the ACT TF](https://www.w3.org/groups/tf//wcag-act/participants). +[Current participants in the ACT TF](https://www.w3.org/groups/tf/wcag-act/participants). ## Facilitation @@ -76,8 +79,8 @@ Staff contacts from the AG Working Group oversee attention to W3C Process with r * **Facilitators:** * Wilco Fiers, Deque Systems * Kathy Eng, Access Board -* **Staff Contact:** [Daniel Montalvo](https://www.w3.org/staff/#dmontalvo/) +* **Staff Contact:** [Daniel Montalvo](https://www.w3.org/staff/#dmontalvo) ## Patent Policy -This Task Force is part of the [AG Working Group Charter](https://www.w3.org/WAI/GL/charter), which operates under the [W3C Patent Policy](https://www.w3.org/Consortium/Patent-Policy-20040205/) (5 February 2004 Version). W3C maintains a public list of any patent disclosures made in connection with the deliverables of the [AG Working Group](https://www.w3.org/2004/01/pp-impl/35422/status). \ No newline at end of file +This Task Force is part of the [AG Working Group Charter](https://www.w3.org/WAI/GL/charter), which operates under the [W3C Patent Policy](https://www.w3.org/policies/patent-policy/20200915/) (15 September 2020 Version). W3C maintains a public list of any patent disclosures made in connection with the deliverables of the [AG Working Group](https://www.w3.org/2004/01/pp-impl/35422/status). \ No newline at end of file diff --git a/pages/about/groups/task-forces/fast.md b/pages/about/groups/task-forces/fast.md new file mode 100644 index 00000000000..4b8d2893760 --- /dev/null +++ b/pages/about/groups/task-forces/fast.md @@ -0,0 +1,93 @@ +--- +title: Framework for Accessible Specification of Technologies Task Force +permalink: /about/groups/task-forces/fast/ +ref: /about/groups/task-forces/fast/ +lang: en +github: + label: wai-groups +--- + +{::nomarkdown} +{% include box.html type="start" title="Summary" class="" %} +{:/} + +Find out about the activities of the Framework for Accessible Specification of Technologies (FAST) Task Force and how you can contribute to its objectives. + +{::nomarkdown} +{% include box.html type="end" %} +{:/} + +{::options toc_levels="2..3" /} + +{::nomarkdown} +{% include_cached toc.html type="start" title="Page Contents" %} +{:/} + +- TOC is created automatically. +{:toc} + +{::nomarkdown} +{% include_cached toc.html type="end" %} +{:/} + +## Objectives + +The objectives of the FAST Task Force are to develop and maintain inventories of user and functional needs; best practices guidance describing the features that web technologies should provide to ensure accessible content can be created; and the self-assessment tool used by W3C working groups during W3C’s accessibility horizontal review process. + +## Work statement + +To learn about the focus, scope and deliverables of the task force, see the [FAST Task Force Work Statement](https://www.w3.org/WAI/APA/wiki/Fast-work-statement). + +## Current work + +The FAST Task Force supports the deliverables of the [Accessible Platform Architectures (APA) Working Group](/about/groups/apawg/). + +For details of the current work, see the [FAST GitHub repository](https://github.com/w3c/fast). + +## Contribute to the work + +The FAST Task Force welcomes input from the global accessibility community on the FAST work. + +### Contribute without joining the task force + +You can contribute to the work without being a member of the task force in the [FAST GitHub repository](https://github.com/w3c/fast/issues): +* If you’re aware of an issue with any of the published FAST resources, raise a new issue. +* Comment on or propose solutions for open FAST issues. + +### Become a participant in the task force + +Joining the FAST Task Force enables you to participate fully in the development of the work and influence the deliverables. You and your organization will also be listed as contributors, where appropriate. + +Being a participant involves commitment to support the work of the task force in the following ways: + +* Engage actively in the work using the task force’s communication channels. +* Keep up with weekly tasks and the progress of the work — for example, via the minutes of past meetings, mailing list discussions, and GitHub issue comments. +* Give your input promptly, when it’s needed. + +To become a participant in the FAST Task Force, you must first be a member of the APA Working Group. See [Instructions for joining the Accessible Platform Architectures Working Group](https://www.w3.org/groups/wg/apa/instructions/). + +Once you are a member of the APA Working Group, email the [W3C Staff Contact for the FAST Task Force](https://www.w3.org/groups/tf/fast/participants/#staff) to let them know you’d like to join the task force. + +**Note:** As a participant in one of the APA Working Group’s task forces, you can choose to focus your time exclusively on the task force deliverables and you do not have to contribute to the working group’s other activities. + +## Task force members + +* [Chairs](https://www.w3.org/groups/tf/fast/participants/#chairs) +* [Current participants](https://www.w3.org/groups/tf/fast/participants/#participants) + +## Communications + +* [Calendar of meetings](https://www.w3.org/groups/tf/fast/calendar/) +* [Minutes from previous meetings](https://www.w3.org/WAI/APA/task-forces/fast/minutes) +* [Mailing list archive](https://lists.w3.org/Archives/Public/public-fast/) + +## Publications + +The FAST Task Force develops and maintains the following resources for the APA Working Group: + +* [Framework for Accessible Specification of Technologies (FAST) — 2024 Editor’s Draft](https://www.w3.org/TR/act-rules-format/) +* [FAST Report Tool](https://fast-rose.vercel.app/) — a checklist for reviewing technologies + +## Contact the chairs + +If you have a question for the FAST Task Force, email the [chairs](https://www.w3.org/groups/tf/fast/participants/#chairs) or the [W3C staff contact](https://www.w3.org/groups/tf/fast/participants/#chairs). \ No newline at end of file diff --git a/pages/about/groups/task-forces/low-vision-a11y-tf.md b/pages/about/groups/task-forces/low-vision-a11y-tf.md index e3480df0e09..353503b627c 100644 --- a/pages/about/groups/task-forces/low-vision-a11y-tf.md +++ b/pages/about/groups/task-forces/low-vision-a11y-tf.md @@ -1,5 +1,5 @@ --- -title: Low Vision Accessibility Task Force (LVTF) of the AG WG +title: Low Vision Accessibility Task Force permalink: /about/groups/task-forces/low-vision-a11y-tf/ ref: /about/groups/task-forces/low-vision-a11y-tf/ lang: en @@ -11,9 +11,7 @@ github: {% include box.html type="start" title="Summary" class="" %} {:/} -The Low Vision Accessibility Task Force (LVTF) is a task force of the [Accessibility Guidelines Working Group (AG WG)](/about/groups/agwg/). The objective of the Task Force is to address web accessibility issues specific to people with low vision. - -Some information on this page is also shown on, and may be more current in, the [automatically generated Low Vision Accessibility Task Force page](https://www.w3.org/groups/tf/low-vision-a11y-tf). +Find out about the activities of the Low Vision Accessibility (LV) Task Force and how you can contribute to its objectives. {::nomarkdown} {% include box.html type="end" %} @@ -32,90 +30,54 @@ Some information on this page is also shown on, and may be more current in, the {% include_cached toc.html type="end" %} {:/} -## Announcements - -The LVTF work is listed in the [LVTF main wiki page](https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Main_Page). - -## Publications - -[LVTF Documents wiki page](https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/LVTF_Documents) lists LVTF publications. +## Objectives -## Task Force Meetings and Participation Channels +The objective of the LV Task Force is to address web accessibility issues that are specific to people with low vision through inputting into WCAG 2 techniques and understanding documents; inputting into WCAG 3; and developing additional low-vision guidance resources. -Task Force meets regularly by teleconference, and plans to hold face-to-face meetings 1-2 times a year in the future. +## Work statement -Updated information on LVTF meetings is on the [LVTF main wiki page, under "Meetings"](https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Main_Page#Meetings). +To learn about the focus, scope and deliverables of the task force, see the [Low Vision Accessibility Task Force Work Statement](/about/groups/task-forces/low-vision-a11y-tf/work-statement/). -**IRC channel**: [#lvtf](irc://irc.w3.org/lvtf) +## Current work -Asynchronous participation: +**Note:** The LV Task Force is currently inactive. W3C is working towards reactivating it in 2025. -- **Email**: [public-low-vision-a11y-tf@w3.org](mailto:public-low-vision-a11y-tf@w3.org) (public [archive](https://lists.w3.org/Archives/Public/public-low-vision-a11y-tf/)) -- **Wiki**: [https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Main\_Page](https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Main_Page) -- **Surveys**: [https://www.w3.org/2002/09/wbs/81151/](https://www.w3.org/2002/09/wbs/81151/) +The LV Task Force supports the deliverables of the [Accessibility Guidelines (AG) Working Group](/about/groups/agwg/). -### Meeting Minutes +For details of the work, see the [LV Task Force wiki](https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Main_Page). -[Minutes from previous meetings](https://www.w3.org/WAI/GL/task-forces/low-vision-a11y-tf/minutes) are available. +## Contribute to the work -## About the Low Vision Accessibility Task Force +The LV Task Force welcomes input from the global accessibility community on the low vision accessibility work. -The Low Vision Accessibility Task Force (LVTF) was created as a task force of the [Accessibility Guidelines Working Group (AG WG)](/about/groups/agwg/) and the [User Agent Accessibility Guidelines Working Group (UAWG)](https://www.w3.org/WAI/UA/). The UAWG has closed. +### Contribute without joining the task force -The objective of the Task Force is to address web accessibility issues specific to people with low vision. Task Force work includes: +You can contribute to the work without being a member of the task force. -- Document accessibility requirements/needs for people with low vision -- Identify gaps between user needs and existing requirements in [WCAG](https://www.w3.org/WAI/intro/wcag), [UAAG](https://www.w3.org/WAI/intro/uaag), [ATAG](https://www.w3.org/WAI/intro/atag) -- Document sufficient techniques, advisory techniques, and failures for WCAG 2 related to low vision -- Develop supplemental guidance to address low vision beyond WCAG 2 -- Contribute to WCAG 3 requirements and guidance related to low vision -- Potentially refine [user agent use cases](https://www.w3.org/TR/UAAG20-Reference/) for low vision -- Develop support materials to explain the issues and implementation of the above resources effectively +If you’re aware of an issue with any of the published low vision accessibility resources, email [public-low-vision-a11y-tf@w3.org](mailto:public-low-vision-a11y-tf@w3.org). -### Facilitators and Contacts +### Become a participant in the task force -- **Task Force co-facilitators:** - - Chris Loiselle - - Jonathan Avila -- **Staff Contact:** [Shawn Lawton Henry](https://www.w3.org/People/#shawn) +Details of how to join the LV Task Force will be published here when it is reactivated. -### Work Statement +## Task force members -- Initial [Low Vision Accessibility Task Force Work Statement](/about/groups/task-forces/low-vision-a11y-tf/work-statement/) (some details have changed since then) +* [Chairs](https://www.w3.org/groups/tf/low-vision-a11y-tf/participants/#chairs) +* [Current participants](https://www.w3.org/groups/tf/low-vision-a11y-tf/participants/#participants) -### Mailing List +## Communications -[public-low-vision-a11y-tf@w3.org](mailto:public-low-vision-a11y-tf@w3.org) (public [archive](https://lists.w3.org/Archives/Public/public-low-vision-a11y-tf/)) +* [Calendar of meetings](https://www.w3.org/groups/tf/low-vision-a11y-tf/calendar/) +* [Minutes from previous meetings](https://www.w3.org/WAI/GL/task-forces/low-vision-a11y-tf/minutes) +* [Mailing list archive](https://lists.w3.org/Archives/Public/public-low-vision-a11y-tf/) -When using the Low Vision Accessibility Task Force mailing list: - -1. Treat other list members with respect. -2. Keep comments within the scope of this group (see [Low Vision Accessibility Task Force Work Statement](/about/groups/task-forces/low-vision-a11y-tf/work-statement/)). -3. When raising an issue: - - provide a clear subject line including the topic it relates to - - explain the issue briefly - - propose a brief & specific solution - - for longer comments, put a summary at the beginning -4. When replying: - - keep your reply comments near the top of a message - - only quote essential parts of a previous message - - if there are multiple topics, break them into separate emails to facilitate threading and to keep the subject line accurate -5. Please send any questions about the mailing list itself to the Facilitators or Staff Contacts, not the whole list. -6. No soliciting. - -## Participation - -To participate in the Low Vision Accessibility Task Force, individuals must also be participants of the AG WG. (You don't have to have previously participated in AG WG. You do have to sign up to participate in AG WG in order to participate in LVTF). - -Participants are expected to actively contribute to the work of LVTF, including: +## Publications -- Minimum 4 hours per week of LVTF work (this time counts towards the individual's participation requirement in the AG WG) -- Complete [LVTF surveys](https://www.w3.org/2002/09/wbs/81151/all) -- Remain current on the [LVTF mailing list](https://lists.w3.org/Archives/Public/public-low-vision-a11y-tf/) and respond in a timely manner to postings -- Participate in LVTF teleconferences, or record regrets in the [Availability for Upcoming LVTF Teleconferences Survey](https://www.w3.org/2002/09/wbs/81151/LVTF-telecons/) +The LV Task Force develops and maintains the following resources for the AG Working Group: -To become a participant of Low Vision Accessibility Task Force or if you have questions, contact [the Facilitators and Team contact via mailto:group-lvtf-plan@w3.org](mailto:group-lvtf-plan@w3.org?subject=Low Vision Accessibility Task Force Enquiry). +* [Accessibility Requirements for People with Low Vision — 2016 First Public Working Draft](https://www.w3.org/TR/low-vision-needs/) +* [Accessibility Requirements for People with Low Vision — 2023 Editor’s Draft](https://w3c.github.io/low-vision-a11y-tf/requirements.html) -### Patent Disclosures +## Contact the chairs -This Task Force is part of the [AG WG Charter](https://www.w3.org/WAI/GL/charter), which operates under the [W3C Patent Policy](https://www.w3.org/WAI/GL/charter#patentpolicy). W3C maintains a public list of any patent disclosures made in connection with the deliverables of the [AG WG](https://www.w3.org/2004/01/pp-impl/35422/status). \ No newline at end of file +If you have a question for the LV Task Force, email the [chairs](https://www.w3.org/groups/tf/low-vision-a11y-tf/participants/#chairs) or the [W3C staff contact](https://www.w3.org/groups/tf/low-vision-a11y-tf/participants/#staff). \ No newline at end of file diff --git a/pages/about/groups/task-forces/low-vision-a11y-tf/work-statement.md b/pages/about/groups/task-forces/low-vision-a11y-tf/work-statement.md index 94c7829a08b..356e9e9ca82 100644 --- a/pages/about/groups/task-forces/low-vision-a11y-tf/work-statement.md +++ b/pages/about/groups/task-forces/low-vision-a11y-tf/work-statement.md @@ -1,5 +1,5 @@ --- -title: Low Vision Accessibility Task Force Work Statement) +title: Low Vision Accessibility Task Force Work Statement permalink: /about/groups/task-forces/low-vision-a11y-tf/work-statement/ ref: /about/groups/task-forces/low-vision-a11y-tf/work-statement/ lang: en @@ -22,7 +22,7 @@ github: This Work Statement was approved in 2015. Updated information is available from the [Low Vision Accessibility Task Force home page](/about/groups/task-forces/low-vision-a11y-tf/) and [wiki page](https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Main_Page). -The Low Vision Accessibility Task Force (Low Vision A11Y TF) is a task force of the [Accessibility Guidelines Working Group (AG WG)](/about/groups/agwg/) (formerly also of the [User Agent Accessibility Guidelines Working Group (UAWG)](https://www.w3.org/WAI/UA/) which has closed). It assists this Working Group with the work identified below. +The Low Vision (LV) Accessibility Task Force is a task force of the [Accessibility Guidelines Working Group (AG WG)](/about/groups/agwg/) (formerly also of the [User Agent Accessibility Guidelines Working Group (UAWG)](https://www.w3.org/WAI/UA/) which has closed). It assists this Working Group with the work identified below. ## Status diff --git a/pages/about/groups/task-forces/matf.md b/pages/about/groups/task-forces/matf.md index 873d97f0464..42cdf834e76 100644 --- a/pages/about/groups/task-forces/matf.md +++ b/pages/about/groups/task-forces/matf.md @@ -1,5 +1,5 @@ --- -title: Mobile Accessibility Task Force (MATF) of the AG WG +title: Mobile Accessibility Task Force permalink: /about/groups/task-forces/matf/ ref: /about/groups/task-forces/matf/ lang: en @@ -11,9 +11,7 @@ github: {% include box.html type="start" title="Summary" class="" %} {:/} -The Mobile Accessibility Task Force (MATF) is a task force of the [Accessibility Guidelines Working Group (AG WG)](/about/groups/agwg/). - -Some information on this page is also shown on, and may be more current in, the [Mobile Accessibility Task Force page](https://www.w3.org/groups/tf/mobile-a11y-tf/). +Find out about the activities of the Mobile Accessibility (Mobile A11y) Task Force and how you can contribute to its objectives. {::nomarkdown} {% include box.html type="end" %} @@ -32,65 +30,67 @@ Some information on this page is also shown on, and may be more current in, the {% include_cached toc.html type="end" %} {:/} -## Announcements and Meetings +## Objectives -_4 January 2024_ **New facilitator appointed**: Jan Jaap de Groot has been appointed as the new MATF facilitator. The MATF direction is changing to creating guidance for Android and iOS apps. The MATF is currently regrouping and welcoming new participants. If you are interested, please reach out to Jan Jaap at: [janjaap@abra.nl](mailto:janjaap@abra.nl) +The objectives of the Mobile A11y Task Force are to produce resources for how to apply the Web Content Accessibility Guidelines (WCAG) to mobile — including, but not limited to, native mobile apps; mobile web apps; mobile web content; and hybrid apps that use web components inside native mobile apps — and to make sure mobile apps are considered in new accessibility guidelines. -## Meetings and Communication +## Work statement -The Mobile Accessibility Task Force conducts its work using a variety of synchronous and asynchronous tools. Most work is done via email and issues as shown below, supplemented by occasional teleconferences. +The Mobile A11y Task Force has regrouped in 2024 and a new Work Statement will be published soon. -- [Email lists](#mailing-lists); -- IRC discussion (server: **irc.w3.org**, port: **6665,** channel: **#matf**) is used by some members during the teleconferences. Please type "present+" _your name_ in the IRC channel when joining a meeting.; -- [Web-Based Surveys (WBS)](https://www.w3.org/2002/09/wbs/66524/); +## Current work -These tools are used by participants of the Task Force. For ways non-participants can contribute, see how to [participate in the Working Group](/about/groups/agwg/participate/). +The Mobile A11y Task Force supports the deliverables of the [Accessibility Guidelines (AG) Working Group](/about/groups/agwg/). -### Online Meetings +For details of the current work, see the [Mobile A11y Task Force GitHub repository](https://github.com/w3c/matf/issues). -- [Meetings Calendar of the Mobile Accessibility Task Force](https://www.w3.org/groups/tf/mobile-a11y-tf/calendar/) +## Contribute to the work -### Meeting Minutes +The Mobile A11y Task Force welcomes input from the global accessibility community on mobile accessibility work. -- [Recent Meeting Minutes](https://www.w3.org/groups/tf/mobile-a11y-tf/calendar/?past=1&tf=0) -- [Older Meeting Minutes](https://www.w3.org/WAI/GL/task-forces/matf/minutes) +### Contribute without joining the task force -### Mailing Lists +You can contribute to the work without being a member of the task force in the [Mobile A11y GitHub repository](https://github.com/w3c/Mobile-A11y-TF-Note/issues): +* If you’re aware of an issue with any of the published mobile accessibility resources, raise a new issue. +* Comment on or propose solutions for open mobile accessibility issues. -- The Mobile Accessibility Task Force uses the public-mobile-a11y-tf@w3.org mailing list for email discussion; members of the public can post to this list to send input to the task force. Mobile Accessibility Task Force [mailing list archives](http://lists.w3.org/Archives/Public/public-mobile-a11y-tf/) are publicly available for the Mobile A11Y TF main mailing list. -- Participants are automatically added to the mailing list when the become a participant of the Task Force. +### Become a participant in the task force -## Current Work +Joining the Mobile A11y Task Force enables you to participate fully in the development of the work and influence the deliverables. You and your organization will also be listed as contributors, where appropriate. -The [editors' draft of Mobile Accessibility: How WCAG 2.0 and Other W3C/WAI Guidelines Apply to Mobile](http://w3c.github.io/Mobile-A11y-TF-Note/) is on Github. [Issues and pull requests](https://github.com/w3c/Mobile-A11y-TF-Note) are welcome. +Being a participant involves commitment to support the work of the task force in the following ways: -The Task Force stores their current work and discussions in their [wiki](https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/Main_Page). You can also follow email discussion on the [email list archive](http://lists.w3.org/Archives/Public/public-mobile-a11y-tf/). +* Engage actively in the work using the task force’s communication channels. +* Keep up with weekly tasks and the progress of the work — for example, via the minutes of past meetings, mailing list discussions, and GitHub issue comments. +* Give your input promptly, when it’s needed. -- Creating mobile techniques for WCAG using HTML5, ARIA, CSS and JavaScript - - Editor's Draft: [Mobile Accessibility: How WCAG 2.0 and UAAG 2.0 Apply to Mobile Devices](http://w3c.github.io/Mobile-A11y-TF-Note/) - - [Draft WCAG Techniques](https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/Draft_WCAG_Techniques "Draft WCAG Techniques") - - [Draft Understanding WCAG 2.0](https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/Draft_Understanding_WCAG_2.0 "Draft Understanding WCAG 2.0") -- Developing design guidance or mobile web accessibility best practices - - [Gap Analysis Discussion: BBC Mobile Guidelines](https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/Discussion:_BBC_Mobile_Guidelines "Discussion: BBC Mobile Guidelines") - - [Gap Analysis](https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/Discussion:_BBC_Mobile_Guidelines "Discussion: BBC Mobile Guidelines") [Discussion: Funka Nu Mobile Accessibility Guidelines](https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/Discussion:_Funka_Nu_Mobile_Accessibility_Guidelines "Discussion: Funka Nu Mobile Accessibility Guidelines") - - [Gap Analysis Discussion: IBM Accessibility Guidelines](https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/Discussion:_IBM "Discussion: IBM") - - [Accessibility Concerns in Responsive Design for Mobile](https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/Responsive_Design) -- [Reviewing existing resources](https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/Mobile_Resources), including those outside of W3C +To become a participant in the Mobile A11y Task Force, you must first be a member of the AG Working Group. See [Instructions for joining the Accessibility Guidelines Working Group](https://www.w3.org/groups/wg/ag/instructions/). -## Publications +Once you are a member of the AG Working Group, email the [W3C Staff Contact for the Mobile A11y Task Force](https://www.w3.org/groups/tf/mobile-a11y-tf/participants/#staff) to let them know you’d like to join the task force. + +**Note:** As a participant in one of the AG Working Group’s task forces, you can choose to focus your time exclusively on the task force deliverables and you do not have to contribute to the working group’s other activities. -- Editor's Draft: [Mobile Accessibility: How WCAG 2.0 and UAAG 2.0 Apply to Mobile Devices](http://w3c.github.io/Mobile-A11y-TF-Note/) +## Task force members -### Work Statement +* [Chair](https://www.w3.org/groups/tf/mobile-a11y-tf/participants/#chairs) +* [Current participants](https://www.w3.org/groups/tf/mobile-a11y-tf/participants/#participants) -The MATF is currently regrouping and creating a new Work Statement for its new direction. +## Communications + +* [Calendar of meetings](https://www.w3.org/groups/tf/mobile-a11y-tf/calendar/) +* Minutes from previous meetings of the Mobile A11y Task Force: + * [Minutes from January 2024](https://www.w3.org/groups/tf/mobile-a11y-tf/calendar/?past=1&tf=0) + * [Minutes from 2013 to 2021](https://www.w3.org/WAI/GL/task-forces/matf/minutes) +* [Mailing list archive](https://lists.w3.org/Archives/Public/public-mobile-a11y-tf/) + +## Publications -### Participation +The Mobile A11y Task Force develops and maintains the following resources for the AG Working Group; -To join the Mobile Accessibility Task Force, individuals must be participants of the [Accessibility Guidelines Working Group (AG WG)](/about/groups/agwg/). Participants are expected to actively contribute to the work of the Task Force, including: +* [Mobile Accessibility: How WCAG 2.0 and Other W3C/WAI Guidelines Apply to Mobile — 2015 First Public Working Draft](https://www.w3.org/TR/mobile-accessibility-mapping/) +* [Mobile Accessibility: How WCAG 2.0 and Other W3C/WAI Guidelines Apply to Mobile — 2018 Editor's Draft](http://w3c.github.io/Mobile-A11y-TF-Note/) +* [Guidance on Applying WCAG 2.2 to Mobile (WCAG2Mobile) — 2024 Editor's Draft](https://w3c.github.io/matf/) -- Minimum 2 hours per week of MATF work (this time also counts towards the individual's participation requirement in the sponsoring WG through which they have joined); -- Remain current on the MATF mailing list and respond in a timely manner to postings; -- Participate in MATF meetings at least once per month. +## Contact the chair -If you are interested in participating in the Mobile Accessibility Task Force, please send e-mail to: [Jan Jaap de Groot](mailto:janjaap@abra.nl), [Kevin White](mailto:kevin@w3.org) and [Roy Ran](mailto:ran@w3.org) include a little bit about what you’re interested in and how you think that you may be able to contribute to the Task Force. \ No newline at end of file +If you have a question for the Mobile A11y Task Force, email the [chair](https://www.w3.org/groups/tf/mobile-a11y-tf/participants/#chairs) or the [W3C staff contact](https://www.w3.org/groups/tf/mobile-a11y-tf/participants/#staff). \ No newline at end of file diff --git a/pages/about/groups/task-forces/matf/work-statement.md b/pages/about/groups/task-forces/matf/work-statement.md new file mode 100644 index 00000000000..9c79658c2b3 --- /dev/null +++ b/pages/about/groups/task-forces/matf/work-statement.md @@ -0,0 +1,144 @@ +--- +title: Mobile Accessibility Task Force Work Statement +permalink: /about/groups/task-forces/matf/work-statement/ +ref: /about/groups/task-forces/matf/work-statement/ +lang: en +github: + label: wai-groups +--- + +{::options toc_levels="2..3" /} + +{::nomarkdown} +{% include_cached toc.html type="start" title="Page Contents" %} +{:/} + +- TOC is created automatically. +{:toc} + +{::nomarkdown} +{% include_cached toc.html type="end" %} +{:/} + +The Mobile Accessibility Task Force (MATF) is a task force of the [Accessibility Guidelines Working Group (AG WG)](/about/groups/agwg/). It assists this Working Group with the work identified below. + +## Status + +This work statement is a draft yet to be approved. The task force is active. + +NOTE: This work is mentioned in the [Other Deliverables section of the current AG WG Charter.](https://www.w3.org/2019/12/ag-charter#ig-other-deliverables) The continuation of the work is also included in the [current AG WG Charter](https://www.w3.org/2023/11/ag-charter). + +## Objective + +The objective of the Task Force is to produce informative resources for applying WCAG to Mobile Applications, including but not limited to native mobile apps, mobile web apps, mobile web content, and hybrid apps using web components inside native mobile apps. + +In addition, the Task Force will draft informative methods that can be applied to make Mobile Applications accessible, which may be included in future versions of WCAG. + +## Scope of Work + +The work of the Task Force includes: + +1. Publishing an updated [W3C Group Note](https://www.w3.org/standards/types/) on how WCAG 2.2 applies to Native Mobile Apps. +2. Drafting informative methods to make Mobile Applications accessible. +3. Collaborating with and supporting other Working Groups and Task Forces by providing Mobile Accessibility expertise. +4. Updating resources which have been created by the MATF, deprecating those who are no longer deemed relevant. + + +## Approach + +The primary effort of this Task Force is to describe how to interpret WCAG 2.2 and its Principles, Guidelines, Success Criteria and Conformance Requirements when applying them to Mobile Applications. + +The resulting W3C Group Note will include specific considerations for native mobile apps, mobile web apps, mobile web content, and hybrid apps using web components inside native mobile apps. + +The work will be carried out iteratively with continual involvement of the public throughout the development. In particular, key stakeholders such as developers, designers, researchers, accessibility experts and users will be regularly involved in the development process. Key participants will be drawn from people who are actively involved in developing Mobile Applications in various roles. + +The work may be broken down into-subgroups to improve efficiency. Success Criteria at Level A and AA will be prioritized before addressing Level AAA. + +## Timeline + +The following sections contain rough timelines for the MATF work. Our goal is to publish a W3C Group Note in the first half of 2025. + +Actual timelines and project management will be handled outside of this work statement, and will not be maintained herein. + +**Phase 1: January - March 2024** + +* Recruit new participants with relevant experience; +* Choose new day(s) and time(s) for meetings; +* Choose tools used for developing guidance; +* Figure out efficient way of collaborating; +* List existing resources for applying WCAG to Mobile Applications. + +**Phase 2: April - June 2024** + +* Develop an initial draft, focusing on Success Criteria at Level A; +* Publish Level A draft on Github; +* Request feedback from stakeholders, participants and AG WG. + +**Phase 3: July - September 2024** + +* Develop second draft, process feedback, add Success Criteria at Level AA; +* Publish Level AA draft on Github; +* Request and process feedback from stakeholders, participants and AG WG. + +**Phase 4: October - December 2024** + +* Publish an First Public Working Draft through W3C, taking all feedback into account; +* Process feedback from the public, stakeholders, participants and AG WG; +* Publish new W3C Group Note. + +**Phase 5: January - March 2025** + +* Expand Working Group Note with guidance for Level AAA criteria; +* Publish Level AAA draft on Github; +* Request and process feedback from stakeholders, participants and AG WG. + +**Phase 6: April - June 2025** + +* Publish a Group Note through W3C, taking all feedback into account; +* Process feedback from the public, stakeholders, participants and AG WG; +* Publish updated W3C Group Note. + +## Dependencies + +The MATF depends on the [AG WG](/about/groups/agwg/) to ensure accurate interpretation and representation of WCAG requirements. + +The MATF harmonizes with the [WCAG2ICT Task Force](/about/groups/task-forces/wcag2ict/) to ensure the developed guidance for Mobile Applications aligns with their guidance for Non-Web ICT. + +The MATF collaborates with the [Accessibility Conformance Testing Task Force (ACT)](/about/groups/task-forces/conformance-testing/) on rules for testing Mobile Applications. + +The MATF will also coordinate with the [Accessible Platform Architectures Working Group (APA)](/about/groups/apawg/), for technical advice and Education and Outreach Working Group (EOWG) where necessary to improve the writing, presentation, and educational value of the developed materials. + +## Communication + +The MATF communications are publicly visible. Communication mechanisms for the MATF include: + +* [MATF public mailing list](mailto:public-mobile-a11y-tf@w3.org) and [MATF mailing list archive](https://lists.w3.org/Archives/Public/public-mobile-a11y-tf/) +* [W3C Community Slack](https://www.w3.org/slack-w3ccommunity-invite), channel **#matf** +* [Github](https://github.com/w3c/matf), [Github Issues](https://github.com/w3c/matf/issues), [Github Wiki](https://github.com/w3c/matf/wiki) +* [Weekly online meetings](https://www.w3.org/groups/tf/mobile-a11y-tf/calendar/) with [Meeting Minutes](https://www.w3.org/groups/tf/mobile-a11y-tf/calendar/?past=1&tf=0) +* IRC server: **webirc.w3.org**, port: **6665**, channel: **#matf** (during meetings) + +## Participation + +MATF participants must join the Task Force through the AG WG, which includes representatives of [W3C Member Organizations](https://www.w3.org/membership/list/) as well as [Invited Experts](https://www.w3.org/invited-experts/). Task Force participants must agree to actively contribute to the work of the MATF, including: + +* Minimum 2 hours per week of MATF work (this time also counts towards the individual's participation requirement in the sponsoring WG through which they have joined); +* Remain current on the MATF mailing list and respond in a timely manner to postings; +* Participate in MATF meetings at least once per month. + +If you are interested in becoming a participant of the WCAG 2 Task Force or have any questions regarding its work, contact the task force facilitators. + +[Current MATF participants](https://www.w3.org/groups/tf/mobile-a11y-tf/participants/) + +Contact [Kevin White](mailto:kevin@w3.org) to become a participant of the WCAG 2 Task Force or with questions. + +## Facilitation + +Staff contacts from the Accessibility Guidelines 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 Working Group. + +* [Chair](https://www.w3.org/groups/tf/wcag2x-backlog/mobile-a11y-tf/#chairs) +* [Staff Contact](https://www.w3.org/groups/tf/wcag2x-backlog/mobile-a11y-tf/#staff) + +## Patent Policy + +This Task Force is part of the [AG Working Group Charter](https://www.w3.org/WAI/GL/charter), which operates under the [W3C Patent Policy](https://www.w3.org/Consortium/Patent-Policy-20200915/) (15 September 2020 Version). W3C maintains a public list of any patent disclosures made in connection with the deliverables of the [AG Working Group](https://www.w3.org/groups/wg/ag/ipr). \ No newline at end of file diff --git a/pages/about/groups/task-forces/maturity-model.md b/pages/about/groups/task-forces/maturity-model.md index 489aa12b4d8..3a330c30f6b 100644 --- a/pages/about/groups/task-forces/maturity-model.md +++ b/pages/about/groups/task-forces/maturity-model.md @@ -1,5 +1,5 @@ --- -title: Maturity Model Task Force of the APA WG +title: Maturity Model Task Force permalink: /about/groups/task-forces/maturity-model/ ref: /about/groups/task-forces/maturity-model/ lang: en @@ -11,9 +11,7 @@ github: {% include box.html type="start" title="Summary" class="" %} {:/} -The Maturity Model Task Force is a task force of the [Accessible Platform Architectures Working Group](/about/groups/apawg/). - -Some information on this page is also shown on, and may be more current in, the [Maturity Model Task Force page](https://www.w3.org/groups/tf/maturity/). +Find out about the activities of the Maturity Model (MM) Task Force and how you can contribute to its objectives. {::nomarkdown} {% include box.html type="end" %} @@ -32,67 +30,65 @@ Some information on this page is also shown on, and may be more current in, the {% include_cached toc.html type="end" %} {:/} -## Announcements - -No announcements at the moment. +## Objectives -## Mission +The objective of the Maturity Model (MM) Task Force is to provide an Accessibility Maturity Model to guide organizations in developing the capability to buy, build or use accessible internal and external products and services, and to help them track changes and trends in providing these products and services over time. -The mission of the Maturity Model Task Force (MMTF) is to craft an Accessibility Maturity Model (AMM) narrative and assessment tool in support of W3C standards and other related guidance, such as Web Content Accessibility Guidelines (WCAG) and Accessibility Rich Internet Applications (ARIA), in consultation with the APA Working Group. Specifically, the MMTF Accessibility Maturity Model will assist organizations in building capacity to develop, and maintain, accessible products or services. -For more information (including scope of work and expected deliverables) please reference the [Maturity Model Task Force Work Statement](/about/groups/task-forces/maturity-model/work-statement/). +## Work statement -## Meetings and Communication +To learn about the focus, scope and deliverables of the task force, see the [MM Task Force Work Statement](/about/groups/task-forces/maturity-model/work-statement/). -The [communication](https://www.w3.org/2017/08/telecon-info_maturity-model) page provides details about: +## Current work -- Teleconferences of the Task Force (also see [meeting minutes](https://www.w3.org/WAI/APA/task-forces/maturity-model/minutes)); -- [Email lists](/about/groups/task-forces/maturity-model/#email); -- IRC discussion on the [#maturity](irc://irc.w3.org/maturity) IRC channel, used largely for minute-taking; -- [Maturity Model Task force source repository](https://github.com/w3c/maturity-model); -- [Wiki](https://github.com/w3c/maturity-model/wiki); -- [Web-Based Surveys (WBS)](https://www.w3.org/2002/09/wbs/141517/); -- [Maturity Model source repository issue tracker](https://github.com/w3c/maturity-model/issues). +The MM Task Force supports the deliverables of the [Accessible Platform Architectures (APA) Working Group](/about/groups/apawg/). -These tools are used by participants of the Task Force. For ways non-participants can contribute, see [how to contribute to the Working Group and file comments](/about/groups/apawg/contribute/). +For details of the current work, see the [Maturity Model GitHub repository](https://github.com/w3c/maturity-model/). -### Teleconferences +## Contribute to the work -- **[Maturity Model Task Force](https://www.w3.org/2017/08/telecon-info_maturity-model)**: Wednesdays at 11:00 until 12:00 Boston time +The MM Task Force welcomes input from the global accessibility community on the Accessibility Maturity Model work. -### Meeting Minutes +### Contribute without joining the task force -[Minutes from previous meetings](https://www.w3.org/WAI/APA/task-forces/maturity-model/minutes) are available. +You can contribute to the work without being a member of the task force in the [Maturity Model GitHub repository](https://github.com/w3c/maturity-model/issues): +* If you’re aware of an issue with any of the published Accessibility Maturity Model resources, raise a new issue. +* Comment on or propose solutions for open Maturity Model issues. -### Mailing Lists +### Become a participant in the task force -The Maturity Model Task Force uses the public-maturity@w3.org mailing list ([mailing list archives](https://lists.w3.org/Archives/Public/public-maturity/)) for email discussion. Participants are automatically added to the mailing list when they become a participant of the Task Force. +Joining the MM Task Force enables you to participate fully in the development of the work and influence the deliverables. You and your organization will also be listed as contributors, where appropriate. -## Publications +Being a participant involves commitment to support the work of the task force in the following ways: -The Maturity Model Task Force published four documents as follow: +* Engage actively in the work using the task force’s communication channels. +* Keep up with weekly tasks and the progress of the work — for example, via the minutes of past meetings, mailing list discussions, and GitHub issue comments. +* Give your input promptly, when it’s needed. -- [W3C Accessibility Maturity Model](https://www.w3.org/TR/maturity-model/) is a guide for organizations to evaluate and improve their business processes to produce digital products that are accessible to people with disabilities. +To become a participant in the MM Task Force, you must first be a member of the APA Working Group — see [Instructions for joining the Accessible Platform Architectures Working Group](https://www.w3.org/groups/wg/apa/instructions/). -See also the [Maturity Model Task Force GitHub repository](https://github.com/w3c/maturity-model). +Once you are a member of the APA Working Group, email the [W3C staff contact for the Maturity Model Task Force](https://www.w3.org/groups/tf/maturity/participants/#staff) to let them know you’d like to join the task force. -## How to Comment, Contribute, and Participate +**Note:** As a participant in one of the APA Working Group’s task forces, you can choose to focus your time exclusively on the task force deliverables and you do not have to contribute to the working group’s other activities. -To join the Maturity Model Task Force, individuals must be participants of the [APA WG](/about/groups/apawg/). Participants are expected to [actively contribute](/about/groups/task-forces/maturity-model/work-statement/#participation) to the work of the Task Force. If you are interested in participating in the Maturity Model Task Force, please send e-mail to: [Janina Sajka, Sheri Byrne-Haber, David Fazio](mailto:janina@rednote.net,sbyrnehaber@vmware.com,dfazio@helixopp.com?subject=Maturity Model%20Task%20Force%20Enquiry) and include a little bit about what you’re interested in and how you think that you may be able to contribute to the Task Force. Then follow the [APA Working Group participation](/about/groups/apawg/participate/) procedures to join the Working Group, and once you have joined ask [Ruoxi Ran (Roy)](mailto:ran@w3.org) to add you to the task force. +## Task force members -To contribute without joining the task force, see the [APA Working Group contribute page](/about/groups/apawg/contribute/) for general instructions. To contribute to documents under development, see [how to contribute to the source repository directly](https://github.com/w3c/maturity-model/). +* [Chairs](https://www.w3.org/groups/tf/maturity/participants/#chairs) +* [Current participants](https://www.w3.org/groups/tf/maturity/participants/#participants) -[Current participants in the Maturity Model Task Force](https://www.w3.org/groups/tf/maturity/participants). +## Communications -## Administrative Information +* [Calendar of meetings](https://www.w3.org/groups/tf/maturity/calendar/) +* [Minutes from previous meetings](https://www.w3.org/WAI/APA/task-forces/maturity-model/minutes) +* [Mailing list archive](https://lists.w3.org/Archives/Public/public-maturity/) -The Maturity Model Task Force is a Task Force of the [Accessible Platform Architectures (APA) Working Group](/about/groups/apawg/). +## Publications -### Facilitator and Contacts +The MM Task Force develops and maintains the following resources for the APA Working Group: -- **Facilitators:** [Janina Sajka](mailto:janina@rednote.net), [Sheri Byrne-Haber](mailto:sbyrnehaber@vmware.com), [David Fazio](mailto:dfazio@helixopp.com) -- **Staff Contact:** [Ruoxi Ran](https://www.w3.org/People/roy/) +* [Accessibility Maturity Model — 2024 Group Draft Note](https://www.w3.org/TR/maturity-model/) +* [Accessibility Maturity Model — 2025 Editor’s Draft](https://www.w3.org/TR/maturity-model/) -### Work Statement +## Contact the chairs -The [Maturity Model Task Force Work Statement](/about/groups/task-forces/maturity-model/work-statement/) defines the initial objective, scope, approach, and participation of the Task Force. \ No newline at end of file +If you have a question for the MM Task Force, email the [chairs](https://www.w3.org/groups/tf/maturity/participants/#chairs) or the [W3C staff contact](https://www.w3.org/groups/tf/maturity/participants/#staff). \ No newline at end of file diff --git a/pages/about/groups/task-forces/maturity-model/work-statement.md b/pages/about/groups/task-forces/maturity-model/work-statement.md index d3aa2d38d02..4d02e15a281 100644 --- a/pages/about/groups/task-forces/maturity-model/work-statement.md +++ b/pages/about/groups/task-forces/maturity-model/work-statement.md @@ -1,8 +1,9 @@ --- -title: DRAFT Maturity Model Task Force (MMTF) Work Statement +title: Maturity Model Task Force Work Statement permalink: /about/groups/task-forces/maturity-model/work-statement/ ref: /about/groups/task-forces/maturity-model/work-statement/ lang: en +doc-note-type: draft github: label: wai-groups --- diff --git a/pages/about/groups/task-forces/pdf-aam.md b/pages/about/groups/task-forces/pdf-aam.md new file mode 100644 index 00000000000..29fe4c5e925 --- /dev/null +++ b/pages/about/groups/task-forces/pdf-aam.md @@ -0,0 +1,91 @@ +--- +title: PDF Accessibility APIs Mapping Task Force +title_html: PDF Accessibility APIs Mapping (PDF-AAM) Task Force +permalink: /about/groups/task-forces/pdf-aam/ +ref: /about/groups/task-forces/pdf-aam/ +lang: en +github: + label: wai-groups +--- + +{::nomarkdown} +{% include box.html type="start" title="Summary" class="" %} +{:/} + +Find out about the activities of the Portable Document Format Accessibility Application Programming Interfaces Mapping (PDF-AAM) Task Force and how you can contribute to its objectives. + +{::nomarkdown} +{% include box.html type="end" %} +{:/} + +{::options toc_levels="2..3" /} + +{::nomarkdown} +{% include_cached toc.html type="start" title="Page Contents" %} +{:/} + +- TOC is created automatically. +{:toc} + +{::nomarkdown} +{% include_cached toc.html type="end" %} +{:/} + +## Objectives + +The objective of the PDF-AAM Task Force is to specify how user agents should map accessibility semantics within the Portable Document Format specification. + +## Work Statement + +To learn about the focus, scope and deliverables of the task force, see the [PDF-AAM Task Force Work Statement](/about/groups/task-forces/pdf-aam/work-statement/). + +## Current Work + +The PDF-AAM Task Force supports the deliverables of the [Accessible Rich Internet Applications (ARIA) Working Group](/about/groups/ariawg/). + +For details of the current work, see the [PDF-AAM GitHub repository](https://github.com/w3c/pdf-aam). + +## Contribute to the work + +The PDF-AAM Task Force welcomes input from the global accessibility community on the PDF-AAM module. + +### Contribute without joining the task force + +You can contribute to the work without being a member of the task force in the [PDF-AAM GitHub repository](https://github.com/w3c/pdf-aam/issues): +* If you’re aware of an issue with the PDF-AAM module, raise a new issue. +* Comment on or propose solutions for open PDF-AAM issues. + +### Become a participant in the task force + +Joining the PDF-AAM Task Force enables you to participate fully in the development of the work and influence the deliverables. You and your organization will also be listed as contributors, where appropriate. + +Being a participant involves commitment to support the work of the task force in the following ways: + +* Engage actively in the work using the task force’s communication channels. +* Keep up with weekly tasks and the progress of the work — for example, via the minutes of past meetings, mailing list discussions, and GitHub issue comments. +* Give your input promptly, when it’s needed. + +To become a participant in the PDF-AAM Task Force, you must first be a member of the ARIA Working Group. See [Instructions for joining the Accessible Rich Internet Applications Working Group](https://www.w3.org/groups/wg/aria/instructions/). + +Once you are a member of the ARIA Working Group, email the [W3C Staff Contact for the PDF-AAM Task Force](https://www.w3.org/groups/tf/pdf-aam/participants/#staff) to let them know you’d like to join the task force. + +**Note:** As a participant in one of the ARIA Working Group’s task forces, you can choose to focus your time exclusively on the task force deliverables and you do not have to contribute to the working group’s other activities. + +## Task force members + +* [Chairs](https://www.w3.org/groups/tf/pdf-aam/participants/#chairs) +* [Current participants](https://www.w3.org/groups/tf/pdf-aam/participants/#participants) + +## Communications + +* [Calendar of meetings](https://www.w3.org/groups/tf/pdf-aam/calendar/) +* [Minutes from previous meetings](https://www.w3.org/WAI/ARIA/task-forces/pdf-aam/minutes) +* [Mailing list archive](http://lists.w3.org/Archives/Public/public-pdf-aam/) + +## Publications + +The PDF-AAM Task Force will develop and maintain the [PDF Accessibility API Mappings — 2024 Editor’s Draft](https://w3c.github.io/pdf-aam/) for the ARIA Working Group. + +## Contact the chairs + +If you have a question for the PDF-AAM Task Force, email the [chairs](https://www.w3.org/groups/tf/pdf-aam/participants/#chairs) or the [W3C staff contact](https://www.w3.org/groups/tf/pdf-aam/participants/#staff). \ No newline at end of file diff --git a/pages/about/groups/task-forces/pdf-aam/work-statement.md b/pages/about/groups/task-forces/pdf-aam/work-statement.md new file mode 100644 index 00000000000..26e85db1f0a --- /dev/null +++ b/pages/about/groups/task-forces/pdf-aam/work-statement.md @@ -0,0 +1,82 @@ +--- +title: PDF Accessibility APIs Mapping Task Force Work Statement +title_html: Portable Document Format Accessibility APIs Mapping (PDF-AAM) Task Force Work Statement +permalink: /about/groups/task-forces/pdf-aam/work-statement/ +ref: /about/groups/task-forces/pdf-aam/work-statement/ +lang: en +github: + label: wai-groups +--- + +{::nomarkdown} +{% include box.html type="start" title="Summary" class="" %} +{:/} + +The Portable Document Format Accessibility APIs Mapping (PDF-AAM) Task Force is a task force of the [Accessible Rich Internet Applications (ARIA) Working Group](/about/groups/ariawg/). It assists this Working Group to map Accessibility APIs (Application Programming Interfaces) to PDFs and keep the development of [PDF-AAM](https://w3c.github.io/pdf-aam/) in sync with WAI-ARIA.' + +{::nomarkdown} +{% include box.html type="end" %} +{:/} + +{::options toc_levels="2..3" /} + +{::nomarkdown} +{% include_cached toc.html type="start" title="Page Contents" %} +{:/} + +- TOC is created automatically. +{:toc} + +{::nomarkdown} +{% include_cached toc.html type="end" %} +{:/} + +## Status + +The PDF-AAM Task Force Work Statement was [approved on 12 November 2024](https://github.com/w3c/aria/issues/2070) and is now active. The [PDF-AAM Task Force home page](/about/groups/task-forces/pdf-aam/) contains information about the operation and resources of the group. + +## Objective + +The mission of the PDF-AAM Task Force is to specify how user agents should map accessibility semantics within the Portable Document Format specification. This Task Force provides a focused forum for this work while the Working Group continues its work on ARIA development. + +## Scope of Work + +The PDF-AAM Task Force will produce a W3C Technical Report on [PDF Accessibility API Mappings](https://w3c.github.io/pdf-aam/), specifying accessibility API mappings for PDF, based on the [Core-AAM](https://www.w3.org/TR/core-aam-1.2/) and [HTML-AAM](https://www.w3.org/TR/html-aam/) specifications. + +## Approach + +The [PDF/UA Processor Liaison Working Group (LWG)](https://pdfa.org/community/pdf-ua-processor-lwg/) is a meeting place for the PDF and assistive technology industries to help drive the formalization of common understandings on processing PDF files that conform to [ISO 14289 (PDF/UA)](https://www.iso.org/standard/64599.html), the standard for accessible PDF documents. The PDF-AAM will incorporate and extend existing work developed by the PDF/UA Processor LWG into a W3C Technical Report, which is expected to reach the Recommendation Track according to the [W3C Process](https://www.w3.org/policies/process/). + +## Communication + +PDF-AAM Task Force communications and discussions are visible to the public. The [PDF-AAM Task Force home page](/about/groups/task-forces/pdf-aam/) 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) methods of communication; +- use the procedures of the [ARIA Working Group Decision Policy](/about/groups/ariawg/decision-policy/) to make decisions; +- provide updates and feedback to ARIA Working Group teleconferences, as appropriate — these liaisons are primarily the responsibility of the PDF-AAM Task Force facilitators; +- maintain information resulting from its activities (deliverables, participants, face-to-face meetings, teleconferences, etc.) on the [PDF-AAM Task Force home page](/about/groups/task-forces/practices/). + +## Participation + +Any participant in the ARIA Working Group may participate in the PDF-AAM Task Force. Participants should expect to dedicate 2 to 4 hours per week for PDF-AAM Task Force work, which is considered part of the overall work commitment to the ARIA Working Group. This work includes: + +- remaining current on the PDF-AAM Task Force mailing list and responding to postings in a timely manner; +- providing feedback to editors of specifications via email or by filing bugs; +- participating in PDF-AAM Task Force teleconferences, or sending regrets to the PDF-AAM Task Force mailing list. + +If you are interested in becoming a participant of the PDF-AAM Task Force or have any questions regarding its work, contact the Task Force facilitators. + +[Current PDF-AAM Task Force participants](https://www.w3.org/groups/tf/pdf-aam/participants/) + +## Facilitation + +The PDF-AAM Task Force facilitators set the meeting agendas, lead the meetings, determine consensus, and are the primary liaison between the Task Force and the ARIA Working Group. + +The W3C Staff Contact for the ARIA Working Group and its task forces oversees attention to W3C Process with respect to the chartered requirements of the ARIA Working Group. + +- **Facilitators:** Duff Johnson, Valerie Young +- **Staff Contact:** [Daniel Montalvo](https://www.w3.org/staff/#dmontalvo) + +## Patent Policy + +This Task Force is part of the [ARIA Working Group Charter](https://www.w3.org/WAI/ARIA/charter), which operates under the [W3C Patent Policy](https://www.w3.org/Consortium/Patent-Policy-20200915/) (15 September 2020 Version). W3C maintains a public list of any patent disclosures made in connection with the deliverables of the [ARIA Working Group](https://www.w3.org/2004/01/pp-impl/83726/status). diff --git a/pages/about/groups/task-forces/practices.md b/pages/about/groups/task-forces/practices.md index fdb6685501c..94c5a7fc54b 100644 --- a/pages/about/groups/task-forces/practices.md +++ b/pages/about/groups/task-forces/practices.md @@ -1,5 +1,5 @@ --- -title: ARIA Authoring Practices (APG) Task Force of the ARIA WG +title: ARIA Authoring Practices Task Force permalink: /about/groups/task-forces/practices/ ref: /about/groups/task-forces/practices/ lang: en @@ -11,9 +11,7 @@ github: {% include box.html type="start" title="Summary" class="" %} {:/} -The ARIA Authoring Practices (APG) Task Force is a task force of the [Accessible Rich Internet Applications Working Group](/about/groups/ariawg/). - -Some information on this page is also shown on, and may be more current in, the [ARIA Authoring Practices Task Force page](https://www.w3.org/groups/tf/aria-practices/). +Find out about the activities of the ARIA Authoring Practices Task Force (known as the APG Task Force) and how you can contribute to its objectives. {::nomarkdown} {% include box.html type="end" %} @@ -32,64 +30,64 @@ Some information on this page is also shown on, and may be more current in, the {% include_cached toc.html type="end" %} {:/} -## Announcements - -No announcements at the moment. +## Objectives -## Meetings and Communication +The objective of the APG Task Force is to develop the WAI-ARIA Authoring Practices Guide, which describes considerations that might not be evident to authors from the WAI-ARIA specification alone, and recommends approaches to make widgets, navigation, and behaviors accessible using WAI-ARIA roles, states, and properties. -The APG Task Force conducts its work using a variety of synchronous and asynchronous tools. +## Work statement -- Teleconferences of the Working Group and its task forces (also see [meeting minutes](https://www.w3.org/WAI/ARIA/task-forces/practices/minutes)); -- Face to face meetings; -- [Email lists](#mailing-lists); -- IRC discussion on the [#aria-apg](irc://irc.w3.org/aria-apg) IRC channel, used largely for minute-taking; -- [aria-practices source repository](https://github.com/w3c/aria-practices/); -- [Wiki](https://github.com/w3c/aria-practices/wiki); -- [Web-Based Surveys (WBS)](https://www.w3.org/2002/09/wbs/102172/); -- [aria-practices source repository issue tracker](https://github.com/w3c/aria-practices/issues). +To learn about the focus, scope and deliverables of the task force, see the [APG Task Force Work Statement](/about/groups/task-forces/practices/work-statement/). -These tools are used by participants of the Task Force. For ways non-participants can contribute, see [how to contribute to the Working Group and file comments](/about/groups/ariawg/contribute/). +## Current work -### Teleconferences +The APG Task Force supports the deliverables of the [Accessible Rich Internet Applications (ARIA) Working Group](/about/groups/ariawg/). -- **[ARIA Authoring Practices](https://www.w3.org/groups/tf/aria-practices/calendar/)**: Tuesdays at 14:00 until 15:00 Boston time +For details of the current work, see the following: +* [APG Task Force wiki](https://github.com/w3c/aria-practices/wiki) +* [APG milestones](https://github.com/w3c/aria-practices/milestones) +* [APG projects](https://github.com/w3c/aria-practices/projects) -### Meeting Minutes +## Contribute to the work -[Minutes from previous meetings](https://www.w3.org/WAI/ARIA/task-forces/practices/minutes) are available. +The APG Task Force welcomes input from the global accessibility community on the ARIA Authoring Practices Guide. -### Mailing Lists +### Contribute without joining the task force -The APG Task Force uses the public-aria-practices@w3.org mailing list ([mailing list archives](http://lists.w3.org/Archives/Public/public-aria-practices/)) for email discussion. Participants are automatically added to the mailing list when they become a participant of the Task Force. +You can contribute to the work without being a member of the task force in the [APG GitHub repository](https://github.com/w3c/aria-practices/issues): +* If you’re aware of an issue with any of the published APG resources, raise a new issue. +* Comment on or propose solutions for open APG issues. -Discussions of the task force prior to September 2017 are [archived on the public-aria mailing list](http://lists.w3.org/Archives/Public/public-aria/). +### Become a participant in the task force -## Current Work +Joining the APG Task Force enables you to participate fully in the development of the work and influence the deliverables. You and your organization will also be listed as contributors, where appropriate. -The scope wiki page describes the task force goals. All work items are defined in the [issues list](https://github.com/w3c/aria-practices/issues), each of which is scheduled into one of the [milestones](https://github.com/w3c/aria-practices/milestones). Issues are topically organized into [projects list](https://github.com/w3c/aria-practices/projects). +Being a participant involves commitment to support the work of the task force in the following ways: -## Publications +* Engage actively in the work using the task force’s communication channels. +* Keep up with weekly tasks and the progress of the work — for example, via the minutes of past meetings, mailing list discussions, and GitHub issue comments. +* Give your input promptly, when it’s needed. -The APG Task Force is primarily developing [WAI-ARIA Authoring Practices 1.1](https://www.w3.org/TR/wai-aria-practices-1.1/) ([WAI-ARIA Authoring Practices 1.1 Editors' Draft](https://w3c.github.io/aria-practices/)). See also the [APG Task Force GitHub repository](https://github.com/w3c/aria-practices/). +To become a participant in the APG Task Force, you must first be a member of the ARIA Working Group. See [Instructions for joining the Accessible Rich Internet Applications Working Group](https://www.w3.org/groups/wg/aria/instructions/). -## How to Comment, Contribute, and Participate +Once you are a member of the ARIA Working Group, email the [W3C Staff Contact for the APG Task Force](https://www.w3.org/groups/tf/aria-practices/participants/#staff) to let them know you’d like to join the task force. -To join the APG Task Force, individuals must be participants of the [ARIA WG](/about/groups/apawg/). Participants are expected to [actively contribute](/about/groups/task-forces/practices/work-statement/#participation) to the work of the Task Force. If you are interested in participating in the APG Task Force, please send e-mail to: [Matt King, Jemma Ku](mailto:a11ythinker@gmail.com,jku@illinois.edu?subject=APG%20Task%20Force%20Enquiry) and include a little bit about what you’re interested in and how you think that you may be able to contribute to the Task Force. Then follow the [ARIA Working Group participation](/about/groups/ariawg/participate/) procedures to join the Working Group, and once you have joined ask [Daniel Montalvo](mailto:dmontalvo@w3.org) to add you to the task force. +**Note:** As a participant in one of the ARIA Working Group’s task forces, you can choose to focus your time exclusively on the task force deliverables and you do not have to contribute to the working group’s other activities. -To contribute without joining the task force, see the [ARIA Working Group contribute page](/about/groups/ariawg/contribute/) for general instructions. To contribute to documents under development, see [how to contribute to the source repository directly](https://github.com/w3c/aria-practices/). +## Task force members -[Current participants in the APG Task Force](https://www.w3.org/2000/09/dbwg/details?group=102172&public=1). +* [Chairs](https://www.w3.org/groups/tf/aria-practices/participants/#chairs) +* [Current participants](https://www.w3.org/groups/tf/aria-practices/participants/#participants) -## Administrative Information +## Communications -The APG Task Force is a Task Force of the [Accessible Rich Internet (ARIA) Working Group](/about/groups/ariawg/). It assists this Working Group to develop [WAI-ARIA Authoring Practices](http://w3c.github.io/aria-practices/) and keep it in sync with WAI-ARIA. +* [Calendar of meetings](https://www.w3.org/groups/tf/aria-practices/calendar/) +* [Minutes from previous meetings](https://www.w3.org/WAI/ARIA/task-forces/practices/minutes) +* [Mailing list archive](http://lists.w3.org/Archives/Public/public-aria-practices/) -### Facilitator and Contacts +## Publications -- **Facilitators:** Matt King, JaEun (Jemma) Ku -- **Staff Contact:** [Daniel Montalvo](https://www.w3.org/People#dmontalvo/) +The APG Task Force develops and maintains the [WAI-ARIA Authoring Practices Guide](https://www.w3.org/WAI/ARIA/apg/) for the ARIA Working Group. -### Work Statement +## Contact the chairs -The [APG Task Force Work Statement](/about/groups/task-forces/practices/work-statement/) defines the initial objective, scope, approach, and participation of the Task Force. \ No newline at end of file +If you have a question for the APG Task Force, email the [chairs](https://www.w3.org/groups/tf/aria-practices/participants/#chairs) or the [W3C staff contact](https://www.w3.org/groups/tf/aria-practices/participants/#staff). \ No newline at end of file diff --git a/pages/about/groups/task-forces/practices/work-statement.md b/pages/about/groups/task-forces/practices/work-statement.md index c8367bd6df6..28efdfa1486 100644 --- a/pages/about/groups/task-forces/practices/work-statement.md +++ b/pages/about/groups/task-forces/practices/work-statement.md @@ -67,7 +67,7 @@ Participants may also join APG Task Force sub-groups. Sub-groups take on specifi If you are interested in becoming a participant of the APG Task Force or have any questions regarding its work, contact the task force facilitators. -[@@Current APG Task Force participants](https://www.w3.org/2000/09/dbwg/details?group=102172&public=1) +[Current APG Task Force participants](https://www.w3.org/groups/tf/aria-practices/participants/) ## Facilitation @@ -78,4 +78,4 @@ Staff contacts from the ARIA and APA Working Groups oversee attention to W3C Pro ## Patent Policy -This Task Force is part of the [ARIA Working Group Charter](https://www.w3.org/WAI/ARIA/charter), which operates under the [W3C Patent Policy](https://www.w3.org/Consortium/Patent-Policy-20040205/) (5 February 2004 Version). W3C maintains a public list of any patent disclosures made in connection with the deliverables of the [ARIA Working Group](https://www.w3.org/2004/01/pp-impl/83726/status). \ No newline at end of file +This Task Force is part of the [ARIA Working Group Charter](https://www.w3.org/WAI/ARIA/charter), which operates under the [W3C Patent Policy](https://www.w3.org/policies/patent-policy/20200915/) (15 September 2020 Version). W3C maintains a public list of any patent disclosures made in connection with the deliverables of the [ARIA Working Group](https://www.w3.org/2004/01/pp-impl/83726/status). \ No newline at end of file diff --git a/pages/about/groups/task-forces/pronunciation.md b/pages/about/groups/task-forces/pronunciation.md deleted file mode 100644 index 9a8300b4f2e..00000000000 --- a/pages/about/groups/task-forces/pronunciation.md +++ /dev/null @@ -1,116 +0,0 @@ ---- -title: Spoken Presentation Task Force of the APA WG -permalink: /about/groups/task-forces/pronunciation/ -ref: /about/groups/task-forces/pronunciation/ -lang: en -github: - label: wai-groups ---- - -{::nomarkdown} -{% include box.html type="start" title="Summary" class="" %} -{:/} - -The Spoken Presentation Task Force is a task force of the [Accessible Platform Architectures Working Group](/about/groups/apawg/). - -Some information on this page is also shown on, and may be more current in, the [Spoken Presentation Task Force page](https://www.w3.org/groups/tf/pronunciation-tf/). - -{::nomarkdown} -{% include box.html type="end" %} -{:/} - -{::options toc_levels="2..3" /} - -{::nomarkdown} -{% include_cached toc.html type="start" title="Page Contents" %} -{:/} - -- TOC is created automatically. -{:toc} - -{::nomarkdown} -{% include_cached toc.html type="end" %} -{:/} - -## Announcements - -No announcements at the moment. - -## Spoken Presentation Overview - -[Spoken Presentation Overview](https://www.w3.org/WAI/pronunciation/) provides an overview of the overall pronunciation technique in W3C. - -## Spoken Presentation Video - -There is also a short [pronunciation technical video](https://ln.sync.com/dl/10e1a9c60/92faztk9-he4wbve6-twt5jp3h-zuh6brfd) available, it shows the demo of pronunciation technical and approaches for controlling pronunciation in spans of web content where uniform markup can make the difference. - -## Meetings and Communication - -The APA WG conducts its work using a variety of synchronous and asynchronous tools: - -- [Teleconferences of the Spoken Presentation Task Force](#teleconferences); -- Face to face meetings (The Task Force will plan a face-to-face meeting at a later stage.); -- [Email lists](#mailing-lists); -- IRC discussion on the [#pronunciation](irc://irc.w3.org/pronunciation) IRCchannel, used largely for minute-taking; -- [Spoken Presentation source repository](https://github.com/w3c/pronunciation/); -- [Wiki](https://github.com/w3c/pronunciation/wiki/); -- [Web-Based Surveys (WBS)](https://www.w3.org/2002/09/wbs/110437/); -- [Spoken Presentation Issue Tracker](https://www.w3.org/WAI/APA/task-forces/pronunciation/track/); -- [Spoken Presentation source repository issue tracker](https://github.com/w3c/pronunciation/issues); -- [Current participants in the Spoken Presentation Task Force](https://www.w3.org/2000/09/dbwg/details?group=110437&public=1). - -These tools are used by participants of the Task Force. For ways non-participants can contribute, see [how to contribute to the Working Group and file comments](/about/groups/apawg/contribute/). - -### Teleconferences - -[Spoken Presentation Task Force meetings](https://www.w3.org/2017/08/telecon-info_pronunciation): Mondays at 11:00 until 12:00 Boston time. - -### Meeting Minutes - -[Minutes from previous meetings](https://www.w3.org/WAI/APA/task-forces/pronunciation/minutes) are available. - -### Mailing Lists - -The Spoken Presentation Task Force uses the public-pronunciation@w3.org mailing list ([mailing list archives](https://lists.w3.org/Archives/Public/public-pronunciation/)) for email discussion. Participants are automatically added to the mailing list when they become a participant of the Task Force. - -## Current Work - -[See the wiki for current planning and draft documents](https://github.com/w3c/pronunciation/blob/master/README.md). - -## Publications - -- **[Explainer: Improving Spoken Presentation on the Web](https://www.w3.org/TR/pronunciation-explainer/)** provides an overview of the work. It: - - Briefly introduces the context for W3C work on pronunciation - - Describes the advantages and disadvantages of two approaches - - Poses questions for additional input -- **[Pronunciation User Scenarios](https://www.w3.org/TR/pronunciation-user-scenarios/)** provides examples of: - - End-users, including screen reader users - - Content providers, including educators - - Software developers, including content managements systems -- **[Pronunciation Gap Analysis and Use Cases](https://www.w3.org/TR/pronunciation-gap-analysis-and-use-cases/)** provides details on the analysis. It: - - Provides more detailed context - - Describes required features for pronunciation and spoken presentation - - Describes specific implementation approaches for introducing presentation authoring markup into HTML5 (called “use cases”) - - Provides a gap analysis - - Describes how the required features may be met by existing approaches - -## How to Comment, Contribute, and Participate - -To join the Spoken Presentation Task Force, individuals must be participants of the APA WG. Participants are expected to [actively contribute](/about/groups/task-forces/pronunciation/work-statement/#participation) to the work of the Task Force. If you are interested in participating in the Spoken Presentation Task Force, please send e-mail to: [Janina Sajka](mailto:janina@rednote.net), [Irfan Ali](mailto:iali@ets.org) and [Paul Grenier](mailto:pgrenier@gmail.com) and include a little bit about what you’re interested in and how you think that you may be able to contribute to the Task Force. Then follow the [APA Working Group participation](/about/groups/apawg/participate/) procedures to join the Working Group, and once you have joined ask [Ruoxi(Roy) Ran](mailto:ran@w3.org) to add you to the task force. - -To contribute without joining the task force, see the [APA Working Group contribute page](/about/groups/apawg/contribute/) for general instructions. To contribute to documents under development, see [how to contribute to the source repository directly](https://github.com/w3c/pronunciation/). - -[Current participants in the Spoken Presentation Task Force](https://www.w3.org/2000/09/dbwg/details?group=110437&public=1). - -## Administrative Information - -The Spoken Presentation Task Force is a Task Force of the [Accessible Platform Architectures (APA) Working Group](/about/groups/apawg/). It assists these Working Groups to produce techniques, understanding, and guidance documents, as well as updates to existing related W3C material that addresses the cognitive space. - -### Facilitator and Contacts - -- **Task Force facilitator:** [Irfan Ali](mailto:iali@ets.org), [Paul Grenier](mailto:pgrenier@gmail.com) -- **Staff Contact: [Ruoxi(Roy) Ran](https://www.w3.org/People/roy/)** - -### Work Statement - -The [Spoken Presentation Accessibility Task Force Work Statement](/about/groups/task-forces/pronunciation/work-statement/) defines the initial objective, scope, approach, and participation of the Task Force. \ No newline at end of file diff --git a/pages/about/groups/task-forces/research-questions.md b/pages/about/groups/task-forces/research-questions.md index 50d561ee683..779f6f5ffb7 100644 --- a/pages/about/groups/task-forces/research-questions.md +++ b/pages/about/groups/task-forces/research-questions.md @@ -1,5 +1,5 @@ --- -title: Research Questions Task Force (RQTF) of the APA WG +title: Research Questions Task Force permalink: /about/groups/task-forces/research-questions/ ref: /about/groups/task-forces/research-questions/ lang: en @@ -11,9 +11,7 @@ github: {% include box.html type="start" title="Summary" class="" %} {:/} -The Research Questions Task Force (RQTF) is a task force of the [Accessible Platform Architectures Working Group](/about/groups/apawg/). - -Some information on this page is also shown on, and may be more current in, the [Research Questions Task Force page](https://www.w3.org/groups/tf/rqtf/). +Find out about the activities of the Research Questions (RQ) Task Force and how you can contribute to its objectives. {::nomarkdown} {% include box.html type="end" %} @@ -31,64 +29,60 @@ Some information on this page is also shown on, and may be more current in, the {::nomarkdown} {% include_cached toc.html type="end" %} {:/} -## Announcements -No announcements at the moment. +## Objectives -## Meetings and Communication +The objectives of the RQ Task Force are to identify accessibility barriers and knowledge gaps in emerging and future web technologies; publish the research findings on those barriers and gaps; and support W3C’s horizontal reviews of web technologies as they mature and are normatively specified. -The APA WG conducts its work using a variety of synchronous and asynchronous tools. The [communication](/about/groups/apawg/communication/) page provides details about: +## Work statement -- Teleconferences of the Working Group and its task forces (also see [meeting minutes](https://www.w3.org/WAI/APA/task-forces/research-questions/minutes)); -- [Email lists](#email); -- IRC discussion on the [#rqtf](irc://irc.w3.org/rqtf) IRCchannel, used largely for minute-taking; -- [RQTF source repository](https://github.com/w3c/rqtf/); -- [Wiki](https://www.w3.org/WAI/APA/task-forces/research-questions/wiki/); -- [Web-Based Surveys (WBS)](https://www.w3.org/2002/09/wbs/91497/); -- [RQTF source repository issue tracker](https://github.com/w3c/rqtf/issues). +To learn about the focus, scope and deliverables of the task force, see the [RQ Task Force Work Statement](/about/groups/task-forces/research-questions/work-statement/). -These tools are used by participants of the Task Force. For ways non-participants can contribute, see [how to contribute to the Working Group and file comments](/about/groups/apawg/contribute/). +## Current work -### Teleconferences +The RQ Task Force supports the deliverables of the [Accessible Platform Architectures (APA) Working Group](/about/groups/apawg/). -- **[Research Questions Task Force](https://www.w3.org/2017/08/telecon-info_rqtf)**: Wednesdays at 9:00 until 10:00 Boston time -- **[RQTF Plan](https://www.w3.org/2017/08/telecon-info_rqtf-plan)**: Mondays at 9:00 until 10:00 Boston time +For details of the current work, see the [RQ Task Force wiki](https://www.w3.org/WAI/APA/task-forces/research-questions/wiki/Main_Page). -### Meeting Minutes +## Contribute to the work -[Minutes from previous meetings](https://www.w3.org/WAI/APA/task-forces/research-questions/minutes) are available. +The RQ Task Force welcomes input from the global accessibility community on the emerging and future web technologies research work. -### Mailing Lists +### Contribute without joining the task force -The RQTF uses the public-rqtf@w3.org mailing list ([mailing list archives](https://lists.w3.org/Archives/Public/public-rqtf/)) for email discussion. Participants are automatically added to the mailing list when they become a participant of the Task Force. +You can contribute to the work without being a member of the task force by commenting on or proposing solutions for open issues in the [Research Questions GitHub repository](https://github.com/w3c/rqtf/issues). -## Current Work +### Become a participant in the task force -Current Task Force work is being maintained in the [Work Plan](https://www.w3.org/WAI/APA/task-forces/research-questions/wiki/Work_Plan). +Joining the RQ Task Force enables you to participate fully in the development of the work and influence the deliverables. You and your organization will also be listed as contributors, where appropriate. -[See the wiki for current planning and draft documents](https://www.w3.org/WAI/APA/task-forces/research-questions/wiki/). +Being a participant involves commitment to support the work of the task force in the following ways: -## Publications +* Engage actively in the work using the task force’s communication channels. +* Keep up with weekly tasks and the progress of the work — for example, via the minutes of past meetings, mailing list discussions, and GitHub issue comments. +* Give your input promptly, when it’s needed. -When the Task Force develops publications, they will be listed here. See also the [RQTF GitHub repository](https://github.com/w3c/rqtf). +To become a participant in the RQ Task Force, you must first be a member of the APA Working Group — see [Instructions for joining the Accessible Platform Architectures Working Group](https://www.w3.org/groups/wg/apa/instructions/). -## How to Comment, Contribute, and Participate +Once you are a member of the APA Working Group, email the [W3C staff contact for the Research Questions Task Force](https://www.w3.org/groups/tf/rqtf/participants/#staff) to let them know you’d like to join the task force. -To join the RQTF, individuals must be participants of the APA WG. Participants are expected to [actively contribute](/about/groups/task-forces/research-questions/work-statement/#participation) to the work of the Task Force. If you are interested in participating in the RQTF, please send e-mail to: [Janina Sajka, Jason White](mailto:janina@rednote.net,jjwhite@ets.org?subject=Research%20Questions%20Task%20Force%20Enquiry) and include a little bit about what you’re interested in and how you think that you may be able to contribute to the Task Force. Then follow the [APA Working Group participation](/about/groups/apawg/participate/) procedures to join the Working Group, and once you have joined ask [Ruoxi(Roy) Ran](mailto:ran@w3.org) to add you to the task force. +**Note:** As a participant in one of the APA Working Group’s task forces, you can choose to focus your time exclusively on the task force deliverables and you do not have to contribute to the working group’s other activities. -To contribute without joining the task force, see the [APA Working Group contribute page](/about/groups/apawg/contribute/) for general instructions. To contribute to documents under development, see [how to contribute to the source repository directly](https://github.com/w3c/rqtf/). +## Task force members -[Current participants in the RQTF](https://www.w3.org/groups/tf/rqtf/participants). +* [Chairs](https://www.w3.org/groups/tf/rqtf/participants/#chairs) +* [Current participants](https://www.w3.org/groups/tf/rqtf/participants/#participants) -## Administrative Information +## Communications -The Research Questions Accessibility Task Force (RQTF) is a Task Force of the [Accessible Platform Architectures (APA) Working Group](/about/groups/apawg/). It assists these Working Groups to produce techniques, understanding, and guidance documents, as well as updates to existing related W3C material that addresses the cognitive space. +* [Calendar of meetings](https://www.w3.org/groups/tf/rqtf/calendar/) +* [Minutes from previous meetings](https://www.w3.org/WAI/APA/task-forces/research-questions/minutes) +* [Mailing list archive](https://lists.w3.org/Archives/Public/public-rqtf/) -### Facilitator and Contacts +## Publications -- **Task Force facilitator:** [Jason White](mailto:jason@jasonjgw.net), [Scott Hollier](mailto:scott.hollier@accessibility.org.au) -- **Staff Contact:** [Ruoxi Ran](mailto:ran@w3.org) +When the RQ Task Force develops publications, they will be listed here. -### Work Statement +## Contact the chairs -The [Research Questions Accessibility Task Force Work Statement](/about/groups/task-forces/research-questions/work-statement/) defines the initial objective, scope, approach, and participation of the Task Force. \ No newline at end of file +If you have a question for the RQ Task Force, email the [chairs](https://www.w3.org/groups/tf/rqtf/participants/#chairs) or the [W3C staff contact](https://www.w3.org/groups/tf/rqtf/participants/#staff). \ No newline at end of file diff --git a/pages/about/groups/task-forces/research-questions/work-statement.md b/pages/about/groups/task-forces/research-questions/work-statement.md index d8b2c143227..b3fdac6220e 100644 --- a/pages/about/groups/task-forces/research-questions/work-statement.md +++ b/pages/about/groups/task-forces/research-questions/work-statement.md @@ -1,5 +1,5 @@ --- -title: Research Questions Task Force (RQTF) Work Statement +title: Research Questions Task Force Work Statement permalink: /about/groups/task-forces/research-questions/work-statement/ ref: /about/groups/task-forces/research-questions/work-statement/ lang: en @@ -11,7 +11,7 @@ github: {% include box.html type="start" title="Summary" class="" %} {:/} -The Research Questions Task Force is a task force of the [Accessible Platform Architectures Working Group (APA Working Group)](/about/groups/apawg/). It assists this Working Group with the work identified below. +The Research Questions (RQ) Task Force is a task force of the [Accessible Platform Architectures Working Group (APA Working Group)](/about/groups/apawg/). It assists this Working Group with the work identified below. {::nomarkdown} {% include box.html type="end" %} @@ -74,7 +74,7 @@ Participants may also join Research Questions Task Force sub-groups. Sub-groups If you are interested in becoming a participant of the Research Questions Task Force or have any questions regarding its work, contact the task force facilitators. -[Current Research Questions Task Force participants](https://www.w3.org/2000/09/dbwg/details?group=91497&public=1) +[Current Research Questions Task Force participants](https://www.w3.org/groups/tf/rqtf/participants/) ## Facilitation @@ -85,4 +85,4 @@ Staff contacts from the APA Working Group oversee attention to W3C Process with ## Patent Policy -This Task Force is part of the [APA Working Group Charter](https://www.w3.org/WAI/APA/charter), which operates under the [W3C Patent Policy](https://www.w3.org/Consortium/Patent-Policy-20040205/) (5 February 2004 Version). W3C maintains a public list of any patent disclosures made in connection with the deliverables of the [APA Working Group](https://www.w3.org/2004/01/pp-impl/83907/status). \ No newline at end of file +This Task Force is part of the [APA Working Group Charter](https://www.w3.org/WAI/APA/charter), which operates under the [W3C Patent Policy](https://www.w3.org/policies/patent-policy/20200915/) (15 September 2020 Version). W3C maintains a public list of any patent disclosures made in connection with the deliverables of the [APA Working Group](https://www.w3.org/2004/01/pp-impl/83907/status). \ No newline at end of file diff --git a/pages/about/groups/task-forces/spoken-presentation.md b/pages/about/groups/task-forces/spoken-presentation.md new file mode 100644 index 00000000000..c9dd3aac509 --- /dev/null +++ b/pages/about/groups/task-forces/spoken-presentation.md @@ -0,0 +1,115 @@ +--- +title: Spoken Presentation Task Force +permalink: /about/groups/task-forces/spoken-presentation/ +ref: /about/groups/task-forces/spoken-presentation/ +redirect_from: + - /about/groups/task-forces/pronunciation/ +lang: en +github: + label: wai-groups +--- + +{::nomarkdown} +{% include box.html type="start" title="Summary" class="" %} +{:/} + +Find out about the activities of the Spoken Presentation (previously known as Pronunciation) Task Force and how you can contribute to its objectives. + +{::nomarkdown} +{% include box.html type="end" %} +{:/} + +{::options toc_levels="2..3" /} + +{::nomarkdown} +{% include_cached toc.html type="start" title="Page Contents" %} +{:/} + +- TOC is created automatically. +{:toc} + +{::nomarkdown} +{% include_cached toc.html type="end" %} +{:/} + +## Objectives + +The objective of the Spoken Presentation Task Force is to develop normative specifications and best practice guidance on providing proper pronunciation for HTML content across operating systems, so that words are pronounced correctly when using text-to-speech (TTS) synthesis and users’ preferred assistive technologies. + +## Work statement + +To learn about the focus, scope and deliverables of the task force, see the [Spoken Presentation Task Force Work Statement](/about/groups/task-forces/spoken-presentation/work-statement/). + +## Overview of the spoken presentation work + +* [Pronunciation overview](https://www.w3.org/WAI/pronunciation/) — an overview of W3C’s pronunciation technique +* [Pronunciation video {% include_cached external.html %}](https://ln.sync.com/dl/10e1a9c60/92faztk9-he4wbve6-twt5jp3h-zuh6brfd) — a technical demonstration of approaches for controlling pronunciation in spans of web content where uniform markup can make a difference + +## Current work + +The Spoken Presentation Task Force supports the deliverables of the [Accessible Platform Architectures (APA) Working Group](/about/groups/apawg/). + +For details of the current work, see: + +* [Spoken Presentation Task Force wiki](https://github.com/w3c/pronunciation/wiki/) +* [Spoken Presentation Task Force current work](https://github.com/w3c/pronunciation/blob/master/README.md) + +## Contribute to the work + +The Spoken Presentation Task Force welcomes input from the global accessibility community on the pronunciation work. + +### Contribute without joining the task force + +You can contribute to the work without being a member of the task force in the [Pronunciation GitHub repository](https://github.com/w3c/pronunciation/issues): +* If you’re aware of an issue with any of the published Spoken Presentation resources, raise a new issue. +* Comment on or propose solutions for open pronunciation issues. + +### Become a participant in the task force + +Joining the Spoken Presentation Task Force enables you to participate fully in the development of the work and influence the deliverables. You and your organization will also be listed as contributors, where appropriate. + +Being a participant involves commitment to support the work of the task force in the following ways: + +* Engage actively in the work using the task force’s communication channels. +* Keep up with weekly tasks and the progress of the work — for example, via the minutes of past meetings, mailing list discussions, and GitHub issue comments. +* Give your input promptly, when it’s needed. + +To become a participant in the Spoken Presentation Task Force, you must first be a member of the APA Working Group — see [Instructions for joining the Accessible Platform Architectures Working Group](https://www.w3.org/groups/wg/apa/instructions/). + +Once you are a member of the APA Working Group, email the [W3C staff contact for the Spoken Presentation Task Force](https://www.w3.org/groups/tf/pronunciation-tf/participants/#staff) to let them know you’d like to join the task force. + +**Note:** As a participant in one of the APA Working Group’s task forces, you can choose to focus your time exclusively on the task force deliverables and you do not have to contribute to the working group’s other activities. + +## Task force members + +* [Chairs](https://www.w3.org/groups/tf/pronunciation-tf/participants/#chairs) +* [Current participants](https://www.w3.org/groups/tf/pronunciation-tf/participants/#participants) + +## Communications + +* [Calendar of meetings](https://www.w3.org/groups/tf/pronunciation-tf/calendar/) +* [Minutes from previous meetings](https://www.w3.org/WAI/APA/task-forces/pronunciation/minutes) +* [Mailing list archive](https://lists.w3.org/Archives/Public/public-pronunciation/) + +## Publications + +The Spoken Presentation Task Force develops and maintains the following resources for the APA Working Group: + +* [Pronunciation User Scenarios — 2019 Public Working Draft](https://www.w3.org/TR/pronunciation-user-scenarios/) — provides examples of: + - end-users, including screen reader users + - content providers, including educators + - software developers, including content managements systems +* [Pronunciation Gap Analysis and Use — 2020 Public Working Draft](https://www.w3.org/TR/pronunciation-gap-analysis-and-use-cases/) — provides details of the gap analysis: + - gives more contextual details + - describes required features for pronunciation and spoken presentation + - describes specific implementation approaches for introducing presentation authoring markup into HTML5 (called “use cases”) + - provides a gap analysis + - describes how the required features may be met by existing approaches +* [Explainer: Improving Spoken Presentation on the Web — 2020 Public Working Draft](https://www.w3.org/TR/pronunciation-explainer/): — provides an overview of the work: + - briefly introduces the context for W3C work on pronunciation + - describes the advantages and disadvantages of two approaches + - poses questions for additional input + +## Contact the chairs + +If you have a question for the Spoken Presentation Task Force, email the [chairs](https://www.w3.org/groups/tf/pronunciation-tf/participants/#chairs) or the [W3C staff contact](https://www.w3.org/groups/tf/pronunciation-tf/participants/#staff). \ No newline at end of file diff --git a/pages/about/groups/task-forces/pronunciation/work-statement.md b/pages/about/groups/task-forces/spoken-presentation/work-statement.md similarity index 87% rename from pages/about/groups/task-forces/pronunciation/work-statement.md rename to pages/about/groups/task-forces/spoken-presentation/work-statement.md index 96e1a7ac762..d5ae775c882 100644 --- a/pages/about/groups/task-forces/pronunciation/work-statement.md +++ b/pages/about/groups/task-forces/spoken-presentation/work-statement.md @@ -1,7 +1,9 @@ --- title: Spoken Presentation Task Force Work Statement -permalink: /about/groups/task-forces/pronunciation/work-statement/ -ref: /about/groups/task-forces/pronunciation/work-statement/ +permalink: /about/groups/task-forces/spoken-presentation/work-statement/ +ref: /about/groups/task-forces/spoken-presentation/work-statement/ +redirect_from: + - /about/groups/task-forces/pronunciation/work-statement/ lang: en github: label: wai-groups @@ -11,7 +13,7 @@ github: {% include box.html type="start" title="Summary" class="" %} {:/} -The [Spoken Presentation Task Force](/about/groups/task-forces/pronunciation/) is a task force of the [Accessible Platform Architectures (APA) Working Group](/about/groups/apawg/). It assists this Working Group with the work identified below. +The [Spoken Presentation Task Force](/about/groups/task-forces/spoken-presentation/) is a task force of the [Accessible Platform Architectures (APA) Working Group](/about/groups/apawg/). It assists this Working Group with the work identified below. {::nomarkdown} {% include box.html type="end" %} @@ -32,7 +34,7 @@ The [Spoken Presentation Task Force](/about/groups/task-forces/pronunciation/) i ## Status -The Spoken Presentation Task Force was [approved on 10 June 2016](https://lists.w3.org/Archives/Public/public-apa-admin/2018Oct/0008.html) and is now active. The [Task Force home page](/about/groups/task-forces/pronunciation/) contains information about the operation and resources of the group. +The Spoken Presentation Task Force was [approved on 10 June 2016](https://lists.w3.org/Archives/Public/public-apa-admin/2018Oct/0008.html) and is now active. The [Task Force home page](/about/groups/task-forces/spoken-presentation/) contains information about the operation and resources of the group. ## Objective @@ -63,12 +65,12 @@ The SPTF works within the APA Working Group and will focus on achieving a specif ## Communication -Spoken Presentation Task Force communications and discussions are visible to the public. The [task force home page](/about/groups//task-forces/pronunciation/) details communication mechanisms in use. The task force will: +Spoken Presentation Task Force communications and discussions are visible to the public. The [task force home page](/about/groups/task-forces/spoken-presentation/) 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](/about/groups/apawg/decision-policy/) to make decisions; - Provide updates and feedback to APA Working Group teleconferences, as appropriate. These liaisons are primarily the responsibility of the Spoken Presentation Task Force Facilitators; -- Maintain information resulting from its activities (deliverables, participants, face-to-face meetings, teleconferences, etc.) on the [Spoken Presentation Task Force home page](/about/groups/task-forces/pronunciation/). +- Maintain information resulting from its activities (deliverables, participants, face-to-face meetings, teleconferences, etc.) on the [Spoken Presentation Task Force home page](/about/groups/task-forces/spoken-presentation/). ## Participation @@ -93,4 +95,4 @@ Staff contacts from the APA Working Group oversee attention to W3C Process with ## Patent Policy -This Task Force is part of the [APA Working Group Charter](https://www.w3.org/WAI/APA/charter), which operates under the [W3C Patent Policy](https://www.w3.org/Consortium/Patent-Policy-20040205/) (5 February 2004 Version). W3C maintains a public list of any patent disclosures made in connection with the deliverables of the [APA Working Group](https://www.w3.org/2004/01/pp-impl/83907/status). \ No newline at end of file +This Task Force is part of the [APA Working Group Charter](https://www.w3.org/WAI/APA/charter), which operates under the [W3C Patent Policy](https://www.w3.org/policies/patent-policy/20200915/) (15 September 2020 Version). W3C maintains a public list of any patent disclosures made in connection with the deliverables of the [APA Working Group](https://www.w3.org/2004/01/pp-impl/83907/status). \ No newline at end of file diff --git a/pages/about/groups/task-forces/wcag2ict.md b/pages/about/groups/task-forces/wcag2ict.md index cb06d3c1a4f..b329c4d7675 100644 --- a/pages/about/groups/task-forces/wcag2ict.md +++ b/pages/about/groups/task-forces/wcag2ict.md @@ -1,5 +1,5 @@ --- -title: WCAG2ICT Task Force of the AG WG +title: WCAG2ICT Task Force permalink: /about/groups/task-forces/wcag2ict/ ref: /about/groups/task-forces/wcag2ict/ lang: en @@ -11,9 +11,7 @@ github: {% include box.html type="start" title="Summary" class="" %} {:/} -The WCAG2ICT Task Force is a task force of the [Accessibility Guidelines Working Group (AG WG)](/about/groups/agwg/). - -Some information on this page is also shown on, and may be more current in, the [WCAG2ICT Task Force page](https://www.w3.org/groups/tf/wcag2ict/). +Find out about the activities of the WCAG2ICT Task Force and how you can contribute to its objectives. {::nomarkdown} {% include box.html type="end" %} @@ -32,66 +30,79 @@ Some information on this page is also shown on, and may be more current in, the {% include_cached toc.html type="end" %} {:/} -## Announcements +## Objectives + +The objective of the WCAG2ICT Task Force is to develop documentation describing how WCAG 2.x and its principles, guidelines, and success criteria could apply to non-Web Information and Communications Technologies (ICT). + +## Work statement + +To learn about the focus, scope and deliverables of the task force, see the [WCAG2ICT Task Force Work Statement](/about/groups/task-forces/wcag2ict/work-statement/). + + +## Current work + +The WCAG2ICT Task Force supports the deliverables of the [Accessibility Guidelines (AG) Working Group](/about/groups/agwg/). + +For details of the current work, see the [WCAG2ICT Task Force wiki](https://github.com/w3c/wcag2ict/wiki). -[WCAG2ICT W3C Group Note published](https://www.w3.org/TR/wcag2ict/) +## Contribute to the work -## Meetings and Communication +The WCAG2ICT Task Force welcomes input from the global accessibility community on the work to update accessibility guidelines to include non-web documents and software. -The WCAG2ICT TF conducts its work using a variety of synchronous and asynchronous tools. Work is being done via teleconference, email and GitHub issues. +### Contribute without joining the task force -- [Email lists](#mailing-lists); -- [wcag2ict GitHub repository](https://github.com/w3c/wcag2ict/) and [GitHub draft document](https://w3c.github.io/wcag2ict/); -- IRC discussion on the [#wcag2ict IRC channel](http://irc.w3.org/?channels=#wcag2ict), used largely for minute-taking. IF you use your own IRC client: - - Server: irc.w3.org; - - Port 6665, 6667, 21, or 994; - - Channel: #wcag2ict -- [Web-Based Surveys (WBS)](https://www.w3.org/2002/09/wbs/55145/); -- [Teleconferences of the task force](https://www.w3.org/groups/tf/wcag2ict/calendar) (also see [meeting minutes](https://www.w3.org/WAI/GL/task-forces/wcag2ict/minutes)); -- Face to face meetings; +You can contribute to the work without being a member of the task force in the [WCAG2ICT GitHub repository](https://github.com/w3c/wcag2ict/issues): +* If you’re aware of an issue with any of the published WCAG2ICT resources, raise a new issue. +* Comment on or propose solutions for open WCAG2ICT issues. -These tools are used by participants of the Task Force. For ways you can contribute, see [How to Comment, Contribute, and Participate](#contribute). +### Become a participant in the task force -### Teleconferences +Joining the WCAG2ICT Task Force enables you to participate fully in the development of the work and influence the deliverables. You and your organization will also be listed as contributors, where appropriate. -Weekly teleconferences are being held on Thursdays at 10:00 AM Eastern (Boston time). +Being a participant involves commitment to support the work of the task force in the following ways: -- **[WCAG2ICT Task Force](https://www.w3.org/groups/tf/wcag2ict/calendar/)**: Thursdays at 10:00 until 11:00 Boston time +* Engage actively in the work using the task force’s communication channels. +* Keep up with weekly tasks and the progress of the work — for example, via the minutes of past meetings, mailing list discussions, and GitHub issue comments. +* Give your input promptly, when it’s needed. -### Meeting Minutes +To become a participant in the WCAG2ICT Task Force, you must first be a member of the AG Working Group. See [Instructions for joining the Accessibility Guidelines Working Group](https://www.w3.org/groups/wg/ag/instructions/). -[Minutes from previous meetings](https://www.w3.org/WAI/GL/task-forces/wcag2ict/minutes) are available. +Once you are a member of the AG Working Group, email the [W3C Staff Contact for the WCAG2ICT Task Force](https://www.w3.org/groups/tf/wcag2ict/participants/#staff) to let them know you’d like to join the task force. -### Mailing Lists +**Note:** As a participant in one of the AG Working Group’s task forces, you can choose to focus your time exclusively on the task force deliverables and you do not have to contribute to the working group’s other activities. -The WCAG2ICT TF uses the public-wcag2ict-tf@w3.org mailing list ([mailing list archives](http://lists.w3.org/Archives/Public/public-wcag2ict-tf/)) for email discussion. Participants are automatically added to this mailing list when they become a participant of the Task Force. Members of the public can post to this list to send input to the task force. +## Task force members -## Current Work +* [Chairs](https://www.w3.org/groups/tf/wcag2ict/participants/#chairs) +* [Current participants](https://www.w3.org/groups/tf/wcag2ict/participants/#participants) -[Editors' draft of Guidance on Applying WCAG 2 to Non-Web Information and Communications Technologies (WCAG2ICT)](https://w3c.github.io/wcag2ict/) +## Communications + +* [Calendar of meetings](https://www.w3.org/groups/tf/wcag2ict/calendar/) +* [Minutes from previous meetings](https://www.w3.org/WAI/GL/task-forces/wcag2ict/minutes) +* [Mailing list archive](https://lists.w3.org/Archives/Public/public-wcag2ict-tf/) ## Publications -- W3C Group Note [Applying WCAG 2 to Non-Web Information and Communications Technologies (WCAG2ICT)](https://www.w3.org/TR/wcag2ict/) — provides guidance on 2.0, 2.1, and 2.2 success criteria, and supersedes the previous Note -- Previous W3C Group Note [Applying WCAG 2.0 to Non-Web Information and Communications Technologies (WCAG2ICT)](https://www.w3.org/TR/wcag2ict-20/) — provides guidance on WCAG 2.0 success criteria +The WCAG2ICT Task Force develops and maintains the following resources for the AG Working Group: + +* [Guidance on Applying WCAG 2.0 to Non-Web Information and Communications Technologies — 2013 Working Group Note](https://www.w3.org/TR/wcag2ict-20/) — provides guidance on WCAG 2.0 success criteria +* [Guidance on Applying WCAG 2 to Non-Web Information and Communications Technologies — 2024 Group Note](https://www.w3.org/TR/wcag2ict/) — provides guidance on 2.0, 2.1, and 2.2 success criteria, and supersedes the previous Note +* [Guidance on Applying WCAG 2 to Non-Web Information and Communications Technologies (WCAG2ICT) — 2024 Editor’s Draft](https://www.w3.org/TR/maturity-model/) — provides informative (non-normative) guidance on how WCAG 2.x can be applied to non-web documents and software + +## Contact the chairs + +If you have a question for the WCAG2ICT Task Force, email the [chairs](https://www.w3.org/groups/tf/wcag2ict/participants/#chairs) or the [W3C staff contact](https://www.w3.org/groups/tf/wcag2ict/participants/#staff). + + + -## How to Comment, Contribute, and Participate {#contribute} -To join the WCAG2ICT TF, individuals must be participants of the Accessibility Guidelines Working Group. Participants are expected to [actively contribute](/about/groups/task-forces/wcag2ict/work-statement/#participation) to the work of the Task Force. If you are interested in participating in the WCAG2ICT TF, email the task force leadership and working group chairs at [group-ag-chairs@w3.org](mailto:group-ag-chairs@w3.org) and include a little bit about what you’re interested in and how you think that you may be able to contribute to the Task Force. Then follow the instructions on [How to join the Accessibility Guidelines Working Group](https://www.w3.org/groups/wg/ag/instructions/). Once you have joined ask [Daniel Montalvo](mailto:dmontalvo@w3.org) to add you to the task force. -[Current participants in the WCAG2ICT TF](https://www.w3.org/groups/tf/wcag2ict/participants). -## Administrative Information -The WCAG2ICT TF is a Task Force of the [Accessible Guidelines Working Group (AG WG)](/about/groups/agwg/). -### Facilitator and Contacts -- **Facilitator:** Mary Jo Mueller (IBM) -- **Staff Contact:**[Daniel Montalvo](https://www.w3.org/People/#dmontalvo) -Contact the task force leadership and working group chairs via email at [group-ag-chairs@w3.org](mailto:group-ag-chairs@w3.org) -### Work Statement -The [WCAG2ICT Task Force Work Statement](/about/groups/task-forces/wcag2ict/work-statement/) defines the objectives, scope, approach, and participation of the Task Force. The work statement has been approved by the Accessibility Guidelines WG. diff --git a/pages/about/groups/task-forces/wcag2x-backlog.md b/pages/about/groups/task-forces/wcag2x-backlog.md index 6c57364474f..7ab57598633 100644 --- a/pages/about/groups/task-forces/wcag2x-backlog.md +++ b/pages/about/groups/task-forces/wcag2x-backlog.md @@ -1,5 +1,5 @@ --- -title: WCAG 2.x Backlog Task Force of the AG WG +title: WCAG 2.x Backlog Task Force permalink: /about/groups/task-forces/wcag2x-backlog/ ref: /about/groups/task-forces/wcag2x-backlog/ lang: en @@ -11,9 +11,7 @@ github: {% include box.html type="start" title="Summary" class="" %} {:/} -The WCAG 2.x Backlog Task Force is a task force of the [Accessibility Guidelines Working Group (AG WG)](/about/groups/agwg/). - -Some information on this page is also shown on, and may be more current in, the [WCAG 2.x Backlog Task Force page](https://www.w3.org/groups/tf/wcag2x-backlog/). +Find out about the activities of the WCAG 2.x Backlog Task Force and how you can contribute to its objectives. {::nomarkdown} {% include box.html type="end" %} @@ -32,35 +30,67 @@ Some information on this page is also shown on, and may be more current in, the {% include_cached toc.html type="end" %} {:/} -## Announcements and Meetings +## Objectives + +The objectives of the WCAG 2.x Backlog Task Force are to maintain up-to-date versions of the normative and informative materials associated with versions 2.0, 2.1, and 2.2 (2.x) of the Web Content Accessibility Guidelines (WCAG); and to document considerations for WCAG 3.0 that cannot be readily addressed within the existing normative language of the WCAG 2.x specification. + +## Work statement + +To learn about the focus, scope and deliverables of the task force, see the [WCAG 2.x Backlog Task Force Work Statement](/about/groups/task-forces/wcag2x-backlog/work-statement/). + + +## Current work + +The WCAG 2.x Backlog Task Force supports the deliverables of the [Accessibility Guidelines (AG) Working Group](/about/groups/agwg/). + +For details of the current work, see the [WCAG 2.x Backlog Task Force wiki](https://github.com/w3c/wcag/wiki). + +The task force has developed a [workflow process](https://github.com/w3c/wcag/wiki/WCAG-2-Task-Force-process) for: + +* creating and vetting pull requests for WCAG 2.x issues, and +* creating responses to WCAG 2.x issues. + +The process includes a two-week review of all changes by the AG Working Group. + +## Contribute to the work + +The WCAG 2.x Backlog Task Force welcomes input from the global accessibility community on the work to resolve WCAG 2.x issues. + +### Contribute without joining the task force + +You can contribute to the work without being a member of the task force by commenting on or proposing solutions for open issues in the [WCAG GitHub repository](https://github.com/w3c/wcag/issues). + +### Become a participant in the task force + +Joining the WCAG 2.x Backlog Task Force enables you to participate fully in the development of the work and influence the deliverables. You and your organization will also be listed as contributors, where appropriate. + +Being a participant involves commitment to support the work of the task force in the following ways: + +* Engage actively in the work using the task force’s communication channels. +* Keep up with weekly tasks and the progress of the work — for example, via the minutes of past meetings, mailing list discussions, and GitHub issue comments. +* Give your input promptly, when it’s needed. -No announcements at the moment. +To become a participant in the WCAG 2.x Backlog Task Force, you must first be a member of the AG Working Group. See [Instructions for joining the Accessibility Guidelines Working Group](https://www.w3.org/groups/wg/ag/instructions/). -## Approach -The WCAG 2.x Backlog TF is a Task Force of the AG WG, which has oversight over the Task Force to ensure accurate interpretation and representation of WCAG 2.x. The AG WG decision process applies within the group. We have an AG WG co-chair liaison to ensure draft content is taken to the AG WG for review as it progresses. +Once you are a member of the AG Working Group, email the [W3C staff contact for the WCAG 2.x Backlog Task Force](https://www.w3.org/groups/tf/wcag2x-backlog/participants/#staff) to let them know you’d like to join the task force. -The WCAG 2.x Backlog TF has developed a [workflow process](https://github.com/w3c/wcag/wiki/WCAG-2-Task-Force-process) for both creating and vetting pull requests and creating responses to issues. The process also includes a two-week review of all changes by the AG WG. +**Note:** As a participant in one of the AG Working Group’s task forces, you can choose to focus your time exclusively on the task force deliverables and you do not have to contribute to the working group’s other activities. -## Communication -The communications of the WCAG 2.x Backlog Task Force are publicly visible. Communication mechanisms include: +## Task force members -* [Publicly archived mailing list](https://lists.w3.org/Archives/Public/public-wcag2-issues/); -* Public [GitHub](https://github.com/w3c/wcag/) and [Wiki](https://github.com/w3c/wcag/wiki) spaces; -* Public minutes (on the wiki and email list); -* Regular updates to the AGWG via the [AGWG email list](https://lists.w3.org/Archives/Public/w3c-wai-gl/); +* [Chairs](https://www.w3.org/groups/tf/wcag2x-backlog/participants/#chairs) +* [Participants](https://www.w3.org/groups/tf/wcag2x-backlog/participants/) -## Participation -To join this WCAG 2.x Backlog Task Force, individuals must be participants of AG WG. Participants are expected to actively contribute to the work of the task force, including: +## Communications -* Minimum 4 hours per week of task force work (this time also counts towards the individual's participation requirement in the AG WG); -* Remain current on the task force mailing list and respond in a timely manner to postings; -* Participate regularly in task force meetings. +* [Calendar of meetings](https://www.w3.org/groups/tf/wcag2x-backlog/calendar/) +* [Minutes from previous meetings](https://github.com/w3c/wcag/wiki/Meeting-minutes-index) +* [Mailing list archive](https://lists.w3.org/Archives/Public/public-wcag2-issues/) -If you are interested in becoming a participant of the WCAG 2.x Backlog Task Force or have any questions regarding its work, contact the task force facilitators. +## Publications -## Facilitation -The AG Working Group chair liaison oversees 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 reporters of progress to the Working Group. +The WCAG 2.x Backlog Task Force does not develop publications. -* Facilitators: Bruce Bailey, US Access Board; Michael Gower, IBM Corporation +## Contact the facilitators (not chairs? why the inconsistency?) -* AG WG chair liaison: Alastair Campbell, Nomensa +If you have a question for the WCAG 2.x Backlog Task Force, email the [chairs](https://www.w3.org/groups/tf/wcag2x-backlog/participants/#chairs) or the [W3C staff contact](https://www.w3.org/groups/tf/wcag2x-backlog/participants/#staff). \ No newline at end of file diff --git a/pages/about/groups/task-forces/wcag2x-backlog/work-statement.md b/pages/about/groups/task-forces/wcag2x-backlog/work-statement.md new file mode 100644 index 00000000000..1a737ec916d --- /dev/null +++ b/pages/about/groups/task-forces/wcag2x-backlog/work-statement.md @@ -0,0 +1,89 @@ +--- +title: WCAG 2.x Task Force Work Statement +permalink: /about/groups/task-forces/wcag2x-backlog/work-statement/ +ref: /about/groups/task-forces/wcag2x-backlog/work-statement/ +lang: en +doc-note-type: draft +github: + label: wai-groups +--- + +{::options toc_levels="2..3" /} + +{::nomarkdown} +{% include_cached toc.html type="start" title="Page Contents" %} +{:/} + +- TOC is created automatically. +{:toc} + +{::nomarkdown} +{% include_cached toc.html type="end" %} +{:/} + +The Web Content Accessibility Guidelines 2.x Task Force (WCAG 2 TF) is a task force of the [Accessibility Guidelines Working Group (AG WG)](/about/groups/agwg/). It assists this Working Group with the work identified below. + +## Status + +This work statement is a draft yet to be approved. The task force is active. + +NOTE: This work is mentioned in the [Other Deliverables section of the current AG WG Charter.](https://www.w3.org/2019/12/ag-charter#ig-other-deliverables) The continuation of the work is also included in the [current AG WG Charter](https://www.w3.org/2023/11/ag-charter). + +* Ongoing updates of non-normative resources to understand and implement guidance, including the current [Understanding WCAG 2.x](https://www.w3.org/WAI/WCAG22/Understanding/) and [Techniques for WCAG 2.x](https://www.w3.org/WAI/WCAG22/Techniques/) as well as new resources to support implementation of the new standard. +* Errata for WCAG 2.1 and 2.2. + +## Objective + +The objective of the WCAG 2 Task Force is to maintain up-to-date versions of the normative and informative materials associated with versions 2.0, 2.1, and 2.2 of the Web Content Accessibility Guidelines, and to document considerations for WCAG 3.0 which cannot be readily addressed within the existing normative language of the 2.x specification. + +## Scope of Work + +The work of the WCAG 2 TF includes: + +* Monitoring and responding to issues opened against the [WCAG github](https://github.com/w3c/wcag/issues) repository; +* Drafting and vetting recommended changes to the existing WCAG documents, in the form of pull requests and other documentation; +* Promoting the ongoing relevance of WCAG 2, and encouraging participation and contribution by different key stakeholders. + +Explicitly out of scope for the WCAG 2 TF is: +* developing a new normative standard or any new normative requirements, beyond suggesting changes to correct 2.x normative language. + +## Approach + +The WCAG2 TF is a Task Force of the AG WG, which has oversight over the Task Force to ensure accurate interpretation and representation of WCAG 2.x. The AG WG decision process applies within the group. We have an AG WG co-chair liaison to ensure draft content is taken to the AG WG for review as it progresses. + +The WCAG 2 TF has developed a [workflow process](https://github.com/w3c/wcag/wiki/WCAG-2-Task-Force-process) for both creating and vetting pull requests and creating responses to issues. The process also includes a two-week review of all changes by the AG WG. + +## Communication + +The communications of the WCAG 2 Task Force are publicly visible. Communication mechanisms include: + +* Task force homepage (link TBC); +* [Publicly archived mailing list](https://lists.w3.org/Archives/Public/public-wcag2-issues/); +* Public [GitHub](https://github.com/w3c/wcag/) and [Wiki](https://github.com/w3c/wcag/wiki) spaces; +* Public minutes (on the wiki and email list); +* Regular updates to the AGWG via the [AGWG email list](https://lists.w3.org/Archives/Public/w3c-wai-gl/); + +## Participation + +To join this WCAG 2 Task Force, individuals must be participants of AG WG. Participants are expected to actively contribute to the work of the task force, including: + +* Minimum 4 hours per week of task force work (this time also counts towards the individual's participation requirement in the AG WG); +* Remain current on the task force mailing list and respond in a timely manner to postings; +* Participate regularly in task force meetings. + +If you are interested in becoming a participant of the WCAG 2 Task Force or have any questions regarding its work, contact the task force facilitators. + +[Current WCAG 2 TF participants](https://www.w3.org/groups/tf/wcag2x-backlog/participants/) + +Contact [Ken Franqueiro](mailto:kfranqueiro@w3.org) to become a participant of the WCAG 2 Task Force or with questions. + +## Facilitation + +The AG Working Group chair liaison oversees 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 reporters of progress to the Working Group. + +* [Chairs](https://www.w3.org/groups/tf/wcag2x-backlog/participants/#chairs) +* [Staff Contact](https://www.w3.org/groups/tf/wcag2x-backlog/participants/#staff) + +## Patent Policy + +This Task Force is part of the [AG Working Group Charter](https://www.w3.org/WAI/GL/charter), which operates under the [W3C Patent Policy](https://www.w3.org/Consortium/Patent-Policy-20200915/) (15 September 2020 Version). W3C maintains a public list of any patent disclosures made in connection with the deliverables of the [AG Working Group](https://www.w3.org/groups/wg/ag/ipr). \ No newline at end of file diff --git a/pages/about/index.md b/pages/about/index.md index b2bb0143747..61e09bca8e5 100644 --- a/pages/about/index.md +++ b/pages/about/index.md @@ -142,6 +142,4 @@ WAI includes the following Working Groups and Interest Group: - [Accessible Rich Internet Applications (ARIA) Working Group](/about/groups/ariawg/) - [WAI Interest Group (WAI IG)](/about/groups/waiig/) hosts an e-mail discussion list that is open to anyone -Within the Working Groups, there are also [Task Forces](/about/groups/task-forces/). - Learn more about [Participating in WAI](https://www.w3.org/WAI/about/participating/).