EVIDENCE · TIMELINES · CLEARER DECISIONS

Browser Compatibility Evidence Matrix

Track tested features, devices and known fallbacks; export a support statement.

Original sources preservedReview before exportSave & reopen projects

Original sources stay unchanged · save your review to keep decisions

Maintain feature/browser/version evidence and export a qualified support statement with untested outcomes visible.

Using Browser Compatibility Evidence Matrix

Track tested features, devices and known fallbacks; export a support statement.

  1. Start with Try worked example. Or open supported local evidence. feature,browser,version,device,outcome,fallback,evidence. Outcomes: Pass/Fail/Partial/Not tested.
  2. Use Details & settings to adjust the declared inputs, thresholds or component content. Review cards retain source evidence and any supported manual decisions.
  3. Open Preview for the actual analysis or interactive component. Test keyboard behavior and narrow layouts before relying on generated UI.
  4. Use Export for task artifacts and the complete workflow ZIP. Save review retains settings/decisions and source fingerprints; file-based projects need the original sources to reopen.

Example

The tailored example for Browser Compatibility Evidence Matrix demonstrates Maintain feature/browser/version evidence and export a qualified support statement with untested outcomes visible.

Questions & answers

What does Browser Compatibility Evidence Matrix support?

Maintain feature/browser/version evidence and export a qualified support statement with untested outcomes visible.

What input should I use?

feature,browser,version,device,outcome,fallback,evidence. Outcomes: Pass/Fail/Partial/Not tested.

What can I download?

Use the Export tab for task-specific artifacts, typed JSON, CSV and a workflow ZIP. Supported artifacts can include compressed files, reviewed CSS, source-position evidence, screenshot PNGs or qualified review reports.

Does this run a live website audit or deploy changes?

No. Performance diagnostics use imported evidence, explicit simulations or selected local bytes. Builders export code for you to review and integrate. No URLs are crawled, no service worker is installed and nothing is deployed. Public pages retain approved ads and optional consent-based analytics.

Help improve this tool

Report a problem or suggest an improvement

Describe the issue without pasting private tool input. Feedback goes to our admin inbox.

Find another tool · Read practical guides