A site disabled users can actually use, built to the standard courts expect
When someone using a screen reader or keyboard cannot get through your site, you lose a customer and invite a demand letter. We assess your site against WCAG 2.2 AA, fix the failures in the code itself, and keep it conformant as it grows. No overlay widget, because overlays do not make a site compliant.
An inaccessible site costs you on both sides
The first cost is human and commercial. Roughly one in four US adults lives with a disability, and many rely on screen readers, keyboard navigation, voice control, or high-contrast modes. If your checkout, contact form, or booking flow breaks for them, they leave, and they rarely come back.
The second cost is legal. For more than a decade, US courts have applied Title III of the ADA to websites, and the volume of web accessibility lawsuits and pre-suit demand letters filed each year now runs into the thousands. “We didn't know” has not worked as a defense. The exposure is highest for businesses serving US customers and for regulated sectors, and it has been trending up year over year.
Built for businesses that can't afford to leave anyone out
Businesses serving US customers
Title III of the ADA has been applied to websites for years, and most demand letters target companies that sell to the US public. If that is you, accessibility is a live legal question, not a future one.
Healthcare, finance, and education
Patient portals, banking flows, and learning platforms face both ADA scrutiny and sector rules such as Section 508. These are also the sites disabled users most need to work flawlessly.
E-commerce and booking
If a screen reader user cannot complete checkout or a keyboard user cannot open your date picker, that is lost revenue on top of legal exposure. Conversion and conformance point the same direction.
Anyone already on notice
Received a complaint, a demand letter, or an internal flag from legal? We can triage the highest-risk failures first and give you a defensible remediation plan with dates attached.
Why the overlay widget is the wrong answer
You have probably been pitched a one-line script that promises instant ADA compliance. Be honest with yourself about what it can and cannot do. An overlay reads your existing page and tries to patch it at runtime, but it cannot rewrite broken semantics, supply meaning for unlabeled controls, or remove a keyboard trap built into your markup. Worse, it frequently collides with the screen reader and browser settings a disabled visitor has already tuned, degrading the very experience it advertises.
This is not a fringe opinion. Many companies running popular overlays have still been named in accessibility lawsuits, and a large coalition of accessibility professionals has publicly urged organizations not to rely on them. An overlay can give you a false sense of safety while leaving both the user barrier and the legal exposure fully intact. Conformance has to live in the code.
Audit, remediate, document, monitor
A full accessibility program, run by the same designers and engineers who build the site, not a drive-by scan.
- 01
Audit against WCAG 2.2 AA
We assess every key template and flow against WCAG 2.2 Level AA, the version most legal complaints now reference. Automated scanners catch maybe a third of real issues, so we pair them with manual keyboard testing and screen reader runs in NVDA, JAWS, and VoiceOver. You get a prioritized report that separates blocking failures from polish.
- 02
Remediate in the code
We fix issues at the source: semantic HTML and landmarks, focus order and visible focus states, name and role and value on custom controls via ARIA, color contrast, form labels and error messaging, captions, and reduced-motion handling. The result holds up to a real assistive-technology user, not just a green checkmark.
- 03
Document the conformance
We write an accessibility statement and a VPAT-style conformance record that shows what was tested, what passed, and what is in progress. If you ever receive a demand letter, this is the evidence of good-faith effort your attorney will ask for.
- 04
Monitor as the site evolves
A single new blog post, plugin update, or marketing landing page can reintroduce a barrier. We run scheduled scans, flag regressions, and keep your templates and component library accessible so compliance does not quietly decay between releases.
What this looks like in practice
Picture a regional clinic that books appointments online. A patient who is blind opens the page with a screen reader and reaches the date picker, but the calendar buttons have no accessible names, so they are announced only as “button, button, button.” She cannot tell which date is which, abandons the booking, and calls a competitor instead. Weeks later the clinic receives a demand letter citing that exact form.
An overlay widget would not have saved them: the calendar markup was the problem, and a script layered on top cannot infer what those unlabeled buttons mean. The fix was structural, correct ARIA names and roles on the date controls, a logical focus order, and a visible focus indicator, done in the code and confirmed with a real screen reader. That is the difference between looking compliant and being usable.
The honest version of what we can promise
No one can promise you will never receive a complaint, and any vendor offering “guaranteed compliance” from a quick install is selling you certainty that does not exist. Any public site can draw a demand letter. What genuinely moves your risk is real WCAG 2.2 AA conformance, a written record proving you tested and remediated in good faith, and maintenance that keeps it true over time. That is the work we sign up for, and it happens to be the same work that makes the site usable for the people it was excluding.
Frequently asked questions
The Web Content Accessibility Guidelines (WCAG) are the technical success criteria for accessible digital content, maintained by the W3C. The ADA itself does not name a version, but courts, the Department of Justice, and settlement agreements have consistently pointed to WCAG, and the current target is the 2.2 release at Level AA. Conforming to it is the practical way to show a good-faith effort to comply.
No. A JavaScript overlay that bolts a toolbar onto your existing markup cannot repair broken semantics, mislabeled controls, or a keyboard trap underneath it, and it often interferes with the screen readers users already have configured. Hundreds of overlay-equipped sites have still been sued, and many disability advocates actively oppose these tools. Real conformance lives in the HTML, CSS, and component code.
No honest vendor can, and anyone selling a guarantee from a one-line script is misleading you. Litigation can target any public-facing site. What materially lowers your risk is genuine conformance, written documentation of it, and ongoing maintenance, which is exactly the work we do.
Both, and the remediation is the point. Many audits stop at a spreadsheet you then have to staff and fix yourself. Our engineers correct the issues in your codebase and re-test to confirm each one is resolved.
Through monitoring plus fixing accessibility at the component level. When your buttons, forms, and templates are accessible by default, new pages built from them inherit that. Scheduled scans then catch anything a content editor or third-party embed slips in.
What clients say about working with us
Steve at OgreLogic is wonderful, so quick to respond to our website requests. The company is accommodating and accurate in their work on our website. Can't ask for more!
I hired OgreLogic for my spiritual custom website. They made it comfortable, and I felt like they knew what I was trying to accomplish. I am continuing to work with them through their maintenance program.
Ash has been working with us on our website for years and is one of the hardest working, dedicated team members we've met. He is reliable and always gets our tasks done in a professional, timely manner. We highly recommend him.
From the blog
Related reading from our blog
Landing Page Optimization in 2026: Anatomy of a Page That Converts
What separates a landing page that sells from one that leaks: message match, one goal, above-the-fold clarity, proof, friction removal, speed, and mobile.
How to Improve Website Speed in 2026: A Practical Guide
A practical 2026 guide to faster websites: why speed drives conversions and SEO, the biggest culprits, concrete fixes, and how to measure Core Web Vitals.
How Cloud Solutions Benefit Businesses in 2026 (and Where They Cost You)
A plain-English 2026 guide to what the cloud really is, the real benefits for small businesses, the honest tradeoffs, and how to choose without overpaying.