diff --git a/.continue/checks/accessibility-fix-agent.md b/.continue/checks/accessibility-fix-agent.md new file mode 100644 index 0000000000..9efa63ac1d --- /dev/null +++ b/.continue/checks/accessibility-fix-agent.md @@ -0,0 +1,415 @@ +--- +name: Accessibility Fix Agent +--- + +## Purpose + +Systematically scan the repository for accessibility issues, categorize them by WCAG compliance level and severity, and create tracked GitHub issues with specific remediation steps. This agent focuses on identifying and documenting accessibility violations that prevent users with disabilities from fully accessing the application. + +## Execution Steps + +### 1. Repository Scan + +1. Scan all HTML, JSX, TSX, and template files in the repository +2. Identify accessibility violations using the triage system below +3. For each unique issue type found, check if a GitHub issue already exists with the `accessibility` label +4. If no issue exists, create a new GitHub issue with detailed remediation steps + +### 2. Issue Classification + +Classify each accessibility issue using the triage system below to determine: + +- WCAG Level (A, AA, AAA) +- Severity (Critical, High, Medium, Low) +- Issue Category +- Affected files and line numbers + +### 3. GitHub Issue Creation + +For each new accessibility issue: + +1. Create GitHub issue with title format: `[A11Y] [Severity] Brief description` +2. Apply labels: `accessibility`, `wcag-[level]`, `severity-[level]` +3. Use the issue template below with specific violations and fixes +4. Group multiple instances of the same issue type into one issue with multiple file references + +### 4. Comment Marking + +Add HTML comment markers to affected code locations: + +```html + +[problematic code] + + +``` + +## Triage System + +### Category 1: Missing Alt Text (WCAG A - Critical) + +**Detection:** + +- `` tags without `alt` attribute +- `` on content images (not decorative) +- `` without `alt` + +**Impact:** Screen readers cannot describe images to blind users + +**Remediation:** + +- Add descriptive `alt` text for content images +- Use `alt=""` for decorative images +- For complex images, consider `aria-describedby` + +### Category 2: Keyboard Navigation Issues (WCAG A - Critical) + +**Detection:** + +- Interactive elements without keyboard support (missing `tabindex`, `onKeyDown`) +- `
` or `` used as buttons without proper ARIA roles +- Focus trap in modals without proper management +- Positive `tabindex` values (anti-pattern) +- Missing visible focus indicators (`:focus` styles) + +**Impact:** Keyboard-only users cannot access functionality + +**Remediation:** + +- Use semantic HTML (`