- From: Alastair Campbell via GitHub <sysbot+gh@w3.org>
- Date: Thu, 16 Jun 2022 10:47:59 +0000
- To: public-css-archive@w3.org
I would suggest D as well. From my personal experience (accessibility testing websites, including with users with low-vision, but not a colour expert) the current WCAG 2 formula does catch a lot of poor colour combinations. A lot of combinations which possibly should fail (but don't) are not attractive and tend not to be used anyway. The dark-mode aspect is concerning. The bottom line from a WCAG point of view is that there needs to be some specific user-research done to ensure we have a solid footing for WCAG 3. In the meantime, I would definitely want to avoid a situation where the results of contrast-contrast change with a browser update, or are different between browsers. Alastair (Co-chair of AGWG) -- GitHub Notification of comment by alastc Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7361#issuecomment-1157516429 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 16 June 2022 10:48:00 UTC