This Wiki page is edited by participants of the WCAG Working Group. It does not necessarily represent consensus and it may have incorrect information or information that is not supported by other Working Group participants, WAI, or W3C. It may also have some very useful information.
WCAG 2.2 Issue tracking and resolution
From WCAG WG
The issue tracking for WCAG 2.2 is done in Github issues for the WCAG repository, and there is a project for WCAG 2.2 which helps track movement of issues.
We have a Friday meeting to review issues which is open to any AG members.
Issue lists per criterion
For each criteria we have a list of open issues, please do get involved:
- Accessible Authentication CFC passed
- Dragging CFC passed
- Consistent Help CFC passed
- Page break locators (REMOVED)
- Focus Appearance
- Focus Appearance (Enhanced) (REMOVED)
- Visible Controls (REMOVED)
- Target Size (Min) CFC Passed
- Redundant Entry CFC passed
Dealing with issues
The basic process for issues is:
- An issue is raised;
- People comment on the issue, agree, disagree, improve, change, etc;
- A person from the group creates a response (e.g. explaining why no change will be made) or creating an update to the documents to put in front of the group.
- The group decides to either: Accept the proposed response (sometimes with some editing), or agree with updating the criterion / documentation, or we do not get agreement and need another round of discussion.
Dealing with an issue
The group decision bit breaks down more, individually YOU can:
- Pick an issue, ideally something you are interested in.
- Read it through, try and understand the arguments, maybe write down a summary for yourself.
- If you are going to tackle it, assign the issue to yourself (If the "assign yourself" link does not appear, please email Michael Cooper your GitHub username and ask to get your Github account added to the WCAG repository).
- Decide what the appropriate response is, which can be any or all of:
- Draft a response to the issue-opener. You can do that as a comment on the thread starting with "Proposed response:", or you can email the AG chairs.
- Draft a change to the success criterion that addresses the issue.
- Draft an update to the understanding document.
- Add a label to the issue of "Survey - Ready for".
You can create the response/update in any format, including:
- A draft response posted in the thread.
- A draft response emailed to the AG chairs.
- Updates drafted in a Pull request.
- Updates drafted in a Google doc.
Then ping the AG chairs that it is ready for surveying, and we discuss it in a meeting.