Meeting minutes
Review agenda and next meeting date
<Matt_King> View agenda at https://
<Matt_King> Next meeting scheduled for May 23.
ARIA Authoring Practices Task Force Weekly Teleconference
site updates
<Matt_King> Questions from Kevin:
<Matt_King> • Primary vs secondary navigation reflow - The solution proposed for reflowing the navigation only reflows the secondary (left hand nav) and does not do anything with the primary main nav (APG Home, Patterns, Practices...). This is ok on the mock ups but a few more words or a slightly narrower viewport and that nav becomes difficult to use. The current approach is to put this in a scrolling...
<Matt_King> ...div which I don't really see as ideal.
<Matt_King> • Two scrolling areas - just following on from the scrolling primary nav, the solution proposed suggests a scrolling secondary nav. This would put two scrolling areas in the browser. I know from dim and distant usability testing that this can cause problems for some people. The main risk I would see with this is that users miss the scroll and don't find the items near the bottom of the list.
Mockups for same level navigation in Single Pattern and Single Practice pages
github: w3c/
Matt_King: The issue related to the top navigation could be treated as something separate, right?
jamesn: I think so, yes
Matt_King: We may need to hold a call with Isaac, Kevin, and Sean in order to move this forward
jamesn: The W3C menu button doesn't appear to satisfy accessibility standards. For instance, the menu it opens is many "Tab" presses away
jongund: I agree; it doesn't seem like something we can use on APG
Matt_King: Do we need to get Isaac back in this meeting in order to re-present? Or is the material he provided in the issue sufficient?
jamesn: In Isaac's design, the position of the menu on mobile doesn't seem correct. If the focus automatically moves to the menu, then I might be okay with it
jamesn: On the WAI site design, the intermediate state (where one menu is collapsed and the other is not) is what concerns me
Matt_King: When the second nav is collapsed, where should the first one be positioned?
Matt_King: An action item is that Isaac should update the mobile version
Matt_King: is there anything about the desktop (or "full") view that should be updated?
jamesn: No, I'm okay with that
Matt_King: There also needs to be an affordance for collapsing the menu. It looks like there is a button at the bottom, but it should be right at the beginning
Matt_King: The current state should be rendered consistently in both navs
jongund: The underline makes it look like a heading to me
jongund: Maybe a vertical bar on the left side would avoid giving the appearance of a heading
Matt_King: When the second nav is collapsed, it is not positioned in the same place that it would appear if you were to expand it. The collapsed form of it and the expanded form of it should be in the same place
Matt_King: Also, two problems with the top menu. First is that it doesn't collapse on mobile, and the current state is visually communicated through color alone (which is a WCAG issue)
Datepicker Modal Dialog: Fixed next/prev month bug and improve adherence with APG code style guide
github: w3c/
Matt_King: jongund , about two weeks ago, jugglinmike posted feedback for you on the tests
jongund: I'll take a look
Listbox Examples: Update scrolling of listbox item with focus into view when page is magnified
github: w3c/
Matt_King: We're waiting on test review and code review from Alex_Flenniken
Add landmark pattern page
github: w3c/
Matt_King: The preview build hasn't rebuilt, and I don't know how to trigger it. I wish I knew how to do that
Matt_King: We're waiting on review from Mark, Andrea, and Kurt. But that might have to wait until we figure out how to rebuild the preview
jamesn: It looks like the script exited with a non-zero exit code. I think the script isn't reporting its error codes correctly
jamesn: But despite this, the relevant commits are rendered with green "check mark" icons on the pull request page
Matt_King: I've converted the pull request as a draft while we work this out. When we get the preview updated, I'll remove the "draft" status
Grid cell content can be actionable and editable
github: w3c/
(CurtBellew restates the problem)
CurtBellew: A cell might have two different kinds of actions: one to update the contents, and one to perform some action (e.g. open a dialog)
CurtBellew: Right now: a cell can do one of those two things, and the "Enter" and "F2" key will perform the same one of those
Matt_King: There aren't real conventions for this, yet
Matt_King: Google Sheets is modeled after Excel, and they're using similar design for this
CurtBellew: The people asking about this are the authors of components that are widely used across all of Oracle
CurtBellew: In one case, we have a field that is editable and also has a popup dialog. There's a lot of instruction to explain to users how to use that. If we could settle on a convention here (e.g. different behaviors for each of "Enter" and "F2"), then that could solve the problem. I don't know if that breaks the Internet or anything.
Matt_King: Or pressing "Enter" could just give people the options
CurtBellew: I think that design-wise, there's interest in making this a "one-click" kind of action
Matt_King: You may want to check out Google Sheets for inspiration
Matt_King: Please don't put in instructions and please don't use aria-haspopup. In something like this, that would drive people bananas!
Matt_King: I think we should have a demo in APG that shows an advanced datagrid
CurtBellew: I'd love to do that, but I'll see how much progress I make and how much else I have going at work
CurtBellew: Since there's nothing that's necessarily prescribed, then I'm comfortable closing this issue