Tithi Mondal

Guide5 min readUpdated

Accessibility in UI Design: A Practical Guide with Checks

Accessibility in UI design made practical: colour contrast, tap target size, screen reader basics and quick checks you can run on any app or website today.

By Tithi Mondal, UI/UX Designer

Accessible design is often treated as a special project for later. In practice it is a set of ordinary design habits, and most of them make the product better for everyone. A person with low vision benefits, and so does someone using a phone outdoors at noon in an Indian summer. This guide gives you practical checks for accessibility in UI design that you can run today on an app or a website. It is general guidance, not legal advice. For a website, the same checks apply to your website design as to an app.

What accessibility actually covers

People use your product with different abilities and in different situations. Some have permanent conditions, such as low vision, colour blindness, hearing loss or limited hand movement. Others are temporarily or situationally limited: a broken wrist, a cracked screen, a noisy bus, a dim room, one hand holding a child.

Inclusive design means thinking about this range early, so the product works for more people without special versions. The widely used reference is WCAG, the Web Content Accessibility Guidelines. It groups its advice around four ideas: content should be perceivable, operable, understandable and robust. You do not need to memorise it. The checks below cover the parts a designer controls most.

Check 1: colour contrast

Contrast is the difference in brightness between text and its background. Low contrast is the most common problem I see in designs, usually light grey text on white because it looks neat.

The published WCAG AA standard asks for a contrast ratio of at least 4.5 to 1 for normal body text. Large text can be a little lower, and the standard sets 3 to 1 for it. Free contrast checkers in design tools and browsers will give you the ratio when you enter two colours.

  • Check body text, button labels, placeholder text and small captions, not only headings.
  • Check text on top of images and gradients, where contrast changes from one part to another.
  • Check disabled and error states. They are the ones people forget.
  • Test in bright light by turning the phone brightness down and walking near a window.

Brand colours often fail. A light orange or yellow button with white text is a classic case. The fix is usually to darken the button colour slightly, not to give up the brand.

Check 2: tap target size

Small targets are frustrating for everyone and a real barrier for people with limited dexterity. Both Apple and Google publish minimum touch target guidance in the region of 44 to 48 units, which is a sensible size to work towards.

  1. Make buttons, icons and links at least that size, even if the visible icon is smaller. Add invisible padding around it.
  2. Leave space between targets. Two small icons packed side by side cause wrong taps.
  3. Put the main action within thumb reach at the bottom of the screen where possible.
  4. Avoid tiny close buttons on pop-ups, a common problem on promotional banners.
  5. Test on a real phone with a real thumb, not with a mouse cursor.

This matters a lot on the budget phones many people use, where screens are smaller and touch response is not perfect.

Check 3: do not rely on colour alone

Many people have some difficulty telling certain colours apart, and everyone loses colour in glare. If red means error and green means success, add something else too.

  • Pair colour with an icon or a word: a red border plus "Enter a valid mobile number".
  • In charts, use labels or patterns, not only colour keys.
  • For links inside text, use an underline or another clear cue.
  • For status in tables, such as paid or pending, write the word.

Check 4: text size and spacing

Do not lock text at a tiny size. Body text that looks fine on a large monitor can be hard to read on a small phone.

  • Keep body text comfortable on mobile, and let it grow when the user raises the system font size. Check that layouts still work at larger sizes.
  • Use enough line spacing and short lines so paragraphs are easy to follow.
  • Keep one clear typeface family and a small set of sizes.
  • For Indic scripts, give extra care to line height, as described in my post on regional language app design.

Check 5: screen reader basics

A screen reader reads the screen aloud for people who cannot see it. On Android it is TalkBack, on iPhone VoiceOver. It reads what developers expose, so design and development share the job.

What a designer can do:

  • Give every button a clear name. "Pay ₹499" is better than "Button".
  • Describe meaningful images. Mark purely decorative ones so they are skipped.
  • Keep a sensible reading order that follows the visual order.
  • Label form fields with visible text, not only placeholder text that disappears when typing.
  • Write error messages that say what is wrong and how to fix it.
  • Mention these points in the hand-off notes for developers.

Turn on TalkBack for ten minutes and try to complete a main flow with your eyes closed. It is the fastest way to learn.

A quick checklist you can reuse

AreaQuestion to ask
ContrastDoes body text reach 4.5 to 1 against its background?
Tap targetsCan a thumb hit every control without a wrong tap?
ColourIs meaning also shown with text or an icon?
TextDoes the layout survive a larger font size?
Screen readerDoes every control have a clear name?
FormsDoes every field have a visible label and a helpful error?
MotionCan animations be short, and can video be paused?

Build it in from the start

Fixing accessibility after launch is slower and more expensive than building it in. When I design the interface, I check contrast and target sizes while choosing colours and components, so the problems never reach the developer. If you are planning a product and want this handled early, see my UI/UX design service or write to me.

Frequently asked questions

What is the minimum colour contrast ratio for text?

The WCAG AA standard asks for at least 4.5 to 1 for normal text and 3 to 1 for large text. A free contrast checker will give you the ratio for any two colours.

How big should a button be on mobile?

Aim for roughly 44 to 48 units in each direction, following the guidance from Apple and Google, with space between neighbouring buttons. The visible icon can be smaller if the tappable area is larger.

How can I test my app with a screen reader?

Turn on TalkBack on Android or VoiceOver on iPhone and try to finish one main flow without looking. Every control should have a clear spoken name.

Is accessible design only for people with disabilities?

No. The same choices help people in sunlight, in noisy places, with one hand free or with a damaged screen. That is why it is called inclusive design.

Have a product in mind? Let us design it properly.

Tell me what you are building. I will reply with questions, a rough timeline and a quote.