The Small Business Owner's Guide to Website Accessibility

When an owner hears that the business website might be a legal liability, the first move is rarely to open a technical specification, and that instinct is sound. WCAG, the Web Content Accessibility Guidelines, was written for developers and accessibility practitioners. Reading it cold is confusing even for people with technical backgrounds.

What an owner needs is a clear answer to four questions. What is website accessibility? Why does it matter for a business? What creates legal exposure? And what does a sensible path to addressing it look like?

This guide covers all four in plain language, without overstating the risk or understating it.

What Website Accessibility Means

Accessibility, for a website, means that people with disabilities can perceive, navigate, and interact with the content.

That covers a wider population than most owners picture. The CDC reports that more than 1 in 4 U.S. adults have some type of disability. That figure covers all disability types, and not all of them affect web use. A substantial portion do. The relevant groups include people who are blind or have low vision, people who are deaf or hard of hearing, people with motor disabilities that prevent mouse use, and people with cognitive or neurological conditions that affect how they process information.

Assistive technology bridges the gap between an inaccessible site and a user who needs it to work. Screen readers translate visual content into audio or braille output. Switch devices allow navigation without a standard keyboard or mouse. High-contrast display settings adjust visual presentation. These tools depend on websites being built to work with them, structurally as well as visually.

A site that looks usable to a person without disabilities may be unusable to a screen reader user, a keyboard-only navigator, or someone with low vision who needs sufficient color contrast to read at all. The gap is not always visible, which is part of why it is easy to miss.

Why WCAG Exists and What It Requires

The World Wide Web Consortium (W3C) developed WCAG to provide a consistent, testable standard for web accessibility. It is organized around four principles: content must be perceivable, operable, understandable, and robust. The principles become specific success criteria at three levels: A, AA, and AAA.

This guide recommends WCAG 2.2 AA as the target. Regulations that cite WCAG currently point to version 2.1, and a site that meets 2.2 AA also meets 2.1 AA, so building to 2.2 covers both. Level AA is also the baseline accessibility professionals use for audits and remediation work.

Most of the criteria reduce to a small number of concrete requirements.

Every image that carries meaning needs a text description a screen reader can communicate. Decorative images should be marked so screen readers skip them. An image that serves as a button or link needs alt text describing its function, not just its content.

Every action a mouse user can take, such as clicking links, submitting forms, opening menus, or closing modals, must work with a keyboard alone. Tab order should follow the visual layout. Focus indicators, the visible outline showing where keyboard focus sits, must not be hidden.

Normal text needs a contrast ratio of at least 4.5:1 against its background. Large text, meaning 18 point or 14 point bold, needs 3:1. This catches a common design choice, light gray text or thin type on colored backgrounds, that looks elegant but is hard to read with low vision.

Every form field needs a label that is programmatically associated with it, not only visually adjacent. “Name” printed above a text input is not sufficient if the label is not connected to the input in the code. Without that connection, a screen reader user hears “text field, blank” with no hint of what to type.

Video with spoken content needs captions. Auto-generated captions from YouTube, Vimeo, or social platforms meet the standard only when they are accurate.

Each page needs a unique, descriptive title. Headings should be used structurally, for organization and not styling, because skipping levels (H1 straight to H4, for example) confuses screen reader users who rely on headings to move through a page.

When a form produces an error, the message must identify the field and describe what is wrong. A red border with no text is not sufficient.

This list is partial. It covers the part of the standard that most service business websites run into in practice. The post on five accessibility mistakes that service business sites make goes deeper on the ones that are easiest to miss.

The Legal Picture Without the Panic

Title III of the Americans with Disabilities Act covers businesses open to the public, and the Department of Justice applies it to websites. Its 2022 web guidance says the ADA’s requirements apply to all the goods, services, privileges, or activities that public accommodations offer, including online. The same guidance says no regulation sets a specific technical standard for Title III websites and names WCAG as helpful guidance.

That distinction matters because of a rule that is easy to confuse with it. The DOJ’s April 2024 rule sets WCAG 2.1 AA for the websites of state and local governments under Title II. It does not apply to private businesses. An April 2026 interim final rule moved that rule’s compliance dates to April 2027 for larger governments and April 2028 for smaller ones. Neither the rule nor the extension changes what Title III requires of a business.

The full picture is in ADA Title III and Your Website. Small service businesses do receive demand letters, and sites with working forms, booking systems, or other contact mechanisms alongside identifiable, unaddressed barriers are the likeliest targets. A business that has audited its site, identified what is present, and is working through remediation, with the records to show it, is in a stronger position than one that has done nothing. This describes posture, not a legal guarantee.

For businesses with customers in Europe, the European Accessibility Act (EAA) is a second framework, covered in the European Accessibility Act post. It applies from 28 June 2025, and its scope is limited to listed products and services provided to consumers, such as e-commerce, consumer banking, e-books, and passenger transport services. Microenterprises providing services are exempt, and the Directive defines a microenterprise as fewer than 10 persons with turnover or a balance sheet total of no more than EUR 2 million. Many small service businesses will fall outside the Act, but any business selling to European consumers should check its own position.

What Does Not Work

Accessibility overlays, the JavaScript widgets sold under names like AccessiBe and UserWay, do not establish compliance. The Federal Trade Commission alleged that accessiBe’s widget did not make all user websites WCAG-compliant. The final order carries a $1 million payment.

Why this is the case technically is covered in Why an Accessibility Overlay Is Not a Compliance Solution. The short version is that overlays operate on top of the rendered page and cannot fix code-level barriers. They give the appearance of action without the substance of remediation.

Relying on an overlay is a common mistake. It trades a solvable problem for a false sense of security.

The Business Case Beyond Legal Compliance

Legal exposure is the entry point for most small business owners. It is not the only reason to take accessibility seriously, and the business case for an accessible website is covered separately.

With more than 1 in 4 U.S. adults having some type of disability, some prospective clients will meet barriers on a site that was not built with them in mind. An inaccessible site loses inquiries that never show up in analytics. A visitor who cannot complete a contact form leaves quietly, and nothing records why.

There is a modest overlap with search work. Heading structure, alt text, and descriptive link text help both screen readers and search crawlers. Good markup produces that overlap as a side effect.

What a Sensible Path Forward Looks Like

Accessibility work has three phases, in order. Skipping to the second or third without the first is a common source of wasted effort.

Phase 1 is the audit. Before remediating anything, the business needs to know which barriers exist. An audit combines automated scanning, which catches issues that can be detected programmatically, with manual testing using assistive technology. Automated scanning covers a lot of ground. Deque’s analysis, a vendor study of over 2,000 audits covering over 13,000 pages and nearly 300,000 issues, found its automated testing covered 57 percent of issues by volume. The rest needed a person navigating with a screen reader, a keyboard, and a magnification tool. The audit output should be a prioritized list of specific failures, not a generic score.

The audit also sets a baseline. Whatever remediation follows, the business has a record of what was present at the start, which may help show good-faith effort if a legal issue arises.

Phase 2 is remediation. Fix what the audit found, in order of priority. Some issues are quick: adding alt text, improving a contrast ratio, adding a missing form label. Others take developer time, such as restructuring navigation, rebuilding a modal to manage keyboard focus, or reworking a form that was not built with accessibility in mind. A good audit prioritizes by impact and effort so a long list does not stall the work.

Phase 3 is ongoing monitoring. Websites change. Pages are added, plugins update, and redesigns introduce new components. Accessibility is a practice that needs maintaining as the site evolves. Quarterly or semi-annual audits of high-traffic pages, plus accessibility checks built into new development, are how accessible sites stay accessible.

Where to Start

For most small service businesses, the starting point is to find out what the site has.

That means a full audit that names the barriers present, which ones carry the most exposure, and what a practical remediation sequence looks like. A vendor selling an overlay does not provide that, and neither does a free automated scanner that returns a letter grade.

That knowledge is useful whether or not the business acts on it immediately. It replaces uncertainty with a clear picture and supports decisions based on what is present.

If you are unsure where your site stands, a 15-minute conversation with COREaccess™ is a reasonable way to start.