Meeting minutes
Inaccessibility of CAPTCHA.
JW: There have been developments on CAPTCHA
Issue raised on Github around trust tokens - a la Privacy Pass
The issue suggests the trust token proposal may help with CAPTCHA use cases
Its not clear how far this work has progressed in W3C but looks interesting..
JS: /me do we have a number for this issue?
<SteveNoble> https://
JW: The idea is that the token can attest to user authenticity
They are privacy preserving etc
<Jason gives background>
JW: Is that right? If so we have questions around how we may incorporate this into our work
JOC: I think we need Janina as there is a new scope for CAPTCHA work, relating to automation
JW: Yes, that's right. This relates to form submissions also
We will need to revise and update the section on privacy pass and work with the trust tokens proposal etc
JW: Any other comments?
SN: I'm also wondering if Janina would have something to say..
JW: It will involve APA to negotiate with other group
Synchronization Accessibility User Requirements.
JW: Lets do this one until Janina comes back
Steve has been working on this, seems to be heading towards a resolution.
<SteveNoble> https://
SN: Yes, I've been working on this with Nigel
SAUR Subtitle/Caption synchronisation #248
Nigel seems to be happy with this new iteration.
SN: I just need to update a branch and make a PR
Looks good to go
<SteveNoble> https://
We also have this issue SAUR subtitle rate summary #247
Comment from James Sanford, I've corrected the language and will also put that into Github.
SN: I'm still working on this
He seems to be saying there are commonalities but some of the user needs may not be explicitly a11y related
Raja: Touching on the subtitles issue, there have been some differences between translation subs, and subtitles for the deaf and hard of hearing
SDH - one diff is that you add environmental information that is in parenthesis
Like (ringtone)..
So currently with auto speech recognition, it could be close to the word popping up very shortly after being spoken
but for translation, it is more 'sentence by sentence' synchronisation and not 'word by word'
JW: Steve does that help?
Potentially greater latency issues in the translation case
SN: Yes, its the same case with Sign language translation - also not 'word for word'
JS: I think we need to be clear that SAUR is primarily aimed at pre recorded media where we dont have these real time issues
The note in intro could clarify - even point to Remote Meetings document
JW: Well we are treating them both, distinctly.
SN: There is no current pointer to remote meetings - we could add this.
Additional language at the top would be useful
Raja: +1
JS: We could get max uptake by keeping the guidance clear. We want to hammer home our research based reasons to pay attention to synchronisation
Raja: I completely understand that distinction - with real time, SDH - we need more information provided, spoken, environmental, lyrics etc
With translation or regular sync, lyrics are not included so if we move towards SDH, they need to be included.
But it doesn't matter what kind of subtitles you have or the time but we still need environmental aspects etc
SDH = Subtitled for the Deaf and Hard of Hearing
SN: Thanks Raja
JW: Steve can you look at this, and make changes to resolve?
SN: yes
JS: Did we resolve Nigel's issue?
SN: We have worked it, and it is ready to go.
JS: I can start conversation around joint publishing shortly
<Discussion on co-ordination on CAPTCHA doc>
SH: Regarding remote meetings, we did reference RTC but dont think we have ref to remote meetings in SAUR.
We should make sure it is referenced correctly
Natural Language Interface Accessibility User Requirements.
JOC: Here are the NAUR related issues https://
<SteveNoble> Joshue108: Lots of new comments from COGA
<SteveNoble> jasonjgw: If some of these issues are already covered by WAI guidelines than we can point there and not focus so much here
[COGA] - we know its related to this tranche
<SteveNoble> janina: Wondering about the word "natural"
<SteveNoble> janina: We may need to think about this and add a note in the introduction
<SteveNoble> janina: Problem with just thinking of natural as a spoken language
<SteveNoble> janina: Are we including sign language?
<SteveNoble> jasonjgw: I'll open an issue to bring this up
[COGA] 2.6.6 Using Multimodal Interfaces to Enhance Understanding
https://
<janina> +1 to Josh's approach
<SteveNoble> Joshue108: There may be multiple points which were merged into issues
Here is the user need 26 https://
<SteveNoble> jasonjgw: Editorial change of wording is fine
<SteveNoble> jasonjgw: User needs 27
<SteveNoble> Joshue108: Comment about additional requirement to include icons
<SteveNoble> janina: A known fact, but we don't have technology for integrating AAC
<SteveNoble> scott_h: Things like mapping technologies that use familiar logos
<SteveNoble> Joshue108: Symbol sets can be very individualized
<SteveNoble> scott_h: If the symbol set were introduced we might lose the storefront
JOC: Thanks Scott interesting points
<SteveNoble> jasonjgw: Not sure if the icon reference was specific to AAC
<SteveNoble> Joshue108: The comment was more about familiar icons
<SteveNoble> janina: We could say that some relate to symbol sets and some to brand icons
<SteveNoble> jasonjgw: Problem with "familiar" is that depends upon the individual
<SteveNoble> Joshue108: "brand related opportunities"
<SteveNoble> user need 27
<SteveNoble> janina: This one needs clarification
[COGA] 2.6.3 Communicating in Language that is Clear, Simple, and Appropriate to the Audience #280
https://
Relates to this in the NAUR https://
<SteveNoble> Joshue108: Included several points...all seem generally appropriate
<SteveNoble> Joshue108: Many are just editorial things
<SteveNoble> janina: Highly technical issues cannot easily be simplified
<SteveNoble> In many cases using specific technical language is important to properly communicating what the author is stating
<SteveNoble> Joshue108: user need about dyscalculia
<SteveNoble> janina: That becomes a very personalized issue
<SteveNoble> jasonjgw: Circle back to more of these next week
Accessibility of Remote Meetings.
I feel better at Git :-)
<SteveNoble> scott_h: Thanks to Josh for helping with the GitHub logistics
Miscellaneous topics.
JS: APA call rescheduling