<scribe> scribe: janina
https://rawgit.com/w3c/apa/security-privacy-considerations/captcha/
jgw: Added a scoping section to clarify we address a11y, even though we note privacy/security issues
<jasonjgw_> Janina: approves of the notion of introducing a "scope" statement. The approach is right and it can be continued to be refined. For instance, we should contextualize the security and privacy considerations more.
<jasonjgw_> Janina: we need to explain whose security is relevant (e.g., that of the service provider in relation to defending against attack). Authentication brings in user security and creates a different focus. Janina will stage that in the scope section.
jb: Notes new staffer focussed on authentication, workshop coming
jgw: Requests workshop info when available
<jasonjgw_> Janina will work on this early next week.
sh: Like the addition, and OK with refining
<jasonjgw_> Janina: queries whether we should remove remarks about security implications of audio/visual CAPTCHA.
<jasonjgw_> Janina: suggests we should be careful that we need to be careful to disentangle the accessibility considerations from security and privacy, as we are asking others to do in evaluating and devising solutions.
https://www.w3.org/WAI/APA/wiki/Verticals_to_Track
<jasonjgw_> Janina: we haven't discussed the relationship with authentication, as well as Verifiable Claims.
<jasonjgw_> Janina: Authentication is now in Candidate Recommendatoin. Jason is invited to review again. Verifiable Claims has also been reviewed. Jaina suggests APA is looking for an Accessibility Impact statement for both of them regarding implementations.
<jasonjgw_> Janina notes, responding to Jason, that the personalization task force is seeking to work on these issues. Jnaina clarifies that any issues with personalization do not affect the Verifiable Claims spec that is about to enter CR. The same is true of uthentication.
<jasonjgw_> Agreement: no issues for RQTF here yet, thought there may be with implementation considerations.
<jasonjgw_> Web payments: Jnaina suggests we're in the same situation - no issues giving rise to research questions, and no issues in the specifications themselves.
<jasonjgw_> Janina and Jason agree that XR, domain-specific content, and navigation issues emerging from CSS (including navigation in graphicl contexts) are the issues identified so far that call for RQTF engagement.
<jasonjgw_> Janina: automotive - the question is wehther there are research issues to investigate.
<jasonjgw_> Janina: recalls that the request was for accessibiity implications to be identified issue by issue. It has been difficult to articulate the use cases and requirements given the scope of their work as it was discussed last year.
<jasonjgw_> It is agreed that we should determine their scope and establish whether there are accessibility issues motivating research questions.
<jasonjgw_> Janina: media - we still have a Media Accessibility User Requirements dcument that is very useful. There are developments relevant to this work.
<jasonjgw_> Janina notes work on audio descriptions that has taken place recently.
<jasonjgw_> Janina: publishing - there is an abundance of activity following the integration of digital publishing into W3C.
<jasonjgw_> Janina: the requirement emerging from Digital Publishing is to be able to replicate the capabilities achieved in DAISY and EPUB using XML and SMIL for synchronized media - having a digital publication that serves as a master for a media alternative (e.g., synchronized text/audio).
<jasonjgw_> Janina suggests that we devise an appraoch that allows any of the alternatives (timed audio, sign language translation - or non-time-dependent text) to serve as the master to which other alternatives are related.
<jasonjgw_> Janina suggests there may not be substantial impact so far as RQTF is concerned.
<jasonjgw_> We expect to conclude the review of verticals next week.
This is scribe.perl Revision: 1.152 of Date: 2017/02/06 11:04:15 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00) Default Present: jasonjgw_, scott_h, janina Present: jasonjgw_ scott_h janina Regrets: David_Sloan Found Scribe: janina Inferring ScribeNick: janina WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth Found Date: 15 Aug 2018 People with action items: WARNING: IRC log location not specified! (You can ignore this warning if you do not want the generated minutes to contain a link to the original IRC log.)[End of scribe.perl diagnostic output]