Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WG and TF updates #1018

Open
wants to merge 31 commits into
base: main
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from 19 commits
Commits
Show all changes
31 commits
Select commit Hold shift + click to select a range
589b8a1
First draft AG
iadawn Dec 13, 2024
6fe1172
Fix typos
tamsinewing555 Dec 19, 2024
ecc93ab
Delete repeated information
tamsinewing555 Dec 19, 2024
e0cd2b6
Suggested tweaks
tamsinewing555 Dec 23, 2024
62d1b1e
Correct typo and add anchor link
tamsinewing555 Dec 23, 2024
7c1651f
Fix broken link and simplify link text
tamsinewing555 Dec 23, 2024
57d3591
Improving wording and link text
tamsinewing555 Dec 24, 2024
0e03f5f
Remove list formatting and fix link text
tamsinewing555 Dec 24, 2024
39bfe65
Remove unnecessary wording
tamsinewing555 Dec 24, 2024
f891d68
Apply new structure and design to the content
tamsinewing555 Dec 24, 2024
026dca8
Fix wording, links and punctuation
tamsinewing555 Dec 24, 2024
5dc1f1d
Correct link and some wording
tamsinewing555 Dec 26, 2024
dbbfc26
Correct and add links in patent disclosures section
tamsinewing555 Dec 26, 2024
84c78ab
Fix link
tamsinewing555 Dec 26, 2024
89fe0ca
Fix second link
tamsinewing555 Dec 26, 2024
e6f0446
Fix link text
tamsinewing555 Dec 26, 2024
94872f8
Apply new template design to page
tamsinewing555 Dec 27, 2024
f2c6617
Correct initialism
tamsinewing555 Dec 27, 2024
b01f2ca
Use sentence case for heading
tamsinewing555 Dec 27, 2024
6385b1d
Delete W3C Process info and move funding info.
tamsinewing555 Dec 27, 2024
9235172
Apply new template design to page
tamsinewing555 Dec 27, 2024
39ec694
Restructure funding info
tamsinewing555 Dec 27, 2024
415272d
Remove funding info
tamsinewing555 Dec 27, 2024
12cbc80
Correct heading
tamsinewing555 Dec 27, 2024
f25d218
Apply new template design to page
tamsinewing555 Dec 27, 2024
a2d08bb
Apply new template design to COGA TF
tamsinewing555 Dec 29, 2024
a64a1cc
Apply new template to Mobile A11y TF
tamsinewing555 Dec 29, 2024
a979940
Apply new template to Maturity Model TF
tamsinewing555 Dec 29, 2024
abaf85a
Correct typos
tamsinewing555 Dec 29, 2024
56a0c18
Apply new template to RQ TF
tamsinewing555 Dec 30, 2024
40c4dec
Apply new template to Spoken Presentation TF
tamsinewing555 Dec 30, 2024
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
91 changes: 52 additions & 39 deletions pages/about/groups/agwg.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
title: Accessibility Guidelines Working Group (AGWG)
nav_title: '<span>AGWG: Accessibility Guidelines <abbr title="Working Group">WG</abbr></span>'
title: Accessibility Guidelines Working Group
nav_title: '<span>AG: Accessibility Guidelines <abbr title="Working Group">WG</abbr></span>'
lang: en
permalink: /about/groups/agwg/
ref: /about/groups/agwg/
Expand All @@ -12,9 +12,10 @@ 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.
The mission of the Accessibility Guidelines (AG) Working Group is to develop and maintain:

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/).
* specifications for making web content accessible to people with disabilities, and
* support materials for implementing the Web Content Accessibility Guidelines (WCAG).

{::nomarkdown}
{% include box.html type="end" %}
Expand All @@ -33,67 +34,79 @@ Some information on this page is also shown on, and may be more current in, the
{% include_cached toc.html type="end" %}
{:/}

## Announcements
## Charter

No announcements at the moment.
The group is chartered until October 2025.

## Current Work
To learn about the group’s current focus, scope and deliverables, see the [AG Working Group Charter](https://www.w3.org/WAI/GL/charter).

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.
The work of the AG Working Group follows the [W3C Process](https://www.w3.org/2023/Process-20231103/).
tamsinewing555 marked this conversation as resolved.
Show resolved Hide resolved

This work is partly funded by the [WAI Core 2015 Project](https://www.w3.org/WAI/about/projects/wai-core-2015/). The work of the AG Working Group does not necessarily reflect the views or policies of the funders.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Again this seems to have crept in, although I think in this case it is needed. The trouble is where to put it. Not really in 'Current work'. Not sure it fits anywhere in new structure. Closest might be 'Contribute to the work'. Open to ideas.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I did think the information about who funds the work sits best under 'current work, since it's related.
But if that doesn't make sense, then how about we place it under 'Charter and funding'?

Copy link
Contributor Author

@iadawn iadawn Dec 27, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, I think it needs to be separate from the Charter... not that I am being helpful with alternative ideas!

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We could place the information under a new h2 heading called 'About the work'. Under that heading will be two h3 headings:

  • Current work
  • Funding
    I've mocked this up on the ARIA WG page that I committed this morning.

Or we could place the information under its own heading, 'Funding', after 'Publications and copyright'?

I don't think the funding information sits logically under 'Contribute to the work' because this is just information about the group (how it is funded) and not a call to action (i.e. to contribute funding), like the other items in this section.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think it should be close to the 'Current work'. Even having a 'funding' section doesn't make sense to me. If you take it out for the moment and then we can discuss in New Year - we could publish without it and then fix following discussion.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will do. This information was removed by a reviewer in the original mock up of the proposed design, so perhaps the information isn't needed on this page and is more appropriate on the 'Sponsor WAI page'?


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 &mdash; GitHub](https://github.com/w3c/wcag/issues/).

## Contribute to the work

### Task Forces
W3C and the AG Working Group welcome input on WCAG work from the global accessibility community.

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.
### Contribute without joining the group

## How to Comment, Contribute, and Participate
There are many ways you can contribute without being a member of the working group:

The Accessibility Guidelines Working Group engages with stakeholders in a variety of ways. See the following resources for information on:
* **Comment on publications:** During development, the group publishes working drafts for public comment &mdash; 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/) &mdash; 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 &mdash; to contribute your views, see the list of [open WCAG 3 discussions](https://github.com/w3c/wcag3/discussions).
* **Participate in a community group:** W3C hosts a small number of active community groups that focus on digital accessibility issues &mdash; for details, search for ‘accessibility’ on [Current Groups &mdash; W3C Community and Business Groups](https://www.w3.org/community/groups).

* [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/).
### Become a participant in the group

## Meetings and Communication
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 AG WG conducts its work using a variety of synchronous and asynchronous tools. The [communication page](/about/groups/agwg/communication/) provides details about:
Being a participant involves commitment to support the work of the group in the following ways:

* 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).
* 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 &mdash; for example, via the minutes of past meetings, mailing list discussions, and GitHub issue comments.
* Give your input promptly, when it’s needed.

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/).
See [Instructions for joining the Accessibility Guidelines Working Group](https://www.w3.org/groups/wg/ag/instructions/).

### Meeting Minutes
## Group members and task forces

[Minutes from previous meetings](https://www.w3.org/WAI/GL/minutes-history) are available.
* [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
iadawn marked this conversation as resolved.
Show resolved Hide resolved

## Administrative Information
## Communications and decisions

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.
* [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/)

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 [[email protected]](mailto:[email protected]).
## 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 [[email protected]](mailto:group-ag-plan@w3.org) to reach these people as well as the chairs.
See the full [List of publications 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 &mdash; for details, see [Intellectual property rights &mdash; 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
iadawn marked this conversation as resolved.
Show resolved Hide resolved

[Current participants in the AGWG](https://www.w3.org/groups/wg/ag/participants/).
If you have a question for the group’s chairs or the W3C staff contact, email [[email protected]](mailto:group-ag-chairs@w3.org).
Loading