06:23:00 <RRSAgent> RRSAgent has joined #cssa11y
06:23:00 <RRSAgent> logging to https://www.w3.org/2021/10/20-cssa11y-irc
06:23:03 <dom> RRSAgent, make log public
06:23:04 <dom> RRSAgent, stay
10:29:41 <painterforum> painterforum has joined #cssa11y
15:39:52 <janina> janina has joined #cssa11y
15:40:24 <janina> zakim, who's here?
15:40:53 <janina> Meeting: CSS & APA Annual Checkin
15:41:02 <janina> Date: 20 Oct 2021
15:42:11 <janina> zakim, who's here?
15:42:22 <Zakim> Zakim has joined #cssa11y
15:42:41 <janina> Chair: Rossen, Janina
15:42:51 <janina> rrsagent, make log public
15:49:18 <janina> agenda+ More Media Queries for A11y?
15:49:18 <janina> agenda+ Can CSS help with preventing video with flashing? Or should it be HTML based?
15:49:21 <janina> agenda+ CSS speech vis a vis APA Pronunciation: Any concerns?
15:49:23 <janina> agenda+ Address issue 6351: https://github.com/w3c/csswg-drafts/issues/6351.
15:49:26 <janina> Agenda+ APA & CSS Liaison Going Forward
15:49:27 <dandclark> dandclark has joined #cssa11y
15:55:48 <vmpstr> vmpstr has joined #cssa11y
15:57:59 <Matthew_Atkinson_> Matthew_Atkinson_ has joined #cssa11y
15:58:18 <MasakazuKitahara> MasakazuKitahara has joined #cssa11y
15:58:26 <MasakazuKitahara> present+
15:58:32 <emeyer> emeyer has joined #cssa11y
15:58:36 <Jennie> Jennie has joined #cssa11y
15:58:46 <Joshue108> Joshue108 has joined #cssa11y
15:58:56 <Francis_Storr> Francis_Storr has joined #cssa11y
15:59:07 <Francis_Storr> present+
15:59:25 <Jennie> present+
15:59:43 <Aimee_U> Aimee_U has joined #cssa11y
15:59:49 <Rossen_> Rossen_ has joined #cssa11y
16:00:03 <amy_c> amy_c has joined #cssa11y
16:00:48 <Rossen_> Here's the agenda project https://github.com/w3c/csswg-drafts/issues/6351
16:00:57 <amy_c> present+
16:01:02 <ivan> ivan has joined #cssa11y
16:01:14 <chris> chris has joined #cssa11y
16:01:31 <Joshue108> present+
16:01:37 <Rossen_> present+
16:01:54 <jamesn> jamesn has joined #cssa11y
16:01:55 <jeff> jeff has joined #cssa11y
16:01:57 <Aimee_U> present+
16:02:00 <dbaron> dbaron has joined #cssa11y
16:02:06 <Rossen_> Rossen_ has changed the topic to: Agenda at https://github.com/w3c/csswg-drafts/issues/6351
16:02:09 <jasonjgw> jasonjgw has joined #cssa11y
16:02:11 <janina> janina has left #cssa11y
16:02:12 <LisaSeemanKest_> LisaSeemanKest_ has joined #cssa11y
16:02:13 <jamesn> present+
16:02:14 <vmpstr> present+
16:02:16 <aaronlev> aaronlev has joined #cssa11y
16:02:19 <alisonmaher> alisonmaher has joined #cssa11y
16:02:25 <fantasai> fantasai has joined #cssa11y
16:02:32 <LisaSeemanKest_> present+
16:02:39 <alisonmaher> present+
16:02:43 <dandclark> present+
16:02:44 <janina> janina has joined #cssa11y
16:02:50 <jasonjgw> present+
16:02:58 <janina> present+
16:02:59 <r12a> r12a has joined #cssa11y
16:03:35 <jfkthame> jfkthame has joined #cssa11y
16:03:48 <chris> present+
16:03:49 <hdv> hdv has joined #cssa11y
16:04:07 <kzms2> kzms2 has joined #cssa11y
16:04:10 <jfkthame> present+
16:04:19 <SuzanneTaylor> SuzanneTaylor has joined #cssa11y
16:04:43 <Morgan> Morgan has joined #cssa11y
16:05:01 <astearns> astearns has joined #cssa11y
16:05:01 <hdv> present+
16:05:04 <florian> florian has joined #cssa11y
16:05:04 <kzms2> present+
16:05:05 <Morgan> present+
16:05:09 <dbaron> Present+
16:05:19 <r12a> present+
16:05:19 <florian> present+
16:05:19 <emeyer> present+
16:05:21 <janina> present+
16:05:21 <Travis> Travis has joined #cssa11y
16:05:22 <ivan> present+
16:05:22 <SuzanneTaylor> present+
16:05:23 <miriam> miriam has joined #cssa11y
16:05:24 <jeff> present+
16:05:27 <aaronlev> present+
16:05:29 <jcraig> jcraig has joined #cssa11y
16:05:30 <Travis> present+
16:05:32 <miriam> present+
16:05:33 <fantasai> present+
16:05:35 <emeyer> Rossen: many people on the call; not sure we have time for intros
16:05:36 <jcraig> present+
16:05:44 <Kim_patch_> Kim_patch_ has joined #cssa11y
16:05:55 <emeyer> …there are a few topoics we captured in Github topic
16:05:59 <dholbert> dholbert has joined #cssa11y
16:06:02 <fantasai> s/topoics/topics/
16:06:08 <Kim_patch_> Present+
16:06:10 <emeyer> …we have three topics tracked by CSS issues
16:06:28 <Becky> Becky has joined #cssa11y
16:06:36 <Becky> present+
16:07:03 <emilio> emilio has joined #cssa11y
16:07:09 <emeyer> Rossen: let’s tackle the first issue on the agenda.  Do we have the Github tracker here?
16:07:11 <Tiger> Tiger has joined #cssa11y
16:07:13 <emeyer> dbaron: No.
16:07:27 <BC> BC has joined #cssa11y
16:07:29 <emeyer> Rossen: okay.  We’ll do our best to capture minutes and post them into discussions.
16:07:43 <kirkwood> kirkwood has joined #cssa11y
16:07:56 <Jemma> Jemma has joined #cssa11y
16:08:06 <chris> https://github.com/w3c/csswg-drafts/issues/6498
16:08:08 <emeyer> https://github.com/w3c/csswg-drafts/issues/6498
16:08:10 <jensimmons> jensimmons has joined #cssa11y
16:08:21 <fantasai> Topic: Highlights in Accessibility Tree
16:08:23 <fantasai> github: https://github.com/w3c/csswg-drafts/issues/6498
16:08:31 <Rossen_> Topic: Figure out how highlights are exposed to the accessibility tree
16:08:35 <jensimmons> present+
16:08:39 <dholbert> present+
16:08:41 <emeyer> Rossen: Florian, you were the person who added this issue.  Could you summarize?
16:08:48 <myles> myles has joined #cssa11y
16:09:01 <Rossen_> q?
16:09:31 <emeyer> Florian: highlights are a things that exist in CSS already, you can select and style them.  Example: spelling-error pseudo.  We’re introducing an API that lets you create more.  You can create a type of highlight and then style it via the API.
16:09:34 <kirkwood> present+
16:09:37 <emilio> present+
16:09:45 <emeyer> …question is, how will this be exposed to the accessibility tree?
16:09:58 <emeyer> …We have a definitive answer to this.
16:10:33 <Leticia> Leticia has joined #cssa11y
16:10:50 <emeyer> Dandclark: What we propose is adding a type field to the highlight API so the author can say what they’re using it for.
16:11:27 <janina> q+ to ask if can be used to hide?
16:11:27 <emeyer> …type field can be ‘spelling-error’, ‘grammar-error’.  enum could be extended later to add more types.
16:11:50 <emeyer> …This would add these to the a11y tree in the same was existing pseudos are exposed to the tree.
16:12:03 <Rossen_> ack janina
16:12:03 <Zakim> janina, you wanted to ask if can be used to hide?
16:12:09 <emeyer> Janina: Could this also be used to hide an area of the screen?
16:12:35 <emeyer> Florian: To the same extent any element can be hidden using CSS, yes. Such as white-on-white text.
16:12:53 <jcraig> q+ to ask Janina the context for her question about "hiding"
16:13:01 <emeyer> …the current difference is element have to be bound to the tree.  Selections don’t; they can cross element boundaries.
16:13:18 <Rossen_> ack jcraig
16:13:18 <Zakim> jcraig, you wanted to ask Janina the context for her question about "hiding"
16:13:27 <fantasai> Actually, much less than can be done with CSS in general. Highlight pseudo styling is extremely limited, and can't affect layout.
16:13:35 <emeyer> jcraig: Can I have more clarrity on what’s meant by hiding?
16:13:39 <LisaSeemanKest_> q+
16:13:57 <emeyer> Janina: looked like another mechanism
16:14:23 <Rossen_> ack LisaSeemanKest_
16:14:35 <emeyer> Lisa: Seems to me we should use the same model we use with ARIA because it works and it’s familiar to people.
16:15:21 <Rossen_> q+
16:15:28 <emeyer> …you can toggle the CSS against element state run by ARIA.  Seems we could do something similar, we could have pink for grammar, green for extra-long words, red for spelling error.  You could have reserved words and allow other words as well.
16:16:05 <emeyer> …This would allow the feature to extend.  So you could have ‘aria-spelling’ or something like that.  ‘off’ or ‘none’ could be reserved, indicating there’s no special highlighting.
16:16:12 <JF> JF has joined #cssa11y
16:16:13 <jcraig> q+ to express preliminary support for Dan Clark's proposal, and mention the WebKit implementation with Apple platform accessibility APIs and attributed strings
16:16:20 <JF> Present+
16:17:00 <smfr> smfr has joined #cssa11y
16:17:06 <emeyer> Rossen: I’d like to question some of the path forward to align with ARIA.  One thing CSS highlight lets us do is cross element boundaries in a not-necessarily-normalized way, given how HTML works today.
16:17:32 <emeyer> …Example: Handling a selection that starts right before a button and ends in the middle of the button.  Describing this with ARIA is difficult.
16:17:50 <emeyer> …In terms of the direction where this is going, I’m not sure it aligns well with ARIA.
16:17:57 <emeyer> Lisa: That makes perfect sense.
16:18:00 <Rossen_> ack Rossen_
16:18:23 <emeyer> Rossen: You could also have multiple overlapping higlights.
16:18:39 <jcraig> ack me
16:18:39 <Zakim> jcraig, you wanted to express preliminary support for Dan Clark's proposal, and mention the WebKit implementation with Apple platform accessibility APIs and attributed strings
16:19:21 <emeyer> jcraig: I’m new to this issue, but the Apple API used attributed strings.  We could do the same for selection ranges, I think.
16:19:27 <emeyer> s/used/uses/
16:19:34 <Rossen_> q?
16:19:43 <aaronlev> q+
16:19:44 <dandclark> q+
16:19:58 <emeyer> …I don’t have any particular concerns about the proposal.  I agree it would be better to put something in ARIA.  That would entail a complicated dance of adding new DOM elements.
16:20:20 <Rossen_> q?
16:20:27 <Jemma> +1 to jamesc
16:20:37 <Rossen_> ack aaronlev
16:20:50 <jcraig> s/ I agree it would be better to put something in ARIA/ I agree that Dan's API would be better to than to use something like ARIA here./
16:21:01 <emeyer> Aaronlev: I appreciate the simplicity of the current proposal.  It’s very useful to be able to overlap area.  Could potentially add problems we’ve had in ARIA annotations.
16:21:25 <Travis> aria-details="place to highlight?"
16:21:29 <emeyer> …imagine a document with multiple commented regions, where the regions overlap.  You can imagaine this would solve those problems.
16:21:40 <Rossen_> ack dandclark
16:22:04 <jcraig> s/We could do the same for selection ranges, I think./We already do the same for selection ranges like the native Find in Page feature./
16:22:08 <emeyer> Dandclark: Building on what James said, we’d been prototyping this in Chrome.  There are annotation types that can mark errors.
16:22:25 <Rossen_> q+
16:22:35 <emeyer> …I don’t know if that’s something that would go into ARIA mappings, but it does seem to fit into assistive tech platforms pretty well.
16:22:53 <jcraig> s/We already do the same for selection ranges /WebKit already does the same for selection ranges /
16:23:18 <emeyer> …In the meeting we had, from reviewing notes, the advnatage of having a set of supported types is that it allows things in the ATA platform to be represented in a first-class way.
16:23:44 <LisaSeemanKest_> agree
16:23:55 <emeyer> …If assistive tech becomes more powerful, if arbitrary strings are used, it limits the ability to make them first-class.
16:23:59 <janina> q?
16:24:23 <jcraig> +1 to  dandclark's comment about the benefits of keeping this as close as possible to the platform features
16:24:34 <emeyer> Rossen: Want to address where this work can and should be specified, where I mean the actual AT specification and any platform mapping that need to take place.
16:25:01 <emeyer> …Good candidate for CSSAAM.  What you’re proposing sound like a great first candidate.
16:25:09 <janina> q?
16:25:11 <LisaSeemanKest_> Im sorry I need to leave early. feel free to be in touch
16:25:42 <emeyer> …It also sounds like most feedback is positive from tech point of view, in terms of user enablement.  Since we have great experts here, what do you all think?  Is this good or great?  Are we missing something?
16:25:42 <janina> q?
16:26:00 <jcraig> ack Rossen_
16:26:11 <aaronlev> +1 for CSS-AAM. There are other uses for CSS-AAM IMO
16:26:16 <emeyer> Janina: I’m not an expert on implementation and AAMs, but not having anyone in queue seems to say this is reasonable.
16:26:18 <Travis> +1 for CSS-AAM
16:26:33 <emeyer> …If this is a reason to get a CSS-AAM started, great.
16:26:35 <jcraig> q+ to talk about whether CSS AAN is necessary for this
16:27:43 <emeyer> jcraig: An AAM may not be necessary.  This doesn’t seem like a terribly complicated API.  ARIA with AAM has a lot of cross-reference to other things on the web.
16:27:56 <Rossen_> ack jcraig
16:27:56 <Zakim> jcraig, you wanted to talk about whether CSS AAN is necessary for this
16:27:59 <janina> q?
16:28:05 <Rossen_> q+
16:28:09 <emeyer> …In that regard, I don’t see quite as much value in spinning up a document to reference just this one API when authors can probably deal without one.
16:28:15 <aaronlev> I recently filed an issue to develop rules to expose CSS cursor info to platforms that want it to allow ATs to use the info for heuristics
16:28:32 <emeyer> …If you do spin up, please make it a living document.  We’ve found AAM docs get out of date very quickly.
16:28:37 <jamesn> q+ to say we are moving all the ARIA AAMs to living standards with the new charter
16:28:44 <emeyer> Rossen: Point well taken.
16:29:05 <emeyer> …I challenge that this is an implementation detail in terms of how ranges and range types are supposed to be mapped.
16:29:27 <emeyer> …We want some level of consistency across various ATs.  Totally with you on this being a living document.
16:29:42 <jamesn> ack me
16:29:42 <Zakim> jamesn, you wanted to say we are moving all the ARIA AAMs to living standards with the new charter
16:30:20 <emeyer> …I’m hearing support from both sides, and am hearing support here.  In terms of CSS AAM, I propose we not spend time here and now.  We can take it to email.  once we have a resolution, we can resume the CSS AAM.
16:30:21 <jcraig> s/API when authors can probably deal without one./API when implementators probably don't need one. This strikes me as an implementation detail./
16:30:31 <emeyer> Janina: Sounds reasonable.
16:30:49 <emeyer> Rossen:  Excellent.  The next two issues: one is Ruby, one is scrollbars.
16:30:56 <rachelandrew> rachelandrew has joined #cssa11y
16:31:19 <emeyer> …One more was raised by Amy.  This is about MIT’s demonstration on video streams and analysis of Flash animation.
16:31:38 <Rossen_> Topic: Deep video-to-video transformations for accessibility with an application to photosensitivity
16:31:43 <emeyer> Janina: that’s mainly a heads-up where we can provide a tech solution to what’s long been a WCAG authoring guidelines.
16:32:29 <emeyer> …MIT has shown double-digit millisecond delay can allow the machine to block flashing and avoid killing people.  Should we trigger that via CSS or HTML?  Still being discussed.
16:32:31 <Rossen_> Document in reference: https://groups.csail.mit.edu/infolab/publications/Barbu-Deep-video-to-video-transformations.pdf
16:33:01 <tantek> tantek has joined #cssa11y
16:33:06 <tantek> present+
16:33:20 <Rossen_> q?
16:33:21 <emeyer> Rossen: I don’t have a firm opinion on how this might be exposed or implemented.  Anyone have a firm opinion?
16:33:50 <emeyer> Florian: Speaking of different issues, I’d like to not discuss the Ruby issue.  I don’t think it’s ben sufficiently discussed in the WG.
16:34:08 <emeyer> …The scrollbar issue is the last one before next stage, so I’d like to discuss that.
16:34:24 <emeyer> Rossen: I’d like to go back to the previous issue and alalow people to express opinions.
16:34:34 <emeyer> …I’ll take the silence as no opinions.
16:34:43 <emeyer> …Let’s go ahead to the scrollbar issue.
16:34:47 <janina> q?
16:34:54 <Rossen_> Topic: [css-scrollbars] Add wide value to scrollbar-width
16:34:54 <janina> zakim, who's here?
16:34:54 <Zakim> Present: MasakazuKitahara, Francis_Storr, Jennie, amy_c, Joshue, Rossen_, Aimee_U, jamesn, vmpstr, LisaSeemanKest_, alisonmaher, dandclark, jasonjgw, janina, chris, jfkthame, hdv,
16:34:58 <Zakim> ... kzms, Morgan, dbaron, r12a, florian, emeyer, ivan, SuzanneTaylor, jeff, aaronlev, Travis, miriam, fantasai, jcraig, Kim_patch_, Becky, jensimmons, dholbert, kirkwood, emilio,
16:34:58 <Zakim> ... JF, tantek
16:34:58 <Zakim> On IRC I see tantek, rachelandrew, smfr, JF, Leticia, myles, jensimmons, Jemma, kirkwood, BC, Tiger, emilio, Becky, dholbert, Kim_patch_, jcraig, miriam, Travis, florian, astearns,
16:35:02 <Zakim> ... Morgan, SuzanneTaylor, kzms2, hdv, jfkthame, r12a, janina, fantasai, alisonmaher, aaronlev, LisaSeemanKest_, jasonjgw, dbaron, jeff, jamesn, ivan, amy_c, Rossen_, Aimee_U,
16:35:02 <Zakim> ... Francis_Storr, Joshue108, Jennie, emeyer, MasakazuKitahara, Matthew_Atkinson_, vmpstr, dandclark, Zakim, RRSAgent
16:35:02 <Rossen_> github: https://github.com/w3c/csswg-drafts/issues/6351
16:35:04 <smfr> present+
16:35:17 <kirkwood> present+
16:35:19 <Travis> Topic: https://github.com/w3c/csswg-drafts/issues/6351
16:35:35 <emeyer> Florian: Two varying degrees based on the platform and browser.  You may have the ability to change the scrollbar.  This is not about that.
16:36:12 <emeyer> …Besides user preferences, we see many web sites that want to change scrollbars in certain contecxts, like narrow scrollbars in a dropdown menu.
16:36:35 <janina> q?
16:36:36 <emeyer> …CSS WG wanted to introduce a property with values ‘auto’ and ‘thin’.
16:36:37 <myles> present+ myles
16:36:45 <emilio> there's a third value (though not relevant to this conversation), which is 'none'
16:37:02 <Rossen_> q-
16:37:06 <janina> q+
16:37:09 <emeyer> …Because CSS also has user overrides in form of user.css etc., if the user doesn’t want this, they can override.
16:37:10 <JF> Q+
16:38:14 <emeyer> …We considered whether sites should be able to make scrollbars wider, but the WG concluded that users should be able to make scrollbars bigger, but that’s a UI setting.  There’s no need for authors to be able to make scrollbars wider.
16:38:42 <emeyer> …We resolved that ‘auto’ and ‘thin’ was all we needed, but not everyone is convinced.
16:39:05 <ivan> ivan has left #cssa11y
16:39:13 <emeyer> …It’s not clear to me whether the ‘wide’ value should make a ‘thin’ scrollbar normal width, or if it would make a wider-than-usual scrollbar.
16:39:26 <tantek> q?
16:39:28 <tantek> q+
16:39:33 <emeyer> …WG still thinks this isn’t needed, because we believe that need is addressed differently.
16:39:46 <emeyer> …We believe we’ve made a compelling case, but we want to discuss.
16:39:53 <Rossen_> ack janina
16:40:15 <emeyer> Janina: Maybe a specific feature in a page needs a wider scrollbar.  That may change our view.  Anyone from APA want to talk to this?
16:40:36 <Rossen_> ack JF
16:41:03 <emeyer> JF: “Author proposes, user disposes”.  A ‘thin’ value is making a decision for the user.  The user may not agree or be able to use that.
16:41:14 <emilio> q+
16:41:15 <florian> q+
16:41:19 <emeyer> …Why wouldn’t a low-vision user be able to say “I want ALL scrollbars to be thick”?
16:41:33 <janina> q?
16:41:42 <emeyer> …It seems to me the obvious choice to have the opposite of ‘thin’ and ‘thick’.
16:41:53 <jyasskin> jyasskin has joined #cssa11y
16:42:18 <emeyer> Rossen: This is a very pointed, quick question: what is it you want from this discussion?
16:42:30 <emeyer> Florian: I’m looking for a reason to close or continue.
16:43:27 <Rossen_> q?
16:43:36 <Rossen_> ack florian
16:43:45 <JF> Q+
16:43:48 <emeyer> …Response to JF: should user be able to make scrollbars thin?  They can already do that.  They can block authors from making any scrollbar thin.  In addition, should the user be allowed to make wider scrollbar?  Yes, but not through CSS.  it should be done through customization elsewhere.
16:44:09 <emeyer> …’auto’ will make scrollbars as the system is configured: thinner, wider, normal, whatever.
16:44:15 <jcraig> rrsagent, make minutes
16:44:15 <RRSAgent> I have made the request to generate https://www.w3.org/2021/10/20-cssa11y-minutes.html jcraig
16:44:33 <emeyer> JF: You keep talking about the author.
16:44:59 <emeyer> Florian: I’m talking about the user.  They can override all author scrollbars, and use their system to widen all scrollbars.
16:45:30 <emeyer> …From a user point of view, we’ve served the need for users to be able to override authors.  Why do users need to use CSS to make things wider?
16:45:46 <astearns> put another way, 'auto' lets the user set all scrollbars to their preferred system setting
16:46:03 <emeyer> JF: Again, I don’t understand the hesitancy to add another value.
16:46:21 <tantek> hesitancy is because there is no documented *developer* use-case need for "wide", so there is no desire to take-up that cost (of specification, implementation, testing, compat, etc.)
16:46:22 <emeyer> …Are you saying we’re going to have browser settings for scrollbars?
16:47:21 <emeyer> tantek: First, I 100% agree with user use cases that JF and Janina have described.  The current solution seems to address them.  It may be confusingly named.
16:47:58 <Rossen_> q?
16:48:00 <emeyer> …If you’d asked us that 10-15 years ago, the WG would have agreed.  But one thing we’ve learned to do is not add anything that doesn’t have a demonstrated developer use case.
16:48:02 <Rossen_> ack tantek
16:48:53 <emeyer> …As long as we’re preserving user intent, that’s sufficient.  All user preferences can be contained within the ‘auto’ value.  With ‘wide’ developers could mess with user preference.
16:49:40 <Rossen_> ack emeyer
16:49:43 <Rossen_> ack emilio
16:50:11 <emeyer> emilio: Concrete example: there are Windows settings that let you set scrollbar width.  You can set them there.  ‘auto’ would then yield wide screenbars.
16:50:42 <tantek> q?
16:50:43 <emeyer> …Adding this ‘wide’ value to CSS doesn’t make sense because authors don’t have a user case for it.  Users do.
16:51:03 <Rossen_> ack JF
16:51:18 <Rossen_> q+
16:51:31 <LouisMaher> LouisMaher has joined #cssa11y
16:51:45 <Rossen_> q- later
16:52:30 <emeyer> JF: Couple of things.  1, we may not be able to come up with author use case, but users have a use case.  The fact that I can fix this in OS settings, okay, but at some point we want to make this easy for the user as well.  I can see users wanting to use a ‘wide’ value.  To withhold this because the OS can address this strikes me as weak.  This feels like separaating the needs form the solutions.
16:52:55 <emeyer> Emilio: You can definitely configure the browser to ignore the OS settings.  In Firefox you can already do that with advanced settings.
16:53:06 <LouisMaher> rrsagent, point
16:53:06 <RRSAgent> I'm logging. I don't understand 'point', LouisMaher.  Try /msg RRSAgent help
16:53:21 <florian> q+
16:53:28 <tantek> No disagreement on the user use case JF.
16:53:29 <Rossen_> ack fantasai
16:54:01 <emeyer> fantasai: I want to re-emphasize the point that the property is a way for authors to say what they want in a scrollbar.  It’s not a way for users to do that.  A CSS property isn’t necessary for this for users because users in general aren’t writing CSS.
16:54:26 <Rossen_> ack Rossen_
16:54:28 <Rossen_> aack florian
16:54:31 <Rossen_> ack florian
16:55:06 <janina> q?
16:55:07 <emeyer> Florian: I feel like we’re not quite hearing each other.  I hear some saying it’s important to let users set scrollbars wide.  They already can, as ‘auto’ will allow users to override authors with whatever their system is set to provide.
16:55:15 <Rossen_> Zakim, close queue
16:55:15 <Zakim> ok, Rossen_, the speaker queue is closed
16:55:26 <janina> q+
16:56:12 <Rossen_> q?
16:56:17 <emeyer> …It’s desirable that an easy UI lets users configure this, but that’s outside the scope of CSS.  For users, we’re covered.  We need something for authors to give hints.
16:56:36 <emilio> To be extra concrete, on Firefox: `about:config` -> `widget.non-native-theme.win.scrollbar.use-system-size=false` -> `widget.non-native-theme.scrollbar.size=<whatever>`
16:56:37 <emeyer> Janina: Renaming may be a good path forward.
16:57:13 <emeyer> Rossen: The CSS WG is trying to move forward and publish this.  It’s work that enables a lot of functionality.
16:57:23 <tantek> Perhaps it would be good to add some advisory text to the spec for users who want wider or default scrollbars to use 'scrollbar-width:auto'
16:57:36 <emeyer> Janina: I don’t think we can resolve here, but we can discuss whether we want to keep debating or resolve.
16:57:47 <florian> +1 to tantek
16:57:49 <tantek> If it's causing this much confusion among experts here, it's worth clarifying in the spec
16:58:08 <emeyer> Rossen: We went in circles a few times here.  Can we make this more actionable?  Perhapas some of the CSS WG could cross over to the APA WG call?
16:58:26 <emeyer> Amy: Thank you for everyone explaining, it really helped understand where the WG is coming from and what’s meant.
16:58:36 <Matthew_Atkinson_> present+
16:58:54 <Matthew_Atkinson_> +1 to Amy; this was really helpful, thanks.
16:59:45 <emeyer> Janina: Want to thank Amy_c for all her help with APA, sad we can’t pay enough to keep you.  And we’re looking for a new liason.
16:59:55 <emeyer> Amy: APA is really good to work with.
16:59:55 <JF> +1 to Tantek re: more clarification
17:00:23 <tantek> ^ it looks like we're close to a resolution
17:00:37 <emeyer> Rossen: Couldn’t agree more.  Want to express appreciation for everyone hanging with us and working through these things.
17:01:39 <tantek> PROPOSED: Add advisory spec text to 'scrollbar-width' noting that for users who want wider or default scrollbars to use 'scrollbar-width:auto' in their user style sheet
17:01:47 <emeyer> Janina: thanks to everyone from APA, CSS, and other groups for being here.  Looking forward to moving this forward in the future, will make the scrollbar our top issue when we return to work in November.
17:02:12 <emeyer> rrsagent, make logs public
17:02:24 <Travis> +1 thanks emeyer
17:02:41 <RRSAgent> I have made the request to generate https://www.w3.org/2021/10/20-cssa11y-minutes.html fantasai
17:03:21 <janina> Thanks!
17:04:18 <emeyer> Thanks for the minutes generation, @fantasai!  (I should’ve realized I probably didn’t have that power.)
17:06:49 <fantasai> emeyer, you definitely have that power
17:06:58 <fantasai> emeyer, you just need to type it out just like I did :)
17:07:08 <emeyer> Oh, I used the wrong command.  Got it.  Thanks!
17:07:15 <fantasai> hahah, no there's two commands here
17:07:22 <Travis> I just heard the He-Man yell: I have the power!!!!
17:07:24 <fantasai> one is to control the access-control on the logs (make them public)
17:07:38 <fantasai> the other is to generate the minutes from the IRC log
17:08:02 <fantasai> Some meetings are Member-only, so iirc RRSAgent defaults to that setting
17:08:32 <florian> I think you no longer need the "v2" part of the command, I think it's the default now.
17:08:40 <fantasai> \^_^/
17:42:11 <emeyer> emeyer has joined #cssa11y
18:41:09 <tantek> present+
18:41:17 <RRSAgent> I have made the request to generate https://www.w3.org/2021/10/20-cssa11y-minutes.html tantek
18:41:53 <tantek> present+ emilio,florian
18:43:12 <tantek> present+ dbaron,jcraig
18:43:19 <RRSAgent> I have made the request to generate https://www.w3.org/2021/10/20-cssa11y-minutes.html tantek
18:54:23 <emeyer> emeyer has joined #cssa11y
19:21:39 <SuzanneTaylor> SuzanneTaylor has joined #cssa11y
19:24:45 <dbaron> dbaron has left #cssa11y
20:02:07 <JF> JF has left #cssa11y
20:31:26 <emeyer> emeyer has left #cssa11y
20:46:44 <jensimmons> jensimmons has joined #cssa11y
21:43:25 <janina> janina has left #cssa11y
23:53:22 <SuzanneTaylor> SuzanneTaylor has joined #cssa11y
23:59:30 <jeff> jeff has joined #cssa11y