For years I have seen people, teams, products, organizations, and projects promoting APCA contrast as the WCAG3 color contrast algorithm. In many of those cases, those same actors have suggested dismissing the contrast algorithm in WCAG2.
This kind of problematic advice happened so often that I started filing issues with tool makers to remove APCA, as with this May 2024 Chromium issue.
In January 2025 I saw a post promoting that advice, which would create legal risk for anyone following it. You can see my original 2025 response on Mastodon and the same post on Bluesky, where the creator of APCA also weighed in. Read those to ensure you aren’t just taking my word for it.
Current Situation
Here is the most current (as of this writing) contrast ratio algorithm in WCAG3 with the salient bit highlighted:
contrast ratio test Exploratory
meeting a sufficient level of contrast between two colors using the relationship of hue, saturation, and lightness values
Editor’s note
The contrast algorithm used in WCAG 3 is yet to be determined.
APCA was marked for removal in early 2023:
Exploratory content that does not gain WG support to proceed to the next stage within 6 months is automatically removed in the WCAG 3 development process. We still hope the promising contrast work will continue to mature for potential later inclusion.
As with other WCAG3 ideas that did not get working group support, the working group pulled it from the July 2023 WCAG3 working draft. APCA was only ever exploratory, and the W3C’s July 2023 update explained removal of exploratory items. The APCA creator’s response to Michael Cooper’s comment acknowledged that APCA versions in the draft were all early versions that were very obsolete (emphasis theirs).
I have no idea if APCA, whatever version, will come back to WCAG3.
What to Do?
You can still use APCA (whatever version). If you do, limit your risk by taking one of these approaches:
Choose colors that also conform to WCAG2 contrast requirements; or
If you pick colors that fail WCAG2 contrast requirements, document it and have a ready response should you receive a drive-by lawsuit from a bad actor using an automated checker to find a contrast violation (assuming your attorney lets you do this).
I am still not a (bird) lawyer.
In the meantime, WCAG3 is years away from being done, perhaps 2030 at the soonest. Any contrast algorithm it picks won’t be final until at least then. But if you like whatever is proposed and want to use it before 2030, then probably refer to my two approaches above.
Hey, Alphabet or Google or Chrome or whomever in that illegal monopoly continues to release things to the web platform that are full of accessibility barriers, I have what I think is a straightforward request.
My Request
Please, if your team cannot explain how the thing satisfies all WCAG Success Criteria at Level AA, then don’t release the thing.
If the thing is a new feature for the web platform (HTML, CSS, ARIA, SVG, etc.), then don’t even propose the thing until you have its WCAG conformance sorted.
Then understand WCAG is the bare minimum, is only table stakes, and does not in itself guarantee the thing is accessible. Which means be prepared for the thing to still contain barriers that must be addressed before it goes any further. Which means you’ll field some questions.
Blowback
I’ll run with two examples lead by Google in the web platform standards world, one older and one recent.
In late 2024, doing an end-run around the HTML spec and the concept of separation of concerns, Google drove carousels in the CSS Working Group. Then accessibility experts got wind of it and weighed in (more than just the once), only to get no traction.
Both of these book-end five years of a consistent experience for me (15 years based on posts linked below). Accessibility experts and disabled users (and the wonderful overlap of both groups) are not consulted at the start. Not in the scoping, not in the research, and not even in traditional shift-left-but-not-left-enough design phase.
Instead, we stumble across these things. We raise alarms or concerns or questions and are seen as buzzkills. Fun police. Hindrance to progress. We flag barriers and are ignored or dismissed or even harassed. And when the project inevitably catches fire, despite claims accessibility is baked in or the assertion it’s only a beta, we are told we didn’t weigh in early enough. We didn’t donate enough time. We didn’t participate in whatever opaque process in our copious free time.
Of course, ableism makes it easy to forget that accessibility experts and disabled users are already under a constant DDoS attack for our attention, never mind dealing with a US federal government that wants us to go away. I know I said I’m good at being a party-pooper, but I don’t want to be. It’s draining. And frankly, Google, it’s your fault (though not yours alone).
Google launched Designcember to promote its work on container queries and other technologies, but failed to support its own developers to ensure the site is accessible. Which I called out. And for which my free labor was requested to QA its fixes, but I did turn it into a teachable moment.
Google Chrome’s developer outreach site, Web.dev, shared how to build an accessible <tool-tip> custom element. If you followed its advice you were guaranteed a SC 1.4.13 WCAG violation. Never mind translation issues, misunderstanding of how <abbr> is exposed, a conflation of accessible name and description, and an enforced inability to select text. 2½ years on, other than moving my bug report to a new tracker, neither Google overall nor the author has made any effort to fix it.
Google has updated Material Design to “Expressive” and, in a repeat of its tendency for confirmation bias with Material UI efforts, seems to again engage in lackluster research.
Using Open-UI as a vehicle for “spitballing,” Google suggests using menus for navigation, for which I am thankfully able to jump in and throw warnings, including references to material that Google should have uncovered in the barest due diligence. I grump about this on the socials.
Google releases its AI Edge Gallery native app for Android, which allows users to generate image descriptions, transcripts, and more, but does so without any support for TalkBack. As Devin Prater points out, Google knew about this 3½ months ago and did nothing.
Wrap-up
Do you work for the company that formerly claimed it wouldn’t do evil? It sucks if you take this as a personal attack. It’s not. Your employer is simply doing a terrible job of supporting you in your efforts to support disabled users. If you want to be angry or frustrated, be angry or frustrated at the multi-billion dollar company that keeps throwing up barriers instead of spending a negligible amount of money to get experts and users involved.
It’s a paycheck that puts food on the table. I get that. Take its money and do what you can.
If you work for not-Google, like, say, Apple or Microsoft or Meta or Adobe or whatever, don’t be smug. If I had the energy I could take all of your employers to task for similar, egregious violations of user trust.
I did this rant in only one thousand and seven words!
Eric Bailey made a point about conference-driven development, essentially rushing broken or half-baked features out the door so the megacorp would have something to reveal on stage.
I think he was right. On 21 May, CSS carousels featured at Google I/O. The comparison example was Elementor, which ignores the more compelling question (to me) of why Elementor needed 165kb of JavaScript for a carousel. It also ignores the very real risk of WCAG violations and the larger question of why Elementor would make such profound claims when only one browser supports the feature.
Also consider the follow-on comment from the Google presenter, that the CSSWG is already looking ahead to exploring things like bringing your own custom elements for buttons and markers and native cyclical scrolling. The CSSWG may be the vehicle where Google continues to exert its dominance over web standards, separation of concerns and accessibility be damned.
Update: 6 June 2025
David Bushell highlights something with which I agree and which I don’t think gets enough attention — ::pseudo-elements?.
He points out it’s a clear violation of separation of concerns (which should sound familiar) and reminds of localization risks (something I would think a Working Group would consider). Google’s rush to market has left many obvious gaps, and I rather hope Google stops doing that seemingly every quarter / conference cycle.
In The Need for Accessibility Excellence, Devin Prater points out Gemini’s accessibility failures on Android (versus iOS), significant gaps in TalkBack, frustrations with Google Play Books, hassles with Gmail on Android, barriers in gaming on Android, and the seeming abandonment of Accessibility Tags in Google Play.
This isn’t about pointing fingers or assigning blame. It’s about recognizing a pattern of inconsistency and demanding a higher standard. How can we expect small companies or indie developers to make their apps accessible, when we can’t get Google to listen to us and take us seriously?
And that’s the thrust of it. When developers continue to justify their decisions because Google did it, that lowers the experience for everyone.