Website accessibility compliance (ADA): What businesses need to know

ADA website compliance isn’t a design preference; it’s about making digital services accessible to people with disabilities. Website accessibility compliance under the ADA means addressing the law’s nondiscrimination and effective communication requirements online, even though the ADA itself doesn’t set detailed technical standards for websites. Many private organizations use WCAG 2.1 Level AA as a practical benchmark for building accessible websites.

It’s understandable to look for one rule that settles the question. A more useful approach is to understand which organizations and digital experiences may be covered, how third-party content can affect access, and what an accessibility audit can reveal. This article explains the legal framework and practical steps for including accessibility in website design, testing, and maintenance.

What is ADA compliance for a website?

The ADA doesn’t set detailed technical website standards, so organizations often use WCAG 2.1 Level AA as a practical benchmark. An inaccessible website can prompt complaints or lawsuits, with remediation or other legal relief among the possible consequences.

WCAG as an Accessibility Benchmark

The Web Content Accessibility Guidelines (WCAG), developed by the World Wide Web Consortium (W3C), provide technical criteria for digital accessibility. They matter because they translate the broad aim of access for people with disabilities into testable expectations for pages, forms, and media. A visual review alone may miss whether screen readers can interpret a page or keyboard users can reach essential controls.

WCAG Conformance Levels and POUR Principles

WCAG groups its success criteria into three conformance levels: Level A, the lowest; Level AA; and Level AAA, the highest. Its four principles are Perceivable, Operable, Understandable, and Robust, often shortened to POUR. Together, these principles help teams assess whether visitors can perceive information, operate controls, understand content, and use assistive technologies to interpret it.

WCAG 2.1 Level AA

WCAG 2.1 Level AA is a commonly used accessibility benchmark for private organizations working toward ADA compliance. Its criteria address practical barriers, including text contrast: standard text needs a contrast ratio of at least 4.5:1, while large text needs at least 3:1. Content should also remain usable when enlarged up to 200%. These checks apply to real tasks, not just a homepage’s appearance.

WCAG and Section 508 Guidance

Section 508 of the Rehabilitation Act of 1973 addresses access to information and communication technology, including digital content. It applies to U.S. government agencies and organizations receiving federal funding, and its technical requirements incorporate WCAG conformance. For other businesses, WCAG remains a useful reference: it gives designers and developers a shared framework for evaluating website features and content.

WCAG includes over 70 success criteria, so conformance involves more than adding an accessibility widget or adjusting a single screen. For example, a visitor may need to navigate a booking form by keyboard, enlarge instructions without losing functionality, or understand a video through captions. The same access considerations can shape a website, web app, or mobile app. Review key user journeys, including navigation, forms, and media, against relevant criteria; then document issues and remediation so teams can track what changed. A clear view of measurable digital results can help teams connect improvements to the experience visitors actually encounter.

ADA coverage of public-facing businesses’ websites

Coverage depends on the organization and service, not simply on whether a website exists. Title II addresses state and local governments; Title III concerns businesses open to the public.

Organizations and Digital Services Covered

Title II applies to state and local governments’ programs, services, and activities, including those delivered online. Title III prohibits discrimination in places of public accommodation, which can involve access to a business’s digital services. Small businesses and private companies aren’t categorically exempt based on size or revenue. Assess the public service a visitor needs, not just the organization’s headcount.

For example, someone may need a public-facing website to learn about a service, complete a transaction, or communicate with an organization. On e-commerce websites for business, a digital barrier can obstruct access even when the same service is available in person. How the ADA applies to a specific private website depends on the relationship between its online content and the business’s public-facing services.

ADA Coverage of Websites and Digital Content

ADA coverage can extend to web content and digital services when barriers prevent people with disabilities from accessing an organization’s services. The U.S. Department of Justice has consistently taken that position since 1996. That matters beyond desktop pages: websites, web apps, mobile apps, and online content can all shape how a person engages with a business or government service.

A booking form, account portal, or service information page may be part of that experience. Review the visitor’s full journey, including linked digital tasks, rather than judging only the homepage. A polished screen doesn’t ensure access if someone can’t complete the same essential task.

Title II Deadlines and Entity Thresholds

For state and local governments, Title II includes technical requirements and compliance deadlines. In early 2024, the U.S. Department of Justice issued a Title II rule establishing WCAG 2.1 AA as the website compliance standard for state and local government entities. The Federal Register published the U.S. Department of Justice’s final rule updating its ADA Title II regulations on April 24, 2024.

Deadlines depend on the covered government entity. On April 17, 2026, the U.S. Department of Justice issued an interim final rule extending local governments’ website accessibility compliance deadlines by one year. Special district governments must comply by April 26, 2028. These dates concern government entities; they aren’t a general deadline for private businesses.

Website Accessibility Laws and Regulations

Which laws require website accessibility under the ADA? Title II covers state and local government services, while Title III prohibits discrimination in places of public accommodation. The U.S. Department of Justice interprets the ADA’s nondiscrimination and effective communication provisions as applying to web accessibility, although the ADA doesn’t set detailed technical website standards for private organizations.

For a private company, the absence of a Title II-style technical rule doesn’t create a blanket exemption. The DOJ’s position and the connection between online content and public services matter when assessing exposure. Make the legal distinction operational: identify which digital services support access, then prioritize barriers that block customers from using them. Thoughtful website design decisions can account for accessibility as part of the user experience.

Accessibility requirements for third-party content

Embedded tools and media can create barriers even when your own pages work well. ADA obligations depend on the organization and service, but third-party content still warrants a practical accessibility review.

Do requirements differ by state or industry? The ADA distinguishes government services under Title II from public businesses under Title III. State and sector-specific rules may also apply, so identify the laws relevant to your organization and the digital service involved.

Title II and Title III Requirements

Title II and Title III address different organizations, which makes the audience and service behind each digital feature important. The U.S. Department of Justice’s Title II rule sets WCAG 2.1 AA as the website compliance standard for state and local government entities. Title III prohibits discrimination in places of public accommodation, while the ADA does not establish the same detailed technical website standard for private businesses.

For a government website, assess third-party functions within the public service, such as an embedded appointment scheduler or payment portal. For a public business, consider whether outside content helps customers access its services. Don’t treat an external vendor’s interface as separate from the visitor’s overall experience.

Differences by State or Industry

The ADA doesn’t create a separate federal rule for each industry, but the organization type and other applicable requirements affect what to consider. A city government’s online service falls under Title II; a private company’s public-facing service raises Title III considerations. Florida municipal governments also need deliberate planning: the Florida League of Cities advises local governments to prioritize digital accessibility planning and remediation for applicable deadlines.

For an organization operating across states, map the services, locations, and government relationships that shape its obligations. For Florida municipalities, planning should include vendor-supported pages and functions, not just in-house content. This helps teams prioritize accessibility work without assuming every organization faces identical requirements.

Third-party content can include videos, maps, social feeds, chat tools, document viewers, and payment interfaces. Review each visitor task: can someone find the embedded feature, understand its controls, and complete the transaction using a keyboard or screen reader? Content accessibility guidelines provide criteria for evaluating digital experiences, but an automated scan may not reveal every barrier in a vendor’s interface.

Build ownership into procurement and maintenance. Record each external feature, the task it supports, and who can address reported barriers. Test the tool on desktop and mobile, including focus order, labels, captions, and error messages. When a vendor updates its interface, repeat the checks; an accessible embed can change when its code or content changes.

For website and mobile app reviews, assess the complete customer journey rather than treating embedded web content as an isolated component. A person with a disability may encounter a barrier at a single step, such as a screen reader failing to announce a required field. Document the issue, its impact, and the needed correction to give your team a clearer basis for prioritizing remediation.

What are ADA audit and ADA compliance assessment services?

An accessibility audit examines how people with disabilities experience your digital services and identifies barriers that may restrict access. A useful assessment turns findings into prioritized remediation, not merely a score.

Accessibility Audits and Assessments

An accessibility audit reviews website content and functions against WCAG success criteria and real user tasks. It matters because a page can appear functional while someone using a screen reader can’t understand its controls or complete a form.

A strong assessment combines automated scans with manual evaluation and assistive technology testing. Automated tools can flag issues such as missing labels, while human review can reveal confusing focus order or instructions. Findings should connect each issue to the affected page, its impact on users, and a practical correction.

Professional Accessibility Audits

A professional audit adds structured testing and clear documentation to a digital accessibility review. Reviewers can examine navigation, headings, form labels, keyboard access, contrast, captions, and error handling across key user journeys.

Ask the assessment to distinguish detected defects from verified barriers. A scan may identify a missing image description, but a reviewer must determine whether the image conveys information and what alternative text would communicate it. Assistive technology testing and testing with people with disabilities can reveal barriers that code-only checks miss.

If your business uses third-party widgets, include embedded booking, payment, and chat features in the audit scope. Record which vendor controls each issue, which task it blocks, and whether a workable correction exists. This makes the findings useful to designers, developers, and decision-makers rather than leaving them as an abstract compliance report.

Audit and Remediation Costs

Audit and remediation costs depend on the scope, site complexity, and number and type of digital experiences reviewed. A small informational site requires a different workload from a site with account access, interactive forms, video, and third-party tools.

Remediation effort depends on the barriers found and where they originate. A shared template defect may affect several pages, while a vendor-controlled feature may require coordination beyond your own codebase. The assessment should distinguish audit work from correction work so you can understand what each phase covers.

To plan a useful scope, identify the pages and tasks most important to customers, then include the components those tasks rely on. Ask for findings grouped by severity and user impact, with examples, affected locations, and recommended fixes. A report that only lists errors leaves your team guessing; actionable evidence helps allocate development time and verify whether changes resolved the barrier.

After remediation, validate changes through manual review, assistive technology testing, and testing with people with disabilities. Retest affected journeys, not just the specific code changes, because a fix can alter nearby controls or page behavior. Treat the audit as a point-in-time assessment, and include accessibility checks in ongoing website maintenance as content and functionality evolve.

Website accessibility compliance practices

Make accessibility part of how you plan, publish, and maintain digital services. As an advisor, connect each website decision to a real client task, from understanding your services to submitting an inquiry.

Accessibility Overlays and Widgets

An overlay or widget can add interface options, but it doesn’t replace evaluating the underlying experience. If you use one, test your website with it enabled and disabled, then verify that menus, forms, and key actions still work as intended.

Build your review around a specific journey. For example, find a service page, navigate through it, and submit an inquiry using only a keyboard. Then repeat the task with a screen reader. Note where you lose context, encounter an unclear control, or can’t complete the action. That evidence is more useful than assuming a widget has addressed every access issue.

Use any accessibility tool as one input in a broader design process. Your team still needs to make content, structure, and controls usable at their source. When you plan a redesign, incorporate accessibility into the requirements and review process; website design that prioritizes user experience can account for how visitors move through important tasks.

Common Accessibility Barriers and Violations

Look for barriers that disrupt the task itself: a form field without a clear label, an error message that doesn’t explain what to fix, or a menu that can’t be operated without a mouse. These problems can leave a prospective client unsure how to proceed, even if the page looks polished.

Review each key journey from the visitor’s perspective. Can you identify the page’s purpose from its headings? Can you understand a link’s destination before selecting it? Does a confirmation message make clear that an inquiry was received? These checks reveal usability failures in real interactions, not just visual details.

Assign clear ownership for accessibility. When publishing a page, designate someone to review its headings, link text, form instructions, and downloadable documents. If you add a service description or update a client intake form, include those changes in the review rather than treating published content as permanently finished.

Use automated checks to identify potential code issues, then evaluate the full experience manually. Keep a working log of the affected page, the task that fails, the person responsible, and the correction made. After a change, retest the same task to confirm it works from start to finish.

For your firm, website accessibility compliance under the ADA is best treated as an ongoing design and maintenance responsibility, not a one-time launch-day check. Set a review point whenever you introduce a feature or substantially revise a client journey. This keeps accessibility connected to the site your clients actually use.

Peter Montoya: SEO Performance Marketing

Peter Montoya can help you connect an accessible website experience with a stronger digital growth strategy. If you’re planning a redesign, High-End Quality Websites can support a site built around usability and conversion, while SEO Performance Marketing can help align your visibility strategy with the experience visitors encounter. Growth Goaching can help you think through priorities and business growth decisions.

Accessibility still requires focused evaluation and testing; marketing and website development don’t replace an accessibility audit. When your digital presence needs to evolve, include accessibility in the planning conversation rather than treating it as an afterthought.

Contact Peter Montoya to discuss your website and growth goals.

Make Accessibility Part of Your Next Digital Decision

Accessibility becomes more durable when it shapes decisions before a page, feature, or campaign goes live. Treat each website change as an opportunity to protect the visitor’s ability to understand, navigate, and act. Assign clear ownership, include accessibility in design reviews, and revisit key journeys whenever content or functionality changes.

For your business, website accessibility compliance under the ADA isn’t a one-time project or a widget to install. It’s an ongoing way to make digital experiences work for more people. Start by identifying the customer journeys that matter most, then build accessibility checks into the teams and processes responsible for them.

If you’re ready to align your website and growth priorities, contact Peter Montoya. Take the next step with clarity, and keep building a digital experience people can use.

Frequently Asked Questions

What does ADA compliance mean for my business?

It means ensuring people with disabilities can access public-facing services without discrimination, including through relevant digital experiences. For your business, begin by examining the tasks your website supports, such as finding service details, submitting an inquiry, or managing an account. Identify where a visitor could be blocked, then assign responsibility for correcting and retesting barriers as your site changes.

What is Title II of the Americans with Disabilities Act (ADA)?

Title II prohibits disability discrimination in state and local government programs, services, and activities. It applies whether a government service is delivered online or in person, so a digital portal can be part of the same public service. For example, a local government should consider whether residents can access information and complete tasks through its website or mobile app.

Are There Any Exceptions or Exemptions?

Some limited exceptions, including undue burden or a fundamental alteration, may be considered individually. They aren’t broad exemptions for every organization or website. The Department of Justice also explains that its guidance documents aren’t final agency actions, legally binding, or themselves law. For state and local governments, an exception involving particular content doesn’t remove the need to provide effective communication and equal opportunity to participate.

Are Websites Covered Under the ADA?

Yes. The U.S. Department of Justice interprets the ADA’s nondiscrimination and effective communication provisions as applying to web accessibility. This may matter when a website provides access to a business’s public service or a government program. Evaluate the full service journey, including eligibility information, online forms, and account features, rather than assuming a website is outside the ADA because it has no physical location.

What Is the ADA?

The Americans with Disabilities Act is a United States law that protects people with disabilities from discrimination. Its five titles address different areas, including employment, state and local government services, and public accommodations. For a business, consider how its obligations relate to employees and public-facing services. The law’s principles apply across changing ways of delivering services, including digital channels.

What are best practices for accessible UX design?

Design around the tasks people need to complete, then test those tasks using different access methods. For example, make service inquiries possible without relying only on a mouse, provide clear instructions for form fields, and ensure error messages identify what needs attention. Keep page structure consistent so visitors can predict where navigation and key actions appear. Include accessibility checks in design reviews before publishing new features or content, or collaborate with a web development specialist like ThinkTank Creative to build accessible usability into custom sites from the start.

What are the basic requirements of ADA?

The ADA’s core requirement is nondiscrimination against people with disabilities in areas it covers. For websites, the Department of Justice connects that principle with effective communication, while technical standards guide practical accessibility work. In everyday terms, consider whether someone can obtain information, understand available options, and use the service. The specific legal framework depends on whether the organization is a public entity, employer, or public-facing business.

What WCAG version and conformance level should websites meet for ADA compliance?

For state and local government entities, the U.S. Department of Justice’s Title II rule establishes WCAG 2.1 Level AA as the website compliance standard. Private organizations often use WCAG 2.1 Level AA as a practical benchmark. WCAG 2.2 is the latest version identified here, so teams may use it as a current technical reference while distinguishing that choice from the government rule’s specified standard.