W3C

– DRAFT –
ARIA WG

08 December 2022

Attendees

Present
Adam_Page, CurtBellew, jcraig, scotto, spectranaut_, StefanS
Regrets
-
Chair
spectranaut_
Scribe
Adam_Page

Meeting minutes

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

spectranaut_: #447
… editorial issue

scotto: this is on my to-do
… html-aam is riddled with old methods of linking, slowly fixing

spectranaut_: #155
… I’ll look at this

jamesn: could you craft a reply to this, jcraig?
… we could mostly use standard HTML to solve this problem

jcraig: yes, I will

spectranaut_: #154
… security considerations — is this the same issue?

jamesn: no, not the same
… too general to be actionable for us
… we need more detail

jcraig: we could point them to the tag issue
… security in this case could mean fingerprinting? or attack vectors? phishing attacks?

jamesn: it’s not specific enough, so we don’t know for certain

scotto: should there even be something in core-aam for this?

jcraig: if there’s some security threat with ARIA itself, it should have been caught by W3C Security cross-review process. If there is an implementation issue here, it should be platform-specific

spectranaut_: we can wait on this issue

spectranaut_: #1851

jamesn: I almost closed this as inapplicable to ARIA

jamesn: re: implicit roles, we do have a slight crossover in that html-aam now says “use ARIA mappings”

jcraig: this seems like a misrepresentation of our intention with accessibility tree inclusion
… maybe we could clarify, but this is an implementation issue

spectranaut_: any disagreements?

jcraig: I’ll comment and close

jamesn: agreed, we could clarify, but nothing needs rewriting. A comment could be sufficient

[New PR Triage](https://bit.ly/3BaCclq)

spectranaut_: #178

spectranaut_: who wants to review?

spectranaut_: melanie

spectranaut_: #448

scotto: this is mine. Was looking through #402 PR and noticed discrepancies
… please review #402, everyone

spectranaut_ I’ll look at #402

jamesn: I’ll review

scotto: UIA was saying labelledby prop pertained only to input, but there’s actually more
… we’re not being specific enough

spectranaut_: #1852

jamesn: I’ll fix

spectranaut_: I’ll look at it too

spectranaut_: melanie will review too

spectranaut_: #177

spectranaut_: reviewers added

spectranaut_: #153
… this is a draft
… we’re discussing this later in the meeting

[Holiday Schedule](https://www.w3.org/groups/wg/aria/calendar)

spectranaut_: we have one more meeting in Dec
… canceled the 22nd and 29th

\[2023 ARIA F2F\](Results of survey, date conflicts)

jamesn: we have 14 responses for face-to-face survey
… please vote if you haven’t, but it might not take it
… majority _wants_ a face-to-face in the first half of the year
… 60% wants California bay area
… bay area is probably the most likely, but somewhere in the central US could be possible with good access and a host
… does anyone disagree with bay area?

jcraig: would like to hear from folks outside the U.S.

jamesn: would like to avoid Europe because TPAC will be there in the fall

rashmi: how about Seattle?

cyns: I could host in Seattle

spectranaut_: anyone who could go to the bay but _not_ Seattle?

spectranaut_: also need to decide date
… any conference conflicts?

jcraig: avoid CSUN, SXSW

cyns: Adobe Mix?

jamesn: Summit is in spring

jamesn: recommend avoiding most of April

jcraig: also need to avoid Global A11y Awareness Day

cyns: end of May, I think?

cyns: May is nice in Seattle, no smoke ;-)

[ARIA ACT Rules review](https://github.com/w3c/aria/discussions/1850)

spectranaut_: jamesn created a discussion in GitHub. Please review the rules there

scotto: we need more than just JAWS-Test and me

jcraig: I may volunteer co-worker who works on ACT

jamesn: don’t need to be a WG member

Flowto https://github.com/w3c/aria/issues/630 (close to resolution to NOT deprecate flowto until better replacement exists)

jcraig: in our deep dive earlier this morning, we came to an agreement that we need some replacement. Brennan and Volker made compelling requests that we do not deprecate
… they currently rely on it
… I plan to close as “not to be deprecated”
… Brennan will file a new issue: “what do we do about accessible diagramming?”

jamesn: would love a community group but need buy-in from browsers
… need to get the right implementation people involved

jcraig: that’s why I’ve proposed a WICG

cyns: +1 to getting the right people there, and also documenting use cases

[aria-haspopup at button should not change role](https://github.com/w3c/core-aam/issues/51)

spectranaut_: jamesn made draft PR for this

jamesn: this has been a long discussion
… Aaron has proposed a Chrome change

spectranaut_: that change landed

cyns: there was a lot of input involved with that; not just Aaron

jamesn: fully support
… would like to go further and do the same for some of the other values, for consistency
… acknowledge that they’re not _as_ important
… but for consistency, we should extend

cyns: they were trying to be incremental

scotto: yes, incremental, but this particular case was super necessary

jamesn: I’m open to making my draft PR focus only on dialog

jamesn: I did some searches on various web source code repos looking for examples of aria-haspopup using other values

cyns: the draft PR is reasonable, but the implementation implications might be fragile

cyns: Aaron will be back on Monday, can we push to next week’s meeting?

spectranaut_: yes

[\[normative\]\[author\] clarify widget in trees can only be group and treeitem](https://github.com/w3c/aria/pull/1793)

spectranaut_: any update?

jamesn: waiting for pkra
… has unresolved questions
… may need to look through old minutes

sarah_higley: is there anything in here that wouldn’t be covered by change to aria-owns?

jamesn: good point, we need to look at that
… that one was blocked y a wording issue

jcraig: “Accessibility child” and “Accessibility parent”
… it disambiguates

sarah_higley: no strong opinion, I’m planning to go through and change to that

[1.3 blocking issues](https://github.com/w3c/aria/issues?q=is%3Aopen+is%3Aissue+milestone%3A%22ARIA+1.3%22+sort%3Acreated-asc+label%3A1.3-Blocking+) agendabot]

jamesn: #1150
… will be resolved by sarah_higley’s work

#1159
… any update?

spectranaut_: no, but I’ll look in Jan

jamesn: #1161
… really does need us to go through everything
… #1177

no update
… #1487

have resolution just need to finish
… #1824
… I created a PR for this
… hopefully can be merged & closed
… needs a test, according to flag

spectranaut_: assign me and I’ll look at the test

jcraig: trying to flag anything that relates to computed name or computed role

spectranaut_: do WPT tests need to be created in WPT?

jcraig: yes, but can create & run them offline, then propose at WPT repo

cyns: how many people do we need to host for face-to-face?

jamesn: need larger than a 10-person conference room

cyns: I’ll look for 15- or 20-person room

jamesn: Adobe is also an option in Seattle

Minutes manually created (not a transcript), formatted by scribe.perl version 196 (Thu Oct 27 17:06:44 2022 UTC).

Diagnostics

Succeeded: s/if there’s some security threat with ARIA, it should have been caught by W3C process. If there is a conversation thread here, it should be platform-specific/if there’s some security threat with ARIA itself, it should have been caught by W3C Security cross-review process. If there is an implementation issue here, it should be platform-specific/

Succeeded: s/sprin/spring/

Succeeded: s/shigley/sarah_higley/

Maybe present: cyns, jamesn, rashmi, sarah_higley

All speakers: cyns, jamesn, jcraig, rashmi, sarah_higley, scotto, spectranaut_

Active on IRC: Adam_Page, CurtBellew, jamesn, jcraig, scotto, spectranaut_, StefanS