Meeting minutes
Agenda Review & Announcements
(no announcements)
New Charters Review https://github.com/w3c/strategy/issues?q=is%3Aissue+is%3Aopen+label%3A%22Horizontal+review+requested%22
MichaelC: No new charters
A11y Review Comment Tracker https://w3c.github.io/horizontal-issue-tracker/?repo=w3c/a11y-review
Web of Things (WoT) Thing Description 1.1
<MichaelC> https://
<MichaelC> https://
Web of Things (WoT) Thing Description 1.1
janina: ready for review
janina: Have been dealing with this for years. Should be done by next week.
… Identify implications of the eco system, "middleware".
Matthew_Atkinson: Does anybody remember?
… They used "middleware" in their reply.
https://
janina: Voice assistance is very common nowadays
Matthew_Atkinson: We need to respond and keep it going
new on TR http://www.w3.org/TR/tr-status-drafts.html
A11y Review Comment Tracker https://w3c.github.io/horizontal-issue-tracker/?repo=w3c/a11y-review
WebXR Device API
<MichaelC> https://
<MichaelC> https://
WebXR device API
VISS version 2 - Core
<MichaelC> https://
<MichaelC> https://
<MichaelC> https://
Fredrik: Not done yet.
VISS version 2
Fredrik: The VISS looks okay.
… Best practices doc contains a list of accessibility issues. Would require a task force.
… Looks like there is a strong buy-in from stakeholders.
janina: We met with them in person, before COVID.
… They wanted a11y use cases and requirements from us, but not for fully autonomous vehicles.
… Entertainment systems in vehicle are out of scope.
… We ended up kind of dropping this.
Fredrik: Action item could be the starting point of an accessibility user requirements (aur).
janina: We need to recruit for it.
janina: Maybe RQTF could take this up. Can talk to Jason about this.
… Would add more people to this conversation.
… RQTF has deaf and hoh participation.
Fredrik: Better to work on this with others.
janina: Michael, let's put something together.
… Continuing discusson on APA and how to be more helpful.
Reporting API 1
<MichaelC> https://
<MichaelC> https://
<MichaelC> https://
Reporting API 1
janina: It relates to http headers.
MichaelC: Let's leave this open for now, since Lionel is not here.
Matthew_Atkinson: Is this Paul's thing about accessibility end point.
<Matthew_Atkinson> This is Paul's draft comment: https://
Matthew_Atkinson: If Lionel has been looking at this, we need to combine it.
janina: It is a strong suggestions. Many interesting ways to leverage.
PaulG: Lighthouse...
Matthew_Atkinson: Not sure how much needs to be specified. Maybe just come up with an identifier.
janina: Maybe a standardized identifier. We need a reporting mechanism, a pipeline.
Matthew_Atkinson: An extension mechanism.
janina: Standardize, opportunity to customize
… Slowly growing participation from overlay sector.
Matthew_Atkinson: Paul suggests there are multiple uses of it.
janina: People with engineering perspective should look at this.
Matthew_Atkinson: We need to hear from Lionel.
MichaelC: We are on open review comments.
janina: Looks like we have time for that.
new on TR http://www.w3.org/TR/tr-status-drafts.html
W3C TAG Ethical Web Principles
<MichaelC> https://
<MichaelC> https://
MichaelC: Accessibility is referenced briefly. Not sure we need more.
janina: If this is the same treatment as the other specs, i am content.
MichaelC: It is just documentation. Link to WAI home page.
… Section "Web is for all people". https://
PaulG: In section 2.4: "the platform should enable a fully accessible end user experience". But nothing is fully accessible.
Matthew_Atkinson: Omit "fully"
MichaelC: Comment?
Matthew_Atkinson: It is pedantic, but a high-level doc should be correct.
janina: Silver would like this to be fixed.
… One of the core arguments of the challenges doc
<Fazio> +1 Janina
Fredrik: I volunteer for it.
Privacy Principles
<MichaelC> https://
<MichaelC> https://
ACTION: Fredrik to draft a comment on Reporting API by 2022-06-01. https://
<trackbot> Created ACTION-2323 - Draft a comment on reporting api by 2022-06-01. https://
action-2323 due 2022-06-01
<trackbot> Set action-2323 Draft a comment on reporting api by 2022-06-01. https://
Privacy Principles
MichaelC: Fingerprinting is the issue
PaulG: There is a wording on this - should be covered
MichaelC: So we just sign off
Web of Things (WoT) Architecture 1.1
<MichaelC> https://
<MichaelC> https://
<MichaelC> https://
MichaelC: We haven't reviewed this doc yet.
janina: Doc must be advancing towards CR.
MichaelC: They say the editor's draft is more current.
ACTION: janina to review Web of Things (WoT) Architecture 1.1 https://
<trackbot> Created ACTION-2324 - Review web of things (wot) architecture 1.1 https://
MiniApp Manifest
<MichaelC> https://
<MichaelC> https://
<MichaelC> https://
<MichaelC> https://
action-2324 due 2022-06-01
<trackbot> Set action-2324 Review web of things (wot) architecture 1.1 https://
Roy: Will do.
Roy: I can do a presentation on miniapps.
<PaulG> noting that "label" which is listed as accessible text in miniapp schema is not required
Lionel_Wolberger: I am now here.
Reporting API 1
Lionel_Wolberger: Hard to read, very abstract.
… It meets a need if there is a failure on the user side.
… Compelling if you are a web provider.
… Happens behind the scenes.
<Matthew_Atkinson> Lionel's email to the list on his review: https://
E.g. failed certificates, CORS problems
… Perhaps we can talk about a11y failures here?
Matthew_Atkinson: Paul responded to this earlier.
<MichaelC> https://
PaulG: Opportunity for inclusion. Accessibility endpoint.
… May build on Accessibility Conformance Testing (ACT).
… Extra precautions for data security.
Lionel_Wolberger: Endpoints could be used to put this on a higher level.
janina: Could be really powerful.
… Adding accessibility as another pipeline. Standardized reporting mechanism.
… Vendor-specific extensions possible.
Lionel_Wolberger: To my understanding, industry will support this.
… Currently, we rely on accessibility statements.
… Service providers should have an interest to know about accessibility failures.
… Standardized across all platforms.
… Users can report about accessibility issues.
PaulG: Reporting API endpoint could point to a third party.
Matthew_Atkinson: What are our next steps?
janina: I would like APA to take this on. Paul, can you beef up your comment? Get the conversation going.
… Maturity model should take notice of this.
<Lionel_Wolberger> +1
ACTION: PaulG to draft a CfC for an accessibility endpoint on the Reporting API spec due 2022-06-01
<trackbot> Created ACTION-2325 - Draft a cfc for an accessibility endpoint on the reporting api spec due 2022-06-01 [on Paul Grenier - due 2022-05-25].
action-2325 due 2022-06-01
<trackbot> Set action-2325 Draft a cfc for an accessibility endpoint on the reporting api spec due 2022-06-01 due date to 2022-06-01.
Dangling Spec Review Cleanup: https://www.w3.org/WAI/APA/wiki/Category:Spec_Review_Assigned
MichaelC: We can move on.
Task Force & Deliverables Updates
RQTF
janina: Remote meetings is out for wide review comments
https://
janina: Two years of COVID experience in this...
Coga
Fazio: Two sessions at ICCHP conference.
… Project room at ICCHP conf.
Pronunciation
PaulG: Talking about use cases with accessibility for children community group.
Adapt
Lionel_Wolberger: Renaming going smoothly. Focusing on TPAC - no breakout meetings alone.
<Fazio> I now have access to Pronunciation
Actions Checkin (Specs) https://www.w3.org/WAI/APA/track/actions/open
TPAC22 https://www.w3.org/WAI/APA/wiki/Meetings/TPAC_2022
Matthew_Atkinson: Haven't seen any requests for joint meetings yet.
… We will send this information later this week. If you have any last-minute requests let us know.
… TPAC organizers asked us to provide input on whether the following events would be of interest to us.
<Matthew_Atkinson> List of events at end of this form (which you don't need to fill in; we will): https://
Options:
Technical plenary with a few high level presentations Place for demos Hackathon Workshop Developer meetup to include local community - evening event Training overview on W3C technologies Other
Fazio: Two tracks by California...
(too fast to minute)
Matthew_Atkinson: Developer meetup should be good.
Fazio: Coga-Workshop with "Content usable"?
janina: You did that last year.
Fredrik: When is the deadline for proposing these events?
Matthew_Atkinson: This is now only to assess interest. You can propose the sessions later.
Matthew_Atkinson: adjourned