WCAG 3 List of Core Issues to Address

	A	B	C	D	E	F	G
1	Core Issues that Need to be Addressed	Related Questions	GitHub Discussion	Status	Latest Subgroup	Priority June 2022	WCAG 3 Timeline
2	Foundational Work (See https://github.com/w3c/silver/projects/7)
3	Accessibility Supported	How comprehensive (across language, OS, browser, etc) does support need to be before guidance is not needed? How do we write the standards so that as coverage increases or when coverage is universal within a closed ecosystem, the user agent and AT support can be claimed as conforming even if the author did nothing? How do we ensure international applicability (example: japanese screen readers)? COGA tools have unique needs and barriers regarding accessibility supported that needs to be captured (for example not being able to install the tools they need, greater variety in tools, using the library to access content How do we evaluate/address situations where the code is correct but the AT its used with (or user agent AT combo) doesn't work?		New group starting
4	Alternate Versions	How do we support evolving technology?
5	ATAG (How and when to include this)	How do we assign responsibility for accessibility between authors, user agents, authoring tools, and assisitive technologies? Are outcomes written to span the end-to-end ecosystem with specific methods to support it (including user agents, etc)
6	Continued improvement	How do we design WCAG to encourage continued improvement while recognizing less than perfect accessibility?
7	Equity	How do we improve the equity of the guidance between different disability types, now and in the future, while preserving a reasonable effort bar for conformance? Can WCAG 3's conformance modal be updated regularly to continually improve equity?
8	Evaluating proposed solutions (QA)	What is the process we use to evaluate various proposals? (metrics, use cases, ?) How do we improve the equity of the guidance between different disability types, now and in the future? What criteria/questions do we use to evaluate new ? How do we reduce or avoid dramatically increasing the cost of testing (e.g. encourage automated testing without reducing the accessibility from manual testing?)		Test reliability subgroup wrapping up
9	Policy Uptake	What considerations are there for uptake in a policy environment?
10	Reporting	How do we make it easier for people with disabilities to learn about the accessibility of web sites and web apps? If metadata outside the content itself is needed to validate a test, how is that reported?
11	Representative Sampling	How can we make conformance apply to larger / fast changing web sites and applications? How do we bridge the gap between WCAG 2's conformance model on pages, and legislators asking for conforming websites?
12	Scoping: Paths/Tasks/Workflows/Components/Views	Can SEO user intents be adapted to better define user process?		Scoping Subgroup Wrapping up User Journeys Subgroup starting in the August/September timeframe	Scoping
13	Structure and terminology	How do we support evolving technology? How do we make WCAG 3 easier for beginners?
14	Test types and terminology	How do we increase testability of guidance? How do we provide guidance that depends on certain contexts (e.g., human language, design differences)? If metadata outside the content itself is needed to validate a test, how is that reported? Make sure that tests do not rely on assumptions of the newest or any specific technology to pass.		Protocols Subgroup Wrapping Up Pre-TPAC subgroup starting
15	Third Party Content	How do we clearly denote responsibility for third party content, while encouraging its continued improvement?		Conformance Options subgroup wrapping up Pick up after TPAC
16	Transition Plan	How do we ensure a smooth and speedy transition from WCAG 2 to WCAG 3 in areas such as education, legislation, tools, etc.
17	UAAG (How and when to include this)	How do we assign responsibility for accessibility between authors, user agents, authoring tools, and assisitive technologies? Are outcomes written to span the end-to-end ecosystem with specific methods to support it (including user agents, etc)? aka: Are outcomes and methods written in such a way that when all user agents meet an outcome, the authors can pass it?
18	Conformance Reporting	Can we require conformance claims be machine readable so that any organization that makes a claim also log it in a machine readable way (APA)?
19	Scoring (See https://github.com/w3c/silver/projects/8 )
20	Measurement: Pass/Fail, Scale, Points, %	How do we test at pass/fail but still expand the coverage? How do we reduce ambiguity of interpretation? How do we better support COGA while ensuring high interrater reliability? How can we ensure WCAG 3 conformance is achievable for smaller organisations and individuals, without setting the bar too low for larger organisations? How do we ensure a high degree of inter-rater reliability? How do we ensure that with issue tolerance, we do not allow conformance with critical / blocking errors?
21	Scoring in Aggregate	How can we make conformance apply to larger / fast changing web sites and applications? How can we ensure WCAG 3 conformance is achievable for smaller organisations and individuals, without setting the bar too low for larger organisations? How can we ensure WCAG 3 better reflects the "lived experience" of people with disabilities on the web? How do we avoid requiring pages pass 100% of the tests but still ensure accessibility? How do we improve the equity of the guidance between different disability types, now and in the future, while preserving a reasonable effort bar for conformance? How do we ensure that with issue tolerance, we do not allow conformance with critical / blocking errors?		Issue Severity Subgroup starting	Issue severity
22	Addressing Gaps	How do we better support COGA while ensuring high interrater reliability? When guidance is missing, how do we stil reward/encourage accessibility? What is the role of user and usabilty testing within WCAG 3
23	Content Creation and Migration (See https://github.com/w3c/silver/projects/10)
24	Placeholder guidelines			Content Creation Exercise
25	Rework Methods			Ready to close issues
26	Reduce Outcome Ambiguity (new template, definition, measure, interrater reliability)			Ready to close issues
27	Writing Process	How do we balance the AG review process vs the need for content from a larger and more diverse set of contributors? How do we write the outcomes and all accompanying documentation in a reasonable amount of time? How do we consider/address early adoption (proactivity) at the guideline level, not only at the level of global conformance?
28	Maintainance	How do we make it easier to update non-normative content? How can we mitigate risks of a complete rewrite? How do we ensure non-normative documentation is properly maintained? How can we create a stable WCAG 3 that can still be updated and expanded on in the future? How do we keep WCAG 3 up to date as new capabilities become available in user agents and assistive technologies?	https://github.com/w3c/wcag3/discussions/18
29	Guidelines (Initial List TBD)
30	Clear Words
31		How do we better support in-browser content that is not oriented towards linear page/document/form abstractions? See https://github.com/w3c/silver/issues/265. Also discussion of html email see https://github.com/w3c/silver/issues/343
32		How will WCAG 3 integrate with VPATS/CSRs? See https://github.com/w3c/silver/issues/269
33	Organization	How will WCAG 3 be organized? General consensus to use tags but what tags are needed? POUR is requested
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100