18:04:33 RRSAgent has joined #aria-apg 18:04:37 logging to https://www.w3.org/2024/06/25-aria-apg-irc 18:04:47 rrsagent, make log public 18:04:55 Zakim, start the meeting 18:04:55 RRSAgent, make logs Public 18:04:57 Meeting: ARIA Authoring Practices Task Force 18:05:08 present+ jugglinmike 18:05:29 scribe+ jugglinmike 18:07:05 meeting: ARIA Authoring Practices Task Force Weekly Teleconference 18:07:33 Matt_King_ has joined #aria-apg 18:07:55 Jem has joined #aria-apg 18:08:04 arigilmore has joined #aria-apg 18:08:18 present+ 18:08:27 rrsagent, make minutes 18:08:28 I have made the request to generate https://www.w3.org/2024/06/25-aria-apg-minutes.html Jem 18:08:35 arigilmore+ 18:08:38 present+ 18:09:12 https://github.com/w3c/aria-practices/wiki/June-25%2C-2024-Agenda 18:09:13 present+ Matt_King 18:09:40 Topic: Setup and Review Agenda 18:09:46 Jem: Any requests for change to agenda? 18:10:11 Jem: hearing none, we'll move forward with the agenda as planned 18:10:17 Jem: Next meeting: July 2 18:10:23 Jem: No meeting July 9 18:10:30 Topic: Publication planning 18:10:59 Matt_King: I think we should shoot for the 23rd or 30th of July... 18:11:14 Matt_King: Daniel isn't present today, so I don't know if there are any considerations on the W3C side. 18:11:25 Matt_King: Are there any considerations relevant on the Bocoup side? 18:11:49 howard-e: Either date is okay on our end 18:12:13 Matt_King: I guess the problem with the 22nd is that it only leaves us two more meetings 18:12:28 Matt_King: That said, we can probably get a lot of the pending items done in that time 18:13:05 Matt_King: The high-contrast work might take longer, though, especially since John Gunderson will only have partial availability 18:13:53 Matt_King: Pending final review by Howard: PR 3024 - Coverage and Quality Report: Add reporting on use of forced-colors media query and currentcolor value by jongund https://github.com/w3c/aria-practices/pull/3024 18:14:09 Matt_King: It didn't look like that was getting updated, so I put a comment in the pull request and asked you to re-review it 18:14:39 howard-e: Yup, I was able to check that out. There was an issue with the build repository (it came from the experimental content push that we did recently). That's been resolved 18:14:55 howard-e: I submitted a patch for that this morning; now, the pull request generates properly 18:15:19 howard-e: Separately, the coverage check is failing. The lint stage was never capturing whenever the script itself is changed alone in a pull request 18:15:26 Matt_King: You mean the coverage script, right? 18:15:28 howard-e: Right 18:15:53 howard-e: My thinking is that if the script itself is changing structural details about the report, then it ought to trigger 18:16:06 Matt_King: Ah, so that would include changes to the template, too, right? 18:16:08 howard-e: Right 18:16:26 howard-e: I submitted pull request #3048 for this purpose 18:16:49 Matt_King: So if we merge #3048, then the job we re-run if we push another commit to #3024 18:16:52 howard-e: That's right 18:17:40 Matt_King: I'll take a look at #3048, merge that, then merge "main" into #3024. That merge ought to make the job run again, right 18:18:02 howard-e: I think you'll have to manually re-run even in that case, since your merge commit won't touch the files which are being monitored 18:18:12 Matt_King: Got it. So #3024 is on its way 18:18:38 Matt_King: next up, Review pending: PR 3025 - Ratings Slider: Use buttontext instead of linktext system color in high contrast mode by jongund https://github.com/w3c/aria-practices/pull/3025 18:18:47 Matt_King: It looks like John added some screen shots 18:18:55 Jem: Got it. I will get to another review today 18:19:47 Matt_King: So we're thinking of a release date of July 29th 18:19:52 Jem: That sounds good to me 18:20:24 Matt_King: If we have everything ready except for the high-contrast page, and it looks like the high-contrast page is going to take longer, we can potentially pull the release date forward to July 22 18:20:35 Topic: New member 18:20:48 Jem: I'd like to add a quick agenda item 18:22:51 Jem: Adam Page is going to join the Working Group 18:23:29 Jem: I'd like to give them an orientation on July 15, and it would be great if you folks could join. I will send you all an invitation. 18:23:30 s/Working Group/APG Taskforce/ 18:23:50 Topic: Change to HTML source section on example pages 18:23:57 jongund has joined #aria-apg 18:24:00 github: https://github.com/w3c/aria-practices/pull/3041 18:24:11 Matt_King: Right now, this pull request is changing a single example page 18:24:28 Matt_King: But if folks agree with this direction, then we'd like to make the change to every single page 18:25:57 arigilmore: I updated the JavaScript to inject an "Open in Codepen" to an element with a certain HTML ID. All we'll need to do to add the change to other pages is add that HTML ID to each of the HTML files. 18:27:44 Matt_King: Is the button positioned similar to how it's positioned in the "example" section? 18:28:12 Matt_King: Yeah, it follows the paragraph that describes the section, and it precedes the rendering of the source code 18:28:25 s/Matt_King/arigilmore/ 18:28:46 Matt_King: And does it behave appropriately for alternate viewport sizes? 18:28:48 arigilmore: Yes 18:29:06 Jem: Do we need to have a distinguishable button text for these two buttons? 18:29:22 Matt_King: No, because they both do the exact same thing, so it's important that they have the same label 18:30:10 Jem: Ah, I understand, now (I thought the behavior of the second button was special for the HTML code) 18:30:35 Matt_King: Before we make the change on 59 other example pages, does this look good? 18:30:55 Jem: Yeah! 18:33:25 Matt_King: Okay, then I think we're good to go 18:33:59 Matt_King: There are 3 pages (e.g. listbox, layout grid, and data grid) that have three examples on the same page, so pay special attention to those ones 18:34:03 arigilmore: Got it 18:34:41 Matt_King: By the way, I've been wanting to refactor those so there is only one example per page, but that involves changing some of the prose, so it's taking me some time 18:35:07 Matt_King: Anyway, this is one of those ones that we don't want to sit around for too long because it touches so many files 18:35:33 Topic: New patterns page filter 18:35:55 github: https://github.com/w3c/aria-practices/pull/3043 18:36:17 Jem: This is awesome! 18:36:28 Matt_King: I have a few questions 18:36:47 Matt_King: It seems like the filter happens dynamically as you type. That how it feels to me as a screen reader user 18:37:04 Matt_King: I didn't have to press the "submit" button, so I don't know what the purpose of the "submit" button is 18:38:39 Matt_King: Are there any circumstances where you need that button? 18:39:12 howard-e: It doesn't seem like there is a need for that button 18:39:46 Matt_King: I do think that a button labeled "Clear Filter" would be very useful. Without it, in order to see all the patterns again, you have to select all the text and delete it 18:40:36 arigilmore: Carbon offers a feature like this using an "X" button inside the search bar 18:41:02 Matt_King: The "clear" button is visually inside the search bar, but not in terms of the DOM, right? 18:45:01 arigilmore: That's right 18:45:33 https://carbondesignsystem.com/components/search/code 18:46:27 jongund has joined #aria-apg 18:48:58 Matt_King: We should change the placeholder text to read "Filter patterns" 18:49:11 Jem: Maybe the heading should read "Search patterns" instead of "Filter" 18:49:46 Matt_King: That may be misleading. Some folks may read the worth "Search" and expect that their query will be evaluated against the entire content of each pattern 18:50:06 Matt_King: As it stands, the query is only matching against the titles of the patterns that are present on the page 18:50:19 Matt_King: I think that's more generally recognized as a "filter" operation 18:51:01 Jem: Okay; could we also change the heading to "Filter patterns" instead of just "Filter"? 18:51:04 Matt_King: Sure 18:51:18 Topic: Three or more levels in disclosure nav menus 18:51:32 github: https://github.com/w3c/aria-practices/issues/3045 18:52:11 Matt_King: I think this is a great question 18:52:22 Matt_King: I don't feel like this is something we necessarily want to do to the APG example 18:52:40 Matt_King: Although I would note that the example does kind of flatten the hierarchy in that navigation 18:53:16 https://www.w3.org/WAI/ARIA/apg/patterns/disclosure/examples/disclosure-navigation/ 18:53:28 Matt_King: If we look at the disclosure show/hide navigation menu example 18:53:43 Matt_King: We have the "mythical university navigation" which has "about", "admissions", etc. 18:54:04 Matt_King: If you expand "About", we have "Overview", "Administration", "FAQs", and "Campus Tours" 18:54:24 https://www.w3.org/WAI/ARIA/apg/patterns/menubar/examples/menubar-navigation/ 18:54:49 Matt_King: In navigation menu bar, we have two levels 18:55:26 Matt_King: Under "FAQs" in the navigation menu bar, it expands to "History", etc 18:55:36 Matt_King: We don't have that level shown in the "disclosure" 18:55:44 Matt_King: In that way, these examples are not equivalent 18:56:02 Matt_King: Should we show what it would be like to do a third level in this navigation in the disclosure version? 18:56:24 Matt_King: The person who raised this issue is asking, if we were to do that, how would we do it? 18:56:48 Matt_King: From an ARIA standpoint, it's fairly straightforward. That "FAQs" link wouldn't be a link; it would be a disclosure button 18:58:18 Matt_King: When you compare these two examples visually, are they different in terms of the way they cover up other content? 18:58:43 Matt_King: Do the disclosure ones visually overlay the disclosure content on top of the content that's below it? Or do they move it down? 18:59:03 Matt_King: Because menus always pop *over* content, but disclosures generally push content down 19:00:31 arigilmore: It appears overlaid on top of the content 19:01:26 jugglinmike: We're over time 19:01:39 Matt_King: We're not going to wrap up this issue today. We'll keep it on the agenda for next time 19:01:51 Zakim, end the meeting 19:01:51 As of this point the attendees have been jugglinmike, howard-e, Jem, Matt_King 19:01:54 RRSAgent, please draft minutes v2 19:01:55 I have made the request to generate https://www.w3.org/2024/06/25-aria-apg-minutes.html Zakim 19:02:01 I am happy to have been of service, jugglinmike; please remember to excuse RRSAgent. Goodbye 19:02:02 Zakim has left #aria-apg 19:02:13 RRSAgent, leave 19:02:13 I see no action items