bug-reporting

Generate structured accessibility bug reports with URL, XPath, HTML snippet, WCAG SC, rule ID, severity, and frequency.

39|2|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/mgifford/accessibility-skills --skill bug-reporting-mgifford
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bug-reporting
Source: https://github.com/mgifford/accessibility-skills/tree/main/skills/bug-reporting
Command: npx skills add https://github.com/mgifford/accessibility-skills --skill bug-reporting-mgifford

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill standardizes and accelerates the creation of actionable accessibility bug reports by ensuring all mandatory fields are present and reports are easy to reproduce for developers.

Core Features & Use Cases

  • Enforces inclusion of URL, XPath (short and full), HTML snippet, WCAG SC, rule ID, severity, and frequency in every report.
  • Guides filing, reviewing, or generating reports from automated tool outputs or manual testing to improve clarity and remediation speed.
  • Use case: when a scan detects an accessibility issue, generate a complete report that engineers can reproduce and fix with minimal back-and-forth.

Quick Start

Provide a complete bug report for the detected issue in the required format, including all mandatory fields.

Frequently Asked Questions about bug-reporting

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

FAQPage Schema
How do I generate an accessibility bug report from automated scan data?

To generate an accessibility bug report from automated scan data, provide the testing output to the Skill. It automatically structures the data into an actionable report containing the URL, XPath, HTML snippet, and WCAG criteria.

What fields are required for a reproducible WCAG bug report?

A reproducible WCAG bug report requires specific mandatory fields: URL, short and full XPath, HTML snippet, WCAG SC, rule ID, severity, and frequency. These fields ensure developers can reproduce and fix issues quickly.

How do I format manual testing results into a structured bug report?

You format manual testing results into a structured bug report by inputting the detected issue details. The Skill enforces consistent formatting across pages and components, ensuring all mandatory accessibility fields are present for triage.

Can I use this for both automated tool outputs and manual QA testing workflows?

Yes, you can use this for both automated tool outputs and manual QA testing workflows. It standardizes the creation of actionable accessibility bug reports, ensuring all necessary fields are included regardless of the testing method.

What is the best way to standardize accessibility bug reporting for developer triage?

The best way to standardize accessibility bug reporting for developer triage is to enforce consistent formatting with mandatory fields like XPath, WCAG SC, and severity. This minimizes back-and-forth and accelerates remediation.

Why does my accessibility bug report lack sufficient detail for remediation?

An accessibility bug report lacks sufficient detail for remediation when mandatory fields like XPath, HTML snippet, or WCAG SC are missing. Enforcing a structured format ensures actionable and reproducible reports for engineers.