Add "Accessibility Fix Agent" check

[continue]

Adds the Accessibility Fix Agent check to this repository.

This check will be synced from .continue/checks/accessibility-fix-agent.md and can be customized by editing the file directly.

---

Opened via Continue Hub

Summary by Sourcery

Add a repository-local definition for an Accessibility Fix Agent that automates detection, classification, and tracking of accessibility issues via GitHub issues and code annotations.

New Features:

• Introduce an Accessibility Fix Agent specification that scans code for accessibility violations and files labeled GitHub issues with remediation details.
• Define a triage system categorizing accessibility issues by WCAG level, severity, and type, with guidance for detection and remediation.
• Add standardized templates for accessibility issue reports, commit messages, HTML comment markers, and scan summaries to ensure consistent tracking and communication.

Documentation:

• Document processes and best practices for automated accessibility scanning, reporting, and remediation across the repository.

[sourcery-ai]

Reviewer's Guide

Adds a new Continue Hub accessibility check definition file that configures an "Accessibility Fix Agent" to scan the repo for WCAG-related accessibility issues, create and label GitHub issues, annotate source code with HTML comments, and define reporting and best-practice guidelines.

Sequence diagram for Accessibility Fix Agent repository scan and issue creation

sequenceDiagram
    actor Developer
    participant AccessibilityFixAgent
    participant Repo
    participant GitHubAPI

    Developer->>AccessibilityFixAgent: Start accessibility scan
    AccessibilityFixAgent->>Repo: Scan HTML/JSX/TSX/template files
    AccessibilityFixAgent->>AccessibilityFixAgent: Classify issues by WCAG level and severity
    loop For each unique issue type
        AccessibilityFixAgent->>GitHubAPI: Check existing issues with accessibility label
        alt No existing issue
            AccessibilityFixAgent->>GitHubAPI: Create issue [A11Y][Severity] with labels
        end
        AccessibilityFixAgent->>Repo: Add accessibility-fix comment markers
    end
    AccessibilityFixAgent->>GitHubAPI: Create weekly digest or Discussion summary

Loading

File-Level Changes

Change	Details	Files
Introduce the Accessibility Fix Agent configuration used by Continue to automate discovery, tracking, and remediation of accessibility issues.	Define the agent purpose and high-level execution steps for scanning repo files, classifying violations, creating GitHub issues, and inserting comment markers in source code. Specify a detailed triage system with 10 accessibility issue categories (e.g., missing alt text, keyboard navigation, forms, contrast, semantic HTML, ARIA, media, dynamic content, mobile, skip links) including detection rules, impact, and remediation guidance. Provide a standardized GitHub issue template, commit message conventions, HTML comment marker formats for open and fixed issues, and integration requirements for GitHub API and filesystem access. Outline recommended automated checks, reporting format for scan results, and general best practices for grouping, prioritizing, explaining, and testing accessibility fixes.	.continue/checks/accessibility-fix-agent.md

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've left some high level feedback:

• The "HTML Comment Marker" format is described twice (once in the Comment Marking section and again later); consider consolidating this into a single, canonical subsection to avoid divergence over time.
• Since the workflow assumes labels like wcag-[level] and severity-[level] exist, it may help to explicitly call out that these labels must be pre-created or define the exact values expected (e.g., wcag-a, severity-critical) to avoid inconsistent labeling.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- The "HTML Comment Marker" format is described twice (once in the Comment Marking section and again later); consider consolidating this into a single, canonical subsection to avoid divergence over time.
- Since the workflow assumes labels like `wcag-[level]` and `severity-[level]` exist, it may help to explicitly call out that these labels must be pre-created or define the exact values expected (e.g., `wcag-a`, `severity-critical`) to avoid inconsistent labeling.

Fix all in Cursor

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}