Meeting minutes
<jongund> prenset+ jongund
<Jem> https://
Setup and Review Agenda
Jem: Today will be the second-to-last meeting this year. The schedule is available in today's agenda
Status of Site Updates
Jem: Four pull requests were included in a release published today
Jem: Five more pull requests are targetted for the December 18th branch cut
Jem: All nine pull requests are listed in today's meeting agenda
<Jem> The changed text is
<Jem> "This rating widget employs a slider because of the relatively large number of values on its scale; it provides a ten-point scale.
<Jem> For inputs with seven or fewer choices,another pattern that could be used is radio group as demonstrated by the
<Jem> <a href="../../radio/examples/radio-rating.html">Rating Radio Group Example</a>.
<Jem> However, when there are more than seven choices, the radio group pattern is less friendly to keyboard and assistive technology users because it does not provide as many ways of easily navigating through choices as other input patterns, such as
<Jem> <a href="../slider-pattern.html">slider</a>,
<Jem> <a href="../../spinbutton/spinbutton-pattern.html">spin button</a>,
<Jem> <a href="../../combobox/combobox-pattern.html">combobox</a>,
<Jem> and <a href="../../listbox/listbox-pattern.html">listbox</a>."
<Jem> https://
PR 2775: Feed Example: Move display of example from separate page into standard APG example page by ariellalgilmore
github: w3c/
Matt_King: Ctrl+N is moving focus to the "feed delay" dropdown, which is at the top of the feed
Matt_King: We could add some kind of focusable element inside the example at the end of the feed--right outside of the feed
jugglinmike: Or a "fake footer" since that's the kind of content which typically follows a feed and which can be difficult to access
jugglinmike: We can describe it very literally so that folks recognize how it fits in the example. "This is a simulated page footer" or something like that
Matt_King: I like that. Maybe a fake "terms of use"
Matt_King: Or a button that opens a standard browser alert
ariellagilmore: So this button will serve as an in-document destination for the "Ctrl+N" keyboard shortcut
ariellagilmore: I can add this to the pull request
Tab behavior in disclosure navigation menu
Matt_King: In the interest of time, we'll revisit this issue in our next meeting
Inconsistencies in Page Up and Page Down guidance
github: w3c/
Matt_King: This person is pointing out that many of our examples do a lot of different things with "Page up" and "page down"
Matt_King: Those buttons behavior differently on macOS and Windows
Matt_King: There are three questions here
Matt_King: Even though this issue is generally about "page up" and "page down", I'm not sure if there's one answer here. The best way to triage may be to break it up into multiple issues
CoryJoseph: I can share some feedback on the issue (though I may need a few weeks)
Issue 2881 - Should there be preference for using hidden attribute?
github: w3c/
Matt_King: Looking at the code for Tree Grid, we're hiding and unhiding using CSS
Matt_King: This person is asking, "wouldn't the code be more clear if it used the 'hidden' attribute instead?"
jongund: I don't think it makes a difference; just a different coding style
jugglinmike: Using the "hidden" HTML attribute is less ambiguous, and I would prefer it, but I think a CSS class name like "hidden" is relatively descriptive
CoryJoseph: I feel the same
Issue 2864 - High contrast support practices
github: w3c/
jongund: We have a lot of examples which are just using the current color value. As a result, we're kind of relying on the background color being managed by the page
Matt_King: As for the approach, we could just start randomly changing individual patterns one-by-one
Matt_King: Or we could create a project to track the work across the site
Matt_King: It might also touch on the idea we've discussed about a code quality report
Jem: It sounds like support for CSS4 has improved since we last considered forced colors. Do you know anything about this, jongund?
jongund: I tried using it, and it seems to be better-supported, now
ariellagilmore: We use media queries in Carbon, though I don't think we've used forced colors, yet
jongund: I think a new practice would be a good place to collect the ways people successfully use the technology
Matt_King: Something like this could fit into a practice
Matt_King: jongund, do you want me to set up a pull request for a new "practices" page about high contrast?
jongund: Yeah, that would be helpful
Matt_King: Is this something that you could test for in the code quality report?
jongund: Yeah, we could check for the presence of the media query
jongund: At this point, we could just look at the the examples which are using "current-color". Those would be the high-priority ones
Matt_King: Okay, I'll start a pull request for a "high-contrast support" practice. And jongund, you can start a pull request for the code quality report