Skip to content

Commit

Permalink
WG and TF updates (#1018)
Browse files Browse the repository at this point in the history
* First draft AG

* Fix typos

* Delete repeated information

* Suggested tweaks

- abbreviations (expanding some)
- simplify summary sentence (without removing or changing meaning) and format as a list for readability
- add section with quick link to Admin home page
- remove generic headings
- add headings / structure content meaningfully under headings that match key words in the information
- make headings sentence case
- remove capital letters from nouns that are not proper nouns
- Make link text slightly more descriptive, including signaling if moving away from WAI to a different sub-site.
- Add / correct URLs
- remove passive tense
- use plain language
- make sentences more concise
- make list items consist of only one sentence per item (best practice)
- fix typos

* Correct typo and add anchor link

* Fix broken link and simplify link text

* Improving wording and link text

* Remove list formatting and fix link text

* Remove unnecessary wording

* Apply new structure and design to the content

* Fix wording, links and punctuation

* Correct link and some wording

* Correct and add links in patent disclosures section

* Fix link

* Fix second link

* Fix link text

* Apply new template design to page

* Correct initialism

* Use sentence case for heading

* Delete W3C Process info and move funding info.

* Apply new template design to page

* Restructure funding info

* Remove funding info

* Correct heading

* Apply new template design to page

* Apply new template design to COGA TF

* Apply new template to Mobile A11y TF

* Apply new template to Maturity Model TF

* Correct typos

* Apply new template to RQ TF

* Apply new template to Spoken Presentation TF

* Apply new template to WAI-Adapt TF

* Fix links

* Apply new template to WCAG 2.x Backlog TF

* Apply new template to WCAG2ICT TF

* correct typo em dash

* Correct links

* Apply new template to WAI IG

* Update landing page for WGs and WAI-IG

- remove distracting information that belongs to pages under other sections in the WAI sub-site, and groups that have closed
- make the summaries consistent with those on the WG pages

* Correct typo

* Add comma

* Correct inconsistencies

* Fix contact details

* Update landing pages WGs and TFs

And testing using h2 on landing pages

* Add semantic structure to list of links on landing pages

* Fix line breaks and expand summary sentence

* Make landing page title clearer

* Use HTML for line break

* Make terms match abbreviations

* Update title

* Remove TF names from link text

* Update missing content

* Change WGs landing page headings back to dl list

* Change TFs landing page headings back to dl list

and remove closed TF

* Update TF landing page title

* Apply new template to Low Vision TF

* Revert page titles to using title case

* Fix perm names

* Update ARIA wiki link

* Remove inline comment

* Harmonize with new WG pages structure

* Update pages/about/groups/task-forces/conformance-testing.md

Co-authored-by: Daniel Montalvo <[email protected]>

* Update pages/about/groups/task-forces/conformance-testing.md

Remove 'Rules'

Co-authored-by: Daniel Montalvo <[email protected]>

* Update pages/about/groups/task-forces/practices.md

Add 'ARIA' to WG name

Co-authored-by: Daniel Montalvo <[email protected]>

* Update pages/about/groups/task-forces/practices.md

Use APG abbreviation

Co-authored-by: Daniel Montalvo <[email protected]>

* Update pages/about/groups/task-forces/practices.md

Use 'APG' abbreviation

Co-authored-by: Daniel Montalvo <[email protected]>

* Update pages/about/groups/task-forces/wcag2ict.md

Add WCAG version

Co-authored-by: Daniel Montalvo <[email protected]>

* Update pages/about/groups/task-forces/wcag2ict.md

Remove question

Co-authored-by: Daniel Montalvo <[email protected]>

* Update pages/about/groups/task-forces/wcag2ict.md

Remove duplicated wording

Co-authored-by: Daniel Montalvo <[email protected]>

* Update pages/about/groups/task-forces/practices.md

Use 'APG' abbreviation

Co-authored-by: Daniel Montalvo <[email protected]>

* Update pages/about/groups/task-forces/practices.md

Use 'APG' abbreviation

Co-authored-by: Daniel Montalvo <[email protected]>

* Update pages/about/groups/task-forces/wcag2ict.md

Add link to wiki

Co-authored-by: Daniel Montalvo <[email protected]>

* Update pages/about/groups/task-forces/wcag2ict.md

Remove unnecessary wording

Co-authored-by: Daniel Montalvo <[email protected]>

* Update pages/about/groups/task-forces/wcag2ict.md

Remove unnecessary wording

Co-authored-by: Daniel Montalvo <[email protected]>

* Add staff contact email address for MM TF

* Add missing Oxford commas

* Revert "Add missing Oxford commas"

This reverts commit 6a7437a.

* Add Oxford comma, correct link text, remove TR version to be consistent with ARIA WG link

* Move process doc; correct links; add list of ARIA repos

* Correct anchor link id

* Shorten heading

* Remove contribute page -- info is already in main page and in readme

* Remove -- most info is already in main page

* Remove -- info to go on github wiki

* Remove -- infor already in main page

* Remove -- no longer maintained

* Remove -- farily outdated, process is more up-to-date

* Remove -- relevant info is now on readme

* Remove -- duplicate info

* Add calendars, repos, and other missing info

* Add heading

* Add links to mappings work

* Updates for WCAG2 backlog group

* Link work statement

* Remove anchor target

* Mobile Accessibility work statement

* Update staff contact links

* Remove unnecessary link text

* @tamsinewing555 I don't think we should be using version here. This is probably more for the type of content under https://www.w3.org/WAI/standards-guidelines/aria/

* Add graphics AAM

* Remove link to contribute (to be removed) page and updaet to actual pointer to mailing list

* Remove CG references

* This is also an ARIA deliverable

* Link to GitHub repo instead of gh pages

* Remove who develops the deliverable -- I don't think this is needed here.

* Remove who develops the deliverable -- I don't think this is needed here.

* Remove who develops the deliverable -- I don't think this is needed here.

* Add TF child section to Groups landing page

* Add Oxford comma

* Add WCAG 2.x Backlog TF calendar

* Remove unnecessary words

* @iadawnUpdate pointers to ACT work statement

* Add WG Charter dates, change spec to publications, remove community groups, add COGA guidance

* Add FAST TF to groups

* Fix navigation

* Shorten to contraction

* Correct typos

* Remove duplication

* Update WCAG 2.x Backlog Work Statement

* Add explicit mention to ACT Rules Format t 1.1 in scope

* Improve page summaries

* Update content on MA TF page

* Add APA Review repo

* Tighten and remove list formatting from summaries;

* Correct punctuation

* Deleted apawg/communication

* Draft content for PDF-AAM Task Force

* Update overview page

* Update pdf-aam work statement

* Fix typo

* Move Work statement and remove announcements

* Include objective in group page

* Fix typo

* Write out LWG

* Backgroun on PDF-UIA Processor LWG based on their available info

* Ced WAI list

* Update title

Co-authored-by: Shawn Lawton Henry <[email protected]>

* Update pdf-aam.md

Review of draft content

* Update work-statement.md

Review of draft content

* Fix wrong WG link

* Add abbr for APIs

* Caps for abbr title value

* Remove duplicate infor about minutes

* Remove duplicate info about how to contribute

* Remove duplicate info about PDF-AAM source repo

* Remove duplicate information about the Task Force and place relevant info at the top

* Try title_HTML to hold abbr

* Clarify work status

* Add link to ISO 14289-1:2012

* Accessibility -> Application

* Remove abbr from summary (already used in h1)

* Expand APIs in second sentence of the summary box

* Addb back the link to Editors Draft

* Add abbr to h1

* Expand APIs in second sentence of the summary

* Fix PDF standard link

* Remove 1.0. This is a Living Recommendation

* Harmonize PDF-AAM Task Force page

* Correct typos  and links PDF-AAM Task Force

* Correct link

* Delete WG child pages with duplicated info

* Add name of WG to Decision Policy page title

* Remove abbreviation in h1

* Improve/correct h1 page titles

PDF is a common abbreviation that has become part of the English language - it's better understood than the expanded term

* Correct link text

* Update ACT work statement status

* Remove duplicate

* Include updates to WCAG2ICT Work Statement

* Create previous groups page

* Add previous groups to groups landing page

* Add archived note to CSS and Silver TFs

* Add closing wording to archived TFs

* Update TF landing page with improved wording for APA TFs

* Update page summaries for APA TFs

* Remove abbreviation for Spoken Presentation TF

* Add missing abbreviation for references to APA WG

* Apply suggestions from code review

* Put "CSS-A11Y" and "Silver" task forces pages into an archive/ folder.

* Test new navigation

* Mark the draft work statements as "Draft"

* Properly test the new navigation

* ACT TF Work Statement fixes:
- Fix link to ARIA WG page
- Remove reference to the closed EOWG
- Update the "Browser Testing and Tools WG" link to point to the W3C website group page.
- Fix broken link to current participants
- Fix broken link to Daniel's section in the Staff listing

* ARIA Authoring Practices TF Work Statement updates:
- Remove "@@" before "Current APG Task Force participants"
- Update the link to current participants
- Update the Patent Policy date and dated URL: use the version referenced in the latest ARIA WG Charter

* ACT TF Work Statement: update the Patent Policy date and dated URL, to use the version referenced in the latest AG WG Charter

* COGA TF Work Statement: Fix link to #references fragment

* WAI-Adapt TF Work Statement updates:
- Add an external icon to the "IMS Global Learning Consortium" link text
- Update the link to current participants
- Udate the Patent Policy date and dated URL, to use the version referenced in the latest APA WG Charter

* PDF-AAM TF Work Statement: update the Patent Policy date and dated URL, to use the version referenced in the latest ARIA WG Charter

* Spoken Presentation TF Work Statement: update the Patent Policy date and dated URL, to use the version referenced in the latest APA WG Charter

* Research Questions TF Work Statement updates:
- Update link to current participants page
- Update the Patent Policy date and dated URL, to use the version referenced in the latest APA WG Charter

* Moving TF listings into Groups page

* Remove TFs page

* Fix abbreviations

Since PDF and ARIA have become part of the English language (and the terms are generally more familiar to people than their expanded forms), I've made these changes to the page titles (and h1), but for clarity have kept the expanded terms in the summary sentences.

* Update TF summary sentences

Taking in feedback from Janina

* Update groups landing page

Formatted the top-level groups with h2 rather than having a long page of nested lists. This helps to make the structure of the information visually clearer (in the nested lists all the links are the same font size)
- Removed the TF summary sentences in the nested lists to reduce information overload on the landing page. The TF objectives are available right at the top of each page, when people click through.
This also helps the 'WAI-IG' and 'Previous groups' pages stand out and not be buried by all the TF information on this higher level landing page.

* Correct mark up

* Remove unnecessary abbreviations

The abbreviations are given in the first sentence and add unnecessary clutter to the page titles.

* Replace expanded form with abbreviation

PDF has become part of the English language and is better understood than the expanded form.

* Use the new 'Spoken Presentation' task-force name in links

* Spoken Presentation Work Statement: fix broken link to the task force home page

* Update WG & TF summaries, and add mission, objectives sections

Also remove charter information for WGs

* Update WG landing page to remove h2 links

* Correct markdown

* Remove link

* Redirect old Task forces page to Groups page

* Redirects removed pages

* Add approval of the work with PDF-AAM

* Use wai-website-data master branch

---------

Co-authored-by: Tamsin Ewing <[email protected]>
Co-authored-by: Daniel Montalvo <[email protected]>
Co-authored-by: Daniel <[email protected]>
Co-authored-by: Tamsin Ewing <[email protected]>
Co-authored-by: Shawn Lawton Henry <[email protected]>
Co-authored-by: Rémi Bétin <[email protected]>
Co-authored-by: Rémi Bétin <[email protected]>
  • Loading branch information
8 people authored Feb 27, 2025
1 parent cb5f76f commit 9485a23
Show file tree
Hide file tree
Showing 59 changed files with 1,504 additions and 2,146 deletions.
104 changes: 64 additions & 40 deletions pages/about/groups/agwg.md
Original file line number Diff line number Diff line change
@@ -1,9 +1,13 @@
---
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: 'Accessibility Guidelines <abbr title="Working Group">WG</abbr>'
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
---
Expand All @@ -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" %}
Expand All @@ -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 &mdash; 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 &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 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 &mdash; for details, search for ‘accessibility’ on [Current Groups &mdash; 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 &mdash; 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 [[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.
[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 &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

[Current participants in the AGWG](https://www.w3.org/groups/wg/ag/participants/).
If you have a question for the AG Working Group’s chairs or the W3C staff contact, email [[email protected]](mailto:group-ag-chairs@w3.org).
82 changes: 0 additions & 82 deletions pages/about/groups/agwg/communication.md

This file was deleted.

4 changes: 2 additions & 2 deletions pages/about/groups/agwg/decision-policy.md
Original file line number Diff line number Diff line change
@@ -1,13 +1,13 @@
---
title: Decision Policy
title: Accessibility Guidelines Working Group Decision Policy
permalink: /about/groups/agwg/decision-policy/
ref: /about/groups/agwg/decision-policy/
lang: en
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.

Expand Down
Loading

0 comments on commit 9485a23

Please sign in to comment.