<Judy> trackbot, thanks
<trackbot> You're very welcome, Judy.
<scribe> scribe: CharlesL
MC: WCAG 2.2 is coming soon.
JB: we will want to add a lot of
messaging for that release
... , can we use the 2.1 messaging more or less?
MC: will need to look at it more closer
JB: expectation setting would be
a good start for 2.2
... , probably more than for a typical update.
... , anything more Michael? Tzviya said nothing for her.
Janina?
... , maybe a FPWD for XAUR sets. MC nothing on aria or other
groups?
MC: aria 1.3 is coming up soon, and silver is coming up in Feb.
JB: those are FPWD so that is a
little more involved.
... , Janina anything from APA?
Janina: several things, from TF:
Research Questions, WebRTC on a 2.0 spec use-cases (pretty much
ready to go, go for CFC.
... , use-cases & requirements for XAUR
... , we have some use-cases and looking to the community for
more.
<Joshue108> http://raw.githack.com/w3c/apa/XAUR/xaur/index.html
<Joshue108> XAUR draft
<Joshue108> Accessible RTC Draft
<Joshue108> http://raw.githack.com/w3c/apa/AccessibleRTC/rtc/index.html
Janina: , personalization TF
looking for wide review for module 1, close to CR status and
wide review which is important for 2.2 since its once of its
dependancies.
... , pronunciation TF looking at text to speech, gap analysis
and adding an explainer, and discussed with Lieone during out
call today. looking to get this to a FPWD even for the
explainer as up to date as we can.
JB: thank you Janina.
... , effects of WCAG 2.2 is that supporting something already
in play. MC you are up to date on that correct?
MC: I don't recognize the title.
Charles: simplification I believe that is the WCAG dependancy.
MC: this is currently an at-risk until the personalization module 1 goes to rec.
Judy: if you are confident that the timing will work, but if you haven't confirmed that you are in sync. dependance, so you may need to be ahead of WCAG.
MC: I haven't seen a draft of the success criteria, but it may be at risk.
JB: other work has been held up in the past when parallel in the past.
Janina: I think we talked timelines in TPAC.
MC: I do remember thinking we are good, but we need to check on timing , we are not focusing on the timeline you are working on, but you want a success criteria for this hasn't been proposed to the group, we would need the techniques referencing the work you are doing in personalization.
Judy: this is important, could I ask you both Janina & Michael maybe Charles, and and timing expectations and checkin points so it stays coordinated.
MC: Yes I can be there and Charles needs to be there.
Judy: Janina you talked about 3 or 4 documents at the same time, and Joshue you may remember this. The group of folks XUAR is this another set of guidelines / requirements so it could be miss understood. if we are introducing RTC usecases if these are new kinds of documents in the WAI space we may need a general blog explaining all of this.
Joshue: we need to be precise in our messaging, and bigger question emerging tech useful information and how this fits into WCAG / Silver we need to coordinate for sure.
JB: Janina, any comments for you on who your audiences etc.
Janina: Yes I have talked to everyone and messaging is important
JB: does anyone spot any intersections with your work? Aira connections, publishing etc. XUAR, Personalization and pronunciation etc.
Tzviya, if you have a link to the pronunciation work because we are working on audio publications. Marisa has been paying attension.
JB: I know of audible.com, is there an expectation/timeline for pronunciation / Narrator unless emotional markup language. does W3C need to pay attention to
Tzviya: right now there is a real desire for human voice, that is what is selling.
JB: this will be in late march
24/25 a11y will be discussed.
... , critical for people for a11y issues to be discussed at
this workshop.
... , OCAD university I will bring this to their attention.
Janina, I am going to look into this personally intersted.
Kathy: David ONeil on TPG side is an expert in ML and AI
JB: can you mention that to him?
Kathy: Yes, I will send an email and cc you.
JB: yes there is also a link in
the agenda
... , workshops are critical for joining w3c, so it is critical
for having these accessibility concerns.
Josh: It looks interesting, but I would need to go in order to see what is needed in that space.
JB: we can talk about that
offline. may be a good place for us to dive into.
... , anyone else of people to bring into this discussion?
Tzviya: Publishing is interested
(consumer side) and will bring this to the group.
... , I need to do more reading on it and will pass it along to
WG.
JB: getting a11y added to the scope for these new emerging WG chaters.
Tzviya: I don't think there is
much to report on. the audio books Candidate release in
November, we are working on testing now. we will add a note on
the packaging. checkins are how testing is going. not a lot of
feedback. EPUB is holding steady the Publishing Steering
committee is having a F2F in Feb. the Publishing WG charter is
up in July, so discussions on that what happens next is
... , will EPUB will become a rec track or hold steady? so lot
up in the air.
Charles: community group working on a Best practices on discoverability of accessible EPUB and its metadata
JB: are you missing any connections with other groups? is there any additional intersection. maybe there is nothing.
Tzviya: I am pretty comfortable,
dpub-aria is what it is, but I think we have worked it out with
associated documents
... , working with james and Joanie on our needs.
JB: this has been covered a
little with the upcoming documents. anything to
highlight?
... , fairly high volume of RTC / XAUR.
Janina: verifiable credentials is another area we are looking into
JB: AR in VR and very specific
things that would be a benefit in that combined env.
... , looking at objects and have an AR in the VR space (remote
collaborative work) could introduce a new user need as we would
need to be accessible.
... , Josh does XUAR cover this?
Josh: No it wouldn't cover
it.
... , AR within VR is a technical implementation. a mix
... , implementation detail maybe?
JB: I think it may go beyond an
implementation detail. Micro apps may be a place for this
... mini-apps and AR/VR combined and it may cross several
areas. we may introduce it into XAUR, and maybe its not the
right place. Does anyone have thoughs? Janina?
Janina: not immediately.
JB: to working on a document in VR.
Josh: collaborating on modeling you could have engineering a part for a car etc. and someone with a disability could also collaborate if their AT could interact with the VR/AR abstraction.
JB: there may be some ARIA support needed.
Joanie: Let us know happy to help.
JB: does anyone have info share for today?
<scribe> …, new focus that may have implications for other groups?
UNKNOWN_SPEAKER: , none..ok.
Janina: conversational
interfaces
... , I don't have the URI handy, but there is a CG on
that.
... , will reach out once we got the explainer for
pronunciation
JB: focus on when we need someone to plug in.
Josh: privacy space that I joined
Ping.
... , privacy and a11y and will have some role, but discovery
phase right now. now tracking that group from now on.
JB: a11y / privacy intersection or 3 things Privacy/security/a11y together or all 3?
Josh: I think it is all 3.
JB: Yeah!
JB: which groups are meeting that
are not squared away.
... , I think it is set but any issues for these F2F
meetings?
Janina: Silver is meeting is covered, all food, space, timing etc. all done
JB: we are at the time we need to
announce since 2 months out now.
... , can you send out this to this mailing list.
MC: announcement sent out to silver mailing list
JB: I think we need to make a
broader announcement including this list
... , any other groups to confirmed to meet.
Steve: Shawn H. for EO to meet on
Mon/Tue but hasn't been announced yet and still need to get the
details sorted.
[post-meeting correction: The EOWG meeting was confirmed with the EOWG Working Group in December 2020 and announced via agenda, teleconference, and EOWG F2F Meetings wiki page. (It's now also in the W3C calendar.)]
JB: isnt there. a 3rd.
MC: Accessibility Guidelines were going to meet but decided to cancel for Silver.
Steve: COGA was going to meet at the end of Silver.
JB: how active are the Mobile and Low Vision TF in AGWA?
??: Finalizing techniques for 2.2 and trying to decide next phase, getting remaining 2.2. SC finished.
JB: mobile and VR intersections?
??: we haven't yet but happy to look into it.
JB: may need to get Hardware support. certain issues that could introduce new angles to a11y.
MC: AIRA authoring practices WAI tutorials format. not sure if morphing … central way resource self consistent covering a broad set of topics and LV should be aware.
JB: looking for consistent approach unified format for supplemental guidance in a coordinated way.
Steve: nothing to add, big picture ideas at the moment.
This is scribe.perl Revision: 1.154 of Date: 2018/09/25 16:35:56 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/zower/XAUR/ Succeeded: s/more for a/more than for a/ Succeeded: s/audio.com/audible.com/ Succeeded: s/XUAR/XAUR/ Succeeded: s/UTC/RTC/ Succeeded: s/Jose/Josh/ Present: stevelee KathyW Joanmarie_Diggs Katie_Haritos-Shea Joshue108 tzviya__ CharlesL janina Rachael Judy Found Scribe: CharlesL Inferring ScribeNick: CharlesL WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth Found Date: 15 Jan 2020 People with action items: 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]