Meeting minutes
New Issue Triage
spectranaut_ accname #227
scotto: there’s an issue for this already in html-aam
… not as easy as you’d think to do this, and possibly not worth doing anymore
<pkra> this one, scotto ? w3c/
scotto: the ARIA spec does say if something has `display: none`, it’s pruned from the a11y tree
<scotto> w3c/
pkra: can we just close this accname issue as a duplicate of html-aam #370?
spectranaut_: yes, we’ll do that
Rahim: I wrote some wpt tests for this
spectranaut_: core-aam #219
… wanted to test all user agent MUST statements in 1.3
spectranaut_: accname #226
BryanGaraventa: essentially a mapping bug, not a spec issue
… seems to be failing consistently across browsers
spectranaut_: do you think there’s anything more to do here?
BryanGaraventa: could be filed against browsers
scotto: this is not the first time an issue like this has come up in accname
… we’ve also had `figure` and `article` come up
… there is the concept of contextual role that could be applicable & helpful here
… this commonly comes up with links that wrap rich content
spectranaut_: could we find one of those existing issues in GitHub?
scotto: there’s an argument that the accname algorithm should be updated so that it doesn’t just rigidly stop at content that could be rolled up
scotto: I’ve found 2 issues
<scotto> w3c/
<scotto> w3c/
<pkra> to ask about w3c/
BryanGaraventa: I’ve made a relatively simple proposal for this in the past
pkra: would scotto’s proposal to add header and footer roles from last year be a short-term workaround?
spectranaut_ I’ve agenda’d one of the linked issues so we can discuss more later
spectranaut_: accname #225
BryanGaraventa: let’s punt this until jcraig is present to discuss
New PR Triage
spectranaut_: accname #228
… editorial
dmontalvo: defines “assistive technology” in the accname spec
spectranaut_: I’ll review this
WPT Open PRs
spectranaut_: anyone want to review some accname tests?
Adam_Page: I’ll link my previous related WPT issues to these ones
spectranaut_: wpt #43740
… do you need any more reviewers?
Rahim: there’s already a lot of attention on this one
… also added some tests for keyboard focusability
… I’ll defer to jcraig for when this is ready to merge
… I put it in the `css` directory because that’s where all the other display-related tests live
… I also raised an issue in the interop repo that is an exploration of adding keyboard functionality testing
… focusability, traps, enter/space operability, etc.
Deep Dive planning
<Rahim> WPT investigation of keyboard operability testing: web-platform-tests/
Rahim: next week’s agenda is light so we can talk about the name from content issue during the weekly meeting