Accessibility audit
axe-core on each monitored page, once a day and after each deployment — a score, the defects with the offending element, the trend.
Pro plan and aboveUpdated on 17 September 2026
On this page
The accessibility check reads eight things on the home page, on deployment. The Accessibility page (Project → Quality → Accessibility) goes further: axe-core, the reference engine for accessibility audits, on each monitored page, with a score per page, each defect with the HTML excerpt of the offending element and the link to the rule, and the score over time.
What PostShip does
The audit
Once a day — and right after a deployment — PostShip reads the served HTML of each page and hands it to axe-core in a DOM without rendering. The pages: the project's home, then the monitored HTTP URLs by age, up to 5 with the Pro plan, 15 with Team, 30 with Agency.
What the audit sees: images without alternative text, fields without a label, mute buttons and links, missing language, misassembled ARIA roles, heading order, iframes without a title, malformed lists, blocked zoom, forced tabindex… about sixty rules.
What it does not see, for lack of rendering: colour contrast and what depends on layout (target size, scrollable regions). These rules are set aside or counted as “inconclusive”, never as violations. An audit in a real browser would see them; that is the price of an audit that runs every day on all your pages without installing anything.
The score
Per page: 100, minus 15 points per violated critical rule, 10 per serious rule, 5 per moderate rule, 2 per minor rule — per rule, not per element: ten images without alt are one template defect, not ten defects. Floor zero. The project's score is the average of the pages.
The detail
Each violation unfolds: the rule's description, up to five offending elements with their HTML as served, the total count, and the link to the rule at Deque. The most common rules have their sentence in your language; the others keep axe-core's help text.
Settings
Nothing to set. “Audit now”, at the top of the page, runs the audit right away (at most once every ten minutes). The audited pages are those of the URLs page: add a page there to audit it.
What triggers an alert
No new alert: the accessibility check already alerts on deployment when the home page loses a label or an alternative text. The audit is there to read, page by page, and to fix.
Limits and plans
| Free | Pro | Team | Agency | |
|---|---|---|---|---|
| The audit | — | Yes | Yes | Yes |
| Audited pages per project | — | 5 | 15 | 30 |
The home page accessibility check stays open to everyone. See plans.
Troubleshooting
“Not audited: this is not an HTML page”
The URL returns something other than HTML (a JSON, an image, a PDF): there is nothing to audit.
“Not audited: the audit exceeded twenty seconds”
A very heavy page (several megabytes of HTML) exceeds the allotted time. The HTML read is capped at 512 KB; beyond that, the audit covers the beginning of the page.
Why is the score good while my site has contrast problems?
Because contrast is not measured here — see above. A tool in the browser (Lighthouse, the axe extension) complements this audit on that point.