Grounded
We make WordPress plugins for the parts of a site nobody enjoys checking: accessibility, European compliance, and what your chatbot actually tells your visitors. The reports say what they can prove and stop where the evidence stops.
What we make
Accessibility Audit — WCAG & EAA Compliance Checker
Scan your WordPress site against WCAG 2.2 and build the accessibility information the European Accessibility Act requires.
AI Customer Support Chatbot & Lead Automator
A chatbot that answers from your own pages, posts and WooCommerce products — and tells visitors it is an AI, because the law now requires it.
Latest writing
WordPress AI Customer Support: How to Build a Chatbot Without Per-Message Fees
Discover how to build a WordPress AI customer support chatbot that actually knows your WooCommerce products, captures leads, and avoids expensive per-message fees.
WordPress Accessibility Checker: Why You Need Rendered Page Scans
Discover why traditional API-based WordPress accessibility checkers fail on modern sites and why you must test the rendered page your visitors actually see.
WooCommerce AI Chatbot: How to Automate Pre-Sales and Capture Leads
Learn how to use an AI chatbot on WooCommerce to automatically answer pre-sales questions about your products and capture leads when a human is needed.
Public Sector WordPress Accessibility: Building the EU 2018/1523 Document
Ensure your public sector WordPress site is compliant. Learn how to audit for WCAG 2.2 and generate the mandatory Implementing Decision (EU) 2018/1523 accessibility statement.
Article 50 in Practice: Five Things to Get Right in a WordPress Chatbot
Where the AI disclosure goes, how it should be worded, why it has to be accessible, and why it belongs outside the message log. Five concrete checks against Article 50 of the EU AI Act.
What Article 50 of the EU AI Act Asks of a WordPress Chatbot
The transparency article has applied since 2 August 2026. Who it binds, what it actually requires of a chat widget, and what our plugin does and does not settle for you.
European Accessibility Act (EAA) for WooCommerce: How to Audit Your Store
Prepare your WooCommerce store for the European Accessibility Act (EAA). Learn why rendered page scans are essential and how to build your Annex V accessibility document.
How to Generate an EAA Annex V Accessibility Statement in WooCommerce
The European Accessibility Act requires an Annex V accessibility statement for e-commerce sites. Learn how to generate an honest, compliant statement for your WooCommerce store.
WCAG 2.1 or 2.2 for the European Accessibility Act? The directive names neither.
The EAA does not mention WCAG anywhere. It requires Annex I, and a WCAG version only enters the picture through a harmonised standard whose reference is published in the Official Journal. Which one that is, and why claiming the higher number is not automatically the safer choice.
Does the European Accessibility Act apply to you? If you employ fewer than 10 people, probably not.
Article 4(5) of Directive (EU) 2019/882 exempts microenterprises providing services from the accessibility requirements and from every obligation attached to them. Almost nobody selling EAA compliance tools mentions this, including, for a while, me.
Your audit report says 2.1.1 fails on every element. Here is how to tell whether that is real.
A vendor's keyboard test marks every control on the page as a Keyboard (2.1.1) failure. You unplug the mouse and everything works. Both of you can be honestly reporting what you saw — and the criterion does not mean what most reports assume it means.
An Author on your WordPress site can rewrite what your AI chatbot tells every visitor
My chatbot plugin fed indexed site content straight into the model's system prompt with nothing marking it as data. Anyone who could publish — not just an administrator — could change what the bot said. Here is the exploit, the fix, and the counterfactual that proves the fix is the reason it stopped.
A reviewer found three wrong WCAG criteria in my accessibility plugin. I went looking, and found eight.
A marketplace review rejected my WordPress accessibility scanner for citing WCAG criteria that were wrong, obsolete, or unrelated to what the check tested. Auditing all 25 rules found more than the reviewer did — and the wrong numbers were ending up in a legal document.
Most "EAA accessibility statement" tools build the wrong document
Implementing Decision (EU) 2018/1523 is the model statement for public sector bodies under Directive 2016/2102. The European Accessibility Act asks a business for something else entirely — Annex V. Mine got this wrong until a reviewer caught it.
The EU AI Act's chatbot rule started five days ago. My own plugin was breaking it.
Article 50 of the EU AI Act has applied since 2 August 2026: a person must be told they are talking to an AI, before or at the very beginning. My WordPress chatbot's default greeting told them nothing. What the rule actually says, and the four decisions it took to ship the fix.
Accessibility Audit: A Practical WordPress Plugin for Finding WCAG Issues Before Your Visitors Do
A WordPress plugin that finds WCAG issues before your visitors do, separates success criteria from recommended practice, and builds the Annex V information the European Accessibility Act requires.