Person typing code on a laptop with a screen displaying a dark-themed code editor, ensuring ADA compliance services are seamlessly integrated.

A website should work for everyone who visits it

An accessible website works for everyone who visits it, including people using screen readers, keyboard navigation, or other assistive technology. It’s also a real compliance issue: WCAG 2.1 AA is the standard U.S. courts and DOJ guidance point to, and government sites have been required to meet it since April 2026. This isn’t an overlay widget you drop in and forget. It’s real audit and repair work, priced by the size of your site.

Accessibility work means making sure your site actually works for people using screen readers, keyboard navigation, or other assistive technology, not just people browsing with a mouse on a fast connection. We build and repair against WCAG 2.1 AA plus general best practices and our own internal Optik standards, since that’s what web professionals, U.S. courts, and government guidance treat as the real benchmark.

700+

25+

4.9/5

What we offer

For new website projects

For existing websites

Accessibility Review

Who it’s for: Sites we didn’t build, or Optik Theme sites older than 5.0.

What’s included: Full audit using pro scanning tools plus a manual review of semantic code, keyboard navigation, alt text, and usability. You get a written report with every issue found and an estimated cost to fix. Audit only — fixes come next.

Accessibility Repair

Who it’s for: Sites that finished a Review, or Optik Theme 5.0+ sites (which can skip the Review).

What’s included: The actual fix work. We modify your theme, features, and content to bring the site up to WCAG 2.1 AA. Final price is quoted from the Review findings.

Accessibility Care Plan

Who it’s for: Sites that just launched with Setup, or finished a Repair within the last 6 months.

What’s included: Ongoing coverage. Quarterly (or monthly on larger plans) reviews, 30-60 minutes of live training, priority repair turnaround, email support, and optional helper plugins like AltText.ai and WP One Tap. 6-month minimum.

Blog posts count as 0.25 pages toward the total. PDFs don’t count — we don’t edit PDFs.

How we handle it

We don’t force it into every project

Historically, the lawsuit risk for a small business has been low, and accessibility work adds real cost and complexity that not every client can or wants to take on. So we offer it to every prospect and encourage it, but we don’t ship it as a mandatory line item on every build.

What changed in April 2026

The DOJ made WCAG 2.1 AA mandatory for government sites: municipalities, libraries, police and fire departments, park districts, and the like. Every one of our government projects now includes accessibility by default. For everyone else, it’s still your call, but the risk keeps rising and the lawsuits are getting easier to file.

What WCAG 2.1 AA actually covers

WCAG is built on six principles. Every fix we make maps back to one of these:

Text alternatives.

Alt text on images and graphics so screen readers can convey what’s there. Captions on videos.

Keyboard accessibility.

Every interactive element (menus, buttons, forms, dropdowns) works without a mouse.

High perceivability.

Enough color/brightness contrast between text and background so people can actually read it. 4.5:1 for body text, 3:1 for large text and interactive elements.

Easy operability.

Multiple ways to move through the site: menus, sitemap, search, breadcrumbs. Interactive elements are clearly navigable.

Understandability.

Clear language, logical heading hierarchy (H1, then H2, then H3, no skipping), descriptive link and button text (not “click here”).

Robustness.

Semantic HTML and proper labeling so the site works with a range of assistive technology, not just one tool.

Note: anyone who tells you they’ll make your site “ADA compliant” is being misleading. The ADA was written in 1990, before modern websites existed, and doesn’t outline specific web criteria. WCAG is the framework U.S. courts, DOJ guidance, and the industry all point to. That’s what we build and repair against.

What we handle

Your theme, code, content structure, semantic HTML, keyboard navigation, alt text, and everything under WCAG 2.1 AA that lives in the site itself. We deliver against WCAG 2.1 AA, current Best Practices, and our own internal Optik standards.

What’s out of scope

PDFs uploaded to your site (that’s on you to test), video captions (that’s your producer’s job), and third-party embeds, code snippets, and iframes. When we find those during a Review, we’ll tell you about them and usually recommend swapping to an accessible external link if the embed itself can’t be fixed. We’d rather be upfront about what’s ours and what isn’t than quietly leave gaps in a report.

How it works and what it costs

Every accessibility project is priced by the size of your site, not a flat number that ignores whether you run 8 pages or 800.

FAQs

What’s WCAG 2.1 AA and why is it the standard?

WCAG 2.1 AA is a set of technical guidelines for making websites usable by people relying on screen readers, keyboard navigation, and other assistive technology. The ADA itself doesn’t spell out web-specific requirements, so WCAG 2.1 AA has become the benchmark U.S. courts and DOJ guidance actually point to when they evaluate a site. It’s also what we build and repair against, alongside our own internal Optik standards.

Do I really need to worry about lawsuits?

It depends on your situation, and we’ll be straight with you about it. If you run a government site, it’s mandatory now, not optional. If you’re in a lawsuit-prone industry like retail, restaurants, healthcare, or financial services, the risk is real and rising. For everyone else, historically the risk for a small business has been lower, which is part of why we don’t force accessibility into every project. We offer it to every prospect and encourage it either way.

Do overlay widgets work?

Not really. Overlay widgets promise instant compliance from a single line of code, but they tend to paper over problems instead of fixing the underlying code, content structure, and markup. Courts have started seeing through them in lawsuits. We don’t sell that as a solution.

What if my site has PDFs and third-party embeds?

Those fall outside our scope, and we tell you that upfront. PDFs uploaded to your site are yours to test. Video captions are your producer’s responsibility. Third-party APIs, code snippets, and iframes aren’t something we can fix directly, but if we spot an accessibility problem in one during a Review, we’ll flag it and usually recommend swapping to an accessible external link.

What’s the difference between Review, Repair, and the Care Plan?

A Review is audit-only: we scan and manually check your site and hand you a report with the issues and an estimated cost to fix them, no fixes included. Repair is the actual fix work, either based on a Review’s findings or done directly if you’re on an Optik Theme 5.0+ site. The Care Plan is ongoing: quarterly reviews, training, priority repair, and email support, for clients who want accessibility handled on a continuing basis instead of a one-off project.

What to look at next

Illustration of a rocket launching from a laptop screen with clouds in the background, symbolizing technology, innovation, or a digital startup.

Ready for a site that actually works for everyone?

Book a free 20-30 min call. We’ll look at your site, tell you what makes sense, and quote a real number.