- From: Tim Nguyen via GitHub <noreply@w3.org>
- Date: Mon, 14 Jul 2025 22:00:00 +0000
- To: public-css-archive@w3.org
@aardrian These design principles were specifically about `appearance: base` default styles, nothing else. I don't know if that was clear from the spec, but if not, we should clarify that. I agree "100%" isn't doing service here, especially since the design principles are sometimes applied in different orders of importance (with a different principle sometimes contradicting with the accessibility one). I believe the original aim of this principle when we originally thought it out at Apple was to say that developers should be able to use a form control with `appearance: base` (and nothing else) without worrying about accessibility because accessibility comes out of the box. But yeah, it's probably idealistic and not a good message to give developers to say that they don't need to think about it. The principles in general were meant to be strongly worded (e.g. no conditional), to make sure we address underlying issues are addressed. Perhaps it's better to word it differently: > The controls are accessible out of the box in default configurations, aiming to pass WCAG 2.2 AA standards. and perhaps add a normative note about accessibility: > NOTE: Authors may need to do extra adjustments to ensure their controls are accessible depending on the context the form control is placed into. The basic appearance does not prevent adjustments by the author that are inaccessible. (or something among those lines) cc @fantasai -- GitHub Notification of comment by nt1m Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12480#issuecomment-3071164861 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 14 July 2025 22:00:01 UTC