The tool I needed and couldn't find.
eiSEO was built by Brent Passmore, the digital accessibility practitioner managing large-scale WCAG audits and PDF remediation programs at a large academic medical center. It's the tool he needed and couldn't find.
Green is not the same as done.
I run large-scale WCAG audits for a living, not as a consultant who files reports and moves on, but as the practitioner at a public university where the compliance obligation is real, the deadlines are fixed, and "we ran Lighthouse and it came back green" is not an acceptable answer when an auditor arrives with findings.
I used every tool available. Lighthouse. WAVE. axe DevTools. Third-party audit platforms. Each told part of the story. None told the whole story. And none were built for the workflow that compliance work actually requires.
The core problem: they don't render pages the way browsers do. Modern websites are JavaScript-rendered, dynamically mounted, framework-dependent. The DOM a screen reader encounters is not the DOM that axe sees when run against a static HTML parse. It's the DOM that exists after JavaScript finishes executing.
If your scanner doesn't run in a real browser after JavaScript executes, it's not scanning your site. It's scanning a snapshot of part of your site.
That's what I built eiSEO to fix.
A real browser, then the real rule set.
eiSEO uses Playwright (the browser automation library maintained by Microsoft) to launch a real Chromium instance and render every page in your sitemap the way a user actually experiences it. After JavaScript executes and the DOM settles, eiSEO runs the full axe-core 4.x rule set against the rendered page.
axe-core is the open-source accessibility testing engine used by Google, Microsoft, and Deque. It is not a proprietary algorithm. It is the industry-standard engine: open-sourced, peer-reviewed, and maintained by the organization that wrote the original specification.
Three additional engines run in the same scan: technical SEO analysis, custom HTML policy enforcement, and AI search visibility scoring. These problems share the same structural foundation and are best addressed together.
One rendered page, four harvests.
Accessibility
Playwright + axe-core against WCAG 2.2 AA. Catches color contrast failures, missing alt text, broken ARIA, and keyboard navigation issues in the rendered DOM.
SEO
Title tags, meta descriptions, canonicals, heading structure, image optimization, broken link detection. Every check maps to a specific ranking factor.
AI SEO
Twelve checks for Answer Engine Optimization. Structured data, FAQ blocks, author attribution, freshness signals, and content extractability.
Policy
Custom rules for your organization's standards. Content length minimums, required meta fields, and naming conventions, all enforced across every page.
Precise about the boundary.
eiSEO is not a compliance program management platform. It finds the problems. How you assign remediation, store evidence, and report progress is a separate workflow, and that's what ComplyField handles. The two tools work together but neither requires the other.
eiSEO is also not a substitute for manual accessibility testing. Automated tools catch approximately 30–40% of WCAG violations, specifically the ones that are structurally detectable without human judgment. eiSEO gives you the automatable findings and tells you where manual review is warranted.
We believe in being precise about what the tool does. Overclaiming is more dangerous than underclaiming when the stakes are compliance documentation.
Rooted in Arkansas. Grown for institutions.
eiSEO is built and maintained by Had A Farm LLC, a portfolio of purpose-built software tools founded by Brent Passmore in Arkansas. Built on production infrastructure and maintained to the quality standards required by institutional compliance work.
50 pages free · No credit card · Results in under 2 minutes