- From: Sebastian Zartner via GitHub <sysbot+gh@w3.org>
- Date: Sat, 18 Jun 2022 22:26:56 +0000
- To: public-css-archive@w3.org
> > Defer color-contrast() until WCAG3 is stable and then default to it > > A drawback with that approach is the length of time to get _all_ of WCAG 3 stable, when > > a) we only need one small part of it b) that part [isn't even normatively referenced](https://github.com/w3c/silver/issues/640) at present I guess it would be enough to have that part be stable, right? And it looks like with the [changes you referred to](https://github.com/w3c/silver/pull/630), it gets properly referenced soon. Anyway, I just wanted to mention this option as it is a possible solution. If it requires the whole WCAG 3.0 spec. to be stable, then it's probably not the best choice to wait for it. Sebastian -- GitHub Notification of comment by SebastianZ Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7361#issuecomment-1159575379 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 18 June 2022 22:26:57 UTC