This group supports the COGA Task Force by supplying user needs and feedback.
Scope The COGA Community Group’s work will include: - Sharing challenges when using the web and other digital displays - Suggesting user needs - Helping with research - Suggesting ways to improve accessibility for the community - Reviewing COGA’s drafts - Outreach and collecting feedback from the community - Helping with policy and the business cases for COGA guidance - Having open meetings to discuss these points Open meetings may be live video conferences or in other discussion formats
Participation
You do not need to be an expert in all topics related to cognitive accessibility to join the community group. The COGA Community Group will work in smaller groups for specific subjects, giving you the opportunity to participate on the topics you choose.
The COGA Community Group will also work together on some topics, brainstorming and building a community dedicated to improved access for all.
However, the community group will specifically benefit from including: - people with learning and cognitive disabilities, people with mental health challenges, - caregivers, therapists and people who work with people with learning, cognitive challenges and in mental health, - researchers, developers, quality assurance professionals, and user interface experts, industry, looking to share and support ideas, and policy makers.
Additional details of participation - Joining the COGA Community Group does not involve joining the COGA Task Force. - If you would prefer to join this group anonymously, please send an email to ran@w3.org. - The community group will not publish specifications, but may make suggestions to the COGA taskforce. - For more information about community groups, please visit Community and Business Groups Frequently Asked Questions. - Short link to this document: bit.ly/coga-community
Group's public email, repo and wiki activity over time
Note: Community Groups are proposed and run by the community. Although W3C hosts these
conversations, the groups do not necessarily represent the views of the W3C Membership or staff.
Chairs, when logged in, may publish draft and final reports. Please see report requirements.
As time zones can change (e.g. daylight savings), please feel free to use this link to place a calendar hold. This calendar hold should automatically adjust to the correct time for your timezone. Please note that this will not have the zoom link in the calendar hold. The zoom link is posted in the community slack channel.
If you would like another timezone translated into local time, please let Aditya Bikkani, Ciara (Kiki) Salmon or Jamie Knight know.
Discuss pending matters from previous meeting (50 minutes)
[Shruti] Reviewing draft disabling patterns (e.g. social media app notifications and likes that cause mental health impacts) with goal of passing it along to COGA Task Force
[Lea] Regarding Content Usable, are there any best practices for influencing adoption of it on newer dev teams looking to improve accessibility on mobile apps?
If Time
[Kiki/General Team] Reviewing dark pattern doc
[Anja] The complexity of language in design guidelines: some words feel overused, some words could maybe be replaced by clearer words.
Closing questions, adding any items to next month agenda and next steps (5 minutes)
As time zones can change (e.g. daylight savings), please feel free to use this link to place a calendar hold. This calendar hold should automatically adjust to the correct time for your timezone. Please note that this will not have the zoom link in the calendar hold. The zoom link is posted in the community slack channel.
If you would like another timezone translated into local time, please let Aditya Bikkani, Ciara (Kiki) Salmon or Jamie Knight know.
Discuss pending matters from previous meeting (50 minutes)
[Kiki] Review any AIs from last month’s discussion on Finish testing guide and reading tools.
[Lea] regarding Content Usable, are there any best practices for influencing adoption of it on newer dev teams looking to improve accessibility on mobile apps?
[Anja] Research how do you test a layout to see if it is simple? There is view hierarchy that AI can now build into that, so is it now testable.
If Time
[Anja] the complexity of language in design guidelines: some words feel overused, some words could maybe be replaced by clearer words.
Closing questions, adding any items to next month agenda and next steps (5 minutes)
As time zones can change (e.g. daylight savings), please feel free to use this link to place a calendar hold. This calendar hold should automatically adjust to the correct time for your timezone. Please note that this will not have the zoom link in the calendar hold. The zoom link is posted in the community slack channel.
If you would like another timezone translated into local time, please let Aditya Bikkani, Ciara (Kiki) Salmon or Jamie Knight know.
[Anja] Reviewing current readability tooling and seeing if COGA has it included. If it is not included, is there research that supports these approaches that we could pass along to the Task force?
If Time
[Lea] regarding Content Usable, are there any best practices for influencing adoption of it on newer dev teams looking to improve accessibility on mobile apps?
[Anja] Research how do you test a layout to see if it is simple? There is view hierarchy that AI can now build into that, so is it now testable.
Closing questions, adding any items to next month agenda and next steps (5 minutes)
As time zones can change (e.g. daylight savings), please feel free to use this link to place a calendar hold. This calendar hold should automatically adjust to the correct time for your timezone. Please note that this will not have the zoom link in the calendar hold. The zoom link is posted in the community slack channel.
If you would like another timezone translated into local time, please let Aditya Bikkani, Ciara (Kiki) Salmon or Jamie Knight know.
We do not want to require you to sign in to fill out this form, which is required if we give the option to upload a file in this form. If you would like to send a screenshot, video, or audio please send it to cogacommunity@googlegroups.com
[Kiki] WCAG three is looking for people to give cognitive and learning disability input. Gauging to see if any individual(s) in the community group want to join a subgroup.
2-4 hours a week for a couple of months
Closing questions, adding any items to next month agenda and next steps (5 minutes)
Discuss pending matters from previous meeting (50 minutes)
[Jamie] Consensus voting
[Kiki] Can we share the examples to the TF that we have in the Google Drive
The task force is updating the document and would like to understand if they are covering issues that affect us and our community. As we have not collected information more broadly with the Google form, I wanted to see if we are okay with sending examples we have collected together over the last year.
[Kiki] Moved questions to google form. Approval from group?
