– DRAFT –
Accessibility at the Edge (A11yEdge) Community Group Teleconference

<Mike2> Here

Glossary

janina: Not certain we need a glossary

Mike2: What is the current publication date?

janina: 12 September is the 3 year anniversary of the original kick-off TPAC meeting

Mike2: Is a glossary required?

janina: It is not unusual to have a glossary

jason: I like the idea of glossary
… use it just for acronyms

janina: We can expand acronyms with the abbr attribute

Mike2: The first instance of any acronym, mnemonic or abbreviation should be spelled out on first occurence, then a glossary is not needed
… I will catch those on my next review

Chris: In general I am a fan of glossaries, as people find them helpful. We can signal that a draft glossary is in preparation and could be included in a future revision
… is this a living document that will continue to be modified?
… then a glossary can be added in future

Lionel_Wolberger: We can make clear that we are taking comments, and are open to having a glossary in future

Announcement Text

jason: What do community group report announcements tyhpically look like?

Lionel_Wolberger: Example, https://byintention.co/web-sustainability-guidelines-report-w3c-community/

https://lists.w3.org/Archives/Public/public-wai-announce/2025JulSep/

Mike: The Accessibility at the Edge Community Group has released a report. Here's a link to its report. Comments are welcome.

Mike2: The Accessibility at the Edge Community Group has released a report. Here's a link to its report. Comments are welcome.

Lionel_Wolberger: Let's add the title

Mike2: Of course

Lionel_Wolberger: The Accessibility at the Edge Community Group has released a report, "Accessibility Capabilities: Post-Source Code and Content". Here's a link to its report [URL]. Comments are welcome in the github, a11yedge/capabilities or by sending to the list, public-a11yedge@w3.org

Chris: Some pre-release announcements may help prepare the audience

janina: We need to add a quick sentence on what the report is about and who will care about it, what we address.

Mike2: Use the first sentence
… This document examines the trade offs and benefits of dynamic accessibility remediations applied to web content in real-time to deliver accessible web experiences.

jason: I have objected to having both dynamic and real-time

Mike2: Can we remove one of those words?

jason: This document examines the trade offs and benefits of dynamic accessibility remediations applied to web content to improve or enhance accessible web experiences.

jason: Proposes:
… This document explores the trade-offs and benefits of applying dynamic accessibility remediations to web content, resulting in more accessible user experiences

Mike2: This document explores the trade-offs and benefits of applying dynamic accessibility remediations to web content.

<Lionel_Wolberger> +1

Jason: +1

janina: The report is the result of a three year effort.

The report is the result of a three year effort to understand the opportunities and road-blocks posed by such an approach.

Lionel_Wolberger: The Accessibility at the Edge Community Group has released a report, "Accessibility Capabilities: Post-Source Code and Content".

This document explores the trade-offs and benefits of applying dynamic accessibility remediations to web content.

Announcement Sentence, Draft

Lionel_Wolberger: The Accessibility at the Edge Community Group has released a report, "Accessibility Capabilities: Post-Source Code and Content".
… This document explores the trade-offs and benefits of applying dynamic accessibility remediations to web content.
… (THE WHY GOES HERE)
… Comments are welcome in the github, a11yedge/capabilities or by sending an email to the list, public-a11yedge@w3.org.