Skip to content
UI/UX13 min read

Accessibility in UI/UX Design: A Practical Guide to WCAG

The accessibility decisions designers own: contrast, typography, focus states, touch targets, color use, forms, motion and annotations for developers, grounded in WCAG 2.2.

01

Quick answer

Accessible UI/UX design means making design decisions that let people of all abilities perceive and use a product. Designers own many of them: meeting WCAG contrast ratios (4.5:1 for normal text, 3:1 for large text and UI components at level AA), visible focus states, adequately sized touch targets, never using color alone to convey meaning, readable typography that scales, clear form labels and errors, restrained motion, and annotated reading order, labels and alt text for developers. Building these in from the start is far cheaper than fixing them later.

02

Design's Role in Accessibility

Developers implement accessibility, but many barriers are designed in: low-contrast text, invisible focus, tiny tap targets, color-only status indicators, placeholder-only labels. This guide covers the design decisions; the website accessibility guide covers implementation such as semantic HTML, keyboard support and screen readers.

03

WCAG in Brief

The W3C's WCAG 2.2 organizes requirements under four principles: perceivable, operable, understandable and robust. Level AA is the common target for business products. The design-relevant criteria are summarized below.

Design areaWCAG guidance (level AA unless noted)
Text contrast4.5:1 for normal text; 3:1 for large text
UI and graphics contrast3:1 for component boundaries, states and meaningful graphics (1.4.11)
Use of colorColor isn't the only way information is conveyed (1.4.1, level A)
Text resize and reflowContent works when text is enlarged and at narrow widths
Focus visibleKeyboard focus is visible, and not entirely hidden by sticky elements (2.4.11)
Target sizeAt least 24 by 24 CSS pixels, with exceptions (2.5.8)
Labels and instructionsInputs have visible labels or instructions
Error identificationErrors are identified and described in text
04

Color and Contrast

Check text and interface contrast as you pick the palette, not after. Pay special attention to placeholder text, disabled-looking elements that are actually active, text over images, and thin fonts. Non-text contrast applies to input borders, icons and focus indicators too. Pair color with text or icons for errors, statuses and charts.

05

Typography and Readability

Use readable sizes, adequate line height and line length, and clear heading hierarchy. Designs should survive users enlarging text: plan how layouts reflow rather than truncating or overlapping. Avoid long passages in all caps or light weights.

06

Focus States and Keyboard Use

Design a clear, consistent focus indicator for every interactive element, with enough contrast against its surroundings. Make sure sticky headers, cookie banners and chat widgets don't cover focused elements, which WCAG 2.2 addresses explicitly. Define a logical focus order in your annotations.

Want your designs reviewed for accessibility?

ZSpace Labs reviews interfaces against WCAG and designs accessible components that meet the standard from the start.

Start a Project
07

Touch Targets and Interaction

Meet WCAG 2.2's 24 by 24 CSS pixel minimum and aim higher on mobile, where Apple and Google recommend around 44 points and 48 dp. Provide alternatives to complex gestures such as dragging or multi-finger swipes, and avoid time limits users can't extend.

08

Forms and Errors

Use visible labels, not placeholder-only fields. Group related inputs, mark required fields clearly, and write error messages that say what's wrong and how to fix it, placed next to the field. Don't clear the form after an error.

09

Motion and Media

Keep animation purposeful, avoid flashing content, and design reduced-motion alternatives that respect users' operating system settings. Plan captions for video and transcripts for audio, and ensure media controls are accessible.

10

Annotating for Developers

  • Heading levels for each screen
  • Reading order and focus order
  • Accessible names for icon-only buttons
  • Alternative text for meaningful images; decorative images marked
  • Form labels, hints and error messages
  • States: focus, error, disabled, selected, expanded
  • Landmarks such as header, navigation, main and footer
11

Accessibility in the Design System

Bake accessibility into tokens and components: accessible color pairs, focus styles, minimum target sizes and error patterns. Then every screen built from the system inherits it. See design systems.

12

This guide describes design best practice aligned with WCAG. Legal requirements differ by jurisdiction and sector, so confirm your obligations with qualified legal advice.

Building an accessible product from scratch?

Talk to ZSpace Labs about UI/UX design with accessibility built into every component.

Start a Project
13

Conclusion

Many accessibility barriers are design decisions: contrast, focus, target size, color use, labels and motion. Design them in, annotate them for developers, and encode them in your design system. Then test with assistive technology and real users, as part of usability testing.

For related guides, see ecommerce accessibility checklist.

FAQ

Common questions.

Designing products that people with a wide range of abilities, including visual, motor, auditory and cognitive differences, can perceive, understand and use.

The Web Content Accessibility Guidelines published by the W3C. WCAG 2.2 is the current version, organized around being perceivable, operable, understandable and robust, with conformance levels A, AA and AAA.

At level AA, 4.5:1 for normal text, 3:1 for large text, and 3:1 for user interface components and meaningful graphics.

Success criterion 2.5.8 (level AA) requires pointer targets of at least 24 by 24 CSS pixels, with exceptions such as sufficient spacing, inline links and equivalent controls.

Both. Designers own decisions such as contrast, focus visibility, target size, reading order and error messaging; developers implement semantics and behavior. Many issues start in design.

No. Clear contrast, readable type and obvious controls improve usability for everyone. Accessibility constrains some choices but rarely limits good visual design.

By specifying heading levels, reading and focus order, labels for icons and inputs, alternative text, error messages and states directly in design files.

In many jurisdictions and sectors it is, but requirements vary. Confirm your obligations with qualified legal advice; this guide covers design practice.

That guide covers implementation: semantic HTML, keyboard support and screen readers. This one covers the design decisions that come before code.

Get in touch

Have a project in mind?

Whether you're building a new digital product, improving an existing website, or looking to automate part of your business — let's talk.