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, user reports, or testing with disabled people. --- ## Core Mandate A useful report lets another person understand the barrier, identify the people affected, reproduce it when possible, judge its impact, identify the responsible source, and verify the correction. Not every field applies to every finding — **do not delay a valid report because a selector, tool rule, WCAG mapping, or code-level fix is unavailable.** **Principles:** 1. **Describe the barrier before the standard** — state what task or interaction fails and under what conditions 2. **Identify the people affected** — describe access needs/interaction methods/AT when evidence supports it; never infer a diagnosis or imply one person represents an entire disability group 3. **State the evidence basis** — distinguish user reports, testing with disabled people, manual evaluation, automated results, and reasoned inference 4. **Record observed facts** separately from assumptions, suspected causes, and suggested fixes 5. **Use complementary testing methods** — automated, manual, and testing-with-disabled-people answer different questions; none substitut