Meeting minutes
Agenda Review & Announcements
janina: Basically our standard agenda.
New Charters Review https://github.com/w3c/strategy/issues?q=is%3Aissue+is%3Aopen+label%3A%22Horizontal+review+requested%22
<MichaelC> https://
MichaelC: Verifiable Credentials. Seem to be finally rechartering. Verifiable Credentials Data Model 2 and Verifiable Credentials 1.0 is what they will be working on. No liaison statement to APA.
janina: We do have a very strong need this tiem around to coordinate, not only to the updated CAPTCHA document but what they will be contributing to it (including a new name fo rthe document).
janina: We are already talking to several people in different groups concerning CAPTCHA activities.
janina: We want to explore a liaison.
MichaelC: I am drafting a response to them concerning liaison.
<MichaelC> APA would like a liaison documentation, worded something like "Coordinate on accessibility use cases for verifiable credentials, and work jointly on a successor technology to inaccessible CAPTCHAs."
MichaelC: That was the only thing on charter review.
Agenda Review & Announcements
A11y Review Comment Tracker https://w3c.github.io/horizontal-issue-tracker/?repo=w3c/a11y-review
MichaelC: SVG native a11y api. They are definitely for things like icons. They don't have animations and so forth.
MichaelC: The inability to use ARIA should not be an issue.
janina: qI propose we can sign off.
(Crickets.)
Matthew_Atkinson: It's very god to have their intent clarified as to what they want it to do.
janina: Does it need an a11y consideratiosn section saying just because this spec doesn't specifically address a11y doesn't mean you as an author are excused from your a11y responsibilities.
MichaelC: The SVG Native turns off so much that the a11y consideratiosn are almost the same as for PNG files.
janina: We seem to be pretty well covered in teh parent SVG spec.
MichaelC: this is what would be considered a "delta spec" and only wants to focus on the changes from the parent spec.
PaulG: It's taking a strictly better image format and reducing it to no better than any other image format. We should protect some level of text so that it is accessible to some a11y APIs and make it better than a PNG.
PaulG: There is no way to interface with a11y APIs even though it is XML and should be readable by a machine. It is nothing more than bitmap.
MichaelC: The introduction says why they did so much reduction.
PaulG: I strongly disagree that text as suchsi a web feature, though. Text is core to the OS.
janina: I don't think we're ready to sign off on this.
MichaelC: Who will volunteer to do a note to them?
new on TR http://www.w3.org/TR/tr-status-drafts.html
<MichaelC> https://
[For the last item, Matthew wil write the note for SVG Native.]
MichaelC: Probably very low level.
PaulG: They should have opened it up so that someone's AT could report probelsm with teh page.
janina: Lionel: Think of a unique page, they are collecting metrics arguably at the Edge. If the metrics are good...
PaulG: In the same vein as collecting certificate issues or performance prolems generated by a web app or site content, the browser, the user agent or additional addons and/or AT could interface int eh same manner with a11y related issues so that a site owner could be notified of problems bgenerated by their systems.
<MichaelC> https://
MichaelC: This is a WD, no timeline known.
Lionel_Wolberger_: You want to add the fact that a11y reporting would be valuable as well?
Lionel_Wolberger_: I'm very interested in this.
janina: Assign this to Paul, Lionel and me and we will make sure to get a hold of them to say that there is an a11y interest here.
MichaelC: Web of Things Thing description. They pinged us in January. We had previously reviewed this (or Josh had).
janina: I want to take another look.
janina: We'll take another week.
Dangling Spec Review Cleanup: https://www.w3.org/WAI/APA/wiki/Category:Spec_Review_Assigned
MichaelC: The main thing I wanted to cover was the WOT thing.
janina: We want to make sure that the middleware information is expoed ina programmatical way.
MichaelC: Just ot mention as spec review cleanup. WebXR thing that Josh has a comment for, cover that next week.
Matthew_Atkinson: Janina and I are looking at Media Source Extensions(tm). There are defeinitely some a11y issues with the spec itself. I have some draft comments, and give me another week.
janina: Let me amplify that. There are two kinds of comments. One is substantive comments with what the spec tries to do (see above concerning Reporting). Taht's substance of waht the spec covers. Tehn there is also the way the spec is presented. We want alt text for graphics, we want summery details for infographics and so forth.
janina: That's all missingi in this spec. This is a beginning point to introduce them to us. You, Matthew, don't have to cite every instance, but tell them that there are multiple instances of not doing the proper thing here.
janina: I am for sending that up to them rather soon. Multiple instances of these things missing is a problem.
<Lionel_Wolberger_> Lionel having connectivity issue. Will reconnect
new on TR http://www.w3.org/TR/tr-status-drafts.html
Matthew_Atkinson: It's a thougth experiment kind of thing. Say we have an SVG that has alt text inside it. The assumption is that when it gets presented in a native context, that would disappear because it would be stripped out.
Matthew_Atkinson: The platforms, however, have a11y APIs that could expose that on an image. I can't think of a platform that doesn't expose a11y information.
Matthew_Atkinson: Why not allow the platform to do this as an optional thing?
janina: Wouldn't it be simpler to support it an dallow it?
Matthew_Atkinson: The content author will ahve to provide the image file and a separate alt text conveyed somehow. Why not just expose what is in the file if there is an alt text? If your system can't, that's fine, but if your system can, it should.
janina: Are you saying that the web a11y information should be used through the native OS a11y APIs?
<PaulG> (also this: https://
Matthew_Atkinson: It's not that the OS can't dop it, but what renders the image is probably something that is from a 3rd party library like libsvg. They probably want to say that the existing renderers that have been around since time out of memory shouldn't suddenly be noncompliant.
PaulG: By taking text support out of SVG, we are making it less than PNG (which has text support built in). Nobody's taking out the text chunks of PNG, but atht seems liek a bad idea as well.
Matthew_Atkinson: That's brilliant, Paul.
Matthew_Atkinson: It's Paul's idea and he put it beautifully. If you, paul, perfer to and want to take it, you're welcome to do so.
PaulG: Happy to collaborate on that.
Dangling Spec Review Cleanup: https://www.w3.org/WAI/APA/wiki/Category:Spec_Review_Assigned
FAST and Maturity Model Deliverables Update
close item 5
<Matthew_Atkinson> zakim take up item 7
Task Force & Deliverables Updates
RQTF
janina: Last call on reviews!
<janina> https://
janina: We have gotten good comments. We didn't want to finalize the note. We suggest a month is adequate. Due date on comments is 13th May.
janina: After that we go to note status after a CFC. Tehn we'll see if we can go to W3C statement status.
janina: REmtoe Meetings was almost ready to go but then we pulled it back because we were all actively collaboratively editing a document in real time during a Zoom meeting. We did bump into lots of a11y issues.
janina: That has opened up issues which may result inour upcoming document. In organizing a meeting, it mibht be said in RM, one must be aware that there are a11y considerations and you should take these into account.
janina: We are looking at an eend of month publication for RM. Another wide review before we finalize it and a prospect that one of the next documents might be an overall review of the status of collaborative, browser-bsed or even inan app, documents.
janina: What are the challenges, what are the AURs that might need to get satisfied on that.
janina: That's the current RQTF status.
janina: Work on CAPTCHA goes on.
Personalization
Matthew_Atkinson: We're still working on addressing our i18n issues.
<Matthew_Atkinson> WAI-Adapt
Matthew_Atkinson: We have decided on a new name: WAI-Adapt.
Matthew_Atkinson: So, WAI-Adapt: <something> Module.
Matthew_Atkinson: We do have a couple of issues needing resolving, hte long standign i18n issue and another one that illustrated the need for clarification around the symbol attribute and so on.
Matthew_Atkinson: That is about it.
Pronunciation
PaulG: I missed last week, have to catch up.
janina: We are meetingm the Silver group looking at the issues with web for children (see last week's notes).
janina: We might be able to end there.
COGA
Fazio: We were seekign participation from an AAC user. Working onit.