bug-reportinglisted

# Accessibility Bug Reporting Skill > **Canonical source**: `examples/ACCESSIBILITY_BUG_REPORTING_BEST_PRACTICES.md` in `mgifford/ACCESSIBILITY.md` > This skill is derived from that file. When in doubt, the example is authoritative. Apply these rules when filing, reviewing, or generating accessibility bug reports from any source — automated tool output, manual testing, or AI agent scans. --- ## Core Mandate **Reproducibility is the single most important quality of a bug report.** If a developer cannot reproduce the problem, they cannot fix it. Every report must give enough information for a developer who was not present during testing to reproduce, understand, and fix the problem without additional back-and-forth. --- ## Severity Scale (this skill) | Level | Meaning | Action | | --- | --- | --- | | **Critical** | Users cannot complete a core task at all | Must fix before release | | **High** | Significant barrier that degrades or blocks a key workflow | Fix urgently | | **Medium** | Noticeable barrier with a workaround available | Fix in near-term backlog | | **Low** | Minor issue with minimal real-world impact | Fix when convenient | --- ## Critical: Required Fields Every accessibility bug report **must** include all eight of the following fields. **Omitting any required field is Critical** — the report cannot be acted on. ### 1. Page URL Provide the exact URL where the issue was found, including query string and fragment identifier if relevant. ``` URL: https