W3C

– DRAFT –
Accessibility at the Edge Community Group Teleconference

29 May 2024

Attendees

Present
janina, Jason, Lionel_Wolberger
Regrets
-
Chair
Janina
Scribe
janina, Lionel_Wolberger

Meeting minutes

Welcome & Introductions (As needed)

Lionel_Wolberger: We have received regrets.

Automatability

janina: I cleaned up the document

https://lists.w3.org/Archives/Public/public-a11yedge/2024May/0011.html

janina: for details see link, https://lists.w3.org/Archives/Public/public-a11yedge/2024May/0011.html

janina: We resume 'automatabilities' from the heading, Accessibility Provider Identification

Lionel_Wolberger: Accessibility Issue Reporting is really about Accessibility Issue Reportability, is it possible to report Accessibility issues

janina: We expect to have a specification at some point specifying a well known destination for reporting accessibility issues

Lionel_Wolberger: automation can help create the trouble ticket as well.

jason: I can think of many situations where automation would be quite challenging

https://w3c.github.io/ctaur/

jason: I'd like to clarify what we mean by automatability
… we are assuming that we cannot change what people are doing right now
… we are not assuming that given, if websites and their managers did so-and-so, then we would be automatable
… instead, we are looking at how technologies can change user outcomes in the current environment and scenarios
… I was thinking, how could this be useful outside of the community of people who do accessibility
… imagine coming to a CMS provider and saying, here are things that you can do in your CMS to help your users
… this is not about debating whether overlays are making false claims or not
… this is about CMSs and entitites that makes thousands of websites, how they can improve their user outcomes
… this focus can set us up for a bigger goal
… browsers can do a better job, CMSs can do a better job

janina: We labeled each item. Good work team!

Next steps

janina: I will find that orphaned H1 after the Appendix

jason: Propose we discuss the big picture question next time
… I propose post-source
… 'Accessibility at the Edge' encompasses the technologies that we might agree are post-source
… I have made a list of those technologies; you might add more

janina: Getting back to my actions, I will check the nesting
… for next time, we either have the high level discussion, or go through the H2s and think about organization

jason: I'm on board H2s

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: janina, jason, Lionel_Wolberger

Active on IRC: janina, Lionel_Wolberger