Web Accessibility: Why It Matters and What the Law Requires

You're about to redesign your site or launch an app, and someone drops the word "accessibility" — but you're not sure if it's a nice-to-have or something that can get you sued. Web accessibility means building your site so people with disabilities can use it just like everyone else, and in the US it's enforced under the ADA, in the EU it's mandatory under the European Accessibility Act since June 2025, and across LATAM it already binds governments and regulated private sectors. The technical standard you need to meet is WCAG 2.2 level AA. Here's the straight version: why it matters, what the law requires, and what compliance actually costs.

What web accessibility is (and isn't)

Web accessibility means your site works for people with visual, hearing, motor or cognitive disabilities. Concretely: a blind user can hear your page through a screen reader, someone who can't use a mouse can navigate everything by keyboard, a person with low vision can tell text from background, and videos have captions.

It isn't charity or a "nice gesture." Around 15 percent of the world's population lives with some form of disability, per the WHO. If your site shuts them out, you're closing the door on a huge slice of your market — and exposing yourself legally.

The universal technical standard is WCAG (Web Content Accessibility Guidelines), published by the W3C. The current version is WCAG 2.2, with three levels: A (minimum), AA (what almost all law references) and AAA (very strict). The realistic target for a business is AA.

What the law requires, region by region

Here's the legal landscape people ask about most, simplified:

Country / Region	Law	Who it binds
United States	ADA + Section 508	Courts apply it to commercial websites; thousands of lawsuits/year
European Union	European Accessibility Act	E-commerce, banking, transport — mandatory since Jun 2025
Brazil	Law 13.146 (LBI)	Public sites and businesses; real fines applied
Argentina	Law 26.653	State and publicly funded entities; expanding to private
Colombia	Law 1618 + NTC 5854	Public entities and citizen services
Chile	Law 20.422	Government bodies
Mexico	General Inclusion Law	Public sector; growing pressure on private

Two things matter. First, even if your country only binds the government today, the regional trend is to expand to banking, health, education and e-commerce. Second, your customer's jurisdiction counts. If your LATAM e-commerce sells to a consumer in the US or EU, those laws reach you. The US alone sees thousands of web accessibility lawsuits a year, many against mid-size online stores.

The 7 most common accessibility problems (and how they look)

In real audits, these show up over and over:

1. Images without alt text. A screen reader just says "image" and nothing else. Every informative image needs a descriptive alt.
2. Insufficient contrast. Light gray text on white. WCAG AA requires a contrast ratio of at least 4.5:1 for normal text.
3. No keyboard navigation. Menus, forms or buttons that only respond to a mouse lock out anyone who can't use one.
4. Forms without labels. Fields with no associated label: the user can't tell what goes where.
5. Videos without captions or transcripts. Excludes deaf users — and anyone watching on mute.
6. Non-semantic HTML. Everything built with divs instead of real headings, lists and buttons. The screen reader can't parse the structure.
7. Invisible focus. You can't see where you are when navigating by keyboard.

The good news: none of these is magic. They're all solved with good HTML, good design and testing. That's why your web development team should have them on the radar from the first wireframe, not as a last-minute patch.

Not sure how accessible your current site is? Book a presentation meeting and we'll run a quick review of the critical points before they turn into a legal problem.

What compliance costs (and why remediation costs more)

The big lesson in accessibility is about timing:

When	Relative cost	Why
From the design stage	+5 to 10% of the project	Built right the first time
Remediating an existing site	USD 800 to 6,000+	Rewrite HTML, fix components, re-test
After a lawsuit	Much more	Legal fees + emergency fix + brand damage

Building accessible from the start costs a bit more planning and almost no extra code. Remediating a finished site means taking components apart, rewriting markup and re-testing everything. And waiting for a lawsuit is the most expensive option of all. If you're starting a project from scratch, accessibility belongs in the brief — the same way it does when we build a custom e-commerce or an MVP to validate your idea.

A practical checklist for an accessible website

If you want an actionable list to review today:

1. Every informative image has a descriptive alt (decorative ones use alt="").
2. Text contrast meets 4.5:1 (use a contrast checker).
3. You can move through the whole site using only the Tab key.
4. The keyboard focus is clearly visible.
5. Every form field has its label.
6. You use semantic HTML: nested headings, button, nav, main.
7. Videos have captions or a transcript.
8. The site works zoomed to 200 percent.
9. You never convey information by color alone ("the red field is required").
10. You tested with a real screen reader (NVDA is free).

An automated test (Lighthouse, axe) catches around 30 to 40 percent of issues. The rest needs manual review. So the right combination is: automated tools + manual testing with keyboard and screen reader.

When chasing AAA does NOT make sense

Let's be honest: not everything needs the top level.

• If you're a pre-validation startup with no traffic or customers yet, hit AA on the essentials (keyboard, contrast, alt, forms) and don't get stuck chasing AAA.
• An internal dashboard used by five employees with no reported disabilities doesn't need the same rigor as your public consumer-facing store.
• A throwaway prototype for an investor demo doesn't justify a full accessibility audit.

What DOES need serious accessibility from day one: anything public and customer-facing, especially e-commerce, banking, health, education and anything touching consumers in the US or EU. For internal employee-facing systems, a well-built custom software already starts from semantic HTML, so you're covered on the basics with almost no extra effort.

Bottom line

Web accessibility is no longer optional. It's an enforced legal requirement in the US and EU, a fast-growing one across LATAM, and on top of that it opens up 15 percent more market and improves your SEO. The key is timing: building accessible from the design stage costs little; remediating later costs a lot; and waiting for a lawsuit costs the most.

About to launch or redesign a site and want it born accessible — no cost overruns, no legal scares? Start your project with us and we'll build it to WCAG 2.2 AA from the very first wireframe.