Skip to content
SiteMonk Learn
Esc
↑ ↓ navigate ↵ open ⌘J preview
On this page
  1. Check actual contrast combinations
  2. The target is more than the icon
  3. Keep states understandable too

Contrast and targets: make controls readable and reachable

Understand text contrast, activation areas, and state cues, with a clear distinction between observation and technical checks.

Faint conditions, tiny icons, and errors communicated only by color can make a website difficult to read or operate. Accessible design supports different vision and input needs, including people using a phone in sunlight or with one hand.

Check actual contrast combinations

Contrast measures the luminance difference between foreground and background. Body text, button labels, field boundaries, and focus indicators need checking against their actual backgrounds. A vivid color is not necessarily readable.

Ordinary text, larger text, and controls have different requirements. The team should verify the applicable WCAG criteria. You do not need to calculate ratios by eye, but can identify faint price conditions or unreadable text on a photo. “I can read it” is not a substitute for checking.

The target is more than the icon

A target is the area that accepts a click or touch. An icon can be visually small while having adequate activation space and suitable separation from nearby controls.

Location What you can observe
Mobile menu and close controls Are they easy to hit without activating a neighbor?
Links in service lists Is the destination clear, and are links distinguishable from ordinary text?
Form errors Does wording explain the problem instead of only a red outline?
Waiting or unavailable actions Is it clear why progress is blocked and what happens next?

Activation area, spacing, and clear naming work together; enlarging a graphic alone may not solve the problem. The team checks applicable dimensions and exceptions.

Keep states understandable too

Controls need suitable information in their normal, focused, waiting, and error states. Errors should not rely only on red; selected options should not rely only on subtle color changes. Important instructions should not appear only on mouse hover.

You can try reading and operating the site on a phone and report difficulties. The team handles measurement, assistive-technology support, and verification of the agreed scope. Passing an automated tool or a short checklist is not accessibility certification.

See color roles and keyboard access and semantics . Technical references include W3C text contrast and target size .

For a SiteMonk website project, discuss the required accessibility scope as part of website design and development . We can explain the applicable checks and record what was tested before you approve the delivery.