17:01:15 <RRSAgent> RRSAgent has joined #aria-at
17:01:19 <RRSAgent> logging to https://www.w3.org/2024/08/14-aria-at-irc
17:01:25 <jugglinmike> rrsagent, make log public
17:01:31 <jugglinmike> Zakim, start the meeting
17:01:31 <Zakim> RRSAgent, make logs Public
17:01:33 <Zakim> please title this meeting ("meeting: ..."), jugglinmike
17:02:23 <jugglinmike> meeting: ARIA and Assistive Technologies Community Group Weekly Teleconference
17:02:29 <jugglinmike> present+ jugglinmike
17:02:33 <jugglinmike> scribe+ jugglinmike
17:02:44 <howard-e> howard-e has joined #aria-at
17:02:49 <howard-e> present+
17:03:05 <Joe_Humbert> present+
17:05:58 <Matt_King> Matt_King has joined #aria-at
17:06:15 <jugglinmike> present+ Matt_King
17:06:24 <jugglinmike> present+ IsaDC
17:06:28 <jugglinmike> present+ howard-e
17:06:37 <jugglinmike> present+ Isaac_Durazo
17:06:44 <jugglinmike> present+ Boaz_Sender
17:07:05 <jugglinmike> present+ James_Scholes
17:07:20 <jugglinmike> present+ Dean_Hamack
17:07:29 <jugglinmike> present+ Lola_Odelola
17:07:45 <jugglinmike> Topic: Review agenda and next meeting dates
17:08:13 <jugglinmike> Matt_King: Requests for changes to agenda?
17:08:54 <jugglinmike> Matt_King: Given that Boaz and Isaac are present, we'll move the "Home page proposal" topic up.
17:09:18 <jugglinmike> Matt_King: Even though we keep "kicking the can" on the verdict API
17:09:29 <jugglinmike> Matt_King: Next community group meeting: Thursday August 22
17:09:39 <jugglinmike> Matt_King: Next AT Driver Subgroup meeting: Monday September 9
17:09:51 <jugglinmike> Topic: Current status
17:10:09 <jugglinmike> Matt_King: I won't spend much time on this today; please refer to the agenda for details
17:10:14 <jugglinmike> https://github.com/w3c/aria-at/wiki/August-14%2C-2024-Agenda
17:10:23 <jugglinmike> Topic: Testing of disclosure navigation menu
17:10:40 <jugglinmike> Dean_Hamack: There are no conflicts in this case
17:11:11 <jugglinmike> Dean_Hamack: The issue here is that the button was dimmed for the tester, so they could not run the test
17:11:25 <jugglinmike> Matt_King: That button disablement is by design
17:12:35 <jugglinmike> IsaDC: This is a well-known VoiceOver issue
17:13:05 <jugglinmike> IsaDC: What happened here is that you have to reload the page to get the "run setup script" button enabled. We don't manually move cursors around
17:14:35 <jugglinmike> Matt_King: Dean_Hamack, when you performed the test, after you pressed the "run setup script button", the focus should have been placed automatically by the script on the "navigate backward from here"
17:15:32 <jugglinmike> Dean_Hamack: I just re-ran, and that did indeed occur
17:18:02 <jugglinmike> Dean_Hamack: Now, I'm getting the same result that IsaDC reported
17:18:32 <jugglinmike> Matt_King: there's something bizarre about VoiceOver and Safari that we've discovered when you programmatically set focus
17:20:00 <jugglinmike> James_Scholes: We also don't have a "tear down" system in place. That's why the button is disabled and you have to reload the page
17:20:24 <jugglinmike> Matt_King: That helps promote consistency
17:20:47 <jugglinmike> Dean_Hamack: Well, after learning all this, I'm willing to defer to IsaDC's results
17:22:12 <jugglinmike> Dean_Hamack: I also had a question about "list boundary conveyed"
17:22:48 <jugglinmike> Matt_King: We only check "unexpected behavior" when it's a behavior that is not described by any of the assertions
17:38:58 <isaacdurazo> isaacdurazo has joined #aria-at
17:43:48 <jugglinmike> Matt_King: We should make boundary assertions optional from some of these commands
17:44:34 <jugglinmike> Topic: Testing action menu button with activeDescendant
17:45:06 <jugglinmike> Joe_Humbert: This isn't pressing; we can discuss it asynchronously
17:45:32 <jugglinmike> Topic: Home page proposal
17:45:41 <jugglinmike> present+ isaacdurazo
17:45:56 <jugglinmike> isaacdurazo: I posted mock-ups and a description to an issue
17:46:13 <isaacdurazo> https://github.com/w3c/aria-at-app/issues/1192
17:47:04 <jugglinmike> isaacdurazo: This is a more polished version of the landing page. It has branding with a logo mark
17:47:10 <jugglinmike> isaacdurazo: The structure is pretty much the same
17:47:33 <jugglinmike> isaacdurazo: At the top, right after the main navigation, we have a "hero" section with the same H1
17:47:59 <jugglinmike> isaacdurazo: Then we have an introductory text with a few calls-to-action: learn more and get involved
17:48:35 <jugglinmike> isaacdurazo: Instead of the video we have on the landing page today, there is a partial screenshot of the app--the test plan status summary
17:48:46 <jugglinmike> isaacdurazo: This is a placeholder, but the idea is to have a screen shot of the app
17:49:15 <jugglinmike> isaacdurazo: After the "hero" section, we have a box that includes a note about how this project is managed
17:50:20 <jugglinmike> isaacdurazo: The "How we are improving interoperability" section still has four columns
17:50:59 <jugglinmike> isaacdurazo: I've added some placeholder text to describe that section
17:51:45 <jugglinmike> isaacdurazo: I've simplified the icons quite a bit. The idea is the same for each of them--I'm not trying to change the message they are trying to convey
17:52:08 <jugglinmike> isaacdurazo: For the "getting involved" section, I've built a two-column layout
17:52:25 <jugglinmike> isaacdurazo: The left-hand side is exactly the same copy as what we already have
17:52:39 <jugglinmike> isaacdurazo: For the right-hand side, I'm proposing we add another screen shot of the app
17:53:29 <jugglinmike> Matt_King: Where and how is the W3C logo featured?
17:53:56 <jugglinmike> Matt_King: The video has been extremely useful for me to bring new people into the project; I liked the fact that it was easy to find. Where is it now?
17:54:25 <jugglinmike> isaacdurazo: I haven't included it in this proposal, but I could see it in the "hero" section where I've included a screenshot of the application
17:54:45 <jugglinmike> isaacdurazo: But it could also go in some sort of "about" page
17:55:12 <jugglinmike> Matt_King: I wouldn't mind having a separate "about" page in the future, but I wouldn't want to take the video away in the mean time
17:55:55 <jugglinmike> isaacdurazo: I haven't included the W3C logo, I suppose because we don't currently use it. But I think that's an oversight and that it would be good to add it
17:56:03 <jugglinmike> Matt_King: Agreed
17:57:23 <jugglinmike> Matt_King: jongunderson suggested that the "skip to" button should be visible at all times--not just when visitors "tab in" to the page
17:57:28 <jugglinmike> isaacdurazo: I do remember that, yes
17:57:41 <jugglinmike> Matt_King: I think this page might be a good place to experiment with an idea like that
17:58:13 <jugglinmike> Lola_Odelola: I think the W3C has a style guide for things like this
17:59:04 <jugglinmike> Matt_King: Potentially. This could get complicated if we try to integrate it too heavily into the W3C website
17:59:28 <jugglinmike> Boaz_Sender: I can work with isaacdurazo to learn about the opportunities here
18:00:26 <jugglinmike> Lola_Odelola: here's a link to the style guide: https://w3c.github.io/design/styleguide/
18:01:30 <jugglinmike> Zakim, end the meeting
18:01:30 <Zakim> As of this point the attendees have been jugglinmike, howard-e, Joe_Humbert, Matt_King, IsaDC, Isaac_Durazo, Boaz_Sender, James_Scholes, Dean_Hamack, Lola_Odelola, isaacdurazo
18:01:33 <Zakim> RRSAgent, please draft minutes
18:01:34 <RRSAgent> I have made the request to generate https://www.w3.org/2024/08/14-aria-at-minutes.html Zakim
18:01:41 <Zakim> I am happy to have been of service, jugglinmike; please remember to excuse RRSAgent.  Goodbye
18:01:41 <Zakim> Zakim has left #aria-at
18:01:50 <jugglinmike> RRSAgent, leave
18:01:50 <RRSAgent> I see no action items