Small businesses that offer goods or services online should make those experiences accessible to people with disabilities. The Department of Justice describes accessibility as an ADA responsibility for businesses open to the public, while also explaining that private businesses have flexibility in how they meet general requirements. This guide is general information, not legal advice.
WCAG 2.2 is a technical standard, not a legal guarantee
WCAG 2.2 is the current W3C recommendation and provides testable success criteria. It is the most useful technical reference for design, content and development work. Meeting a checklist does not by itself guarantee legal compliance in every jurisdiction or situation, and this article does not make that promise.
Why an automated scan is not enough
Automated tools can identify candidates such as missing labels, contrast errors or invalid markup. They cannot reliably decide whether alternative text communicates the right purpose, whether focus order makes sense, whether instructions are understandable, or whether a workflow works with assistive technology.
A practical remediation process
- Inventory the public templates, documents, media and third-party widgets.
- Prioritize high-risk and high-use paths such as navigation, forms, checkout, account access and support.
- Test with keyboard and assistive technology, not only an automated scanner.
- Fix shared components before isolated pages so the correction scales.
- Document owners, verification and a process for future content and releases.
Common gaps to examine
- Missing or unhelpful text alternatives for meaningful images.
- Insufficient contrast or information communicated by color alone.
- Unlabeled form controls, unclear errors and missing status announcements.
- Keyboard traps, invisible focus and controls with ambiguous names.
- Documents or third-party widgets that do not provide an equivalent accessible path.
When to involve legal counsel
Legal advice is appropriate when the business needs an interpretation of obligations, a response to a demand, contract language, or a jurisdiction-specific risk decision. A designer or scanner should not pretend to replace that advice.
Build an accessibility inventory before choosing fixes
List public templates, forms, checkout and account flows, PDFs, videos, embedded tools, mobile apps and third-party services. Record the owner, audience, traffic or business criticality, known barriers and the system that creates each item. This turns an abstract compliance concern into a manageable remediation program.
Prioritize barriers by impact and reach
- Start with paths needed to buy, apply, schedule, pay, access an account or request support.
- Fix shared navigation, form, dialog and design-system defects before page-by-page exceptions.
- Provide an accessible alternative when a third-party barrier cannot be corrected immediately, then track the vendor resolution.
- Document temporary measures, owners and review dates so a workaround does not become permanent by accident.
Accessibility statements should create a usable feedback path
A public statement can explain the organization’s commitment, current standard or policy, known limitations and a way to request help or report a barrier. Keep it accurate and update it when the program changes. Avoid declaring complete compliance unless the organization has evidence and legal guidance supporting that statement.
PDFs and downloadable documents need their own plan
Inventory forms, reports, menus, policies and other documents that customers need. Prioritize current and frequently used files, provide accessible HTML when practical, and establish an authoring and review process for new documents. An inaccessible PDF does not become usable because the surrounding webpage passes an automated scan.
Third-party tools remain part of the customer journey
Booking systems, payment tools, chat, maps, video players and consent controls can introduce barriers outside the core codebase. Include accessibility requirements in procurement, ask vendors for current conformance evidence, test the real integration, and define an escalation or replacement path.
Create ongoing governance
- Assign an accountable program owner and component or content owners.
- Add accessibility acceptance criteria to design, development, content and procurement work.
- Train the people who publish content and approve releases.
- Retest high-value tasks after major changes and on a scheduled basis.
- Track user-reported barriers through resolution without exposing personal information.
Understand the limits of this guide
ADA obligations and remedies depend on facts, jurisdiction and current law. WCAG is the strongest practical technical reference, but conformance is not a universal legal safe harbor. Counsel should interpret legal obligations, contracts, demand letters and jurisdiction-specific decisions. Design and engineering teams should provide accurate technical evidence rather than legal conclusions.
For implementation practices such as keyboard navigation, forms and media, continue with the accessible web design guide. For a scoped website implementation discussion, use web design services.
For the design and SEO overlap, see Accessible Web Design in 2026. For implementation scope, use web design services.
