bitclone
Desert landscape near Tucson under a wide blue sky.

Accessibility readiness

Get your website ready for the new accessibility rules.

For public entities, nonprofits, and businesses that want a clear path — scan, fix, and document — without fear-mongering or empty promises. The first step is a free scan of your homepage.

Request a free homepage scan

Context

What’s actually changing

  • The DOJ’s ADA Title II rule requires state and local government web content and mobile apps to meet WCAG 2.1 Level AA.
  • Compliance dates were extended in April 2026: April 26, 2027 for entities serving 50,000 or more people; April 26, 2028 for smaller entities and special district governments.
  • Private businesses aren’t covered by that Title II rule, but website accessibility lawsuits under ADA Title III remain frequent — 3,117 federal filings in 2025 per Seyfarth Shaw.

Last reviewed: October 2026. This is general information, not legal advice.

Process

How it works

Four steps. You’ll work with us directly — no account manager in the middle.

  1. Scan

    We run our own scanner against your site and pull out the issues that matter most.

  2. Review

    We read the results ourselves, check what automation misses, and prioritize a fix list with you.

  3. Fix

    We rebuild or repair in WordPress — GeneratePress and blocks — with accessibility built into the work.

  4. Re-scan & document

    We re-scan, write down what changed, and help you publish an accessibility statement.

Honesty first

What a scan finds — and what it can’t

Automated tools catch only part of WCAG. Manual review is part of our process. We don’t claim or promise that a site is “ADA compliant.”

A scan is good at

  • Missing or empty image text alternatives
  • Low-contrast text and controls
  • Form labels and basic keyboard traps
  • Heading structure and landmark gaps
  • Link names that don’t describe the destination

Still needs a human

  • Whether alt text is actually useful
  • Complex interactions and custom widgets
  • Content clarity and reading order in context
  • Real keyboard and screen-reader flow
  • Judgment calls on what’s “enough” for your users

Sample

What a report looks like

A short excerpt from the kind of summary we send after a scan. Plain language, prioritized — not a dump of raw tool output.

Sample report excerpt · public library district · anonymized
  • 25 pages scanned
  • 534 places failing automated checks, in 16 kinds
  • 509 places flagged for a person to judge
  • 231 linked PDFs, not scanned

Tested against WCAG 2.1 AA. A starting point, not a grade.

Three findings, in plain language

  1. Serious · WCAG 1.4.3 contrast

    One color is behind most of the problems

    White text on the site’s light green is hard to read for anyone with low vision. It shows up in the footer, buttons, and labels on every page.

    Fix: darken the green once, in the theme. That clears 391 places on all 25 pages.

  2. Critical · WCAG 4.1.2 name, role, value

    Dropdown menus have no name

    A screen reader announces the page-jump menu as just “combo box.” The visible label isn’t connected to it in the code.

    Fix: add a label and connect it to the menu. 8 places on 7 pages.

  3. Serious · WCAG 1.4.11 non-text contrast

    Form fields have no visible edge

    Search boxes and contact form fields blend into the page, so some visitors can’t tell where to click or type.

    Fix: give fields a darker border. 84 places on 7 pages.

What the scan can’t judge

Text over photos and gradients, the image carousel, keyboard focus, heading order, and all 231 PDFs. These go on a manual review list, and a person works through them.

In practice

Our own work

Case study · bitclone.com

We scanned our own site first

Before we asked anyone else to trust our scanner, we pointed it at this site. It found real problems, and we fixed them.

Oct 19 · first scan

50

places failing automated checks, in 6 kinds, across 9 pages

Oct 20 · after fixes

0

automated failures, across 10 pages

What it found

  • Orange links and tags that were too faint against the dark background, at 3.1 to 3.8:1 where 4.5:1 is needed.
  • Grey project details that missed by a hair, at 4.3:1. It looks fine to the eye and still fails.
  • Contact form fields with edges too faint to see.

All of it traced back to a few colors in the theme, so the fixes were small.

What it still can’t tell us

Zero automated failures is not the same as compliant. The same scan still flags 109 places for a person to review, mostly text over images and gradients and how the layout holds up when text is enlarged. We’re working through them by hand.

Ways to start

Engagement options

Most people start with the free scan. Every site is different, so we quote after a look at yours, and you’ll get a straight answer.

Free homepage scan

Free · no obligation

We scan your homepage, review it ourselves, and send a plain-language summary of what we’d fix first.

Request a scan →

Full audit

Broader coverage across key templates and flows, with a prioritized fix list.

Ask about an audit →

Remediation

We fix issues in WordPress — or rebuild where that’s the cleaner path.

Talk about fixes →

Ongoing care

Re-scans, small fixes, and help keeping your accessibility statement current.

Ask about care →

Questions

FAQ

Do you make websites ADA compliant?

We don’t promise or certify that a site is ADA compliant. Accessibility is an ongoing practice. We help you measure against WCAG 2.1 AA, fix what we can, document the work, and publish a clear accessibility statement.

What is a free homepage scan?

We run our scanner against your homepage, review the results ourselves, and send you a plain-language summary of the highest-priority issues. It’s a starting point for conversation, not a full-site audit.

Who is this for?

Public entities preparing for the DOJ Title II rule, nonprofits, and businesses that want a clearer path on website accessibility. We work best with WordPress sites, especially GeneratePress and block-based builds.

Can you work on a site we already have?

Yes. Most of this work is remediation on existing WordPress sites. If a rebuild is the better path, we’ll say so before you spend money.

How is your scanner different from free online tools?

We built our own scanner so we can tune how results are grouped and reported for the sites we actually fix. Automated tools only catch part of WCAG. Manual review is still part of our process.

What happens after we contact you?

Tell us your URL and what you’re trying to accomplish. We usually reply the same business day with next steps — often starting with a free homepage scan.

Ready for a clear look at your homepage?

Send us your URL. We’ll scan it, read the results ourselves, and tell you what we’d fix first.

Request a free homepage scan