Skip to main content

See the whole site Free

CSV export of the content report

Download the Content report as a spreadsheet, one row per issue, with your filters applied. Free, and limited to what each person may see.

Updated for Lumtera 1.2.2 and Lumtera Pro 1.1.1.

Overview

The Content report, under Lumtera → Checks → Content, has an Export CSV button above the results. It downloads every issue that matches the report's current filters, one row per issue. Possible issues, the tips the checks are least sure of, are included only when "Show possible issues" is on.

Each row has the post ID, title, URL, content type, post status, severity, the issue's name, its WCAG criterion and level, the message and the markup involved. The file is named after your site and the date, and starts with a marker that lets Excel show accented text correctly.

The export contains only what the person downloading it can see in the report. Someone given permission to see reports, but not to edit other people's work, gets published items and their own, never other people's drafts. Cells that a spreadsheet would run as a formula are neutralized, and the file is built on request on your own site.

Why does it matter?

Accessibility work rarely stays inside WordPress. Issues get shared with developers, pasted into tickets, sorted in spreadsheets and attached to audits. Copying them out of a report screen by hand is slow and easy to get wrong.

What do you get?

  • An Export CSV button on the Content report.
  • Follows the report's filters: search, content type, status, check and severity, and includes possible issues only when "Show possible issues" is on.
  • One row per issue: post ID, title, URL, type, status, severity, issue, WCAG criterion, level, message and markup.
  • Exports only what the person downloading may see in the report.
  • Cells that a spreadsheet would run as a formula are neutralized, and accented text opens correctly in Excel.

How does it work?

  1. Filter the report

    Open Lumtera → Checks → Content and narrow it down, for example to errors in pages.

  2. Choose Export CSV

    The file is built on your site when you ask for it and downloads straight away.

  3. Or use WP-CLI

    On the command line, wp lumtera issues --format=csv streams the same kind of list, which suits large sites.

Who is it for?

  • Handing issues to developers

    Filter to errors in one content type and send the file with the markup for each issue.

  • Importing into a tracker

    Most ticketing tools and spreadsheets import CSV, so issues can be assigned and tracked outside WordPress.

  • Audit records

    Keep a dated snapshot of what the automated checks found at a point in time.

Good to know

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

Free
The export is part of the free plugin.
Who can export
People with the "See reports and check the site" permission, which you set under Lumtera → Settings → Permissions.
Safe to open
A cell starting with =, +, - or @ gets a leading apostrophe, so a spreadsheet shows it as text instead of running it.
Nothing leaves your site
The file is streamed straight to your browser. It is not stored or sent anywhere.
From the command line
wp lumtera issues --format=csv streams issues too, with its own filters such as --rule and --post_type.

Questions

Something else on your mind? Contact support

Do I need Lumtera Pro to export?

No. The CSV export is part of the free plugin.

Does it include whole-page findings?

No. The export lists issues from the content checks, as the Content report does.

Can I export a single check?

Yes. Filter the report by that check, then choose Export CSV.

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.