Skip to main content
Back to Blog

A Good Gate Earns Its Keep: A11y Gate, the Accessibility Gate for Statamic

By Brent Passmore 3 min read

The problem with reports

Every accessibility tool we tried had the same shape: scan the site, produce a list, hope somebody reads it. The list gets long, the list gets ignored, and the broken pages are already live while it sits there. A report arrives after the harm is published.

So we built the other thing. Accessibility Gate is a free Statamic addon that refuses the publish itself. Press Save & Publish on an entry with a detectable accessibility error and the save stops, right there in the control panel, with plain words about what is wrong and how to fix it. An image with no description. A link that says "click here." A page with no main heading. The entry does not go live until the problem does not exist.

What a gate is for

A gate on a farm is not decoration. It earns its keep by staying shut at the right moments, and a gate that swings open for whatever pushes on it is just a gap in the fence. That is the whole design here. The addon does not score your site out of a hundred, does not issue a compliance badge, and does not add an overlay widget for your visitors. It stands at one spot, the moment of publishing, and it holds.

It checks the page the way a visitor would receive it: rendered through your own templates, with your unsaved changes applied, before anything is written to disk. Authors get a panel in the entry sidebar to check a page before pressing publish, including a page that has never been saved. Developers get a command, php please a11y:check, that scans every published page and exits non-zero, so a release can be stopped by it too.

What it will not tell you

The part we care most about is what it refuses to say. A page that passes has not been proven accessible, and the addon says so in its own interface, its documentation, and its license. Automated checking reads markup. It cannot see color contrast or anything else a stylesheet decides, it cannot tell a good image description from a lazy one, and a great deal of WCAG is not mechanically detectable at all. When a check cannot run, it tells you that too, because a check that silently finds nothing looks exactly like a check that passed.

An accessibility tool that overstates what it knows is worse than none. People trust it, stop looking, and ship the problems it never saw.

It runs here

This site publishes through the gate. Every post, including this one, rendered and passed before it went live, and more than one draft has been sent back to fix a heading or a link on the way out. That is the arrangement we wanted: not a report to read later, but a gate that was already closed.

Accessibility Gate is free on the Statamic Marketplace, and the source is on GitHub for anyone who wants to read exactly what it checks. Install it with composer require bpmore/statamic-a11y-gate and try to publish something broken.

About the gate.

What does Accessibility Gate check?

It renders the entry through your site's own templates and checks the resulting HTML: heading structure, link and button text, image descriptions, embed titles, and touch target sizes written into the markup. Errors block the publish; warnings do not. Two further checks, links to unpublished pages and plain-language reading level, are available when your templates mark them up.

Does a clean result mean my site is accessible?

No. Automated checking finds a subset of accessibility problems. The addon cannot see anything a stylesheet decides, including color contrast, and it cannot judge whether an image description is accurate. A page it allows has not been proven accessible, and the addon never claims conformance with any standard. A browser-based tool like axe catches more.

How much does it cost?

Nothing. There is no price, no license key, and no site limit. Install it with composer require bpmore/statamic-a11y-gate, or find it on the Statamic Marketplace under Accessibility Gate.

More from the field

Why Accessibility Is the Soil Your Website Grows In

A healthy harvest starts underground. Accessibility isn't a feature bolted onto a finished product. It's the soil everything else depends on. Here's why WCAG compliance should be the first seed you plant.

3 min read

Five Accessibility Weeds Hiding in Every Website

Even well-tended gardens get weeds. These five common WCAG violations show up on nearly every site we scan, and most teams don't know they're there until someone can't get through.

3 min read