Service · Accessibility
ADA accessibility remediation you can document
Law firms scan thousands of small-business sites; most have accessibility violations: missing image descriptions, unlabeled forms, mouse-only navigation. ArdinGate provides a full WCAG 2.2 Level AA audit, manual screen-reader and keyboard-only testing, code-level fixes for every problem, and a dated attorney-ready report of tests, findings, and fixes. No overlays, partial scans, or shortcuts.
Six things a complete accessibility remediation covers
Most ADA demand-letter recipients didn't know their site had violations. Finding them requires testing as assistive-technology users do: listening to every word through a screen reader or navigating by keyboard. Full remediation follows this sequence.
Automated scan to find the obvious violations and sort them by severity
Professional software used by large compliance teams and federal agencies scans every page for missing image descriptions, unlabeled fields, low-contrast colors, and structural errors, ranked by severity. It catches 30 to 40 percent of problems; the rest requires testing as blind or keyboard-only users navigate.
Keyboard navigation testing: using the site without a mouse to catch broken elements
Many disabled visitors navigate entirely by keyboard. ArdinGate tests every page's links, buttons, fields, dropdowns, popups, and overlays for reachability, visible position, logical navigation order, and mouse-free popup closure. Mouse-only testing misses these failures, which rank among the most-cited ADA demand-letter violations.
Screen reader testing with three different programs to catch what the automated scan missed
Screen readers read pages aloud for blind or low-vision visitors. ArdinGate tests NVDA and JAWS, Windows' two most-used programs, plus VoiceOver, built into every Mac and iPhone. Each exposes different problems: vague image descriptions, unannounced field names or errors, and navigation unintelligible without seeing the layout. Automated tools cannot assess these.
Color contrast check: every piece of text and every button measured for readability
Accessibility standards set mathematical minimum text/background contrast for low-vision and color-blind readers; buttons, field borders, and other controls have separate minimums. Common failures on small-business sites with unchecked palettes include gray-on-white text, pale placeholders, and pastel buttons. Every text and interactive element is measured. You approve proposed adjustments before application.
Code-level fixes for everything: no overlay widgets, no problems ignored or worked around
Every audit finding receives a code-level fix: descriptive image alternatives, screen-reader field labels, readable colors, and structurally corrected keyboard navigation. Unfixable problems and reasons are explicitly documented for your acceptance; nothing is hidden. Every fix is retested. No overlay shortcuts: these products don't fix problems and have been cited as bad-faith evidence against businesses in ADA lawsuits.
Written compliance report: a dated PDF record of what was tested, found, and fixed
The deliverable isn't just a fixed website: it's a document. A PDF compliance report covering:
- Which pages were reviewed and what tools were used
- A complete inventory of every problem found before any fixes were applied
- Confirmation of every fix made, with before-and-after details
- The specific accessibility rule reference for each issue
- The date of the audit and a statement of where the site stands against WCAG 2.2 Level AA as of that date
Attorneys, compliance officers, and developers can use this dated, specific record of good-faith remediation, including when responding to a later ADA demand letter. It is neither a legal opinion nor a guarantee against claims.
The accessibility problems that get found first, usually before you know they're there
Reportedly, firms pursuing ADA web claims in volume generally scan business lists by category: metro-area restaurants, medical practices, salons. Scans take seconds per site, without anyone browsing for problems. Below are common findings, roughly ordered by their frequency on small-business sites.
Missing or meaningless image descriptions: the failure scanners flag most often
Non-decorative images need descriptions blind visitors can hear. Scanners detect missing descriptions in under a second; existing descriptions can still fail: filenames ("IMG_4421", "photo-1.jpg"), generic "image" or "photo", team members all labeled "staff member", products all labeled "product photo", or keyword-stuffed stock-photo text. Images span most sites' pages, producing long, itemizable violation lists that often lead complaints.
Unlabeled contact forms: the failure with the clearest real-world consequence
Screen readers announce field labels so blind visitors know what to type. Placeholder-only fields announce nothing; placeholders disappear on entry. Small-business contact forms commonly leave Name, Email, Phone, and Message unlabeled. Complaints often lead with this concrete barrier to contacting you. Proper labeling is also among the cheapest fixes.
Insufficient color contrast: flagged on virtually every site using light brand colors
Accessibility standards require a mathematical minimum text/background contrast. Gray-on-white, pale-on-pastel, and light placeholder text can look acceptable to typical eyesight while failing low-vision or color-blind users. Small-business sites commonly use unchecked light text, pastel buttons, and gray secondary content. Scanners calculate ratios and flag failures automatically, making this widespread violation especially easy to document.
Broken keyboard navigation: the problems that only show up when someone tests without a mouse
After an initial scan, claims reportedly often involve a few minutes of manual keyboard testing. It exposes failures automation misses: menus closing during arrow navigation, click-only dropdowns, popups that open by keyboard but require a mouse to close, and keyboard-inoperable sliders or carousels. Components never tested without a mouse commonly make specific tasks entirely inaccessible, strong evidence of functional barriers.
Missing skip navigation: a small fix that determines whether keyboard users tolerate your site at all
A hidden skip link at the top of the page lets keyboard and screen-reader users jump past repeated navigation straight to page content. Without one, every single page visit means tabbing through the full menu, sometimes 20 or more presses, before reaching anything new. It's a near-zero-effort fix and one of the first things a manual tester checks, since its absence signals no keyboard testing was ever done.
Silent state changes: menus, popups, and form errors that never announce themselves to a screen reader
Opening a menu, submitting a form, or triggering an error updates the screen visually but often announces nothing to a screen reader. Without the invisible markup that reports state changes, a blind visitor can't tell whether a menu opened, a submission succeeded, or a dialog is waiting for input. This is the failure behind demand letters that cite "no programmatic notification of changes" — a violation invisible to anyone not testing with actual assistive technology.
What usually happens after a demand letter arrives, and where documentation changes the picture
Most small-business recipients first consider accessibility when an unfamiliar law firm's ADA letter cites unfamiliar technical violations, settlement and attorney fees, and a response deadline before federal complaint. Below is the reported general pattern, not legal analysis or a prediction for any claim.
Letters usually arrive without prior complaints or repair requests. Federal law generally requires no advance ADA-claim notice; some states add notice rules. Sending costs almost nothing; responding entails attorney evaluation fees, any settlement, and required remediation.
Most claims reportedly settle: federal defense costs, regardless of merits, can exceed remediation plus payment even for seemingly weak claims. Letter amounts tend to reflect litigation costs rather than underlying problems. Published settlements therefore vary widely and cannot benchmark your costs.
Passing scans plus documented manual screen-reader and keyboard testing leave scan-based letters less to cite. If a complaint arrives, your dated report provides specific evidence of good-faith remediation for an attorney's response. Its value in any dispute is for your attorney to assess.
Remediation is one-time work; settlements generally require that work plus payment and your attorney's evaluation and response fees. Attorneys will likely request a written compliance report after a letter arrives. Having it beforehand avoids paying legal fees to be told to obtain it.
Why every business that bought an accessibility overlay widget still has an inaccessible website and a new legal risk on top of it
AccessiBe, UserWay, AudioEye, and competing overlays promise compliance through one code line and a monthly subscription. Contractual guarantees are generally narrow; read their coverage. These widgets cannot substitute for underlying code repairs.
- Overlays cannot repair underlying code. Browser scripts intercept keyboard input or adjust contrast but cannot supply missing structure, reliably label fields from guessed context, or repair mouse-only navigation. Failed attempts often worsen screen-reader access beyond the original broken site.
- Blind visitors disable overlays for their own tools. The National Federation of the Blind, American Council of the Blind, and extensive user feedback document frequent screen-reader interference. Many users block known overlay scripts, exposing the underlying failures just as litigation scanners see them.
- Overlays have appeared against defendants in ADA lawsuits. Subscribers still face suits; plaintiffs argue widgets show owners knowingly bought ineffective products instead of repairing code. Success of that argument depends on the case. Overlays have not delivered their advertised protection.
- Overlay economics fall short. AccessiBe starts around $490/year (mid-2026), indefinitely, without achieving compliance and potentially worsening access. One-time code repairs fix problems, include a written report, and require no subscription. A few subscription years add up to the cost of a one-time fix while leaving the code broken.
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 $1,500 and $4,500 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
- Structural problems in the site's code that require more than targeted fixes
Unusual complexity gets assessed during intake and built into the quote, so there are no surprises mid-project.
New builds include WCAG 2.2 Level AA conformance free: proper structure, labeled forms, keyboard navigation, and no later retrofitting. Single-page from $1,200; multi-page: $2,800–$5,000. Compare $1,500–$4,500 retrofitting costs or demand-letter responses, commonly reported in five figures including both sides' attorney fees.
Optional prelaunch WCAG 2.2 AA reviews of content/features are managed-hosting add-ons. Hosting: $60/mo includes uptime monitoring, nightly backups, SSL, server-level patches; $100/mo adds up to an hour of content edits a month, quarterly performance reviews, and application-level patches. Accessibility reviews are separately itemized.
Website accessibility remediation: questions and answers
Is my website legally required to be accessible?
The ADA doesn't explicitly name websites; law remains contested. Federal appeals courts split between standalone websites as public accommodations and sites connected to physical locations. Department of Justice 2022 guidance says ADA covers public-facing business websites; WCAG is a reference, not a binding private-business technical standard. Demand letters have risen for years: firms scan entire local categories (restaurants, dental offices, salons), sending letters before businesses hear complaints. Reported settlements commonly reach five figures before either side's attorney fees; outcomes vary, with no promised amount. Remediation generally costs a fraction of claim response. This isn't legal advice; consult your attorney. Accessibility compliance guide →
What will an accessibility remediation do to my website?
Remediation fixes code barriers for blind and keyboard-only users: adds descriptive image text and spoken contact-field labels, corrects unreadable colors, and makes mouse-only controls keyboard-operable. Most fixes are invisible to mouse users but can determine usability for roughly 26 percent of American adults with disabilities. A written findings-and-fixes report also documents the work for any later legal demand.
Can I just install an accessibility widget and be done with it?
No. AccessiBe, UserWay, and AudioEye toolbars work around broken HTML in-browser; they cannot supply missing structure, field labels, or keyboard navigation. The National Federation of the Blind and American Council of the Blind document interference with screen readers. Overlay users still face lawsuits; plaintiffs have cited widgets as evidence owners knowingly bought ineffective fixes. Overlays cost $400 to $800 annually indefinitely (mid-2026); code-level remediation fixes underlying problems once.
How much does accessibility remediation cost?
After brief intake, page count and complexity determine quotes. Most five-to-fifteen-page sites cost $1,500–$4,500 including the report. More pages, downloadable documents (also subject to accessibility rules), multi-step forms, carousels, or deep structural repairs cost more. New builds include WCAG 2.2 Level AA free: single-page from $1,200; multi-page from $2,800–$5,000. Compare reported ADA settlements commonly in five figures before either side's attorney fees. Full pricing →
How long does the remediation take?
Five-to-fifteen-page sites take three to seven business days for scanning, manual keyboard/screen-reader tests, fixes, and reporting. Audits usually take one to two days; missing descriptions or labels fix faster than pervasive keyboard failures or structurally broken forms. Disclose legal deadlines, including letter response windows or court-ordered dates, at intake so scope and schedule accommodate them from the start.
What's in the written compliance report?
The PDF records reviewed pages, testing tools and screen readers, every original finding by type/severity, every fix with before/after details, rule numbers/names/conformance levels, audit date, and dated WCAG 2.2 Level AA status. Written for attorneys, compliance officers, and developers, it documents tests, findings, and fixes for any later demand-letter response. It is not a legal opinion or guarantee of any claim's outcome.
Will this change how my website looks?
Rarely noticeably. Missing descriptions, field labels, structural markers, and keyboard failures affect assistive-technology users but are invisible to mouse users with good eyesight. Contrast fixes may slightly darken text or buttons. You approve any visible changes before launch. Most sites look identical afterward; assistive-technology usability changes.
Does fixing accessibility issues help my Google ranking?
Yes. Descriptive image text helps Google understand images and improves image-search visibility. Proper headings outline page content; clear section labels identify each part. Clean, structured code tends to load faster, a ranking factor. These direct accessibility/SEO overlaps improve rankings versus the same site without them, regardless of accessibility intent.
I already got an ADA demand letter. Can you still help?
Yes. At intake, mention the letter and deadline; scope and scheduling account for them immediately. First, identify cited violations, whether they remain, and response time. Our report records findings, fixes, rule citations, and dates: evidence of serious, good-faith correction for your attorney's response. Your attorney assesses its weight in a dispute. Response windows usually span 30 to 60 days, comfortably enough for full remediation in most cases.
Do I need ongoing accessibility maintenance after the initial remediation?
Regularly updated sites need reviews: new photos without descriptions, unlabeled fields, or keyboard-inaccessible pages/features can undo conformance within months. ArdinGate's optional monthly-maintenance accessibility review checks content and feature changes before launch. Rarely updated sites usually need re-auditing every twelve to eighteen months to catch drift before gaps accumulate.
Can ArdinGate fix accessibility on a WordPress or Shopify site?
The audit and report scope stay the same; code access limits repairs. Locked themes or platform code may be unsafe to modify. Every finding is categorized: fixable through theme overrides/custom styling/code; requiring theme changes or custom development; or a platform limitation requiring migration. The report shows all problems and feasible repairs, explicitly identifying deep flaws in low-quality themes or inaccessible plugins.
Do accessibility rules apply to PDFs on my site?
Yes. Website PDFs (menus, brochures, pricing sheets, fillable forms) face accessibility requirements. Untagged PDFs commonly printed from Word/design tools present text as images, leaving screen readers silent or garbled. ArdinGate adds reading-order structure tags, image descriptions, and fillable-field labels, within site projects or standalone engagements. Document remediation is separately scoped/priced from the website audit and assessed during intake when downloads are present.
What does the accessibility standard mean in plain English?
WCAG (Web Content Accessibility Guidelines) comes from the World Wide Web Consortium (W3C), the international web-standards body, not Google or statute. Levels are A (minimum), AA, and AAA (enhanced). Auditors, DOJ guidance, settlements, and demand letters generally reference AA. Current WCAG 2.2 AA means meeting 55 requirements across four principles: perceivable (content seen/heard despite blindness/deafness); operable (navigation regardless of input device); understandable (clear, predictable content/behavior); robust (compatible with screen readers, braille displays, and other assistive technology). WCAG 2.2 AA conformance supports blind, low-vision, deaf, and mouse-free users, with a dated record for exclusion complaints. Technical conformance is not a favorable legal ruling; we do not sell it as one.
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. You get an upfront audit and remediation scope, plus a flat quote within 5 business days.
Get a quote