Meeting minutes
Agenda Review & Announcements
matatk: without any updates, can close this
janina: Jason has converted issues to GH repository. some will end up in MAUR refresh.
<matatk> s/issues relating to MEIG to GH/
<Helixopp> We, Helix Opportunity, are beginning our 2nd Digital Accessibility Developer Apprenticeship Cohort on August 14, 2023
janina: MAUR - Media Accessibility User Requirements
<matatk> MAUR: https://
<matatk> MEIG = Media and Entertainment Interest Group - https://
matatk: as @helixopp said above, bringing in the new cohort
<gb> @helixopp
Helixopp: intense digital learning in the apprenticeship, all participants have disabilities and softwar eengineering background. trying to pair working professionals with on-the-job training
Helixopp: scalability is a focal point, 10 people at a time in each cohort
<Helixopp> https://
janina: brainstorm at some point how to get candidate projects in through APA, a discussion to be had
janina: in AGWG, different challenges would need to be covered in Silver, some which could benefit from further engineering (browser exntesions, coding, etc.). these types of things could be valuable considering the spectrum of such candidate projects
Helixopp: come up with project and apply for a grant to cover wages for apprentice and colleagues
APA Charter approved - https://www.w3.org/WAI/APA/
matatk: charter approved until July 2025!
<Roy> https://
matatk: would encourage all to read through and see what you might be able to contribute to
TPAC 2023 planning - https://www.w3.org/WAI/APA/wiki/Meetings/TPAC_2023
<Helixopp> verified credentials???
matatk: haven't put the times in Wiki but we have a few things scheduled: MEIG, ARIA, and Web of Things
matatk: nothing planned with Verifiable Credentials at the moment
matatk: let us know if there's anything missing
matatk: encouraging all task forces to submit a breakout session to discuss work they do
matatk: breakouts can be public. held on Wednesday afternoon. great opportunity to speak about work
<Helixopp> eh, we've done 2
<Nichole> We have one as well; Design Tokens for Accessibility Settings: Empowering Inclusive Design with CSS .
<matatk> w3c/
New Charters Review - https://github.com/w3c/strategy/issues?q=is%3Aissue+is%3Aopen+label%3A%22Horizontal+review+requested%22
Solid Working Group Charter
<Roy> - charter: https://
<Roy> - issue: w3c/
Roy: new WG. define concept of storage to give priority to individual and community autonomy. allow jurisdiction over their data.
matatk: looking at the spec. has rather comprehensive a11y considerations section. nice that they've acknowledged a11y. I don't have concerns about the charter itself. we will see the protocol spec separately
Roy: agree
matatk: any objections from anyone to sign off on this?
Roy: can sign off on this, yes. no objections from anyone.
Web Performance rechartering
<Roy> - charter: https://
<Roy> - issue: w3c/
Roy: comes from Web Performance Working Group.
janina: met them last year. they seemed excited and we didn't follow up like we should have. still think we should follow through on this
janina: they were interested in working with us
janina: let's sign off on this
matatk: agree
PNG WG recharter
<Roy> - charter: https://
<Roy> - issue: w3c/
Roy: no concerns about a11y here
<matatk> https://
matatk: we signed off on this
matatk: no concerns about current charter
Explicit Review Requests - https://github.com/w3c/a11y-request/issues
matatk: don't think we have any new ones. still need to do an a11y considerations section for another spec
Roy: no new requests for review
A11y Review Comment Tracker - https://w3c.github.io/horizontal-issue-tracker/?repo=w3c/a11y-review
matatk: many remaining issues that we need to get through
matatk: the issue is called disallow interactive content in summary element
matatk: Paul indicates that summary is an unusual element which can contain many things. since summary is interactive, cannot have interactive children within. we should just say we cna't have focusable content inside a summary element
matatk: can turn interactivity off using inert or aria-hidden and render it non-interactive and thus eligible to be placed inside the summary element
matatk: agree with these comments. our position has been articulated and we can keep tracking this moving forward. no need to have it pending
matatk: we don't need to revisit this
<Helixopp> +1
<Helixopp> Focusable elements in summary may have COGA benefit
Popover invoker example shouldn't have aria-haspopup #159
<gb> Issue 159 §3.8 user need 10 add real-time text [RAUR] (by gunnarhm) [RAUR]
<matatk> w3c/
matatk: I suggest we close this issue on our end
matatk: can send details of summary element to the list and have a discussion there
matatk: any new work in TFs we need to cover?