W3C

– DRAFT –
Accessibility at the Edge Community Group Teleconference

10 July 2024

Attendees

Present
Bev, Chris, janina, Lionel_Wolberger
Regrets
Jason, Mike
Chair
Janina
Scribe
Lionel_Wolberger

Meeting minutes

<janina> scirbe+

Welcome & Introductions (As needed)

<BC> Bev C is here

<janina> Lionel_Wolberger: Notes we're in summer when vacations fall

<janina> Lionel_Wolberger: Proposing next telecon is 31 July

<BC> July 31 is good

<BC> Bev C is present+

<janina> present_

<janina> +1

RESOLUTION: Next telecon will be 31 July

Further Capabilities Editing--Continuing H2-H3 review

https://a11yedge.github.io/capabilities/

janina: Numbers and strings of digits: Phone numbers are the best example, they are read as numbers
… e.g. 800-5555555 might be read as eight hundred, five million 5 hundred 55 thousand, 5 hundred and 55.
… edge technology could somehow cause such a number to be more intelligible

janina: There is some support in SSML

Lionel_Wolberger: This is aspirational, as it would be very difficult to implement today

Bev: +1

Acronym expansion

Lionel_Wolberger: This is very similar to 5.11.1 Dictionary on Demand

janina: It's more than a dictionary lookup, take for example CD
… compact disk, certifice of deposit? Candela?
… AI could read the adjacent text and context and provide the fully spelled out name

Lionel_Wolberger: Same problem as the above digits, I do not see how the page would encode this information for the screen reader to pick up

Lionel_Wolberger: This is aspirational

Post-source as a descriptive term for 'accessibility at the edge'

Lionel_Wolberger: I find the term "post source" does work well, once context is provided.

janina: I propose incorporating it in a descriptive section
… e.g., the introduction

<BC> +1 Research related features

Looking at WCAG to find what we may have missed

Link, https://www.w3.org/TR/WCAG22/#text-alternatives

janina: WCAG 2.2 1.1.1, Non-text content, is an Edge capability thanks to AI

Lionel_Wolberger: We have it in the capabilities doc under 3.1.1 Image Alternative Text Provisioning

janina: The mention in capabilities could cross-link to WCAGhttps://www.w3.org/TR/WCAG22/#text-alternatives

<BC> WCAG 3

https://www.w3.org/TR/wcag-3.0/

WCAG 3.0

janina: I propose we link to WCAG 3.0

Lionel_Wolberger: I am concerned it will still change quite a bit and such links will be brittle

<BC> too early to know

janina: It may not change that much, and Edge Capabilities has a big overlap

+1 to 'too early to know'

WCAG 2.2, Guideline 1.2 Time-based Media: Provide alternatives for time-based media.

<BC> screen reader, closed captions

janina: This is now common for the edge to provide close captions
… it is aspirational that AI could provide some audio description

Summary of resolutions

  1. Next telecon will be 31 July
Minutes manually created (not a transcript), formatted by scribe.perl version 221 (Fri Jul 21 14:01:30 2023 UTC).

Diagnostics

No scribenick or scribe found. Guessed: Lionel_Wolberger

All speakers: Bev, janina, Lionel_Wolberger

Active on IRC: BC, janina, Lionel_Wolberger