Website accessibility basics for small businesses

Updated September 26, 2026

Can every customer read your services and ask for an appointment on your website? Someone may use enlarged text, a keyboard instead of a mouse, or a screen reader that reads the page aloud. Basic accessibility work starts by making those ordinary customer tasks possible.

Make your text readable without extra effort

Start with your phone number, opening hours, service descriptions, and form instructions. If you have to lean toward the screen to read them, customers may struggle too. Use a plain font with comfortable spacing and avoid putting essential information in tiny print.

Check the text on a phone as well as a computer. A heating contractor's emergency instructions should not disappear beneath a large photograph. A cleaning company's list of excluded tasks should be just as readable as the heading advertising the service.

Then enlarge the page using your browser's zoom control. W3C's text resizing guidance calls for text to reach 200% without losing content or functionality, with specified exceptions such as captions and images of text. Look for overlapping words, cut-off buttons, and forms that become unusable. W3C's resizing explanation describes the standard.

Use meaningful headings such as “What move-out cleaning includes.” They help break up a long page and make the information easier to navigate. For more everyday checks, see building your small business website for phones first.

Choose colors that keep information visible

Pale gray text on white can look tidy while being hard to read. Text over a jobsite photograph is another common trouble spot because the background changes behind each word.

Ask your website provider to measure color contrast rather than judging it by eye. W3C's Level AA minimum for ordinary text is 4.5:1. Large text has a different threshold, but using strong contrast throughout is a practical starting point. The W3C contrast guidance explains the thresholds and exceptions.

Check the small parts of the page too:

• The words inside your estimate button.
• The labels and instructions beside form fields.
• Links inside paragraphs.
• Opening hours in the footer.
• Error messages after an incomplete form submission.

Do not rely on color alone to explain a problem. “Please enter your email address” gives the customer something to fix; a field that merely turns red does not. Underlined links are also easier to recognize than links distinguished only by a subtle shade change.

Describe images according to their purpose

Alternative text, often called alt text, gives a text alternative to an image. It should communicate what matters about that image in that particular place. It is not a space for a string of town names and search terms.

For a roofer's project page, “New charcoal shingles on a detached garage” is more useful than “Roofing photo.” For a cleaning company's before-and-after pictures, describe the meaningful difference, such as mineral buildup on a shower door and the cleaned glass.

Some pictures are only decoration. They should be marked as decorative, with an empty text alternative, so a screen reader can skip them. An image that acts as a button needs an accessible description of its action. W3C's image decision guide shows how purpose changes the right approach.

Keep prices, service areas, and booking instructions as real page text, even when you also use them in a promotional image. Review taking useful business photos with your phone with those descriptions in mind. A photo and a clear caption can explain a job without asking the picture to carry every detail.

Try your website without touching the mouse

On a computer, use the keyboard to move through your site. Start with Tab to move forward and Shift plus Tab to move backward. Links and buttons should show where you are, usually with a visible outline or another clear highlight.

Try opening the navigation menu, following a service link, and reaching the contact form. Depending on the control, Enter, Space, or arrow keys may be needed. You should be able to complete the task and leave any menu or pop-up without getting stuck.

Keyboard operation matters for people who cannot use a mouse and for people using other assistive tools. W3C's keyboard guidance explains the requirement and its limited exceptions.

Give your provider a concrete report: “I can reach the menu button with Tab, but I cannot open it with the keyboard.” That is more useful than “The menu feels wrong.” Repeat the test on outside booking tools too, since customers still have to use them to finish an appointment.

Make contact forms understandable from start to finish

Every field needs a clear label that remains understandable while someone fills it in. Use visible labels such as “Email address” and “ZIP code,” not just a faint hint inside an empty box. Ask your provider to confirm that each label is properly connected to its field for assistive technology. W3C's form labeling guide explains why that connection matters.

Tell people which details are required before they submit. A lawn care estimate might need the service address and requested work, but you can probably ask about gate access during the follow-up. Fewer unnecessary questions leave fewer obstacles to completing the form.

Test a mistake on purpose. Leave a required field blank and check whether the message explains the problem. Make sure the form keeps the details already entered and gives a clear success message after a valid submission.

Provide another contact option, such as a phone number, but keep working on the form itself. Someone who cannot use a phone call still needs a usable way to ask for service. See contact forms that actually get filled out for a practical field-by-field review.

Review a complete customer visit

Pick a realistic task instead of inspecting random pages. For example, act as a customer who needs a leaking faucet repaired, lives near the edge of your service area, and wants to request an appointment.

Find the service, confirm the town is covered, and send a clearly labeled test inquiry. Repeat with enlarged text and keyboard navigation. Check that the inquiry arrives where you expect. An accessible form is only useful if the request reaches someone who can respond.

Keep a short fix list with the page, the action attempted, and what failed. Address blocked tasks first, then repeat those checks after repairs. W3C cautions that its Easy Checks are an initial review, not a complete accessibility evaluation. Use a qualified accessibility reviewer when you need a fuller assessment.

Frequently asked questions

Is a mobile-friendly website automatically accessible?

No. A page can fit a phone screen while still having unlabeled fields, poor contrast, or a menu that cannot be used with a keyboard.

Will an accessibility scan find every problem?

No single automated check can tell you whether every customer can complete a task. Combine tools with manual checks and, where possible, feedback from people who use assistive technology.

Do these checks prove my site meets legal requirements?

This guide is a practical starting point, not a legal determination. Ask a qualified lawyer about obligations that apply to your business and use an accessibility specialist for a full technical evaluation.

Should I fix everything at once?

Start with anything that prevents someone from reading essential information or contacting you. Keep the remaining issues on a written list and check new pages and features as you add them.

The short version

Make essential information readable, describe useful images, label forms, and test your site with a keyboard. Follow a complete customer task to find barriers that a quick glance misses. Keep checking after website changes.

If you want someone to handle website changes, Front Step Sites includes two change requests a month on the $99 annual plan, made within two business days.