Meeting minutes
Overview of new structure for COGA subgroups
<kirkwood> new tructure: research subgroup & guidance subgroup
Research subgroup would focus on issues papers, mental health, and other topics that are new to COGA
Guidance subgroup would focus on next version of Making Content Usable, helping draft and providing feedback on drafts of WCAG 3, and Internationalization
Rain said the structure makes sense and likes the idea of having more intentional planning for the subgroupos
kirkwood asked how are we determining our priorities for creating new issues papers and what to include in our guidance
kirkwood How do we make sure we've got coverage of key issues, such as age-ing? How do we make sure there are no gaps?
kirkwood It's such a big umbrella. How do we ensure we're doing research in the right areas? Is there something we need before research to determine priority areas
Rain Right now I don't think we have a process or at least not a process that everyone is clear on
julierawe I am hopeful that the research subgroup will develop a clearer process for how to identify gaps to research, which issue papers to prioritize, and how those papers get drafted and reviewed
julierawe noted that Making Content Usable and WCAG 3 coordination are both massive workstreams and we will have to plan carefully to avoid overwhelming COGA members
Update on Making Content Usable
The plan is to get 5 or so patterns into the new format
Rain is also going to work on the coding. This means creating a branch in github so people can start seeing what the content will look like in the new format.
It will be in HTML, it will be interactable. We can see what it looks like in an actual web page rather than a google doc.
Rain only needs one pattern to start out with. Julie and Lisa will share that pattern with you soon.
Here is the migration tracker: https://
Link to page purpose draft: https://
<kirkwood> +1
Discussed with Rain how her research strongly supports making user needs an H3 section rather than an H2 section.
Rain plans to have the coding ready by early October
Rain will make a guide to help people replicate this work
Julie described a three-part process: (1) Julie and Lisa finish editing a pattern, (2) the task force reviews and has concensus vote, (3) Rain codes in github
Rain and John discussed how to handle changes from the task force
Julie asked whether/how internationalization will be involved in this review process
Julie echoed Rain's comment it doesn't need to be absolutely perfect. The main goal is to get something that is good enough to get feedback on the larger W3C community. We can fine-tune later.
Update on WCAG 3 coordination
A new working draft will be published soon. It does not include user needs, tests, and techniques.
There is a lot of opportunity for COGA to review user needs, tests, and techniques -- the question is when.
It's going to involve a lot of mapping out of the work
kirkwood The more you can map out the work, the more people are likely to participate because it's so overwhelming.
This work will be ongoing. We'll map out what we can do before the December working draft is published.
We'll plan to get updates from COGA members who are active in the different subgroups as well as looking at the actual drafts.
WCAG 3 trade-off discussion
https://
I asked Rachael to come to Monday's task force meeting to help us understand the trade-offs.
Julie is concerned about Detlev's comment.
Rain thinks we are moving too slowly.
Rain said we came up with requirements for Lists and requirements for Harm from Motion. Why can't we go ahead and publish those?
Rain is suggesting we publish an incomplete WCAG 3 so we can start putting stuff out there.
Rain said holding on to an old structure doesn't make sense.
Rain said we have a lot figured out even if we don't know how it's scored yet.
kirkwood I think the scoring is impossible. Scoring means you have to prioritize.