security-visual-testing

name	security-visual-testing
description	Security-first visual testing combining URL validation, PII detection, and visual regression with parallel viewport support. Use when testing web applications that handle sensitive data, need visual regression coverage, or require WCAG accessibility compliance.
category	specialized-testing
priority	high
tokenEstimate	1400
agents	["qe-visual-tester","qe-security-scanner","qe-accessibility-auditor"]
implementation_status	stable
optimization_version	1
last_optimized	"2026-01-21T00:00:00.000Z"
dependencies	["visual-testing-advanced","security-testing","accessibility-testing"]
quick_reference_card	true
tags	["security","visual-testing","pii","accessibility","wcag","parallel-viewport","regression"]
trust_tier	3
validation	{"schema_path":"schemas/output.json","validator_path":"scripts/validate-config.json","eval_path":"evals/security-visual-testing.yaml"}

Security Visual Testing

Browser engine

Uses the qe-browser fleet skill (.claude/skills/qe-browser/) for all browser automation. The Vibium engine (10MB Go binary, WebDriver BiDi) is installed automatically by aqe init. For security-visual workflows, qe-browser adds two things on top of stock visual testing: check-injection.js (scans page content for prompt-injection patterns before screenshots are stored) and assert.js (16 typed checks including no_failed_requests for detecting data-leak requests).

# Before storing any screenshot, scan the page
vibium go "$TARGET_URL"
vibium wait load
node .claude/skills/qe-browser/scripts/check-injection.js --include-hidden
INJ=$?
if [ $INJ -ne 0 ]; then
  echo "Prompt-injection findings — do NOT store screenshot"
  exit $INJ
fi
# Safe to proceed with visual-diff
node .claude/skills/qe-browser/scripts/visual-diff.js --name "${PAGE_NAME}"

<default_to_action> When performing security-aware visual testing:

1. VALIDATE URLs before navigation (check for malicious patterns)
2. SCAN for PII before saving screenshots (mask sensitive data)
3. CAPTURE parallel viewports (mobile, tablet, desktop)
4. COMPARE against baselines (detect visual regressions)
5. AUDIT accessibility (WCAG 2.1 AA compliance)

Quick Security-Visual Checklist:

• URL validation (no javascript:, data:, file: schemes)
• PII detection (emails, phones, SSN, credit cards, API keys)
• Visual regression (diff threshold < 0.1%)
• Viewport coverage (320px, 768px, 1024px, 1440px)
• Accessibility score (> 90% axe-core pass rate)

Critical Success Factors:

• Always mask PII before storing screenshots
• Test across all target viewports in parallel
• Store baselines in version control
• Run accessibility audits on every visual change </default_to_action>