W3C

– DRAFT –
(MEETING TITLE)

26 July 2023

Attendees

Present
janina, jasonjgw, John_Paton, Roy, scott_h
Regrets
-
Chair
jasonjgw
Scribe
janina, jasonjgw

Meeting minutes

Collaboration Tools Accessibility User Requirements.

Lisa's Email about Communications

https://lists.w3.org/Archives/Public/public-apa/2023Jul/0018.h

Janina notes Scott's remarks on the use of color to convey information in the COGA comments.

scott_h: Coloring clearly shows, but didn't work for my high-contrast scheme

scott_h: Caught the initial "COGA" numbering may have dropped in the "download into Microsoft Word"

scott_h: Couldn't figure out where the GOGA comment ended

janina: Perhaps also noting "END COGA Comment"

jasonjgw: Seems they might not have used the comment feature in Google Docs? That would have trasferred to Word. Libreoffice, Pages, would still show up as comments

jasonjgw: Would also show where the comments start and end

scott_h: Had to resort to a colleague's assistance, still difficult to tease out; though definitely easier

scott_h: We're still not to a clean "copy and paste into github" state

scott_h: Still interpretation required

Substance of COGA Comments

janina: Noting COGA hasn't finished on this

scott_h: My feedback just initial and my perspective

scott_h: Much of it very useful; particularly adding a summary--though how that should work is a question to consider

scott_h: Like summary very much; hoping AI can help

jasonjgw: Agree comments very interesting

jasonjgw: Concerned scope not addressed; some would apply to document editing and beyond

jasonjgw: Creation of summaries can apply to docs, but also web pages, etc

jasonjgw: CTAUR is scoped to editing environments, and the COGA comments exceed this scope

jasonjgw: So, yes the comments are useful, but we can't use them in CTAUR

jasonjgw: If COGA wants to argue for a wider scope, that should be explicitly addressed

jasonjgw: On the other hand there may be creative ways to rework the comments into what would fit the doc

jasonjgw: Summary is a good example

jasonjgw: But in collaborative environment one might need to be more specific, e.g. while editing is in process auto generated summaries should be available on some time interval

jasonjgw: So, we want to ask COGA to consider how to work their thoughts into scope--or redefine scope with us

scott_h: Agree re scope; and summary does provide a good example of scope creep

jasonjgw: As the comments stand, some we would rule out of scope, others we'd need to work on a way to bring them into scope, others are clearly relevant

janina: Also, there's no explicit explanation of why github is so hard for COGA people to use

janina: Notes we consider github a collaborative environment, and very much in scope of CTAUR

janina: We expressly want COGA to explain their issues with git (and github)

jasonjgw: It's notable there are multiple interfaces into github, including editing environments that take care of github on the back end

jasonjgw: There are so many different ways of dealing with github, not just the default browser

jasonjgw: Having multiple interfaces into the same tool seems so accessibility friendly that it's critical for us to investigate and comment on the strenghts and challenges for different accessibility users

janina: Noting it's also not a binary. It's not just browser or CLI; there are other tools that help one edit and handle the editing and the github push

Media accessibility: update and planning.

jasonjgw: Looked at issues recorded from MEIG

jasonjgw: Link in this meeting's agenda ...

jasonjgw: We've discussed most, at least to a degree

jasonjgw: All useful and relevant, and we can get into github at some point

jasonjgw: Notes some environments left builtin a11y and are now retrenching because it didn't work out for them to reinvent all of a11y

jasonjgw: Good luck relying to reinvent a11y in canvas

jasonjgw: Attended a conference, will need to find link, but it was noted the major tech names were doing quite well for a11y, but beyond them there's a rapid and steep decline in quality

jasonjgw: Expertise in using available tools is highly concentrated, also the ones driving the standards; everyone else is lacking

Miscellaneous updates and topics.

janina: We expect Raja back, as he said he'd be back in August

Roy: Will followup

janina: Expect to be here all of August

https://lists.w3.org/Archives/Public/public-apa-admin/2023Jul/

janina: CfC ends midnight Boston time Friday 28 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: janina

All speakers: janina, jasonjgw, Roy, scott_h

Active on IRC: janina, jasonjgw, JPaton, Roy, scott_h