GitShow/tmcw/wcag-contrast
tmcw

wcag-contrast

WCAG contrast ratio measurement and scoring

by tmcw
Star on GitHubForknpm

JavaScript

130 stars7 forks5 contributorsQuiet · 6y agoSince 2013BSD-2-Clause

Meet the team

See all 5 on GitHub →
tmcw
tmcw49 contributions
greenkeeper[bot]Bot
greenkeeper[bot]27 contributions
davidpett
davidpett7 contributions
paulcpederson
paulcpederson1 contribution
RobbieTheWagner
RobbieTheWagner1 contribution

Languages

View on GitHub →
JavaScript100%

Commit activity

Last 12 weeks · 0 commits

Full graph →

Community health

2 of 6 standards met

Community profile →
42
✓README✓License○Contributing○Code of Conduct○Issue Template○PR Template

Recent PRs & issues

Quiet · 1 in progress · Last activity 6y ago
See all on GitHub →
Myndex
Vers 3.0, comments RE: perceptual uniformity, and WCAG 3 & APCAOpenIssue

Hi Tom, I just happened upon your site, and read this on the readme: _I (personally, speaking as Tom) have doubts about the universality, accuracy, and application of this particular standard. High contrast is a good value, but I argue that the standard is over-strict and doesn't precisely match human perception._ Regarding WCAG 2.x contrast, you are correct: it is not perceptually uniform nor accurate. And you're not the first to notice. Circa April 2019 I started a thread on W3 WCAG GitHub pointing out that _"um... this is the wrong math..."_ and that any standard dependent on that math is therefore somewhat meaningless. As a result, this led me to the multi-year research project that created ACPA, the Advanced Perceptual Contrast Algorithm. _APCA is the method we are using for the emerging WCAG 3.0_ APCA is perceptually uniform and accurate, processes reverse polarity differently than for normal (dark text on light), and takes into account other psychophysical attributes like spatial frequency (i.e. small thin fonts). You might be interested in clicking "research mode" at the SAPC live demonstrator site, it has some interactive experiments that demonstrate some of the concepts. I also saw on your blog post: Compliance with A should be the first step Here's a funny thing, there is literally no contrast requirement for A. None whatsoever. And like I said, the issues with WCAG 2 contrast are well known, hence my involvement in creating the fix. One other thing (the actual issue) The actual reason I stumbled by was I saw this code listed as a dependency listed as "wcag-contrast 3.0.0" and then saw that it was released about the time we created a first editor's draft of WCAG 3.0, so for a moment I thought you were using the new APCA, but in fact your code is still using the WCAG 2 math. So.... I am concerned about confusion as WCAG 3 does not use the WCAG 2 method at all. My concern is if someone wants the WCAG contrast and they see yours at version 3.0.0 they might wrongly think that it is the new APCA method, which is incompatible as it is a new science based paradigm. Here are links to brief comparisons of WCAG 2 and APCA. Part I:Orange You Wondering About Contrast? Answering some contrast questions, and demonstrating a real solution to the infamous orange conundrum. Part II:The Lighter Side of Dark Backgrounds An article comparing some parts of APCA with the old WCAG 2 contrast methods. Part III: WCAG 2 vs APCA Contrast Shootout** Answering some recent questions regarding APCA, and comparisons and examples of the old (WCAG 2 1.4.3) and the new WCAG 3 with APCA. Thank you! Andy _Andrew Somers_ _W3 AGWG Invited Expert_ _Senior Color Science Researcher_ _Myndex Perception Research_ _Inventor of APCA_ THE REVOLUTION WILL BE READABLE™

Myndex · 4y ago

Recent fixes

View closed PRs →
RobbieTheWagner
Support AA Large and FailMergedPR

This adds from 3-4.5 and returns when under 3 now. The empty string I think could be misconstrued as an error, since the output is not explicit.

RobbieTheWagner · 6y ago
mattdesl
Cannot read property 'startsWith' of undefinedClosedIssue

Getting this error when trying to use this library via browserify/frontend. I'm in latest Chrome so it does support string , my first guess is that the problem lies with which is an unusual and non-standard way of bundling up modules (I've run into the same problem with before in other modules).

mattdesl · 7y ago
tmcw
chore(package): update documentation to version 10.1.0MergedPR

Closes #53

tmcw · 7y ago
Structured data for AI agents

Repository: tmcw/wcag-contrast. Description: WCAG contrast ratio measurement and scoring Stars: 130, Forks: 7. Primary language: JavaScript. Languages: JavaScript (100%). License: BSD-2-Clause. Open PRs: 1, open issues: 1. Last activity: 6y ago. Community health: 42%. Top contributors: tmcw, greenkeeper[bot], davidpett, paulcpederson, RobbieTheWagner.

·@ofershap

Replace github.com with gitshow.dev