Meeting minutes
remembering Carolyn
A moment of rememberance and celebration for Carolyn.
A Celebration of Life will be held Wed Feb23 11-2 ET. Out of town attendees are welcomed to join virtually. Details are here: https://
Jon: I always appreciated working with her and her comments and work for the group, hard to imagine she's gone.
Bryan: It's weird to think that we had all just talked with her last week.
Matt: I enjoyed working with her so much for the last couple decades, I loved meeting her and husband a few years ago. I always had hopes she'd become an editor or something. *laughs*
Jemma: Life is always so unexpected, it's so hard to believe. She was so kind, and always willing to help out. I can still hear her laughing with us right now.
<Jem> A Celebration of Carolyn's Life will be held Wed Feb23 11-2 ET. Out of town attendees are welcomed to join virtually. Details are here: https://
Matt: Her last commit was literally only days ago, it's so...wow. I feel honored that she helped us out all the way until...
Curt: I was stunned to hear about it - she was so vibrant, always. It was astounding to hear about it.
Mark: It's all just so unbelievable.
Matt: She was so committed to us and doing the right thing.
Mark: And the disabled community by extension, not many people would do that.
Siri: It's so shocking, just seeing her online last week and seeming so vibrant.
Jon: I wonder if there's something we can do, a tribute or something like that, for the next publication. It would be a great memorial and honor for her.
Jemma, Mark, Matt: +1
Here's to you Carolyn.
<siri> +1
Triage
Jemma: Disclosure pattern, #2220
Jemma: I can make the comment that this is in APG 1.2, as it's officially replaced 1.1
Jon: I think there's some confusion about the versions
<Jem> https://
Jemma: yes, we're working on resolving some of that and i think that the redesign will help too. Moving on to 2082
Matt_King: This sounds like a violation, not a warning. Do we need to rasie an issue with Michael Smith?
Matt_King: I guess the question is who we assign this to, if they're errors that need correcting or not. Or if it's an issue with the JAR
Matt_King: let's add the agenda item and we'll discuss at a later meeting.
jemma: moving on to 2063
Jemma: issue is stating that the language surrounding grid is vague
CurtBellew: that makes sense
Matt_King: let's add it to the grid project
<siri> https://
Matt_King: this could use some deep dive work, taking a look at wording side by side
Matt_King: assign to me, i'll add other labels when appropriate
Jemma: moving on to 2061
jemma: this is more infrasture work, looks like he has a PR for us too
Matt_King: looks like this is to automatically regenerate coverage the same way we do index
jemma: looks like it just needs to be merged
Matt_King: well we'll need to decide if this is what we want to do, first
jongunderson: some of it comes down to whether or not we use the coverage report
Matt_King: it's a way of tracking our project towards full coverage
Matt_King: this is probably already on Bocoup's list of things to look at
Erika: I could talk with Howard about it and get an update.
Matt_King: i don't think this is in the infrastructure project, so I'll add it.
jongunderson: I'll be retiring in a few month and I'd like to update some examples, so I want to work on some of that before then.
Matt_King: so, retiring from everything? *laughs*
jongunderson: well.... *chuckles*
jongunderson: basically I can't make any promises right now!
Matt_King: Definitely understanable.
CurtBellew: Congrats!
Matt_King: that's what I should say! *laughs*
Matt_King: sorry Jon!
Jemma: Maybe let's skip open PRs and move to redesign?
Open PRs
Matt_King: I do have one question, about the tabs.
<Jem> https://
Matt_King: the name of the tabgroup includes "Selected" - maybe that's not a great idea, since it's used by ARIA announcements etc.
Matt_King: It can be confusing to hear different "Selected"s in different contexts, let's just leave it "Danish composers?"
jongunderson: that's fine
Matt_King: do other companies/organizations do things like that? Should we have more explicit guidance about that in APG?
MarkMcCarthy: I try to do that, personally, though we don't have anything explicit.
MarkMcCarthy: maybe we could include a note or something?
Matt_King: that helps, thanks
jongunderson: that little change is done!
Jemma, Matt: Thanks!
Redesign
<Jem> https://
isaacdurazo: sent an email last week with a link to the mockup, would love to get some feedback
isaacdurazo: the idea is to have a hero section at the top, title, description, enticing goodies
isaacdurazo: after that, info that represents APG in general
Matt_King: a question about the hero section, could we provide a link in that description to page in the About section of the guidance?
jemma: Matt, do you mean the introduction or readme first in the APG?
Matt_King: I thought we had one called "About"
jemma: Oh yes, we talked about that.
Matt_King: a section with acknowledgements and things like that. just wanted to see if that kind of "front matter" would be linked to
isaacdurazo: the answer should be yes, that makes sense. i don't have that in the mockup but it does make sense
isaacdurazo: keep in mind that basically all this content is a placeholder
Matt_King: i'd like to work with you and others on that. one thing that'd help a ton is to have a Word layout
Matt_King: i wonder if someone that's new will go below the fold, maybe only if they're curious
<jongunderson> need to leave a little early today
isaacdurazo: i haven't worried much about the fold yet, i think people are used to scrolling etc. I hadn't thought about that as a problem
Jemma: my point was that having such a long page of text might not be the most friendly
Matt_King: maybe we need to consider what's "long" and what's "short"
isaacdurazo: and then, how should we think about different viewports?
jemma: I think mostly what I'm arguing for is brevity and succinct writing. I'd rather see things a little more compact
Matt_King: are you saying it's not compact enough?
isaacdurazo: what I need to know now is 1) is this layout good? does it makes sense, do people like it? 2) what i'm proposing for the different type of content 3) look and feel - are colors good etc.? (I'm trying to follow W3C look and feel though)
Matt_King: i like all the sections for #2, but I'm least ceartain about the current work
Matt_King: one of the things i want to include somehow is recent changes
isaacdurazo: i was thinking we could make this a place for working progress, news, articles that are written, etc.
Matt_King: i wanna be careful to not always have to maintain that part though
isaacdurazo: yes, I'm thinking of that too. I wanted to put this in as is to show potential, rather than what we should do
Matt_King: what do others think?
isaacdurazo: i'm curious to get feedback about the resources I have (patterns, landmarks, making the web accessible, etc.)
Matt_King: i'm really leaning towards highlighting the accessible naming section, probably more important than the keyboard one
Jemma: +1
MarkMcCarthy: +1
<Jem> mark: moving keyboard section away
<Jem> ... focus on why people visit this site.
<Jem> mck: we are talking about content priorities.
have to head out to my next meeting gang, have a good day and week.
<Jem> keyboard interface can be after naming section one.
<Jem> curt: sounds reasonable not to add keyboarding section as the priorities.
<Jem> ... naming will be the key