– DRAFT –
ARIA Authoring Practices Task Force

<Matt_King> resent+

<Jem> jon: tab example - adding insert

<siri_> joining now:)

<Jem> mck: it is like what google chrome tab works ...adding action 1 and action 2.

<Jem> we don

<Jem> jon: how about adding delete tab and adding insert tab at the end.

<Jem> mck: the problem for that design is that you can add only insert the tab at the end.

<Jem> mck:only thing I have in the wild is close button on the browser tab. it is sort of like delete.

<Jem> jon: I was thinking about adding more composers to the list..

<Jem> mck: it would be great if the design can be simpler.

<Jem> jon: you can add the note as the tab.

<Jem> jon: my initial design idea is adding one more tab and delete tab.

<Jem> mck: I like the design idea you described.

<Jem> mck: adding action button such as "close" rather than "delete" will be more preferrable?

<Jem> ... my question is whether "add tab" action will be right after the tab and what would be the tab order.

<Jem> jon: I will work on the "action" added tab example.

<Jem> mck: it can be the third example.

<Jem> jon: I would like to explore tab orders with this example.

<Jem> siri: this will be the great example because marketing people will like it.

<Jem> mck: button inside of tab list is sort of working but the spec is ambiguous about whether it is allowed or not.

<Jem> we want to allow that.

triage

<Jem> https://github.com/w3c/aria-practices/issues?q=is%3Aissue+is%3Aopen+created%3A%3E2021-10-01+no%3Alabel+

<Jem> https://github.com/w3c/aria-practices/issues/2261

<Jem> wcag: Dismissible

<Jem> A mechanism is available to dismiss the additional content without moving pointer hover or keyboard focus, unless the additional content communicates an input error or does not obscure or replace other content;

<Jem> https://www.w3.org/WAI/WCAG21/Understanding/content-on-hover-or-focus.html

<Jem> closing issue 1571 because esc key is supported.

<Jem> matt: I will add comments to issue 2261

<Jem> "Discussed in March 22, 2022 meeting. The task force agrees that the escape key behavior is not required by WCAG. We will modify the text accordingly."

<Jem> mck: modification is like "escape is considered because it is beneficial to show the hidden content..."

<Jem> https://github.com/w3c/aria-practices/issues/2257

<Jem> mck: is it something that APG fix or browser should fix?

<Jem> jon will add the comment on potential root cause and raise the bug to appropriate party.

<Jem> mck: adding browser dependancy and bug label as the part of triage.

<Jem> rragent, make minutes