Can you use your website with one hand?

A useful mobile check starts with a real task, not a tour of every page. Sit somewhere safe, open your business website on your phone, and follow a route a visitor might take. Notice where you change your grip, tap the wrong thing, or search for the next control. If holding the phone in one hand is uncomfortable, use it in the way that works for you.

Your experience is one observation shaped by your device, browser, hands, and preferences. Use it to find issues worth checking. It cannot show whether the site works for everyone or meets accessibility requirements.

Start with one visitor task

Choose a specific task, such as finding a service, checking where you work, and reaching the relevant contact or booking page. Begin at the homepage rather than using a saved link. Stay seated or otherwise stationary while you test. Do not try this while walking or driving.

Stop before placing a call, sending a request, confirming an appointment, making a purchase, or submitting anything. You can inspect the route without triggering an action. Keep a note open, or jot down observations after each step: where you were, what you tried, and what happened.

Follow the route from the homepage

Use the mobile menu to find the service, read enough to decide whether it fits the task, and move toward the next step. If you lose your place, write down the page and action. For example: “After I opened Services, I couldn’t tell how to close the menu.” This is an example of a useful observation, not a report about a particular site.

A specific note gives someone a place to start investigating. “The site is confusing” describes a reaction, but it doesn’t show where the route broke down. Record any grip change or extra search along the way, too. Those details can help distinguish a navigation issue from a control that is hard for you to reach or activate.

Check the menu and nearby controls

Open the menu, choose a destination, return, and close it. Check whether the labels make the destinations clear and whether the close control is easy to find. Pay attention to nearby links or buttons. A control can be hard to tap when it sits close to another one, even if its visible icon looks large enough. If you can comfortably try your other hand or another phone, note what changes. People have different grip preferences, so treat yours as one observation rather than a design rule.

W3C’s target-size guidance describes a minimum target size and allows spacing as an alternative in some cases. It also includes exceptions. A phone check can flag crowded controls, but a visual glance cannot determine whether the site meets the formal criterion. Ask a developer to inspect the clickable areas and relevant conditions. W3C target-size guidance

Repeat the task at a larger text size

Use a text-size or zoom setting supported by your browser or device, then repeat the task. Look for clipped text, overlapping elements, controls that disappear, or a page that requires sideways scrolling. Note the setting you changed so someone else can reproduce what you saw. Restore it afterward if you changed it only for this check.

W3C’s reflow guidance covers whether content and functionality remain available when the viewing area narrows, with exceptions for content that needs a two-dimensional layout. It describes a specific technical criterion, not a general test of one-handed use. Your phone check can point to something for further review, but it cannot establish whether the criterion is met. W3C reflow guidance

Look for overlays and keyboard obstructions

Scroll the page and inspect any sticky booking bar, chat launcher, cookie panel, or promotion. Check the lower part of the page as well as the first screen. Can you reach the footer links? Can you dismiss a panel and continue where you left off? Notice whether an overlay covers text or a control you need.

Open a form field without entering or submitting sensitive information. When the on-screen keyboard appears, check whether it hides the field or covers a persistent button. If something blocks the task, take a screenshot without personal information and note the device and browser. A sticky action may look convenient in one view and get in the way in another. Test it against the content it could cover before keeping or adding it.

Turn findings into a repair list

For each issue, record the page URL, device, browser, action, expected behavior, and what actually happened. Add a screenshot when it helps locate the problem. Separate task blockers, such as being unable to close the menu, from smaller interruptions, such as needing to adjust your grip to reach a control. That makes it easier to decide what to investigate first.

After a change, repeat the same route on the same phone and try another available screen size. Ask someone who did not make the change to follow the route, too. They may notice a different problem or interpret a label differently. Keep the check safe and stop before any call, booking, purchase, or submission is made.

This is a narrow usability exercise. One person’s check on one phone cannot establish accessibility for everyone or replace broader testing, including checks with different input methods and assistive technology. Keep your notes with your website maintenance records and revisit the route when you change navigation, add a widget, or update the booking flow.