Accessibility in Product Design: WCAG for Apps and Devices

Accessibility means people with visual, hearing, motor or cognitive impairments can use a product, and good accessibility usually makes products easier for everyone. The Web Content Accessibility Guidelines, WCAG, are the common reference. Version 2.2 became a W3C Recommendation in 2023 and is organised under four principles: perceivable, operable, understandable and robust. Laws in many markets point to WCAG, directly or through standards such as EN 301 549.

At a glance

Level AA
The conformance level most laws and procurement rules reference.
4.5:1
The minimum contrast ratio for normal-size text at Level AA.
24 px
The Level AA minimum target size in WCAG 2.2, in CSS pixels, with some exceptions.
June 2025
When the European Accessibility Act began to apply to many products and services in the EU.

The problem

Accessibility is often left to a late audit, by which point the colour palette, custom controls and navigation structure are built. Fixing contrast and adding screen reader support across a finished app is slow and expensive.

Devices and their companion apps are frequently missed altogether. A touchscreen with low-contrast text, small targets and no audio or tactile alternative excludes users that a little early design work would have included.

Accessibility is a design requirement, not a final check. Contrast, targets and labels cost almost nothing when they are specified up front.

Applying WCAG beyond the web

In native mobile apps, the platform accessibility services do much of the work if the app uses standard controls and labels them: VoiceOver on iOS and TalkBack on Android read those labels aloud. Custom controls need roles, names and states added explicitly. Respect the system text size setting rather than fixing font sizes.

For device interfaces, W3C guidance on applying WCAG to non-web technology and the European standard EN 301 549 translate the criteria to hardware and closed systems. Controls that can be found by touch, audible feedback and adequate display contrast are the starting points.

What good looks like

Adopt WCAG 2.2 Level AA as a written requirement for apps, web interfaces and device screens, and check the specific laws in each target market.

Build it into the design system: colours that meet contrast ratios, minimum target sizes, visible focus indicators and labelled components.

Test with screen readers, keyboard navigation, large text settings and automated checkers, and include people with disabilities in usability testing where possible.

WCAG 2.2 contrast minimums
:1
Text, AA4.5
Large text, AA3
Text, AAA7
Large text, AAA4.5
UI components, AA3
Luminance contrast between foreground and background. Large text is at least 18 point, or 14 point bold.
Selected criteria added in WCAG 2.2
CriterionLevelWhat it requires
2.4.11 Focus Not Obscured (Minimum)AAThe focused item is not entirely hidden by other content
2.5.7 Dragging MovementsAAAnything done by dragging can also be done with single taps or clicks
2.5.8 Target Size (Minimum)AATargets at least 24 by 24 CSS pixels, or adequately spaced
3.2.6 Consistent HelpAHelp options appear in the same relative place across pages
3.3.7 Redundant EntryAInformation already given is not requested again in the same process
3.3.8 Accessible Authentication (Minimum)AANo memory or puzzle test to log in unless an alternative or aid is allowed
WCAG 2.2 also removed criterion 4.1.1 Parsing.

What it changes

Wider Reach

More people can buy and use the product, including an ageing population.

Compliance

Accessibility law and public procurement requirements are met by design.

Better Usability

Clear contrast, large targets and good labels help every user in difficult conditions.

Lower Rework

Accessibility built into components does not need retrofitting screen by screen.

Where to go next

Automated tools catch only part of the problem. Manual review with assistive technology finds issues such as illogical reading order or unclear labels.

Publish an accessibility statement describing conformance and known limitations. Many buyers, particularly in the public sector, expect one.

Problems this prevents

  • Text too faint to read in daylight
  • Custom controls invisible to screen readers
  • Touch targets too small to hit reliably
  • An accessibility audit failed after launch

Discuss your project

Email support@aavico.com or use Get in Touch when the website finishes loading.