COGA Issue Management

	A	B	C	D	E	F	G	H
1	Description	Issue#	Status	Lead	Next Action	Part of Document	Parent Issue	Draft Response

2	Consider whether to use Do/Don't instead of Use/Avoid.	116	ready to close	lisa	*BEFORE Closing, we need to make language consistent and roll parts 2a and 2b into Git. Then we can reference that PR when closing. Discussed at https://www.w3.org/2020/11/19-coga-minutes.html meeting. Resolution: Rewrite the examples by adding a short introductory sentence that meets the verbal pattern. Review all examples to see if any obvious ones are missing. Been reworked. Need response after reveiwing revised content.	Patterns		Draft Response
3	Test with real users! should be pulled out as it is NOT a Objective and applies to ALL the objectives listed above it.	118	ready to close	Justine	Justine added "key topics" to first sentence of summary and created draft full request on Github. Response also submitted to the issue.	Summary		Thank you for your feedback. We've added "key topics" to the first sentence of the summary.
4	Consider reworking the headings in Summary and reordering them Clear structure, clear design, clear content	118	Ready to close	Justine	Based on email discussion with Rachael January 26, 2021 this portion of issue 118 should be closed.	Headings, Summary		Adding the term object permanence into the document to make it easier for those looking for the term to find the appropriate user stories and patterns
5	consider changing the content to put user need 1st in all cases	118	ready to close	Justine	as above	User Needs		Adding the term into the glossary if the term becomes added into the document
6	Remove or move Test with Real Users	118	ready to close	Justine	Justine replied on Github on 2/18			Thank you for your feedback. After discussion with the editorial group, we have decided to keep the existing heading structure as pursuing the action would require a mahor change to the document structure. We are updating the objectives.
7	Persona Diversity	131	In process	Rachael	EA and Rachael Addressing; Discussion Needed of 131, 135, 161, 162	Personas
8	Include sensitivity to sound and complex patterns in 3.6 Help Users to Maintain Focus	132	ready to tag for next version, respond and close	Lisa	Also see 137, 198. I added some claifications to 4.6.1.1 and 4.6.3.2 Description we should also tag for v2 and add user need in next version. sent to the list aproved . https://lists.w3.org/Archives/Public/public-cognitive-a11y-tf/2021Feb/0021.html	Patterns		Thank you for your comments! We have added content to 4.6.3.2 Avoid Too Much Content and 4.6.1.1 to emphasis this. We will also revisit this issue in the next version. Could you send us any reaserch you have on the topic? Any and all help is appriciated.
9	Persona Diversity	135	In process	Rachael	EA and Rachael Addressing; Discussion Needed of 131, 135, 161, 162	Personas
10	Better incorporate the use of spatial representations	136	Discuss	rachael	**Have we written back to UMD? If yes, we can close. rachael wrote draft in github. Lisa agrees. I think we can close	Patterns
11	Review visual processing for inclusion in Content UsableReview use of judgemental terms	137	ready to tag for next version, respond and close	Lisa	Also see 137, 198. I added some claifications to 4.6.1.1 and 4.6.3.2 Description we should also tag for v2 and add user need in next version. aproved https://lists.w3.org/Archives/Public/public-cognitive-a11y-tf/2021Feb/0021.html	Patterns		Thank you for your comments! We have added content to 4.6.3.2 Avoid Too Much Content and 4.6.1.1 to emphasis this. We will also revisit this issue in the next version. Could you send us any reaserch you have on the topic? Any and all help is appriciated.
12	Test with real users" actually applies to all the objectives and is not really one itself.	138	Ready to close	Justine	Justine replied on Github on 2/18	Summary		Thank you for your feedback. We have modified the first sentence of the summary to address these comments.
13	Compare Objective 3 with summary. Make the division consistent	138	Ready to close	Justine	See row 12 above for action item	Summary
14	Use of Person First Language for Autism	139	in to do list	Justine	discusion from https://www.linkedin.com/feed/update/urn:li:activity:6755550272950554624/Justine to update references to autism to use identity-first language https://autisticadvocacy.org/about-asan/identity-first-language/ Issue closed on Github on 2/17	Document		Thank you for your suggestion. We will update the references to use identity-first language.
15	Math abbreviation	141	Ready to close	Justine	Design guide updated and created draft pull request on Github on 2/18. Issue was closed on Github at the beginning of February.	Document		Adding the term into a Use Case/Persona
16	"Object permanence" and "Motor automaticity"	143	edit responce and close		Double checked on list, make changes and close. Jennie to send draft to list, group to discuss aproved on the list. also revisit for next draft https://lists.w3.org/Archives/Public/public-cognitive-a11y-tf/2021Jan/0048.html	Document		Draft sent to list after meeting on 1/19/21
17	Easy to Read replacement suggestion	144	disccustion on list	Lisa	add easy to understand lang to the glossary	Document		standard text 1. We have clarified how we are using the term.
18	Define Cognitive accessibilty	145	respond and close	Lisa	1.we do not use the term Cognitive accessibilty. 2. Mention other groups that benefit from it. - good idea. text sent to list for aproval. Approved	Document		Thank you for your suggestions. We do not use the term "cognative accessibilty " as such but have have added the term accessibility to the title of the background section. We have also added to the abstract and introduction clarificaltions of who it helps. Thanks again for your review!
19	Updates to objectives	149	In process	Rachael	Review Betsy's work and see if that addresses these concerns	Objective Summaries
20	More pattern examples	153	ready to close		*After Lisa has merged all the patterns in, ask Steve to review and if satisfied to close the issue. from steve Check in with Steve and Lisa on status; identify patterns missing examples, sign people up for them	Patterns
21	Additions to 3.3.2 User Story Visual Presentation	157	draft responce	Lisa	covered in the genral responces to issues .dont think she is used to user stories. confirm and nice responce	User Stories		Thanks for your comments. Most of these are covered in different user needs. We have tried to divide these issues in different user needs (user perspective) so that they map to different patterns from the designer perspective. We can consider changing the structure in the next version . Thanks again for the detailed review. The task force
22	Suggested edits to 3.4.1 User Story: Assistance and support	158	dconfirm with other editor	Lisa	dont think she is used to user stories. confirm and nice responce	User Stories		as above
23	Internatonlazation Suggested content for 4.4.2	159	sent to list	Lisa	agrred. slight change and added to googledoc. editorial	Patterns		standard text 1 with email text from 18/2
24	reference to language tags for Clear, Unambiguous Text	160	sent to list	Lisa	added to google docNeed an OK for the addition and reference	Patterns		standard text 1 with email text from 18/2
25	Persona Diversity	161	In process	Rachael	EA and Rachael Addressing; Discussion Needed of 131, 135, 161, 162	Personas		4.3.1 Pattern: Make it Easy to Identify the Most Important Tasks and Features of the Site - "Placing the tasks/features towards the top of the page so the user does not have to scroll to see them,
26	Persona Diversity - Addition of non-native speaker persona	162	In process	Rachael** (Internationalization Group)	Discussion Needed of 131, 135, 161, 162 (Draft Response for review; out of scope, add to business considerations)	Personas		Placing the tasks/features toward the top of the content so assistive technology finds them quickly"
27	Lots of stuff - see subtopics	163	DRAFT responce sent to the list and aproved	Lisa	sent to the list 18/02. deadline to object 21/2
28	Add reference to other disabilities and barriers to physical access	163.1	draft respnce	Lisa	Lisa to draft a sentence to add to the Summary and send to the list.	Introduction		we cant due to complicated with scope of coga
29	Add contrast to 4.4.11.2	163.10	done	Lisa	added "use strong color contrasts	Document		standard text 1: added bullet "use strong color contrast"
30	Required fields in 4.5.4.2	163.11	draft respnce	Lisa	we feel this is covered via aria - wcag, and implied in error suggestions	Document
31	Add features to settings - 4.6.1.4	163.12	draft respnce	Lisa	we feel this would nakemore busy screens without an advatge. more reserch would be needed to include	Document
32	Move paragraphs to Introduction - 4.7	163.13	draft respnce	Lisa	The introduction is a consencis text between working groups so we are not adding to it, easily	Document
33	Adjustments to login	163.14	draft respnce	Lisa	we propose to not rely on it, which meens to provide an altervie. we also do not want to conflict with wcag 2.2	Document
34	Missing heading	163.15	done	Lisa	We have added the heading to section 4.7.2. Thank you for the feedback.	Document
35	Add telephone companies to examples - 4.7.4.3	163.16	draft respnce	Lisa	we have tried to keep this inscope for the web	Document
36	Fix typo - 4.7.5.3	163.17	done	Lisa	newly added, an easy fix	Document		check in final version
37	Clarify terminology - objective 8	163.18	draft respnce	Lisa	Thank yu for the information about arrosac, we are indeed awear of it	Document
38	Fix typo - 4.9.3.2	163.19	draft respnce	Lisa	we think this is fixed	Document
39	Use consistent terminology when referring to cognitive disabilities	163.2	done	Lisa	Standard text response needed	Document		standsard text 1 - or add sentce that we have edited the document to make the terms more constent were aroppriate
40	Add reminder to not test abilities - 5.5.4.1	163.20	draft respnce	Lisa	thanks, this is disscussed but we are leaving it as is	Document
41	Add "read aloud" to the text - 5.5.4.1	163.21	draft respnce	Lisa	This may not work well for everyone. we need more testing	Document
42	Relate methods of communication to user needs	163.3	sent to list	Lisa	J+L reviewed , we have been asked to reduce the size of document. and the need doesnt seen so urgent	Document
43	Add "in easy to understand language" to 3.7.5	163.4	on list	Lisa	newly added	Document
44	Add more detail to 4.3.2.3	163.5	on list	Lisa	newly added	Document
45	Avoid synonyms and abbreviations - 4.4.1.2	163.6	on list	Lisa	newly added	Document
46	Consistent referral to plain language	163.7	on list	Lisa	newly added	Document
47	Confusing examples in 4.4.3.4	163.8	draft responce	Lisa	example added	Document
48	Add more detail to 4.4.9.2	163.9	draft responce	Lisa	hestetent to add lenghth to add emhasis	Document
49	Additional examples to 3.5.1 User Story: Distractions	164	Ready to close	Justine	Responded in Github on 2/18	User Stories		Thank you for your suggestions. We have removed the word "weak" from the text. Unfortunately, the group agreed to avoid adding the examples to the bulleted list.
50	Suggested edits for 3.6.3 User Story: Voice Menus	165	Ready to close	Justine	Responded in Github on 2/18	User Stories		Thank you for your suggestions. We have adjusted the language to avoid the use of judgmental terms. After some discussion, the group felt that the other suggestions were out of scope.
51	Suggested changes for Pattern 4.2.5 Clearly Identify Controls and Their Use	167	closed	steve	Steve to review status. Also see 154
52	Addition to 3.7.5 User Story: Task Management	168	Ready to close	Justine	Responded in Github on 2/17			Thank you for your suggestion. Addressing the task order is addressed in a different pattern.
53	The concept that “I need alternatives to spoken and written language such as icons, symbols or pictures” is important and could be included in many other user story examples.	169	Response needed	Lisa	Lisa to send a query to the list			Thank you for your suggestion. In order to keep the length of the document to a minimum, we will avoid making this change in order to avoid repetition throughout the document.
54	4.2. Objective 1: Help Users Understand What Things are and How to Use Them	170	Ready to close	Justine	Added to "to do" list. Justine responded in Github on 2/18	Objectives		Thank you for your helpful suggestions. We have made changes to the document. Note that we do not feel text-to-speech can aid users who have difficulty read (regarding reading age). Our focus is on understandable content. Regarding alt text, we are trying not to overlap with WCAG.
55	add another example to 4.3.3. Pattern: Use a Clear and Understandable Page Structure: Expandable UI elements such as “Read more” link that only shows more content if the user opts in"	171	edit the responce and close	Lisa	lisa will write option to the list	Pattern		Thanks for your comment. We hope to research this suggestion for the next version.
56	Four suggested changes to 4.4 Objective 3: Use Clear and Understandable Content	172	Ready to close	Justine	Responded in Github on 2/17	Pattern		Thank you for your comments. We will avoid making these changes due to potential impact on other types of disabilities as well as other signifiant impacts.
57	Three suggested changes to 4.5. Objective 4: Help Users Avoid Mistakes or Correct Them	173	Ready to close	Justine	Responded in Github on 2/17	Pattern		Thank you for your feedback. Regarding #1, we will avoid making this change in this version of Content Usable but will consider the feedback for the next version. We are not able to add links to external resources regarding #2. Number 3 is addressed elsewhere in the document.
58	add "attention" to wayfinding list in 4.8.6 Pattern	174	Ready to close	Justine	Google doc updated. Responded in Github on 2/18	Pattern		Thank you for your suggestion. We have added "attention" to the list in 4.8.6.
59	Two suggested changes to 5.4.1 Differences from Usability Testing with the General Population	175	Ready to close	Justine	Responded in Github on 2/18	Usability Testing		Thank you for your helpful suggestions. We have addressed these considerations elsewhere in Content Usable.
60	Anna (dyslexia) persona and scenarios changes	177	In process	Rachael	EA Addressing	Personas
61	Suggested changes to Jonathan (dyscalculia) persona and scenarios	179	In process	Rachael	EA Addressing	Personas
62	Icon work	180	In process		After justine finishes and icons are aproved, add throughout document	Document
63	Plain language changes - passive voice	182	Editorial review	Rachael	Rachael to make change. *Discuss on editor's call.	Document
64	Plain Language	186	In process		John Rochford reviewing
65	What does a "a symbol user" mean?	190	Ready to close	Justine	Responded in Github on 2/18			standard text 1
66	Restructuring changes	193	draft to facilitators for review	Steve	Decision to reject. Steve offered to draft response. Lisa to follow up with Steve.
67	Suggested changes to introduction	195	Ready to close	Justine	Response submitted in Github 3/25.	Introduction
68	Incorporate need for human assistance (Rainbow Model)	197	Needs Response	Rachael	Out of scope. Very important. Goal of design to work independently. Help has tiered. Not about designing services.			4.3.4 Pattern: Ensure the Most Important Things on the Page are Easy to Find - "Make key content visually stand out and be visible to users without needing to scroll the page or hover over content."
69	A number of editorial suggestions	197	responce needed	lisa	rachael will add the tolist , lisa writes responce need to add to the document done in pieces at https://docs.google.com/document/d/1fc7TI8V6dNgFrD6wzGR8CjbbtO7Az0U-zYylrRSy8QQ/edit#;lis
70	Amanda Lazar comments	198		Rachael	Responses created. Rachael to go through and see status
71	Heading repetition	221	Discuss	Justine	Justine emailed editorial group for initial consultation on 1/28. Justine to check with Rachael to confirm what response should be. Previously discussed in COGA.	Patterns
72	Check that glossary terms work as hyperlinked text	227	Ready to close	Justine	Responded in Giithub on 2/18	Glossary		startd tec=xt 1
73	COGA icon review suggestions	231	Ready to close	Justine	Responded in Github on 2/18	Summary/Icons		Thank you for the helpful suggestions! We are in the process up updating the icons and the task will be completed before publishing.
74	replace verbal with langauge	232	Ready to close	lisa	added to todo list	standard text 1		stardard text 1
75	Avoid acronyms and abbreviations - 4.4.1	233	Ready to close	Justine	Justine responded in Github on 2/18. Issue is tied to 163.	Document		Thank you for your suggestion. We have adjusted the language to address this topic.
76	Font usage	237	closed	Lisa	Sent response to list. Review at COGA.	Document		Thank you for bringing this up. We have added this in
77	Use of numbers - 4.4.13	238	Discuss editorial	Lisa	added in comments to the google doc change the name 4.7.5 Pattern: Do Not Rely on Users Memorizing Information - to cover cuculations and add their example	Document		Thatk you for your sugestion. We have included it in 4.7.5 and added your example!
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100