– DRAFT –
ARIA Authoring Practice Guide

<Jemma> Meeting agenda: https://github.com/w3c/aria-practices/wiki/Januray-11%2C-2022-Agenda

Setup and review agenda

Jemma: going through the agenda

<Jemma> ack

<Zakim> Jemma, you wanted to move onto the discussion "sharable/reusable" topic

ARIA and APG

Jemma: is there anything that needs attention to for ARIA?

<Jemma> https://github.com/w3c/aria-practices/wiki/Januray-11%2C-2022-Agenda

Matt: we covered APG changes in 1.2. James has a dependency tracker.

ARIA APG and Beyond

Jemma: let's talk about our goals, dreams, wishes for this year

Matt: most ambition had in mind was APG relaunched with the new design. get the new platform in place with the new content by axe-con

Matt: ARIA 1.3 content should be a priority. Jon's work next

Jemma asked about project timeline. Rich: will have an update on the timeline in early February

James: new features in ARIA 1.3. There is a wiki for ARIA 1.3, but it might not be used in the same way as the 1.2 wiki

<jamesn> https://github.com/w3c/aria/wiki/non-parity-1.3-features

<Jemma> https://github.com/w3c/aria/wiki/1.3-Planning

Matt and James talking about issue tracking in ARIA

<jongunderson> https://raw.githack.com/w3c/aria-practices/coverage/coverage/index.html

Matt: what is a logical approach to breaking out the work in coverage? Jon: would rather go by example

Boaz: one strategy could be to touch one example and fix all the problems for that example

Jon: concerned about touch events on mobile, less about key codes

Boaz: did we have mobile support? Matt: we do not have mobile support, but tried slider and spinner. not all content looked good on mobile, but examples are the beginning to making it better

<Jemma> "last revised" labeling for new apg site will be very helpful.

<Jemma> in terms of showing quality control

<Jemma> so users of apg would know which one is the most updated and following best coding practices

Boaz: feature request is to add dates on examples

Jemma: how is the task force going to be involved? If on a project level, it can be with scope. It can also be on an issue level basis

Sarah: What is the timeline?

Jemma: we can talk timeline later. where can we get coverage? can we have subnavigation for the document?

Github issues

<jongunderson> https://github.com/w3c/aria-practices/pull/2194

<Jemma> "Tab example updates include:

<Jemma> Updating js code to use latest coding standards

<Jemma> Updated keyboard focus styling for high contrast modes

<Jemma> Updated visual affordance for selected tab in high contrast modes

<Jemma> Removed tabindex=0 from elements with role=tabpanel

<Jemma> Removed delete tab feature

<Jemma> Added additional tabs to increase the utility of Home and End key behavior"

<Jemma> matt and bryan are talking about "Removed tabindex=0 from elements with role=tabpanel'

<Jemma> example link is https://raw.githack.com/w3c/aria-practices/tablist-update/examples/tabs/tabs-automatic.html

<Jemma> https://www.w3.org/WAI/WCAG22/Understanding/focus-appearance-minimum.html

<jongunderson> https://raw.githack.com/w3c/aria-practices/tablist-update/examples/tabs/tabs-automatic.html

Matt, Jon, and Jemma: talking about distinguishing the tab that's selected from the other tabs, in a visual way

Sarah: don't run into this because of the styling of used

<jamesn> https://user-images.githubusercontent.com/1724479/116632565-507cf400-a90c-11eb-8a19-0c67fc8ca950.png