VoiceOver is the screen reader built into every iPhone and iPad. If you build, design, or test anything that runs on an iPhone, you should know how to use it. Testing your apps with VoiceOver will be the one of the best ways to find out whether the your app or website is accessible. This guide walks you through the common gestures. First, the set up Before you turn VoiceOver on, give yourself a quick way to turn it off. How you interact with the phone will change. When you're new, it's easy to feel stuck once the gestures change. Go to Settings > Accessibility > Accessibility Shortcut. Choose VoiceOver. Now you can turn VoiceOver on or off by triple-clicking the side button (or the Home button on older phones). If you get lost, three clicks and you're back to no VoiceOver mode. Once VoiceOver is on your relationship with the screen changes. Practice in a safe sandbox Every beginner should spend a few minutes in VoiceOver Practice. Go to Settings > Accessibility > VoiceOver and tap VoiceOver Practice. (The button only appears while VoiceOver is on.) It opens a blank screen where you can tap, flick, and swipe freely. The phone says which gesture it detected, without changing any settings. It's the perfect place to learn the Magic Tap, a two-finger double-tap that starts or stops music and answers or ends calls, before you try it in the real world. Select first, then double-tap In VoiceOver mode, your finger explores. A single tap doesn't open an app. Instead, it draws a thick black border around the item (the VoiceOver cursor) and the phone speaks its name aloud. Once you hear the item you want, you activate it with a double-tap. But you don't have to hit the icon itself twice. Once the black border is on an item, you can double-tap anywhere on the screen to "click" it. Think of it this way: One tap looks at the button. Double-tap presses the button. Separating selection from activation is what keeps you in control, even when you can't see the screen. Flick to move through the screen To move from item to item, flick one finger to the right. The cursor jumps to the next item and reads it aloud, like turning the pages of a book. Flick left to go back. Flicking is faster than dragging your finger around. It also shows you something important as a developer: the order VoiceOver reads things in. If the focus order jumps around or skips a control, your users will notice. Scroll with three fingers Since a one-finger swipe now moves between items, scrolling needs more fingers. To scroll a long list or a webpage, swipe up or down with three fingers. It feels a bit like pushing the page away. When you reach the top or bottom of a list, the phone plays a low "thump" sound. That's how you know there's no more content. Conclusion Automated accessibility checks catch missing labels. They don't catch a button that reads as "button," a focus order that makes no sense, or a custom control that VoiceOver can't reach at all. Only a real screen reader shows you that. So the next time you're about to mark a ticket done, turn VoiceOver on and try the flow yourself. Ten minutes of testing will teach you more than any checklist.