17:52:36 RRSAgent has joined #aria 17:52:36 logging to https://www.w3.org/2021/12/09-aria-irc 17:52:39 RRSAgent, make logs Public 17:52:40 please title this meeting ("meeting: ..."), jamesn 17:52:41 meeting: ARIA WG 17:52:46 chair: JamesNurthen 17:57:34 agenda+ [New Issue Triage](https://bit.ly/3GrI5uz) 17:57:34 agenda+ [New PR Triage](https://bit.ly/3lKYId0) 17:57:34 agenda+ Holiday Meeting Schedule - meet Dec 16. Then next meeting is Jan 6, 2022 17:57:34 agenda+ [onboarding](https://github.com/w3c/aria/issues/1401) 17:57:34 agenda+ [Should user agents calculate aria-posinset and aria-setsize on treegrid row if there is no author-provided value?](https://github.com/w3c/aria/issues/1602) 17:57:35 agenda+ [Prohibit rowcount and rowindex on rows in treegrid and prohibit posinset and setsize on rows in tables and grids](https://github.com/w3c/aria/issues/1303) 17:57:35 agenda+ [Spec is unclear on aria-invalid="spelling" | "grammar" uses](https://github.com/w3c/aria/issues/989) 18:01:25 pkra has joined #aria 18:02:30 present+ Joanmarie_Diggs 18:02:35 present+ 18:02:43 harris has joined #aria 18:02:48 present+ 18:03:01 Jemma has joined #aria 18:03:26 aaronlev has joined #aria 18:03:33 present+ 18:03:38 present+ 18:03:55 present+ 18:04:11 present+ 18:04:17 present+ 18:04:20 scribe: spectranaut 18:04:30 zakim, next item 18:04:30 agendum 1 -- [New Issue Triage](https://bit.ly/3GrI5uz) -- taken up [from jamesn] 18:04:38 IrfanA has joined #aria 18:04:43 present+ 18:04:48 https://github.com/w3c/aria/issues/1656 18:06:19 StefanS has joined #aria 18:06:27 siri has joined #aria 18:06:31 jamesn: I think we should move to 1.4 18:07:02 bryan: aria-current was never meant to be restricted to only interactive elements 18:07:19 +1 18:07:49 CurtBellew has joined #aria 18:07:56 scottohara has joined #aria 18:08:03 present+ 18:08:06 jcraig: I don't think step is fully represented, I don't think there is enough for the AT to know you are on step 14 of 20, unless you have an additional label... we def need more time to discuss this 18:08:06 present+ 18:08:23 jcraig: this proposal doesn't need a deepdive 18:08:37 jcraig: maybe there is related issues 18:08:40 present+ 18:08:45 jcraig: I'll think about more after call 18:09:01 https://github.com/w3c/accname/issues/147 18:09:18 agenda? 18:09:21 jamesn: I think we should close, other than the link from accname to html aam 18:09:34 cyns: both directions 18:09:42 peter: there is a note in the html spec... 18:09:52 jamesn: it's not in the references in the bottom of the doc 18:10:25 jamesn: an editor of the doc needs to change hte format so it links correctly via respec. it's a hard coded anchor andit shouldn't be. 18:10:32 bryan: I'll try to look at it and fix 18:11:38 zakim, next item 18:11:38 agendum 2 -- [New PR Triage](https://bit.ly/3lKYId0) -- taken up [from jamesn] 18:11:58 https://github.com/w3c/core-aam/pull/103 18:12:24 joanie: I didn't merge because james had asked for two reviews, and caroline reviewed it, I'm ready to merge it 18:12:53 https://github.com/w3c/aria/pull/1657 18:13:16 jamesn: sarah reviewed, can I have two more reviews? 18:13:20 peter: I'll review 18:14:26 jcraig: the respect prefixes the text with "note". rfc2019 normative/non-normative/informative is clear 18:14:43 jamesn: we can merge when peter reviews 18:14:47 zakim, next item 18:14:47 agendum 3 -- Holiday Meeting Schedule - meet Dec 16. Then next meeting is Jan 6, 2022 -- taken up [from jamesn] 18:15:10 James was faster than me. 18:15:26 zakim, next item 18:15:26 agendum 3 was just opened, spectranaut 18:15:37 zakim, next item 18:15:37 agendum 3 was just opened, spectranaut 18:15:54 zakim, close this item 18:15:54 agendum 3 closed 18:15:55 I see 4 items remaining on the agenda; the next one is 18:15:55 4. [onboarding](https://github.com/w3c/aria/issues/1401) [from jamesn] 18:16:03 zakim, next item 18:16:03 agendum 4 -- [onboarding](https://github.com/w3c/aria/issues/1401) -- taken up [from jamesn] 18:16:44 jamesn: is this done? jemma, do you need help? 18:16:58 Jemma: this is on going documentation, never "done" 18:17:22 jamesn: can we move from google doc into something we can all see? 18:17:28 Jemma: sure 18:18:12 Jemma: can we just check in everyonce in a while to see if there is anything to add? 18:19:21 jamesn: it can be in the repository or the wiki? 18:19:45 zakim, next item 18:19:45 agendum 5 -- [Should user agents calculate aria-posinset and aria-setsize on treegrid row if there is no author-provided value?](https://github.com/w3c/aria/issues/1602) -- taken 18:19:48 ... up [from jamesn] 18:20:57 agenda? 18:20:59 mcking: aaron, can you give your summary of the difference between row count and posinset, in practice, what are their differences? 18:21:15 aaronlev: I need to think more before doing that 18:21:36 jamesn: 1303 is the background for this 18:22:03 jamesn: from my perspective, they can be two different things. sometimes they are the same, sometimes not. 18:22:35 jamesn: if you have a virtualized treegrid..... 18:22:43 dcaro has joined #aria 18:23:11 jamesn: just because the properties are available, does not mean the AT should read them at all times when navigating between rows 18:23:57 jamesn: to me they are kind of different, the number of rows may be spoken when you enter the ride yourself. when you navigated around and drop levels.... it does required a lot of screen reader intelligence in order to know what is the relevent data 18:24:08 mcking: I don't think we know if we know what a user might want to know 18:24:54 mcking: they are a useful construct, trees, but when you combine them with the notion of virtualization... you are layering complexity, and I don't know the concept of numbers is the way to help a screen reader user get the same information that a sighted user has 18:25:57 mcking: if you have a virtualized structure on the screen, like scrollbars, and the way things fad at the edges... these are imprecise an subtle, and most users might not notice or care. if you hoist info of the nature on a screen reader user, you are creating cognitive load 18:26:12 jamesn: when you change rows, you hear the row number change 18:26:40 jamesn: despite whether you only have 10 rows, you might move ot the next row and hear 11 18:26:54 mcking: we don't know what kind of end state we want to provide 18:27:21 mcking: but maybe that is not our role, we just provide all information we have to screen reader, and the screen reader decides 18:28:01 jamesn: if you had a treegrid with 100 rows, then that would be too many to go all the way through, if you are row 50 to go to row 51, is that useful? and if so, we need the virtualization 18:28:25 mcking: I never understood if row count applies too... 18:28:39 jamesn: if you don't include them at all, and let the SR calculate them, what does it read? 18:28:52 jcraig: it will count every row that is not a header row 18:29:09 mcking: but is the row count all rows are all levels that are currently visible? 18:29:28 How will they get sublevel row count? and what about invisible rows 18:29:39 mcking: or the rows that are in the dom .. but not visible because the branch is collapsed 18:30:00 mcking: are those counted in rowcount? 18:30:12 jamesn: they might not be fetched 18:30:31 jamesn: they might or might not be in the dom. they are unlikely to be in accessibility tree 18:31:05 mcking: if you have a tree, but every node is in the dom, but only one is visible (because all collapsed) the accessibility tree only has root node 18:31:41 aaronlev: you do nine accessibility APIs, right? 18:32:07 q? 18:32:07 mcking: if you have a normal tree, with one parent node visible, is that the only tree item in the accessibility tree? 18:32:58 aaronlev: it's possible that is the case 18:33:05 jcraig: I think that is how we do it in mac 18:34:04 aaronlev: on mac, there is no "invisible" objects for the accessibility API 18:34:23 aaronlev: on others there is a concept of that in the accessibility tree 18:35:08 aaronlev: there is no requirement about this. trees are treated as things that when they get focused, it provids the data about what you can do with it 18:35:39 mcking: so we talk about rowcount is for virtualized content, to give you the correct total number of rows.... 18:35:48 aaronlev: the setsize is for the level that you are in 18:36:13 mcking so when it comes to treegrids, one question is which row is counted in row count... 18:36:36 mcking: my guess is that it is what person can navigation to without expanding or collapsing. 18:38:42 mcking: I don't know if you want it to be consistent... there are so many views that load more junk, imessage or messanger, if you scroll back in time it loads more stuff. the way I know it loaded more stuff, is you do a three finger tap. at first, you might hear 9-15 of 15, then you scroll back and you hear rows 30-36 of 45, and you scroll back and hear 52-58 of 80 18:39:01 mcking: you get the same idea on the web 18:39:16 jamesn: so knowing that number of how many their are... why put a rowcount on there 18:39:34 mcking: that is just the screen reader counting what is available, not using rowcount 18:39:50 mcking: you can never know what is the total msg history, right? 18:40:09 jcraig: yeah. the screen reader knows "is it rendered in the dom or not" 18:40:24 siri: if the row count is changing based on what is available 18:40:35 siri: how do you know if there is more to reveal? 18:41:02 jcraig: the same way a sited user know? does a sited user know they are going to expand? only when you get closer to the top 18:41:20 mcking: sited users have the scrollbar indicator 18:42:01 mcking: when I'm in imessanger on web, I hit ctrl-home and it will take me to the top of what is loaded, and if I hit page up I know it will load more. I just know, but I don't know how that can be communicated to all users 18:42:47 siri: with sighted users, there is usually some queues to tell you you can load 18:44:17 jamesn: rowcount="-1" means useragents do not calculate rowcount 18:44:39 mcking: does that mean that when the user is in the table they can't know how many rows are currently rendered?? 18:45:15 jamesn: when you have a table and you don't know how many rows are in it, then you don't want to give misleading info 18:45:42 mcking: but if there are 20 rows displayed, and you set it to -1, then the screen reader cannot tell me that I'm row on 1 of 20 18:46:04 mcking: there is a big use in knowing there are at least 20 rows available 18:46:20 jamesn: it would be nice to know there is a minimum but probably more... 18:46:32 +1 james 18:46:39 jamesn: that is what I wanted to be able to provide 18:47:05 mcking: but if the user agent sets it to -1 and the API doesn't have a way to get to the number 20 18:48:23 joanie: this is weedy, and depends on the accessibility API, but you can get from the API how many rows are rendered.. in ATK and IA2 have ways of knowing how many cells are rendered, screen readers need to know that for their own navigation to work. screen readers need a representation for the rendered table. the -1 is the indication that there are more rows or column that are present, but there are more than we know 18:48:42 mcking: I just want to make sure the screen reader can know how many are currently available 18:49:06 jamesn: it says user agents "should not" calculate how many rows exist. 18:50:02 joanie: I would love a straw pull on this because I have a bit rotting change on chromium that aaron is waiting to hear if it should be done 18:50:27 mcking: I don't think they are the same thing posinset/setsize and rowcount/rowindex. 18:51:01 Straw poll: Should user agents calculate aria-posinset and aria-setsize on treegrid row if there is no author-provided value? 18:52:06 Matt_King has joined #aria 18:52:12 prsent+ 18:52:15 present+ 18:52:39 +1 18:52:57 +1 18:53:02 +1 18:53:04 +1 18:53:27 +1 18:53:45 0 18:53:48 +1 18:53:53 +1 no thinking other wise. 18:54:20 +1 this is what AT does currently as far as I am aware 18:54:50 +1 18:55:04 q? 18:55:19 s/AT does/UAs do/ 18:56:24 bkardell_ has joined #aria 18:57:30 jamesn: maybe we need to make a really big tree grid to see how screen readers handle it 18:57:41 mcking: I've seen some really big tables that cause trouble 18:58:05 jamesn: lets not make spec changes until we do more experimentation 18:58:27 mcking: experimentation would allow us to open a more concrete convo with screen reader developers 18:58:41 I added onboarding doc link to https://github.com/w3c/aria/wiki 18:58:42 mcking: maybe we can find creative approaches to mimicing virtualization 18:58:48 agenda? 18:58:50 zakim, next item 18:58:53 agendum 6 -- [Prohibit rowcount and rowindex on rows in treegrid and prohibit posinset and setsize on rows in tables and grids](https://github.com/w3c/aria/issues/1303) -- taken up 18:58:53 ... [from jamesn] 18:58:58 zakim, take up item 7 18:58:58 agendum 7 -- [Spec is unclear on aria-invalid="spelling" | "grammar" uses](https://github.com/w3c/aria/issues/989) -- taken up [from jamesn] 18:58:59 onboarding doc in github is https://github.com/w3c/aria/wiki/ARIA-WG-onboarding-:-Cheat-sheet-for-new-members 18:59:23 jamesn: aaronlev do we have a path forward, or is there something you need? 19:00:00 aaronlev: the way that we do it in chrome, if aria-invalid it used... it should have never been done in one attribute... 19:00:52 aaronlev: spelling and grammar only makes sense on text in editing context. like on a span for example. it doesn't make sense on a whole form control. aria-invalid=true, it only makes sense on form controls and not spans. I don't think this is clear in the spec, and chrome implements the thing that makes sense 19:00:58 Need to go. bye everyone 19:01:06 jamesn: we deprecated aria-invalid on anything other than a form 19:01:38 mcking: when we deprecated it, didn't we discuss adding a new property? 19:01:46 jamesn: we have discussed it sense. 19:02:32 mcking: I'm concerned about letting aria-invalid being something that is not an input, I'm more interested in a new property 19:03:09 aaronlev: I think that would make sense to have a new property for spelling and grammar, there are few implementers of aria-invalid for spelling and grammer, and I think that user agents should support the old deprecated situation for a while 19:03:26 jamesn: I don't imagine this will be removed 19:03:43 RRSAgent: make minutes 19:03:43 I have made the request to generate https://www.w3.org/2021/12/09-aria-minutes.html spectranaut