– DRAFT –
Editing Content Usable using the V2 template

<rashmi> [Link- https://docs.google.com/document/d/1xnoNFwfjJZbfadFiU-qOW49n4-gODbd_4ff5UDyYFTM/edit?tab=t.0#heading=h.idcp8usoxm85]

<rashmi> Draft proposal Personalization of Trigger Warnings and Triggering Content [Link- https://docs.google.com/document/d/1Itskr4srybRQa7hyIqMRiOPyjFyKB9apHYWdvGRb6gE/edit?tab=t.0#heading=h.ogv44rfz22qt]

<rashmi> https://docs.google.com/document/d/1S9K4i0CAiTHCWXD0_LnpS90E2l9VC_Xs18UmOXhGzaw/edit?tab=t.0#heading=h.t3uqwwnk7ffi

<Lisa> https://docs.google.com/document/d/1_f3cJ2Wvnv7Q56QDPvGUADE_JQ7HiyOYYREDiaQpPmM/edit?tab=t.hnip6jqr9d7x#heading=h.zgit72wgd3vm

<Lisa> anyone joining the github call?

https://docs.google.com/document/d/1B1vCqlU1IF5UmqxhJAy8Khdi-kRQNPalVX8f3lCMr7w/edit?tab=t.0#heading=h.kxpt0yrvdco6

<Lisa> https://docs.google.com/document/d/1x0l8JpOxxbksibwfhvMdT11FHAT0SI3S1-_atnZi0RY/edit?tab=t.0#heading=h.8op9ructilp5

Review the structure feedback from the Internationalization Accessibility Community Group (global-inclusion): https://docs.google.com/document/d/1TeGEsD1JVf7L9bFW3_e7YTnqtmUnpTldJhD6N16ElAU/edit?tab=t.0#heading=h.p3pa6f9fr2s0

<Lisa> https://docs.google.com/document/d/19uLKmVcxYiiyDhJnUDWzmXYbXTD88EZhHn8NAoKpekY/edit?tab=t.0

<Jan> Here's the spreadsheet Frankie set up for the Internationalization Community group to provide feedback on the new structure: https://docs.google.com/spreadsheets/d/1GJxeaZwpmbSXyfrUXvS0SmXcuykCcwy9pUgD0FvNos0/edit?usp=sharing

<Lisa> pattern drafts: https://docs.google.com/document/d/19uLKmVcxYiiyDhJnUDWzmXYbXTD88EZhHn8NAoKpekY/edit?tab=t.0#heading=h.iooo9ws6eb0

<Jan> IRC Minutes from the last global-inclusion meeting: https://www.w3.org/2025/03/12-global-inclusion-minutes.html

Review Persona feedback from the Internationalization Community Group (Andy's feedback: https://docs.google.com/document/d/1YL1eK0z5pQbUkmdvJWa0pTV4JhkkWZ4dqwT7yIh7CpY/edit?tab=t.0#heading=h.iwv30wqbni6) - (Content Usable Personas - https://www.w3.org/TR/coga-usable/#persona)

Summary sentence structure

The group is discussing whether the summary should start with what to do and then describe the "why" or if the summary should start with the "why" so that the "how" details are more meaningful.

12: 18 <julierawe> Option A that starts with what to do: Use clear titles to help users understand the purpose and context of any web page they visit.

12: 19 <julierawe> Option B that starts with the why: Help users understand the purpose and context of the page by using clear titles or other research-backed mechanisms.

12: 19 <julierawe> Rain: Users told us they want us to get the point. "Just tell me what to do."

12: 20 <julierawe> Rain suggested looking lower down in the drafts and then come back to discuss the high-level summaries/

12: 26 <kirkwood> This is great!

12: 27 <julierawe> The group looked at the pattern migration tracking spreadsheet

12: 27 <julierawe> Can someone please put the url for the spreadsheet in IRC?

12: 27 <julierawe> Rain recommended starting with the first two that are ready for editorial review.

12: 28 <julierawe> Lisa: We got stuck on the first sentence.

12: 28 <julierawe> Lisa: The consensus is going toward starting with what to do. Does anyone besides me disagree and think you should start with what you're trying to achieve?

12: 29 <julierawe> Rain: In addition to what the research showed us, another practical reason for starting with "what to do" is that a lot of these are different ways of trying to achieve the same thing. So we're trying to start with something that doesn't sound like we're repeating the first part in several summaries that are talking about

different ways of achieving that goal.

12: 30 <julierawe> Lisa Does everyone agree to start with what to do?

12: 30 <julierawe> +1

12: 31 <julierawe> kirkwood A key element is that the "what to do" sentence includes describing the problem as well. It's more than 'what to do.' It's the purpose and what to do in one sentence, which comes across very well.

12: 32 <julierawe> Lisa: The consensus is to start with what to do and then say why.

Frankie proposed using written comments/questions so we can work asynchronously for the next few weeks

<Lisa> https://docs.google.com/spreadsheets/d/1AFAtja2ngUcTzHKdXNvvzx_DILw5A6dhHho5Igb520k/edit?gid=0#gid=0

<Lisa> frankins spread sheet : https://docs.google.com/spreadsheets/d/1AFAtja2ngUcTzHKdXNvvzx_DILw5A6dhHho5Igb520k/edit?gid=0#gid=0

<Lisa> page pourpose: https://docs.google.com/document/d/1x0l8JpOxxbksibwfhvMdT11FHAT0SI3S1-_atnZi0RY/edit?tab=t.0#heading=h.8op9ructilp5

<Lisa> overview document - not for wordsmithing (we think) https://docs.google.com/document/d/1GwIadQU2rmDwqPDeYX6PF7UjnD4D47vqRjvPysXNe-A/edit?tab=t.0

Group realized we had been wordsmithing in the overview document and will now focus our wordsmithing efforts in the actual draft.

The group debated whether to keep "and context" in the summary sentence or to move it lower down where we can define what is meant by "context."

The group debated the expansion from "Use clear titles" in the overview doc to "Use clear titles, supportive design elements, and organizational cues"—will the latter two elements be clear to users?

Current summary sentence: "Use clear titles, supportive design elements, and organizational cues to help users understand the purpose and context of any web page they visit."

Lisa: A title is very precise in HTML. Sometimes there isn't a title tag available such as in "views" in apps.

Lisa: Sometimes there is no title tag so you have to mention "header" in addition to title.

<Lisa> original https://www.w3.org/TR/coga-usable/#make-the-purpose-of-your-page-clear-pattern

We can solve the problem by using singular "A clear title or heading" instead of "titles and headings," which may make people think they need to look at all of the headings on a page to understand its purpose.

julierawe I will add a detailed note in the google doc explaining why we are suggesting this alternate wording.