Meeting minutes
pkra: reminder: board is at https://
… put something in the agenda+ column.
… https://
… then I'll add it to the "short" agenda.
… let me know if you want to do it differently.
follow ups to removing common.css
pkra: that's a follow up to my PR where I removed the stylesheets.
… accname list styles
mel: assign an issue to me
pkra: thanks
spectranaut_: I ticked the other item
pkra: thanks.
… the last one does actually depend on aria.js so I'll redirect that.
melsumner: where do we put styles?
pkra: in the accname spec right now. The others don't have any. Maybe TR design or respec want list styles.
revisit prettier automation
pkra: prettier automation.
pkra: basically: we had it, then we accidentally disabled it b/c of forks. I re-activated it. Also, actions security.
spectranaut_: I like merging on main.
… would it cause issues?
… would it affect the changelog?
… e.g., changelog links to commit that's not formatted.
Daniel: that doesn't sound too bad. Would only impact reviewers.
pkra: we could go back to dry-run but not continue on fail.
… then formatting has to happen somewhere.
spectranaut_: I'm still +1 to run on main.
melsumner: +1
pkra: then we just need someone to work on it.
Daniel: I'll take a look
Provide the ARIA “Characteristics” data as JSON
pkra: this seems to be a broader issue. Do we need more machine readable version of the ARIA specs?
… do we want to do something? If so, what?
scotto: if we had something, we could pull in data into the various specs. E.g., html-aam pulling from core-aam.
… I'm not sure what this issue's scope is though.
pkra: I think it's for ladybird
scotto: ok. for valdiators, I don't know what other tooling would do.
melsumner: I've been in projects where we extracted things into lists of thins.
… my concern is: do we then have 2 things to maintain?
… or do we reconsider our source of truth?
scotto: that's a good point. If we go this way, we should populate the spec from the data.
… that obviously means that we're creating barriers for people using the spec.
pkra: ran into this while rewriting aria.js. Maybe keeping small json blobs in the spec could be a compromise.
spectranaut_: maybe we should think more about it while working on aria.js
<spectranaut_> aria.js PR: w3c/
pkra: right. coming back to my PR, this work really needs another person to ground and speed it up.
melsumner: I might know somebody who could be interested
spectranaut_: I might have some time.
pkra: great! Let's see if we can find common times.
status of graphics2.html
pkra: I think we can remove the two files mentioned in the issue.
jamesn: those look odd.
… I think we can.
Daniel: I think so. We can always revert / find it in the git repo
melsumner: I remember a similar file a client referenced.
… which was causing confusion. Maybe it was this one.
jamesn: the requirements one is for 1.1.
pkra: great. What about graphics2.html?
melsumner: https://
jamesn: yeah, this looks old, too.
pkra: I'll make a PR.
SVG-AAM Section 8.1 Name and Description needs rewrite
pkra: what do we do about the SVG specs? This looks like a worthwhile thing but hard to get traction on.
… I'm wondering how to find some new editors to move things forward.