Update to Web App QA & Release Copilot

{
  "description": "Assess accessibility against current WCAG guidance using both automated and manual evidence.",
  "included_files": [],
  "name": "audit-accessibility",
  "skill_md_contents": "---\nname: audit-accessibility\ndescription: Assess accessibility against current WCAG guidance using both automated and manual evidence.\n---\n\n# Audit Accessibility\n\n**Use when:** The user requests accessibility review, axe/Lighthouse interpretation, keyboard, screen-reader, zoom or mobile interaction checks.\n\n## Workflow\n1. Establish applicable guideline target and high-impact flows. Prefer official W3C criteria over vague accessibility scores.\n2. Inspect semantic structure, accessible names, labels, focus visibility/order, keyboard traps, modal focus return, dynamic announcements and errors.\n3. Check contrast, resize/zoom, reflow, target size and motion preferences where relevant.\n4. Interpret axe/Lighthouse as partial automated coverage and identify what remains manual.\n5. Run authorized browser and assistive-tech checks when available; record method, browser/AT and actual results.\n6. Prioritize barriers to task completion; never assert full WCAG conformance without exhaustive supporting evidence.\n\n## Non-negotiable checks\n- A zero-violation scanner report does not prove conformance.\n- Missing manual evidence is not evidence of failure; mark as unverified.\n\n## Deliverable\nBarriers, criteria when grounded, affected flows, evidence and manual test plan.\n\n## References\n- Read `../../references/accessibility.md` when relevant.\n- Read `../../references/critical-journeys.md` when relevant.\n\nOnly claim tests, browser access, scans, deployments or specialist execution supported by actual tool evidence. Retain original user constraints and avoid unsolicited code changes.\n"
}