Meeting minutes
<Jem> https://
Setup and Review Agenda
Jem: Next meeting will be April 30
Jem: Any requests for changes to the agenda?
Jem: Hearing none, we'll move on
Publication status
Matt_King: Shawn and I will be travelling for AccessU
Matt_King: So it will be hard to choose a specific time for that week
Matt_King: Maybe the best decision is to work on getting everything ready by May 7th, and then just check in with Shawn if that doesn't work out for some reason
Matt_King: I don't think we have to be very particular about the day of the week, so Shawn can fit it in some time during the week of the 14th
dmontalvo: I support that. It will help dramatically if we can have a publication ready for May 7th
Matt_King: The pull request that I really want to get landed is the one related to "Feed"
<Jem> https://
Matt_King: w3c/
Matt_King: I'd like to get that done within the next two weeks
Matt_King: Same goes for this pull request concerning skipTo w3c/
Matt_King: Only howard-e has looked at that, so we might want someone to do a visual design review--just to ensure that there are no regressions
Jem: I can do that review. I'll assign myself
Matt_King: Awesome
Matt_King: And thanks to howard-e for the code review
Matt_King: I think this is looking good for May 7th
Matt_King: I'm responsible for w3c/
Coverage and Quality Report: add information about use of forced-colors media query in examples
github: w3c/
Matt_King: We don't have any reviewers assigned here. Is this ready for review?
Matt_King: There are some conflicting files in this pull request because we changed how the report date is being generated (now, it's being generated during build instead of when the report is run)
Matt_King: Actually, it is only a conflict in the generated file... I wonder, is this a matter of jongund merging the "main" branch into his branch...?
Matt_King: I would like howard-e to look at this because he recently looked at the quality report stuff and I want to make sure it's all in-line with those other changes
Jem: I've assigned howard-e and added his name to the checklist in the pull request description
Feed example update
Matt_King: We'll skip this because Ariella isn't present today. I'll send an e-mail
Plans to Enhance High Contrast Support
<siri> can you please give to join zoom meeting?
Matt_King: The first step in this plan is the coverage report
<dmontalvo> presnt+ dmontalvo
<Jem> https://
Matt_King: I started a draft pull request to start experimenting with some ideas, w3c/
jongund: I can take over from where you left off
Matt_King: Thank you!
Matt_King: let's get pull request 2902 in shape and delivered, first, than then work on pull request 2991
Adding a Live regions practice page
github: w3c/
<Jem> w3c/
Matt_King: We had a pull request that was originally started by Simon
Matt_King: It never got finished for a number of reasons
Matt_King: And there has recently been more attention given to live regions in ARIA
Matt_King: So now seems like the right time to "wake up" this piece of work that has been dormant for five years (since 2019!)
Matt_King: I created this pull request. The preview doesn't work right now, there are broken links, etc.
Matt_King: I could continue work on it, but I thought it was a great pull request for someone who wants to get their hands dirty for the first time
Matt_King: The first step is to bring the text up to date in terms of linking to the correct places in the APG, fixing the other evident problems in the pull request, and then facilitating a discussion about what SHOULD be on this new page.
Jem: It would be helpful if this had more of a description
Matt_King: I'd be happy to mentor someone if someone wants to pick this up
Matt_King: It includes a link to issue 1027. I don't know if that has a functional preview, but you can at least see the functional content by opening the "files" tab of that pull request
dmontalvo: I can make an attempt. No promises about deadlines, though!
Matt_King: I thought about raising an issue in ARIA and maybe pulling in one of the people in ARIA
dmontalvo: that's a good idea. ARIA is a larger group, to be sure, so we may find someone there
<Jem> Now I see what Matt did. https://
Matt_King: I think I wanted to do something like that for ARIA Actions, too
Matt_King: But if, in the mean time, we could assign this to you, dmontalvo, just to get your initial impressions
dmontalvo: Sure
dmontalvo: This is only about live regions, correct? We're not considering ARIA Notify, yet, right?
Matt_King: That's right--not yet
Matt_King: For now, anything on ARIA Notify would have to be in the "experimental content" area. But this is not about that
Matt_King: We're not getting rid of declarative live regions--not at all. There's no movement in ARIA for anything like that
Matt_King: I think people will continue to use live regions when content is in the DOM and in a fixed location
Matt_King: There are other use cases where the Accessibility Notifications API will come into play
<Jem> content/practices/live-regions/live-regions-practice.html
Support for experimental content
Matt_King: I think we want to skip this topic, as well. I hoped to do more work on this before today's meeting started, but I did not
Other new issues
Default actions on modal dialogs via ENTER key
github: w3c/
Jem: This person is asking to use the "enter" key for escaping the modal dialog
Matt_King: They want to know if we can take the list of default actions in the modal dialog, should we say something about the enter key performing the default action
Jem: What is the default action?
jongund: Typically, it's the "submit"
Matt_King: I'm personally nervous about pressing "enter" in these situations because I'm not confident what it will do
Matt_King: ARIA doesn't have anything related to "default action"
Jem: "Enter key for submit action" is a clear scope. But it's not clear what the default action is
CoryJoseph: I never use the default action in a modal, either
Matt_King: I think this is why ARIA doesn't include a default action attribute that you can apply to dialogs
<Jem> s/Enter key for default action/Enter key for submit action/
Matt_King: because there's no way of communicating the default action in a web dialog to an end user
Matt_King: That's why I feel a little reluctant to say anything at all about default actions in the interactions section of the modal dialog
jongund: Well, it's a browser convention
jongund: You get default action, it looks for the submit button
jongund: If you're in a form, that is
jongund: What does ARIA say about default actions? That you should do it? That you shouldn't do it? That sometimes you should do it?
jongund: Maybe this is beyond the scope of ARIA. It might not be worth saying anything about it in APG
Matt_King: If we said something about it, that would suggest that there is a way to define a default action for a dialog
CoryJoseph: Escape closes the dialog
Matt_King: That's not a default behavior, though
CoryJoseph: No, it's just a user expectation
<Jem> Enter key for default action
Jem: I searched the ARIA spec, and there's nothing about default in 1.3. In 1.2, however, there's a comment about it in a note
[Jem reads the note]
Matt_King: That is the way that screen readers emulate a mouse click in "reading" mode. It's not related to the default action which we're considering here
CoryJoseph: If there's a form inside the modal, and you have a submit button, then there's a default action
CoryJoseph: Otherwise, there is no default action
Matt_King: Does a screen reader ever tell you about the default action in a form...?
CoryJoseph: I don't think so, not even with the most generous hints on
dmontalvo: I think you can get at the default on a Windows desktop app
Matt_King: Sure, in a dialog you can
dmontalvo: That may be out of scope for this discussion, though
Jem: I think we're saying "no", and the uncertainty here is the reason
Matt_King: Because ARIA does not provide a way of communicating what the default action will be, for us to say how to perform a default action is going beyond the spec.
<Jem> w3c/