Agent skill

Ibm A11y PR Remediation

Scan every frontend surface touched by the current PR/branch for IBM Equal Access Level 1 accessibility issues and fix all in-scope violations by default.

MITAuto-check passedFrontend & Design

Install Ibm A11y PR Remediation

skills CLI

$ npx skills add langflow-ai/langflow --skill ibm-a11y-pr-remediation -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install langflow-ai/langflow ibm-a11y-pr-remediation --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/langflow-ai/langflow.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/ibm-a11y-pr-remediation .claude/skills/ibm-a11y-pr-remediation && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "ibm-a11y-pr-remediation" agent skill from https://github.com/langflow-ai/langflow/tree/main/.agents/skills/ibm-a11y-pr-remediation into .claude/skills/ibm-a11y-pr-remediation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ibm-a11y-pr-remediation", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/langflow-ai/langflow/tree/main/.agents/skills/ibm-a11y-pr-remediation

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add langflow-ai/langflow --skill ibm-a11y-pr-remediation -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install langflow-ai/langflow ibm-a11y-pr-remediation --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/langflow-ai/langflow.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/ibm-a11y-pr-remediation .agents/skills/ibm-a11y-pr-remediation && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "ibm-a11y-pr-remediation" agent skill from https://github.com/langflow-ai/langflow/tree/main/.agents/skills/ibm-a11y-pr-remediation into .agents/skills/ibm-a11y-pr-remediation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ibm-a11y-pr-remediation", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add langflow-ai/langflow --skill ibm-a11y-pr-remediation -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install langflow-ai/langflow ibm-a11y-pr-remediation --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/langflow-ai/langflow.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/ibm-a11y-pr-remediation .cursor/skills/ibm-a11y-pr-remediation && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "ibm-a11y-pr-remediation" agent skill from https://github.com/langflow-ai/langflow/tree/main/.agents/skills/ibm-a11y-pr-remediation into .cursor/skills/ibm-a11y-pr-remediation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ibm-a11y-pr-remediation", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/langflow-ai/langflow.git --path .agents/skills/ibm-a11y-pr-remediation

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add langflow-ai/langflow --skill ibm-a11y-pr-remediation -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install langflow-ai/langflow ibm-a11y-pr-remediation --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/langflow-ai/langflow.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/ibm-a11y-pr-remediation .gemini/skills/ibm-a11y-pr-remediation && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "ibm-a11y-pr-remediation" agent skill from https://github.com/langflow-ai/langflow/tree/main/.agents/skills/ibm-a11y-pr-remediation into .gemini/skills/ibm-a11y-pr-remediation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ibm-a11y-pr-remediation", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install langflow-ai/langflow ibm-a11y-pr-remediation

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add langflow-ai/langflow --skill ibm-a11y-pr-remediation -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/langflow-ai/langflow.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/ibm-a11y-pr-remediation .github/skills/ibm-a11y-pr-remediation && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "ibm-a11y-pr-remediation" agent skill from https://github.com/langflow-ai/langflow/tree/main/.agents/skills/ibm-a11y-pr-remediation into .github/skills/ibm-a11y-pr-remediation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ibm-a11y-pr-remediation", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add langflow-ai/langflow --skill ibm-a11y-pr-remediation -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install langflow-ai/langflow ibm-a11y-pr-remediation --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/langflow-ai/langflow.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/ibm-a11y-pr-remediation .opencode/skills/ibm-a11y-pr-remediation && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "ibm-a11y-pr-remediation" agent skill from https://github.com/langflow-ai/langflow/tree/main/.agents/skills/ibm-a11y-pr-remediation into .opencode/skills/ibm-a11y-pr-remediation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ibm-a11y-pr-remediation", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: ibm-a11y-pr-remediation
GitHub stars: 155k
Token cost: ~2k tokens
SKILL.md length: 759 words
Files: 1
Skills in repo: 10
Repo updated: Oct 10, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Scan every frontend surface touched by the current PR/branch for IBM Equal Access Level 1 accessibility issues and fix all in-scope violations by default.

Works in 6 steps: Collect changed frontend files → Map files → surfaces → Scan (both engines must pass) → …
The user asks to check
SKILL.md covers Mandate, Progress checklist, 1. Collect changed frontend… and 2. Map files → surfaces, plus 4 more sections
Calls git, npx and gh

What it does

Ibm A11y PR Remediation is an agent skill from langflow-ai/langflow. Scan every frontend surface touched by the current PR/branch for IBM Equal Access Level 1 accessibility issues and fix all in-scope violations by default. Discovers changed files, maps them to routes/components/states, runs both axe and IBM engines, remediates until both are green (or only documented baselines remain), and reports back. Use when the user asks to check, scan, or clean up accessibility for "this PR", "my branch", or "my changes" and wants fixes applied, not just a report. For a single scoped audit…

Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Frontend & Design, covering Accessibility. The repository describes itself as: Langflow is a powerful tool for building and deploying AI-powered agents and workflows. The licence is MIT.

When your agent uses it

The user asks to check
Clean up accessibility for this PR
My changes and wants fixes applied
Not just a report

Example prompts

“this PR”
“my branch”
“my changes”
“/ibm-a11y-pr-remediation”

Requirements

Python 3
Node.js

Workflow steps

6 steps, taken from the step headings in SKILL.md.

Collect changed frontend files
Map files → surfaces
Scan (both engines must pass)
Fix all in-scope Level 1 violations
Tests / coverage
Re-scan and report

What it can do on your machine

Read from SKILL.md and the folder at commit 504c02f. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- git
- npx
- gh
- uv
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, npx, gh and uv, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Ibm A11y PR Remediation loads about 2k tokens when it runs. Until then it costs about 164 tokens; SKILL.md has 759 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~164
When it runs · the whole SKILL.md, loaded when a task matches: ~2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from langflow-ai/langflow at commit 504c02f, republished under its MIT licence (© langflow-ai). 759 words, ~2,047 tokens.

Download SKILL.mdSave it as .claude/skills/ibm-a11y-pr-remediation/SKILL.md (or your agent's skills folder).

name: ibm-a11y-pr-remediation
description: Scan every frontend surface touched by the current PR/branch for IBM Equal Access Level 1 accessibility issues and fix all in-scope violations by default. Discovers changed files, maps them to routes/components/states, runs both axe and IBM engines, remediates until both are green (or only documented baselines remain), and reports back. Use when the user asks to check, scan, or clean up accessibility for "this PR", "my branch", or "my changes" and wants fixes applied, not just a report. For a single scoped audit report without a default fix pass, use ibm-a11y-level1-audit; for a route batch scan only, use ibm-a11y-route-scan.
disable-model-invocation: true

IBM Level 1 PR Accessibility Remediation

Scope is IBM Equal Access Level 1 only. Default mode is fix, not report-only. Scan every frontend surface touched by the PR/branch and remediate all in-scope issues until both engines are green (or only documented baselines remain).

This skill is a PR-scoped orchestrator. It does not duplicate detailed engine/pattern guidance — read the linked skills for that:

ibm-a11y-testing-guide — which engine/test layer to use, POUR checklist, axe-vs-IBM gaps, Radix/AG-Grid gotchas, baselines.
ibm-a11y-route-scan — Python scanner options for ad-hoc route batches.
ibm-a11y-level1-audit — Level 1 criteria references and report template, useful when the user wants a formal audit report for the PR instead of (or in addition to) fixes.
frontend-i18n — accessible names / UI strings must go through i18n.

Mandate

Diff the PR (or current branch vs its merge base) for src/frontend/** changes.
Map changed files → UI surfaces → routes / components / states to scan.
Run both axe (Jest where applicable) and IBM Equal Access (Playwright page.runA11yScan and/or scripts/a11y/a11y_scan.py — see ibm-a11y-testing-guide / ibm-a11y-route-scan).
Fix every in-scope Level 1 violation in the changed surfaces. Do not stop at a findings list unless the user says report only (in that case, hand off to ibm-a11y-level1-audit).
Re-scan until assert mode passes. Add/update a11y specs when coverage is missing.
Report what changed, commands run, and any baselined/deferred debt.

Do not invent new tag names, silently disable scans, or expand into IBM Level 2/3 unless asked.

Progress checklist

IBM L1 PR A11y:
- [ ] 1. Collect changed frontend files
- [ ] 2. Map files → surfaces / routes / states
- [ ] 3. Scan (IBM + axe)
- [ ] 4. Fix all in-scope violations
- [ ] 5. Add/update tests if needed
- [ ] 6. Re-scan assert-green
- [ ] 7. Report back

1. Collect changed frontend files

Prefer the PR merge base when a PR exists; otherwise the branch merge base vs main/master.

bash

# PR number known
gh pr diff <n> --name-only | grep -E '^src/frontend/' || true

# Current branch vs upstream default
BASE=$(git merge-base HEAD origin/main 2>/dev/null || git merge-base HEAD origin/master)
git diff --name-only "$BASE"...HEAD -- 'src/frontend/**'

# Include uncommitted work when the user is mid-change
git diff --name-only HEAD -- 'src/frontend/**'
git diff --name-only --cached -- 'src/frontend/**'
git ls-files --others --exclude-standard 'src/frontend/**'

Include:

src/frontend/src/**/*.{tsx,ts,jsx,js,css} (UI)
src/frontend/tests/a11y/** (existing coverage)
Locale files only when they change accessible names / labels

Skip pure non-UI churn unless it affects a11y (e.g. test helpers that change focus / ARIA). If no frontend files changed, say so and stop.

2. Map files → surfaces

For each changed file, identify:

Change type	Scan target
Page / route	That route + meaningful states (empty/populated/modal/mobile)
Shared component (`TableComponent`, dialogs, menus)	Every consumer page that uses it — not only the file you touched
Primitive	Jest axe on the primitive + any Playwright surface that embeds it
Spec / baseline only	Re-run that spec; no product fix unless it fails
`a11y_routes.json`	Update static coverage; run static or route scan

List interactive controls and states (default, empty, populated, open modal / menu, selected row, error, mobile). Prefer existing specs under src/frontend/tests/a11y/.

3. Scan (both engines must pass)

Automated a11y is not one tool — see ibm-a11y-testing-guide for the full engine comparison and gotchas. Summary:

axe-core — Jest axe() (@/utils/a11y-test), jsdom-only.
IBM Equal Access — stricter on ARIA structure and keyboard semantics. Playwright page.runA11yScan(label) for stateful surfaces (modals/menus/selected/editing); scripts/a11y/a11y_scan.py for default-loaded page only.

bash

cd src/frontend
RUN_A11Y=true RUN_A11Y_ASSERT=true npx playwright test tests/a11y/<feature>.a11y.spec.ts --project=chromium --workers=5

# Python scanner playwright deps are NOT in default uv sync.
# One-time: uv run --with playwright playwright install chromium
uv run --with playwright python scripts/a11y/a11y_scan.py \
  --url http://localhost:3000 \
  --routes /settings/<route> \
  --out /tmp/a11y.json --markdown /tmp/a11y.md --timeout-ms 45000

RUN_A11Y=true runs the scan; RUN_A11Y_ASSERT=true fails on new violations. After changing a shared component, re-scan every page that uses it.

For component-only changes:

bash

cd src/frontend
npx jest path/to/<name>.a11y.test.tsx --runInBand

Do not invent findings — prefer scanner output plus manual Level 1 spot checks scanners miss (keyboard trap both ways, focus restore, 320px reflow, color-not-only).

Show full SKILL.md (278 more words)Show less

4. Fix all in-scope Level 1 violations

Default: fix. Only list proposed fixes without editing if the user asked report only — then hand off to ibm-a11y-level1-audit for the formal report format.

Rules:

Prefer semantic HTML over ARIA.
Follow the Langflow patterns in ibm-a11y-testing-guide (AG Grid, Radix asChild, focus restore, icon-only aria-label).
Route new UI strings / aria-labels through i18n (t(...), all locale files) per frontend-i18n.
Keep fixes minimal; do not refactor unrelated UI.
Do not silently disable scans. Use IBM baselines under src/frontend/tests/a11y/baselines/ only for documented framework debt.
Map each issue to a Level 1 WCAG/IBM id; defer anything listed as Level 2/3 in the criteria guide (ibm-a11y-level1-audit/references/ibm-level1-criteria.md) unless the user expands scope.

Manual Level 1 spot checks (when relevant)

2.1.1 / 2.1.2: Tab and Shift+Tab; Escape closes overlays; no trap.
2.4.3 / 2.4.7: Focus order matches visual order; focus ring visible.
1.4.10: 320px / ~400% zoom — no essential horizontal scroll.
1.4.1: Status/errors not color-only.
3.3.1 / 3.3.2: Errors in text and tied to fields; inputs labeled.

5. Tests / coverage

Surface	Spec
Static routes	`static-routes.a11y.spec.ts` (+ `scripts/a11y/a11y_routes.json`)
Auth	`auth-pages.a11y.spec.ts`
Core pages	`core-pages.a11y.spec.ts`
Data-rich	`files.a11y.spec.ts`, `api-keys.a11y.spec.ts`, `global-variables.a11y.spec.ts`
Other data-rich	`data-rich-routes.a11y.spec.ts`

If you fixed a state with no scan, add one (and keyboard tests for custom keyboard behavior) following files.a11y.spec.ts / api-keys.a11y.spec.ts patterns.

Tag every Playwright a11y test @release plus a domain tag (@workspace / @api / @database / @components / @starter-projects). Import test/expect from ../fixtures.

6. Re-scan and report

Re-run the same scans with RUN_A11Y_ASSERT=true. Each finding → fixed | baselined | open.

When done, state:

Changed frontend files considered
Surfaces / states scanned
Fixes applied (files + what)
Commands run — whether both axe and IBM ran and both reported zero
Specs / baselines added or updated
States skipped and why
Remaining risk or accepted limitation

Files

Just SKILL.md in .agents/skills/ibm-a11y-pr-remediation of langflow-ai/langflow.

Open the folder on GitHubat commit 504c02f

Compare with similar skills

Ibm A11y PR Remediation next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Ibm A11y PR Remediation compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Ibm A11y PR Remediation this skilllangflow-ai/langflow	155k	—	~2k	Automated safety check: Pass	MIT	yesterday
Web Interface Guidelines Reviewervercel-labs/openreview	1.7k	97 repos	~308	Automated safety check: Pass	None	7 mo ago
Accessibility Reviewmarkmead/hyperui	12k	1 repos	~1.1k	Automated safety check: Pass	MIT	yesterday
Web Animation DesignbaptisteArno/typebot.io	11k	2 repos	~2.7k	Automated safety check: Pass	Custom licence	4 days ago
Accessibility Fixeribelick/ui-skills	9.6k	4 repos	~1.2k	Automated safety check: Pass	MIT	today
Wcag Audit PatternsvmDeshpande/ai-agent-automation	178	11 repos	~610	Automated safety check: Pass	Apache-2.0	28 days ago

Similar skills

Web Interface Guidelines Reviewer
vercel-labs/openreview
Official
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my…
1.7k GitHub starsUsed in 97 repos~308 tokens
Frontend & DesignAuto-check passed
Accessibility Review
markmead/hyperui
Run a WCAG 2.1 AA accessibility audit on a design or page. An agent skill from markmead/hyperui.
12k GitHub starsUsed in 1 repo~1.1k tokens
Frontend & DesignAuto-check passed
Web Animation Design
baptisteArno/typebot.io
Guides easing, timing and animation choices for UI motion, based on a web animation course, and reviews existing animations in a before-and-after table.
11k GitHub starsUsed in 2 repos~2.7k tokens
Frontend & DesignAuto-check passed
Accessibility Fixer
ibelick/ui-skills
Audits and fixes HTML accessibility problems such as ARIA labels, keyboard navigation, focus management, contrast and form errors with minimal changes.
9.6k GitHub starsUsed in 4 repos~1.2k tokens
Frontend & DesignAuto-check passed
Wcag Audit Patterns
vmDeshpande/ai-agent-automation
Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance.
178 GitHub starsUsed in 11 repos~610 tokens
Frontend & DesignAuto-check passed
Baseline UI
ibelick/ui-skills
Applies a fixed set of UI rules for stack, components, interaction, animation, typography and layout, or reviews a file against them with concrete fixes.
9.6k GitHub starsUsed in 8 repos~855 tokens
Frontend & DesignAuto-check passed

More from langflow-ai/langflow

All 10 skills in this repo

Backend Code Review
langflow-ai/langflow
Review backend code for quality, security, maintainability, and best practices based on established checklist rules.
155k GitHub stars~3.5k tokensUpdated yesterday
Auto-check: notes
Component Refactoring
langflow-ai/langflow
Refactor high-complexity React components in Langflow frontend.
155k GitHub stars~3.5k tokensUpdated yesterday
Auto-check passed
E2E Testing
langflow-ai/langflow
Write and review Playwright E2E tests for Langflow. An agent skill from langflow-ai/langflow.
155k GitHub stars~3.3k tokensUpdated yesterday
Auto-check passed
Frontend Query Mutation
langflow-ai/langflow
Guide for implementing Langflow frontend query and mutation patterns with Axios and TanStack React Query v5.
155k GitHub stars~979 tokensUpdated yesterday
Auto-check passed
Ibm A11y Level1 Audit
langflow-ai/langflow
Perform a scoped IBM Equal Access Level 1 compliance audit of a chosen Langflow frontend surface (routes, components, or a PR) and produce a findings report mapped to WCAG/IBM Level 1 criteria.
155k GitHub stars~2.4k tokensUpdated yesterday
Auto-check passed
Frontend I18n
langflow-ai/langflow
Add, change, or review user-facing text in the Langflow frontend using the i18n system (i18next / react-i18next).
155k GitHub stars~1k tokensUpdated yesterday
Auto-check passed

Questions about Ibm A11y PR Remediation

What does Ibm A11y PR Remediation do?

Scan every frontend surface touched by the current PR/branch for IBM Equal Access Level 1 accessibility issues and fix all in-scope violations by default. Ibm A11y PR Remediation is an agent skill from langflow-ai/langflow. Scan every frontend surface touched by the current PR/branch for IBM Equal Access Level 1 accessibility issues and fix all in-scope violations by default.

When should I use Ibm A11y PR Remediation?

Ibm A11y PR Remediation fits situations like: the user asks to check; clean up accessibility for this PR; my changes and wants fixes applied; not just a report.

How do I install Ibm A11y PR Remediation in Claude Code?

Run `npx skills add langflow-ai/langflow --skill ibm-a11y-pr-remediation -a claude-code`. Or copy the skill folder (.agents/skills/ibm-a11y-pr-remediation in langflow-ai/langflow) into .claude/skills/ibm-a11y-pr-remediation in your project. Claude Code loads it when a task matches its description.

How do I install Ibm A11y PR Remediation in Codex?

Run `npx skills add langflow-ai/langflow --skill ibm-a11y-pr-remediation -a codex`. Or copy the skill folder (.agents/skills/ibm-a11y-pr-remediation in langflow-ai/langflow) into .agents/skills/ibm-a11y-pr-remediation in your project. Codex loads it when a task matches its description.

Can I use Ibm A11y PR Remediation in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add langflow-ai/langflow --skill ibm-a11y-pr-remediation -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ibm-a11y-pr-remediation, .gemini/skills/ibm-a11y-pr-remediation, .github/skills/ibm-a11y-pr-remediation and .opencode/skills/ibm-a11y-pr-remediation in your project.

What does Ibm A11y PR Remediation need to run?

Going by SKILL.md and its folder, Ibm A11y PR Remediation needs the command-line tools its instructions call (git, npx, gh and uv). Our summary lists: Python 3; Node.js.

Does Ibm A11y PR Remediation access the network?

SKILL.md contains no URLs. Its commands use git, npx, gh and uv, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Ibm A11y PR Remediation safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Ibm A11y PR Remediation use?

Ibm A11y PR Remediation is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Ibm A11y PR Remediation use?

About 2k tokens (SKILL.md is roughly 8.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Ibm A11y PR Remediation?

Skills that share tags, products or a category with Ibm A11y PR Remediation: Web Interface Guidelines Reviewer (vercel-labs/openreview, 1.7k stars), Accessibility Review (markmead/hyperui, 12k stars), Web Animation Design (baptisteArno/typebot.io, 11k stars) and Accessibility Fixer (ibelick/ui-skills, 9.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Ibm A11y PR Remediation?

langflow-ai (a GitHub organization) maintains it in langflow-ai/langflow, which has 155,453 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on October 10, 2026.

Source: langflow-ai/langflow on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Ibm A11y PR Remediation

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

IBM Level 1 PR Accessibility Remediation

Mandate

Progress checklist

1. Collect changed frontend files

2. Map files → surfaces

3. Scan (both engines must pass)

4. Fix all in-scope Level 1 violations

Manual Level 1 spot checks (when relevant)

5. Tests / coverage

6. Re-scan and report

Files

Compare with similar skills

Similar skills

More from langflow-ai/langflow

Related

Questions about Ibm A11y PR Remediation