W3C

– DRAFT –
ARIA Authoring Practices Task Force

18 April 2023

Attendees

Present
Andrea, arigilmore, CurtBellew, jongund, jugglinmike, MarkMcCarthy, Matt_King
Regrets
-
Chair
Jemma
Scribe
jugglinmike

Meeting minutes

Review Agenda and Next Meeting Date

<Matt_King> View agenda at https://github.com/w3c/aria-practices/wiki/April-18%2C-2023-Agenda

<Matt_King> Next meeting: April 25

Matt_King: May 2nd will be a travel day for many folks involved with ARIA because it precedes a face-to-face meeting

Matt_King: We'll probably cancel the meeting for May 2.

Matt_King: But that's two weeks from today, so we'll confirm during next week's meeting

Status of Site Updates

Matt_King: We had an amazing cross-team effort involving a lot of people to release support tables--five of them on four different pages on APG!

Matt_King: And a blog post titled "ANSWERING 'WHAT ARIA CAN I USE?'" available here: https://www.w3.org/blog/2023/04/answering-what-aria-can-i-use/

Matt_King: This is a really big milestone in my mind. The post explains why

jongund: It looks like the "skip to" content is being rendered twice on the new page

Matt_King: I noticed that, too. I wasn't sure if it was just me

jongund: I'll try to look into it further

Pull request reviews

PR 2643 - Datepicker Modal Dialog: Updated code and fixed next/prev month bug by jongund

github: w3c/aria-practices#2643

Matt_King: I think this is really close

Matt_King: The only thing we're waiting on is a review of the regression tests by Alex_Flenniken

jugglinmike: That will probably not happen this week due to Bocoup's week-long "all-hands" meeting taking place now

PR 2622 - Listbox Examples: Update scrolling of listbox item with focus into view when page is magnified by jongund

github: w3c/aria-practices#2622

jongund: I fixed the issue where when you were using keyboard commands, it wasn't following focus

Matt_King: Just if you're pressing the shortcut keys, or also when focus is on the "up" and "down" buttons

jongund: Just the shortcut keys. The expected behavior when focus is on the "up" and "down" buttons needs more discussion

Matt_King: Okay, I think we have a separate issue for that

Matt_King: We're also waiting on Alex_Flenniken here

Matt_King: I have a little to do as well

PR 2670: Add landmark pattern page by mcking65

github: w3c/aria-practices#2670

Matt_King: arigilmore has reviewed

Matt_King: We don't have a preview, though. arigilmore were you looking at the code diff?

Matt_King: Alex_Flenniken told us it failed to build

<arigilmore> w3c/aria-practices#2622 (comment)

Matt_King: There are other people listed for review, but since we don't have a preview, let's mark the pull request as a draft

Matt_King: Hopefully we'll be able to get that into a ready-to-review state, but we'll have to talk with Alex_Flenniken

New Issue Action Planning

Matt_King: I'm going to take some steps to make gh-2675 more actionable, so we'll skip that one for now

Select-Only Combobox Closes When Clicking on its Scrollbar

github: w3c/aria-practices#2674

<jongund> need to leave a little early today

jugglinmike: I can replicate this using Firefox and Ubuntu

Matt_King: Does this occur in other examples?

jugglinmike: it works as expected in "Editable Combobox With Both List and Inline Autocomplete Example"

Andrea: I can take a look

Matt_King: Thanks, I have assigned you

Switch Pattern: probably not exactly "interchangable" with checkboxes

github: https://github.com/w3c/aria-practices/issues?q=is%3Aissue+is%3Aopen+created%3A%3E2021-08-15+no%3Alabel++sort%3Aupdated-desc

github: w3c/aria-practices#2647

Matt_King: I don't want to muddy the waters in the first paragraph which describes how to choose a role. But maybe we could address this difference in how they may be conventionally applied in the second paragraph

jamesn: It seems like you should use switch only if activating it takes effect immediately

jugglinmike: So does that mean switches shouldn't be used in forms which aren't powered with JavaScript?

jamesn: I don't think they should be used in that case

Matt_King: We might have some other places where we use accessibility to say, "change your visual design because it doesn't reflect the accessibility semantics", but we've worked pretty hard to avoid doing that. I might be forgetting something, but it somehow feels like crossing a line.

Matt_King: I guess there are some places were we say, "for accessibility reasons, don't create massive radio button groups--use something like a typeahead, instead"

MarkMcCarthy: It only says "they are often functionally interchangeable". It doesn't say "always", but maybe we could say "sometimes"

MarkMcCarthy: I think this is a non-issue, though. I can see that they aren't exactly interchangeable, but APG isn't saying that they're exactly interchangeable.

End of Meeting

Minutes manually created (not a transcript), formatted by scribe.perl version 210 (Wed Jan 11 19:21:32 2023 UTC).

Diagnostics

Succeeded: s/jugglinmike/Matt_King/

Found 'Next meeting:' not followed by a URL: 'April 25'.

Maybe present: jamesn

All speakers: Andrea, jamesn, jongund, jugglinmike, MarkMcCarthy, Matt_King

Active on IRC: Andrea, arigilmore, CurtBellew, jongund, jugglinmike, MarkMcCarthy, Matt_King