Meeting minutes
V2 interactive control pattern: What-to-do info about target size
We discussed changing the guidance to mention "When possible, use WCAG 2's larger target size."
Background
We've been in the weeds reformatting a few V2 patterns.
With Jen new to our subgroup, we'll use this week to step back and revisit Rain's December 2024 recommendations.
One high-level goal is to gather questions and help make sure we aren't missing any work that has already been done.
V2 group refresher: Revisiting Rain's December 2024 recommendations
julierawe gave a quick overview of the December 2024 deck
V2 user needs: Seeking clarification on location and format of user needs
julierawe looked at slide 25, which shows the "How it helps" section for a specific pattern. "How it helps" includes a few user stories. https://
julierawe looked at slide 28, with details on "Know your users." It includes user stories, not a long list of user needs. https://
<Jennifer> +1 to Len's comment regarding focusing on the guidance at hand.
LenB The goal was to keep people focused, not to sure every single user need.
LenB One possibility would be to link out to a list of user needs.
LenB Do these lists of user needs exist?
LenB And would we have to continually update that list?
julierawe Should we include a review question asking if people miss having a list of user needs? Do they like the way we present user needs only in user stories.
Jennifer suggest we could tee up the user stories by framing that this is not an exhaustive list.
Jennifer At Google, people want to hear the impact to user stories. We intentionally avoid trying to have a comprehensive list of all possible needs because of intersectionality. It would be very challenging to make it truly comprehensive.
<LenB> Goal was to keep people focused on the scope of the document. If we added every user need in this document we'd have a big 'intermission' in the content scope for that list.
<LenB> If we add a 'complete' list of user needs we'd need to create a W3C list (that includes COGA, Internationalization, etc). It could then be soo large it becomes a point in the document that people leave it.
<LenB> Another issue was that site authors know their audience better than we do. Some of our guidance may not apply. For example, passive voice is a must for certain industries while others can be a hindrance for users. We'd have a difficult time to selecting the users needs that match the reader's context.
https://
<LenB> +1
<Jennifer> +1
Stick with Rain's proposal to only show user stories, not long bulleted lists of user needs? +1 if you agree
<julierawe> +1
kirkwood +1
Questions about next steps in Rain's December 2024 deck
Did Rain's team meet with Kevin, Shawn, and Tamsin to see if any of the proposed design template is not possible for us to do?
Did the COGA community group provide feedback on December 2024 deck?
ACTION: item: Jennifer to ask Rain today
Still-to-do list in December 2024 deck: Wayfinding icons, storyboards, and other items
LenB we started looking at wayfinding icons but got waylaid. Ask Rain if got reassigned?
LenB This was more than "previous," next," etc. We were looking at icons for "Developer," "Designer," etc.
julierawe Some of these icons we can save for later. ]
lenB We can prioritize what we need first.
ACTION: item: Jennifer to ask Rain if any progress was made on wayfinding icons
ACTION: item: Jennifer to ask Rain about everything on the still-to-do slide
This annotated V2 doc had the wrong design template: https://
But Rain provided the updated link and also some key questions
Those questions are different from the ones we discussed today and that Jennifer will seek answers to.