Meeting minutes
<jasonjgw> prezakim, remove agendum 6
TPAC 2022 - participant availability.
Who is going to TPAC?
<Lionel_Wolberger> Lionel will check back for the Captcha agenda items later this call.
janina: TPAC is week of Sept 12 in Vancouver BC
Scott: will need to see how travel options open closer to event
raja: When is it?
janina: Monday Sept 12, and runs through the week
raja: can an email be sent with this info?
janina: Yes, will send.
Miscellaneous topics.
janina: Announcement - W3C planning for a reorg
janina: Looking at a sustainable organization to provide for continuing development of the web
janina: March 9 (APA hour) meeting will discuss this work
janina: CFC out on W3C Maturity Model
janina: CFC will end March 2
janina: Any quesions?
TPAC 2022 - participant availability.
jasonjgw: Added an issue in GitHub to discuss recommendations
janina: Not ready to close document
janina: We still need approach Timed text for joint publication
janina: May need to add some pointers that are more on the mainstream side
For instance, the connection to translation subtitles is related but not exactly an accessibility issue
janina: XR environments may have considerations where mainstream access has common ground with accessibility issues
raja: In support of asking Timed text
<Joshue108> JS: How much has the document changed?
janina: May need a second wide review draft
<Joshue108> JS: Steve, how substantial are the changes?
<Joshue108> SN: We did address the 7-8 issues that were raised in Github
<Joshue108> Some addition research was referenced etc
<Joshue108> I'd say 10-15% has seen some change
<Joshue108> OTTOMH
<Joshue108> JS: Lets ask Timed text
<Joshue108> They may want to introduce things, and that would hit both ours and their wide review audience
<Joshue108> JS: We can defer our decision
<Joshue108> JS: <Likes the intro - this is a kerbcut>
<Joshue108> JS: I'd like to see this kerbcut in the abstract to include this..
<Joshue108> JW: Lets get those into issues
<Joshue108> SN: Makes sense to me
<Joshue108> SN: We do provide recommendations - but if useful to pull them into a summary - to underscore.
<Joshue108> JS: Could be useful.
<Joshue108> JOC: What about timeframe?
<Joshue108> JS: Could be end of March.
<Joshue108> JS: We do have CSUN in the middle.
Synchronization Accessibility User Requirements.
<jasonjgw> zkim, close item 2
Accessibility of Remote Meetings.
jasonjgw: Look at a few open issues
scott: Worked through the COGA input
scott: Issue around captioning
scott: Sometimes captioning is an additional media
scott: Suggest expanding the use case of captioning
janina: Both seeing caption text and hearing the words is commonly known to enhance comprehension in the mainstream population
raja: Have some citations for general population use of captions
raja: 40% of Netflix users use captions
raja: 20% for standard TV usage
raja: will email these references
scott: Point about screen readers - comment was to expand to more mainstream use of text-to-speech
janina: Not sure it this expands to remote meetings
<Joshue108> +1 to Janina
Joshue108: Agree that this seems a problem
janina: Listening to TTS while people in a meeting are speaking is clearly difficult
jasonjgw: Example of TTS reading a slide while someone is speaking
jasonjgw: Reading a set of slides before a meeting and using TTS in that settings is a very different scenario
Natural Language Interface Accessibility User Requirements.
jasonjgw: Some activities have occurred in GitHub issues
jasonjgw: Will need to push these items to next week
Inaccessibility of CAPTCHA.
jasonjgw: Open issues have been documented, and research around trust tokens continue...
jasonjgw: Further thoughts on CAPTCHA?