Meeting minutes
Agenda Review & Announcements
janina: Agenda flow changed because of the shift betwween Michael and Roy being our staff contacts. Michael is still our senior staff contact.
github repositories moved -- Roy
<Roy> https://
Roy: Cocnerning our Github repository for the APA.
Roy: Formerly we used the repo for our developing documents.
<Roy> https://
Roy: We have decieded to split all deliverables into their own repos.
Roy: I have already done this work. Here is a list to show the new repo address.
Roy: TAll pull requests, issues and comments have already been transferred to their correct repos.
Roy: Still some work to do on this, but progressing smoothly.
janina: all with the object of simplifying hiearchies.
New Charters Review https://github.com/w3c/strategy/issues?q=is%3Aissue+is%3Aopen+label%3A%22Horizontal+review+requested%22
MichaelC: No new charters this week.
A11y Review Comment Tracker https://w3c.github.io/horizontal-issue-tracker/?repo=w3c/a11y-review
<MichaelC> https://
<MichaelC> https://
MichaelC: WebXR a11y overview doc. Someone recently flagged it to our attention while also saying it has been completed.
MichaelC: I think, from a review comment tracker perspective, this should be closed. Do we want to review this thing maybe?
janina: Maybe. WebXR has a separate item further down. Josh?
Joshue108: I would keep an eye on it I guess.
janina: Any time sensitivity on this?
MichaelC: I donät know. I think itäs reasonable for us to take a few weeks.
Fredrik: Iäd do it.
<Joshue108> Fredrik to review
ACTION: Fredrik to review https://
<trackbot> Created ACTION-2320 - Review https://
MichaelC: Nothing more of substance.
new on TR http://www.w3.org/TR/tr-status-drafts.html
Dangling Spec Review Cleanup: https://www.w3.org/WAI/APA/wiki/Category:Spec_Review_Assigned
MichaelC: I think itäs just the ones assigned...
MichaelC: I18n glossary. lionel took this one.
lionel: Everything paused until next week.
MichaelC: Paul had a spec as well.
PaulG: Iäve recorded my actions on that.
<MichaelC> https://
MichaelC: I looked through the new active specs (meaning something has happened).
MichaelC: The first oen is POE Use Cases and Requirements. WG is closed and the spec is hibernated.
janina: Sounds like we can abandon this.
MichaelC: I don't know that htis is advancing anywhere.
MichaelC: Skipping WebXR.
<MichaelC> https://
MichaelC: WebRTC Encoeded Transform. Will close that.
<MichaelC> https://
janina: I need to contact them.
MichaelC: Moving back to assigned because of middleware question.
<MichaelC> https://
MichaelC: Notifications API. We filed an issue with them 4½ years ago and had a meeting with them at TPAC. Nothing is recorded since then.
<MichaelC> https://
janina: We had a joint meeting on a teleconference here.
janina: It's a WHATWG spec and we can negotiate with them about this. There is an a11y consideratiosn section probably failing.
Fredrik: I'll have a look at it as well.
ACTION: Fredrik to draft a11y considerations on https://
<trackbot> Created ACTION-2321 - Draft a11y considerations on https://
MichaelC: That is it!
FAST and Maturity Model Deliverables Update
FAST
Joshue108: We met during the week with the a11y for Chidlren CG. They are interested in our work and they highlighted a little about what is interesting about children and a11y and cognitive disabilities and so on.
Joshue108: They are quite interested inteh matrix that we have, the user needs and requirements. WE took them a little throught his. They will work off our main functional needs document.
Joshue108: They will develop their own functional and user needs documents which we can then incorporate into our documents.
MichaelC: The functional needs subgroup has been workingon this matrix of functional categories and user needs as part of trying to figure out how WCAG2 success criteria might fit into WCAG3.
MichaelC: This also included breaking them down into slices in order to try to have versions that matter only to one type of content or to one type of test. Then we coudl take those slices and fit them into WCA3 in different ways.
MichaelC: It's an attempt to get things from one space to another so to speak. No one is committing to anything, but some of us are finding it a useful way to think about things.
janina: One issue that kind of jumped out of the work of this group that is focusing on the needs of children came to the attention of Pronunciation. There might be solid use cases to say that when you do TTS you should do a child's voice.
janina: We don't have any way to specify that.
janina: The use cases laid out are as folows: among other thigns in pronunciation we are trying to lock in hwo you say something. It's more than just heteronyms and abbreviations.
janina: One that keeps coming up is pronouncing historical content. Does the language tag in HTML suffice to identify a language for TTS purposes? I have become confinced that is does not.
janina: Soem language will even split out specific dialects. What none of these codes do is provide anything historical. The argument is that Shakespearean English isn't pronounced like current English, neither is koine Greek pronounced the way today's Greek is.
<Fazio> that was going to be my question: how important is this?
janina: Koine Greek was the lingua franca of the Roman empire, in case you didn't know.
janina: We might need something time based. If we can buidl it into a set of rules or a TTS engine to be called up by a tag.
janina: With TTS increasingly becomign an a11y requirement but also a mainstream technology, historical pronunciation, accurate pronunciation may be useful. Build in the children's group here - you want to be able to contemporise English but you also want a child's voice.
janina: You need the letter-ladies to make the children comfortable with the communciation. We have a little researching to do.
janina: We have to validate the premise that this doesn't exist curently in Unicode, ISO or any other standard pertaining to the subject. We are rapidly getting to a web-based world where we need that kind of identifier.
janina: FYI: we're emerging anothe rrequirement that is probably coning to be an APA-I18n conversation during tPAC.
Lionel_Wolberger_: I find these issues very important and we need dto sort through them quickly and find out where they belong paygradewise.
Lionel_Wolberger_: The built environment is not made for hildren, most homes aren't, and TTS and screen readers aren't made for children either. It's deep.
Lionel_Wolberger_: I went through all community groups to find out which a11y groups are alive and which not. It's good to hear that thte children's a11y is.
Lionel_Wolberger_: We could ask the screen reader companies about TTS and other technologies for and/or by children.
Lionel_Wolberger_: Children tend to respond to children's voices.
Lionel_Wolberger_: That CG thing, we can let that simmer. I would like to capture that the Children CG is active.
janina: We have a list somewhere. Lionel took a look.
Lionel_Wolberger_: I doidn't mean to say TTS and SR are not primarily made for children. The voices aren't made for children, or have childrenh's voices.
Lionel_Wolberger_: There is also a number of companies doing speech to text work.
Fredrik: Don't mix up engines for the creation fo speech and the voices themselves.
<Fazio> cochlear implants too
Lionel_Wolberger_: It is in our scope to understand voice recognition and uiquitous computing, understanding people who cannot form consonants and vowels, epope who have musculars disorders and so on. some private companies with very promising technologies which are succeeeding in understanding highly differently formed speech.
Lionel_Wolberger_: Also, what you might heare form a d/Deaf person learning to speak, those kinds of consonatns and vowels.
<Fazio> that creates attentional set
<Fazio> it's a cognitive process
janina: With any of those conditions that Lionel named (it could be cultural as well, sociolects and so on). Would it be useful in teaching children to read if you show them standard written text but give them pronunciation closer to what they would speak?
janina: I can almost see an agenda for our meeting with i18n forming.
Fazio: This is importnat ot the attentional set. We creat our images of how soemthing will look based on past experiences. In our minds we have an attentioanl set we react to in terms of understanding.
WebXR Open Issues -- Josh
WebXR
Joshue108: The purpose of this is to walk through some of hte comments I have posted on different specs of WebXR.
Joshue108: I have sent a few pings to the list. I'll go through each one.
<Joshue108> WebXR DOM Overlays Module FPWD
Joshue108: WebXR DOM Overlays.
Joshue108: This module descirbes a mechanism for showing interactive 2D content during a VR experience. Thsi DOM Overlays module can be quite useful rfor rendering semantics within an XR environment.
<Joshue108> https://
jsohI had some questions relating to this.
Joshue108: My concerns were that the APA has reviewd the spec. If this module is content accesible.. If this module can be used as a container for accessibility semantics. And if this has been considered.
Joshue108: I worte this response six months ago.
Joshue108: There are three of these comments. One has been dealt with.
janina: Anyone mind forwarding those right now as they are?
Joshue108: Michael had some comments here. He made some comment about this before.
janina: We give better responses when we can suggest solutions. Sometimes, thoguh, we simply don't know the answer.
Joshue108: This is an imporntat hook for a11y technolgoies in XR environments.
janina: Is the Silver groupon XR still active?
Joshue108: At least I haven't been active on it for a while.
janina: We are looking for someone who would be in a position to follow up on XR issues.
Joshue108: URIs are in the minutes here, they can be used as bthe basis for more detailed repsonses if you like.
Joshue108: The next one is the review of the WebXR Hit Test module.
<Joshue108> WebXR Hit Test Module FPWD
<Joshue108> https://
Joshue108: This describes a mechanism to allow WebXR apps to ccast rays into the user's environmetn. It's essentialoloy hit testing in the user's environment.
Joshue108: When a signal from an AR defice hits something the real world, soemthing can be put upon that surface.
Joshue108: It is rather low level. My point is that it bubles fast, it becomes important quickly.
Joshue108: It has privacy implications as well if you ahve the capabilities of scanning a user's environemtn.
Joshue108: I did a boilerplate response.
Joshue108: I think we would want to flag privacy as a concern. There are however more sensitivtiies with PWDs.
Joshue108: There may also be issues related to orientation with this module.
<Joshue108> WebXR Layers API Level 1
<Joshue108> https://
Joshue108: WebXR Layers API Level 1.
<Joshue108> https://
Joshue108: It is kind of resolved. I posted an issue in the immersive Web Grpouip Github relating to this.
Joshue108: We had this question aroudn the resolution aroudn eye buffers.
Joshue108: Would this lead to issues for people with captions or legibility issues in such a setting?
Joshue108: That was all on that Github and it is still an open issue.
janina: Captions could conceivably be rendered at another resolution even if the background is downsampled?
Joshue108: Basically, yes.
Lionel_Wolberger_: I was absorbing the WebXR Hit discussion. I recalled our original discussion. Your response in teh summary didn't cover, I could be wrong, if I put rays in my environment and the reays rays find that I'm sitting in a wheelchair, that is a kind fo privacy that would be a concern, right?
<Lionel_Wolberger_> "APA are asking if there any aspects of how assistive technology may use or interact this the dynamics of this module that are of concern?"
Joshue108: jAll of these things increase the fingerprinting surface. We need to be careful with people's privacy.
Joshue108: That's basically it from my side.
<Lionel_Wolberger_> Our privacy concern goes to the fact that rays in the user's environment may detect artificial limbs, wheelchairs, canes and other artifacts that would reveal highly private information.
janina: Thanks for that in particular and thanks for all you've done in all the last years.
Joshue108: I will be back in any shape or form.
janina: I know there a re a couple of actions due next week - one of them ine.
janina: Quick reminder of the actions page.
<janina> http://
janina: TPAC: We did respond. There will be others. We will create our own page soon. Not yet. Today we had a good conversation about i18n. We do expect a good number of us will be in Vancouver.