DEV Community

Roshan Madusanka
Roshan Madusanka

Posted on Edited on

The accessibility mistakes I keep finding on small business websites

I built a website accessibility scanner, and the first thing I did with it was point it at a lot of small business sites. Restaurants, dental clinics, a few agencies, a couple of gyms. 70 sites in total.

I expected a long, messy list of weird problems. What I got was the same six or seven mistakes, over and over. Different industries, different site builders, same issues.

That's good news, really. It means most of the damage comes from a small set of habits, and you can fix those in an afternoon. Here's what I found, roughly in order of how often I saw it.

1. Text that's hard to read

Low colour contrast was the most common problem by a distance. Light grey text on white. White text on a pastel button. A pale placeholder on a photo.

It's easy to miss when you're the designer, because you already know what the text says. WCAG asks for a contrast ratio of at least 4.5:1 for normal text and 3:1 for large text. Grey #999 on white is about 2.8:1, so it fails.

The fix is boring. Darken the text.#767676 on white is the lightest grey that still passes. Most brand colours need one step darker than you'd think for text, even if the lighter version is fine for a border or a background.

2. Images with no description

Missing alt text came second. Either the attribute isn't there at all, or it's there and says image1.jpg, which is worse than nothing because a screen reader reads it out.

<!-- Bad -->
<img src="IMG_4021.jpg">

<!-- Good: says what matters -->
<img src="IMG_4021.jpg" alt="Chef plating the lunch special at the pass">

<!-- Also good: decorative, so skip it on purpose -->
<img src="divider.png" alt="">
Enter fullscreen mode Exit fullscreen mode

The empty alt="" is not laziness. It tells assistive tech "this is decoration, move on." Use it for flourishes and dividers. If an image carries meaning, say what the meaning is, not what the file is.

3. Buttons and links with no name

This one surprised me by how common it was. A hamburger menu that's just an icon. A social link that's just a logo. A "close" button that's an X in a circle.

To a sighted person it's obvious. To a screen reader it's "button" or "link" with nothing after it.

<!-- Bad -->
<button><svg>...</svg></button>

<!-- Good -->
<button aria-label="Open menu"><svg aria-hidden="true">...</svg></button>
Enter fullscreen mode Exit fullscreen mode

If there's visible text, you don't need the aria-label. The text is the name. Only reach for ARIA when there's genuinely nothing to read.

4. Form fields without labels

A placeholder is not a label. It disappears when you start typing, it's usually low contrast, and a lot of screen readers don't announce it reliably.

<label for="email">Email address</label>
<input id="email" type="email" autocomplete="email">
Enter fullscreen mode Exit fullscreen mode

I saw contact forms with five fields and not one real label. These are the forms that are supposed to bring the business customers.

5. Keyboard users get lost

Try this on your own site right now. Put the mouse away and press Tab.

Can you see where you are? Can you reach the menu, the form, the buttons? Can you get out of that popup again?

The usual culprit is this line, copied from somewhere years ago:

*:focus { outline: none; }
Enter fullscreen mode Exit fullscreen mode

It removes the focus ring so things look "cleaner," and it makes the site close to unusable for anyone who doesn't use a mouse. Don't remove it. Style it:

:focus-visible {
  outline: 3px solid #1a56db;
  outline-offset: 2px;
}
Enter fullscreen mode Exit fullscreen mode

6. Two small things in the

These are quick, and I still found them missing all the time.

The page language. Without it, a screen reader may read your English page in the wrong accent, or the wrong language entirely.

<html lang="en">
Enter fullscreen mode Exit fullscreen mode

And the viewport. This one blocks people from zooming on a phone, which is exactly what people with low vision do:

<!-- Don't -->
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1, user-scalable=no">

<!-- Do -->
<meta name="viewport" content="width=device-width, initial-scale=1">
7. Headings that are just big text
Enter fullscreen mode Exit fullscreen mode

A lot of sites use <h3> because it looks the right size, or use a bold

where a heading should be. Screen reader users jump between headings to get around a page, the same way you skim one. If the structure is random, that map is useless.

Use one <h1>, then <h2> for sections, and <h3> inside those. Pick the level by meaning, then control the size with CSS.

What a scanner can and can't tell you

I should be honest about this part, since I built one.

Automated tools, mine included, run on top of the open source axe-core engine, and they only catch a portion of real problems. The usual figure is somewhere between a third and a half. A tool can tell you an image has no alt. It can't tell you whether the alt you wrote is actually useful. It can't tell you the tab order makes no sense, or that your error message is confusing.

So treat a scan as a starting point. It finds the cheap, obvious stuff quickly so you can spend your attention on the things only a person can judge. A five-minute pass with a keyboard and a screen reader (NVDA is free on Windows, VoiceOver is built into every Mac) will teach you more than any report.

If you only do three things

If this feels like a lot, start here:

Fix text contrast.
Give every image, button and form field a proper name or label.
Put the mouse away and make sure you can use the whole site with Tab.

That alone gets you past most of what I saw. [Add one line here about a real site you scanned that improved after a fix, if you have one.]

I turned my scanner into a free tool, Kerbly. Paste in a URL and it gives you the issues in plain English: kerbly.analytihq.com. I'd like to hear what you find on your own site, and which of these you've been guilty of. I've done most of them myself.

Top comments (0)