What I don't sell

Here's what's not in my product line. If you're here looking for any of the below, you'll get a better answer from one of the named partners than from me. Email hello@joegullo.com and I'll make the introduction.

Remediation sprints

I don't run engineering teams. When a client's audit reveals fixes I can't deliver as a single auditor, I refer the work out to a partner studio that ships my audit findings as PRs against the client's repo.

What that looks like for the client: my audit + their procurement-grade remediation partner, in two consecutive engagements. No re-explaining the findings; the partner reads the same SC enumeration table I produced on Day 8.

Overlay tools

I don't sell or recommend accessibility-overlay widgets. Overlays mask accessibility problems, increase legal exposure — every major US overlay lawsuit since 2019 has gone against the overlay — and degrade the experience for the users they claim to help. The full reasoning is in §16 of the brand guide.

If a vendor is pitching you an overlay, I'm happy to read the contract on a 15-minute call before you sign.

VPATs for US federal procurement

ADA Title II / Section 508 compliance is a US-specific framework. I don't hold the credentials federal procurement requires (Trusted Tester certification; CPACC for some agencies). For VPAT 2.4 / ACR work I refer to a US-credentialed partner.

I'll write VPAT-format conformance reports for EU-headquartered clients with US-facing properties on request — but only as a deliverable inside an EAA Readiness Audit, not as standalone US federal-acceptance documentation.

Native mobile audits

I audit web platforms — websites, web apps, hybrid PWA shells. Native iOS / Android is a different specialty (WCAG works, but the platform-specific patterns and developer tooling are different enough that someone who lives in that stack gives you better findings).

For native-mobile audits I refer to a mobile-a11y specialist.

AI accessibility audits

I don't audit ML-mediated experiences (conversational interfaces, generative-UX surfaces, model-output rendering). The accessibility questions in that category — prompt readability, screen-reader handling of streamed responses, latency-bound focus management, "regenerate" affordances — are real, but they need a specialist who has shipped against them.

For that work I refer to a partner who specialises in it.

Subscriptions, dashboards, monitoring tools

I am a consultant, not a SaaS. I don't sell monthly monitoring, I don't have an "accessibility platform," and I don't earn a referral fee from any tool I mention.

If you want a tool, the resources page lists the ones I trust. The most boring answer — axe-core running in your existing CI on every push — is correct for most mid-market teams.

Why publish this

Saying what's not in the product line is harder than saying what is. The "what I don't sell" list reads as discipline because every item is adjacent to my category — not unrelated. ("I don't bake bread" would be a joke. "I don't sell remediation sprints" is a position.)

If you came to this page looking for one of the above and I haven't named a partner, that's because the partner agreement isn't yet on paper. Email hello@joegullo.com — I'll either make a fresh introduction or tell you honestly that I don't know the right person in that space.