Category
Plugin version
1.1.0-beta.29

Data & storage

Custom tables

The plugin may create tables such as:

  • wp_wcag_lighthouse_results — latest Accessibility Test rows
  • wp_wcag_lighthouse_results_history — historical runs
  • wp_wcag_lighthouse_analytics_daily — daily rollups
  • wp_wcag_lighthouse_analytics_issues — issue tracking
  • wp_wcag_lighthouse_analytics_content — content analytics
  • wp_wcag_lighthouse_ai_explanations — AI Explanation & Fix payloads

WordPress options

  • wcag_*_settings — one blob per settings module
  • wcag_batch_cancel_flag — cooperative cancel signal
  • wcag_scheduled_batch_* — planned batch tests configuration
  • wcag_batch_tested_destination_urls — temporary URL deduplication map for the active batch; removed when the run ends or is reset
  • wcag_lighthouse_redirect_events — capped log of the 500 most recent redirect decisions for the 30-day Analytics counters; it stores status, context, timestamp, an error key where applicable, and hashes instead of source or destination URLs

Accessibility Toolbar browser storage

Visitors choose how Toolbar preferences are stored:

  • This session: active state in sessionStorage
  • Remember on this device: active state in localStorage
  • Named profiles: up to ten profiles with 1–40-character names in localStorage

Changing storage scope moves the active state and removes the obsolete active record from the other store. Named profiles remain device-local independently of that scope. The former wcagToolbarState preference object is migrated to the new schema where possible. The selected duration for a hidden Toolbar button is also stored locally in the browser. These visitor preferences are neither written to the WordPress database nor sent to an EZZE endpoint.

Cloud usage data

Before Cloud Features are activated, the plugin does not request quotas or usage history from the EZZE proxy. Account & License shows only the local activation state until opt-in is complete. The plugin loads the limits and usage data associated with the connected account only after that point.

The proxy stores this quota data atomically in a private SQLite database. Monthly-history details and tested URLs are retained for four months; durable aggregate counters preserve one-time Free allowances beyond that period. New SQLite usage events contain no IP address. The database is protected by consistent, encrypted off-site snapshots. A parallel JSON rollback copy is used only during the controlled migration and for no more than 14 days. This infrastructure is entirely on the EZZE proxy; the WordPress installation requires no server configuration.

Post meta

  • _wcag_enable_lighthouse_test — per post/page auto-test flag
Focused reading view

Reading mode