About this plugin
General accessibility checkers look at your whole site and give you a long list dominated by your blog. This one looks at the five pages that decide whether a disabled customer can actually spend money with you: the shop archive, a product page, the cart, the checkout and the account area.
It fetches each page the way a visitor would, reads the HTML your theme and extensions really produced, and reports what would stop somebody using a screen reader from finishing an order.
What it checks
- Product images with no alt attribute, and alt text that is really a file name
- Star ratings that convey the score visually only
- Add to cart buttons that all announce the same name on an archive
- Quantity fields and variation dropdowns with no label
- Icon-only links and buttons with no accessible name
- Checkout and account fields with no label, or labelled by a placeholder alone
- Required markers with no text equivalent
- Notice containers that are not live regions, so validation errors are never announced
- Checkout fields missing autocomplete attributes
- Skipped heading levels and missing h1
- Missing page language
- Duplicate element ids, a common cause of broken label associations
- Cart and order tables with no header cells
- Link text such as “read more” that says nothing on its own
What you get
- A severity breakdown across your whole buying journey
- Plain-English guidance on every issue, written for a shop owner rather than an auditor
- A dismissal log that records who dismissed what, when, and why
- CSV export of every open and dismissed issue, with WCAG references – useful evidence for an agency handover or an internal review
Honest limits
Automated testing catches roughly a third of WCAG problems. This plugin reads server-rendered HTML, so it cannot judge colour contrast after CSS is applied, keyboard focus order, focus traps in modals, or whether your alt text is accurate. A clean scan is a floor, not a certificate.
Test with a keyboard and a screen reader before claiming conformance, and do not treat any tool – this one included – as proof of legal compliance.
Because no stylesheet is applied and no JavaScript is run, the scan treats an element as hidden only when the markup itself says so – aria-hidden, the hidden or inert attribute, an inline display:none, or a template or noscript wrapper. Something hidden purely by a class in your stylesheet still gets checked, so a small number of findings may point at markup a sighted visitor never sees. Dismiss those with a note; the dismissal is remembered across rescans.
This plugin does not add an accessibility overlay or a toolbar widget. Overlays have a poor record: they are opposed by major disability organisations, and sites using them have still been sued. This plugin only tells you what to fix in your own markup.
External Services
Scanning, the issue list, the dismissal log and the CSV export all run entirely on your own server and require no account.
com/a11y/), to produce an AI-written explanation of how to fix one specific issue.
Data sent when you press that button, and only then:
- The rule that fired and its WCAG reference
- The description of the issue
- The HTML snippet already shown to you on screen
- The page type (shop, product, cart, checkout or account)
- Your site locale
- Your site address, so the service can apply the site limit on your plan
- Your API key, for authentication
When you request a free key, your email address and your site URL are sent.
Separately, once an API key is saved, the settings screen asks the service how many suggestions remain on your plan. Only your API key is sent, and the answer is cached for one hour. Remove the key to stop this.
No customer data, order data, post content or user information is ever sent. No issue data or page content leaves your server unless you press “Suggest a fix”.
- Terms of service: https://tetphilosopher.com/a11y/terms.html
- Privacy policy: https://tetphilosopher.com/a11y/privacy.html