12:50:40 <RRSAgent> RRSAgent has joined #rqtf
12:50:40 <RRSAgent> logging to https://www.w3.org/2022/04/13-rqtf-irc
12:50:42 <trackbot> RRSAgent, make logs public
12:50:42 <Zakim> Zakim has joined #rqtf
12:50:44 <trackbot> Meeting: Accessible Platform Architectures Working Group Teleconference
12:50:44 <trackbot> Date: 13 April 2022
12:50:46 <jasonjgw> chair: jasonjgw
12:50:49 <jasonjgw> present+
12:51:04 <jasonjgw> agenda+ Synchronization Accessibility User Requirements - publication process.
12:51:04 <jasonjgw> agenda+ Inaccessibility of CAPTCHA.
12:51:04 <jasonjgw> agenda+ Accessibility of Remote Meetings.
12:51:04 <jasonjgw> agenda+ Natural Language Interface Accessibility User Requirements.
12:51:11 <jasonjgw> agenda+ Miscellaneous topics.
12:58:31 <Lionel_Wolberger> Lionel_Wolberger has joined #rqtf
12:59:15 <JPaton> JPaton has joined #rqtf
12:59:56 <SteveNoble> SteveNoble has joined #rqtf
13:00:03 <SteveNoble> present+
13:00:22 <janina> janina has joined #rqtf
13:00:57 <Lionel_Wolberger> present+
13:01:27 <jasonjgw> zakim, next item
13:01:27 <Zakim> agendum 1 -- Synchronization Accessibility User Requirements - publication process. -- taken up [from jasonjgw]
13:02:25 <SteveNoble> jasonjgw: Second working draft of SAUR has been published
13:03:21 <SteveNoble> janina: Expecting that the messaging on SAUR publication will commence in another day or so
13:03:46 <SteveNoble> jasonjgw: Review period will go through May 13
13:03:55 <jasonjgw> zakim, next item
13:03:55 <Zakim> agendum 2 -- Inaccessibility of CAPTCHA. -- taken up [from jasonjgw]
13:05:08 <SteveNoble> jasonjgw: Made an attempt at the document reorganization - in a new branch
13:05:35 <SteveNoble> jasonjgw: Any discussion on the reorganization?
13:07:28 <SteveNoble> janina: We do not need to rush to cement these changes
13:07:54 <Joshue108> Joshue108 has joined #rqtf
13:08:11 <SteveNoble> janina: We likely need to change working in the abstract and conclusions and many things in between
13:08:47 <SteveNoble> For the zoom meeting?
13:09:10 <SteveNoble> 310589
13:09:50 <Joshue108> s/310589/
13:10:10 <SteveNoble> jasonjgw: Currently we have separation between legacy and state-of-art
13:10:29 <SteveNoble> jasonjgw: Also between interactive and passive
13:11:37 <SteveNoble> scott: That reorg plan sounds good
13:12:03 <Joshue108> present+
13:12:33 <SteveNoble> scott: how much do we think will be new content?
13:13:02 <SteveNoble> janina: Could be 10% to 20%
13:14:16 <SteveNoble> janina: New technology is pressing toward 99.99+% confidence, so this could indeed kill CAPTCHA
13:15:22 <SteveNoble> jasonjgw: Will merge the existing changes and then we can discuss from there
13:15:52 <SteveNoble> jasonjgw: We can wait in the title till later
13:16:28 <SteveNoble> Lionel_Wolberger: Had an action item to review the specification
13:16:57 <SteveNoble> Lionel_Wolberger: Connecting to verifiable credentials group
13:17:31 <SteveNoble> Lionel_Wolberger: The CAP protocol is first
13:18:07 <SteveNoble> Lionel_Wolberger: Verifiable credentials is also a good direction
13:18:43 <SteveNoble> Lionel_Wolberger: Privacy pass is a third option to look at
13:20:11 <scott_h> scott_h has joined #rqtf
13:20:40 <scott_h> present+
13:20:47 <SteveNoble> Lionel_Wolberger: "Privacy pass" may be a poor name - the driver behind that spec was for people who need to keep their identity private for safety reasons
13:20:57 <janina> q+
13:21:56 <SteveNoble> Lionel_Wolberger: Verifiable credentials seems to be a mature approach
13:23:05 <SteveNoble> janina: The IETF connection was not considered in our original document, so this is a good addition
13:25:40 <SteveNoble> jasonjgw: Possible connection to an organized key signing?
13:26:30 <SteveNoble> Lionel_Wolberger: Perhaps a more common place analogy is using an ATM to get a new bank pin?
13:27:24 <SteveNoble> janina: Mentioned Bookshare's approach to use one's NLS credentials to sign up
13:27:49 <Lionel_Wolberger> present+
13:27:49 <Lionel_Wolberger> Non-profit in-person vetting with single-use tokens
13:28:16 <Lionel_Wolberger> q?
13:28:25 <Lionel_Wolberger> s/mature/immature
13:28:48 <SteveNoble> jasonjgw: We can come back to this next week
13:29:23 <Lionel_Wolberger> Lionel meant to say, Verifiable credentials is likely to be more immature approach as it is a newer technology, but it is W3C (and works closely with DIDs)
13:29:46 <SteveNoble> scott_h: Great progress!
13:30:23 <jasonjgw> zakim, next item
13:30:23 <Zakim> I see a speaker queue remaining and respectfully decline to close this agendum, jasonjgw
13:30:39 <Joshue108> scribe: Joshue108
13:30:44 <Joshue108> q?
13:30:48 <Joshue108> ack jan
13:30:57 <jasonjgw> zakim, next item
13:30:57 <Zakim> agendum 3 -- Accessibility of Remote Meetings. -- taken up [from jasonjgw]
13:31:06 <Lionel_Wolberger> Lionel adds for the minutes some Privacy Pass links:
13:31:19 <Lionel_Wolberger> Privacy Pass Architectural Framework, https://www.ietf.org/archive/id/draft-ietf-privacypass-architecture-03.html
13:31:33 <Lionel_Wolberger> The Privacy Pass HTTP Authentication Scheme, https://www.ietf.org/archive/id/draft-ietf-privacypass-auth-scheme-02.html
13:31:39 <Lionel_Wolberger> Privacy Pass Issuance Protocol, https://www.ietf.org/archive/id/draft-ietf-privacypass-protocol-04.html
13:32:01 <Lionel_Wolberger> Lionel quietly leaves, see you in two weeks
13:32:14 <Joshue108> JW: On remote meetings - I think we should, instead of editors note - decide on what we want to say, and leave out
13:32:48 <Joshue108> JW: We should try to cover other issues around tooling to another document
13:33:04 <Joshue108> This could allow us to avoid extra rounds of public review
13:33:19 <Joshue108> JS: We have a week or two - we dont have our messaging lined up.
13:33:59 <Joshue108> SH: We have had some discussion but to comment, I'd need to think on diffs between ATAG and other tools. Where is that line drawn?
13:34:11 <Joshue108> Documents vs online publishing?
13:34:30 <Joshue108> JW: Its broad - but doesn't deal with the colloborative aspects
13:34:48 <Joshue108> Deals with conforming content and the UI a11y - but not collaborative challenges
13:34:57 <Joshue108> Working on a shared resource.
13:35:07 <Joshue108> SH: Makes sense
13:35:39 <Joshue108> Depends on specifics but I think, any platform used for collaboration should adhere to a11y user requirements
13:35:45 <Joshue108> We can draw on ATAG
13:35:53 <Joshue108> q+
13:36:06 <Joshue108> SH: We have discussed Google docs etc
13:36:36 <Joshue108> JS: There are things at play - it is not a REC at W3C - didn't get support
13:37:09 <Joshue108> https://www.w3.org/TR/ATAG20/
13:38:45 <Joshue108> <Discussion on if ATAG is or is not normative>
13:38:56 <Joshue108> <Janina gives some background>
13:39:01 <Joshue108> q?
13:40:35 <Joshue108> q?
13:41:02 <Joshue108> SH: Collaborative tools are in this grey zone
13:41:49 <Joshue108> JS: I like what Jason wrote. but the question is to what degree should this document cover requirements for cloud based authoring environments?
13:42:10 <Joshue108> SH: +1 to Janina
13:42:55 <Joshue108> SH: We do need to reference to it etc but maybe no so deep. I support focussing on online collaborative tools.
13:43:03 <Joshue108> JW: I'm in line with that.
13:43:27 <Joshue108> We may need to broaden this to cover other tools etc?
13:43:33 <Joshue108> SH: Good place for it.
13:44:05 <Joshue108> JW: There are issues with speed etc - and this relates to issues around organisation
13:44:31 <Joshue108> Should we also ref the ATAG? And defer it to new possible work?
13:44:54 <Joshue108> Then the editors note may not be needed.
13:45:26 <Joshue108> RK: Just to add a big problem is making it easy to add a11y automatically - in the software tool chain.
13:45:31 <Joshue108> SH: +1 to taht
13:45:44 <Joshue108> s/taht/that
13:46:18 <Joshue108> RK: Like PDFs can be terrible but a PDF is better. Its hard to convince people to convert
13:46:23 <Joshue108> Something to think about.
13:46:50 <Joshue108> SH: ATAG 2 part B is about how tools should be used to create accessible content.
13:47:53 <jasonjgw> Josh: thinks ATAG needs attention and could benefit from the work done regarding remote meeting accessibility.
13:49:30 <Joshue108> JW: On the collaboration side on the user needs - there have been some good things published.
13:50:14 <Joshue108> JW: I'll create a branch and we can refine?
13:50:18 <Joshue108> SH: Sounds good.
13:53:25 <jasonjgw> zakim, bye
13:53:26 <Zakim> leaving.  As of this point the attendees have been jasonjgw, SteveNoble, Lionel_Wolberger, Joshue, scott_h
13:53:26 <Zakim> Zakim has left #rqtf
13:53:38 <jasonjgw> rrsagent, make minutes
13:53:38 <RRSAgent> I have made the request to generate https://www.w3.org/2022/04/13-rqtf-minutes.html jasonjgw
14:01:56 <becky> becky has joined #rqtf