Mobile Accessibility

Mobile accessibility is the practice of designing and building smartphone and tablet apps so people with disabilities can perceive, understand, navigate, and operate them. It covers native, hybrid, and mobile-web interfaces, platform assistive technologies such as VoiceOver and TalkBack, and the same WCAG principles used on the wider web.

itMobile and client application development

Don't Panic - Mobile Accessibility

Mobile accessibility is the art of making sure a phone app still works when the person using it cannot rely on the same eyes, ears, fingers, or patience the mockups assumed. VoiceOver and TalkBack are not exotic add-ons. They are how many people read the accessibility tree your app already exposes, whether you meant to design that tree or not.

Before tiny screens and multi-touch, the same job lived on desktops with keyboards and browser semantics. Mobile did not invent accessibility. It did invent new ways to get it wrong: icon rows with no names, swipe-only deletes, orientation locks, and zoom that a viewport meta tag quietly disables.

Everything hangs off three ideas. First, assistive technology consumes name, role, state, and value, not your gradient. Second, WCAG is still the shared test language, with WCAG2ICT helping when the surface is native instead of a web page. Third, gestures and tiny targets are fine as shortcuts only when a boring, focusable alternative exists.

The surprise is how continuous this is with web work. Phones grow keyboards. Laptops grow touch. Responsive layouts blur the categories. W3C's mobile guidance keeps telling people to apply WCAG rather than wait for a separate mobile rulebook. The new criteria in 2.1 and 2.2 simply named pressures mobile teams already felt: orientation, reflow, pointer gestures, motion actuation, and a Level AA target-size floor.

If a control only works for a sighted index finger performing a secret handshake, it does not work yet.

What to open next: the Intro for the four-layer stack; the Cheatsheet when you need criterion IDs and prop names under pressure; Field Notes when you want the judgment calls scanners never make; the Quiz when you are ready to check whether "tree, not pixels" actually stuck.

Don't Panic - Mobile Accessibility

Relevant careers