Compliance without Accommodation: The Unfortunate Circumstance of Existing Accessibility Guidance
This post discusses accessibility standards and legal frameworks for educational purposes. It is not legal advice. Consult qualified counsel for compliance decisions.
Executive Summary
WCAG 2.x's color contrast algorithm—designed for CRT monitors—misclassifies nearly half of all color combinations on modern displays. A superior alternative, the Accessible Perceptual Contrast Algorithm (APCA), exists and is expected in WCAG 3.0, but legal counsel increasingly advises against early adoption because WCAG compliance is effectively codified in U.S. disability law through Section 508 and ADA enforcement patterns. This creates an accessibility governance dilemma: organizations can satisfy legal requirements while failing users, or pursue better outcomes while accepting litigation exposure. The accountability gap falls on disabled users caught between outdated standards and inaccessible alternatives. This post examines both positions and proposes a dual-measurement approach—conforming to WCAG 2.x for legal defensibility while measuring against APCA for genuine accessibility outcomes, bridging the gap between what law requires and what users need.
The Paradox
The enshrining of the Web Content Accessibility Guidelines (WCAG) into U.S. disability law was, by any reasonable measure, a victory for digital accessibility. For the first time, organizations faced enforceable requirements to make web content accessible. Yet this victory has come with an unintended consequence: the very mechanisms intended to protect people with disabilities have, in some cases, become barriers to protecting them more effectively. Compliance became the measure of success—and actually serving users became secondary.
This is the paradox of accessibility compliance in 2025. A better algorithm for evaluating color contrast exists. It has been validated by peer-reviewed research. It produces more accurate results for users with low vision. And cautious corporate counsel across industries advise against adopting it—not because it fails to serve users, but because WCAG 2.x has been effectively codified as law. Practitioners now work in a gap—caught between what regulations require and what users actually need.
The Contrast Problem
The Web Content Accessibility Guidelines (WCAG), developed by the World Wide Web Consortium (W3C), provide a comprehensive framework for making web content accessible. Much of it remains sound guidance.
The problem lies specifically in WCAG 2.x's approach to color contrast. The contrast ratio calculation, designed in an era of CRT monitors and limited display technology, does not accurately model how humans perceive luminance differences on modern displays. Research suggests the algorithm is wrong nearly half the time.
The Accessible Perceptual Contrast Algorithm (APCA), developed by Andrew Somers and expected in WCAG 3.0, addresses these deficiencies through calculations grounded in modern vision science. Yet APCA adoption remains blocked by legal uncertainty—and WCAG 3.0 remains years away.
Two Perspectives
This situation admits no easy answer. Critics argue that legal entrenchment of a flawed standard actively harms the users it was designed to protect. Defenders counter that legal stability provides more practical protection than promising but immature alternatives.
Both arguments have force. The details reveal the tension.
The Compliance Trap: Why WCAG's Legal Entrenchment Harms Users
The Core Problem
WCAG 2.x's contrast algorithm is not perceptually accurate. Research from Myndex estimates the algorithm is "wrong nearly half the time": roughly 40% of color combinations passing WCAG criteria should actually be rejected for poor readability, while over 50% of "failing" combinations are perfectly readable.
The "Orange Button Problem"
White text on medium orange is clearly readable to most users, including many with visual impairments, yet fails WCAG's requirements. Conversely, text meeting the 4.5:1 ratio against near-black can be functionally unreadable yet passes.
Legal Lock-In
Section 508 explicitly incorporates WCAG 2.0 Level AA. ADA enforcement consistently cites WCAG 2.1 AA as the settlement standard. This creates an unintended incentive structure: organizations optimize for legal defensibility rather than actual user experience. Deviating from WCAG—even for demonstrably superior alternatives—exposes organizations to litigation risk.
The APCA Alternative
The Accessible Perceptual Contrast Algorithm (APCA) addresses these failures by:
- Recognizing that contrast perception is polarity-sensitive (swapping text/background produces different results)
- Accounting for font size and weight
- Providing graduated guidance rather than arbitrary pass/fail thresholds
When properly implemented, APCA conformance exceeds WCAG 2.x AAA requirements—the highest level of the current standard.
The Timeline Problem
As of early 2025, WCAG 3.0—which is expected to incorporate APCA—remains years away from becoming an official W3C Recommendation. The working group does not expect to finalize a timeline until 2026. Until then, organizations must choose between adhering to a flawed standard or adopting superior approaches that expose them to legal risk.
Sources: Myndex Research APCA Documentation; W3C WCAG 3.0 Issue #192; WebAIM Million analysis
In Defense of Stability: Why Legal Certainty Matters
The Value of Legal Certainty
Legal standards exist to provide predictable, enforceable protections—not to facilitate perpetual technical refinement. For 1.3 billion people worldwide living with disabilities, consistent enforcement of known standards offers more practical protection than theoretically superior algorithms that remain years from adoption.
APCA's Implementation Challenges
The APCA system introduces complexity that falls disproportionately on smaller organizations:
- Every color combination requires checking for both font-size and weight
- Designers must compare chosen fonts to a Helvetica-based reference table—a process described as "error-prone"
- The algorithm itself continues to change, meaning colors sufficient today may not be sufficient under later versions
When the algorithm's own developer acknowledges ongoing simplification efforts, it seems premature to fault regulators for not adopting it.
WCAG Is More Than Contrast
The focus on contrast algorithms obscures a crucial point: WCAG addresses keyboard accessibility, text alternatives, navigability, timing, seizure prevention, and dozens of other critical success criteria. Even APCA's creator acknowledges: "There's a lot in WCAG 2 that's very good and very important for accessibility—just not the contrast."
WCAG 2.2 was published in October 2023 with nine new success criteria, demonstrating that the standard continues to evolve within its established structure while maintaining backwards compatibility.
The Compliance Floor
Clear legal requirements establish baselines below which conduct becomes actionable. A person with low vision denied access to a non-conforming website has grounds for complaint. Replacing clear thresholds with sliding scales makes legal enforcement murkier. Organizations genuinely committed to accessibility will exceed requirements regardless of which algorithm underlies them.
Sources: W3C WCAG 2.1; Eric Eggert, "WCAG 3 is not ready yet"
The Cost of Uncertainty
Both arguments have merit. But here is what gets lost in the debate: while regulators deliberate and standards bodies refine, real users encounter interfaces every day that technically comply with WCAG yet fail to serve them.
Dark mode—now ubiquitous across operating systems and applications—exposes this constantly. The contrast algorithm only works reliably with light backgrounds and dark text, providing little meaningful guidance for modern interface design. Meanwhile, organizations facing thousands of ADA accessibility lawsuits annually optimize for defensibility rather than usability. The question "Does this pass WCAG?" supplants "Does this work for users?" (This same pattern plays out with AI-generated content—see Accessible AI: Why LLM Outputs Fail Users with Disabilities.)
The result: disabled users lose access to better accommodation they could have today because the legal risk of innovation outweighs the benefit of serving users better. The accountability gap falls on those least able to advocate for change.
A Path Forward
The solution is not to abandon compliance—legal protections for accessibility are essential and hard-won. But neither is the solution to accept indefinitely a standard that even its governing body acknowledges is deeply flawed in specific areas.
Organizations committed to genuine accessibility—not just compliance—can adopt a dual approach: measuring against WCAG 2.x for legal conformance while also measuring against APCA to achieve better actual outcomes. Tools like Bridge PCA exist specifically to provide WCAG 2.x compatibility while using APCA technology internally. (I built Contrast Chaser to address similar workflow friction within WCAG's constraints.) This is not ideal—it adds complexity and cost—but it represents a pragmatic response to an imperfect situation.
More fundamentally, this situation illustrates a broader challenge in accessibility governance and systems integration. Standards that worked for one technological era become constraints in the next. Legal codification, while necessary for enforcement, freezes those constraints in place. The feedback loop between accessibility science and accessibility law moves slowly, and disabled users bear the cost of that misalignment.
Until regulatory bodies catch up with accessibility science, inclusive design practitioners must navigate the gap between what the law requires and what users actually need. That gap is where the real work of digital accessibility happens.