·3 min read
Web accessibility matters more than most teams think
Accessibility is a legal requirement, a business advantage, and a matter of equal access. What the ADA and European Accessibility Act mean for your website, and where to start with WCAG.
I spent a long stretch of my career working on accessibility software, and the thing that stuck with me is how differently teams treat accessibility before and after they understand it. Before, it is a checklist item someone will get to eventually. After, it is obvious that the site was quietly turning away a meaningful share of its visitors the whole time.
Around one in six people worldwide lives with a significant disability. That is not a niche audience. It includes people using screen readers, people who navigate entirely by keyboard, people with low vision who need real contrast, people with motor impairments who cannot hit small touch targets, and people with cognitive differences who need clear structure and plain language. Most of them do not file complaints when your site fails them. They just leave.
The law has caught up
For years accessibility was framed as a nice thing to do. That framing is now legally out of date in most major markets.
In the United States, courts have consistently treated websites as places of public accommodation under the Americans with Disabilities Act. Thousands of ADA website lawsuits are filed every year, and they increasingly target small and mid-sized businesses, not just large corporations. Settlements are expensive, and the remediation still has to happen afterward.
In the European Union, the European Accessibility Act became enforceable in June 2025. It applies to e-commerce, banking, and a wide range of consumer digital services, including companies outside the EU that sell to EU customers. Public sector requirements existed before, but the EAA pulled private business into scope.
The technical standard behind almost all of this is WCAG, the Web Content Accessibility Guidelines. Level AA of WCAG 2.1 is the bar most regulations and courts reference. It is public, testable, and free to read.
Equal access is the point
The compliance argument gets attention, but it is the weaker argument.
The web is no longer an extra channel. It is where people apply for jobs, do their banking, order groceries, book medical appointments, and study. When a site is inaccessible, the person locked out does not lose a convenience. They lose access to something the rest of us take for granted. Building accessibly is the digital version of building a ramp next to the stairs, and it is just as reasonable an expectation.
It is also simply good business
Accessible sites are better sites, for everyone.
Captions help the person watching in a loud cafe. High contrast helps anyone reading a screen in sunlight. Clear focus states help every keyboard power user. Logical heading structure helps screen readers and also helps search engines, which is why accessibility work and SEO work overlap so much. Add the direct market effect, since people with disabilities and their families control significant spending power, and the business case writes itself.
Where to actually start
Most accessibility problems on real websites come from a small set of causes, and none of them require special tooling to fix.
Use semantic HTML. Real buttons, real links, real headings in a sensible order, real labels attached to form fields. Half of accessibility is using the platform the way it was designed.
Test with your keyboard. Unplug your mouse and try to complete your site's main task using Tab, Enter, and Escape. If you get stuck or lose track of where focus is, so does everyone who relies on a keyboard.
Check your contrast. Light gray text on white backgrounds fails real users long before it fails an audit. A contrast checker takes seconds to use.
Write alt text that carries meaning, and leave it empty for purely decorative images so screen readers skip them.
One honest note from someone who worked in this industry: automated scanners and quick-fix tools catch maybe a third of real issues. They are useful for finding problems, but they do not replace building on solid foundations and testing with actual assistive technology. Accessibility is not a plugin. It is a property of how the site is built.
Start with one page, fix what you find, and make the checks part of how you ship. It is far cheaper to build accessibly than to retrofit under a legal deadline, and it is the right thing to build either way.