Tampa Forge

Web accessibility & ADA · Tampa Bay

An accessible website — and no snake-oil "compliance"

Web accessibility means people who use a screen reader, navigate by keyboard, or have low vision can actually use your site — not bounce off it. It's also the thing behind the ADA demand letters landing on real businesses right now. Here's our position, plainly: accessibility is real work done in the markup, not a script you paste in for $49 a month. Anyone selling you a one-click "compliance widget" as the fix is selling wind, and we'll tell you why.

What This Actually Means

Four things that make a site accessible

WCAG — the Web Content Accessibility Guidelines — is the standard everyone points to, and WCAG 2.1/2.2 level AA is the common target for a business site. Skip the version numbers for a second, though: here's what accessibility looks like in plain terms, and it's the same list we work through whether we're building new or fixing yours.

Eyes that don't see the screen

Text alternatives and semantic structure

A screen reader can only announce what the code tells it. Images need real alt text, headings need to be actual headings in order, and buttons need to be buttons — not a styled <div> that a mouse can click but a screen reader can't find. Get the structure right and a blind visitor moves through your site the way a sighted one moves through it with their eyes.

No mouse aboard

Full keyboard navigation

Plenty of people never touch a mouse — motor disabilities, screen-reader users, or just power users. Every link, menu, and form control has to be reachable and operable with the Tab and Enter keys, with a visible focus outline so you can see where you are. Menus that only open on hover and forms you can't submit without clicking are where sites quietly lock people out.

Low vision, bright sun

Color contrast and readable text

Light grey text on a white background looks tasteful in a mockup and disappears for anyone with low vision — or anyone reading on a phone in Florida sunlight. WCAG sets measurable contrast ratios for text and controls, and we check real numbers, not vibes. The same fixes make the site easier to read for every visitor, not only the ones who need them.

Forms that talk back

Labeled forms and clear ARIA

Contact and booking forms are where accessibility most often breaks — and where you lose the lead. Every field needs a real label a screen reader can announce, errors need to be described in words, not just a red glow, and ARIA attributes get used only where plain HTML can't do the job. Used sparingly and correctly, ARIA fills gaps; sprinkled everywhere, it makes things worse.

Straight Answers

The accessibility questions businesses actually ask

No fear-mongering and no false promises. If a "compliance" pitch made you nervous, these are the plain answers first — especially if you run a professional practice or law firm, where clients ask about this directly.

Is my business legally required to have an accessible website?

The honest answer is "it's complicated, and the risk is real." The ADA has been read by many courts to cover the websites of businesses open to the public, and there's no single federal checklist that stamps a site "compliant." What's not in dispute is that inaccessible-site demand letters and lawsuits are common and growing, and they hit small businesses, not just big ones. Professional services — law firms, medical and dental practices, anyone with public clients — draw the most attention. We're web developers, not your lawyers, so for your specific legal exposure talk to an attorney; what we can do is make the site genuinely usable so you're not the easy target.

Won't an accessibility widget or overlay just fix it?

No — and this is the most important thing on the page. Those overlay widgets promise instant compliance from one line of JavaScript, and they're widely criticized by the actual accessibility community, including many screen-reader users, for making sites harder to use. They can't rewrite bad markup, can't invent meaningful alt text, and their presence has itself been cited in lawsuits. We don't sell them, and we'd steer you away from anyone who does. Accessibility lives in the HTML, the structure, and the content — the overlay just paints over it.

How do you actually test for accessibility?

Automated scanners are the start, not the finish. Tools like axe and Lighthouse catch maybe a third to a half of issues — missing alt attributes, contrast failures, unlabeled fields — and we run them. Then we do the part software can't: navigate the whole site with the keyboard only, run it through a real screen reader, check focus order, zoom the text to 200%, and confirm forms announce their errors. A clean automated score with a site nobody can tab through is exactly the false comfort we're trying to save you from.

Can you fix my existing site, or does it need a rebuild?

Usually we can remediate what you have — that's the common request. We audit the current site, hand you a plain-language report of what fails and why it matters, and quote a fixed price to fix it: alt text, contrast, keyboard access, semantic structure, form labels, ARIA where it's genuinely needed. If the underlying code is so tangled that patching costs more than rebuilding, we'll say so honestly. Accessibility can also ride along with a broader website speed and security audit if you're already having the site looked over.

Worried about your site? Let's look at it — for free

Send us your URL and what's prompting the question — a demand letter, a nervous client, or just doing it right. We'll tell you honestly where the site stands, whether you need a full remediation or a few targeted fixes, and quote a fixed price for the real work. No overlay upsell, no promises of legal immunity nobody can actually make. If you run a practice where clients care about this, our websites for law firms page covers how we approach that world.

No ransom required. First consultation is free.