Meeting minutes
<Jem> https://
set up and review agenda
Status of Site Updates
Repository Restructure Update
Matt_King: All redirects and 404s fixed. 110 bookmarks now work!
Matt_King: In the future, I'd like to test redirects
AlexFlenniken: "Broken image links on feed display page" is in progress
AlexFlenniken: we've split up relevant files into three separate directory structures, but this makes some of the file links very "distant" -- lots of relative pathing ("dot-dot-slash")
AlexFlenniken: tracking issue: w3c/
AlexFlenniken: I think the solution is to make sure the assets are all in the same folder, just like the APG--even though it would be faster to just change the example
Matt_King: Is it broken in production?
AlexFlenniken: Yes, if you look at the "feed" example, it has missing images for the "stars" ratings
Matt_King: Let's not deep-dive on this right now
Matt_King: I'm wondering if we should apply a quick-fix for now
AlexFlenniken: We could maybe use an inline SVG so that it wouldn't have to be fetched as an external resource
Matt_King: Since WAI is talking about changing their infrastructure next year, I'm inclined to kind of "kick this can down the road"
AlexFlenniken: I will file an issue
<Jem> restructure and improvement of About Page -- PR 2558
<Jem> w3c/
Work in progress on restructure and improvement of About Page
Work in progress on first AT support table - pull request #2569
<Github> w3c/
AlexFlenniken: I'm working on the requirements behind using sample data
AlexFlenniken: I think we'll have something to look at for this next week
Pull Request Review
Combobox Date Picker Example: Change previous and next month and year behavior for dates near end of month by jongund
github: w3c/
jongund: All the test cases finished; I'll check them in later today
jongund: I've updated the documentation as well
Matt_King: We need a review checklist
Jem: I'll add that
Matt_King: We only need to verify the functionality and the editorical review, but there's no changes to CSS. Only two files changed, just the JavaScript and HTML files.
Matt_King: We should have at least one reviewer besides myself
Siri: I will perform the functional review
Listbox Examples: Update scrolling of listbox item with focus into view when page is magnified by jongund · Pull Request #2622 · w3c/aria-practices
<Github> w3c/
github: w3c/
arigilmore: I've commented with notes on my initial review
Matt_King: the test failures are blocking the review failures
jongund: I haven't had an opportunity to look into those test failures, yet
Infrastructure: Update script that provides skipto menu on all pages to version 5.1 by jongund · Pull Request #2619 · w3c/aria-practices
<Github> w3c/
github: w3c/
Matt_King: I made two changes to the "skipto.js" file. They were strictly editorial--within code comments. Minor typos
Jem: I will finish my review by the end of my day today
Landmark examples: Updated SkipTo script and configuration by jongund · Pull Request #2624 · w3c/aria-practices
<Github> w3c/
github: w3c/
Matt_King: I think this is waiting on me
Jem: Two regression tests failed
Matt_King: Occassionally there are timing issues, and sometimes they'll pass if you just have them run again (e.g. by pushing another commit to the pull request's branch)
New About Section Content
Preview the content without site chrome in RawGitHack
https://
Matt_King: This is a pretty substantial set of changes to content and messaging
Matt_King: Some of it is driven by recent issues and questions that have been raised
Matt_King: If you visit the current "About" page, it includes an introduction to the APG
Matt_King: The structural change to this pull request, is that we are going to replace the content so that it will be a little more like the "practices" page
Matt_King: This gives this a surface where we can include a lot of things about the APG such as our coding guide and instructions on contributing to the APG
Jem: So each part of the "about" page is presented on a separate page?
Matt_King: Yes, just like in "Practices"
Jem: Can we change the order of the content?
Matt_King: Definitely. I'd like for the "Introduction" to be at the top, but otherwise, I'm open to suggestion
Jem: I like having "ARIA Basics" as a second topic is a good idea. I also like having the "Coverage and Quality Report" toward the end, as you've placed it.
Matt_King: Regarding the Introduction--we've had many issues asking about the purpose of the APG (e.g. "Is APG a 'standard?'). That's part of what motivated me to structure this introduction as I have
Matt_King: I'd like feedback on the language around "Exercise caution"
Matt_King: Thinking about the kinds of questions we get, I'm trying to get readers to treat the APG with the appropriate level of respect. It's not a standard, but we're pulling together a lot of information from standards
Matt_King: I'd like readers to understand the implications of deviation from these recommendations
Matt_King: Does this take on a good, positive tone but still convey that message in a meaningful way?
jongund: I think you may want to re-emphasize that the examples are designed to conform to standards, even though they aren't standards themselves
jongund: Maybe specify which standards the examples are implementing (or at least, some of the standards)
Matt_King: I don't know how we're going to bring people in to the introduction, yet. We may want something on the home page...
Jem: When I read the content, I know what you mean by "APG is not a UI Design System," but I think the wording of that heading is somewhat misleading
Jem: I think the word "System" bothers me because I worry that it might exclude UI designers. Maybe "APG is not a UI Design Component" is more inclusive
jugglinmike: What about "APG is not a UI Design Framework" ?
jamesn: Or "APG is not a Design System" ?
Matt_King: Or "APG is not a Design System or Framework"
Matt_King: For "Assumed Prerequisite Knowledge", I was trying to avoid the term "prerequisite", but I couldn't find a way to do that
Matt_King: I was also trying to avoid using the second-person voice, even though I am trying to answer the question, "are you ready for APG?"
<Jem> +1 to Jon's inclusive approach
jongund: I'd like to see it made more inviting. To say that, "there's valuable stuff here even if you're not an accessibility expert"
Jem: This is awesome, Matt_King