A 20-Minute Accessibility Check for Your Small-Business Website

A customer is trying to book a repair from a phone with one hand while carrying groceries in the other. The menu is tiny, the form asks for an address before explaining why, and the send button is hard to spot. They may give up before you ever know they were there.

You do not need to be a web designer to catch some common obstacles. Set aside 20 minutes and walk through a few important pages as if you were a customer who cannot use a mouse, has low vision, or is in a hurry. These checks are a first look, not a full accessibility evaluation or a guarantee that a site meets every requirement. They can still reveal fixes worth making.

Start with the pages that matter most

Choose your home page, contact page, and one page where a customer takes action, such as booking, ordering, or requesting an estimate. If your website has a long menu, do not try to inspect every page at once. Pick the route a customer is most likely to use when they want to visit, call, book, or buy.

Write down the goal before you start: find the phone number, check today's hours, or send a request. Then notice where you hesitate. A small pause can point to a confusing label or a missing instruction. If a friend or staff member is available, ask them to try the same task without coaching. Their first question is useful evidence, not a test they need to pass.

Try the site without a mouse

Put the mouse aside and use the Tab key to move through the page. Each press should take you to the next link or control. Use Shift and Tab to move backward, and press Enter or Space to activate the item that has focus. Try the menu, contact links, form fields, and submit button.

Watch the screen as you go. Can you tell which link or field is selected? The outline or highlight around it should be easy to see. If the focus seems to vanish, or the tab order jumps from the logo to the footer and back again, a keyboard user may lose track of where they are. A visitor who cannot use a mouse might never reach the action you want them to take.

Do not assume the site is broken because one key behaves differently than expected. Menus and forms can have their own controls. The practical question is whether you can move around, understand where you are, and complete the task without reaching for the mouse.

Make text and buttons easier to see

Look at the page on a phone in ordinary light. Is the small print comfortable to read? Does pale gray text fade into a white background? Are buttons distinct from nearby labels and easy to tap? Color should not be the only clue that something is a link or that a field needs attention. For example, a form error should explain what needs fixing in words, not only turn a box red.

Now zoom the page in using your browser controls. Check whether text grows without forcing you to scroll sideways across every line or losing access to the menu. You can also turn your phone's text size up. These are everyday settings, not unusual edge cases. Someone may need larger text today because the screen is small, the room is bright, or their eyes are tired.

If you change your site's colors, do not pick them by taste alone. Compare the text against its background, including text on buttons and image overlays. W3C's accessibility guidance calls out sufficient contrast and easy-to-identify interactive elements. A quick visual check will not calculate compliance, but it can help you spot the pale button label that disappears in sunlight.

Give images and headings a job

Images can show what your store looks like, how a product is used, or where a service is available. For an image that adds useful information, write alternative text that gives the same important meaning to someone who cannot see it. A photo on a bakery page might say, "Front counter with the daily pastry case," if that detail helps a visitor know what to expect. A decorative swirl beside the logo does not need a paragraph of description.

Keep the description focused. A screen reader already announces that an item is an image, so starting every alternative text with "picture of" usually adds little. If an image is also a link or button, describe what it does. For example, a linked logo should make clear that it takes the visitor to the home page. The right wording depends on the image's purpose in that spot, not on a generic rule to describe every pixel.

Headings help people scan a page and understand how its parts fit together. Use a clear main heading, then headings that introduce the sections below it. A page with several paragraphs styled to look like headings may seem fine visually, but can be harder to navigate with assistive technology. Read only the headings in order. Do they sketch the page's contents, or do they leave out the part where a customer learns how to book?

Test one real form from start to finish

Fill out your contact or booking form on a phone. Check whether each field has a clear label, whether required details are identified before you submit, and whether the error message tells you how to fix a problem. An example such as "Enter a phone number with area code" gives a person more help than "Invalid input." Make sure the form does not erase everything someone typed when one field needs attention.

After you send a test, look for a clear confirmation. Does the page say the request went through and what happens next? If a customer needs a reply within two business days, say so only if your team can meet that expectation. A form that accepts a message but gives no confirmation leaves people wondering whether to try again, which can create duplicate requests for your staff.

Do not use a real customer's details for a test. Use a team address or a clearly marked test entry, and remove it afterward if it appears in your inbox or customer system. This is a quick website check, not a reason to collect extra information.

Turn the check into a small routine

Keep a short list with three columns: what you noticed, which page it affects, and who will follow up. Sort problems by what blocks a customer from completing a task. A missing phone number on the contact page is more urgent than a slightly uneven gap between two decorative images.

• Fix obvious labels, missing instructions, and hard-to-see focus indicators first.
• Ask whoever maintains the website to review issues that need code or theme changes.
• Repeat the check after a redesign, a new booking tool, or a major form change.

One person can run the keyboard and zoom checks, then ask another person to try a customer task. You might be surprised by the small things a fresh visitor notices, such as a phone number that looks like plain text but does not open when tapped.

W3C's Easy Checks are useful for an initial review, but they explicitly are not a complete evaluation. If your site is central to taking orders or serving customers, consider asking a qualified accessibility professional for a fuller assessment. In the meantime, a clear label, a visible focus marker, and an image description that explains the point can make a visit easier for real people today.