Basic Web Accessibility in Plain English for a Small Business Owner (No Specialist Needed)

You've heard your website should be "accessible," and you probably pictured an expensive audit, a specialist, and a checklist you can't even read. Good news: most of the benefit comes from a few simple decisions you can check yourself in an afternoon, without writing a line of code.

Accessibility isn't just "a site for people with disabilities." It means a site that works for someone on a phone in bright sunlight, an older customer who can't read light-gray text, or someone navigating by keyboard. In practice, more people end up calling you or filling in your form. In this article I'll show you exactly what to look at and what to fix, in the order that matters most.

What accessibility actually means (and why it affects you)

Web accessibility means your site can be used by as many people as possible, regardless of sight, hearing, mobility, or their context (cheap phone, weak signal, screen in direct sun).

This isn't about political correctness. It's very practical: every person who can't read the price, tap the button, or find your phone number is a lost customer. Most accessibility problems are really usability problems that affect everyone.

Another concrete benefit: Google "reads" an accessible site more easily. Clear text, properly described images, and a logical structure help SEO too, not just your readers. So you do the work once and solve two problems.

Text contrast — the cheapest win

The most common issue on small-business sites is light-gray text on a white background. It looks "elegant" on the designer's laptop, but becomes unreadable on a phone outdoors or for a tired pair of eyes.

Rule of thumb: dark text on a light background (or vice versa), no borderline shades. The WCAG standard asks for a contrast ratio of at least 4.5:1 for normal text — sounds technical, but you can check it for free.

• Search Google for "WebAIM contrast checker," enter your text and background color codes, and it tells you whether it passes.
• Pay special attention to small text: footers, prices, terms, buttons with thin type.
• Don't rely on color alone. If you mark an error only in red, someone who can't distinguish colors well won't see it — add text too ("Required field").

Alternative text for images (alt text)

Every meaningful image should have a short text description — "alt text." Screen readers use it for blind users, but it also shows up when the image fails to load (weak signal), and Google reads it for context.

How to do it well, with little effort:

• Describe what's useful in the image, briefly and naturally: "Two-tier cake with wild berries" — not "IMG_2043."
• For purely decorative images (a background texture), leave the description empty so it doesn't clutter the screen reader.
• Don't stuff in SEO keywords. Write it for a person who can't see the photo.

In most platforms (WordPress, Wix, any builder) there's an "Alt text" field right next to the image. It takes a few seconds per photo.

Buttons, links and forms anyone can use

This is where most conversions are lost, even when the rest of the site looks good.

• Buttons and links you tap with a finger need to be big enough and well-spaced. If you struggle to hit them on your phone, so does your customer.
• Link text should say where it leads: "See the menu" or "Call now," not "Click here." Someone browsing a list of links needs to understand without the surrounding context.
• On forms, every field needs a visible label (Name, Phone), not just gray placeholder text that vanishes once you start typing.
• Your phone number and address should be real text, not a picture. That way they can be tapped directly and read by any device.

A quick test: try moving through the page using only the Tab key. If you can reach the button and clearly see where you are, you're on the right track.

Common traps and how to know you're okay (no paid audit)

A few mistakes I see often:

• "Accessibility widgets" (that bar of icons promising to make your site accessible in one click). Most of the time they don't fix the real problems and sometimes make them worse. There's no magic button — fix things at the source instead.
• Text laid over busy images with no contrast.
• Font too small. Below 16px for body text gets hard to read on a phone.
• Video that autoplays with sound.

How to check yourself, for free: open the site on a phone, in daylight; enlarge the browser text and see if the layout breaks; tab through the page; run an automated test (search for "WAVE accessibility" or use the "Accessibility" report in Lighthouse, in Chrome). It won't catch everything, but it shows you the easy wins.

If you'd like, at MPO Web Studio we build a free demo of your site, already set up correctly for contrast, structure and mobile — you see it before paying anything, we work remotely across the country, and we tell you transparently what it costs. Message us on WhatsApp and we'll do a quick check of what you have now.