Meeting minutes
Synchronization Accessibility User Requirements.
jasonjgw: The announcement text has been drafted and is ready for further editing
janina: Editorial changes to the SAUR itself are a little further in the Note process
janina: The Note will be published now that the CfC has been successful - that itself is independent of the messaging
Accessibility of remote meetings.
jasonjgw: Emails with the EO working group have transpired
jasonjgw: They may have comments on the draft
jasonjgw: We do not yet have an ETA on comments as of this point
jasonjgw: The CfC runs through Friday
scott: Have we any new COGA comments?
janina: We went through all their comments and dealt with each one, although not all were adopted
janina: Would be good to have a summary of how we addressed each comment
Scott: will look at these and list them out so they are documented
jasonjgw: Other comments
Accessibility of collaboration tools.
Inaccessibility of CAPTCHA.
Lionel_Wolberger: Apple has moved forward with Passkey
Lionel_Wolberger: We are tracking this - reached out to get more details
Lionel_Wolberger: Meeting with Manu this week - should give us more perspective
janina: There is a movement away from multiple passwords, which should also be heading toward human authentication
Raja: There are a lot of users who find face recognition or verbal authentication innaccessible - especially if there are more than one users on a give device
janina: We have always stressed multiple authentication techniques
janina: There are mechanisms for a single device to accommodate multiple users
janina: The problem is when a user who doesn't already have account access set up tries to use it
Josh: downloadable keys are also a possible method
jasonjgw: The expectation is that the user has at least one method that works for them
janina: APA has always insisted that the multiple biometric options be available - not just one
janina: A lot of this presumes access to a mobile device - which is not a reality everywhere
jasonjgw: We can come back to this next week
jasonjgw: At some point we will need to update the existing document
janina: That would probably be after TPAC due to other priorities
Lionel_Wolberger: Any further thoughts from Raja?
Raja: Nothing else
Lionel_Wolberger: One corner of this discussion of caretaker identities (like power of attorney in the legal field)
Lionel_Wolberger: One example is a child's account that must be set up by a parent
raja: One example is using a voice relay service
Raja: Cannot use voice authentication for a bank account, since the vocal assistant changes
raja: Under US law, all banks must accept a call that comes from a voice relay service
Lionel_Wolberger: Examples include fiduciary, caretaker, POA, interpreter, etc.
janina: A lot of concerns also for users with cognitive issues
Lionel_Wolberger: Thanks to the signers on the call!
Accessibility of collaboration tools.
jasonjgw: Thanks to Scott for the references on the wiki
jasonjgw: We need a title and need to firm up the scope
jasonjgw: Annotation tools should be in scope
jasonjgw: Ideas for refining the scope and title?
Scott: Like the term "online collaboration tools"
janina: Regardless of the title, we need the short name for the repository
Josh: "Collaboration accessibility user requirements"
jasonjgw: Some points include Revision management, annotation and comments, multiple users at the same time, handling viewing and editing rights, etc.
janina: We can assume Copyright issues are handled by access rights and policies
Potential accessibility-related use cases for reporting API.
Natural Language Interface Accessibility User Requirements.
jasonjgw: Josh and I worked on the editorial comments, but still have more to go through
jasonjgw: We will need to bring back to next week's meeting
Inaccessibility of CAPTCHA.
Miscellaneous topics.
Scott: nothing now
jasonjgw: XR access symposium happened last week