Skip to main content

🎉 Lumtera Pro Introductory Offer — 50% OFF! ✨ Go Pro for half the price. Limited time! 🚀

Offer ends in 0d 00h 00m

Get Lumtera Pro

See the whole site Free

Works with AI assistants

Lumtera registers 13 abilities with the WordPress Abilities API, so AI assistants can check content, read issues and coverage, and propose fixes a person approves.

Updated for Lumtera 1.2.2 and Lumtera Pro 1.1.1.

Overview

On WordPress 6.9 and later, Lumtera registers 13 abilities with the WordPress Abilities API. Abilities are WordPress's standard way for a plugin to describe what it can do, with a schema for the input and output, so an AI assistant or automation tool can find and call them without custom code. They are published to the Abilities REST endpoints and marked for MCP, so an assistant connected through the WordPress MCP Adapter can use them.

To check: check-content checks HTML or block markup and saves nothing, and check-post checks a saved post and updates its stored results. To read: site-summary, list-issues, list-issue-groups (the same problem in the same markup, most widespread first), list-site-parts, list-page-results (saved whole-page results), get-coverage, get-manual-review-status, get-statement-status, list-rules and explain-rule. To act: propose-fix drafts a fix for one stored finding and saves it as a proposal. It never changes the post; a person reviews the before and after and applies it.

A typical use: the assistant drafts a post, runs check-content, fixes what it can and leaves the judgment calls to a person. Or it lists the issues on a page and proposes alt text or link text, which an editor reviews and applies. Every call runs as the WordPress user the assistant is connected as, and site content in the answers is marked as untrusted, to be treated as data, never as instructions.

Why does it matter?

More and more site work happens through AI assistants. If they cannot see accessibility results, they will happily write content with the same problems a person would.

What do you get?

  • Check content or a saved post, and read the site summary, stored issues, repeated issues, site parts and saved whole-page results.
  • Read coverage, the status of manual checks and of the accessibility statement, and what any check means.
  • Propose a fix: the assistant drafts it, and it waits for a person to review and apply it. The free abilities never change post content.
  • Each ability checks the same WordPress permissions as the Lumtera screens. Lumtera Pro adds six more.
  • Also available as a REST API (lumtera/v1) for your own tools.

How does it work?

  1. Install Lumtera

    On WordPress versions with the Abilities API, the abilities register automatically.

  2. Connect your assistant

    Any client that discovers WordPress abilities can call them.

  3. Review what it proposes

    Fixes an assistant proposes are saved as proposals. A person reviews the before and after and applies them in wp-admin.

Who is it for?

  • Teams drafting with AI

    An assistant can check its own output before handing it over, so drafts arrive with fewer automated issues for an editor to find.

  • Site managers asking questions in plain language

    Ask an assistant how the site is doing and it can call site-summary or get-coverage for real numbers instead of guessing, if your account can see the reports.

  • Developers building automation

    Scripts and workflow tools can call the same abilities through the Abilities REST endpoints, with schemas that describe every field.

Good to know

How it behaves, what it needs, and where its limits are.

Permissions
check-content, list-rules and explain-rule need the edit_posts capability. check-post and propose-fix need permission to edit that post. site-summary, the issue, site part and page result lists, coverage and manual review status need the permission to see reports, which editors and administrators have by default. get-statement-status needs that or the publish_pages capability.
What can change
Eleven abilities only read. check-post updates the stored results for one post, like Check again in the Content report. propose-fix saves a proposal. No free ability changes post content.
No AI inside
The abilities are ordinary server-side functions. Lumtera does not call an AI service to run them, and the results match what a person sees in the sidebar.
Lumtera Pro adds six
With an active license, Pro adds list-proposals, apply-approved-changes, revert-change, create-task, compare-scans and evidence-summary, each with its own permission check.
Older WordPress versions
Before WordPress 6.9 the Abilities API is not available, so the abilities are not registered. Everything else in Lumtera works as usual.

Questions

Something else on your mind? Contact support

Does this send my content to an AI service?

No. Abilities are just a documented way to call Lumtera. What an assistant does with the results is up to the assistant you choose.

Which assistants can use this?

Any client that can call WordPress abilities, for example through the WordPress MCP Adapter. Lumtera does not include its own connector.

Can an assistant dismiss issues or apply fixes?

There is no dismiss ability, and in the free plugin an assistant can only propose a fix. Dismissals and applying fixes are done by a person.

What is the lumtera/v1 REST API for?

It powers Lumtera's own screens: live checks, stored issues, re-checks, dismissals, bulk checks, fixes, manual results and a site summary. It uses normal WordPress authentication and permission checks. For automation, the abilities are simpler because they describe their own inputs and outputs.

More in “See the whole site”

Start with the free plugin today

All 69 content checks and 33 whole-page checks, fixes you approve with undo, and the site report — free, with no account and no page limits.