Re: [csswg-drafts] [css-ui] Consider removing slider-horizontal from <compat-auto> (#8506)

The CSS Working Group just discussed `[css-ui] Consider removing slider-horizontal from <compat-auto>`, and agreed to the following:

* `RESOLVED: remove slider-horizontal, square-button, and push-button from <compat-auto>; PaulG will open an issue about ARIA roles and concerns about slider-vertical and push-button`

<details><summary>The full IRC log of that discussion</summary>
&lt;emeyer> emilio: Firefox never supported this<br>
&lt;emeyer> …Recently, I found three keywords where there are problems in WPT<br>
&lt;emeyer> …Usage is pretty low<br>
&lt;emeyer> …We also have no compat issues about this<br>
&lt;masonf> q?<br>
&lt;masonf> q+<br>
&lt;astearns> ack masonf<br>
&lt;emeyer> masonf: We don’t object to this<br>
&lt;emeyer> astearns: What are we resolving?<br>
&lt;emeyer> emilio: Drop slider-horizontal, square-button, and push-button<br>
&lt;PaulG> q+<br>
&lt;astearns> ack PaulG<br>
&lt;emeyer> PaulG: slider-vertical has native semantics around orientation<br>
&lt;emeyer> …If there is usage, we should communicate that ARIA values need to be used<br>
&lt;masonf> q?<br>
&lt;emeyer> emilio: Right now, the spec says it does nothing special<br>
&lt;emeyer> dbaron: I don’t think there a history of appearance changing accessibility rules, is there?<br>
&lt;emeyer> PaulG: In Chromium, (scribe got lost)<br>
&lt;emeyer> dbaron: I don’t think the CSS `appearance` property affect accessibility<br>
&lt;emeyer> PaulG: I’m looking at the demo in the issue, in Chromium, the vertical slider renders with orientation: vertical that nothing else set<br>
&lt;emeyer> dbaron: That’s surprising to me<br>
&lt;dbaron> masonf: me too (but confirm it)<br>
&lt;bkardell_> Is it bad? Seems good?<br>
&lt;emeyer> PaulG: Concern is if it’s dropped, anyone depending on that orientation needs to know they need to replace that with ARIA<br>
&lt;dbaron> s/rules/roles/<br>
&lt;emeyer> astearns: Given that usage is very low, is this a big concern?<br>
&lt;emeyer> PaulG: This is in no way a reason to stop, but this is a concern APA will probably voice<br>
&lt;masonf> q?<br>
&lt;emeyer> …I’m guessing where this is used, understanding of accessibility is low<br>
&lt;emeyer> …I’ll help smooth that over with APA, I’d just like numbers<br>
&lt;emeyer> masonf: We’re speaking just about slider-horizontal, yes?  Not slider-vertical<br>
&lt;emeyer> …Is it an accessibility problem for horizontal?<br>
&lt;emeyer> PaulG: No, only concerned with vertical and that semantic meanings are conveyed in other ways<br>
&lt;emeyer> masonf: We should open an issue about vertical<br>
&lt;emeyer> …I think we’re okay horizontal, but need to discuss more about vertical<br>
&lt;emeyer> astearns: So proposed resolution is to remove slider-horizontal, square-button, and push-button<br>
&lt;emeyer> PaulG: I might need to check push-button<br>
&lt;emeyer> …Does ARIA pressed get added?<br>
&lt;emeyer> astearns: What if we resolve to do the removal, then Paul, can you open an issue on slider-vertical and push-button on possible ARIA concerns?<br>
&lt;emeyer> PaulG: Yes<br>
&lt;dbaron> https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/modules/accessibility/ax_slider.cc;l=47-83;drc=5a252fef36aced8857912a7eba43dad5590cb54d<br>
&lt;emeyer> RESOLVED: remove slider-horizontal, square-button, and push-button from &lt;compat-auto>; PaulG will open an issue about ARIA roles and concerns about slider-vertical and push-button<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8506#issuecomment-1515062326 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 19 April 2023 16:51:59 UTC