<janina> Date: 02 dec 2020
<Matthew_Atkinson> scribe: Matthew_Atkinson
<paul_grenier> [there was much rejoicing]
+1
Janina: Work is ongoing on the rechartering (expected completion early next year; to last for a few years).
<Rachael> https://raw.githack.com/w3c/coga/add-glossary/content-usable/index.html#glossary
Rachael: The URL above doesn't
have all of the recent changes, but does include a new glossary
section.
... Content Usable is a set of design patterns, user stories
and personas that address the needs of individuals with
cognitive disabilities, which are not necessarily covered by
WCAG. The work relates to both AG and APA. Currently in wide
review stage, addressing feedback (including the
glossary).
... the document will become a W3C Note when published.
... COGA has standing approval to publish iterations,
contingent on providing updates for us (hence today's
topic).
... COGA is specifically looking for feedback on the glossary
at the above URL.
<paul_grenier> queu+
JF: Really like this document. Question about the requirement for clear language. Recently discovered there is work going on at ISO around clear language. Are there any links with ISO?
Rachael: *will check with COGA and come back on this*
JF: Seems like a good idea to get in contact with ISO.
Rachael: There's work being done in the Silver team on clear language too, so good to talk with them also.
Paul: Didn't see a mention of brain fog or chronic pain, which affect focus—are these intended to be covered?
<JF> FYI: https://www.iso.org/standard/78907.html
<paul_grenier> https://www.medicinenet.com/brain_fog/article.htm
<JF> More on the ISO work: https://www.iso.org/news/ref2566.html
Rachael: The space around cognitive disabilities is large, and there is a large gap in need at the moment, hence this initial publication. Research will be ongoing after this publication to cover more areas in future. Will take this suggestion back to COGA too.
Janina/Rachael: GitHub issues (or email) feedback welcome.
Thanks Rachael, from the group.
Janina: RQTF withdrew the RAUR document and put it back on the development table, as new requirements have come to light in recent discussions. May need metadata or API support for some assistive technologies (maybe not browser-based; potentially for digital assistants also).
Michael: Suggests publishing what is current as a working draft whilst updates are in progress.
Janina: *Has been advocating for this; will continue to.*
Josh: Aiming to avoid two wide review drafts in very quick succession.
Michael: Could publish the first one as just a working draft as opposed to a wide review.
*General agreement on publishing soon, but not as wide review, and following up shortly after with the wide review version after further issues have been addressed.*
*Josh and Michael to work on publishing a new working draft, under the standing permission for RQTF.*
Janina: Have been doing more
research and getting interesting data on synchronization and
timed text. This can be an issue in both live and published
media.
... Tighter envelopes of synchronization generally needed to
aid understanding.
Paul: Pronunciation update: soon to present the attribute-based model.
Janina: Have had an ongoing matter regarding which model to use.
Becky: For clarification: is the decision between one or two attributes, or attribute(s) and SSML?
Paul: The choices include: single attribute (with JSON in the value, which is not consistent with other specs); multiple attributes (which is more complex but doesn't force all the JSON into one attribute value); and SSML (which is desired but there are current implementation issues across several stakeholders to resolve).
JF: Is part of the issue with SSML that it's XML-based?
Paul: There were general concerns
about changes to parsers/rendering being undesirable due to
them being key browser components.
... Generally SSML would not be rendered, though there is a "p"
element where there may be rendering/parsing concerns.
Janina: We need to move (for
Pronounciation and Personalization) to dedicated attributes at
some point, not just data-* attributes (though we are not ready
yet). We can file a GitHub issue to request reserved
words.
... Personalization work going well (minutes available from
last Monday).
... Media Queries has some overlap (though there are
differences). Horizontal reviews are almost complete. Some
clean-up of the document and Explainer is ongoing.
Becky: *agrees/ACKs current status*
Michael: Work on this is restarting.
<MichaelC> Web of Things (WoT) Profile
Janina: The Web of Things group has requested a follow-up meeting with us (following TPAC).
Josh: Looks like this could relate to accessibility (though it's not mentioned in this document).
Becky: Seems like accessibility information should be included in the profiles.
*Michael, Janina agree*
<MichaelC> ACTION: joshue to review Web of Things Profile https://www.w3.org/TR/wot-profile/
<trackbot> Created ACTION-2269 - Review web of things profile https://www.w3.org/tr/wot-profile/ [on Joshue O Connor - due 2020-12-09].
Janina: the follow-up meeting will be soon (check out the list soon).
<MichaelC> action-2269: https://www.w3.org/WAI/APA/wiki/Web_of_Things_(WoT)_Profile
<trackbot> Notes added to action-2269 Review web of things profile https://www.w3.org/tr/wot-profile/.
<MichaelC> Web Authentication:
<MichaelC> An API for accessing Public Key Credentials
<MichaelC> Level 2
Janina: Jason and I reviewed it and didn't have issues, though we did have one member who expressed some concerns about it—need to contact them.
*Janina and Michael wonder if we can review a diff from the last version, as it is a long and technically detailed document.*
<MichaelC> ACTION: grenier to review WebAuthn 2 https://www.w3.org/TR/webauthn-2/
<trackbot> Created ACTION-2270 - Review webauthn 2 https://www.w3.org/tr/webauthn-2/ [on Paul Grenier - due 2020-12-09].
<MichaelC> action-2270: easier to review diff from level 1: https://services.w3.org/htmldiff?doc1=https%3A%2F%2Fwww.w3.org%2FTR%2Fwebauthn%2F&doc2=https%3A%2F%2Fwww.w3.org%2FTR%2Fwebauthn-2%2F
<trackbot> Notes added to action-2270 Review webauthn 2 https://www.w3.org/tr/webauthn-2/.
Paul: Has some knowledge of authentication [though is busy]; could have a look.
Matthew_Atkinson: Wondering if the WG had any particular concerns about accessibility?
Janina: It does appear to be fairly low-level and we have dialogue with the group, but concerns arise about devices that may use the API. We need to contact our member who has looked at this before.
<MichaelC> ACTION: janina to approach John Rochford about Web Authentication Level 2
<trackbot> Created ACTION-2271 - Approach john rochford about web authentication level 2 [on Janina Sajka - due 2020-12-09].
<MichaelC> action-2271: https://www.w3.org/WAI/APA/wiki/Web_Authentication:_An_API_for_accessing_Public_Key_Credentials_Level_2
<trackbot> Notes added to action-2271 Approach john rochford about web authentication level 2.
<a_carney> https://github.com/w3c/css-a11y/blob/master/README.md
Amy: Updated the README (above) recently.
<becky> scribe: becky
<MichaelC> https://github.com/w3c/csswg-drafts/issues/4201
Michael: issue title: Clarify effect of list styling on speech output
Janina: will track
Janina: can push this off to
January
... requested any addtional items, none announced
Janina: requested any addtional items, none announced
This is scribe.perl Revision of Date 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/synchronisation/synchronization/ Succeeded: s/The choices include single/The choices include: single/ Present: janina becky NeilS a_carney Rachael paul_grenier joconnor JPaton_ Matthew_Atkinson JF Regrets: Gottfried Found Scribe: Matthew_Atkinson Inferring ScribeNick: Matthew_Atkinson Found Scribe: becky Inferring ScribeNick: becky Scribes: Matthew_Atkinson, becky ScribeNicks: Matthew_Atkinson, becky Found Date: 02 Dec 2020 People with action items: grenier janina joshue 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]