Meeting minutes
Set up and Review Agenda
<Jem> seth: he would like to add communication discussion later.
<Jem> isaac: removing current work section.
<Jem> mck: we can add that to the second meeting agenda topic, new apg site
New apg site home page launch
<Jem> Mck: https://
<Jem> new site is http://
<Jem> mck: new begining for APG wg
<Jem> ... there will be the announcment about the release this week.
<Jem> ... going back to homepage content topic
<Jem> mck: is going over page structure
<Jem> and some changes are coming up
<Jem> ...current issue 2323 does not generate the preview
<Jem> ... wondering where the bug is coming out
<Jem> rich: there is the bug from the build process.
<Jem> ... team is suggesting to use display none for the section while the team is working on the changes.
<Jem> isaac: we can ask Alex where to touch on.
<Jem> mck: I would like to send out this to the WG members so that it can be reviewd.
<Jem> ... Shawn would also need time to push this out.
<Jem> the group is discussing the workflow details for updating home page structure.
<Jem> Seth: our team will work on the fix and prepare the comments so that WG knows how to update the page.
<Jem> mck: it is CMS problem.
<Jem> ... we will talk more about manage content
Providing Accessible Names Practice: Change heading levels to make page TOC more informative #2324
<Jem> https://
<Jem> seth: that is respec generator, not jekill for preview.
<Jem> seth: I will look into PR preview error.
<Jem> mck: This PR proposes removing the headings associated with items 4 and 5 to bump up their subsections and expose them in the page TOC.
<Jem> https://
<Jem> ...both Accessible Names Accessible Descriptions are large section. It is difficult for users to know what is on the page with so many subsections tucked away under them. This PR proposes removing the headings associated with items 4 and 5 to bump up their subsections and expose them in the page TOC.
<Jem> ... I bumped up the headling levels from h4 to h3.
<Jem> ... I would like to work on edtioral section before the launch.
<Jem> ... I am not sure about Shawn's availability for the changed push.
JAWS, VoiceOver, and Narrator do not work correctly when accessing links in cards on APG Patterns and Fundamentals pages when using Chrome, Edge, or Safari #70
<Jem> rich: We have PR which Isaac can review.
<Jem> ... we will do internal test
<Jem> mck: is error verification done?
<Jem> https://
<Jem> rich: yes
<Rich_Noah> https://
Date format and page footer
<Jem> shawn: she asked us to use specific Date from the site.
<Jem> rich: we will take that as the work item at next sprint meeting. we would like to focus on issue 70 for now.
<Jem> jon:Was issue 89, jump to discussed?
<Jem> rich: we will focus on issue 70 first for the relese and disucss issue 89, jump to scrption next.
<Jem> seth: which version we should look at? non paypal version?
<Jem> jon: Matt, in which repo do we want to put the jump to code? currently it is just script, not source code repo.
<Jem> mck: I am not sure what the best aveneu for now but I prefer jump to to be part of the repo.
<Jem> jon; we can talk about where to/how to host that. it is branded as paypal, not actually paypal code.
<Jem> seth: currently jumpto is only on APG examples but is it eventually for every page?
<Jem> mck: yes
<Jem> rich: # 2324 preview was successfuly created.
<Jem> seth: new build process is interacting with old respect flow. that is where the main errors came from.
Communication plan for the release
<Jem> seth: our team prepare the short and long messages. They can be posted to social media. our company will also post and retweet.
<Jem> the message.
<Jem> ... two things: one media release is aria apg example focused tweet.
<Jem> seth: it would be good to talk about who post to where.
<Jem> ... the other type of messsage is general annoucmentment on new apg site.
<Jem> jem: I can also work with other accessibility mailing list such as Educause IT accessibilty community and Athens mailing list
<Jem> jon: our colleage can tweet about new apg site.
<Jem> jon: I can announce the new site to web aim list.
<Jem> jemma will post it to wai ig mailing list.
<Jem> also send it to Bruce Bailiey, Section 508 mailling list.
<MarkMcCarthy> I sent a note to my department's social media person, and hopefully it can propogate from there (she might know who to talk to get RTs from different departments, the bigger university accounts etc.)
<Jem> meta is going to post announcement to meta accessibility community group.
<Jem> Jon willl send the new site release to Big 10 high education alliance.
<Jem> s/setup/Setup/
<Jem> s/set up and review agenda/Set up and review agenda/
<Jem> s/date format and page footer/Date Format and Page Footer/