W3C

- DRAFT -

Accessible Platform Architectures Working Group Teleconference

01 Aug 2018

Attendees

Present
janina, Joanmarie_Diggs, MichaelC, Becka11y, Irfan_Ali, JF, tzviya
Regrets
Chair
Janina
Scribe
JF

Contents


<scribe> scribe: JF

Agenda Overview; Announcements

JS: any additional items?

Other Business

MC: New Publications - one is urgent
... Web Authentication

<MichaelC> Web Authentication: An API for accessing Scoped Credentials Level 1

that WG is looking for a wide review at the same time as requesting transition

seems a bit late

We've looked at this in the past, we sent some questions

MC: unaware of any further action on their part

Q: Do we want to look at this again?

JS: we can. Perhaps assign Janina and Jason?

<MichaelC> ACTION: janina to review Web Authentication in response to wide review request

<MichaelC> ACTION: jason to review Web Authentication in response to wide review request

<trackbot> Created ACTION-2176 - Review web authentication in response to wide review request [on Janina Sajka - due 2018-08-08].

<trackbot> Created ACTION-2177 - Review web authentication in response to wide review request [on Jason White - due 2018-08-08].

<MichaelC> CSS Basic Box Model Level 3

MC: Next is CSS basic box model level 3. Just published with a warning

but also seems to be soliciting review. Last published in 2007

MC: believe the warning is for implementation but still wanting review

No apparent changes in change log

MC: the diff seems significantly enough different to warrant another look

JS: perhaps add to ian's list?

MC: agree

JSL flow/overflow would be a concern

MC: this seems to have somethingabout overflow, but that is also covered in another module (likely why the warning is there)

JS: they might work on this for a while and not publish an update

MC: they develop at different speeds - sometimes quickly other times not so much
... filed as an issue
... Css display module level 3

<MichaelC> CSS Display Module Level 3

MC: we've looked at this in the past with no issues, however an issue was filed against bikeshed tool

<MichaelC> Bikeshed Issue 1316

used to generate TR documents

MC: if you use display content property, bad things happen for a11y - confirmed by leonie elsewhere

We may have to ask them not to use that property - we did not forsee this as an issue

MC: Is this an implementation problem?
... appears via the bug that when the box is no longer exposed on the screen, it is also lost to the A11y API
... Leonie has weighed in, so believe there is a there there

JS: add to Ian's list, but add APA to the bug as an interested party

MC: not sure if we can do that, but individuals can add themselves

bug in bikeshed is cross-referenced to our bug in CSS TF

JS: assign to Ian (?) [agreement to do so]

<MichaelC> ACTION: pouncey to manage review of css display:contents issue

<trackbot> Created ACTION-2178 - Manage review of css display:contents issue [on Ian Pouncey - due 2018-08-08].

MC: suspect that this may circle around, with an attempt to involve this WG

<MichaelC> action-2178?

<trackbot> action-2178 -- Ian Pouncey to Manage review of css display:contents issue -- due 2018-08-08 -- OPEN

<trackbot> https://www.w3.org/WAI/APA/track/actions/2178

Should be prepared for that

<MichaelC> action-2178: https://www.w3.org/WAI/APA/wiki/CSS_Display_Module_Level_3

<trackbot> Notes added to action-2178 Manage review of css display:contents issue.

<MichaelC> action-2178: https://www.w3.org/TR/css-display-3/

<trackbot> Notes added to action-2178 Manage review of css display:contents issue.

new on TR http://www.w3.org/TR/tr-status-drafts.html

<MichaelC> action-2178: https://github.com/w3c/css-a11y/issues/24

<trackbot> Notes added to action-2178 Manage review of css display:contents issue.

JS: tzviya did a review, which we should likely take up as an APA comment

s/TViay/Tzviya

<MichaelC> action-2176?

<trackbot> action-2176 -- Janina Sajka to Review web authentication in response to wide review request -- due 2018-08-08 -- OPEN

<trackbot> https://www.w3.org/WAI/APA/track/actions/2176

Tzviya: no image descriptions

<MichaelC> action-2176: https://www.w3.org/WAI/APA/wiki/Web_Authentication:_An_API_for_accessing_Scoped_Credentials_Level_1

<trackbot> Notes added to action-2176 Review web authentication in response to wide review request.

there are implementation issues that may need to be addressed, but the actual document here has nothing to address

<MichaelC> action-2177: https://www.w3.org/WAI/APA/wiki/Web_Authentication:_An_API_for_accessing_Scoped_Credentials_Level_1

<trackbot> Notes added to action-2177 Review web authentication in response to wide review request.

<MichaelC> action-2176: https://www.w3.org/TR/webauthn/

<trackbot> Notes added to action-2176 Review web authentication in response to wide review request.

<MichaelC> action-2177: https://www.w3.org/TR/webauthn/

<trackbot> Notes added to action-2177 Review web authentication in response to wide review request.

This is mostly about the data (so heavy impact onprivacy and security) but for a11y it's more of an implementaiton issue

JS: No direct concern, but implementers should be aware...
... any objection to making this an APA comment

Gottfried: no

<Becka11y> +1

JS: send out a CfC here and then forward the comment upon approval
... likely the same paragraph (warning it's about implementations) could also be used in the Web Auth comments

Agenda Overview; Announcements

Charter Status Update

JS: Have received comments on the Draft, believe we've addressed them all

MC: all the comments were non-binding (no objection), mostly editorial
... have sent responses to the commenters
... reviewing changes

Publishing & HTML Transcript Redux

CAPTCHA Rewrite Update

JS: the research group are looking at the comments. Too many negative coments regarding reCaptcha
... now is the time to review whether the reordering of the content works. Need comments by EOB Tuesday

The goal is for the document to flow in a more logical fashion

so looking to review the comments on reCaptcha, and the reordering

there was also a comment/concern on privacy/security

Charter Status Update

but if anyone has any comment on the organization of the document, speak up quickly

TPAC 2018 https://www.w3.org/WAI/APA/wiki/Meetings/TPAC_2018

JS: not much to say. JS starting on a draft agenda, will require some discussion/negotiation with other groups to coordinate meetings

Gottfried: will only be there on the Mon/Tues

Publishing & HTML Transcript Redux

JS: we made some commitments, and had a useful overview of some of the things we wanted to achieve from last year's TPAC notes

also looked at other past discussions. Noted a few things we never finalized

including the programmaticly association of a Transcript to the video, which resulted in a debate

differing opinions on what is sufficient

JS: recall a past discussion from ~5 years ago , where it was a "wait and see" approach

but nothing has advanced in 5 years

potential of including timing offsets in the transcript... some of the other things we looked at may have relevance here as well

JS: transcripts or "a book" could also be the master (?)

<janina> \ack t

tzviya: the desire is that the navigation can lead you to either, so that the user can access the content in the mode they desire (text, audio, etc.)

[discussion on this]

JS: Marrisa wasn't able to attend, hopefully next week.
... I think there is enough there that "the same approach" would work for either use-case

JF: possible that Personalization would be involved here as well

JS: we need to get the discussion re-started
... start socializing this across other groups, with a TPAC Follow-up (??)

Knowledge Domain Handling

JS: idea is that accessible math in browsers is a big deal.
... there is a never-ending demand for specific knowledge for many related topics (heard from Diagram Center on needs/use-cases)
... seems there may be some generic things that could be said (at the highest level) when it comes to Math, Music, STEM, etc. that it may often be available in text as well

we want a simpler means of addressing this - perhaps with A11y API mappings, and then use page-level metadata

don't want to wait on AT to figure this out, we need subject matter expertise on the topics. May have a generic way of discussing, or maybe not

tzviya: this sounds very much about tool-building and education

a lot of publishing around math is automated

JS: noting a specific discussion around Math on the Monday at TPAC
... hope we can bring forward approaches - may never be 100% but what can we do to make it easier to expose this to AT (for example)

CSS Update

JS: done for today. thanks and bye

trackbot, end meeting

Summary of Action Items

[NEW] ACTION: janina to review Web Authentication in response to wide review request
[NEW] ACTION: jason to review Web Authentication in response to wide review request
[NEW] ACTION: pouncey to manage review of css display:contents issue
 

Summary of Resolutions

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.152 (CVS log)
$Date: 2018/08/01 17:02:51 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
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)

Succeeded: s/al.so/also/
Succeeded: s/TViay/tzviya/
FAILED: s/TViay/Tzviya/
Succeeded: s/implementoer/implementers/
Succeeded: s/al lthe/all the/
Default Present: janina, Joanmarie_Diggs, MichaelC, Becka11y, Irfan_Ali, JF, tzviya
Present: janina Joanmarie_Diggs MichaelC Becka11y Irfan_Ali JF tzviya
Found Scribe: JF
Inferring ScribeNick: JF
Found Date: 01 Aug 2018
People with action items: janina jason pouncey

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


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]