Meeting minutes
Inaccessibility of CAPTCHA.
janina: Not a lot of movement yet on CAPTCHA
janina: We should continue to work on this as time allows
Accessibility of Remote Meetings.
jasonjgw: Scott sent out the previous blog post text from the first time
jasonjgw: The blog text is a bit long for an announcement
janina: The is a wiki page with a template for announcements and other types of communications
jasonjgw: However, it looks like the earlier version of the announcement on that page is no longer there
janina: Will see if we can get some staff help to find this
Accessibility of collaboration tools - scope of possible work.
jasonjgw: Created wiki page at https://
jasonjgw: Have found numerous examples in the research literature, although it seems very screen-reader heavy
jasonjgw: Not much in the way of cognitive impairments
raja: Have some experience in collaboration in games and teams
raja: But not seeing a lot in the wiki
janina: The wiki is bare bones right now
raja: Agree that we need more discussion and come to some agreement on definitions
raja: The general concept of synchronous or asynchronous - for example, with captions and transcriptions, where captions are timed but a transcript is OK without timestamps
janina: We could look at these distinctions as examples
jasonjgw: One concern - if several are collaborating online in real time in a document, but also communicating at the same time (like in a meeting) that creates a lot of cognitive load
raja: Sometime people need more time to digest information
janina: One example is the real-time meeting, but the other is perhaps more on asynchronous collaborative document editing
raja: We need to find a way to allow people to slow down or pause which would support those with longer processing time
janina: This seems more like an issue for Remote Meetings
jasonjgw: Yes - the Remote Meetings updated draft has this now
scott_h: Collaborative tool documents like Office 365 online with Narrator works very well
scott_h: Good example is writing grant applications - lots of people writing different points
scott_h: Agree that there are different implications for different assistive technology use cases
jasonjgw: Literature on this mostly concerns screen reader users
jasonjgw: We should do a cross-disability analysis
<scott_h> sorry everone - will share comments in IRC
<scott_h> basically just saying that when we look at collaborative tools
<scott_h> we should consider stastic documents, editing periodically
<scott_h> and also a fflurry of editing such as in a collaborative grant application
<scott_h> and the implications for assistive technology use in all these sceanrios
raja: defining the user case and scenarios will be helpful
<scott_h> across differen disability groups
<scott_h> I thik that's it - sorry that my internet seems to ahve died for zoom tonight
<scott_h> Will add my references to the wiki durig the week
jasonjgw: We should consider what features we have an interest in, and let that determine what types of collaborative tools we wnat to discuss
Natural Language Interface Accessibility User Requirements.
jasonjgw: Nothing to report here
jasonjgw: Should resume this discussion when Josh is present
jasonjgw: Updated draft is likely in order
Miscellaneous topics.
jasonjgw: The web machine learning ethics document has not made any changes this far
janina: Two CfCs out - renaming the personalization task force to "WAI Adapt:" with the name of the module afterward
janina: An SVG draft is out as well
janina: The Maturity Model work is in the works as well
jasonjgw: Other thoughts?