- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Thu, 02 Dec 2021 00:45:56 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `some scrollbars aren't accessible`, and agreed to the following: * `RESOLVED: Change SHOULD to MUST in the normative text about UAs ensuring the scrollbars are wide enough to interact with` <details><summary>The full IRC log of that discussion</summary> <TabAtkins> Topic: some scrollbars aren't accessible<br> <TabAtkins> github: https://github.com/w3c/csswg-drafts/issues/6675<br> <TabAtkins> Rossen_: do we need Greg?<br> <TabAtkins> florian: I'll try.<br> <TabAtkins> florian: two parts to the issue<br> <TabAtkins> florian: some people complain that scrollbars found on the web were weird or unusable<br> <TabAtkins> florian: Those were ::-webkit-scrollbar, not thru our specced properties<br> <TabAtkins> florian: The spec doesn't need to write about how to use those, since we consider them to not exist<br> <TabAtkins> florian: the part we do need to talk about is that the spec currently says that narrow scrollbars "should remain wide enough to be usable". Greg says this should be a MUST.<br> <TabAtkins> florian: At least, when the user begins interacting.<br> <TabAtkins> florian: I'd skip that last part, because we're not really specifying that the narrow scrollbar has a dynamic width; browsers can do whatever.<br> <TabAtkins> florian: But going from "should be usable" to "must be usable"... why not? Not sure it's enforceable, but a browser deciding its narrow scrollbars don't need to be usable would be odd.<br> <flackr> q+<br> <TabAtkins> florian: WCAG, note, says that the minimum size to be interacted with is 40px, and wide scrollbars aren't ever anywhere near that, so what it means to be "wide enough to be interacted with" seems difficult to understand<br> <TabAtkins> florian: for overlay scrollbars, having them dynamically change size is fine, but layout scrollbars you probably don't; I don't think we should exclude it tho.<br> <TabAtkins> Rossen_: Just moving the SHOULD to MUST and leaving the text otherwise the same makes sense<br> <Rossen_> ack flackr<br> <TabAtkins> flackr: I raised this in OpenUI - even if the scrollbar isn't visually large enough, we do "fuzz" touches on buttons, and could do the same thing for the scrollbar, so as long as your finger touches near the scrollbar it considers you to be touching it<br> <TabAtkins> flackr: I think it should be a reasonable way to have a narrow scrollbar that's still usable<br> <TabAtkins> florian: Perhaps we can include this in a note - if you're overlay, feel free to enlarge it on hover; if not, maybe fuzz hit testing. Nothing normative, just suggestions<br> <TabAtkins> Rossen_: Stepping back, from pure a11y, the change makes sense.<br> <TabAtkins> Rossen_: Said many times - we shouldn't be specifying how the UI frameworks should work.<br> <TabAtkins> Rossen_: But if we've already gone to the extend of adding normative text about "scrollbar width must be large enough", changing that to a MUST makes sense<br> <TabAtkins> +1<br> <TabAtkins> Rossen_: Objections?<br> <TabAtkins> RESOLVED: Change SHOULD to MUST in the normative text about UAs ensuring the scrollbars are wide enough to interact with<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6675#issuecomment-984189166 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 2 December 2021 00:45:59 UTC