Meeting minutes
New Issue Triage
2297 added two reviewers and removed existing
2431 closed
New PR Triage
pkra: 2410 look at the specs. changes are fairly contained.
James Editors or anyone else should take a look
WPT Open PRs
@jamesn: James isn’t here let’s look at them next week
Deep Dive planning
pkra: stale PR review?
jamesn: I am not here for next 3 weeks. But someone else can drive. Not wanting Val to do 3 in a row
jamesn: evne for those that are approved, we may need to wait for implementation
jamesn: Peter can you schedule with Val?
pkra: Sure
Breakouts day
jamesn: Breakouts day. Wednesday of TPAC. Propose breakouts. If you want feedback form the community. Anyone is welcome to propose a session. 26th of March. Proposals by 12th of march.
@daniel: You don’t need a lot of details to provide.
Remove group as allowed child of tree
jamesn: 2094, why is this not merged yet?
pkra: all we need are validated test?
scott: we may want to consider assigning multiple people to PRs. It can be a lot of work but we have raised the level of effort for non-editorial PRs because one person may not be able to do it all.
<Adam_Page> +1 to scott, would be enthusiastic to make PR production more collaborative
pkra: should we file bugs with certain validators?
scott: When people know what the parameters are is the author of a PR the one who has to do all of it.
jamesn: MDN can be inaccurate
spectranaut_: I’ve made follow up issues. Land PR but assign author test. So it’s clear these can be broken up. Bugs on browsers is intimidating. Especially coming form someone who is known. Test make sense to break out.
pkra: Wants to knwo whnat needs doing and who can do it for this issue. But appreciate the broader converstion.
jamesn: validators don’t test everything.
Matt_King: allow children in a tree should have a test for it.
jamesn: Is this something validators would like to test? Ask giacomo-petri
giacomo-petri: Definitely, we need to check this.
jamesn: Can we just file against ACT?
smockle: Why is it the purview of the ARIA group to open issues?
spectranaut_: It won’t happen unless we ask them to.
scott: I agree with Val. If specs changes you would think they would be on top of it.
giacomo-petri: as to vendors, we have another problem. If you push something that is not available, why do I need to do it?
jamesn: Do we file against ACT?
scott: It would be a polite thing to do. But not bar ourselves from merging.
jamesn: if we’re not waiting for them to respond, it seems like we should do it.
giacomo-petri; I can do that
jamesn: then we can merge it
svg element in HTML-AAM, SVG-AAM and WAI-ARIA Graphics Module specs
@james: 2427 inconsistency in specs. This sounds similar to section and role of region. Section is mapped differently if is has accname or not. Do we want to treat all of these the same?
<jamesn> +
pkra: wold this interfere with new fandango features? Image description by browser vendors? Auto generated alt text.
scott: generic or none is all well and good, but how improtant is it for people to know they’re entering anSVG adn they may be entering a subdocument or not. Should we ignore ??document role?
pkra: navigable or tabbable inside graphics. There may not be a name by author on root b-c its a complex diagram.
<scott> if the svg ended up being removed, by having a generic or none role - then that seems like it'd be an implementation bug
Matt_King: role none, there isn’t a cascading of it.
jamesn: usually yo uput aria-hidden on it. If graphics document doesn’t require an accmane does it help?
giacomo-petri: it∏s a spec detail but it’s still an empty image
giacomo-petri: render as generic it’sstill available.
Adam_Page: SVG of artwork. given a title as name. but in iOS was treated as decorative. We allowed implicit role of documemt to persist. Once we overrode with role image it was fine. May be relevant.
<Zakim> scott, you wanted to say "if rendered as an empty _image_ is that not potentially an implementation issue as well?"
scott: If SVG graphics document is that an implementation issue. You sould have used the image element or role. If graphics doc didn’t require a name that may be fine. There might be conetent in here. But if it∏san image with no accname then it∏s an implementation bug of graphics document.
Matt_King: does AT announce graphics document? How does this work today?
Matt_King: I’ve never heard that announced.
jamesn: Is there a resolution?
Matt_King: We may need to figure out what the problems of
pkra: SVG exploration feature would go outside the SVG. We tested setting role presentation on SVG and Chrome wanted to describe it. We’ve had a couple of these SVG issues. We need to make a more serious effort, task force of popele who want to dig into it. James Craig has an interest. I may also get involved.
giacomo-petri: I agree with Peter. We still need people to update, etc.
[AriaNotify] Scope proposal for V1 of API
alisonmaher: 2426, interrupt and type need inplementers to get onboard. Need more notification types. Want to ship so authors can use. Do we need a more scoped version for version 1.
<scott> +1 to getting something shipped, even if it's less than the original proposed set of features
Matt_King: In favor of getting this in people’s hands sooner.
jamesn: agreed. Anyone disagree?
spectranaut_: should we talk about this more?
jamesn: if anyone wants to suggest, they can do that in the issue. General consent from the group.
keithamus: there’s an alternative to supports, but otherwise I support it.
jamesn: we have agreement