– DRAFT –
ARIA Authoring Practices Task Force

<Jem> present

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

APG Issue Triage

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

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

mk: would be editorial fix

mk: assigned to Jemma

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

https://github.com/w3c/aria-practices/issues/2204

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

mk: assigned to jon, marked editorial

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

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

https://github.com/w3c/aria-practices/issues/2178

Shortcut keys needed for calendar widget?

<Jem> This is interesting question. this raises the bigger issue

<Jem> we actually don't state this is required or option for each example.

mk: requires discussion how to respond.

adding agenda label.

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

<Jem> mck: with my chair hat off, I would prefer take disabled one from tab order.

<Jem> jon: dicoverability and keyboard usabilty issues

<Jem> mck: it is also scrolling issue.

<Jem> the problem is written in too specific way.

<Jem> curt: disabled vs read only

<Jem> bryan: disabled - you can not copy the info.

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

https://github.com/w3c/aria-practices/issues/2175

<Jem> https://developer.apple.com/design/human-interface-guidelines/macos/fields-and-labels/token-fields/

added agenda label; needs further discussion.

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

Assigning to Jemma to fix typo

Tabs Example

Tabs example

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

jon: Based on feedback, made use tabindex 0 on the auto activation example

On the manual example one, no tabindex on the tabpanel

Added note to tabs pattern for focusability of tabpanel

<Jem> changes are "<li>Since the first element in each <code>tabpanel</code> is a focusable element (e.g. link), the tabpanel does <strong>not</strong> need to set a <code>tabindex</code> value to include it in the tab sequence of the page.</li>"

Added that info about tabindex on tabpanel to accessibility features section of example page.

Also removes delete function b/c was not accessible.

mk: ready for full review process?

Jemma: are we done with visual design review?

mk: We did that a s a group

jon: Caolyn made one visual design fix related to alignment

Discussed Carolyn's feedback about touch

Accessibility review is done.

Review process nearly complete; outstanding is code/test and editorial.