Re: COGA structure v2 recommendations review

Wow, Fantastic work!
some thoughts comments:


   1. In the "what to do" section of the pattern. I loved the culture /
   international bullet point, as well as the semantics/ personalization .
   Should we make the last two bullet points reserved for these issues
   across patterns, to be filled in when they occur?
   2. To me a quick start guide is something along the lines of  *Getting
   started
   <https://www.w3.org/WAI/GL/task-forces/coga/wiki/Getting_started> or **“ten
   tips”
   <https://www.w3.org/WAI/GL/task-forces/coga/wiki/%E2%80%9Cten_tips%E2%80%9D>*.
   Is "how to use this document" a better title or am I just used to that
   phrase?
   3. Is it too long? Should we be moving sections out the document such as
   the  persona (or an appendix?)
   4. Again , for discussion - when the pattern is open isthe @how it helps@
   section too long? Do users get lost in this subsection? Should the how it
   helps be a link like the* understanding *sections in wcag
   5. Also in the how it helps section:  i think the examples inline were
   very helpful to the understanding, especially as you did not need to click
   further.

All the best
Lisa



On Tue, Dec 3, 2024 at 7:01 PM Rain Michaels <rainb@google.com> wrote:

> Hello COGA Task Force,
>
> At last, about a week later than I'd hoped, here are the materials for you
> to review the recommendations for the structure of v2 of Making Content
> Usable:
>
>    - The deck with the structure v2 design recommendations
>    <https://docs.google.com/presentation/d/1aOyK6N5coRlT1ZA7SZNp4w4sP7ynxBNNT2HBUt4NCOQ/edit?usp=sharing>
>    - A video of me going through the deck and explaining everything
>    <https://drive.google.com/file/d/13CC6jWp6q2Cr98HDSZ5jXggVT3FXUpGJ/view?usp=drive_link> (47
>    minutes)
>
> We have time planned for our meeting on Monday, December 9th, for
> discussion and live feedback. Please review before then if possible as
> there won't be time to both review and get feedback in one meeting.
>
> Feel free to also leave feedback on the deck itself at your own pace.
>
> I'll be going over this with W3C staff as well, as some of the
> recommendations may be more difficult to implement than others. Where that
> happens, we'll find alternatives if needed.
>
> I've also shared this with the community group, so you may see comments or
> questions from them in the deck, as well.
>
> Let me know if you have any questions for me.
>
> Warmly,
> Rain
>
>
> [image: Google logo written with braille dots and ASL hands]
> Rain Breaw Michaels
> Design Lead, Accessibility UX
> rainb@google.com
>
>