qa

Validate web interfaces for visual and accessibility compliance using agent-browser.

Updated Mar 12, 2026
One-click install
npx skills add https://github.com/sethihq/guide --skill qa-sethihq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/sethihq/guide/tree/main/public/kit/skills/qa
Command: npx skills add https://github.com/sethihq/guide --skill qa-sethihq

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires agent-browser, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that user interfaces are visually correct and meet accessibility standards, preventing bugs and improving user experience.

Core Features & Use Cases

  • Visual QA: Perform comprehensive visual checks on web pages or components.
  • Accessibility Audits: Verify compliance with accessibility guidelines (WCAG).
  • Use Case: After developing a new feature, use this Skill to visually inspect the changes, check for broken layouts, and ensure all interactive elements are accessible before submitting a pull request.

Quick Start

Use the qa skill to navigate to http://localhost:3000 and perform a visual and accessibility check.

Frequently Asked Questions about qa

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I perform a visual UI validation check on a local web page?

To perform visual UI validation, the Skill navigates to your local web page using agent-browser, captures screenshots, and analyzes the interface against a defined checklist to detect broken layouts and visual regressions.

Can I automate accessibility audits for WCAG compliance before a release?

Yes, you can automate accessibility audits by having the Skill snapshot the accessibility tree via agent-browser and evaluate interactive elements against a11y standards, ensuring WCAG compliance before submitting a pull request.

Do I need agent-browser to run web accessibility and visual checks?

Yes, agent-browser is a required dependency, as the Skill relies on it to navigate web interfaces, capture screenshots, and extract accessibility trees for validation against design and a11y standards.

What is the best way to verify component UI changes and a11y standards during development?

The best way is to run the Skill after developing a new feature; it visually inspects component changes, checks for broken layouts, and validates that all interactive elements meet accessibility guidelines before release.

Does this visual QA process work for pre-release checks on web interfaces?

Yes, the Skill is explicitly designed for pre-release checks, allowing you to perform comprehensive visual QA and accessibility verification on web interfaces and components prior to deployment.

Why does my accessibility audit require an accessibility tree snapshot?

Accessibility tree snapshots are required because they provide the structured DOM representation needed to verify interactive elements and validate compliance against defined a11y and WCAG checklists.