Website Accessibility Basics Every Small Business Should Know

Website accessibility means making a site usable by people with disabilities, including people who use screen readers, keyboards instead of a mouse, magnification, voice input, or other assistive technology.

For a small business, the practical starting point is to make sure the core customer journey — reading the offer, navigating, completing forms, booking, buying, or contacting the business — works for more people.

Accessibility is both a usability issue and a legal issue

In the United States, the Department of Justice says the ADA's nondiscrimination and effective-communication requirements apply to the goods and services public accommodations offer through websites.

Its current web accessibility guidance also makes an important distinction: for private businesses, DOJ has not issued one detailed technical regulation that says every business website must meet one specific WCAG version. Instead, it points to standards such as WCAG as useful technical guidance.

Do not treat an automated “ADA compliant” badge as a complete legal answer. Accessibility requires technical work, content work, testing, and maintenance.

Use WCAG as the practical technical benchmark

The Web Content Accessibility Guidelines, or WCAG, are published by W3C's Web Accessibility Initiative.

WCAG 2.2 is organized around four principles:

• Perceivable: people can access the information
• Operable: people can use the interface
• Understandable: content and controls make sense
• Robust: the site works with assistive technologies and user agents

For most business websites, Level AA is the practical target teams discuss when planning accessibility work.

Make the whole website usable with a keyboard

A visitor should be able to move through the site without relying on a mouse.

W3C's current keyboard guidance says functionality should be operable through a keyboard interface except where the underlying task genuinely depends on path-based movement.

Test:

• Main navigation
• Dropdown menus
• Buttons
• Forms
• Accordions
• Tabs
• Popups
• Booking widgets
• Checkout controls

Press Tab through the page. You should always be able to see where focus is, activate controls, and escape menus or dialogs without getting trapped.

Keep visible focus states

Keyboard accessibility is not enough if the visitor cannot see which element is selected.

A visible focus indicator might be an outline, border, background change, or strongly contrasting highlight.

Do not remove browser focus outlines unless you replace them with something equally clear.

Check text and interface contrast

Low contrast is easy to create accidentally.

WCAG Level AA requires at least 4.5:1 contrast for normal text and 3:1 for large text, subject to defined exceptions.

W3C also requires important non-text interface components and graphical information to reach 3:1 contrast against adjacent colors where the criterion applies.

Check body copy, navigation, form labels, buttons, text over images, error messages, input borders, and focus indicators.

Write useful alt text for informative images

Images need different treatment depending on why they exist.

W3C's current images tutorial says informative images should have text alternatives that communicate the essential information or function.

A decorative image should usually use empty alt text — alt="" — so a screen reader can ignore it.

Do not turn alt text into a place to repeat SEO keywords.

Give every form control a real label

Contact, booking, and checkout forms are often where accessibility failures become lost enquiries.

W3C's form-label guidance recommends labels that identify the purpose of text fields, checkboxes, radio buttons, and other controls.

Use a visible label such as:

Email address

rather than relying only on placeholder text.

W3C's form instructions guidance also recommends explaining required fields, expected formats, and other restrictions before users run into errors.

Use headings to create real structure

A page should not merely look like it has sections. The underlying heading structure should reflect them.

Use one clear H1, H2s for major sections, and H3s for subsections where needed.

Do not choose heading tags only because of their default font size.

A logical hierarchy helps screen-reader users navigate and makes the page easier for everyone to scan.

Do not use color as the only signal

Color can reinforce meaning, but it should not carry the whole message.

Avoid:

• Required fields identified only in red
• Errors shown only with a red border
• Selected states distinguished only by color
• Charts where categories are separated only by hue

Add text, icons, labels, patterns, or another visual cue.

Make links and buttons descriptive

A visitor should understand what an action does.

Prefer:

• View Website Pricing
• Book a Consultation
• Download the Accessibility Checklist
• Read the Case Study

over repeated labels such as Click here, More, or Go.

Clear action labels improve accessibility and conversion because they reduce uncertainty.

Test the real customer journey

Accessibility problems often hide inside third-party tools.

Test contact forms, booking widgets, payment flows, cookie controls, chat widgets, popups, embedded maps, and account logins.

A homepage can look excellent while the booking or enquiry process is unusable by keyboard.

Automated scanners can help find some issues, but they do not replace manual testing.

The ACCESS framework

Use ACCESS for a practical small-business review:

• A — Alternatives: Do meaningful images and media have appropriate alternatives?
• C — Contrast: Can text, controls, and important visual information be seen clearly?
• C — Controls: Can interactive elements be used without a mouse?
• E — Errors: Are form requirements and mistakes explained clearly?
• S — Structure: Are headings, labels, and relationships meaningful?
• S — Steps: Can a visitor complete the full customer journey?

10-point website accessibility checklist

Before launch or after a redesign, check:

1. Can the main navigation be used with a keyboard?
2. Is keyboard focus always visible?
3. Does normal text meet appropriate contrast requirements?
4. Do buttons and important controls have enough visual contrast?
5. Do informative images have useful alt text?
6. Are decorative images ignored appropriately?
7. Does every form field have a meaningful label?
8. Are errors and required formats clearly explained?
9. Is the heading structure logical?
10. Can someone complete the main enquiry, booking, or purchase flow without a mouse?

Accessibility is not a one-time checkbox. New pages, forms, plugins, and content can introduce new barriers.

If your current website needs a practical accessibility review alongside usability, mobile, and conversion issues, Veil Vertex's free tailored website audit can identify the highest-impact problems first. For a broader rebuild, the current Managed Website plan includes responsive design, hosting, monitoring, and ongoing technical maintenance.