- From: Matthew Atkinson <matkinson@tpgi.com>
- Date: Wed, 1 Mar 2023 15:56:08 +0000
- To: Janina Sajka <janina@rednote.net>, W3C WAI Accessible Platform Architectures <public-apa@w3.org>
Hi all,
Thanks to Paul for co-scribing. The minutes are at https://www.w3.org/2023/03/01-apa-minutes.html and repeated below in plain text for convenience.
Best regards,
Matthew
– DRAFT –
APA Weekly Teleconference
01 Mar 2023
[2]IRC log.
[2] https://www.w3.org/2023/03/01-apa-irc
Attendees
Present
Fazio, Fredrik, Gottfried, janina, Lionel_Wolberger,
matatk, mike_beganyi, niklasegger, PaulG, present, Roy
Regrets
Alisa_Smith, Fredrik_Fischer
Chair
Janina
Scribe
matatk, PaulG
Contents
1. [3]Agenda Review & Announcements
2. [4]Coming Clock Changes https://www.timeanddate.com/time/
dst/2023a.html
3. [5]Agenda Review & Announcements
4. [6]APA Charter CfC Reminder https://lists.w3.org/Archives/
Public/public-apa-admin/2023Feb/0025.html
5. [7]Proposed WoT Comments & Matter/Thread https://
lists.w3.org/Archives/Public/public-apa/2023Jan/0000.html
6. [8]CSS Update (Paul) https://github.com/w3c/css-a11y/issues
7. [9]Agenda Review & Announcements
8. [10]APA Charter CfC Reminder https://lists.w3.org/Archives/
Public/public-apa-admin/2023Feb/0025.html
9. [11]New Charters Review https://github.com/w3c/strategy/
issues?q=is%3Aissue+is%3Aopen+label%3A%22Horizontal+review+
requested%22
1. [12]Media Working Group Rechartering
10. [13]Explicit Review Requests https://github.com/w3c/
a11y-request/issues
1. [14]Digital Publishing WAI-ARIA Module 1.1 and Digital
Publishing Accessibility API Mappings 1.1
2. [15]PNG 3rd edition
11. [16]A11y Review Comment Tracker https://w3c.github.io/
horizontal-issue-tracker/?repo=w3c/a11y-review
12. [17]Actions Checkin (Specs) https://www.w3.org/WAI/APA/
track/actions/open
13. [18]Task Force & Deliverables Updates
1. [19]Maturity Model
2. [20]Pronunciation
14. [21]Other Business
15. [22]be done
Meeting minutes
Agenda Review & Announcements
janina: there are 2 key announcements which have their own
agenda items
… any additional announcements?
Coming Clock Changes [23]https://www.timeanddate.com/time/dst/
2023a.html
[23] https://www.timeanddate.com/time/dst/2023a.html
janina: through March, 11-12 times change in America and calls
will be an hour earlier until times change in Europe
Agenda Review & Announcements
APA Charter CfC Reminder [24]https://lists.w3.org/Archives/Public/
public-apa-admin/2023Feb/0025.html
[24] https://lists.w3.org/Archives/Public/public-apa-admin/2023Feb/0025.html
janina: reminder to CfC for our charter draft is open until
midnight tonight
Proposed WoT Comments & Matter/Thread [25]https://lists.w3.org/
Archives/Public/public-apa/2023Jan/0000.html
[25] https://lists.w3.org/Archives/Public/public-apa/2023Jan/0000.html
janina: there's a new spec affecting WoT to certify devices
that would solve some of our issues
Gottfried: I'm not sure how much we can do about Matter. It's
going to be the standard. Thread is the low-level standard for
transmission.
… WoT is sort of a competitor to Matter
janina: it's from a separate organization but it might be
helpful to the problems we've identified we call "middleware"
… aggregation technology should be helped by it
Gottfried: I haven't looked into Matter in depth, the issues
remain the same but the technology has advanced and industry
seems ready to collaborate
… I think the Matter standards is just a roof on the other
standards
… to allow better interop
… do we plan to talk to Matter experts or WoT developers?
janina: I think we should take our concerns to WoT as the
experts we've worked with before
… we can ask them to clarify or to have a joint meeting on our
concerns
Gottfried: I still see this as a competitor standard
… I don't think there's space for two
Gottfried: I support talking to WoT as they probably have a
better idea of how they stand compared to Matter
Gottfried: I'm thinking about how you find devices in public
spaces which is mostly neglected by developers
… which affects accessibility
janina: I'll take an action to send a note to them
niklasegger: I agree that Matter could be the "winner" here
after doing some research. Security is a big reason for it.
Gottfried: it could get extended to work in public spaces
Lionel_Wolberger: I would add that Meta has an unsolved problem
to present the data of the environment around us
… WoT will mean actual physical interaction in space not just
"I see WiFi near me"
CSS Update (Paul) [26]https://github.com/w3c/css-a11y/issues
[26] https://github.com/w3c/css-a11y/issues
[27]w3c/csswg-drafts#7761
[27] https://github.com/w3c/csswg-drafts/issues/7761
PaulG: This is how outline style differs across browsers due to
a fuzzy part of the spec. This can affect the focus ring.
… The group resolved to change the spec: [28]w3c/
csswg-drafts#7761 (comment)
… This doesn't conflict with anything in WCAG. They've done
research to ensure it won't break accessibility. Should be more
consistent across UAs as a result.
… There will be more debate on this as UAs implement it, but
the change is due to happen.
[28] https://github.com/w3c/csswg-drafts/issues/7761#issuecomment-1440512109
Agenda Review & Announcements
APA Charter CfC Reminder [29]https://lists.w3.org/Archives/Public/
public-apa-admin/2023Feb/0025.html
[29] https://lists.w3.org/Archives/Public/public-apa-admin/2023Feb/0025.html
New Charters Review [30]https://github.com/w3c/strategy/
issues?q=is%3Aissue+is%3Aopen+label%3A%22Horizontal+review+requested%2
2
[30] https://github.com/w3c/strategy/issues?q=is:issue+is:open+label:"Horizontal+review+requested"
Media Working Group Rechartering
<Roy> - charter: [31]https://w3c.github.io/charter-media-wg/
[31] https://w3c.github.io/charter-media-wg/
Roy: The charter mentions accessibility and APA.
matatk: I like this part "Each specification should contain a
section on accessibility that describes..." :-)
janina: We've had a long and good relationship with this group,
going back to HTML5 developent.
Roy: They noted the FAST, too.
janina: I have no concerns; others?
<Lionel_Wolberger> +1 great that the FAST is explicitly listed
Explicit Review Requests [32]https://github.com/w3c/a11y-request/
issues
[32] https://github.com/w3c/a11y-request/issues
Digital Publishing WAI-ARIA Module 1.1 and Digital Publishing
Accessibility API Mappings 1.1
<Roy> - issue: [33]w3c/a11y-request#55
[33] https://github.com/w3c/a11y-request/issues/55
<Roy> - URL of spec:
<Roy> - [34]https://www.w3.org/TR/2023/
WD-dpub-aria-1.1-20230222/
[34] https://www.w3.org/TR/2023/WD-dpub-aria-1.1-20230222/
<Roy> - [35]https://www.w3.org/TR/2023/
WD-dpub-aam-1.1-20230223/
[35] https://www.w3.org/TR/2023/WD-dpub-aam-1.1-20230223/
Roy: They want to publish these as CR next month.
janina: We are generally OK with these, as we know ARIA knows
their stuff, unless anyone wants to dive into these?
… This is about mapping ARIA semantics into DPUB, and the AAM
is about how those mappigns are instantiated across different
platforms.
matatk: I'm looking out of interest (relating to the Landmarks
extension).
<Lionel_Wolberger> The landmark extension is available at
[36]https://chrome.google.com/webstore/detail/
landmark-navigation-via-k/ddpokpbjopmeeiiolheejjpkonlkklgp
[36] https://chrome.google.com/webstore/detail/landmark-navigation-via-k/ddpokpbjopmeeiiolheejjpkonlkklgp
PNG 3rd edition
<Roy> - TR: [37]https://www.w3.org/TR/2022/WD-png-3-20221025/
[37] https://www.w3.org/TR/2022/WD-png-3-20221025/
<Roy> - tracking: [38]https://www.w3.org/WAI/APA/wiki/
Portable_Network_Graphics_(PNG)_Specification_(Third_Edition)
[38] https://www.w3.org/WAI/APA/wiki/Portable_Network_Graphics_(PNG)_Specification_(Third_Edition)
matatk: Re Landmarks, you can get it for multiple browsers,
too: [39]https://matatk.agrip.org.uk/landmarks/ - On Firefox
(and Opera) it has a sidebar.
[39] https://matatk.agrip.org.uk/landmarks/
<Roy> [40]w3c/a11y-request#42
[40] https://github.com/w3c/a11y-request/issues/42
matatk: Wanted to confirm there was a way to do textual
metadata (remember our SVG Native review); according to their
FAST report, there is: [41]w3c/PNG-spec#228 (comment)
[41] https://github.com/w3c/PNG-spec/issues/228#issuecomment-1279341797
janina: Sounds like we're good with this one.
Roy: Will close
A11y Review Comment Tracker [42]https://w3c.github.io/
horizontal-issue-tracker/?repo=w3c/a11y-review
[42] https://w3c.github.io/horizontal-issue-tracker/?repo=w3c/a11y-review
Roy: Nothing new this week, and nothing on TR this week.
Actions Checkin (Specs) [43]https://www.w3.org/WAI/APA/track/actions/
open
[43] https://www.w3.org/WAI/APA/track/actions/open
matatk: [44]https://lists.w3.org/Archives/Public/public-apa/
2023Feb/0035.html
[44] https://lists.w3.org/Archives/Public/public-apa/2023Feb/0035.html
matatk: Fredrik's review of EditContext API - [45]https://
www.w3.org/TR/edit-context/
[45] https://www.w3.org/TR/edit-context/
matatk: Sounds overall very good from Fredrik's review, but it
lacks an accessibility considerations section.
… We should ask for one if there's no obvious parent spec?
janina: Fredrik's already written a proposed section; we could
just ask them to include that.
matatk: +1
janina: I'm inclined to ask Fredrik to ask the editors of that
document to include his proposed section, noting that we're
finding it increasingly useful to have these appendices.
janina: Any objections?
Roy: I think we can file an issue in their GitHub repo. This is
a FPWD FYI.
janina: +1; thanks Roy
Task Force & Deliverables Updates
Maturity Model
janina: Several new members! They're working through issues.
Not sure if there's yet a sense of when a new milestone WD will
be published, maybe soon.
Pronunciation
janina: Activity is ongoing to engage with ARIA regarding their
latest proposal, and then with AT vendors regarding the group's
proposed course of action.
Other Business
Roy: Will we have a WG meeting during CSUN week?
janina: TFs can decide for themselves. Is anyone aware of a
reason for APA to _not_ meet?
<Roy> [46]"Secure the Web Forward" Worskhop
[46] https://github.com/w3c/strategy/issues/370
janina: We'll meet during CSUN week.
Roy: Does anyone have any interest/thoughts on this workshop?
[47]https://w3c.github.io/secure-the-web-forward-workshop/
[47] https://w3c.github.io/secure-the-web-forward-workshop/
matatk: Looks quite low-level.
janina: Might it relate to CAPTCHA?
matatk: Not sure yet; seems not; but we can follow it.
be done
janina: Thanks all, and to our scribes.
--
Matthew Tylee Atkinson (he/him)
--
Principal Accessibility Engineer
TPG Interactive
https://www.tpgi.com
A Vispero Company
https://www.vispero.com
--
This message is intended to be confidential and may be legally privileged. It is intended solely for the addressee. If you are not the intended recipient, please delete this message from your system and notify us immediately.
Any disclosure, copying, distribution or action taken or omitted to be taken by an unintended recipient in reliance on this message is prohibited and may be unlawful.
Received on Wednesday, 1 March 2023 15:56:25 UTC