- From: Amelia Bellamy-Royds via GitHub <sysbot+gh@w3.org>
- Date: Thu, 27 Aug 2020 18:17:59 +0000
- To: public-css-archive@w3.org
During yesterday's teleconference, there was a lot of discussion among group members about how important it was to have normative text about which parts of the form element should get the accent or contrasting color. There was a lot of concern (on the call & in this discussion) about whether authors would use the property at all without assurances of consistent appearance. I threw up a quick Twitter poll to gauge author reactions. Thanks for those of you who retweeted, although caveat that my own followers have a larger than average share of web accessibility devs. About 1 in 13 respondents said that current native HTML form elements are good enough for them. Of the remainder, half said they need more complete styling than just changing colors. And the rest were evenly divided between whether they would only use this property if it was consistent cross browser vs whether they were OK with variations to match native styling. [The tweet and results](https://twitter.com/AmeliasBrain/status/1298656779274825728) were: > If CSS added a property that allows you to tweak native form elements (checkboxes, select, etc.) to use one or more colours you specify, would you use that? > > Or would you still need to fully customize? > > Would it matter if results looked different between browsers? > > - **46.5%** no, I need full styling > - **22.9%** only if all browsers same > - **22.9%** color-tweaked native = 💯 > - **7.6%** unstyled forms are fine > > 419 votes · Final results -- GitHub Notification of comment by AmeliaBR Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5187#issuecomment-682112201 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 27 August 2020 18:18:01 UTC