Meeting minutes
Review agenda and next meeting dates
Matt_King: Requests for changes to agenda?
Matt_King: Given that Boaz and Isaac are present, we'll move the "Home page proposal" topic up.
Matt_King: Even though we keep "kicking the can" on the verdict API
Matt_King: Next community group meeting: Thursday August 22
Matt_King: Next AT Driver Subgroup meeting: Monday September 9
Current status
Matt_King: I won't spend much time on this today; please refer to the agenda for details
https://
Testing of disclosure navigation menu
Dean_Hamack: There are no conflicts in this case
Dean_Hamack: The issue here is that the button was dimmed for the tester, so they could not run the test
Matt_King: That button disablement is by design
IsaDC: This is a well-known VoiceOver issue
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
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"
Dean_Hamack: I just re-ran, and that did indeed occur
Dean_Hamack: Now, I'm getting the same result that IsaDC reported
Matt_King: there's something bizarre about VoiceOver and Safari that we've discovered when you programmatically set focus
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
Matt_King: That helps promote consistency
Dean_Hamack: Well, after learning all this, I'm willing to defer to IsaDC's results
Dean_Hamack: I also had a question about "list boundary conveyed"
Matt_King: We only check "unexpected behavior" when it's a behavior that is not described by any of the assertions
Matt_King: We should make boundary assertions optional from some of these commands
Testing action menu button with activeDescendant
Joe_Humbert: This isn't pressing; we can discuss it asynchronously
Home page proposal
isaacdurazo: I posted mock-ups and a description to an issue
<isaacdurazo> w3c/
isaacdurazo: This is a more polished version of the landing page. It has branding with a logo mark
isaacdurazo: The structure is pretty much the same
isaacdurazo: At the top, right after the main navigation, we have a "hero" section with the same H1
isaacdurazo: Then we have an introductory text with a few calls-to-action: learn more and get involved
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
isaacdurazo: This is a placeholder, but the idea is to have a screen shot of the app
isaacdurazo: After the "hero" section, we have a box that includes a note about how this project is managed
isaacdurazo: The "How we are improving interoperability" section still has four columns
isaacdurazo: I've added some placeholder text to describe that section
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
isaacdurazo: For the "getting involved" section, I've built a two-column layout
isaacdurazo: The left-hand side is exactly the same copy as what we already have
isaacdurazo: For the right-hand side, I'm proposing we add another screen shot of the app
Matt_King: Where and how is the W3C logo featured?
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?
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
isaacdurazo: But it could also go in some sort of "about" page
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
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
Matt_King: Agreed
Matt_King: jongunderson suggested that the "skip to" button should be visible at all times--not just when visitors "tab in" to the page
isaacdurazo: I do remember that, yes
Matt_King: I think this page might be a good place to experiment with an idea like that
Lola_Odelola: I think the W3C has a style guide for things like this
Matt_King: Potentially. This could get complicated if we try to integrate it too heavily into the W3C website
Boaz_Sender: I can work with isaacdurazo to learn about the opportunities here
Lola_Odelola: here's a link to the style guide: https://