WordPress accessibility, fixed and logged

Fixes that land in the HTML, not in a promise.

A11yLog scans your WordPress and WooCommerce templates with axe-core, applies fixes in the HTML WordPress serves, and keeps a dated evidence log your team can hand to an auditor.

riverbend.example (sample data)

Last scan Sep 26, 2026
12 templates checked

Sample
23issues found
19fixes applied
4need review
Fixes applied19 / 23

Every fix is applied through WordPress output filters, never by editing your theme, and logged with date, page, and before → after.

Illustration of a web page being scanned, with each fix checked off in a log panel

Where remediation time goes

The five basics eating most remediation budgets.

As one agency put it on r/accessibility: “the actual remediation budget is not eaten by the rare exotic issues, it gets eaten by the same five basic things across almost every site.” In our sample scan of riverbend.example, all 23 findings were these five.

Alt text

Fourteen images shipped with no alt text. A11yLog writes approved text back to the media library.

Labels

Three fields announced as “edit text.” On WooCommerce cart and checkout, labels are added without changing the design; elsewhere the fix assistant proposes one for you to approve.

Contrast

Four text elements failed the 4.5:1 ratio. A color that meets the measured ratio is proposed, and is written to your child theme only when you click Apply.

Landmarks

One theme template had no main region. The fix assistant proposes the markup change with its source; nothing changes until you approve it.

Heading order

One skipped level (h2 → h4) broke the screen reader outline. The fix assistant proposes the corrected level for you to approve or reject.

How it works

Scan, fix, prove.

Built for agencies managing 5–50 client sites and universities preparing for audits. No overlay. No cosmetic layer. Changes happen where your content lives.

axe-core scans on your own site

Scan real rendered pages, including WooCommerce product, cart, and checkout pages. Paid plans add scheduled scans from our server. Results stay tied to the page and the rule that failed.

Real server-side fixes, not overlays

Fixes are applied in WordPress output: post content, blocks, menus, image alt text, and WooCommerce buttons and checkout fields. Visitors and assistive technology get the repaired HTML, and every patch rolls back in one click.

A dated evidence log for auditors

Each fix is recorded with date, page, rule, and before → after. Export a PDF record when procurement or an accessibility office asks what changed.

Sample evidence log

What changed on riverbend.example.

Sample data, not a customer. Nineteen fixes were applied: rule-based fixes run on their own, the rest after a person approved them. The four contrast findings stay in review, because a color change is a design decision A11yLog never makes on its own. Each change keeps its date and page.

riverbend.example (sample) · Sep 26, 2026 scan · 23 issues · 19 fixes applied · 4 in review
Date Fix Page Before → after
Sep 26, 2026 Alt text written for 14 images /library <img src="herbarium-specimen.jpg">→alt="River birch specimen"
Sep 26, 2026 Labels added to 3 form fields /apply <input id="email">→<label for="email">
Sep 26, 2026 Main landmark added (approved) /programs/biology <div class="content">→<main id="content">
Sep 26, 2026 Heading order corrected (approved) /news h2 → h4→h2 → h3
Sep 26, 2026 Contrast flagged for review (4 elements) /programs/biology #9198a2 on #ffffff · 2.9:1→in review · needs 4.5:1

Pricing

Start free. Scale when clients do.

Annual billing through Freemius, with a 14-day trial on every paid plan and no card needed. The free plugin is not on WordPress.org yet: the buttons below open an email to admin@brandon-ta.com, and nothing is collected on this page. Paid tiers add AI alt text on your own AI key, scheduled scans, PDF evidence reports and a multi-site dashboard.

Coming to WordPress.org

Free

$0

per year · 1 site

  • axe-core scan of a page you choose, run inside wp-admin
  • Rule-based fixes for links, buttons, lists and image alt, with one-click rollback
  • Evidence log stored on your own site
  • Contrast report for text and buttons
Ask for the free plugin
Solo site

Starter

$79

per year · 1 site

  • AI alt text on your own AI key, approved before it is saved
  • PDF evidence report
  • Weekly scheduled scans with an email digest
Ask about Starter
Fleet

Agency+

$249

per year · 20 sites

  • Everything in Agency, for up to 20 sites
  • White-label PDF reports with your agency's logo
  • REST API key per site
Ask about Agency+

Questions teams ask

Built for real stacks.

Page builders, cached pages, and audited institutions are the normal case, not the edge case.

Will it work with Elementor, Divi, WPBakery, or block themes?

A11yLog scans the rendered front end, so builder output is checked the way visitors get it. Fixes are applied through WordPress output filters and WooCommerce hooks, not injected by JavaScript in the visitor’s browser. The only file it ever writes is a contrast rule in your child theme, and only when you click Apply.

Is it safe with caching and CDNs?

Fixes are saved in WordPress and applied when the page is built. If A11yLog detects a caching plugin, it names it and reminds you to clear the cache so visitors get the fixed page.

Is A11yLog an overlay?

No. There is no toolbar layered on top of a broken page and no script that claims to make a site accessible on its own. A11yLog changes the HTML WordPress serves where a rule is certain, and leaves judgment calls in a review queue.

How do universities use it during an audit?

Accessibility offices use the dated evidence log to show what was found, what was fixed, when it changed, and what still needs review. It is a record of the work, not legal advice or a certification.

A scan report flipping accessibility issues into fixed checkmarks
The audit-trail log recording every fix with a timestamp