16:48:14 RRSAgent has joined #aria 16:48:14 logging to https://www.w3.org/2022/04/14-aria-irc 16:48:17 RRSAgent, make logs Public 16:48:18 please title this meeting ("meeting: ..."), jamesn 16:48:21 meeting: ARIA WG 16:48:31 agendabot, find agenda 16:48:31 jamesn, OK. This may take a minute... 16:48:31 agenda: https://www.w3.org/events/meetings/2b92a902-1365-4ea0-8c68-9f8ae2106fe3/20220414T130000 16:48:31 clear agenda 16:48:31 agenda+ Working Group news! 16:48:31 agenda+ -> New Issue Triage https://bit.ly/3uybe49 16:48:34 agenda+ -> New PR Triage https://bit.ly/3JBcdVR 16:48:37 agenda+ -> Deep Dive planning https://bit.ly/aria-meaty-topic-candidates 16:48:39 agenda+ -> TPAC Announcement https://www.w3.org/blog/news/archives/9503 16:48:42 agenda+ -> Support aria-description https://github.com/w3c/accname/pull/69 16:48:45 agenda+ -> When is hidden content taken into calculation of name and description? https://github.com/w3c/accname/issues/57 16:48:48 agenda+ -> Initial aria-textseparation (depends on generic PR being merged) https://github.com/w3c/aria/pull/996 16:48:51 agenda+ -> Inconsistency between native and ARIA listboxes when implicit aria-selected is provided https://github.com/w3c/aria/issues/1661 16:48:54 agenda+ -> Secondary actions on items in composite widget roles https://github.com/w3c/aria/issues/1440 16:48:57 agenda+ -> Add combobox value support for aria#1225 https://github.com/w3c/core-aam/issues/76 16:49:00 agenda+ -> Do we need a notifications API in ARIA https://github.com/w3c/aria/issues/832 16:53:08 regrets+ PeterKrautzberger 16:53:50 regrets+ HarrisSchneiderman 17:00:10 myasonik has joined #aria 17:00:29 StefanS has joined #aria 17:03:10 scotto has joined #aria 17:03:11 scribe: chlane 17:03:16 present+ 17:03:38 present+ 17:04:21 present+ 17:05:20 CurtBellew has joined #aria 17:06:46 zakim, next agendum 17:06:46 agendum 1 -- Working Group news! -- taken up [from agendabot] 17:07:08 Siri has joined #aria 17:07:13 zakim, next agendum 17:07:13 agendum 1 was just opened, chlane 17:07:21 zakim, take up item 2 17:07:21 agendum 2 -- -> New Issue Triage https://bit.ly/3uybe49 -- taken up [from agendabot] 17:07:55 present+ 17:07:57 sarah_higley has joined #aria 17:08:00 present+ 17:08:30 154 Bryan hasn't had time to see scotto was looking at an old HTML AAM issue 17:08:59 there was a suggestion to cover case where label contains a form control and points to another one 17:09:25 scotto: suggests to call this out as maybe do it but invalid if you do it 17:09:43 jamesn: milestone this for accname 17:10:08 w3c/aria #1721 17:10:10 Consider a mechanism to associate controls without an explicit grouping 17:10:14 1721 17:10:31 scotto: goes back to radio button and related to open UI 17:10:39 specing radio and radiogroup 17:10:54 html allows for associations without radio group 17:11:06 allow for markup patterns that don't neatly fit 17:11:08 q+ 17:11:13 jamesn: arent these patterns broken 17:11:20 scotto: arguable 17:11:49 scotto: a lot of discussion allowing for association of other elements, checboxes, toolbar, x of y 17:11:53 ack StefanS 17:12:00 StefanS: embed in li 17:12:32 StefanS: when you arrow to toolbar items, described by is not elegant 17:12:37 StefanS: will work on this 17:12:59 scotto: will keep eye on it 17:13:00 w3c/aria #1720 17:13:01 Add explicit value calculations for textbox and searchbox role 17:13:15 nothing in it 17:13:24 q- 17:13:38 jamesn: combobox textbox 1.4 17:13:48 need to say something about getting value 17:14:03 scotto: behaves as expected, describing reality 17:14:13 jamesn: 1.3 17:14:23 Matt_King has joined #aria 17:14:29 zakim, close this item 17:14:29 agendum 2 closed 17:14:30 I see 11 items remaining on the agenda; the next one is 17:14:30 1. Working Group news! [from agendabot] 17:14:35 present+ 17:14:36 zakim, take up item 3 17:14:36 agendum 3 -- -> New PR Triage https://bit.ly/3JBcdVR -- taken up [from agendabot] 17:15:19 https://bit.ly/3JBcdVR 17:15:30 w3c/aria #1719 17:15:31 Update authoring requirement for aria-selected on options 17:15:40 matt sarah and chlane reviewers 17:16:16 zakim, close this item 17:16:16 agendum 3 closed 17:16:17 I see 10 items remaining on the agenda; the next one is 17:16:17 1. Working Group news! [from agendabot] 17:16:22 zakim, take up item 4 17:16:22 agendum 4 -- -> Deep Dive planning https://bit.ly/aria-meaty-topic-candidates -- taken up [from agendabot] 17:17:08 4/28 open UI deep dive scheduled 17:17:14 5/5 dialog deep dive 17:17:19 scheduled 17:17:30 open UI catchup is tentative 17:17:52 dialog deep dive is confirmed 5/5 17:18:13 some weeks we have in depth meeting an hour before this one 17:18:38 zakim, close this item 17:18:38 agendum 4 closed 17:18:39 I see 9 items remaining on the agenda; the next one is 17:18:39 1. Working Group news! [from agendabot] 17:18:49 zakim, take up item 5 17:18:49 agendum 5 -- -> TPAC Announcement https://www.w3.org/blog/news/archives/9503 -- taken up [from agendabot] 17:19:09 TPAC is going to be hybrid 17:19:20 reg will open early July 17:19:39 will be 9/12-9/16 17:19:46 in Vancouver 17:20:00 remote will be better that in the pasty 17:20:01 past 17:20:04 zakim, close this item 17:20:04 agendum 5 closed 17:20:05 I see 8 items remaining on the agenda; the next one is 17:20:05 1. Working Group news! [from agendabot] 17:20:10 zakim, take up item 6 17:20:10 agendum 6 -- -> Support aria-description https://github.com/w3c/accname/pull/69 -- taken up [from agendabot] 17:20:55 present+ 17:21:08 Support aria-description #69 17:21:19 jamesn: Bryan update? 17:21:43 Bryan, doesn't know the current status, James C and Aaron working on details 17:22:39 Bryan will go back and look 17:22:55 scotto: will review as well 17:22:57 zakim, close this item 17:22:57 agendum 6 closed 17:22:58 I see 7 items remaining on the agenda; the next one is 17:22:58 1. Working Group news! [from agendabot] 17:23:02 zakim, take up item 7 17:23:02 agendum 7 -- -> When is hidden content taken into calculation of name and description? https://github.com/w3c/accname/issues/57 -- taken up [from agendabot] 17:23:41 jamesn: waitng for reviews 17:23:51 from James C and Cynthia 17:23:53 zakim, close this item 17:23:53 agendum 7 closed 17:23:54 I see 6 items remaining on the agenda; the next one is 17:23:54 1. Working Group news! [from agendabot] 17:23:58 zakim, take up item 8 17:23:58 agendum 8 -- -> Initial aria-textseparation (depends on generic PR being merged) https://github.com/w3c/aria/pull/996 -- taken up [from agendabot] 17:24:47 Matt_King: no progress yet, not prioritized, aria-haspopup was higher 17:25:03 Matt_King: wants to work on it 17:25:54 jamesn: not convinced of pressing need for text separation 17:26:05 Matt_King: popup is higher prioirity 17:26:16 scotto: if we could just add a note to core AAM 17:26:21 zakim, close this item 17:26:21 agendum 8 closed 17:26:22 I see 5 items remaining on the agenda; the next one is 17:26:22 1. Working Group news! [from agendabot] 17:26:23 scotto: will file an issue 17:26:32 zakim, take up item 9 17:26:32 agendum 9 -- -> Inconsistency between native and ARIA listboxes when implicit aria-selected is provided https://github.com/w3c/aria/issues/1661 -- taken up [from agendabot] 17:28:12 sarah_higley: no need to discuss 17:28:16 jamesn: have solution 17:28:17 zakim, close this item 17:28:17 agendum 9 closed 17:28:18 I see 4 items remaining on the agenda; the next one is 17:28:18 1. Working Group news! [from agendabot] 17:28:25 zakim, take up item 10 17:28:25 agendum 10 -- -> Secondary actions on items in composite widget roles https://github.com/w3c/aria/issues/1440 -- taken up [from agendabot] 17:29:31 https://github.com/w3c/aria/issues/1440#issuecomment-1091984559 17:29:54 sarah_higley: will put the link in the gist too 17:31:12 steps are listed in the comment 17:32:36 sarah_higley: change the wording "authors may use aria-keyshortcuts" 17:32:49 Matt_King: 3rd most permissive scoping, nameable 17:33:07 Matt_King: wondering whether starting with broad scope is a good idea 17:33:18 just becuase of the amount of testing 17:33:28 large amount of examples 17:33:29 present+ 17:33:35 present+ 17:33:37 to avoid situaitons from the past 17:33:38 agenda? 17:33:42 don't limit unecessarily 17:33:56 when introducing something new 17:34:13 going big as the start has greater potential for chaos 17:34:34 would we be open to start with a more narrowly scoped option 17:34:53 jamesC is pushing for more permissive scope 17:35:13 jamesn: do we risk locking AT in behaviors around what we have done now 17:35:30 Matt_King: if that risk exists there is a problem 17:35:37 with extending it, period. 17:35:53 Matt_King: if the use cases are that different, it shouldn't be broad 17:35:57 jamesn: why is that? 17:36:31 jamesn: if allowed on a broad set of things, constraints may make the interface decision different 17:36:43 risky to narrowly scope originally 17:37:10 Matt_King: the risk in designing broadly will make it more difficult to get implementation in AT 17:37:26 Matt_King: need conversation with AT folks 17:37:51 tests, colloborate with authors and AT devs 17:38:07 the rest of the world will come 17:38:20 success depends on bringing on all stakeholders 17:38:27 end to end from the start 17:38:38 jamesn: no point in doing the work 17:38:55 scotto: aria readonly on checkboxes 17:39:16 sarah talk to jaws and nvda 17:39:25 Matt_King: has meeting with vispero tomorrow 17:39:55 Matt_King: this is actually, going to add this to the agenda in concept 17:40:03 jamesn: out tomorrow 17:40:22 Matt_King: not tomorrow, next week 17:41:05 Matt_King: not talk about secondary actions specifically 17:41:34 Matt_King: 1 goal get feedback on test 17:41:41 with signoff process 17:42:05 Matt_King: the dream for the project, involve them from beginning in the developoment of tests 17:42:15 this is how we might to ARIA in the futute 17:42:21 future 17:42:32 Matt_King: awesome synergy 17:42:47 Matt_King: it was already hard to get stuff in the spec 17:42:57 this is increasing scope 17:43:21 Matt_King: the more we can turn this into a process and the right people to work on things 17:43:34 we have stuff in 1.0 that is not used 17:43:50 jamesn: much of the role parity stuff will not be used 17:43:58 scotto: we should leverage them 17:44:09 we should help them with feedback 17:44:19 sarah_higley: still make a PR 17:44:30 zakim, next item 17:44:30 agendum 1 -- Working Group news! -- taken up [from agendabot] 17:44:45 we have found a new co-chair 17:45:05 Valerie brings technical knowledge 17:45:29 valerie excited to help get 1.2 out the door 17:45:50 valerie learned a lot 17:46:05 engineered regression test framework for APG 17:46:18 scotto: congrats and sorry 17:46:27 scotto: corry 17:46:40 jamesn: lives in same town as jamesn 17:46:48 alemeda 17:47:40 zakim, next item 17:47:40 agendum 11 -- -> Add combobox value support for aria#1225 https://github.com/w3c/core-aam/issues/76 -- taken up [from agendabot] 17:48:48 valerie can close it 17:49:00 not blocking combobox changes 17:50:06 jamesn: fewer user agens how do we get through cr 17:50:33 MichaelC: not before tuesday, brainstorm some proposals 17:50:41 jamesn: only 3 user agents 17:51:01 MichaelC: if we were maintainging html org we would have that angst 17:51:11 zakim, next item 17:51:11 agendum 12 -- -> Do we need a notifications API in ARIA https://github.com/w3c/aria/issues/832 -- taken up [from agendabot] 17:52:19 https://wicg.github.io/aom/notification-api.html 17:52:29 scotto: make things we are using live regions now 17:52:52 q+ 17:52:55 better solution, to pipe what you need to a notification API 17:53:30 Matt_King: can browsers implement for live regions 17:53:41 live regions could leverage this API to be better 17:54:31 scotto: should we have this and also live regions 17:54:54 Matt_King: from authoring perspective you can do both 17:55:30 Matt_King: gazillion ways the DOM can change hard to enumerate 17:55:44 all should be owned by user agent and fed to API for screen reader 17:56:09 just as we have the a11y API we need an API for screen readet 17:56:18 need reliable queuing 17:56:38 if two diff live regions use 2 different ways to render 17:56:58 sarah_higley: are you saying we should be pushing a11y apis to change? 17:57:09 browser managed interactivity 17:57:42 Matt_King:narrator should be able to rely on UIA for anything related to notifications 17:57:57 https://www.w3.org/TR/core-aam-1.2/#mapping_events_visibility 17:58:01 narattor should not be looking at hide/show events 17:58:17 jamesn: coreaaam, has events that fire when things happen 17:58:27 like when text is removed 17:58:35 jamesn: not sufficient, this is what we have 17:58:36 now 17:58:41 ack StefanS 17:58:43 https://experience.sap.com/fiori-design-web/invisible-message/ 17:58:56 StefanS: important to invent messaging framework 17:59:03 q chlane 17:59:44 StefanS: important to offer service 18:00:01 I think every framework has one of those 18:00:01 need guidelines to prevent misuse 18:00:10 https://github.com/adobe/react-spectrum/blob/main/packages/%40react-aria/live-announcer/src/LiveAnnouncer.tsx 18:00:17 q- 18:02:37 jamesn: notifications api is from microsoft 18:02:48 live regions punted to 1.4 18:02:59 will go ahead with or without it 18:03:16 jamesn: notifications API is out of scope for ARIA 18:03:30 Matt_King: rrsagent, make minutes 18:03:38 bkardell_ has joined #aria 18:03:38 rrsagent, make minutes 18:03:38 I have made the request to generate https://www.w3.org/2022/04/14-aria-minutes.html chlane 18:03:42 myasonik has left #aria 19:49:20 quit 19:49:22 exit 19:49:24 quit 19:49:27 leave 19:49:29 exit 19:49:31  21:48:07 github-bot has joined #aria