A customer finds a local business online. The website looks polished, the services seem right, and the booking button is visible. But can the customer read the text, navigate the page, and complete the booking with assistive technology?
A new study suggests those questions deserve attention. On November 10, 2026, accessibility vendor Accessible published its Main Street Accessibility Report, reporting that 90.1% of 12,682 scanned U.S. small-business websites had at least one automatically detectable WCAG A or AA failure. The company attempted 13,735 sites and scanned 53,464 pages on November 9–10, 2026. These are the researcher’s results for its selected sample, not an official or representative count of all U.S. businesses.
The distinction matters: an automated finding is a starting point for review, not proof of a lawsuit or a complete assessment of a website. Conversely, a scan that detects no failures does not establish that a site is accessible.
What did the small-business study actually find?
Accessible reported that text contrast was the most common automatically detected failure: 71.5% of sites in its small-business sample had at least one detected contrast issue. Within the same sample, it reported a detected failure on 95.6% of 2,102 dental and medical sites and 80.8% of 3,665 restaurant sites. These industry figures describe the sites and pages studied, not every practice or restaurant in the country.
The researchers also reported structural indicators, such as missing main regions or top-level headings, separately as best-practice findings. They did not count those indicators as WCAG failures in the reported failure figures. Accessible sells accessibility services, so its report is useful primary research but is not independent of commercial interests. Review its methodology before comparing it with other studies.
Why can a good-looking page be difficult to use?
A page is experienced in different ways. A person with low vision might need stronger contrast or larger text. Someone using a keyboard needs a visible focus indicator and a logical route through controls. A screen reader user needs meaningful names, roles, headings, and feedback when the page changes.
Consider a pale gray appointment link on a white background. It may be easy to overlook, especially on a phone in bright light. Check the actual text and background colors—including hover, focus, and disabled states as applicable—against relevant WCAG criteria. For ordinary text, WCAG 2.2 success criterion 1.4.3 generally requires at least 4.5:1 contrast, with exceptions including large-scale text, which generally requires 3:1. Measure rather than judging by appearance alone.
Start with the task that matters most

A local business does not have to review every page at once to start learning where barriers are. Choose one important journey and follow it from beginning to end:
- Dental practice: find a service, locate the appointment form, select a time, and review the confirmation.
- Restaurant: select a location, navigate the menu, customize an item, and proceed to checkout.
- Retailer: search for an item, select an option, add it to the cart, and review the order.
These are suggested tests, not examples of businesses examined in the report. Try each journey using only a keyboard. Confirm that focus is visible, controls have clear names, users can recover from errors, and important status changes are perceivable. Then test with relevant screen readers and browsers. For restaurant-specific scenarios, see our restaurant online ordering guide.
What automated results can—and cannot—tell you

Automated tests can flag certain missing labels, contrast problems, and other detectable issues quickly. They cannot reliably determine whether a customer understands every instruction or completes a complex interaction. The U.S. Department of Justice’s web accessibility guidance recommends using manual checks alongside automated tools.
When a tool flags a result, record the page, component, test conditions, and affected user task. Have someone qualified verify it, prioritize fixes that block essential services, and retest the changed interaction. Our comparison of automated and manual testing explains the respective roles.
Five questions to ask your web team
- Can a customer reach and operate the main navigation and call-to-action without a mouse?
- Are text, labels, and error messages readable and understandable?
- Can someone using a screen reader identify each control and its state?
- Have booking, purchasing, or contact forms been tested from start to finish?
- Who owns issues in third-party booking, checkout, or payment tools, and when will fixes be retested?
These questions do not constitute a full WCAG audit. They help organize a first conversation. For a broader list, consult our small-business accessibility checklist.
What about legal requirements?
The DOJ explains that accessibility barriers can prevent people with disabilities from using goods and services offered by businesses online. Applicable obligations depend on the organization, the law, the jurisdiction, and the facts. WCAG is a technical standard; a particular scan score or a single fix is not a legal determination. Discuss legal questions with qualified counsel.
Turn a finding into a practical plan
Begin with the pages customers rely on most, document findings and ownership, fix underlying components, and retest. Revisit important tasks when the website, theme, content, or integrations change. An assessment should describe its scope and provide reproducible findings rather than promising that a website can never face a claim.
Want to know where customers may encounter barriers on your site? Contact ADA Access Group to discuss an accessibility assessment focused on your key customer journeys. Learn more about what an accessibility audit includes.
Research figures reflect the source’s stated sample and methodology. This article is general information, not legal advice.
Featured photo: Tim Gouw / Pexels.
