Analytics

Charts and tables for accessibility trends, recurring issues, and content-level breakdowns from saved Accessibility Tests.

What is Analytics?

The Analytics screen aggregates Accessibility Test data: scores over time, frequent issues, affected URLs, and more.

Why use it

• Trends: See improvement or regression over time
• Prioritization: Focus on frequent or severe issues first
• Content lens: Compare post types or templates
• Progress tracking: Evidence for roadmaps
• Reporting: Export-friendly views for stakeholders
• Planning: Decide where engineering time has the most impact

What you get

Event history:

• The dedicated, immediately visible Event History card directly shows the five latest batch tests, updates, and deletions in chronological order
• Show complete event history expands the same card to all stored events from the last three months; the compact preview can then be restored
• On phones, each compact entry provides a Details action that opens date and time, type, message, user, and URL in a focused bottom sheet
• Close the detail view with its visible actions, Escape, the backdrop, or a downward swipe from the handle; keyboard focus returns to the entry that opened it

Trends:

• Average accessibility score over time
• Issue counts (overall and by severity)
• Test activity by period

Top issues:

• Most frequent issues (by pages affected)
• Most severe issues
• WCAG criteria with the most hits

Content analytics:

• Issues by post type (post, page, …)
• URLs with the most findings
• Issues by taxonomy/category where applicable

Layout and help

• The four Analytics views are available from the upper navigation inside one shared main surface.
• Analytics uses the available content width without a separate right sidebar. The action-oriented cards reflow responsively from three columns to one phone column.
• Identified Issues, Affected Elements, and Affected Pages now share the same decision-oriented card system as the dashboard. Each view starts with a concise next-step card and keeps its filters and primary actions directly in the working context. On phones, the Affected Elements multi-select filter opens as a bottom sheet; Apply commits the draft, while Cancel, Close, Escape, the backdrop, or a downward swipe restores the previous selection.
• Opening an issue can carry that issue as a filter into Affected Elements or Affected Pages. Opening an element can continue into the filtered page list, where the current test result and the WordPress editor are available as visible actions.
• Affected Pages opens as one prioritized All list by default and can alternatively load By Type or By Priority. Scores, dates, and result links come from the latest stored desktop result for each normalized URL; occurrence totals remain separate from affected-page counts.
• Accessibility status shows the average score, movement since the previous measurement, and latest test date. When desktop and mobile data exist, the same viewport switch also updates page status, issue reach, and WCAG coverage.
• Next steps ranks the three issue types with the largest current impact. Test coverage separates current, stale, and untested content; Pages by status groups tested pages into score ranges with no automatically detected issues (score 100), needs improvement (50–99), and critical (0–49).
• WCAG coverage summarizes stored outcomes by the four WCAG principles. Only criteria without automated violations count as an automated pass; open manual reviews are not presented as passed.
• Quick Overview, Live Status, and Sites with Issues add tested and affected pages, issue types, batch progress, the latest aggregation, and issue reach by priority. All found issues restores the complete sortable inventory with a priority filter and desktop/mobile occurrence counts.
• Redirect activity separates current scored results, redirects skipped without a test, redirect destinations tested automatically, and redirect errors for the last 30 days. Skipped and failed redirect checks have no score, findings, or effect on averages. A tested destination contributes exactly once under its destination URL, even when several source URLs redirect there.
• Score trend can be filtered by 7, 30, or 90 days or the complete stored period, by content type or author, and by daily, weekly, or monthly intervals. Successful test runs are stored per content and separately for desktop and mobile, so one viewport cannot replace the other. Current inventory uses the latest known result for every included content item up to the end of each interval; weekly and monthly points show the final state of that interval. The tooltip discloses the number of contents, result freshness (maximum age: 30 days), test activity, and—for all content—the content-type mix. Dotted sections carry the last known state forward because no new test occurred; a diamond marks a changed number of contents in the score. Comparable inventory instead keeps a fixed cohort per viewport: only contents measured before the selected period and retested during it are included. Both compact score summaries follow the same filters, and desktop, mobile, or both lines remain freely selectable.
• Help opens guidance for the current view as a side panel and as a bottom sheet on narrow screens.
• Re-aggregate analytics remains visible in the dashboard header and rebuilds derived data from stored test results when needed.
• Dashboard cards use one calm, consistent card grid; status and priority remain available as text or numbers in addition to color.
• Media purpose resolved combines images with an alt text and images reviewed as decorative. Images with neither remain open; Accessibility Test findings for concrete page uses remain independent.

Configuration

Analytics is generated automatically from stored Accessibility Test runs—no separate Analytics settings screen.

Workflow

1. Open the Analytics tab in the plugin
2. Review current aggregates
3. Inspect historical trends
4. Drill into top issues
5. Use filters for post types or issue categories
6. Export CSV when your plan supports it

Examples

Example 1: Reporting

Snapshot current scores, highlight regressions, and show progress to stakeholders.

Example 2: Triage

Fix the top 10 recurring issues first, then use content analytics to see which templates still fail.

Example 3: Quality targets

Track average score over quarters and tie refactors to measurable movement.

Tips

• Run tests regularly so trends are meaningful
• Use batches to populate coverage quickly
• Pair with AI Insights on Premium/Agency for narrative prioritization
• Aggregates refresh as new tests complete

Available for: Premium and Agency; administrators only from Premium