Skip to content
Saturday, November 21, 2026Newsletter
Advertisement
Website & Digital Presence

WCAG Compliance Checklist for Small Business Websites

Learn what WCAG compliance means for your small business website, where your legal exposure lies, and how to fix the most common barriers.

By

Founder

7 min read

ShareLinkedInXEmail
Photograph: Ruler and laptop on a desk (Unsplash)
Photo: Oli Dale olidale / Wikimedia Commons, CC0 1.0. Cropped from the original.

If you run a small business website, working through a wcag compliance checklist small business website owners can actually use is worth your time right now. Courts have consistently ruled that ADA Title III covers commercial websites, and demand letters to small businesses have become routine. This is not a problem limited to large retailers or service chains.

After reading, you will know which accessibility barriers appear most often, how to check for them without hiring a developer, and which fixes you can make yourself this week. The goal is a practical starting point, not a legal brief. You do not need to rebuild your site to close the most common gaps.

What WCAG Compliance Means for Your Website

WCAG stands for Web Content Accessibility Guidelines, a set of technical standards published by the World Wide Web Consortium. They define how websites should work for people who use screen readers, keyboard-only navigation, or other assistive tools.

The guidelines are organized around four principles: content must be Perceivable, Operable, Understandable, and compatible with assistive technologies. Each principle breaks into specific success criteria. Some criteria are straightforward, such as requiring sufficient color contrast between text and its background (ADA.gov). Others are more technical, covering how page elements communicate their purpose to assistive software.

Duplicate ID values in your page code, for example, can cause screen readers to misread form fields or buttons. WCAG connects to legal exposure because the Americans with Disabilities Act has been interpreted by courts and the Department of Justice to cover private business websites. Size does not create an exemption. A small retail shop or a local services firm faces the same baseline expectations as a large corporation.

Advertisement

You do not need to understand every success criterion before you start. Most real-world problems cluster around a short list of common failures, and fixing those moves you meaningfully closer to compliance.

Courts have applied ADA Title III to websites even though no final federal rule specifically governs them. The absence of a published rule does not protect you. What triggers legal risk in practice is a demand letter, not a government audit. A plaintiff's attorney finds a site with obvious failures, sends a letter, and demands remediation plus fees.

Advertisement

The regulation's readily achievable standard takes business resources into account, which gives smaller organizations more flexibility in how they approach barrier removal. During the Title III rulemaking, the Department of Justice considered whether a formula for barrier removal would give small businesses an incentive to plan for accessibility, though it ultimately did not adopt such a formula (ADA Title III regulations). Congress also directed agencies to consider alternative compliance paths for small businesses specifically (ADA Title III regulations). That flexibility matters when you are budgeting a remediation project.

Many small businesses settle demand letters quickly because the cost of litigation exceeds the cost of fixing the site. Your concrete step this week: run a free automated scan on your homepage and document the failures it finds. That record shows good-faith effort, which courts weigh when assessing whether barrier removal was readily achievable.

Advertisement

Five Common Small Business Website Failures

Automated scans flag the same issues on most small business sites. Here are the five failures that appear most often, in the order you should address them.

  • Missing alt text on images. Write a short description of what each image shows or does. Decorative images get an empty alt attribute so screen readers skip them.
  • Low color contrast. Text that blends into its background is hard to read for people with low vision or color blindness. Test foreground and background color pairs with a free contrast checker before you publish changes.
  • Unlabeled form fields. Every input field needs a visible label above or beside it. A placeholder inside the field disappears when the user starts typing and does not count as a label.
  • Missing keyboard navigation. Every link, button, and form control must work with the Tab key alone. Users who cannot operate a mouse are locked out if any control requires a click.
  • Auto-playing video or audio. It disorients screen reader users whose software suddenly competes with your audio. Disable autoplay or add a prominent pause control at the top of the page.

None of these fixes require a full site rebuild. A developer can often resolve all five in a single focused session. Prioritize the page where most visitors contact or buy from you first.

Advertisement

Free Tools to Run a WCAG Compliance Checklist Today

Start with WAVE (Web Accessibility Evaluation Tool) or Axe, both free browser-based scanners. Run either one on your contact page or checkout page first. Each tool highlights missing alt text, low-contrast text, and form fields without labels. The results appear as icons overlaid on your live page, so you see exactly where each problem sits.

What automated tools miss matters as much as what they catch. They cannot judge whether an alt text description is meaningful, only that one exists. They will not catch a confusing navigation order that a keyboard user would struggle with. Plan to do a quick manual check after any automated scan: tab through the page with your keyboard and watch where the focus lands.

Advertisement

Section 508 of the Rehabilitation Act set federal standards for accessible information and communication technology, and those standards align closely with WCAG (ADA.gov). The GSA runs Section508.gov, which offers free tools and training you can use even if your organization is not a federal agency (ADA.gov). After scanning, export or screenshot the results. A developer can sort findings by severity and work through the critical ones in priority order, starting with your highest-traffic page.

Building a Remediation Roadmap Without a Full Rebuild

Once you have a list of findings, resist the urge to fix everything at once. Group issues into three buckets: critical, serious, and minor. Critical issues block users entirely, such as a form with no labels or a video with no captions. Serious issues create significant friction. Minor issues are polish.

Start with your highest-traffic pages and clear the critical bucket first. That work alone moves the needle most for the most people. Document every change you make, including the date, the page, and what was fixed. That record demonstrates good-faith effort if a complaint ever arises.

Set a realistic pace. A small site can often clear its critical issues in a few focused work sessions. Larger sites may need a phased schedule spread across several months. Build a simple tracking sheet with columns for page, issue type, severity, assigned to, and date resolved. Review it monthly and add new findings from periodic rescans.

Advertisement

Accessibility is not a one-time project. Browsers update, plugins change, and new content gets added. Treat it as ongoing maintenance, the same way you treat security patching. If your site runs on a platform like WordPress, adding new plugins or themes can introduce new barriers, so rescan after major changes.

Advertisement

What to Document to Show Good-Faith Effort

Keep a simple accessibility file in a shared folder your team can find. Save three things at minimum: dated scan reports from WAVE or Axe, a short log of what you fixed and when, and a written accessibility policy or statement posted on your site.

The scan reports prove you looked. Run them at least quarterly and name each file with the date. The fix log does not need to be formal. A spreadsheet with columns for the issue, the page, the fix applied, and the date completed is enough.

The policy statement signals intent. It should say that you are actively working toward WCAG 2.1 Level AA conformance and provide a contact method for users to report barriers. If you receive a demand letter, your goal is to show a pattern of active effort, not perfect compliance. Courts and plaintiffs' attorneys look for whether a business ignored the problem or was working on it. These records answer that question directly.

Assign one person to own the file. Review it when you add new pages or change your site platform. Treat it the same way you treat your security patch log: routine work that is worth its weight if something goes wrong. For more on keeping your site working for visitors, see our post on call tracking for your small business website.

Start with the highest-return fix: add alt text to every image, check your color contrast, and label every form field. Those three changes address the most common barriers without touching your site's structure or design. If you want help reviewing your site or building a remediation plan, see our website development services and managed website offer.

Book a free 30-minute call with Joshua to talk through what your site needs and where to start.

Frequently asked questions

Do I need to rebuild my entire website to fix accessibility problems?
No. The most common barriers can often be resolved by a developer in a single focused session without touching your site's structure or design.
Where should I start if I want to check my site today?
Run a free automated scan on your contact page or checkout page first, then tab through the page with your keyboard to catch issues the automated tool may miss.
What should I do if I get a demand letter?
Your goal is to show a pattern of active effort rather than perfect compliance. Dated scan reports, a log of fixes, and a written accessibility statement on your site all demonstrate that you were working on the problem rather than ignoring it.
Does being a small business protect me from ADA Title III claims?
Size does not create an exemption. The readily achievable standard under Title III does take business resources into account, which gives smaller organizations more flexibility in how they pace remediation, but it does not eliminate the obligation.

Sources

  1. Some criteria are straightforward, such as requiring sufficient color contrast between text and its background (ADA.gov). ada.gov (accessed 2026-11-19)
  2. During the Title III rulemaking, the Department of Justice considered whether a formula for barrier removal would give small businesses an incentive to plan for accessibility, though it ultimately did not adopt such a formula (ADA Title III regulations). ada.gov (accessed 2026-11-19)
  3. Congress also directed agencies to consider alternative compliance paths for small businesses specifically (ADA Title III regulations). ada.gov (accessed 2026-11-19)
  4. Section 508 of the Rehabilitation Act set federal standards for accessible information and communication technology, and those standards align closely with WCAG (ADA.gov). ada.gov (accessed 2026-11-19)
  5. The GSA runs Section508.gov, which offers free tools and training you can use even if your organization is not a federal agency (ADA.gov). ada.gov (accessed 2026-11-19)
Advertisement

Is your website doing its job?

Book a free 30-minute call. We will look at your current site together and tell you honestly what to fix, patch or replace.

Book a free website review

Related service: Website & Digital Presence

Junious Digital Labs logo

Joshua Junious

Founder of Junious Digital Labs, a veteran-owned IT consultancy. Army National Guard veteran and former IT director. About Joshua

Reach readers across the Junious Media Network. Advertise with us →