– DRAFT –
ARIA WG

<jamesn> - Please register https://www.w3.org/2021/10/TPAC/#participation

<jamesn> - ARIA sessions Scheduled Thursday Oct 28 - (1 hour) 7am Pacific / 10am Eastern & (2 hours) 9am Pacific / noon Eastern

<jamesn> - [Sessions with APA about future of a11y APIs](https://www.w3.org/WAI/APA/wiki/Meetings/TPAC_2021#APA_.26_ARIA:_The_Future_of_Accessibility_APIs)

<jamesn> - Graphics/ Canvas a11y?? (cyns?)

zakim next item

[New Issue Triage](https://bit.ly/3aWxQ3O)

[New PR Triage](https://bit.ly/30KsTcF)

james n will merge

james n will merge

[TPAC 2021](https://github.com/w3c/aria/issues/1482)

<jamesn> - Please register https://www.w3.org/2021/10/TPAC/#participation

<jamesn> 09:43

<jamesn> - ARIA sessions Scheduled Thursday Oct 28 - (1 hour) 7am Pacific / 10am Eastern & (2 hours) 9am Pacific / noon Eastern

<jamesn> 09:43

<jamesn> - [Sessions with APA about future of a11y APIs](https://www.w3.org/WAI/APA/wiki/Meetings/TPAC_2021#APA_.26_ARIA:_The_Future_of_Accessibility_APIs)

<jamesn> 09:43

<jamesn> - Graphics/ Canvas a11y?? (cyns?)

jamesn reminder, please register for TPAC!

jamesn we will be discussing resolving text to speech conflicts in Ruby

jamesn Tuesday next week there is a joint with APA around A11y APIs

<Jemma> APA & ARIA: The Future of Accessibility APIs (Session 1)

<Jemma> Tuesday, October 26, 11:00 AM-1:00 PM CDT

jamesn it sounds like the cyns conversation about Canvas a11y may be post-TPAC

jcraig attended the Focus Group: Toggles and Tabs, recommends checking out that session's artifacts

<jamesn> https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/Focusgroup/explainer.md

<jamesn> https://tabatkins.github.io/css-toggle/#introduction

<Jemma> https://web-eur.cvent.com/hub/events/2b77fe3d-2536-467d-b71b-969b2e6419b5/sessions/3dca6f35-69d1-47c4-8f7e-14a0b543f428?goBackHref=%2Fevents%2F2b77fe3d-2536-467d-b71b-969b2e6419b5%2Fsessions&goBackName=All+Sessions&goBackTab=21-9-2021

<Jemma> https://web.dev/fugu-status/

[Updating ARIA 1.2 due to IDL implementations (exit and re-enter CR?)](https://github.com/w3c/aria/issues/1598)

cyns is planning to write a draft of the element reflection spec this week

[Spec is unclear on aria-invalid="spelling" | "grammar" uses](https://github.com/w3c/aria/issues/989)

jamesn there was an interesting TPAC session around a way of marking spelling /grammar errors across component boundaries

jamesn eventually we may replace aria-invalid on elements with that

<jcraig> ## Highlight API Accessibility

<jcraig> https://github.com/w3c/csswg-drafts/issues/6498

<jcraig> Dan Clark, proposed type field to the API.

<jcraig> Implementation seems reasonable.

<jcraig> Minutes: https://www.w3.org/2021/10/20-cssa11y-minutes.html#t02

<cyns> Project Fugu: https://web.dev/fugu-status/

jamesn suggests we don't create a new "spelling" value for aria-invalid only to deprecate it in favor of this new cross-element method

jamesn is for "option1" of the proposal (aria-invalid back to global)

Aaron L. what might the consequences of deprecation be? We need it currently

Scott O. Should we add a not about this? Indicating aria-invalid is valid based on a match between value and role

Aaron L. I'm good with whatever will make sure we have support until we have a better replacement

Scott O. will file an issue with ARIA in HTML to make sure we have a note of explanation to avoid confusion

aaron L we may still need a version of this that is an attribute for the sake of things like virtual nodes

[Add figcaption to computation?](https://github.com/w3c/html-aam/issues/325)

Scott o. This is about figuring out to which element figcaption provides ACCName

Scott o. proposes that a figcaption should provide description so that something else can provide the name

Scott O. IS there anyone who opposes this or do we thing there will be User Agent pushback?

cyns and Aaron: this seems reasonable

jamesn that we can put structured content in figcaption suggests it should not be a decription

<jamesn> https://w3c.github.io/aria-practices/examples/disclosure/disclosure-img-long-description.html

Scott O will add notes to the issue from this conversation

jamesn we have an example of a complex figcaption here: https://w3c.github.io/aria-practices/examples/disclosure/disclosure-img-long-description.html

[clarify img naming steps](https://github.com/w3c/html-aam/pull/322)

jamesn waiting on this pending more comments from Matt

cyns what is most important is consistant approach, either approach is ok

cyns we could tie this to the verbosity setting?

jamesnare we saying that title is like an ARIA global? It makes role="presentation" not applicable?

<jcraig> I hadn't seen the "wall of text" Scott mentioned but it's here: https://github.com/w3c/html-aam/pull/322#issuecomment-947857392