Meeting minutes
<Jem> rragent, make log public
<Jem> https://
Setup and Review Agenda
future meetings
propose cancelling next week due to CSUN and axe-con
issue triage
RESOLUTION: no meeting next week (Mar 15)
https://
<Jem> https://
Matt_King: This is a webkit issue with aria-activedescendant
Matt_King: we should just say that
<Jem> https://
Matt_King: is there a WPT test for the name calculation algorithm for comboboxes?
jamesn: I don't know
jamesn: I would need to check
ACTION: sarah_higley to check if there is a gecko bug
<trackbot> Error finding 'sarah_higley'. You can review and register nicknames at <https://
https://
<howard-e> https://
(discussion about webkit bugs)
Matt_King: Gecko bug needs to be filed is if one is not already
<Jem> https://
Matt_King: sounds editorial
Matt_King: misinterpreting the text
Open Pull Requests
<Jem> https://
<Jem> https://
<Jem> james' comment
sarah_higley: This may be a browser bug
Matt_King: should not block the PR on this
all agreed
siri: would suggest this should not block the PR
Matt_King: not going to add to the documentation on this page
jamesn: suggest filing a new issue even if it is a chromium bug
jongunderson: original example was using buttons
jongunderson: likely that there is an artifact of the tabs being buttons... not sure we consider that a best practice or not
Matt_King: if using a non aria supporting browser would get fallback to buttons
Matt_King: in practice not sure how much of an issue that is
Matt_King: if had a website with older versions of TB on android it might be relevant
Matt_King: used to talk a lot about using the closest HTML
jongunderson: generally shy away from button unless closely related as have to undo a lot of stuff... tend to get unintended artifcacts
jongunderson: could be something to think about
Matt_King: thought what we were doing was accepted best practice
Matt_King: anyone have a viewpoint on this
sarah_higley: buttons have a different text selection behaviour - less selecty with static text
sarah_higley: if don't use a button then get some selection behaviour that is unintended
Matt_King: 4 years ago there was a lot of talk in best practice about this. Doesn't feel enough of an issue to write anything about but the fact we are using buttons may demonstrate that we should do that
ACTION: jongunderson to file an issue about the high contrast border issue
<trackbot> Error finding 'jongunderson'. You can review and register nicknames at <https://
APG Site Redesign Update
APG Site Redesign Update
seth: What to epxect in the content side
alex: do we want to put this HTML file into the root of the APG repo or do we want to consider any other options
… I think we are pretty flexible
Matt_King: since it is the Home page and the default page - it feels to me like an index.html in the root directory
alex: sounds good to me
seth: sounds good to me too
… try it out with a sibling file in the root
… next step will be a PR to add the home page file
Matt_King: did you talk about for the resources segment there would be some sort of construct
<siri> https://
alex: right now not dynamic just a document
<Jem> http://
alex: built into the architecture... the links will point to the redesign links
Matt_King: right now building all those redesign links by parsing the giant file
Matt_King: 2 weeks from today have this new page and the netlify site being generated
Matt_King: going to be talking to E&O
Matt_King: where APG will live
jongunderson: is jump to in there?
Matt_King: on the preview site.
seth: will need someone to merge the PR
File Directory Treeview Design Update
Issue #1817
sarah_higley: how soon do you want this to happen
Matt_King: on your timetable
Matt_King: at this point current focus is getting current content out there
Matt_King: at some point we will break the ability to push to our current editors draft
Matt_King: but doesn't need to affect timing
Matt_King: do we need time to discuss design goals
sarah_higley: set agenda time
sarah_higley: have an idea what it would look like