Service · Accessibility
Your site has ADA violations you don't know about. I find them, fix them in code, and give you documentation that holds up.
Law firms scan small business websites by the thousands, looking for accessibility violations. Most sites have them. A missing image description here, an unlabeled contact form there, navigation that only works with a mouse—each one is a documented violation. ArdinGate delivers a full Google-standard accessibility audit, manual testing with the screen-reading software used by blind visitors and keyboard-only navigation, code-level fixes for every problem, and a written compliance report you can put in front of an attorney. No overlay widgets. No partial scans. No shortcuts.
Six things a complete accessibility remediation covers
Most businesses that get hit with ADA demand letters didn't know their site had violations. The problems are invisible unless you test the way people who rely on assistive technology actually use the web — with a screen reader reading every word aloud, or with a keyboard instead of a mouse. Here is what a full remediation involves, in the order it gets done.
Automated scan to find the obvious violations and sort them by severity
Every page gets scanned with professional accessibility testing software— the same tool used by large compliance teams and federal agencies. It surfaces the problems it can find automatically: images without text descriptions, form fields without labels, color combinations too light to read, and structural errors in how the page is built. Each problem gets categorized by severity. This is the starting point. The software catches somewhere between 30 and 40 percent of accessibility problems. The rest requires testing the site the way someone who is blind or unable to use a mouse would actually navigate it.
Keyboard navigation testing: using the site without a mouse to catch broken elements
A meaningful share of people with disabilities navigate the web entirely with a keyboard — no mouse. ArdinGate tests every interactive element on every page this way: every link, every button, every form field, every dropdown menu, every popup or overlay. The test confirms that visitors can reach everything, that the current location is always visible, that the order they move through the page makes logical sense, and that any popups that open can also be closed without a mouse. Navigation failures are among the violations most often cited in ADA demand letters, and they're completely invisible to anyone who tests a site only with a mouse.
Screen reader testing with three different programs to catch what the automated scan missed
Screen readers are programs that read web pages aloud for people who are blind or have low vision. ArdinGate tests with NVDA and JAWS (the two most widely used programs on Windows computers) and VoiceOver (built into every Mac and iPhone). Testing with all three matters because they work differently and expose different problems. This is where you discover whether your image descriptions actually describe what the image shows or just say "photo," whether your contact form announces field names aloud before a blind visitor starts typing, whether your navigation menu makes sense when someone can't see the layout, and whether error messages are announced aloud when something goes wrong. No automated software can tell you any of this.
Color contrast check: every piece of text and every button measured for readability
The accessibility standard sets a minimum contrast ratio between text and background — a specific mathematical measurement that's not up for debate. Body text needs to be dark enough relative to its background that people with low vision or color blindness can read it. Buttons, form field borders, and other interactive elements have their own minimum. Light gray text on a white background, pale placeholder text inside form fields, pastel-colored buttons — these are the most common failures, and they appear on most small business sites whose color choices were made without checking whether they're actually readable. Every text element and every interactive element gets measured. If anything needs to change, you see the proposed adjustment and approve it before anything gets applied.
Code-level fixes for everything: no overlay widgets, no problems ignored or worked around
Every problem found in the audit gets fixed in the actual code of your site. Images get real, descriptive text alternatives. Form fields get properly labeled so screen readers know what each one is for. Color readability failures get corrected. Keyboard navigation issues get resolved at the structural level. If any problem can't be addressed for a specific reason, that gets documented explicitly and you decide whether to accept it — nothing gets buried or quietly ignored. Each fix gets retested after it's applied to confirm it actually solves the problem. No overlay script gets injected as a shortcut — those products don't fix anything and have been cited against businesses in ADA lawsuits as evidence of bad faith.
Written compliance report: a dated PDF document formatted for an attorney or judge
The deliverable isn't just a fixed website—it's a document. A PDF compliance report that covers: what pages were reviewed and what tools were used; a complete inventory of every problem found before any fixes were applied; confirmation of every fix that was made, with before-and-after details; the specific accessibility rule reference for each issue; the date of the audit; and a statement that the site meets the legal accessibility standard. This report is written to be readable by an attorney, a compliance officer, or a judge, not just a web developer. If someone sends you an ADA demand letter after the remediation is done, this is what your attorney uses to negotiate a settlement or defend the claim in court.
How plaintiff attorneys scan and find your accessibility problems before you discover them
ADA web accessibility litigation against small businesses follows a specific playbook. The plaintiff's attorney doesn't personally visit your site and notice a problem. They run automated scanning software against lists of business websites organized by category — all the restaurants in a metro area, all the medical practices, all the salons. The scan takes seconds per site. Any site with violations above a threshold gets a demand letter. Here is what those scans look for first, in order of how commonly each type shows up in demand letters against small businesses.
Missing or meaningless image descriptions: the violation that appears in most demand letters
Every non-decorative image on a website needs a text description so that people who are blind can hear what the image shows. An image with no description at all is an instant problem that a scanner catches in under a second. But "has a description" and "has a useful description" are different things. File names used as descriptions (like "IMG_4421" or "photo-1.jpg") technically exist but don't actually describe the image. Generic descriptions ("image," "photo," "staff member") fail too. Team photos where everyone is described as "staff member," product images where each one just says "product photo," stock photos with keyword-stuffed text instead of real descriptions—all of these are problematic. Because images cover every page of most websites, these issues often appear in the opening paragraph of a demand letter with a long list of specific examples that look damning to a judge.
Unlabeled contact forms: the violation most likely to anchor a discrimination framing
When a blind person using screen-reading software navigates to a form field, the software announces the label so they know what to type. If the field has no label— just placeholder text that disappears when you click into it—the software announces nothing. The visitor has no idea what the field is for. Contact forms on small business sites are where this shows up constantly: Name, Email, Phone, and Message fields styled with placeholder text and nothing else. The demand letter frames this as your contact form being inaccessible to blind customers — and that framing works because not being able to contact a business is a clear, direct injury. It's hard to argue your site doesn't discriminate when a blind customer literally cannot fill out your contact form to request your services.
Insufficient color contrast: flagged on virtually every site using light brand colors
The accessibility standard requires a specific minimum contrast ratio between text and its background — a number, not a design opinion. Light gray text on white, pale text on a pastel background, light-colored placeholder text inside form fields— these look acceptable to people with typical eyesight and fail the mathematical requirement for people with low vision or color blindness. Most small business sites use some combination of light text, pastel buttons, or gray secondary content without ever checking the contrast numbers. The scanning software doesn't care whether it looks fine to you. It calculates the ratio and flags the problem if the number doesn't meet the minimum. This is one of the most common violations on small business sites and one of the easiest for a scanner to find and document automatically.
Broken keyboard navigation: the problems that only show up when someone tests without a mouse
After the automated scan identifies a site worth pursuing, some plaintiff's firms send a manual reviewer to spend ten minutes navigating with only a keyboard. This is where they find the problems that automation can't detect: navigation menus that close when you arrow through them, dropdown menus that open on click but don't respond to keyboard keys, popups that can be opened by keyboard but can't be closed without a mouse, sliders and carousels with no keyboard control at all. These failures are common on sites built with interactive components that were never tested without a mouse. They also represent the strongest evidence of functional inaccessibility: the site doesn't just work poorly for keyboard users — it doesn't work at all for specific tasks.
How a demand letter turns into a settlement: and where accessibility documentation breaks the chain
Most small business owners who receive an ADA web accessibility demand letter have never thought about website accessibility before the letter arrives. The letter comes from a law firm they don't recognize, cites technical violations they've never heard of, demands a settlement in the $10,000 to $25,000 range plus attorney fees, and gives them a window to respond or face a federal complaint. Here is how that sequence unfolds— and where documented WCAG compliance stops it.
The letter is the first contact. There's rarely a prior complaint or a request to fix anything. The ADA doesn't require advance notice before a lawsuit can be filed— inaccessibility is the violation, and it's already documented by the time the letter is sent. The plaintiff's attorney has a scanner, a list of sites in your business category, and a template. The cost of sending the letter is near zero. The cost to you of responding (attorney fees to evaluate the claim, potential settlement, remediation as a condition of any settlement) is not near zero.
Most small businesses settle. Federal ADA lawsuits are filed in districts where the filing cost for the plaintiff's firm is low and defending in federal court is expensive regardless of the merits. A settlement that includes remediation plus $5,000 to $15,000 looks reasonable compared to federal litigation costs, even if the business owner is confident the claim wouldn't survive a challenge. Demand letters are sized to the cost of not settling, not to the cost of the underlying violation.
WCAG compliance with documentation breaks the chain at the beginning. A site that passes an automated scan and has a record of manual screen reader and keyboard testing is not a viable target for scan-based demand letters — there are no violations to cite. A site with a written compliance report is also in a substantially stronger position if a complaint is filed anyway, because documented evidence of good faith remediation is relevant at every stage from settlement negotiation through trial.
The cost comparison runs one direction. Remediation is a one-time project. A demand letter settlement requires both a payment and a compliance obligation — you end up doing the remediation anyway, plus paying the settlement, plus paying your own attorney to evaluate and respond. Doing the remediation before the letter arrives costs less and produces more protection. The written compliance report from an ArdinGate audit is exactly what an attorney would tell you to get after receiving a demand letter. Getting it before means you're not paying legal fees to be told to do something you could have done for a fraction of the cost.
Why every business that bought an accessibility overlay widget still has an inaccessible website and a new legal risk on top of it
Accessibility overlay products — AccessiBe, UserWay, AudioEye, and their competitors— sell themselves as turnkey compliance solutions. One line of code, a monthly subscription, compliance guaranteed. The compliance guarantee in most of their contracts is narrow and rarely applies to actual ADA litigation. Here is what overlay widgets actually do and why they are not a substitute for fixing the underlying code.
Overlay widgets cannot fix what is broken in the underlying site. An overlay is a program that runs in your visitor's browser, on top of your existing page. It can intercept some keyboard inputs and try to adjust color contrast on the fly. What it cannot do is add structure that was never in your site's code. It cannot make an unlabeled form field properly labeled—at best it can guess a label from surrounding text, which is unreliable and often wrong. It cannot repair navigation that was never built to work with a keyboard. When the overlay tries and fails, it often makes the experience worse for blind visitors using screen-reading software than the underlying broken site would have been.
Blind visitors disable overlay widgets to use their own tools. The National Federation of the Blind, the American Council of the Blind, and a large body of documented feedback from blind internet users show that overlay products frequently interfere with the screen-reading software users rely on rather than helping it. Many blind visitors have configured their software to block known overlay scripts entirely. When the overlay is blocked, the underlying problems on your site are fully exposed — which is exactly the state your site is in when a litigation scanner runs against it.
Overlay widgets have appeared in ADA lawsuits as evidence against the business. The presence of an overlay widget shows a judge that the site owner was aware of the accessibility problem and chose an ineffective product rather than fixing the underlying code. That interpretation has appeared in multiple notable cases against companies that had overlay subscriptions active at the time of the lawsuit. The courts found the sites non-compliant. The overlay was not a defense — it was proof of negligence.
The numbers don't favor overlay widgets. AccessiBe starts around $490 per year for small sites (as of mid-2026) — an annual recurring cost with no end date, for a product that doesn't achieve compliance and may actively worsen the experience for the people it's supposed to help. Code-level remediation is a one-time project that fixes the actual problems, comes with a written compliance report, and requires no ongoing subscription. Three years of an overlay subscription exceeds what most small business sites cost to remediate properly — and at the end of those three years, the underlying problems in your code are still there.
See the full breakdown: WCAG compliance guide — what works and what doesn't →
Pricing
Accessibility remediation on an existing site is quoted by page count and complexity after a brief intake conversation. Most small business sites in the five-to-fifteen-page range land between $800 and $1,800 for a full audit and code-level remediation, including the written compliance report.
The audit alone — without remediation — is also available. This works for site owners who want to understand the scope of violations before committing to fixes, or who need a violation inventory to bring to their existing developer.
What moves a project toward the higher end: more pages or more complex page designs; PDFs or downloadable documents served from the site (the accessibility rules apply to documents too, not just web pages); complex interactive elements like multi-step forms, image carousels, accordions, or popups; or structural problems in the site's code that require more than targeted fixes. If a project has unusual complexity, that gets assessed during intake and built into the quote — no surprises mid-project.
For new website builds, legal accessibility compliance is built in from the start at no additional charge. When accessibility is part of the build from day one — proper structure, labeled forms, keyboard-navigable components — there is nothing to remediate later. New builds start at $1,200 for single-page sites and $2,800–$5,000 for multi-page projects. Compare that to the $800–$1,800 remediation cost of retrofitting a site built without accessibility in mind, or the $10,000–$50,000 settlement cost of a demand letter that arrives because the site was never fixed.
Ongoing accessibility maintenance — reviewing any new content or feature additions for WCAG compliance before they go live — is available as an add-on to managed hosting plans. Managed hosting starts at $30/month for uptime monitoring, nightly backups, SSL, and server-level security patching; the $50/month tier adds an hour of content edits and application-level patching. Accessibility review of changes is available as a line item within that maintenance structure.
Website accessibility remediation: questions and answers
Is my website legally required to be accessible?
The ADA doesn't name websites explicitly, but federal courts have consistently ruled that business websites count as places of public accommodation under the same law that requires a physical store to have a ramp. The Department of Justice confirmed this position in 2022 guidance and explicitly named the legal compliance standard. Demand letters from law firms targeting inaccessible small business sites have been rising steadily for years. These firms scan entire categories of businesses — all the restaurants in a metro area, all the dental offices, all the salons — and send demand letters before the business ever hears about a complaint. Settlement costs in ADA web accessibility cases commonly run $10,000 to $50,000 before attorney fees on either side. The cost of remediation is a fraction of that. Accessibility compliance guide →
What will an accessibility remediation do to my website?
It fixes the underlying code problems—the ones that make your site difficult or impossible to use for people who are blind or rely on keyboard navigation. Missing descriptions on images get written and added. Contact forms that were completely unlabeled get properly labeled so screen-reading software can announce what each field is for. Color combinations that don't meet readability requirements get adjusted. Interactive elements that only worked with a mouse get built to work with a keyboard too. Most of these changes are invisible to someone using the site normally with a mouse—but they're the difference between your site working and not working for roughly 26 percent of American adults who have some kind of disability. You also get a written report documenting everything that was found and fixed, which matters if you ever receive a legal demand letter.
Can I just install an accessibility widget and be done with it?
No—and this is worth understanding clearly. Accessibility overlay widgets—the floating toolbar buttons from companies like AccessiBe, UserWay, and AudioEye—cannot fix the underlying code problems on your site. They try to work around broken HTML in the browser, but they cannot add structure that was never there, fix form fields that were never labeled, or repair navigation that was never built for keyboard use. The National Federation of the Blind and the American Council of the Blind have both documented extensively how these products interfere with the screen-reading software their users rely on. Multiple ADA lawsuits have cited the presence of an overlay widget as evidence against the business— showing the owner knew about the problem and chose an ineffective fix rather than actually fixing it. Overlay widgets also cost $400 to $800 per year with no end date (as of mid-2026). Code-level remediation is a one-time project that fixes the underlying problems.
How much does accessibility remediation cost?
Audit and remediation on an existing site is quoted based on page count and complexity after a brief intake conversation. Most small business sites in the five-to-fifteen-page range land between $800 and $1,800, including the written compliance report. What moves a project higher: more pages, PDFs or downloadable documents that also need remediation (the accessibility rules apply to documents served from your site, not just web pages), complex interactive elements like multi-step forms or image carousels, or underlying structural problems in the site's code that require more than targeted fixes. For new website builds, legal accessibility compliance is built in from the start at no additional charge. New builds start at $1,200 for single-page sites and $2,800–$5,000 for multi-page projects. Compare that to a settlement in an ADA demand letter case, which commonly runs $10,000 to $50,000. Full pricing →
How long does the remediation take?
For a small business site of five to fifteen pages, the full process—automated scan, manual keyboard testing, screen-reading software testing, code fixes, and written compliance report—runs three to seven business days. The audit phase (finding everything wrong) usually takes one to two days. How long the fixing takes depends on what the audit finds: a site that mostly has missing image descriptions and unlabeled form fields is faster than one with broken keyboard navigation throughout or forms built without any proper structure. If you're working against a specific legal deadline (a demand letter response window or a court-ordered compliance date), bring that up at the start and the project gets scoped and scheduled around it, not revised partway through.
What's in the written compliance report?
The report is a PDF document that covers: which pages were reviewed and what testing tools and screen readers were used; a complete list of every problem found before any fixes were applied, organized by type and severity; confirmation of every fix that was made, with before-and-after details for each one; the specific rule reference for each issue (rule number, name, and which compliance level it addresses); the date the audit was conducted; and a statement saying the site meets the legal accessibility standard. The report is written to be readable by an attorney, a compliance officer, or a court, not just a developer. If you receive a demand letter after the remediation is complete, this is the documentation your attorney uses to negotiate a settlement or show the court what was done and when.
Will this change how my website looks?
Rarely in any noticeable way. The most common problems (missing image descriptions, unlabeled form fields, broken keyboard navigation, missing behind-the-scenes structural markers) are completely invisible to someone using the site normally with a mouse and good eyesight. They only affect people using screen-reading software or navigating without a mouse. The fixes that can affect how the site looks are color readability adjustments, which sometimes require darkening text or button colors slightly to meet the minimum contrast requirement. If any visible design change is needed, you see it first and decide whether to proceed before anything goes live. Most sites look identical after remediation. What changes is how the site works for people who need assistive technology—which is the point.
Does fixing accessibility issues help my Google ranking?
In several concrete ways, yes. Descriptive image descriptions are both an accessibility requirement and something Google uses to understand your images — which contributes to image search visibility. Proper heading structure (which accessibility requires) gives Google a clearer outline of what your page covers. Clean, well-structured code tends to load faster, which Google factors into rankings. Clear section labels help Google understand what each part of your page is about. These aren't vague indirect benefits— they're direct overlaps where the right accessibility fix is also the right thing for Google. A site with proper structure, descriptive image text, and clean code ranks better than the same site without those things, regardless of any accessibility intent.
I already got an ADA demand letter. Can you still help?
Yes, and demand letter timelines are something ArdinGate factors in from the first conversation. If you've received a letter, the immediate priority is understanding which violations were cited, whether they're still present on your current site, and how much time you have to respond. The written compliance report from an ArdinGate audit documents what was found and what was fixed with specific rule citations and dates—exactly what an attorney needs to negotiate a settlement or demonstrate to a court that the business took the violations seriously and fixed them. Demand letter response windows are usually 30 to 60 days; in most cases a full remediation can be completed comfortably within that window. Mention the letter and its deadline at the start of intake so the project gets scoped and scheduled accordingly rather than treated as a standard timeline project.
Do I need ongoing accessibility maintenance after the initial remediation?
If your site gets updated regularly, yes. Accessibility isn't a one-time checkbox— every new image, form field, page, or interactive element added without accessibility in mind can introduce new problems. The most common drift: new photos added without descriptions, new contact form fields added without labels, new interactive sections added without keyboard support. A site that was fully compliant at remediation can slip out of compliance within months if content is added without checking it. ArdinGate offers an accessibility review add-on within monthly maintenance plans that checks any content or feature changes before they go live. For sites that are rarely updated, a re-audit every twelve to eighteen months is usually enough to catch any drift before it accumulates into a compliance gap.
Can ArdinGate fix accessibility on a WordPress or Shopify site?
The audit process is the same and the written compliance report covers the same scope. What changes is what can be fixed in code. Theme files and core platform code are sometimes locked or outside the scope of what a third-party developer can safely modify without causing other problems. In those cases, every problem gets documented and categorized: fixable within the current setup (theme overrides, custom styling and code), requiring a theme switch or custom development to address properly, or a known platform limitation that can't be fixed without changing the platform itself. You get a full picture of what's wrong and what can be fixed as things stand, not a remediation scoped around what's convenient to fix. For sites with deep problems caused by a low-quality theme or inaccessible plugin, the report will say so directly.
Do accessibility rules apply to PDFs on my site?
Yes. If a document is served from your website — a menu PDF, a service brochure, a pricing sheet, a fillable form — the accessibility requirements apply to it. An untagged PDF (the kind most small businesses create by printing to PDF from Word or a design tool) is completely inaccessible to screen readers. The text is present as an image, not as readable content. A blind visitor using screen-reading software hears nothing, or hears garbled nonsense. ArdinGate can remediate PDFs as part of a site project or as a standalone engagement. The process involves adding proper structure tags so a screen reader can follow the document in order, adding descriptions for any images inside the PDF, and labeling any fillable fields. Document remediation is scoped and priced separately from the website audit and gets assessed during intake if your site serves downloadable documents.
What does the legal accessibility standard mean in plain English?
The standard is a set of rules published by an international web standards organization that defines what "accessible" means for websites. It has three levels: minimum, standard, and enhanced. The standard level is what courts, the Department of Justice, and accessibility auditors use as the legal compliance target for business websites. It covers 50 specific requirements organized around four principles: your site needs to be perceivable (people can see or hear the content even if they're blind or deaf), operable (people can navigate it regardless of what input device they use), understandable (the content makes sense and works predictably), and robust (it works with assistive technology like screen readers and braille displays). In practice, meeting the legal standard means your site works for people who are blind, low-vision, deaf, or who navigate without a mouse—and you have a documented compliance record if anyone ever sends you a legal complaint claiming your site excludes them.
Need WCAG compliance documentation before a deadline?
Tell me about your site, any legal context or demand letter timeline, and what platform it's built on. I'll scope the audit and remediation upfront and give you a flat quote within 5 business days.
Get a quote