Meeting minutes
Status of Coming Site Updates
jugglinmike: The latest deploy is completed
Matt_King: I will validate the issues listed here in the agenda
jugglinmike: The link to the new "Landmarks" pattern is broken; it returns a 404/"Document not found error"
jugglinmike: We've only just now identified this, and we're currently investigating why it occurred in order to understand how to fix it and prevent similar errors in the future
Pull request reviews
Matt_King: I've merged "PR 2724: Example Pages: Change Javascript to JavaScript in h2 elements by mcking65" w3c/
Skipto menu on all pages: Update skipto.js script to version 5.1.6
github: w3c/
Matt_King: This was awaiting review
Matt_King: ariellalgilmore has approved the visual appearance. That's what I was looking for. Maybe this is ready to go
Checkbox Example (Mixed-State): Toggle on keyup to prevent continuous toggling by sivakusayan · Pull Request #2722 · w3c/aria-practices
github: w3c/
Matt_King: It seems like someone should have been assigned to review the code
andrea_cardona: I can review it
Matt_King: Awesome; I'll assign you right now
PR 2723: Select-only Combobox Example: Fix scroll event listener bug by ariellalgilmore
github: w3c/
Matt_King: This is ready for review; did we assign a reviewer last week?
andrea_cardona: We asked Valerie to review, and she said that she could
Matt_King: It's awesome to see spectranaut back in APG stuff
Feed Display Example Broken Star Images
github: w3c/
Matt_King: Paul Brown (GitHub handle "frozenzia") has volunteered to take this up, but they're having trouble running the tests on their Mac
andrea_cardona: I develop on a Mac. I can try to run these tests and comment on this issue about my experience
Matt_King: It appears as though there might be some documentation missing for folks who want to run the tests on Mac. The "command" versus "control" thing may be a red herring
jugglinmike: I can bring this to Carmen and see that someone from Bocoup takes a look at this alongside andrea_cardona
New Issue Action Planning
ARIA & Progressive Enhancement
github: w3c/
Matt_King: Most of the ARIA we add in APG is added dynamically
<siri> Can you add grid for layout issue for our next APG discussion. I need to dropout now
jugglinmike: I'm thinking about the Treeview pattern. Right now, if the user views the example with JavaScript disabled, it appears as a broken treeview. Wouldn't it be better to render that content as a list in that case?
jugglinmike: It might be better to describe this topic with the term "graceful degradation" rather than "progressive enhancement" because we don't necessarily believe the patterns in APG are "enhancements"
Matt_King: I agree that the "graceful degradation" is preferable, but I have more fundamental questions about this. I don't know how realistic it is for screen reader users to browse the web with JavaScript disabled
Matt_King: I don't personally browse with JavaScript disabled, so I may be biased, but we haven't typically considered it as a use case
jugglinmike: It sounds like what we're saying is: graceful degradation generally takes additional effort, so we would want evidence that the practice would benefit real end-users before making a recommendation in APG...
jugglinmike: ...and that we currently don't have evidence that screen reader users browse the web with JavaScript disabled.
Matt_King: That sounds right to me. However, this person is asking whether it is okay to make their implementations of the patterns degrade gracefully
Matt_King: And to that specific question, I think that yes, it is certainly okay (because that practice does not interfere with the behavior as outlined in APG)