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
What you get
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.
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.
Scanning, the issue list, the dismissal log and the CSV export all run entirely on your own server and require no account.
The optional “Suggest a fix” button connects to the TET Accessibility API, operated by TET (https://tetphilosopher.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:
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”.