Meeting minutes
<Jem> Meeting Agenda: https://
Set up and review agenda
Jem: still waiting for Matt and a couple other people
New APG issue Triage
Jem: no new issues this week!
APG redesign Project
<Jem> https://
Rich: we have a few items that are necessary for launch, we've sized them. we have 6 days left before deploying for review
Rich: Right now, it's set that our changes will take 7.5 days, so I'm waiting to hear about more resources
Rich: We found some issues, we have to overwrite the template. I'd like to avoid if possible
Rich: But we're working on it
<Jem> to ask where the information is.
Rich: Hopefully will be ready for review before GAAD on May 19
Jem: I don't see those 9 issues on the project board
Matt_King: They're in wai-aria-practices
<Jem> https://
Rich: they should all be there
Rich: I accounted for 10, so I'm not sure if anything else moved in. The URL item isn't from us
Matt_King: That's on MichaelC_ and Shawn
Rich: There's one that wasn't scoped out this morning, #49, so I'll have to get things resized
Matt_King: it depends on #48
Matt_King: I just didn't want to interrupt the flow of the meeting or anything else before getting to that
jongunderson: What's the plan for bypass blocks? There's two different ways to do it right now
Rich: That's in issue 26
Matt_King: we're removing the extraneous one that's just a link, instead using SkipTo.js. it won't be persistently visible on launch, but issue 40 contains some designs from Isaac
Matt_King: current plan is that it will appear on Tab for initial launch, #40 will be taken up right after launch
jongunderson: thanks
Placement of "Read This First" links
<Jem> https://
Matt_King: currently, the Read Me First section contains basic principles (No ARIA...), basic browser/AT support, etc.
Matt_King: right now, it's kind of buried on the about page. this issue turns the Read Me into a fundamentals page like landmarks, hiding content, etc.
Matt_King: it'll be titled "Read This First" and will be the first item on the fundamentals page
Matt_King: ideally, we should highlight it on the homepage and patterns/widgets page
Matt_King: if we're forced to do either/or right now, there's two questions:
Matt_King: what does the TF think we should do if we have to choose a location, and if it's on the homepage, where do we put it?
Matt_King: my understanding is that, when you load the homepage, the only thing you see without scrolling down is the intro card which links to the patterns page
https://
Matt_King: so, if we put Read This First on the homepage, i don't think i'd want it below the fold and above the "view patterns" link
Matt_King: so maybe the place to feature it is at the top of the patterns page, maybe that's more important than featuring it on the homepage
Jem: I agree, but maybe adding a navigation item and putting it on its own page
Matt_King: it'll be on the fundamentals page as the first card for sure.
Matt_King: that's a given. but we have to make sure people are aware of it before using the patterns, too
jongunderson: i think putting it on the patterns page is a good place to put it
jongunderson: maybe naming it something more inviting than "read this first"
Matt_King: so we'll need a small intro after that first heading, or maybe "read this first: no aria is better than bad aria", that could be good
jongunderson: i like that
MarkMcCarthy: +1
Jem: hearing two suggestions: 1, adding read me first as first card item in fundamentals, 2: adding read me first as first item under design patterns and widgets
Matt_King: if the card was just "read this first" with the "no aria..." tagline, Rich, would something like that look any different?
Rich: each card has: on the upper left, the icon representing the widget, in the top right, the name of the widget, then a description afterwards
Rich: Everything is ordered alphabetically, and adding "Read this first" Would break that, but we're here to do what you (all) would like
Matt_King: could it be added under the H1, in such a way it doesn't break the flow of the page
Rich: It could be another element for sure, but I'd have to talk with Isaac
Matt_King: maybe instead of a card on the fundamentals page, it's represented the same way throughout.
jongunderson: i think Isaac would have good ideas
Matt_King: if it's done this way where it's separate from the cards, maybe it could take up less vertical space.
Rich: I could see it spanning across.
Rich: if this is the case, then "Read this first" is the heading, and after that the CTA is "No aria...."?
<Jem> Decision: "Read me" section under "about" page will move to the "patterns and widgets" page as the first card item.
<Jem> https://
<MarkMcCarthy> 👏
<Jem> Matt will open the issues regarding heading level in fundamental page.
<Jem> https://
Homepage content update
<Jem> "Home" link does not indicate that it is apg site because there is no correct H1 unless it says APG home
<Jem> jon: it is a bit backward convention to show w3c after ARIA APG.
<Jem> discussing to resolve the descrepancy of accessible name for home and actul h1 in the hompage
<Jem> Mck: Matt will update the h1 to apg, rather than being the tag like of "get empowered..."
<Matt_King_> https://
<Jem> mck provided the content
<Jem> mck: I would prefer something else instead of div and span
<Jem> jon: I will add comment on wai template.
<Jem> https://
<Jem> mck: I don't see there is preview link for the changes.
<Jem> rich: I will check with Howard about the workflow.
<Jem> mck: removing the texts of "recommended approach..." under "building blocks that..."
<Jem> "APG resources" look like h3 visually although it is h2.