For small law firms

Every client should be able to use your intake forms.

A form can look fine and still read as a row of blank boxes to someone using a screen reader. I fix law firm websites in the site’s own code, forms included. I can also build a client portal or online intake to fit how your office runs.

I build and fix websites. I’m not a lawyer, and nothing here is legal advice.

An empty field gets an error that’s announced, focus moves to it, and the next step is announced by name. Sample app, invented data.
What I build

Accessibility work, and intake built to fit

  • The accessibility fixes

    I scan every published page at a desktop and a phone width, then go through the site by hand with a keyboard. I fix the shared template first, so one fix clears every page. The fixes go in the site’s own code, not in a widget on top of it.

  • Intake forms that hold up

    Every field gets a real label a screen reader can announce. Errors get announced too, and each step says where you are. A scanner can miss the later steps of a long form, so I check those by hand.

  • A statement and a dated record

    An accessibility statement names the standard, says what was tested and when, and tells people how to reach you if something gets in their way. It doesn’t make a site accessible on its own, so it goes alongside the fixes.

  • A client portal, if you need one

    This isn’t a product I sell. It’s something I’d build to fit your firm, so clients have one place for forms and documents.

Video: recreated with invented content, not any firm’s own pages.

What one firm’s site needed

A Miami-area law firm’s WordPress site, in October 2026

4,499failing elements in automated scans, before
0in the same scans on October 20, 2026
45pages, at desktop and phone widths
591intake form fields given a label

Nine in ten of the failures were one problem: the brand gold was too faint to read against white. Five of the eight kinds of failure lived in the header, footer and chat bubble, so fixing the template once cleared them on every page.

The part a scanner can’t see took the most care. The firm’s three intake questionnaires had about 225 fields whose labels weren’t connected, so a screen reader would announce a blank box.

Zero is a measurement on a date, not a permanent state, and automated tests catch only part of the problems. So the work also included manual checks.

The full case study, failure by failure →

Built to fit

A client portal or online intake, if your firm needs one

I don’t have a portal product to sell you. This is something I’d build to fit your firm, so this page has no feature list to compare. What it does depends on your practice and how your office runs today.

So the first step is a few questions:

  • Which forms do your clients fill out, and what happens to the answers after that?
  • Which documents do you end up chasing the most?
  • Who in your office needs to see what, and who shouldn’t?
  • What are you already paying for that might do this today?

If the practice management or payment software you already have can do the job, I’ll tell you. Client documents are confidential, so where the files live and who can see them gets agreed in writing before anything is built. Whether that fits your duties to your clients is your call.

How it starts

Two easy ways in

The free accessibility check

Enter your homepage address and it checks that page against the WCAG 2.0 and 2.1 A and AA rules. Automated tests catch only part of the problems, so treat it as a starting point.

  • Free
  • About 30 seconds
  • No email needed
  • Homepage only

If you want help after that, each stage is a fixed price, agreed up front.

Technical · advancedUnder the hoodHow I test, where the fixes go, and what I will and won’t say about the result.

I’d rather you know exactly what you’re getting. This is how I tested and fixed the site in the case study, and where I’d start on yours.

How I test

  • axe-core, run through Playwright, against the WCAG 2.1 A and AA rules.
  • Every published page, at a desktop width and a phone width.
  • By hand with the keyboard, through the menus, forms and controls.
  • Every page at 320 pixels wide, the width that stands in for 400% zoom, and with enlarged text spacing.

Where the fixes go

  • In the site’s own code, never in an overlay.
  • I save a copy of the theme as I found it before changing anything.
  • New files that load after everything else, plus small edits to the theme, so each fix is easy to find, test and undo.

What I will and won’t say

  • You get what was tested, on what date, and how.
  • I won’t call a site certified or lawsuit-proof.
  • The W3C says no tool alone can determine whether a site is accessible, so a clean scan is a starting point.
  • A theme or plugin update can undo a fix, so I show you where the fixes live.

What you get at the end

  • A written report of what was tested, the date and the results.
  • An accessibility statement, if you want one. Any line that’s a promise only your firm can make gets flagged for you to approve.

Straight answers

Is this legal advice?

No. I build and fix websites, and I’m not a lawyer. Whether the ADA covers your site, and what to do about a demand letter, are questions for your attorney. I do the technical work.

Does my firm’s website have to meet the ADA?

That’s a legal question for your attorney. The ADA lists the office of a lawyer as a public accommodation. The Eleventh Circuit, which covers Florida, vacated its 2021 ruling that a website isn’t one, so the question is open in Florida. The Department of Justice says it has no regulation setting detailed web standards for private businesses, and it calls WCAG helpful guidance.

Are law firms the main target of website lawsuits?

No, and I won’t tell you they are. EcomBack’s 2025 report puts restaurants and food first and fashion and apparel second, and legal services isn’t in its top five. Firms have their own reasons, though. Your intake forms are how many clients first reach you, and the CDC estimates about 28% of Florida adults live with a disability.

Can you promise my site will be compliant?

No. What I can give you is a dated record of what was tested, how, and what changed. The honest claim is that a site conforms to WCAG 2.1 AA as tested on a given date with a given method. A new page or a theme update can change that, so it should be checked again after any big change.

We already have an accessibility widget. Isn’t that enough?

I wouldn’t count on it. The Department of Justice warns that a clean automated report doesn’t necessarily mean everything is accessible. In 2025 the FTC finalized a $1 million order against accessiBe over claims its widget could make any website compliant. Whether to keep yours is up to you, however, the fixes I make go in the site itself.

Do you sell a client portal?

No. There is no product and no feature list. If your firm needs a portal or online intake, I’d build it to fit how your office runs. If the software you already pay for can do the job, I’ll tell you that instead.

What does it cost?

Each stage is a fixed price, agreed up front before any work starts. Every firm’s site is different, so there’s no price list. The check is free, and my guide below lists what other vendors publish for this kind of work.

Who are you?

Justin Zagar, and it’s just me. I build custom software and fix websites for small businesses. From 2012 to 2026 I ran the eBay side of AllOEMRims and built the system behind it.

I’m not a lawyer, and this page isn’t legal advice. Sources: 42 U.S.C. 12181(7), Gil v. Winn-Dixie (11th Cir., vacated December 28, 2021), U.S. Department of Justice web guidance (March 2022), FTC press release (April 22, 2025), W3C WAI, EcomBack 2025 annual report, CDC disability state profile for Florida. The firm numbers are from my own October 2026 audit files.