manual-testing

# Manual Accessibility Testing Skill > **Canonical source**: `examples/MANUAL_ACCESSIBILITY_TESTING_GUIDE.md` in `mgifford/ACCESSIBILITY.md` > This skill is derived from that file. When in doubt, the example is authoritative. Apply these rules when planning or reviewing manual accessibility testing. --- ## Severity Scale (this skill) | Level | Meaning | |---|---| | **Critical** | Issue completely blocks a core task for one or more disability groups | | **Serious** | Significantly impairs access; workaround unreasonable to expect | | **Moderate** | Creates friction; workaround exists and is not too burdensome | | **Minor** | Best-practice gap; marginal impact on access | --- ## Core Principle **Manual testing reveals issues that automated tools cannot detect**, including: * Screen reader announcement quality and user experience * Keyboard navigation flow and logical sequence * Focus management in dynamic interfaces * Context and orientation for assistive technology users * Forced colors mode (Windows High Contrast) — automated tools cannot simulate OS-level color overrides * Real-world usability barriers --- ## Critical: When Manual Testing Is Required Perform manual testing: * **Before each release** — test critical user flows end to end * **After UI changes** — test all affected components * **For new features** — test complete user workflows * **When automated tests pass** — validate actual user experience * **When accessibility bugs are reported** — reproduce ...