- From: Andrew Somers via GitHub <sysbot+gh@w3.org>
- Date: Sun, 19 Jun 2022 07:35:47 +0000
- To: public-css-archive@w3.org
Hi Lea @LeaVerou
> .... _as well as to satisfy legal constraints....WCAG 2.1 contrast ... is legally mandated that websites pass it._
Legally mandated is a strong term for the narrow areas where there is actual codification into law.
In the USA, the ADA does not mandate WCAG 2 contrast (indeed, the native ADA signage regulations were gutted of any specific contrast guidance regarding architectural signage some time ago). For government sites and government procurement, the 508 rules **_do_** specify WCAG 2 contrast, but with **two big exception clauses:**
**1. Commercially available.** If something is needed but no commercially available solution is WCAG 2 compliant, it does not have to comply.
**2. Alternate method.** An alternate method can be used so long as it provides for equivalent or better accessibility.
As for case law, the 11th circuit vacated Winn-Dixie in February, so that is moot.
Above is federal level. For state level there is _mainly_ New York and California. I don't have Lexus Nexus access at the moment, but from what Ive seen, no cases relating to contrast have gone to trial and won on merits. Most are out of court settlements, and I'm going to guess many of these _were_ relying on Winn-Dixie.
For other nations it's a grab bag, but in nearly all cases the specification of WCAG 2 is limited to governmentally controlled entities or sites. An exception is Finland. In Australia it extends to non-governmental sites, but last I checked it was level A only, so contrast is not included. In Canada, there is some case law, but a number of exclusions.
> _....we may want color-contrast() to find us a color pair that both satisfies WCAG 2.1, as well as the new improved algorithm._
I'd like to introduce you to Bridge-PCA. It is fully backwards compatible to WCAG 2 but using APCA technology, it fixes the problem of false passes. What is lost is the greater design flexibility of the full APCA guidelines. Bridge-PCA was created specifically to answer the question of "meeting legal obligations by the absolute letter of WCAG 2, regardless of actual veracity".
I do not suggest Bridge PCA as a permanent solution—it is specifically a stop-gap, stepping-stone to address various concerns. It does a much better job calculating for dark mode for instance, and also has enhanced conformance levels. The npm package is:
npm i bridge-pca
And the demo tool is https://www.myndex.com/BPCA/
--
GitHub Notification of comment by Myndex
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7357#issuecomment-1159641406 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 19 June 2022 07:35:49 UTC