17:59:28 RRSAgent has joined #aria-apg 17:59:32 logging to https://www.w3.org/2023/10/31-aria-apg-irc 17:59:32 RRSAgent, make logs Public 18:00:03 please title this meeting ("meeting: ..."), Matt_King 18:00:04 MEETING: ARIA Autoring Practices Task Force 18:00:08 MEETING: ARIA Authoring Practices Task Force 18:00:20 CHAIR: Jemma 18:00:25 present+ 18:00:26 jugglinmike has joined #aria-apg 18:00:31 rrsagent, make minutes 18:00:32 I have made the request to generate https://www.w3.org/2023/10/31-aria-apg-minutes.html Matt_King 18:00:40 arigilmore has joined #aria-apg 18:00:48 jongund has joined #aria-apg 18:00:52 jongund has left #aria-apg 18:00:58 jongund has joined #aria-apg 18:01:06 present+ jongund 18:01:29 present+ jugglinmike 18:02:44 howard-e has joined #aria-apg 18:03:00 present+ Daniel 18:03:05 present+ 18:03:48 siri has joined #aria-apg 18:04:02 scribe+ jugglinmike 18:04:21 Topic: Setup and Review Agenda 18:04:50 [Jem summarizes the agenda] 18:05:11 Jem: Before we get started, would anyone like to change this in some way? 18:05:28 Jem: Hearing none, we'll keep it as-is 18:05:34 https://github.com/w3c/aria-practices/wiki/October-31%2C-2023-Agenda 18:05:43 Topic: Setup and Review Agenda 18:05:58 Jem: We will meet next week, November 7 18:06:40 Jem: We're considering cancellations on November 14 (due to Matt_King's absense) and November 21 (due to the US holiday of Thanksgiving) 18:07:43 Jem: We'll decide about the 14th next week 18:09:01 Topic: Status of Site Updates 18:09:20 Jem: https://github.com/w3c/aria-practices/pull/2818 is ready for the next publication 18:09:44 Jem: The agenda lists another five patches which are ready for the next publication 18:10:13 Matt_King: It doesn't seem like we're going to have many of those five complete this week 18:10:26 Matt_King: I guess it depends on how much progress we make 18:11:08 Matt_King: I'd prefer to save the "keyboard" patch for last because it will touch so many pages 18:11:46 Matt_King: Regard the feed example, we're still waiting on input from Alex on the iframe issue 18:12:10 s/Regard/Regarding/ 18:12:36 Matt_King: Alternatively, we could remove the iframe. I don't have a strong point of view on that 18:12:41 present+ arigilmore 18:13:03 arigilmore: I'm happy to wait for the solution for the iframe 18:13:21 Matt_King: Yeah, I was kind of looking at it as an experiment for using iframes for all the examples 18:13:43 howard-e: I can take a look, though I've lost a bit of context 18:13:49 jugglinmike: I can bring you up to speed 18:14:09 Matt_King: I'm skeptical that we can have a substantial update ready by Monday 18:14:50 Matt_King: If we wait two weeks, we might be able to get some other items in 18:15:22 Matt_King: I suggest that we don't push ourselves to publish next week, and that we target November 14, instead 18:15:26 Jem: That sounds good to me 18:15:41 Topic: PR 2839 - set aria-expanded false when menus are closed 18:15:58 github: https://github.com/w3c/aria-practices/pull/2839 18:16:09 arigilmore: I worked on this with Andrea 18:17:00 arigilmore: Oh, wait, no. Andrea worked on this alone 18:17:13 Matt_King: This is updating JavaScript, documentation, and tests 18:17:45 Matt_King: I don't see any JavaScript changes here 18:18:36 arigilmore: I'll let Andrea know and see if she needs any help working on it 18:18:56 Matt_King: Probably the more complicated part of this fix will be writing a test 18:19:21 Matt_King: It at least won't be starting from scratch--there is already a test for setting aria-expanded to "true" 18:19:36 Jem: We eventually need a reviewer... 18:19:54 Matt_King: Let's wait until we have the patch closer to ready 18:20:26 Topic: Issue 2501 - Rating slider redesign 18:20:49 github: https://github.com/w3c/aria-practices/pull/2831 18:21:03 Matt_King: We assigned reviewers, and the primary thing that came up was related to the design review 18:22:51 arigilmore: I performed a visual review, and I found one issue. On mobile, the UI extends beyond the width of the page and triggers the rendering of a horizontal scroll bar 18:22:58 Jem: Good catch, arigilmore! 18:23:29 Matt_King: do you think you can address that soon, jongund? 18:23:30 present+ jongund 18:23:49 jongund: WCAG has target size requirements 18:24:41 Matt_King: The minimum target size for AA is 24-by-24. We have 10 targets on this thing arranged horizontally 18:24:55 Matt_King: That means the slider itself can't be less than 240 pixels 18:26:39 arigilmore: Could it become a vertical slider? 18:27:41 jongund: I would rather see a note explaining how to accommodate mobile devices 18:27:58 Matt_King: It should still be functional on mobile, though... 18:28:13 Matt_King: What if we do make it scrunched down and failed WCAG on mobile, but it still works? 18:28:19 Matt_King: Is that better? 18:35:11 (monitoring online) - the width of each of the targets is 48 - why can't they be made a little narrower and still pass wcag 18:36:43 jugglinmike: We might not have a WCAG concern, here. It is still a slider--you can still drag along the spectrum of values 18:37:08 jugglinmike: ...we just happen to be rendering the value "stops" with vertical lines 18:37:36 jugglinmike: ...so while it appears as a row of ten buttons, it is still fundamentally a slider widget 18:37:48 Matt_King: I think jugglinmike may have a point there 18:38:53 jongund: What's the mobile viewport width that we're targetting, anyway? 18:39:00 Matt_King: We don't have a specification for that 18:39:14 Jem: I typically test with the iPhone width 18:39:49 Matt_King: I'm wondering if there should be something in our code guide on this topic 18:40:42 Matt_King: I bet Carbon has some sort of spec for its responsive design requirements 18:41:21 we should support 1280 at 400% zoom - which equals 320 18:41:31 [arigilmore could not respond to this as she left the meeting] 18:41:56 Topic: Issue 2842 - Bug in modal dialog example when accessed on mobile 18:42:22 github: https://github.com/w3c/aria-practices/issues/2842 18:42:40 Matt_King: We received both an issue and a pull request from this contributor--that's great! 18:43:12 Matt_King: But before we look at the patch, we should agree on whether this is truly a bug as raised 18:43:32 present+ siri 18:43:42 siri: It is somewhat subjective 18:44:28 Matt_King: can others reproduce whatever is in the provided screen shot? 18:50:37 [the group works to reproduce the problem, eventually discovering that is occurs in a nested modal dialog] 18:51:14 jongund: There appears to be an unrelated problem--with touch, I can't close the dialog 18:51:26 howard-e: I can reproduce that, jongund 18:53:56 Jem: The patch solves the "obscuring button" problem. I'm using my mouse to confirm this, so I can't confirm touch 18:55:15 howard-e: I can confirm the fix as well. It also fixes "touch" for me (I'm using a simulated version of touch with my browser's developer tools) 18:55:24 howard-e: The best confirmation will be from a true mobile device 18:57:08 Matt_King: I think I can merge this fix because it is so simple. Even if it doesn't address the problem that jongund reported, I think it would still be worth merging 18:57:22 jongund: I can't verify with my phone right now 19:01:29 Zakim, end the meeting 19:01:29 As of this point the attendees have been Matt_King, jongund, jugglinmike, Daniel, howard-e, arigilmore, siri 19:01:31 RRSAgent, please draft minutes 19:01:32 I have made the request to generate https://www.w3.org/2023/10/31-aria-apg-minutes.html Zakim 19:01:38 I am happy to have been of service, jugglinmike; please remember to excuse RRSAgent. Goodbye 19:01:39 Zakim has left #aria-apg 19:06:23 RRSAgent, leave 19:06:23 I see no action items