17:47:12 RRSAgent has joined #aria 17:47:12 logging to https://www.w3.org/2022/12/01-aria-irc 17:47:14 RRSAgent, make logs Public 17:47:16 please title this meeting ("meeting: ..."), jamesn 17:47:21 meeting: ARIA WG 17:47:26 agendabot, find agenda 17:47:26 jamesn, OK. This may take a minute... 17:47:26 agenda: https://www.w3.org/events/meetings/2b92a902-1365-4ea0-8c68-9f8ae2106fe3/20221201T130000 17:47:26 clear agenda 17:47:26 agenda+ -> New Issue Triage https://bit.ly/3VzqbxN 17:47:27 agenda+ -> New PR Triage https://bit.ly/3ihwp6Z 17:47:29 agenda+ -> Deep Dive planning https://bit.ly/aria-meaty-topic-candidates 17:47:32 agenda+ -> ACT/ARIA Review https://github.com/w3c/aria/issues/1847 17:47:35 agenda+ -> 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+ 17:56:47 chlane has joined #aria 17:58:50 Adam_Page has joined #aria 18:00:01 scotto has joined #aria 18:00:07 present+ 18:01:03 present+ 18:01:03 Wilco has joined #aria 18:01:07 present+ 18:02:01 regrets+ PeterKrautzberger 18:02:10 present+ 18:02:29 MarkMcCarthy has joined #aria 18:02:37 present+ 18:02:43 scribe; chlane 18:02:45 present+ 18:02:52 scribe: chlane 18:03:47 StefanS has joined #aria 18:04:16 zakim, next item 18:04:16 agendum 1 -- -> New Issue Triage https://bit.ly/3VzqbxN -- taken up [from agendabot] 18:04:25 present+ 18:04:46 siri has joined #aria 18:05:09 dpubaam 16 18:05:32 jamesn: sounds like a PR is the easiest way 18:05:55 CurtBellew has joined #aria 18:05:57 present+ 18:05:58 jamesn: who is the editor 18:06:05 martt garrish 18:06:12 assigning to matt 18:06:17 present+ 18:06:27 aria act rules review 18:06:36 go over later 18:06:48 #176 accname 18:07:08 would not pick up aria description from there 18:07:12 adding editorial note 18:07:19 milestoning next year 18:07:35 adam page will rewrite 18:07:44 zakim, next item 18:07:44 agendum 2 -- -> New PR Triage https://bit.ly/3ihwp6Z -- taken up [from agendabot] 18:07:57 html aam pr #446 18:08:05 popover related attributes 18:08:11 BGaraventa has joined #aria 18:08:24 jamesn: no reviewers needed but can volunteer if involved 18:08:30 present+ bgaraventa 18:08:30 scotto: not complete yet 18:09:41 zakim, next item 18:09:41 agendum 3 -- -> Deep Dive planning https://bit.ly/aria-meaty-topic-candidates -- taken up [from agendabot] 18:09:54 next week we have 18:10:01 aria-flowto 18:10:12 jamesn: no more slots for this year 18:10:30 jamesn: propose no more this year 18:10:46 jamesn: resolved 18:10:47 zakim, next item 18:10:47 agendum 4 -- -> ACT/ARIA Review https://github.com/w3c/aria/issues/1847 -- taken up [from agendabot] 18:11:12 Wilco: 18:11:32 act is a project in the a11y guidelines working group 18:11:50 8 years working to get orgs to test wcag consistently 18:11:54 tools focus 18:11:57 spectranaut has joined #aria 18:12:00 manual testing methodologies 18:12:04 present+ 18:12:16 developed ACT rules format as a w3c recommedation 18:12:22 for how to write rules 18:12:35 applicability/expactations 18:12:50 effectively and few requirements 18:12:56 used in tools to verify 18:13:14 have a lot of wcag rules and some ARIA rules 18:13:22 wcag/aria overlap 18:13:34 is where my ask for this groups come in 18:13:42 WCAG/ARIA has overlap 18:14:08 ACT is a task force, need a Working group to say yay or nay 18:14:27 to "how we think aria should be tested" 18:14:36 jamesn: take us through one of these rules 18:14:59 jamesn: glossary forms a significant part of the length of the rule 18:15:12 https://www.w3.org/WAI/standards-guidelines/act/rules/6a7281/proposed/ 18:15:18 know how these are constucted to prevent duplication 18:15:38 "aria state or property has valid value" 18:15:56 Descriptions, Applicability, Expectation, Assumptions 18:16:23 applicability looks for non empty values on svg or html elements 18:16:35 any element with aria attributes 18:16:44 expectation, a valid value 18:16:51 value types are defined 18:17:13 ID reference rules are in question 18:17:20 need ARIA WG opinion 18:17:25 jamesn: see contradiction 18:17:42 Wilco: generic URI syntax 18:17:51 does ARIA require this? 18:18:02 do we have value types in URI? 18:18:03 we do 18:18:13 Wilco: assumptions, related to wcag 18:18:23 theoretical false positive opportunity 18:18:31 interpretation questions 18:18:48 background provides more details 18:18:54 bibliography, 18:19:12 accessibility requirements mapping, habe no or unknown mapping 18:19:32 input aspects, the info necessary to run test, access to DOM, CSS 18:19:37 test cases 18:19:50 pass fail and inapplicable 18:20:04 Glossary, has definitions 18:20:20 'namespaced element', 'outcome' 18:20:30 links to specs 18:20:58 q+ to say I think URI may have been proposed for aria`describedat`but I don't see any current URI types https://w3c.github.io/aria/#propcharacteristic_value 18:21:12 implementations, list of tools and testing methodologies that have know consistency with the rule 18:21:19 q+ to ask why the list version locks it to 1.2 18:21:26 Wilco: questions? 18:21:48 StefanS: are axe and AMP related? 18:22:13 Wilco: not a question for ACT task force 18:22:26 Wilco: this list comes for orgs that publish test results 18:22:47 orgs who want to can run there test methods and tools against this 18:23:00 list of orgs and tools that have done that work 18:23:22 jamesn: I think we look through all pass fail examples 18:23:44 ack me 18:23:44 jcraig, you wanted to say I think URI may have been proposed for aria`describedat`but I don't see any current URI types https://w3c.github.io/aria/#propcharacteristic_value and to 18:23:46 jamesn: why put in passing failing examples 18:23:47 ... ask why the list version locks it to 1.2 18:23:52 q+ cyns 18:24:12 jcraig: URI had been proposed with describedat 18:24:34 the applicability and expectations sections list aria 1.2 18:24:45 wondering why 18:24:57 Wilco: not sure how else to do it 18:25:08 q+ 18:25:18 Wilco: what do we do with aria 1.3? 18:25:32 qq+ 18:25:37 jcraig: just link to top level of ARIA? 18:25:45 ack me 18:25:45 jamesn, you wanted to react to jcraig 18:25:50 Wilco: have to worry about versions 18:25:58 jamesn: 1.1 rules not valid in 1.2 18:26:17 jamesn: version specifics are a good idea 18:26:36 Wilco: we review rules once a year 18:26:47 living documents not parked 18:27:03 ack cyns 18:27:15 Wilco: inconsistencies happen as these things evolve 18:27:22 q+ StefanS 18:27:47 cyn: aria conformance test suite source for additional rules? 18:27:59 Wilco: it might be interesting to explore 18:28:09 ack scotto 18:28:33 scotto: 2 things, specific versioning it would be great if can not do it in case we go to living standard model 18:28:40 no such thing as version numbers 18:28:51 expecially in this space 18:29:00 rules may not help people anymore 18:29:07 second thing, 18:29:27 ack StefanS 18:30:03 StefanS: these rules are defined and correctly spelled, allowed/not allowed overrides 18:30:24 override checks? 18:30:39 Wilco: a separate rule 18:30:53 StefanS: super helpful with discussions with developers 18:31:01 these cases are detected late 18:31:20 jamesn: not pure ARIA html/aam rule 18:31:30 aria in html 18:31:42 jamesn: how to review 18:31:53 Wilco: not a tight timeline 18:31:59 Wilco: years to go 18:32:11 piecemeal approach is good 18:32:16 start with one 18:32:50 Wilco: announcing a formal list of implementations 18:32:55 https://www.w3.org/WAI/standards-guidelines/act/implementations/ 18:33:11 jamesn: any rules that those things are checking that you are asking us to review 18:33:26 Wilco: the proposed rules 18:33:35 need our agreement 18:34:05 Wilco: no rush, start with 1 or 2, what is the preferred way for this group to survey things? 18:34:30 jamesn: concerned with rules already approved that the group won't agree with? 18:34:50 jamesn: anything with ARIA should go through this group 18:35:04 Wilco: no ARIA specific rules 18:35:10 https://www.w3.org/WAI/standards-guidelines/act/rules/ 18:35:16 jamesn: proposed rules for wcag look aria specific 18:35:39 rules beyond wcag include ARIA rules 18:35:43 there is overlap 18:35:55 jamesn: I'd like to set timelines 18:36:05 when are you looking for feedback 18:36:11 Wilco: no timeline 18:36:38 in an ongoing process to get a very lengthy list approved 18:36:50 working in batches with WCAG 18:37:04 we would do that every few months 18:37:24 jamesn: filing an issue will be good 18:37:43 jamesn: this is important for content creation 18:38:03 jamesn: encourage a careful eye 18:38:19 Wilco: would love more rules to write 18:38:45 jamesn: go through spec and look for authors MUST 18:39:12 cyns see core aam as well 18:39:26 svg and css should be looked at too 18:39:42 jamesn: we used to avoid authors 'must' 18:39:52 we didn't have tests 18:40:00 q+ 18:40:11 cyns, aria authors must in 1.3 18:40:37 cyns looking for things that will become author must in 1.2 18:40:58 jamesn: we created test cases, not as detailed with multiple pass/fails 18:41:16 ack Wilco 18:41:43 Wilco: we think there are places that there should be authr must and should 18:42:07 jamesn: show of hands for interested 18:42:13 I’m interested 18:42:26 I'm interested as well 18:42:26 I'm interested 18:42:30 melsumner has joined #aria 18:42:34 I'm interested. 18:42:38 happy to review as well 18:43:01 I've already been reviewing them :) Excited about this project, and ember-template-lint has some good a11y rules too. 18:43:05 jamesn: if you are creating frameworks you should review this 18:43:21 spectranaut: talk about how to split up work 18:43:49 spectranaut: in the issue, you can list the one's you have reviewed 18:44:02 comment that you looked at the whole thing 18:44:18 scotto: good place to move to discussions 18:44:48 jamesn: using discussions and threads for each rule 18:44:55 and glossary definition 18:45:14 jamesn: only downside 18:45:20 they don't query the same way 18:45:27 we have to remember to look at them 18:46:11 q? 18:46:34 zakim, next item 18:46:34 agendum 5 -- -> 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+ -- taken up [from 18:46:37 ... agendabot] 18:46:40 jamesn: 18:47:07 jamesn: no movement 18:47:29 great to get some movement, some will go away with Sarah's descendant issue 18:47:43 jamesn: has that one had any progress? 18:47:59 jcraig: suggested another name 18:48:14 child, descendant parent has baggage from DOM 18:48:24 jamesn: 1454 18:48:44 jamesn: were close 18:50:02 scotto: prefer ancestor roles 18:50:31 in html aam been working on 18:50:42 the concept of scoped elements in html 18:50:53 and how roles are related based on that 18:51:07 that is where my terminology is going 18:51:19 jamesn: if you can all agree that is great 18:51:30 jamesn: last thing other than tests to merge 18:51:45 jamesn: coming to concencus just worried about naming 18:52:21 jamesn: if we are going to use a word that has another meaning in the DOM 18:52:26 we need to clarify 18:52:41 jcraig: fwiw, drop context role 18:52:59 requiredaccessibiltyancestor 18:53:12 Adam_Page: working on pr related to ownership 18:53:15 ancestry 18:53:30 can be another candidate for naming 18:53:42 jcraig: inclusivity, like master slave 18:54:03 jamesn: allowed elements rather than owns 18:54:18 cyns aria owns does not change a11y tree 18:54:31 jcraig: complicated but will get it done 18:54:56 cyns is heirarchy a11y tree? 18:54:58 jcraig: yes 18:55:03 q+ siri 18:55:16 cyns add a11y tree things to glossary 18:55:23 more clarification would be good 18:55:36 sarah 18:55:46 same as original problem 18:55:56 direct ancestor and descendant 18:56:06 jamesn: objected to DOM meanings 18:56:16 need to be unambiguous 18:56:32 melsumner: not talking about dom anymore? 18:56:40 cyns like proposal 18:56:52 cyns talk about both in same paragraph 18:57:14 ack siri 18:57:17 siri: aria-owns 18:57:27 issues comboboxes 18:57:39 when I raised issues and point to 1.2 18:57:56 developers cant implement 18:58:04 when will it be ready? 18:58:12 jamesn: soon 1.2 will go to pr 18:58:26 jamesn: core-aam is in CR 18:58:35 jamesn: have passing test 18:58:44 cyns; once in pr, how long? 18:58:52 jamesn: 30 days? 18:59:16 MichaelC: 30 day for CR review by advisory committee 18:59:38 MichaelC: no objections can go to req 18:59:49 jamesn: many people a PR is good 19:00:29 jamesn: anyone doing a 1.1 combobox is making more work 19:00:45 cyns this happens in big companies 19:00:51 cyns, timeline? 19:01:08 jamesn: working on it, before xkmas 19:01:13 end of january 19:01:17 2023 19:01:23 cyns will say q1 19:01:35 jamesn: how to get 1.3 draft out 19:01:46 zakim, end meeting 19:01:46 As of this point the attendees have been MichaelC, Adam_Page, chlane, daniel-montalvo, Wilco, jamesn, StefanS, scotto, CurtBellew, bgaraventa, spectranaut 19:01:49 RRSAgent, please draft minutes 19:01:49 I have made the request to generate https://www.w3.org/2022/12/01-aria-minutes.html Zakim 19:01:51 I am happy to have been of service, chlane; please remember to excuse RRSAgent. Goodbye 19:01:55 Zakim has left #aria 19:03:13 DPUB-AAM issue: https://github.com/w3c/aria/issues/1643 19:03:17 PR: https://github.com/w3c/dpub-aam/pull/15 19:04:05 The PR is Apple API specific, but IMO, other APIs may want to do something similar to not overload their AT users with verbose minutia. 19:04:23 Reviewers requested. Thanks. 19:04:53 rrsagent, make minutes 19:04:53 I have made the request to generate https://www.w3.org/2022/12/01-aria-minutes.html jcraig 19:16:41 quit 20:09:23 howard-e has joined #aria 21:22:59 howard-e has joined #aria 22:49:22 melsumner has joined #aria 23:09:36 melsumner has joined #aria