Meeting minutes
Meeting time pole
<Jem_> https://
Matt_King: we have times in the poll for 7am and 8am Pacific
… don’t think we want those in the poll
Jem_: okay, I’ve removed just now
Matt_King: should also delete any times that conflict with other W3C calls
Jem_: I’ve updated all the time options in the poll
<Jem_> https://
<Jem_> https://
Matt_King: we might want to run this poll through the first full week of Jan
… to include the meeting on Jan 6
… so run the poll through the 12th
… to give time before the Jan 20 meeting to compile results and make recommendation
Jem_: sounds good
Matt_King: we could even run it to Jan 16
… please send poll to the APG public email distro and Slack channel
… and to the public ARIA WG email distro, in case anyone there might want to join
Matt_King: if we stay on the same biweekly cadence, the first meeting in the new time slot will start the week of Feb 2
PR 3386: Update APG support tables
<Siri> w3c/
github: w3c/
<Jem_> https://
Matt_King: there’s a “View full report” link, and you need to make sure it goes to the correct report
Siri: I’ll confirm for each pattern
Publication planning
Matt_King: do we just take the main branch and make a PR to merge into the publication branch — is that correct?
howard-e: yes
… there’s a template in the wiki
Matt_King: same script as changelogs
… okay, I did see that in the wiki
… great, thank you
… so for this next publication, I’ll own doing the PR
… I’ll find the template and email you with questions, howard-e
… we have multiple PRs that are close but not quite ready
… thinking that there isn’t necessarily a good reason to tidy these up by tomorrow
… so we could could do it right after the Jan 6 meeting
… still some feedback on CurtBellew’s PR
… haven’t reviewed Adam_Page’s PR
… another editorial PR in my backlog
… we did get skipto
… so if we did release tomorrow, we’d have skipto merged
… but only that
… so my recommendation is we change the release to be after Jan 6 meeting
Adam_Page: sounds good to me
jongund: yep, no rush for the skipto
Matt_King: okay, I‘ll change the milestone
… the other one we’d have ready is AT support tables
… it’s a graceful degradation
… it doesn’t actually break anything, it just doesn’t show the data — so okay waiting until after the holiday for that
PR 3372: listbox example with aria-actions
github: w3c/
Matt_King: have lots of feedback to talk through
… CurtBellew did lots of work to get checks passing
CurtBellew: yeah :-)
Matt_King: let’s talk about stuff that’s related to code
… JoeLamyman had feedback about conventions
CurtBellew: I haven’t had the chance to act on any of the feedback yet, but I did read it
Matt_King: thank you very much for absorbing the code style guide, JoeLamyman!
… there was also something from Ari about hover
CurtBellew: yeah, I may need to remove a line of CSS
… when you’re using both a mouse and a keyboard
Matt_King: there’s one related to overlap
… someone made a comment about using both keyboard and mouse
jongund: yeah, on my Mac
<Jem_> https://
Matt_King: don’t know the root cause of this
jongund: I check these multimodal scenarios sometimes
Matt_King: we’ve had similar issues in the past where SR users accidentally activate things when they don’t know where their mouse cursor is and it happens to be in an influential location
jongund: yes, the arrow keys don’t seem to work depending on the mouse cursor location
… has there be any discussion about how AT should support this?
Matt_King: yes, Vispero is working on this, and this is the main point of this experiment — to work through the details of that
… currently, the browser isn’t doing everything Vispero needs
… we don’t want to put a toolbar around the buttons, because you can’t put a toolbar inside an option
jongund: so this will affect validators
Matt_King: yes
… but this is still a proposal
… we’re discussing this in the ARIA WG, where the feature is being specified
<Jem_> w3c/
jongund: I’m concerned about the non-linearity of it
Matt_King: so we do not want to put a toolbar around the buttons
jongund: I assume the interface for the AT will just announce “Hey, there are 5 actions here”
Matt_King: yes
… they just need to be something that receives a click event
… so CurtBellew, this particular bug is something to address
… and then the question about the visual design that Ari raised is separate
CurtBellew: yeah
… I had one question
… these are selectable
… if I click Plutonium, I get a checkmark next to it
… there was a question: should we put a visual indication of whether it’s been favorited
Jem_: I think we should have a more user-friendly example than the transuranic elements
Matt_King: say it’s a list of chats
… and each option is a person’s name
… and there’s a mini-panel with chat content for one selected person
… it would be a list of things where you’re changing the content of another panel
… sort of like tabs
jongund: if you want something simpler, it could just be “alphabetize this list of words”
… and when you successfully alphabetize, we show “you win”
Jem_: I like the simplicity
jongund: and there would be 4 actions: move to first, move to previous, move to next, move to last
… or “Rank your favorite sports and delete sports you don’t like”
Matt_King: but we want to make use of the concept of selection
… so we could have a mini-panel with “latest data on this sport”
Matt_King: CurtBellew, if it’s helpful, I can put together a content proposal
… and add it as a comment to the PR
CurtBellew: yes, please
… and I’ll look into the mouse/keyboard conflict
Matt_King: we don’t need more than 5 items in the list