FNA Technology Header Logo
ServicesProductsWorkAboutBlog
[ start a project ]
FNA Technology Footer Logo

Transforming your digital vision into reality. Software, AI, web & mobile — built for outcomes.

contact@fnatechnology.com footer link+91 8879510299 footer link
FOLLOW US
VERIFIED ON
TechBehemoths verified company badge for FNA Technology
MAIN
HomeOur ServicesOur ProductsProjectsCompany Blog
SERVICES
AI DevelopmentAI ChatbotsAI AgentsWeb AppsMobile AppsSaaS DevelopmentCustom SoftwareProduct & UX DesignSupport & Maintenance
COMPANY
About UsContact UsLinkedInX (Twitter)
LEGAL
Privacy PolicyTerms & Conditions
© 2026 FNA TECHNOLOGY LLP — ALL RIGHTS RESERVEDBuilt in India · Clients in India, the UK & the Middle East
UI/UX

Accessible UI Design: A WCAG 2.2 Guide for Product Teams

April 5, 2025
7 min read
FNA Technology
Share
Accessible interface design with high-contrast text, large targets and visible focus

The short version: Design to WCAG 2.2 level AA. In practice that means 4.5:1 text contrast, visible focus, every control usable by keyboard, labels tied to inputs, targets of at least 24 CSS pixels (44 pt on iOS, 48 dp on Android) and dialogs that manage focus. Automated scans find the easy half; test the rest by hand.

Last updated: 21 October 2026.

Accessible UI design means people can perceive, operate and understand your product whatever their vision, hearing, motor or cognitive ability, and whatever device or assistive technology they use. The working standard is WCAG 2.2 at level AA. Most of it is ordinary good design written down precisely: readable text, obvious controls, forms that explain themselves.

This guide covers the decisions that matter most at the design stage, the failures we see most often, and three fixes we made on our own site this year.

Why does accessibility matter for a product team?

Because the audience is large and the web is still failing it. The World Health Organization estimates that 1.3 billion people, 16% of the world's population, experience significant disability (WHO, March 2023). Many more have temporary or situational limits: a broken wrist, bright sunlight on a phone, a noisy train.

The state of the web is poor. WebAIM's February 2026 scan of the top one million home pages found detectable WCAG failures on 95.9% of them, up from 94.8% in 2025, with an average of 56.1 errors per page (WebAIM Million 2026). These are only the automatically detectable errors, so the true picture is worse.

There is also a legal side. The European Accessibility Act covers services such as e-commerce and banking across the EU (European Commission). If you sell into regulated markets, expect WCAG AA conformance to appear in contracts.

Which standard should you design to?

WCAG 2.2. It became a W3C Recommendation on 5 October 2023 and adds nine success criteria to WCAG 2.1 (W3C, What's new in WCAG 2.2). The current published version is dated 12 December 2024 (W3C). Level AA is the usual target. The new AA and A criteria that affect design most:

CriterionLevelWhat it asks of the design
2.4.11 Focus Not Obscured (Minimum)AASticky headers and cookie bars must not fully hide the focused element
2.5.7 Dragging MovementsAAAnything done by dragging also works with a single tap or click
2.5.8 Target Size (Minimum)AATargets at least 24 by 24 CSS pixels, or spaced so they do not crowd
3.2.6 Consistent HelpAHelp links or contact options sit in the same place on every page
3.3.7 Redundant EntryADo not make people type the same information twice in one process
3.3.8 Accessible Authentication (Minimum)AALogin must not depend on a cognitive test such as solving a puzzle

What are the most common accessibility failures?

WebAIM's 2026 data is a good priority list, because six failure types account for 96% of everything it detects:

FailureShare of home pages
Low contrast text83.9%
Missing alternative text for images53.1%
Missing form input labels51%
Empty links46.3%
Empty buttons30.6%
Missing document language13.5%

Every item on that list is cheap to prevent at design time and tedious to fix afterwards. Empty links and buttons are usually icon-only controls with no accessible name, such as a bare trash-can icon or a social logo.

How do you get colour and contrast right?

WCAG 1.4.3 requires a contrast ratio of at least 4.5:1 for normal text and 3:1 for large text at level AA (W3C). Check every text and background pair in your design tokens once, rather than screen by screen, and the problem mostly disappears.

The usual offenders are grey placeholder text, light text on brand colour buttons, and text over images. Never use colour as the only signal: an error needs an icon or words as well as red, and a chart needs labels or patterns as well as hues. If you ship a dark theme, test it separately; a palette that passes in light mode can fail in dark mode. Our dark mode guide covers that in detail.

How big should touch and click targets be?

WCAG 2.5.8 sets the AA floor at 24 by 24 CSS pixels, or enough spacing that a 24 pixel circle centred on each small target does not overlap its neighbours (W3C). Platform guidance is more generous. Apple's Human Interface Guidelines list a minimum control size of 44 by 44 points on iOS and iPadOS (Apple HIG, Accessibility), and Android recommends a touch target of at least 48 by 48 dp (Android Developers).

Design mobile apps to the platform figure, and treat 24 pixels as the absolute minimum for dense web interfaces such as data tables.

How do you make forms accessible?

Tie every visible label to its input in code, so that a screen reader announces it and a click on the label focuses the field. This was one of our own fixes. The audit form on fnatechnology.com had visible labels that were not associated with their inputs. We added matching for and id attributes and autocomplete hints, which also lets browsers fill names and email addresses correctly.

Beyond labels: describe errors in text next to the field (WCAG 3.3.1), keep the user's input when showing an error, and announce dynamic messages such as "Saved" through a live region. Our guide to UX writing and microcopy covers what those messages should say.

How do you make modals and custom controls keyboard-friendly?

Prefer native HTML elements. The W3C's first rule of ARIA use is that if a native element or attribute already has the semantics and behaviour you need, use it instead of re-purposing another element with an ARIA role (W3C, Using ARIA). A real <button> is focusable, activates with Enter and Space and has a role, for free.

When you must build a custom widget, follow the ARIA Authoring Practices pattern. For a modal dialog, focus moves into the dialog when it opens, Tab and Shift+Tab cycle within it, and Escape closes it (W3C ARIA APG, Dialog (Modal)).

Our second fix was exactly this. The image lightbox on our blog opened only on mouse click. We gave the trigger a button role, made it focusable and operable with Enter and Space, marked the overlay as a modal dialog, moved focus to the close button on open, and made Escape close it.

Why does heading structure matter?

Screen reader users navigate by headings the way sighted users skim. Headings should follow the page outline, not the font size the designer wanted. Our third fix was small: the 404 page used an h4 directly under the page's h1, skipping two levels, so we made it an h2. Style headings with CSS and choose the level by structure.

How should you test accessibility?

Use three layers:

  1. Automated checks in CI for the easy, common failures: contrast, labels, alternative text, empty buttons, page language.
  2. Keyboard testing by a person. Unplug the mouse and complete every main task. Watch for invisible focus, focus traps and focus hidden behind sticky elements.
  3. Screen reader passes on the platforms you support: VoiceOver on iOS and macOS, TalkBack on Android, and NVDA or JAWS on Windows.

Then fix at the source. A contrast problem in a design token, or a missing name on an icon button component, is one change that fixes hundreds of screens.

Accessibility is cheapest when it is part of the design system from the first sprint. Our product UX design team builds WCAG 2.2 AA into components and reviews, and our web development team implements and tests it in code.

Frequently Asked Questions

WCAG 2.2, published by the W3C as a Recommendation on 5 October 2023. Most teams, regulators and procurement checklists target level AA. WCAG 2.2 adds nine success criteria to WCAG 2.1, including minimum target size, focus not obscured and accessible authentication.

At level AA, normal text needs a contrast ratio of at least 4.5:1 against its background, and large text needs at least 3:1. Low contrast text is the most common failure found by WebAIM, on 83.9% of the top one million home pages in its February 2026 analysis.

WCAG 2.2 AA requires pointer targets of at least 24 by 24 CSS pixels, or enough spacing around smaller ones. Platform guidance is larger: Apple recommends a minimum of 44 by 44 points on iOS and iPadOS, and Android recommends at least 48 by 48 dp. Design to the platform figure.

They catch a useful share of problems, such as missing labels, missing alternative text and low contrast, but not all of them. Keyboard use, focus order, meaningful alternative text and whether a screen reader experience makes sense all need a person to test them.

Indirectly. Proper headings, labelled controls, descriptive links and text alternatives make pages easier for search engines and AI systems to parse, and they make pages easier for people to use. Accessibility is worth doing for users first; the machine-readability is a side effect.

#accessible UI design#WCAG 2.2#WCAG 2.2 AA checklist#colour contrast ratio#touch target size#accessible forms#accessible modal dialog
Share this article:
FNA Technology company logo

Written by

FNA Technology

Team Member at FNA Technology

FNA Technology is a software development company specializing in AI, mobile apps, and web solutions.

Work with us