W3C

– DRAFT –
ARIA Authoring Practices Task Force

02 November 2021

Attendees

Present
bryan, Jamesn, Jemma, jesdaigle, jongund, Markmccarthy, Matt_King, Rich_Noah, sarah, sarah_higley, simon, zcorpan
Regrets
-
Chair
Jemma
Scribe
Rich, Rich_Noah

Meeting minutes

<Matt_King> HAIR: Jemma

<Jemma> https://github.com/w3c/aria-practices/wiki/November-2%2C-2021-Agenda

https://github.com/w3c/aria-practices/pull/1814#issuecomment-954708336

Matt_King: we will start going down the issue list.

Matt_King: I believe PR #1814 is done.

Jemma: I checked Hi Contrast on PC & Mac. It looks fine.

Matt_King: we should raise an issue for the visual design

Jemma: can anyone give a comment on my visual review.

<Jemma> https://github.com/w3c/aria-practices/pull/1814#issuecomment-957008214

Pull Request #1869: Set aria selected to active tree view item by kdoberst · w3c/aria-practices

Matt_King: I am confused about this PR and why are we doing this? Do we want to make this change?

zcorpan: we shouldn't make the change if it is not required.

<Jemma> original issue https://github.com/w3c/aria-practices/issues/1680

sarah_higley: we could change wording or call it a selection thing but only if we add visual style.

sarah_higley: the current wording implies selection

<Jemma> https://github.com/w3c/aria-practices/pull/1869

Matt_King: this is a pretty old issue but I believe we could write a response in that issue.

Matt_King: i will revisit this myself and comment to propose the future direction.

Jemma: thank you Simon for your work

Matt_King: This is now more editorial than anything else

zcorpan: I can look at the regression tests tomorrow

Issue #1267: Combobox Examples: Make compatible with touch-based screen readers · w3c/aria-practices

Issue #756: Alert Dialog Example: Is disappearing toaster alert WCAG compliant? · w3c/aria-practices

Matt_King: so issue 1267 only needs a code review

zcorpan: the PR is already reviewed and merged.

<zcorpan> https://github.com/w3c/aria-practices/pull/2086

<zcorpan> https://github.com/w3c/aria-practices/issues/756

<Jemma> https://github.com/w3c/aria-practices/issues/756#issuecomment-957037176

sarah_higley: have the message be close to the action. have the check mark persist until you change it.

sarah_higley: a separate message so no timing issues

Jemma: possible note a message above the button

sarah_higley: it would be on the button itself

Matt_King: I am thinking about what the accessible name would sound like. I am thinking a check mark on a button would be hard to announce.

<Jemma> <div role="alert" id="alert_toast" class="toast hidden">Saved</div>

Matt_King: it feels more understandable if we separate the button from the status.

zcorpan: should this be a live region?

Matt_King: we would probably use role alert on the hidden message. It might create double speaking on some screen readers.

Jemma: do you want to work on this for the milestone?

Matt_King: if Howard or Simon have time to work in this it would be great.

Matt_King: the off screen element in the dom order prior to the save button

zcorpan: why do we want it to use aria-describedby

Matt_King: we don't have a screen reader equivalent to the icon

zcorpan: yes, this seems like a good change

Jemma: I left some notes on the issue and assigned it to you Simon.

Issue #894: Bug in example menu-button/menu-button-actions-active-descendant.html: tabindex · w3c/aria-practices

Matt_King: I am going to close that right now, it is done.

https://github.com/w3c/aria-practices/pull/2071

<Jemma> https://github.com/w3c/aria-practices/pull/2071#issuecomment-955813347

zcorpan: I looked at the PR and the comments and it seemed like a lot to dive into. Does someone have any suggestions?

Matt_King: I feel like this is going to be a lot of brain work to do in the coming weeks. I want to focus on closing bugs.

Matt_King: I do think we could get this into the editor's draft prior to the end of the year.

zcorpan: should we merge 2071 as is and treat the change as a follow up?

Matt_King: I will consider that option. I want to be careful we don't give guidance to cause people to do things they shouldn't do or not be in line with current practice. I will re-read it with the idea of what can be done minimally.

Matt_King: James and Sarah this might be a good one for you to read.

Jemma: can you share the guidance Matt?

Matt_King: the difference between focus and selection is the biggest misunderstanding. I am thinking about adding the section and selection.

Matt_King: we haven't really explained clearly the difference between focus and selection.

https://github.com/w3c/aria-practices/milestone/2

<zcorpan> https://github.com/w3c/aria-practices/pull/1895

Matt_King https://github.com/w3c/aria-practices/pull/1895 Jon are you able to take care of this?

jongund: is this a formatting issue primarily?

<Jemma> https://github.com/w3c/aria-practices/pull/1895

<Jemma> This doesn't follow https://github.com/w3c/aria-practices/wiki/Code-Guide#prefixed-properties

<Jemma> just simple linting issue

Jemma: do we agree on removing the prefix property for now?

Matt_King: if we can say don't use the vendor prefix unless there is a reason.

Matt_King: Jon can you check to see if it is needed for some reason.

<zcorpan> https://caniuse.com/?search=user-select

<Jemma> https://github.com/w3c/aria-practices/pull/1876

Matt_King: Jon if you could you provide a review on howard's work.

<Jemma> https://github.com/w3c/aria-practices/pull/1834

Matt_King: Jemma can you help on https://github.com/w3c/aria-practices/pull/1870?

Minutes manually created (not a transcript), formatted by scribe.perl version 136 (Thu May 27 13:50:24 2021 UTC).