Updated Draft: Process for Creating Silver Content (New and Migrated WCAG)

	A	B	C	D	E
1	Step	Steps To Create Silver Guidance	Where it Goes in Silver Template	Using WCAG 2.0/2.1 as a Resource	Example
2	1	User Needs	Remember that User Needs are always the central touchpoint.
3	1a	Functional Need Assessment: List each user group, and individual barrier (based on co-design with PWD for new guidelines, or, in the case of migrating guidelines, using personas as if self-advocate or other advocate).	Rough Draft of User Needs Extended Description.
4	1b	Identify the common need across these multiple user groups in one sentence. List unique needs of specific user groups as bullet points. Identify and list conflicts that may exist within and between user groups as additional bullet points.	Rough Draft: First part of User Needs Extended Description. (One sentence about common need with additional bullet points)
5	1c	Are there terms in the sentence about common user need that need specific examples or description to explain context? This does not replace eliminating words nor is it a glossary.	Rough Draft: Second part of User Needs Extended Description (keep to one sentence if possible).
6	1d	Write the crux of the solution to meet that need. That is a minimal concept.	Rough Draft: Third part of the User Needs Extended Description. Keep to one sentence if possible.	Understanding (from existing Intent section)
7	1e	Consider the perspective of a (specific) beginner user. Re-draft the User Needs Extended Description paragraph so your beginner user will have a functional understanding of the paragraph.	Copy the refined paragraph and bullets into Silver Content Template "Get Started" tab under "Why?"
8	1f	Refine list from Step 1a (functional needs assessment) in plain language.	Copy the refined paragraph and bullets into Silver Content Template "Get Started" tab under "Who?"
9	1g	Write a one sentence plain language summary line of the user needs paragraph. This becomes the short description of User Need.	Copy this to the Silver Content Template "Get Started" tab, as the first sentence under "Summary".	Guidelines and shorter SC
10	2	Tests of User Needs	How can we test to ensure we've met the user need?
11	2a	Are there current Techniques or ACT Rules - link to them.	Testing Tab also Testing section of Methods	Tests (from existing Techniques section), including Procedure and Expected Results
12	2b	Map current Techniques & ACT Rules to the User Needs Extended Description (Step 1 complete): i - Identify where a given rule or technique addresses the user need. ii - Which orphan tests don’t map to a user need? Should the user need be expanded to address this? Or should the test be dropped? iii - Which user needs are not met by the current tests? iv - Are there any reasons why this gap exists (e.g. emerging area, or difficult user need to address)? Are there barriers to address this gap?	Propose: also be copied to the Discussion document accompanying each Guideline Draft
13	2c	Looking at gaps where there are no existing tests to address a user need listed in User Needs Extended Description (Step 1 Complete): i - what are the possible tests that could be written? ii - Are there other known suggested tests? (link to suggestion) iii - Which of the new test types may be helpful in creating a new test: scale, rubric, task completion or usability of any kind? Why one type of test over the other? iv - Write a possible test, indicating which type(s) of test you chose. v - How do we ensure that tests are for testing “content”/interaction, versus testing the tester?
14	2d	Testing to Test/Audit Tab	Propose: Copy list of links to tests to the Test Audit tab. There may be too many and it may be better to link to the Method/Technique
15	3	Methods that Map to User Needs	How can we create methods that help users meet their needs?
16	3a	Are there current Methods or Techniques? - link to them.		Methods or Techniques - Also draw from UAAG/ATAG and related materials
17	3b	Map current methods to the Step 1 Extended Description: i - Identifying where given method addresses the user need. ii - Which orphan methods don’t map to a user need? Should the user need be expanded to address this? Or should the method be dropped? iii - Which user needs are not met by the current methods? Are there any reasons why this gap exists (e.g. emerging area, or difficult user need to address)? Are there barriers to address this gap?
18	3c	Looking at gaps where there are no existing methods to address a user need listed in Step 1: i - what are the possible methods that could be written? ii - Are there other known suggested methods? (link to suggestion) iii - Write a possible method, indicating which user need you are addressing.
19	3b replace	If there is an existing Technique you identified under Tests, link to it. If there is a gap, sketch out the technical solution that is specific for a platform, language, or technology.
20	3d	Methods to Develop and Design Tab	How will this information inform the Develop and Design tabs?
21	4	Evaluate Methods	How can we evaluate whether our method helped us meet the user need?
22	4a	Map current or proposed methods to existing tests.
23	4b	Where methods don’t map to an existing test at all, write a test for that method to evaluate how well it meets the user need.
24	4c	Where a test for that method exists, consider whether this is the best test: Is there a better quality test to measure how well the method meets the user need (compared to other methods), or does the method require additional tests? If so, write the new tests.
25	4d	Consider what potential new problems may arise from the method, or if the method may present new barriers to user needs? Is there a test to measure this? If possible, write this test. (e.g. high contrast, emerging tech - VR, IoT, etc.) - flag to customization/personalization (where conflicts arise)
26	5	Write the Guideline Explainer	Bringing it all together
27	5a	Write the Get Started Tab	Did we migrate content from Step 1 User Needs to Complete this tab? What is missing?
28	5b	Write the Plan Tab	Does our guideline, method and test promote use early and often, including by people without extended knowledge of digital accessibility? (plan tab)
29	5c	Write the Develop Tab	Did we migrate content from Methods to the Develop tab? What is missing?
30	5d	Write the Design Tab	Did we migrate content from Methods to the Design tab? What is missing? What other design considerations are important?
31	5e	Write the Test/Audit Tab	Did we migrate content from Step 2 tests and Step 4 Evaluate into the Test/Audit tab? What is missing?
32
33
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