17:51:18 RRSAgent has joined #aria-apg 17:51:18 logging to https://www.w3.org/2022/03/29-aria-apg-irc 17:51:31 Zakim has joined #aria-apg 17:51:49 MEETING: ARIA Authoring Practices Task Force 17:51:59 CHAIR: Jemma 17:52:05 rrsagent, make log public 17:52:09 present+ 17:52:17 rrsagent, make minutes 17:52:17 I have made the request to generate https://www.w3.org/2022/03/29-aria-apg-minutes.html Matt_King 17:56:15 jongunderson has joined #aria-apg 17:57:13 Jem has joined #aria-apg 17:58:18 rrsagent, make minutes 17:58:18 I have made the request to generate https://www.w3.org/2022/03/29-aria-apg-minutes.html Jem 18:00:40 Matt_King has joined #aria-apg 18:01:47 Meeting agenda: https://github.com/w3c/aria-practices/wiki/March-29,-2022-Agenda 18:01:56 present+ JaeunJemmaKu 18:03:18 rrsagent, make minutes 18:03:18 I have made the request to generate https://www.w3.org/2022/03/29-aria-apg-minutes.html Matt_King 18:05:28 Topic: setup and review agenda 18:07:17 siri has joined #aria-apg 18:07:37 Topic: Issue Triage 18:07:50 scribe: Sarah 18:07:54 sarah_higley has joined #aria-apg 18:07:57 present+ 18:07:59 https://github.com/w3c/aria-practices/issues?q=is%3Aissue+is%3Aopen+created%3A%3E2021-09-15+no%3Alabel+ 18:08:04 present+ jon 18:08:08 present+ siri 18:08:17 scribe: sarah_higley 18:09:45 MK: I thougth this search results issue was assigned to me, and we agreed it was out of scope 18:09:55 https://github.com/w3c/aria-practices/issues?q=is%3Aissue+is%3Aopen+created%3A%3E2021-09-15+no%3Alabel+ 18:10:22 zakim, current topic 18:10:24 I don't understand 'current topic', sarah_higley 18:10:45 present+ jamesnurthen 18:13:02 JK: we'll add the label wontfix 18:13:17 JK: next is #2048, managing focus using aria-activedescendant 18:13:21 https://github.com/w3c/aria-practices/issues/2048 18:13:43 JK: I don't know where we are in terms of aria-activedescendant 18:14:40 MK: we can add the documentation and guidance labels 18:14:56 MK: I am reluctant to commit a timeline for this one 18:15:01 MK: let's label it and leave it in the backlog 18:15:21 SH: is the fix just to add combobox and searchbox to textbox? 18:15:28 MK: I'm not sure, I guess I can open the file 18:16:05 JK: we can move on to the next item for now 18:16:16 https://github.com/w3c/aria-practices/issues/2044 18:16:18 https://github.com/w3c/aria-practices/issues/2044 18:16:49 JK: editorial? 18:17:06 MK: so this is in the pattern? 18:17:13 JG: this is from a while ago 18:17:31 JG: I think I was talking to someone who mentioned they didn't understand the tab behavior for menubar, so that's why I put the issue in 18:17:47 JK: so Jon, is it OK if we assign this to you, and you can suggest editorial aspects to make it clear? 18:18:05 JG: I can take a try at it 18:18:27 MK: if you can just pull in the quote to the issue, what is the text that you think is ambiguous 18:18:50 MK: I suppose if the whole pattern doesn't say enough, that's a different thing 18:19:24 MK: I wonder if the same person, if they read radiogroup and toolbar, if they'd have the same question 18:19:40 MK: that's always my first instinct with issues like this, is to compare with other places we might have the same problem 18:19:50 MK: sometimes that leads down a rabbit hole 18:20:08 JN: just from looking, it is different. In menubar it's at the end of the pattern, and in toolbar it's up front and the first thing in the pattern 18:20:10 https://github.com/w3c/aria-practices/issues/2044 18:20:20 JK: would you mind adding that comment to the issue? 18:21:13 JG: it looks like it's a lot clearer in toolbar at least, tab and shift-tab are a lot clearer 18:21:21 JG: so I'll recommend using what's in toolbar in menubar 18:21:31 JN: potentially all composites should be the same as this or similar 18:21:54 https://github.com/w3c/aria-practices/issues/2043 18:22:55 MK: I actually don't think this is a disclosure pattern 18:23:24 MK: we're dealing with a11y problems caused by read more/see more 18:23:43 rrsagent, make minutes 18:23:43 I have made the request to generate https://www.w3.org/2022/03/29-aria-apg-minutes.html Jem 18:23:48 MK: looking at what other sites do, it does look super problematic, almost no one handles focus well in these. But I don't think this is related to the disclosure pattern 18:23:59 https://github.com/w3c/aria-practices/issues/2043 18:24:12 SH: I'm in favor of us not making an example of this pattern 18:24:43 MK: this is a really common pattern 18:25:06 MK: why do you think that? 18:25:29 SH: it's not an ARIA pattern, I agree it's not a disclosure -- you just make a button, and then figure out how to handle focus 18:25:53 JK: how do we label this? 18:26:08 MK: not for practices would be a good label, but I'm sort of unwilling to close the issue without an explanation 18:26:30 JK: I think Sina explained well why it's an antipattern, I think that's good for now 18:26:43 JK: I put the not for practices label for now 18:26:46 MK: could you assign it to me? 18:27:05 https://github.com/w3c/aria-practices/issues/2041 18:27:52 MK: it doesn't say non-interactive 18:28:23 MK: I think our grids that have a combination of interactive and non-interactive content 18:29:13 MK: oh I see, it's just that sentence that doesn't have the word interactive. Maybe we should say something about interactive in that sentence 18:30:02 SH: we have good info in the preceding section, maybe we can literally just insert the word "interactive" 18:30:30 SH: it's the first sentence after this heading: https://w3c.github.io/aria-practices/#dataGrid 18:30:45 zakim, next item 18:30:45 I see nothing on the agenda 18:30:55 JK: Next topic: APG redesign topic 18:31:15 s/Next topic/Topic/ 18:31:28 MK: we met with the chairs of the education and outreach WG, including Sean Henry 18:31:29 MK: 18:32:04 MK: and our goal there was to discuss the launch plan for the WAI APG website and work through decision practices, roles and responsibilities, and schedule. 18:32:43 regrets+ Mark 18:32:49 regrets+ Curt 18:32:50 MK: when it comes to our publication process and decisions, Sean Henry is the primary gatekeeper for publication to the WAI website. The APG will become a standalone resource on the WAI website, and so we have alignment on that, and on which design template we want to use 18:33:14 MK: and on the basic mechanics of what a publication process will look like. So when we merge to our main branch, a chain of things will happen 18:33:29 MK: we also have alignment on shooting for GAAD as a launch 18:33:53 MK: and coordinating with education/outreach WG with the w3c stuff, turning that into some sort of notable launch event 18:34:03 MK: essentially some sort of media presence 18:34:39 MK: our next step is to dig into the template design, that'll get into nitty-gritty detail about the differences we have now between prototype design on the preview website and what w3c is currently using for standalone resources 18:35:03 MK: so they're actually in a redesign process for that template, so we'll be meeting this wednesday to work out some of those details, and come up with a todo list before we can publish 18:35:24 MK: I'm happy with the outcome of the meeting and where we landed, it feels like things are on track 18:35:43 MK: once we're on the WAI website, we'll no longer be a big long note doc, and no longer versioned 18:36:04 JK: we're going to meet tomorrow morning to go through issues 18:36:17 JK: Sean has a question about the skip-to, and Jon wanted to talk about skip-to this meeting 18:36:20 https://github.com/w3c/apg-redesign/issues/7 18:36:52 JK: WAI comes with a skip to content button, so it's asking about our skip to content component 18:37:18 JG: from what I saw in the issue, it looks like the skip-to is a popup, and I guess I feel that really negates the value of the skip-to. I put some info in the issue 18:37:23 https://github.com/w3c/apg-redesign/issues/7#issuecomment-1078440417 18:37:54 jongunderson has joined #aria-apg 18:38:04 JG: I think there are 3 things it helps promote: 1) if it's statically on the website, anyone can access it. So these landmarks and headings are available to everyone. You could choose not to click on it, but if you do, these concepts of landmarks and headings are actually useful to you by providing a high-level outline to the page 18:38:17 JG: so this is a step in awareness for people to start learning about these concepts 18:38:40 JG: 2) if it's visible all the time, authors will be more careful about how they use landmarks and headings, and hopefully learn how to use them in more functional ways 18:38:53 JG: it doesn't show every landmark and heading, but it does show a quick check if the page still makes sense 18:39:23 JG: and obviously the WCAG req to bypass blocks of content, and this provides a way for keyboard users to not only go to the main content, but also other sections of content. Even screen reader users might find use in it, since it's a filtered list 18:39:51 JG: I think the reason it should be visible is it will help raise awareness. I know in my work headings are often abused for style rather than structure 18:39:55 JG: those are my main arguments 18:40:04 JG: if there needs to be any changes to the code, I'm happy to work with them 18:40:27 JG: I do feel it should look like a natural part of the website, and not gaudy 18:40:41 MK: what makes theirs appear, is it just tab? 18:41:02 JG: I don't know, they said if you hit tab, the skip to pops up, and it's a big gaudy yellow button 18:41:12 JG: and it just seemed the antithesis of the whole skip to content 18:41:24 jon's info is https://github.com/w3c/apg-redesign/issues/7#issuecomment-1080890243 18:41:26 MK: and is the way we have it in our netlify preview right now? 18:42:19 https://main--wai-aria-practices2.netlify.app/ 18:43:15 MK: is the way we have it on the netlify link, is the jump-to presented the way you would expect? 18:43:21 JG: no, because it's only visible when you tab to it 18:43:24 MK: oh, really? 18:43:32 JG: really! That's the way the rest of the world does it 18:43:40 MK: in the current APG, the one that's published 18:43:47 JG: that one is visible all the time, the way we want it 18:43:58 MK: lets go to one of the preview examples, I want to make sure I know... 18:44:02 MK: I'll go to accordion 18:44:07 JG: they're all hidden now 18:44:15 MK: so it's not correctly done in our preview 18:44:19 MK: OK, that sucks 18:44:55 JN: I don't think we should have it visible all the time, because I don't think that's the way the web works, and people will reject it if it's visible all the time 18:45:05 MK: so how do we have it integrated visually in our current example pages now? 18:45:44 JG: they're visible, just at the top of the page 18:45:45 https://www.w3.org/TR/wai-aria-practices-1.2/examples/menu-button/menu-button-links.html 18:46:02 SH: it's like an upside down tab at the top 18:46:16 MK: I'm most keep to hear your objection, James, to the way it's currently presented on our example pages 18:46:51 JN: I just feel like it's very heavy, especially if you're looking at mouse and touch users, who, lets be honest, don't care about this at all. So why clutter the display with something they don't care about? 18:47:10 JG: I guess I have a different view, I think they just haven't had it. I think a touch user would like it 18:47:48 JK: if I summarize, if we put this as part of a template, maybe some users will complain about it 18:48:08 JK: what Jon mentioned is like a table of contents, that has a utiltiy people don't see yet 18:48:23 JK: I can see both sides 18:49:02 JN: so if we are going to display it to everybody, it needs to have a different name. Skip to content isn't good, if that's not intended as a keyboard thing 18:49:10 SH: I was also going to suggest that it should be called something else 18:49:23 JK: I think every site has the skip to content for now 18:49:35 MK: what do you mean every site? Every w3c site? 18:49:38 JK: yes 18:49:50 JG: I don't think so, the main w3c site doesn't have a skip link or landmarks 18:49:55 JN: I think the WAI sites do 18:50:22 MK: the WAI sites are super inconsistent, and some have weird skip link in the middle of the page that are crap 18:51:12 Shawn's comment, "I’m missing how having an always visible "Skip To Content" would help that? And, I actually worry it might “backfire” with authors who feel that it always visible is inelegant and cluttering?" 18:51:24 MK: I'm just going to throw a harebrained idea out. Is there any merit to potentially integrating the ToC/skip-to into the logo itself? Like the W3C logo so there's a way that maybe clicking on the logo would give you a link to the homepage but also show the skip to functions? 18:51:38 JG: I think the button needs to tell people what it does. To me, skip to content, is what it does 18:51:56 JG: whether you're a keyboard user, or a touch user, it'll take you to that piece of content. I'm not sure skip to content is the worst thing 18:52:31 JN: so if I, as a touch user, I would never think to tap it to see what's underneath it. I'm not used to the term, i wouldn't think I need it. If it's showing a ToC or site structure, we should make it clear that's what it's doing 18:52:41 MK: is there an icon for this? I'd love to have a designer on it 18:52:59 JG: the words can be customized, if we have an icon, that'd be great too 18:53:18 MK: I wonder for space, if the visible label was just ToC, something small, and also an icon, if that would make it visibly more compact 18:53:31 MK: still big enough, easy to hit, but is this a design issue primarily? 18:53:47 MK: in order to overcome objections, do you think it could be addressed through a more universally attractive presentation? 18:54:05 JN: yes. If we have something universally visible, it needs to look elegant and not bolted on top. It needs to be integrated into the design 18:54:17 JG: I agree 100%, I should look like it's designed into the page 18:54:30 JK: the concern was that it looks inelegant and cluttering 18:54:53 MK: both Sean and Isaac have a design background. If we put them on this, to come up with some options for the group to consider. It feels like a worthy project to me 18:55:32 MK: does anybody disagree with the idea of putting some more effort and energy into this? 18:55:51 MK: somehow it does feel to me like we're trying to move a11y more to the forefront in a meaningful way, and make it more universally appealing 18:56:04 JK: yeah, and it seems doable 18:56:27 MK: Jon, thank you for pushing the issue 18:56:46 JG: I agree, this is one area where we can make hidden a11y info more visible to people 18:57:19 JG: not enough people understand this stuff, so anything we can do to make this more salient and functional, use of landmarks and headings will be incrementally improved on teh web 18:57:23 s/teh/the 18:57:36 MK: we'll put a little resource behind it 18:57:44 rrsagent, make minutes 18:57:44 I have made the request to generate https://www.w3.org/2022/03/29-aria-apg-minutes.html Jem 18:59:07 rrsagent, make minutes 18:59:07 I have made the request to generate https://www.w3.org/2022/03/29-aria-apg-minutes.html Matt_King 18:59:40 zakim, make log public 18:59:40 I don't understand 'make log public', Jem 19:14:11 MichaelC_ has joined #aria-apg 21:09:14 Zakim has left #aria-apg 21:44:38 MichaelC has joined #aria-apg 22:04:49 Jem has joined #aria-apg