Website Accessibility (ADA Compliance) for Business Websites

A website works only for the people who can actually use it. That sounds obvious, but a great many business websites quietly exclude a substantial number of visitors: people who cannot see the screen, cannot use a mouse, cannot hear audio, or find dense, cluttered interfaces impossible to navigate. Website accessibility is the practice of building sites that everyone can use, including people using assistive technology, and it has become both a basic mark of professional work and a subject with real legal weight. This guide covers what accessibility actually involves, why it matters commercially as well as ethically, and where the legal questions properly belong.

What website accessibility actually means

Accessibility means that people can perceive, understand, navigate, and interact with a website regardless of how they access it. In practice, that covers a wide range of people and situations.

Someone with limited or no vision may use a screen reader that speaks the page aloud, which means the site has to make sense when it is heard rather than seen. Someone with low vision may enlarge text substantially or need strong contrast to read at all. Someone who cannot use a mouse, whether through a motor condition, an injury, or simply preference, navigates entirely by keyboard or by voice, so everything has to be reachable that way. Someone deaf or hard of hearing needs captions or transcripts for anything spoken. Someone with a cognitive or learning difference is served by clear language, predictable layouts, and interfaces that do not overwhelm.

It is worth noting how broad this group is. Accessibility is often imagined as serving a small minority, but it includes a very large number of people once you count age-related vision and hearing changes, temporary injuries, and situational limitations, someone using a phone in bright sunlight, or without sound in a quiet room. Building for accessibility improves the experience for far more people than the term suggests.

Why it matters

There are several reasons a business should care, and they reinforce one another.

It is the right thing to do. A website that excludes people excludes them from a service they are entitled to use like anyone else. For businesses serving the public, and especially for healthcare and essential services, that exclusion matters in a way no other justification is really needed for.

Excluded visitors are lost customers. Every person who cannot use your site is a customer who goes elsewhere, and they rarely tell you why. Inaccessible sites lose business invisibly, which is part of why the cost is so often underestimated.

There is genuine legal exposure. Accessibility is the subject of real law in many places, and claims against businesses over inaccessible websites have become common. What any particular business is legally required to do is a question for its own legal professionals, but the existence of meaningful legal risk is simply a fact of the landscape now.

It improves the site for everyone. Accessible sites tend to be clearer, better structured, faster to navigate, and easier to use, which benefits every visitor rather than only those who need it most.

It aligns with what search engines reward. Well-structured headings, meaningful text alternatives, clear navigation, and good performance are all accessibility practices, and they are also the things search engines use to understand a page. Accessibility and search visibility pull in the same direction.

The standard everyone points to

When people discuss website accessibility, they are almost always referring, directly or indirectly, to the Web Content Accessibility Guidelines, universally shortened to WCAG. These are the internationally recognized technical guidelines for making web content accessible, and they are what most laws, policies, and procurement requirements around the world reference.

WCAG is organized around four principles, often summarized as perceivable, operable, understandable, and robust. Perceivable means information must be presentable in ways people can perceive, so images need text alternatives and audio needs captions. Operable means the interface must be usable, including entirely by keyboard. Understandable means content and behaviour should be clear and predictable. Robust means the site should work reliably with assistive technologies.

WCAG also defines conformance levels, A, AA, and AAA, in ascending order of stringency. Level AA is the level most commonly referenced in policy and in practice, and it is the usual target for a business website. AAA is demanding enough that it is rarely required across an entire site. When a developer says a site meets AA, that is generally what is meant, though it is worth knowing that automated testing alone cannot confirm it, since a meaningful portion of the criteria require human judgment.

Where the legal questions belong

This is the part to be careful about, and we will be direct: what your business is legally obliged to do about website accessibility is a question for your own legal professionals, not for a web developer or a guide like this one.

The landscape is genuinely complex. Different jurisdictions impose different obligations through different instruments, and the way courts have applied older legislation to websites has evolved considerably and continues to. Requirements can vary with the kind of organization, its size, its sector, and where its customers are, and public-sector and healthcare organizations often face stricter expectations than others. Some regimes set explicit technical standards and deadlines; others are enforced largely through litigation.

What that means practically is that a business should get its own advice about its own obligations rather than relying on general information. What a developer can properly say is which technical standard a site has been built and tested against, and that is exactly how we work: we build to recognized standards and verify against them, and we leave the determination of legal obligations to the people qualified to make it. A business that wants certainty about its position should ask its legal advisers, who can assess its particular circumstances.

What accessible design involves in practice

Accessibility is not one feature but a set of practices applied throughout a site.

Sufficient colour contrast. Text needs enough contrast against its background to be readable by people with low vision, which rules out some fashionable but faint design choices.

Text alternatives for images. Meaningful images need descriptions so that someone using a screen reader receives the same information a sighted visitor gets from looking.

Full keyboard operability. Everything on the site, every control, menu, and form, must be reachable and usable without a mouse, with a clearly visible indicator of where the keyboard focus currently is.

Proper heading structure. Headings should describe the actual structure of the page in order, because screen reader users navigate by them. Headings used purely for visual size, out of order, make a page far harder to navigate.

Properly labelled forms. Every field needs a programmatically associated label, and errors need to be identified clearly and in text rather than by colour alone.

Captions and transcripts. Video and audio content needs captions or transcripts so that the information is available to everyone.

Descriptive navigation wording. Navigation elements should describe where they lead, since screen reader users often browse them out of context, which makes generic wording like "click here" useless.

Respect for motion and touch preferences. Animation should respect the preferences of people who experience discomfort from motion, and interactive targets should be large enough to use reliably.

Common failures, and one to be wary of

The failures that come up most often are consistent: text with too little contrast, images with no alternatives, forms whose fields are not labelled, functionality that cannot be reached by keyboard, keyboard focus that becomes invisible or trapped, headings applied for appearance rather than structure, and video without captions. Most are straightforward to avoid when a site is built with accessibility in mind, and considerably more tedious to retrofit afterward.

One thing deserves a specific warning: the accessibility overlay widgets marketed as instant compliance, typically a script that adds a floating accessibility button to a site. These are widely criticized by accessibility practitioners and by many people who actually use assistive technology, because they do not fix the underlying problems in a site's code and can interfere with the assistive technology a visitor already uses. They are also, notably, not a defence against the legal exposure they are often sold as solving. A business genuinely concerned about accessibility is far better served by building and remediating the site itself than by installing a widget over the top of an inaccessible one.

Building it in rather than bolting it on

Accessibility is dramatically cheaper and better when it is part of how a site is designed and built rather than an audit performed afterward. Retrofitting means revisiting design decisions, colour choices, layouts, components, and interactions that were made without accessibility in mind, and unpicking them is far more work than making better choices in the first place.

This is why serious accessibility is a matter of process rather than a checklist applied at the end: designing with contrast and structure in mind, building components that are keyboard-operable and properly labelled by default, and testing throughout, with automated tools for what they can catch and with real judgment for what they cannot. A site built this way is accessible because of how it was made, not because something was added to it, and that is the only approach that holds up as the site grows and changes.

Who else benefits from asking

One practical reason accessibility has moved up the agenda for many businesses is that other people increasingly ask about it. Public-sector buyers and larger organizations frequently require suppliers to meet a stated accessibility standard as a condition of procurement, so a business bidding for that kind of work may find its website's accessibility is part of what is being evaluated. Partners, funders, and institutional clients ask similar questions for similar reasons.

That gives accessibility a commercial dimension beyond the customers it directly serves. A business that can state plainly which standard its site meets and how that was verified is in a position to answer those questions; one that has never considered the subject is not, and may find itself scrambling or excluded. It is a modest point next to the human one, but it is often what moves accessibility from something a business agrees with in principle to something it actually schedules, and the work is the same either way.

What good accessibility looks like

A genuinely accessible business website can be used comfortably by someone using a screen reader, someone navigating entirely by keyboard, someone who needs large text and strong contrast, and someone who finds complexity difficult. It has been built to a recognized standard and tested against it, including by human judgment rather than automated tools alone. It does not rely on an overlay to paper over structural problems, and it does not treat accessibility as a legal box to tick. It is simply a site made properly, which is why accessible sites tend to be better sites for everyone.

Questions businesses often ask

Are we legally required to make our website accessible? That depends on your organization, your sector, and where you operate, and it is a question for your own legal professionals. What we can say is that accessibility law is real, active, and evolving in many jurisdictions, and that building to a recognized standard is the sensible foundation whatever your specific obligations turn out to be.

Does accessibility mean an ugly or limited design? No. It constrains a few specific choices, notably contrast and some interaction patterns, but accessible sites can be as distinctive and beautiful as any other. Most accessibility work is invisible to visitors who do not need it.

Is an accessibility widget enough? Overlay widgets are not a substitute for an accessible site. They do not fix underlying problems, can interfere with assistive technology, and are not the protection they are often marketed as. The real work is in the site itself.

Does it cost much more? Built in from the start, the additional cost is modest, because it is mostly a matter of making better decisions rather than doing extra work. Retrofitting an inaccessible site later costs considerably more, which is the strongest practical argument for getting it right initially.

Where to go from here

Accessibility is part of building a website properly, and it serves both the people who need it and the business that reaches them. To go further, see how we approach web design and SEO, and read into the specifics: what ADA website compliance actually requires, designing accessible forms and navigation, and accessibility for healthcare and booking websites.