Website
accessibility
Website accessibility means people with low vision, limited hand movement, hearing loss or cognitive disabilities can use your site to find a service and contact you. In the US it's also a legal exposure: ADA claims over websites are common. I build sites to WCAG 2.1 AA practices from the first sketch, which costs far less than retrofitting later.
Free: a 30-minute call, an action plan and a price range in writing.

Accessible from
the first sketch
Contrast and text size
Text that meets AA contrast ratios and can be enlarged to 200% without the layout falling apart.
Keyboard navigation
Every link, menu and form works without a mouse, with a clearly visible focus outline.
Screen reader structure
Real headings, landmarks, labels and alt text, so assistive technology can read the page in order.
Usable forms
Visible labels, clear error messages in text and no time limits that cut people off.
Media with alternatives
Captions for video, no autoplay with sound and nothing that flashes.
Tap targets
Buttons and links large enough for shaky hands and big thumbs on phones.
Accessibility
at every step
Requirements
Your industry, audience and any rules you've been told apply to you.
Design
Contrast, type scale, focus states and tap targets checked in the mockups.
Build
Semantic code, labels, alt text and full keyboard support.
Testing
Automated scans plus manual keyboard and screen reader passes.
Handover
Guidance on adding accessible content yourself and a draft accessibility statement.
What an accessible
website costs
Final prices in US dollars. Accessibility is part of the build, not a surcharge.
Accessible multi-page site built to WCAG 2.1 AA practices.
- Accessible design and code
- Keyboard and screen reader testing
- Accessible edit panel
- Draft accessibility statement
A walkthrough of the main barriers on your current site.
- Screen-shared review
- Prioritized list of issues
Website accessibility in plain English
Website accessibility means a person can use your site whatever their abilities: someone who navigates with a keyboard because of a tremor, someone who listens to pages through a screen reader, someone who zooms text to 200%, someone colorblind, someone older whose eyes tire on small gray text. Millions of Americans live with a disability, and many more have temporary or age-related limits: a broken wrist, cataracts, reading glasses left in the car. For a local business, that's a real share of customers.
Good accessibility also helps everyone else. Clear headings, readable contrast, large tap targets and forms with proper labels make a site easier on a phone in bright sunlight, too.
The ADA and why websites get sued
The Americans with Disabilities Act was written before the modern web, and it doesn't contain a detailed rulebook for private business websites. In practice, though, courts and plaintiffs' lawyers widely apply it to them, particularly when the business also serves customers in person. Demand letters and lawsuits about websites arrive in large numbers every year, with New York, California and Florida among the busiest places. Small businesses are frequent targets because their sites often have obvious, easy-to-document barriers.
WCAG 2.1 at level AA is the standard most often used as the yardstick in these claims and in settlements. I'm not a lawyer and can't tell you your legal risk; for that, talk to your attorney. What I can do is build a site that meets the technical practices those claims are measured against. The background is in ADA website accessibility.
What I check on every site
- Structure: one H1, logical heading order, landmarks for header, navigation, main content and footer.
- Text alternatives: meaningful alt text on informative images, empty alt on decorative ones.
- Color and contrast: at least AA ratios, and color never used as the only signal.
- Keyboard: everything reachable and usable by Tab, Enter and Space, with a visible focus outline and no traps.
- Forms: visible labels, instructions before fields, errors described in text and announced to screen readers.
- Zoom and reflow: content readable at 200% zoom and on narrow screens without sideways scrolling.
- Motion: respect for the reduced-motion setting, pausable carousels, nothing flashing.
Barriers I see most often
On sites I review, the same problems repeat: phone numbers and prices placed inside images, light gray text on white, icon-only buttons with no label, booking widgets that can't be used with a keyboard, PDF menus that screen readers can't read, and pop-ups that grab focus and can't be closed. Each of these is cheap to avoid when building and fiddly to patch afterward. That's one reason I rebuild rather than retrofit, as described on website redesign.
Content you add later
A site can launch accessible and slowly stop being so as new content goes in. The edit panel I build asks for alt text when you upload an image, keeps heading levels in order and doesn't let you paste text as a picture. I also give you a one-page guide: how to write link text, when to use headings, how to caption a video. Accessible design starts with the interface itself, covered under UX/UI design.
An accessibility statement
I'll draft a short accessibility statement for your site: what standard you aim for, what's known to be imperfect and how people can reach you if they hit a barrier. Your attorney should review it before it goes live. You can see how this site handles it on its own accessibility page.
Accessibility
and compliance
ADA and WCAG
questions
Does the ADA apply to my website?
The ADA doesn't spell out website rules for private businesses, but courts and plaintiffs widely apply it to business websites, especially those connected to a physical location. Demand letters and lawsuits are common, particularly in New York, California and Florida. Whether your business is at real risk is a question for your attorney; building accessibly lowers it either way.
What's the difference between WCAG 2.0, 2.1 and 2.2?
Each version adds criteria on top of the previous one. WCAG 2.1 added points about mobile use, zoom and low vision, and 2.1 AA is the reference most often cited in US website claims and settlements. Version 2.2 adds a few more, mostly about focus and forms. I build to 2.1 AA and follow 2.2 where it's practical.
Can you certify my site as compliant?
No, and be careful with anyone who sells certificates. There's no official US certification for website accessibility. What I can do is build to WCAG 2.1 AA practices, test with automated tools, keyboard and screen reader, and document what was checked. Legal advice on compliance comes from your attorney.
Can you make my existing site accessible?
I don't remediate sites built by others; fixing accessibility in unfamiliar themes and plugins is slow and often incomplete. I build a new, accessible site on your domain and move the content. If you only want to know where you stand, a review call gives you a prioritized list your developer can work through.
Are accessibility overlay widgets enough?
Usually not. Overlays add a toolbar on top of the page but don't fix the underlying code: missing labels, broken heading order or keyboard traps stay. Many accessibility experts criticize them, and sites using overlays have still received demand letters. Accessible code is the real fix.
Need a site
everyone can use?
Tell me about your business and, if you have one, a link to your current site. I'll reply within one business day with what an accessible rebuild would involve. The first 30-minute call is free.
- 9 short steps
- No obligation
- I reply personally
- I reply within 1 business dayPersonally, by email or on WhatsApp, whichever you prefer.
- A 30-minute call, freeI ask about your business, customers and budget. Beforehand I review your website and ads.
- A proposal with a price, in writingWhat I’ll do, by when and for how much. You decide with no pressure.
What do you need most?