CI/CD Automated Accessibility Check Workflow
Automatically run accessibility checks on every pull request, generate a report, and comment on the PR to help teams catch and fix accessibility issues before merging.
When a PR is triggered, clone the repository using {repo_url} and {branch}, run {accessibility_rules}, output the results in {output_format}, and post a comment on the PR via GitHub API.Variable Dictionary (fill in your AI tool)
This section only explains placeholders. It is not an input form on this website. Copy the prompt, then replace variables in Coze / Dify / ChatGPT.
{repo_url}GitHub repository HTTPS URL, e.g., https://github.com/owner/repo.git
Filling hint: replace this with your real business context.
{branch}Branch name of the PR, e.g., feature/login-form
Filling hint: replace this with your real business context.
{accessibility_rules}List of accessibility rule IDs to run, e.g., ['wcag2a', 'wcag2aa']
Filling hint: replace this with your real business context.
{output_format}Report format, either 'markdown' or 'json'
Filling hint: replace this with your real business context.
Quick Variable Filler (Optional)
Fill variables below to generate a ready-to-run prompt in your browser.
{repo_url}GitHub repository HTTPS URL, e.g., https://github.com/owner/repo.git
{branch}Branch name of the PR, e.g., feature/login-form
{accessibility_rules}List of accessibility rule IDs to run, e.g., ['wcag2a', 'wcag2aa']
{output_format}Report format, either 'markdown' or 'json'
Generated Prompt Preview
When a PR is triggered, clone the repository using {repo_url} and {branch}, run {accessibility_rules}, output the results in {output_format}, and post a comment on the PR via GitHub API.How to Use This Template
Best for
Teams that need faster development output with more stable prompt quality.
Problem it solves
Reduces blank-page time, missing constraints, and inconsistent output structure from ad-hoc prompting.
Steps
- Copy the template prompt.
- Paste it into your AI tool (Coze / Dify / ChatGPT).
- Replace placeholder variables using the dictionary above.
- Run and refine constraints based on output quality.
Not ideal when
You need live web retrieval, database writes, or multi-step tool orchestration. Use full workflow automation for that.
Success Case
Boundary Case
What to Try Next
Keep exploring with similar templates and matching tools.
Continue Where You Left Off
No recent items yet.
Workflow Steps
1. Listen for GitHub PR events and retrieve PR ID, repo_url, and branch.
2. Clone the specified branch using a GitHub Actions runner or self‑hosted runner.
3. Execute axe‑core or a similar tool in the cloned directory, passing {accessibility_rules} for scanning.
4. Parse the scan results and generate a {output_format} report.
5. Use the GitHub API to post the report as a comment on the PR and set a status check.
Constraints
- PR contains no HTML/CSS/JS files relevant to accessibility
- Repository exceeds 500MB, causing clone timeout
Explore More in This Category
Development