Association website
120–150% more online visitors after the rebuild
Laravel · CMS · ERP
I'm Kafi, a senior freelance web developer. My ADA website compliance services audit your site against WCAG 2.2 AA, fix the issues in the code itself, and keep new content accessible, so people using screen readers, keyboards or magnifiers can actually use your site.
Starting from $10/hr
A WCAG 2.2 AA audit with real-user testing
Issues fixed in your code and templates
An accessibility statement you can publish
Checks after every change, not once a year
SEE THE DIFFERENCE
Most accessibility problems are this ordinary. Flip the switch to see what changes for someone using a keyboard, a screen reader or a phone in bright sun.
Example form
Illustration · a real audit covers every template and journey
WHAT I DO
Testing, fixing and keeping it fixed. Automated scanners catch a fraction of issues; the rest need a person.
Automated scans plus manual checks of key pages and journeys, with every issue mapped to a WCAG criterion.
Audit · Report
Your main pages and forms tested with NVDA, VoiceOver and TalkBack the way real users use them.
NVDA · VoiceOver
Every menu, modal, slider and form usable without a mouse, with visible focus.
Keyboard · Focus
Text and buttons adjusted to meet contrast ratios while keeping your brand.
Contrast · Brand
Labels, error messages, required fields and instructions that screen readers announce correctly.
Forms · Errors
Meaningful image descriptions, captions and transcripts for video and audio.
Alt text · Captions
Logical headings, landmarks and link text so pages make sense when read aloud.
Semantics · ARIA
Menus, tabs, carousels and dialogs rebuilt to WAI-ARIA patterns.
WAI-ARIA
Key PDFs checked and fixed, or turned into accessible web pages.
PDF · Documents
A clear statement of your standard, known issues and how to ask for help.
Statement
New pages and changes checked regularly so accessibility does not quietly slip.
Monitoring
Short guides for your editors on headings, alt text, links and documents.
Training
Describe what you want to build. I'll reply within a few hours and tell you honestly what it would take.
WAYS TO IMPROVE ACCESSIBILITY
This is general information, not legal advice. A general guide to the approaches people compare:
| Automated scan | Manual audit | Overlay widget | Code remediation | |
|---|---|---|---|---|
| What it does | Runs tools that flag common issues | A person tests with keyboard and screen reader | Adds a toolbar and script on top of the site | Fixes the underlying code and design |
| What it finds or fixes | Some issues, not all | Most issues, with context | Does not change the underlying code | The issues themselves |
| Good for | A quick first look | Knowing exactly what to fix | A supplement, not a replacement | A lasting result |
| Ongoing effort | Repeat after changes | Repeat after big changes | Subscription | Check new pages and features |
ADA WEBSITE COMPLIANCE
ADA website compliance means making your website usable by people with disabilities, in line with the Americans with Disabilities Act. In practice, the benchmark courts, regulators and settlements point to is the Web Content Accessibility Guidelines (WCAG), at level AA.
For state and local government websites, the US Department of Justice set WCAG 2.1 AA as the required standard in a 2024 rule. For private businesses open to the public, US courts have repeatedly applied the ADA to websites, and demand letters and lawsuits over inaccessible sites are common. I am a developer, not a lawyer, so for legal advice speak to one; what I can do is make the site itself accessible.
Be wary of one-line "accessibility overlay" widgets that promise instant compliance. They do not fix the underlying code, and sites using them are still sued. Real compliance means fixing templates, components and content, then keeping them that way.
| Code fixes | Overlay widget | |
|---|---|---|
| What changes | The actual HTML, CSS and components | A script layered on top |
| Screen reader users | Pages work as expected | Often still broken, sometimes worse |
| Legal risk | Real progress towards WCAG AA | Sites with overlays are still sued |
| Performance | No extra scripts | Extra weight on every page |
| Cost over time | One-off fixes plus light checks | Subscription forever |
CHECKLIST
The Web Content Accessibility Guidelines (WCAG) are the technical standard most accessibility work follows. These are the checks I start with.
Meaningful images have descriptive alt text; decorative ones are skipped.
Every link, menu, form and dialog works without a mouse, with a visible focus outline.
Text and controls are readable against their backgrounds.
A logical structure that screen readers can navigate.
Every field has a label, and errors say what to fix.
Captions for video, and layouts that hold up when zoomed in.
HOW IT RUNS
Highest-impact pages and issues first, so risk drops quickly.
Key pages, templates and user journeys chosen for testing.
Automated scans plus manual keyboard and screen reader testing.
Issues ranked by severity and how many pages they affect.
Templates and components fixed first, then content.
Every fix verified, with a short report and statement.
Regular checks of new content and changes.
HOW IT IS TESTED
Free browser tools highlight common problems quickly, but cannot judge everything.
Tab through every page: can you reach and use everything?
Listen to key pages and forms with a screen reader.
Enlarge text and shrink the window to see if content stays usable.
Measure text and interface colours against recommended ratios.
New pages and features can reintroduce issues, so check as you go.
TOOLS
Tools find the obvious problems; manual testing finds the rest.
PROOF
Real products in production, described without client names. Each one started with a conversation like the one you're about to have.
120–150% more online visitors after the rebuild
Laravel · CMS · ERP
Manual admin work cut by 80–85%
Laravel · MySQL
News platform with authors, categories and ads
Laravel 11
FOR US BUSINESSES
Whether and how accessibility rules apply to your organisation is a legal question, so please ask your own adviser. My part is the technical work: testing against WCAG, fixing the code and design, and documenting what changed.
Cost depends on the number of pages and templates, the state of the existing code, forms, media and third-party widgets, and whether you want an audit only or fixes too. I work in US dollars from $10 per hour and give a written estimate. Related: website redesign and website maintenance.
COST
It depends on the size of the site and how many issues sit in shared templates. Fixing a header, menu or form template once often fixes hundreds of pages. You get a written estimate after the audit, and rates start at $10 per hour when you hire me directly.
Compared with a demand letter or a redesign forced in a hurry, accessibility work is inexpensive, and it widens your audience at the same time.
More unique templates mean more to test and fix.
Custom code is fully fixable; some page builders limit what can change.
Captions, transcripts and PDFs add time.
Sites with broken navigation or forms need deeper work.
Ongoing checks can be added monthly or quarterly.
WHO IT'S FOR
The organisations that need accessible sites most urgently.
PRICING & PLATFORMS
Work with me directly for the best rate, or through Upwork or Fiverr if you want the platform's payment protection.
From $10/hr
Upwork
Fiverr
Long-term work starts at $10 per hour. Every project gets a written estimate before it starts, so there are no surprises.
FAQ · 12 QUESTIONS
Still unsure? Book a free call and ask me directly. I'll tell you honestly if I'm the right fit.
It means making your website usable by people with disabilities under the Americans with Disabilities Act. In practice that means meeting WCAG at level AA, currently version 2.1 or 2.2.
State and local governments must meet WCAG 2.1 AA under a 2024 Department of Justice rule. For private businesses, courts have repeatedly applied the ADA to websites. I am not a lawyer; for legal advice, consult one.
With automated scanners such as axe and Lighthouse, then manual testing: keyboard-only use, screen readers like NVDA and VoiceOver, zoom, contrast and form checks on key pages and journeys.
Run a free scan with WAVE or Lighthouse, then try using your site with only the keyboard and with a screen reader. If menus, forms or pop-ups get stuck, you have work to do.
The Web Content Accessibility Guidelines are the international standard for accessible websites. Level AA is the target most laws and settlements refer to; version 2.2 adds criteria such as focus visibility and easier authentication.
No. Overlays do not fix the underlying code, many users find them harder to use, and sites with overlays are still sued. Fixing the code is the reliable route.
Small sites can be audited and fixed in a few weeks. Larger sites are fixed template by template, with the most-used pages first.
Yes. Most fixes happen in the theme and its components, plus content changes such as headings and alt text. Some page builders limit what can change; the audit will say so.
No. Most fixes are invisible or subtle: better contrast, visible focus outlines, labels and structure. The brand stays recognisable.
Yes. Clear headings, descriptive links, alt text, captions and fast, well-structured pages help search engines and AI tools understand your content too.
Yes. After fixes, I draft a statement listing the standard you follow, any known issues and how visitors can request help.
Check new pages and changes regularly, train editors on headings, alt text and documents, and build accessible components so new pages start compliant.
Tell me what you're building and where you're stuck. You'll get an honest plan, timeline and estimate, even if I'm not the right fit.