Learn & Understand

Accessibility Beyond Contrast: POUR, Screen Readers, and the Curb-Cut Effect

The companion calculator checks color contrast against WCAG thresholds, and contrast is one of the most common accessibility failures. But contrast is a single slice of a much larger discipline. Web accessibility means building sites usable by people with a wide range of disabilities, visual, motor, auditory, cognitive, and it rests on principles and techniques that go far beyond color. Understanding the broader framework, how assistive technology actually works, the legal stakes, and the surprising truth that accessibility helps everyone, turns a contrast check into a real commitment to inclusive building.

The POUR Principles

The Web Content Accessibility Guidelines are organized around four principles, remembered by the acronym POUR, that define what accessible means.

Contrast falls under Perceivable, but it is one requirement among dozens. An accessible site must also be operable without a mouse, understandable in language and structure, and robust enough to work with the assistive tools people actually use. Seeing contrast as one item in this larger framework is the first step beyond treating accessibility as a color checkbox.

How Screen Readers Depend on Structure

Much accessibility work is invisible because it serves assistive technology like screen readers, which convert a page to speech or braille for blind and low-vision users. Screen readers do not see pixels; they read the underlying structure, so the way a page is built determines whether it is usable. Semantic HTML, using real headings, buttons, lists, and landmarks rather than generic divs, gives screen readers the structure to navigate and announce content meaningfully. Alt text on images conveys what a sighted user would see. Labels on form fields tell users what to enter. A visually perfect page built from meaningless markup can be completely unusable to a screen reader, which is why semantic structure and text alternatives are foundational, not optional polish.

Keyboard and Operability

Many users cannot use a mouse, relying instead on a keyboard or other input, so every interactive element must be reachable and operable by keyboard alone, with a visible focus indicator showing where you are. A menu that only opens on hover, a control that only responds to a click at a precise pixel, or a custom widget that traps focus can lock these users out entirely. Ensuring logical tab order, visible focus, and keyboard operability for everything clickable is core to the Operable principle, and it is easy to break without noticing if you only ever test with a mouse. Testing with the keyboard alone reveals barriers invisible to mouse users.

The Legal Stakes and the Curb-Cut Effect

Accessibility is increasingly a legal requirement, not just good practice: public-facing sites face obligations under disability-rights laws, and accessibility failures, contrast among the most cited, are a frequent basis for complaints and lawsuits. But the most encouraging truth is the curb-cut effect: accommodations built for people with disabilities routinely benefit everyone. Curb cuts in sidewalks, made for wheelchairs, help anyone with a stroller or cart; likewise, captions help people in noisy rooms, clear structure helps everyone navigate, and good contrast helps in bright sunlight. Building accessibly produces a better product for all users, which reframes it from a compliance burden into a quality practice with universal payoff.

Building Accessibly, Not Just Checking Contrast

Use the calculator to verify contrast, and treat it as one entry point into the whole discipline: build to the POUR principles, use semantic HTML and alt text so screen readers can convey your content, ensure everything works by keyboard with visible focus, and recognize both the legal stakes and the curb-cut effect that makes accessibility better for everyone. The calculation checks one requirement; understanding accessibility broadly is what makes a site genuinely usable by all.