Re: [csswg-drafts] [css-color-5] Make it easier for authors to select the right WCAG level in color-contrast() (#6319)

> _There is a lot to pick apart in that response, which in general is very handwavy and poorly defined, but this is not the place for it._

Hi Chris @svgeesus 

I'm concerned you find my reply "handwavy" though to be sure, I'm not quite ready to "defend my thesis" — mainly I wanted to address the statement regarding colorspaces, as that flexibility has always been a consideration, and there is substantial due diligence behind this project.

> _However, this issue is about making it easier to select the correct WCAG 2.1 contrast._

Understood, I simply saw some of your concerns in your reply to Michael, and I wanted to address them and mention the background/basis for some of the work.

> _If WCAG 3.0 starts to nail down the new contrast algorithm such that it is adequately documented, widely reviewed, and multiply implementable then we could revisit to select the right level (which apparently would need the font size, and some indication of how serify the font is, and a bunch of other as-yet poorly defined criteria)._

There is documentation, white papers, and other discussion up on my site, GitHub, W3, and elsewhere, as well as some informal reviews, though this is certainly a work in progress. Font definition related methods are part of the plan for next year.

Nevertheless, APCA does not require anything regarding the font, as far as returning the L<sup>c</sup> value. The font recommendation is separated, in part to facilitate use with other languages, which use different glyphs / logograms etc.

There is a lot of new activity in the newly re-born Low Vision Task Force, but I was planning on reaching out later and more formerly once the key paper is close to ready... Covid slowed some of the empirical study sadly, but getting moving again.....


Thank you,

Andy


-- 
GitHub Notification of comment by Myndex
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6319#issuecomment-911584010 using your GitHub account


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

Received on Thursday, 2 September 2021 11:50:29 UTC