16:58:24 RRSAgent has joined #aria 16:58:24 logging to https://www.w3.org/2021/06/10-aria-irc 16:58:26 RRSAgent, make logs Public 16:58:28 please title this meeting ("meeting: ..."), jamesn 16:58:28 meeting: ARIA WG 16:58:33 chair: JamesNurthen 16:59:03 agenda+ [New Issue Triage](https://bit.ly/3wlqKig) 16:59:03 agenda+ [New PR Triage](https://bit.ly/3pOjIAx) 16:59:03 agenda+ [Meaty topic for next week](https://bit.ly/3ivpVzm) 16:59:03 agenda+ [Problematic mappings for without href](https://github.com/w3c/html-aam/issues/333) 16:59:03 agenda+ [Mappings for body and html don't seem to match reality](https://github.com/w3c/html-aam/issues/330) 16:59:04 agenda+ [Exit Criteria Testing: Need test cases and results for Authors MUST/MUST NOT statements in ARIA 1.2](https://github.com/w3c/aria/issues/1492) 16:59:04 agenda+ [When is hidden content taken into calculation of name and description?](https://github.com/w3c/accname/issues/57) 17:05:04 CurtBellew has joined #aria 17:05:07 pkra has joined #aria 17:05:09 present+ 17:05:10 present+ 17:05:42 scribe: pkra 17:05:49 present+ 17:05:50 present+ 17:05:53 zakim, next item 17:05:53 agendum 1 -- [New Issue Triage](https://bit.ly/3wlqKig) -- taken up [from jamesn] 17:06:17 StefanS has joined #aria 17:06:30 jnurthen: issue 1500 17:07:33 MarkMcCarthy has joined #aria 17:07:34 ... do we call this a won't fix ? 17:07:38 RRSAgent, make minutes 17:07:38 I have made the request to generate https://www.w3.org/2021/06/10-aria-minutes.html MarkMcCarthy 17:07:46 ... or anyone disagree? 17:07:57 bryan: I'll take a look 17:07:57 present+ 17:08:26 jnurthen: accname issue 132 17:08:43 ... will assign to Melanie 17:08:45 present+ Joanmarie_Diggs 17:09:11 ... accname issue 131 17:09:17 ... is it a duplicate? 17:09:19 bryan: will do. 17:09:33 zakim, next item 17:09:33 agendum 2 -- [New PR Triage](https://bit.ly/3pOjIAx) -- taken up [from jamesn] 17:10:09 jnurthen: aria PR 1498. please take a first look 17:10:15 zakim, next item 17:10:15 agendum 2 was just opened, pkra 17:10:20 zakim, close item 17:10:20 I don't understand 'close item', pkra 17:10:21 zakim, next item 17:10:22 agendum 2 was just opened, pkra 17:10:27 zakim, close this item 17:10:27 agendum 2 closed 17:10:28 zakim, next item 17:10:29 I see 5 items remaining on the agenda; the next one is 17:10:29 3. [Meaty topic for next week](https://bit.ly/3ivpVzm) [from jamesn] 17:10:29 agendum 3 -- [Meaty topic for next week](https://bit.ly/3ivpVzm) -- taken up [from jamesn] 17:10:45 jnurthen: deep dive next week. 17:11:19 ... Aaron can't make it for accname discussion, so probably not a good idea. 17:11:33 bryan: would be good to have as many as possible. 17:12:05 jnurthen: any proposals? Otherwise we skip 17:12:22 ... e.g., work session on author tests 17:13:21 ... ok. currently no proposal. accname deep dive for week after. 17:13:22 zakim, next item 17:13:22 agendum 4 -- [Problematic mappings for without href](https://github.com/w3c/html-aam/issues/333) -- taken up [from jamesn] 17:14:06 scott: comes back to "generic inline" etc. 17:14:38 q+ 17:14:45 ack me 17:15:13 jnurthen: it's not really the role that makes it generic inline or block. 17:15:35 siri has joined #aria 17:15:43 scott: right. comes down to platform mappings. One currently says it maps to text. 17:15:56 ... that's why I'd like to get consensus from the group 17:16:02 jnurthen: what does span map to>? 17:16:11 joanie: ATK maps it to generic. 17:16:40 ... if my platform is the only blocker, I'm ok with changing it. 17:16:56 scott: a no href for IA1 maps role system text / text frame 17:17:44 ... but we have different mappings, same with div 17:18:22 joanie: maybe we can check with NVDA people. IA2 are parallel to ATK mappings. So ask them if it's a problem. 17:18:37 ... if they agree, then we can make progress. 17:18:52 ... as a follow up conversation, make inline vs block generic a separate issue 17:18:58 ... taking CSS into account 17:19:29 ... I think we can take CSS into consideration for platform roles 17:19:42 scott: sounds good with me 17:21:04 aaron: do we agree that a without href can just map as span with id? 17:21:19 all: sounds good 17:21:38 agree as as it is used a place holder when we without href 17:22:10 aaron: speaking with James Teh, they use a different role for div vs span 17:22:20 ... he agreed it was kind of nice but probably didn't matter. 17:23:32 .. and we can tackle block vs inline (and other display) separately 17:23:42 zakim, next item 17:23:42 agendum 5 -- [Mappings for body and html don't seem to match reality](https://github.com/w3c/html-aam/issues/330) -- taken up [from jamesn] 17:24:46 jnurthen: do we have what we need for this? 17:25:18 joanie: currently, we don't match reality. We could match but what would the mapping of body be? 17:25:27 ... scott had suggested generic 17:25:57 ... but aria-label then prohibited, brought in "UA not to expose it" discussion 17:26:15 ... but authoring error and resolution as follow up 17:26:18 ... which seems ok 17:26:39 scott: I'm still for generic. naming is not a good idea. 17:27:06 jnurthen: what about matt's recent comment? 17:27:24 joanie: I disagree. it's generic, authors shouldn't put labels on body. 17:27:30 ... does anyone think it's a good idea? 17:27:52 cynthia: at most: iframe scenarios 17:28:05 joanie: same as with div 17:28:22 ... if we think authors should not / must not do it, then validators will flag it 17:28:29 ... but UAs can handle it 17:28:41 scott: and validators already flag it. 17:28:48 jnurthen: so we map it to generic? 17:29:05 ... no objection 17:29:21 zakim, next item 17:29:21 agendum 6 -- [Exit Criteria Testing: Need test cases and results for Authors MUST/MUST NOT statements in ARIA 1.2](https://github.com/w3c/aria/issues/1492) -- taken up [from 17:29:24 ... jamesn] 17:30:16 jnurthen: a deep dive / work session would be great. 17:30:32 joanie: I could do that. Tried locally, throwing at aXe 17:30:40 cynthia: I could, too. 17:30:50 +1 from pkra 17:31:06 jnurthen: ok, then let's schedule a work session for deep dive next week. 17:32:23 cynthia: could use a refresh on test framework 17:32:39 joanie: couldn't find a great way to automate things yet. But yes, let's talk. 17:33:04 jnurthen: Harris should be able to help. Hopefully at the meeting, too. 17:33:41 ... I won't be there though. 17:34:31 zakim, next item 17:34:31 agendum 7 -- [When is hidden content taken into calculation of name and description?](https://github.com/w3c/accname/issues/57) -- taken up [from jamesn] 17:34:40 +1 to that 17:35:00 jnurthen: not a lot of comments on it so far. 17:35:23 ... maybe start with joanie's tldr 17:35:35 https://github.com/w3c/accname/issues/57#issuecomment-843173057 17:37:39 q? 17:39:51 cynthia: I think I remember some history. 17:40:18 ... the original idea for allowing hidden content was to have accessibility API only content. 17:40:45 ... initially, all visually hidden was disregarded always. 17:41:12 jnurthen: is there a real world use case for this? I can make some up but I don't know a real one. 17:41:26 ... children of something that's hidden not getting exposed. 17:41:58 ... e.g. tooltip via describedBy, not visible when focus is moved (delayed) there but you still want it as description. 17:42:12 ... you still want that child span to be part of the accessible description. 17:42:37 cynthia: I wonder why it has to be so complicated though. 17:42:50 siri: is this similar to screen-reader only text? 17:43:09 jnurthen: not quite. 17:43:39 https://github.com/w3c/accname/issues/57#issuecomment-843186043 17:43:48 ... joanie's next comment. 17:43:51 17:44:26 ... div hidden and being referenced, div with two children additionally hidden 17:44:42 cynthia: first reaction: everything but aria-hidden 17:46:06 scott: a situation where I wouldn't want hidden ones exposed would be a input with aria-required and a hidden label, I might want that. 17:46:16 + scott 17:46:49 jnurthen: but that'd be aria-hidden again 17:47:08 scott: right. 17:48:05 cynthia: the only scenario I can come up with is a dynamic tooltip. Use hidden to get rid of visual stuff and use aria-hidden to hide it from accessibility tree 17:48:32 scott: yes, I can imagine that. 17:49:17 siri: sometimes you put aria-hidden on chevrons etc. because they add too much noise. 17:49:31 jnurthen: so nobody expected it to work the way the spec says today? 17:49:43 ... and what about implementations? 17:50:35 joanie: IIRC James had mentioned not wanting to accidentally dive into a huge tree. 17:50:41 ... we should check on that. 17:51:05 ... my colleague tested it and it seems to prune it all. 17:51:28 jnurthen: do we need a way to not prune that stuff? E.g., aria-hidden. 17:51:35 cynthia: what's chromium doing right now? 17:51:53 https://github.com/w3c/accname/issues/57#issuecomment-843032936 17:51:55 joanie: I think Case 2 was only baz in the tree. 17:52:09 jnurthen: comment has some results. 17:53:10 ... so chromium matches what you suggested 17:53:25 ... firefox ignores both types of hidden 17:53:45 ... webkit we'll have to double check. 17:53:56 ... can we get agreement from implementors? 17:54:45 ... real world use cases would greatly help here. 17:55:15 cynthia: maybe complex tooltips? 17:56:46 cynthia: so for labels, can we agree that aria-hidden is to prune it from accessibility tree, display:none from visual tree? 17:57:04 jnurthen: everyone, please comment on the issue. 17:57:35 ... more comments will help inform these decisions, especially from real world examples. 17:58:14 rrsagent, make minutes 17:58:14 I have made the request to generate https://www.w3.org/2021/06/10-aria-minutes.html pkra 18:00:38 present+ 18:01:10 there's a bunch of thing impacted by some outage yep: https://www.w3.org/2003/08/system-status