Meeting minutes
Agenda Review & Announcements
Nothing new from Matthew this week
TPAC 2023 planning - https://www.w3.org/wiki/TPAC/2023
matatk: W3C timetable covers only room; we're set for Monday, Tuesday, and Thursday
matatk: We have to arrange cross-group meetings ourselves
matatk: Friday meetings, esp. cross-group are still a possibility
matatk: Wiki will be updated as we go through
<matatk> https://
matatk: No news yet on when to propose breakouts, but have two to propose
matatk: One re Adapt; one re gh tool
matatk: will monitor
matatk: Will announce here for anyone thinking of it
New Charters Review - https://github.com/w3c/strategy/issues?q=is%3Aissue+is%3Aopen+label%3A%22Horizontal+review+requested%22
Pointer Events Working Group 2023
<matatk> - charter: https://
<matatk> - issue: w3c/
matatk: Looking to enhance pointer events ...
matatk: Notes a11y
matatk: Don't see issue beyond that, ... no A11y Considerations
matatk: suggest we push for AC section
matatk: thoughts?
PaulG: Agree; and work sounds needed
matatk: Will note our approval on github thread
Explicit Review Requests - https://github.com/w3c/a11y-request/issues
matatk: Checking ... Look like issue reqs
. no spec reviews
A11y Review Comment Tracker - https://w3c.github.io/horizontal-issue-tracker/?repo=w3c/a11y-review
Disallow interactive content in <summary>
<matatk> - issue: whatwg/
<matatk> - ping: whatwg/
. the one that 3 of us volunteered for last week .... #164 in our APA repo
<ghurlbot> Issue 164 §5.3 Bandwidth for video - confusing title [RAUR] (gunnarhm) RAUR
matatk: notes thread is quite long; wonders whether others have looked?
PaulG: started, finding places where problems could occur, but may still be OK to allow the feature
PaulG: e.g. accelerators
. having secondary actions -- need to check a bit more
matatk: Wonders whether What wants to disallow because not used much
. Also, we have other ways to get same functionality
. will return to this next week
Should <dir> behave like a list element?
<matatk> - issue: whatwg/
matatk: Recalls Paul suggest element may be deprecated?
matatk: got a thumbs-up
PaulG: Scott O mentioned
paul html-aam #486 has the list
<ghurlbot> Issue 486 [not found]
matatk: seems 486 is what we should be tracking; i'll add label for our dashboard
matatk: we'll look again
New on TR - http://www.w3.org/TR/tr-status-drafts.html
No news
CSS Update (Paul) - https://github.com/w3c/css-a11y/issues
paul: mostly api; but one a11y re font super/subscript
PaulG: so constructing a variant glyph
PaulG: most AT doesn't recognize super/subscript
<PaulG> w3c/
<PaulG> https://
matatk: nothing in axtree?
PaulG: nvda will read when enabled; but lots of ignoring it
janina: suggests spoken presentation to consider
matatk: concern that this may incentivise devs to use non-semantic techniques (though other similar situations exist; assume there's a general warning against using non-semantic techniques in CSS)
PaulG: easy to position visually
PaulG: this is fallback where gliph not available
<matatk> s//concern that css will keep out of axtree/concern that this may incentivise devs to use non-semantic techniques (though other similar situations exist; assume there's a general warning against using non-semantic techniques in CSS)/
PaulG: could add rules to ensure proper visual representation
Fredrik: Could you define smart clients more?
janina: There was some work done a while back in the Linux Foundation that took the view that for some content on the page, a specialsed/"smart" client would be needed to process and present that content, rather than just the browser. E.g. math, science, formulae.
… A corpus of rich domain-specific content would grow over time.
… E.g. Should be able to tag musical notes as they are performed.
… The idea is the general browser isn't going to build in that level of sophistication. We need a handoff mechanism from the browser to the specialised UA.
… Had a converssation about this in a breakout in Lyon, 2018. Well-attended and thought that someone should build it, but it's not yet come about.
… Good time to raise this with EPub, now in a transition phase, folloiwng the recent spec release.
… Time to bring it up at TPAC etc.
… We asked for a meeting with the TAG, and this is on the agenda.
janina will send pointers to list
Lionel_Wolberger: what was described very much like what happens on mobile today
Lionel_Wolberger: what was meant by plugin?
matatk: we have concepts where another component can present some embedded content in a smarter way
matatk: notes that html5 trying to move away from plugins
Lionel_Wolberger: appreciate the redux!
Fredrik: do you see environment on mobile where a browser can open embedded content in an app context?
Fredrik: but you don't get back to the browser when finished
Lionel_Wolberger: route back is an issue
Lionel_Wolberger: w3c interoperability
matatk: not quite the same as the app taking over; idea is a specific bit of content; more fine grained
Getting a Grip on the A11y Review Comment Tracker https://github.com/w3c/a11y-review/issues
matatk: already done some today!
Alisa_Smith: began, but not finished ...
matatk: feel free to comment on issue or email list
matatk: looking for Niklaus' issue ...
https://
matatk: niklaus looked at
matatk: don't recall we reached a conclusion on previous consideration of this
matatk: concern of not getting focus trap
matatk: so we'll come back to this
matatk: Notes studying up on available labels; how best to use for managing these
matatk: pending label and the closed label are the ones we should focus on first
matatk: We'll get more adept as we do this