Meeting minutes
<alastairc> Can you access this? https://
<Lisa1> next item
Lisa: Moving agenda item forward for Alastair to discuss survey from AG
<Charli> My mic is still not working with Zoom. I'm sorry.
<Lisa1> next item
<alastairc> https://
Alastair: About how AG will be working in the next charter period.
… charter ends later this year, need to determine scope for next 2 years
… By the end of this year, we want an approach of how to finish WCAG 3
… High Priority Content: new provisions for COGA and low vision, color contrast algorithm, updates in conformance model, assertions. Approach for conformance claims at bronze, silver, gold.
… Will provide suggestions to regulators on how to use WCAG 3 across all options for publication.
Lisa: What is being missed in high priority content? Question for later.
Alastair: (reviewed types of publication)
… Regarding scope- WCAG 3 is largest scope. Regulatory adoption scope is medium scope that can replace WCAG 2.2, and partial scope is smallest size scope (e.g., interim docs on way to larger scopes).
… Content can be divided up in different ways (e.g., by priority, topic, overlap with WCAG 2.2)
Lisa: Can we cover what is left out of the different scope types?
… need clarity on what is included in partial scope or regulatory adoption
Alastair: Less about details about what is/is not included. About how long each approach will take to get to milestones.
… (reviewed tradeoffs table)
Julie: As we look at tradeoffs table, would you consider adding a row about milestones for publishing the working drafts? Will some topics not get worked on for several years as they are deprioritized or will everything be included?
Alastair: We aim to publish working drafts every 6 months regardless of path.
… Content will depend on what subgroups are working on. Larger group would review every 6 months-1 year.
… For regulatory adoption scope, we'd include content we are confident will get adopted.
… (reviewed the two different partial scope options)
… 2+ partial scope has longest time to regulatory adoption. (offered perspective on the cons of partial scope approaches)
Lisa: Who else has questions?
… WCAG 3 scope from a COGA perspective is the safest. Can't get pushed off. The next safest is regulatory adoption scope which would contain some COGA guidelines but not everything.
… Other 2 paths are less clear about what is/is not included in scope.
Alastair: Agree somewhat. There is a general desire to improve COGA coverage regardless of options.
… Assertions are key because they are process-based about incremental improvements from an organization.
… the other thing is that WCAG 3 full scope isn't necessarily safe because group wants to post content sooner than 6-10 years.
<Jennie_Delisi> Then we have to add the time it takes regulators to add it into their work...
Julie: I understand choices but still confused about history of WCAG, how many years transpired from version to version, and why there is suddenly a desire to publish WCAG 3 as soon as possible.
… why the push for fastest, and regulators may wait to adopt if they know updates will occur every 2 years.
Alastair: Because it has been so difficult to update WCAG 2 it has taken a long time. Pace of technology changes make people feel like WCAG 3 is urgent.
Rain: Agree that we need to figure out how to make this happen quickly, even with incremental improvements. Technology is changing so quickly that standards are not sufficient. Is challenging because it leaves things open to interpretation.
… Doesn't work well when you are trying to do the best you can and standards do not align with technology.
… The speed of change regarding AI is happening so fast, unprecedented.
… We can have the best impact with WCAG if we can make small improvements now. People are already using AI to understand WCAG.
… Unless we publish material that AI agents can leverage, people will look for other sources of information that are not based in standards
Alastair: Survey will be published soon.
Lisa: Other questions?
<alastairc> Rain - I'd love to get your perspective on what areas need updating the most based on technology changes. It's something people say a lot, but hard to pin down...
Jennie: Having watched a large government agency wait to adopt WCAG 2.1...when you look at key elements that COGA wants implemented, what are your thoughts on different publication options?
<Rain> +1 to Jennie, it's easy to see the pros and cons of all of them
<Rain> alastairc - I'll collaborate with my colleagues to put together a short list of examples and get them to you and the other chairs
Alastair: We have structure and content for WCAG. It is difficult to change structure once established.
<Jennie_Delisi> Thank you Alastair
<julierawe> Thanks alastairc
<alastairc> Rain - thank you, that would be great.
Lisa: Let's move to actions next.
<Lisa1> next item
Lisa: tasks for Making Content Usable. We have a call on Tuesdays before the COGA call. If people can join, we assign each person a task which hopefully is easier and faster.
… does approach sound okay?
Rain: Timing will not work for me. Plan sounds good. We were aiming to cover structure proposal by the end of September.
… I can put together a prototype of structure that can be reviewed by group, then we can begin plugging content in.
Lisa: Sounds great.
Rain: We can have something to review by end of September.
Lisa: Also content that needs to be written beyond patterns.
… putting on agenda for July 21.
Jan: I should be able to attend call tomorrow.
Lisa: Moving to open issues for Content Usable. Reviewed different action items.
… moving to issue papers. New module structure is complete.
… we have online safety paper ready to go to Github.
… I thought we should prioritize safety and supported decision making.
… is less mature, but can still be published.
Julie: Conversation voice systems is close. We can resolve open issue.
Lisa: We could take open issues and put in editor's notes about them.
Lisa: Would supported decision making be ready for editor review this week/next week?
Len: Ready to show progress and share where more work is needed.
Lisa: We'll spend time next week on helping people engage with COGA.
… passing mic to Julie.
<Lisa1> next item
<julierawe> Please review the Clear Language draft for WCAG 3—you only need to look at the June tab (please ignore the other tabs for now): https://
Julie: Looking at June tab of this multi-tab document
… WCAG 3 is getting ready to publish another draft with subgroups working on different topics including clear language.
… Next version of WCAG 3 has foundational requirements, which each need testing and techniques.
<Lisa1> Foundational Requirements
<Lisa1> Summary
<Lisa1> Unambiguous numbers
<Lisa1> Unambiguous words (this currently covers non-literal language and abbreviations and acronyms, but we can split into two separate requirements)
<Lisa1> Uncommon words
<Lisa1> Unnecessary words or phrases
<Lisa1> Visual aids
Julie: Supplemental requirements don't need to be fully built out.
… Assertions assume there would be requirements about clear language. If that changes, we might approach assertions differently.
… This week, we need folks to review June tab and put in comments/questions.
… We need to finalize version for publication by this coming Monday.
… Will look for an additional time slot this week for folks to come and discuss.
Lisa: People will not be able to review everything, suggest focusing on foundational requirements (which Lisa listed above in minutes).
<Jan> @julie: If you want to take the Thursday COGA call to work on this as a group, we could use that time. I will plan on putting this on the agenda for the Internationalization Subgroup to discuss during that time.
Lisa: If we focus on foundational requirements and user needs, that might be workable.
Julie: There are 8 different subgroups in AG. Organizational structure subgroup covers things like white space which is why it is not included in our content.
… There will be many other opportunities to make adjustments in future working drafts.
<Charli> Julie, if I can review and send feedback this week, how do I get the feedback to you? I have to drop for another meeting. You can send me an email at rigglec@amazon.com. Thank you