Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
borghei avatar

Qa Browser Automation

  • 75 installs
  • 451 repo stars
  • Updated July 21, 2026
  • borghei/claude-skills

QA Browser Automation is a Claude skill that combines Chrome MCP browser control with Python tools for health scoring, WCAG accessibility auditing, visual regression tracking and QA reporting.

About

QA Browser Automation drives Chrome MCP for live browser testing and adds four Python tools for health scoring, accessibility auditing, visual regression tracking and report generation. A developer uses it for systematic, repeatable QA sweeps of web apps covering functional, accessibility, performance and security-header checks. It defines four testing tiers and gates on a health score of at least 85, zero P0 findings and WCAG AA at 95%.

  • 11-phase full-app QA sweep with 0-100 health scoring across 10 categories
  • WCAG 2.1 A/AA/AAA accessibility auditing with remediation guidance
  • Visual regression tracking via baseline vs current screenshot comparison

Qa Browser Automation by the numbers

  • 75 all-time installs (skills.sh)
  • Ranked #1,076 of 2,153 Testing & QA skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
At a glance

qa-browser-automation capabilities & compatibility

Capabilities
accessibility audit · visual regression · pr review expert
Works with
chrome · playwright
Use cases
testing · code review · web design
Pricing
Free
From the docs

What qa-browser-automation says it does

Use when performing browser-based QA testing, visual regression tracking, WCAG accessibility auditing, performance profiling, or health scoring web applications.
SKILL.md
**Validation checkpoint:** Health score >= 85. Zero P0 findings. WCAG AA >= 95%.
SKILL.md
The agent drives Chrome MCP for live browser testing and uses four Python tools for deterministic health scoring, accessibility auditing, visual regression tracking, and report generation.
SKILL.md
npx skills add https://github.com/borghei/claude-skills --skill qa-browser-automation

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs75
repo stars451
Last updatedJuly 21, 2026
Repositoryborghei/claude-skills

What it does

Run repeatable browser QA sweeps with health scoring, WCAG accessibility audits, visual regression tracking and performance checks.

Who is it for?

Repeatable browser QA sweeps with accessibility, visual-regression and performance checks.

Skip if: Static code review of a PR diff (use pr-review-expert).

When should I use this skill?

Performing browser QA, visual regression tracking, WCAG auditing, or performance/health scoring a web app.

What you get

A scored, evidence-backed QA report with WCAG findings and flagged visual regressions.

  • 0-100 health score
  • WCAG violation report
  • visual regression results

By the numbers

  • 11-phase QA sweep
  • 4 Python tools
  • 10 weighted health-score categories

Files

SKILL.mdMarkdownGitHub ↗

QA Browser Automation

The agent drives Chrome MCP for live browser testing and uses four Python tools for deterministic health scoring, accessibility auditing, visual regression tracking, and report generation.

---

Quick Start

# Score QA findings (0-100 weighted across 10 categories)
python scripts/qa_health_scorer.py findings.json --threshold 85 --baseline .qa-baselines/latest.json --save-baseline --json

# Audit HTML for WCAG 2.1 violations
python scripts/accessibility_auditor.py page.html --level AA --json

# Track visual regressions
python scripts/visual_regression_tracker.py --init --baseline-dir ./baselines
python scripts/visual_regression_tracker.py --register ./baselines
python scripts/visual_regression_tracker.py --baseline ./baselines --current ./screenshots --threshold 5

# Generate full QA report
python scripts/test_report_generator.py session_data.json --format markdown -o report.md

Tools Overview

ToolInputOutput
qa_health_scorer.pyFindings JSONScore 0-100, grade A-F, category breakdown, trend data
accessibility_auditor.pyHTML file (or stdin)WCAG violations by level with remediation guidance
visual_regression_tracker.pyBaseline + current screenshot dirsPass/fail per page, change percentages
test_report_generator.pySession data JSONMarkdown or JSON report with recommendations

All tools support --json for machine output. Health scorer and regression tracker return exit code 1 on failure (CI-friendly).

---

Workflow 1: Full Application QA Sweep (11 Phases)

Phase 1-2: Pre-flight and authentication.

  • Verify git status is clean. Abort if dirty.
  • Create session directory: .qa-sessions/{timestamp}/
  • Authenticate via Chrome MCP if needed.

Phase 3-4: Orient and explore.

  • Use mcp__claude-in-chrome__read_page to build sitemap/page map.
  • Navigate each route. Check read_console_messages for errors, read_network_requests for 4xx/5xx.
  • Test all forms with valid data, empty submissions, and boundary values.

Phase 5: State testing.

  • Verify loading states (skeleton screens, not blank), empty states (guides to first action), error states, success states, partial states.
  • Four shadow paths per interaction: happy path, nil input, empty input, error upstream.

Phase 6: Cross-device and security.

  • Resize to 320px, 768px, 1024px, 1440px, 1920px.
  • Check touch targets (44x44px min), layout shifts.
  • Verify security headers (CSP, HSTS, X-Frame-Options), cookie flags.

Phase 7-8: Document and score.

  • Record every finding with screenshot evidence. No finding without evidence.
  • Classify by severity (P0-P4) and category (10 categories).
  • Run: python scripts/qa_health_scorer.py findings.json --baseline .qa-baselines/latest.json

Phase 9: Triage and fix loop.

  • P3/P4: AUTO-FIX, commit atomically, verify.
  • P0/P1/P2: ASK, present evidence, propose fix, wait for approval.
  • After each fix: re-run check. If fail: git revert.
  • Hard stop at 50 fixes.

Phase 10-11: Regression check and report.

  • Re-visit fixed pages. Verify no new errors.
  • Generate report: python scripts/test_report_generator.py session.json --save-baseline

Validation checkpoint: Health score >= 85. Zero P0 findings. WCAG AA >= 95%.

---

Workflow 2: Visual Regression Testing

# Set up baseline
python scripts/visual_regression_tracker.py --init --baseline-dir ./baselines
# Capture and register screenshots
python scripts/visual_regression_tracker.py --register ./baselines
# After changes, compare
python scripts/visual_regression_tracker.py --baseline ./baselines --current ./screenshots --threshold 5 --json
# Accept intentional changes
python scripts/visual_regression_tracker.py --update-baseline --baseline ./baselines --current ./screenshots

Pages exceeding the threshold (default 5%) are flagged as regressions. Uses SHA-256 hashing and byte-level comparison.

---

Workflow 3: Accessibility Audit

python scripts/accessibility_auditor.py page.html --level AA --json
curl -s https://example.com | python scripts/accessibility_auditor.py - --level AAA

What gets checked by level:

  • A (Must Fix): Alt text, page language, form labels, headings, duplicate IDs, autoplay media
  • AA (Should Fix): Color contrast (4.5:1 text, 3:1 large), heading hierarchy, focus visible, error identification
  • AAA (Nice to Have): Enhanced contrast (7:1), extended audio, reading level

Each violation includes: WCAG criterion, severity, element selector, and remediation guidance.

---

Testing Tiers

TierDurationScope
Quick30sConsole errors, broken links, basic a11y, mobile resize
Standard2-5 min+ Top 10 routes, forms, contrast, Core Web Vitals
Deep10-20 min+ Full sitemap, state testing, WCAG AA, performance, visual regression, security headers
Exhaustive30+ min+ Every element, WCAG AAA, all pages performance, 5 breakpoints, auth edge cases, memory leaks

---

Health Scoring System

10 weighted categories, score 0-100:

CategoryWeightMeasures
Functional18%Forms, CRUD, navigation flows
Accessibility13%WCAG compliance, keyboard nav
Console Errors12%JS errors, unhandled rejections
UX Flow12%Logical navigation, clear feedback
Performance12%Core Web Vitals within thresholds
Visual Consistency10%Layout shifts, alignment, z-index
Broken Links8%HTTP 4xx/5xx, dead anchors
Content Quality5%Spelling, placeholder text, truncation
Security Headers5%CSP, HSTS, cookie flags
Mobile Responsive5%Breakpoints, touch targets, no h-scroll

Severity deductions: P0: -30, P1: -18, P2: -10, P3: -4, P4: -1.

Grades: A (90-100), B (80-89), C (70-79), D (60-69), F (0-59).

---

Safety Controls

  • Clean working tree required -- abort if git status dirty.
  • Max 50 fixes per session -- hard stop.
  • Risk accumulator -- component (+5), style (+2), config (+8), revert (+15). Stop at 25% of budget.
  • WTF heuristic -- 3 consecutive fix verification failures = stop entirely.
  • Atomic commits -- one fix = one commit: fix(qa): [P{severity}] {description}

---

Troubleshooting

ProblemCauseSolution
Scorer exits code 1 with no errorsScore below --threshold (default 70)Check score in output; raise threshold or fix findings
Auditor reports parse-errorMalformed HTMLVerify file is complete; check curl is not returning redirect
Regression tracker 100% change on all pagesBaseline manifest emptyRun --init then --register before comparing
Findings default to P3/functionalMissing severity or category keysInclude both keys in each finding dict
Chrome MCP returns stale content after SPA navDOM updated without full page loadWait for transition, call read_page again

---

References

GuidePath
Browser Testing Methodologyreferences/browser_testing_methodology.md
WCAG Compliance Guidereferences/wcag_compliance_guide.md
Performance Benchmarksreferences/performance_benchmarks.md

---

Integration Points

SkillIntegration
code-reviewerHealth score and findings in PR review context
senior-frontendVisual regression baselines align with component library
senior-devopsHealth score gates CI/CD via exit code
senior-secopsSecurity header findings escalate to security review
incident-commanderP0 findings trigger incident response

---

Last Updated: April 2026 Version: 2.1.0

Related skills

FAQ

What does the QA sweep gate on?

A health score of at least 85, zero P0 findings, and WCAG AA at or above 95%.

Which WCAG levels are audited?

Level A (must fix), AA (should fix), and AAA (nice to have), each violation including the WCAG criterion, severity, element selector and remediation guidance.

Testing & QAtestingfrontend

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.