WCAG3 working process

This page proposes how the AGWG and Silver intend to work on migration of WCAG 2.2 SC to WCAG3.

Overall process

1. An initial list of WCAG to Silver Migration Outline Map was drafted in March 2019 to see how SC could potentially be re-grouped into guidelines by user needs. This list can be used as guidance, but we encourage changing it based on user needs as the potential guidelines are developed.
2. The people who are migrating the WCAG 2.2 SC(s) will write up a plain English statement of what the new guideline is trying to achieve.
3. We will run a survey for people to sign up to work on each SC, creating one cross-discipline group (CDG) per SC. We are looking for 2-5 people on each SC, including 1 or 2 subject-matter-experts (e.g. COGA TF members for a COGA SC), and 1-3 people from other TFs or the Working Group. At least one person should be familiar with writing WCAG3 style guidelines.
4. Each mini-group will [create a document from template] for each new guideline. This process will take a few weeks, and could run in parallel to the review sprints.
5. We will hold a survey to establish the initial ordering of SC to migrate.
   • The survey will contain a mechanism to quantify the prioritization of SC to work on.
6. The first two (a) guidelines will be reviewed by the working group, and worked on in 2-week review sprints.
   • Feedback offered by the WG in the first week needs to be incorporated by the end of the week for Working Group review during week two.
   • We anticipate that each guideline will take three (3) two-week sprints. An estimate would be:
     1. Write Scope, identify user flow and user needs
     2. Write Outcomes, Tests, and Methods
     3. Write How-To and formal wording of the guideline
7. At the end of each sprint "objections" (b) are noted in a survey, and SC not agreed on are put in the backlog. SCs that have been put into the backlog can be put into a new sprint if there are changes that address the objections.
8. At the end of the three sprints two SC will be selected for the next sprint. There will need to be discretion by the chairs to keep making progress efficiently, deciding when to put SC into each sprint or move on to new SC.
9. When there is agreement that an SC is complete (except for scoring) it will be integrated in to the Editors draft for publication in the next Working Draft.

Note: The group will run periodic retrospective to assess the process & progress, approximately every 5 sprints.

Notes

a) After the 1st sprint, we may vary the number of SCs we deal with at one time.

b) "Objections" in the sense of "this doesn't meet the SC requirements yet", it does not mean the purpose of the SC is invalid.

Github is still the best place for comments, but each document will be listed on this wiki.