Website Accessibility for Small Businesses and the Key WCAG Points Explained Simply

Why accessibility matters for a small business

People with low vision, color blindness, hearing loss or limited hand control visit your site, and so does anyone squinting at a phone in bright sunlight. Many fixes for these visitors help everyone: readable text, clear buttons and forms that explain themselves.

There is also a legal side. In the United States, lawsuits over inaccessible websites have been brought under Title III of the Americans with Disabilities Act, and courts have not ruled the same way everywhere. Other countries have their own rules, and they vary by country and by type of business. You do not need to guess your exposure. The practical response is to build to a recognized standard and to fix problems when you find them. This article is not legal advice. If you have received a demand letter, talk to a lawyer.

What WCAG is, in plain terms

WCAG stands for Web Content Accessibility Guidelines. The World Wide Web Consortium publishes them, and the current versions are 2.1 and 2.2. Each requirement belongs to level A, AA or AAA. Level AA is the usual target for business websites and the level most often referenced in policies and agreements. The W3C overview of WCAG is the official source.

The guidelines group into four ideas:

• Perceivable. Visitors can see or hear the content in some form.
• Operable. The site works with a keyboard, touch or voice, and nothing demands fast reactions.
• Understandable. Language is clear, navigation is predictable and errors are explained.
• Robust. The code is clean and works across browsers and assistive technology such as screen readers.

The key points, explained simply

1. Describe meaningful images. Give informative photos a short text alternative that says what they show, such as "technician installing a heat pump outside a house." Decorative images get an empty text alternative so screen readers skip them. Avoid putting important words inside images.
2. Use enough color contrast. Normal text needs a contrast ratio of at least 4.5 to 1 against its background, and large text at least 3 to 1. Light gray on white can fail. Never let color alone carry meaning, as in "required fields are red."
3. Make everything work with a keyboard. A visitor should reach every link, menu, button and form field with the Tab key, see where they are through a visible focus outline and never get stuck. A "skip to main content" link at the top helps.
4. Use real headings and lists. One H1, then headings in order. Screen reader users jump from heading to heading the way sighted people scan a page.
5. Write links and buttons that say what they do. "Request a quote" works and "Click here" does not. Make buttons and links big enough to tap without hitting their neighbors. WCAG 2.2 level AA sets a minimum of 24 by 24 CSS pixels, and larger is better.
6. Label every form field. Placeholder text disappears when someone types, so keep a visible label. Error messages should say in words what went wrong and where.
7. Let people zoom. Enlarge the page until everything is twice as large. Text should stay readable and nothing should overlap or vanish.
8. Handle video, audio and motion with care. Provide captions or a transcript, avoid autoplay with sound and let visitors pause moving content.
9. Name the page. Each page needs its own descriptive title and the correct language set in the code.

A 20-minute self-check

You can find many problems without special tools.

1. Put the mouse aside. Tab through your home page and your contact form. Can you reach everything, see where you are and submit the form?
2. Zoom the browser in until everything is twice as large, then open the site on your phone in both orientations.
3. Check the contrast of your body text, buttons and footer links with a free contrast checker.
4. Submit your contact form empty. Do the messages tell you what to fix?
5. Run an automated checker, such as the audit built into Chrome called Lighthouse. Automated tools catch only part of the issues, so a clean report is not proof of accessibility.
6. Turn on a screen reader for a few minutes (VoiceOver on Mac and iPhone, TalkBack on Android, NVDA on Windows) and listen to your home page. Does the heading order make sense? Are the images described?
7. Write down what you found, fix the biggest barriers first and repeat the check after every redesign.

Overlays, widgets and where to get help

You will see tools that promise instant compliance with one line of code. A widget that adds a toolbar to the page does not repair problems in the underlying code, so treat it, at most, as an addition to fixing the page itself.

Better habits are simple. Ask your web designer to build and test against WCAG 2.1 or 2.2 level AA from the start, since that is easier than retrofitting. Give visitors a phone number or email address where they can report a barrier, and answer promptly when someone does. The official site of the U.S. Americans with Disabilities Act, ada.gov, is the place for the government's own information.

Accessibility also fits into the bigger picture of a good site. The small business website guide covers the basics, the website redesign checklist is a good moment to add accessibility to your list, and website speed and Core Web Vitals covers another quality check. The guide overview lists every topic.

If you want an outside look

The easiest time to build accessibility in is when a site is planned or rebuilt.

Frequently asked questions

Is my small business required to have an accessible website?

It depends on your country, your industry and who you serve, so there is no single answer. A practical target is WCAG level AA, and a lawyer who knows your situation can tell you more.

Which WCAG level should I aim for?

Level AA. Level AAA contains requirements that cannot be met for every kind of content, so it is not expected for whole sites.

Do I need an accessibility statement?

It is not required everywhere, but a short statement with a way to contact you is good practice. It shows visitors where to turn if they run into a barrier.

Can an automated scanner tell me if my site is accessible?

No. Scanners find some problems, such as missing text alternatives or low contrast, but they cannot judge whether a page makes sense with a keyboard or a screen reader. Combine them with the manual checks above.