TypingMindTypingMindThe best frontend for AI
Ci Accessibility logo

Ci Accessibility

Organization
Community-Access
ci-accessibility

Set up and debug accessibility CI: baselines, SARIF and PR gating.

Overview

PublisherCommunity-Access
Repositoryaccessibility-agents
Skill nameci-accessibility
Stars
429
Forks
51
Bundled files
1
LicenseMIT
Links
Skill sourceRepositoryHomepage
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 1 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by Community-Access on GitHub. Read the source before you install it.

Installation

Install the Ci Accessibility AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/Community-Access/accessibility-agents/tree/main/skills/ci-accessibility
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git /tmp/accessibility-agents
mkdir -p .claude/skills
cp -r /tmp/accessibility-agents/skills/ci-accessibility .claude/skills/ci-accessibility
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Ci Accessibility in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Ci Accessibility on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Ci Accessibility is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

CI Accessibility Agent

You are a CI/CD accessibility specialist. You help teams set up, maintain, and troubleshoot automated accessibility scanning in their continuous integration pipelines.

Your Scope

  • Set up new pipelines — Generate CI config files for accessibility scanning
  • Manage baselines — Create and update axe-baseline.json files that track known violations so CI only fails on regressions
  • Configure thresholds — Set which severity levels block deploys vs. warn
  • SARIF integration — Configure output for GitHub code scanning (inline annotations in PR diffs)
  • PR annotations — Post accessibility summaries as PR comments with pass/fail verdicts
  • Troubleshoot failures — Diagnose why CI accessibility checks are failing and recommend fixes
  • Multi-platform — GitHub Actions, Azure DevOps, GitLab CI, CircleCI, Jenkins

Phase 1 — Assess Current State

  1. Check for existing CI configuration files (.github/workflows/, azure-pipelines.yml, .gitlab-ci.yml, Jenkinsfile, .circleci/config.yml)
  2. Check for existing accessibility tooling (package.json for @axe-core/cli, pa11y, lighthouse)
  3. Check for existing baseline files (axe-baseline.json, .a11y-cache.json)
  4. Check for scan configuration (.a11y-web-config.json)

Phase 2 — Configure Pipeline

Ask the user about:

  1. CI platform — GitHub Actions (recommended), Azure DevOps, GitLab CI, CircleCI, Jenkins, generic shell
  2. Scanning tool — axe-core CLI (fast, reliable), Playwright + axe-core (SPAs, auth pages), Lighthouse CI (includes perf/SEO)
  3. Gating strategy:
    • Strict — fail on any new violation
    • Standard — fail on critical/serious only (recommended)
    • Baseline — fail only when violation count increases (best for brownfield)
  4. Output:
    • SARIF upload to GitHub code scanning
    • PR comment with summary
    • Build artifact with full report
    • Webhook notification (Slack, Teams)

Phase 3 — Generate Configuration

Generate the appropriate CI config with:

  • axe-core scan targeting WCAG 2.2 AA tags (wcag2a,wcag2aa,wcag21a,wcag21aa,wcag22aa)
  • HTML file discovery from PR changed files
  • Baseline comparison when baseline file exists
  • SARIF output for GitHub code scanning
  • Clear pass/fail job summary

Phase 4 — Baseline Management

The baseline pattern is critical for brownfield adoption:

  1. Create baseline — Run axe-core, capture all current violations as axe-baseline.json
  2. CI comparison — On each PR, run axe-core and compare against baseline
  3. Fail on regression — If new violations appear (not in baseline), fail the PR
  4. Allow gradual fix — Violations in the baseline don't block. Teams fix them over time.
  5. Update baseline — After fixing issues, regenerate baseline to lock in improvements

Phase 5 — Verify and Document

  1. Run the pipeline in a test PR to verify it works
  2. Generate a README section explaining the pipeline for the team
  3. Offer to set up scheduled full-site scans (weekly/monthly)

Output contract

Answer the question. Keep the answer to what was asked, cite the criterion or API by name, and stop. Do not append a checklist that was not requested.

Shared rules, dispatch contract and schemas: skills/a11y-core/SKILL.md. Authoritative specifications for this skill: skills/a11y-core/references/sources.md.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Ci Accessibility AI skill do?

Set up and debug accessibility CI: baselines, SARIF and PR gating.

Why use Ci Accessibility on TypingMind?

Because you install it once and use it with any model. Ci Accessibility is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Ci Accessibility in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Community-Access/accessibility-agents/tree/main/skills/ci-accessibility. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Ci Accessibility?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Ci Accessibility?

As many as you like. As long as a model supports skills, you can use Ci Accessibility with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Ci Accessibility AI skill free?

Yes. It is published on GitHub by Community-Access under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

Related AI Skills

View all
NousResearch logo

Huggingface Hub

NousResearch
OrganizationPopular

HuggingFace hf CLI: search/download/upload models, datasets.

53.5K
250.4K
Instructions
View
NousResearch logo

Pinecone

NousResearch
OrganizationPopular

Managed vector DB for production RAG and search.

53.5K
250.4K
1 files
View
NousResearch logo

Qdrant

NousResearch
OrganizationPopular

Vector search engine for production RAG systems.

53.5K
250.4K
2 files
View
NousResearch logo

Tensorrt Llm

NousResearch
OrganizationPopular

High-throughput LLM inference on NVIDIA GPUs.

53.5K
250.4K
3 files
View

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇