Agent skill

Compliance Mapping

by Owl-Listener in Owl-Listener/inclusive-design-skills

Map design decisions to accessibility standards and legal requirements.

MITAuto-check passedFrontend & Design

Install Compliance Mapping

skills CLI
$ npx skills add Owl-Listener/inclusive-design-skills --skill compliance-mapping -a claude-code

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

GitHub CLI
$ gh skill install Owl-Listener/inclusive-design-skills compliance-mapping --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/Owl-Listener/inclusive-design-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/accessibility-decisions/skills/compliance-mapping .claude/skills/compliance-mapping && 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/

Facts

Skill name
compliance-mapping
GitHub stars
105
Token cost
~1.1k tokens
SKILL.md length
506 words
Files
1
Skills in repo
55
Repo updated
First seen
Licence
MIT

At a glance

Map design decisions to accessibility standards and legal requirements.

  • Works in 4 steps: Can the team map their key design… → Are there design decisions that would… → Does the team know which legal… → …
  • Documenting WCAG conformance
  • SKILL.md covers Why Designers Need This, Key Standards, Design Decision to WCAG Mapping and How to Use This, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Compliance Mapping is an agent skill from Owl-Listener/inclusive-design-skills. Map design decisions to accessibility standards and legal requirements. Use when documenting WCAG conformance, preparing for audits, tracking compliance status, or when legal or procurement requires accessibility documentation. Triggers on: WCAG, compliance, conformance, audit, VPAT, accessibility statement, legal requirement, ADA, EAA, European Accessibility Act, Section 508, EN 301 549, accessibility standard, success criterion.

Its SKILL.md is about 1.1k 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 and Architecture decision records. The repository describes itself as: Inclusive design skills for AI coding agents — from cognitive accessibility to adaptive interfaces, inclusive research, and accessibility decision-making. The licence is MIT.

When your agent uses it

  • Documenting WCAG conformance
  • Preparing for audits
  • Tracking compliance status
  • Procurement requires accessibility documentation

Example prompts

  • “/compliance-mapping”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Can the team map their key design decisions to WCAG criteria?
  2. Are there design decisions that would cause conformance failures?
  3. Does the team know which legal frameworks apply to their product?
  4. Is there a process for checking designs against standards before

What it can do on your machine

Read from SKILL.md and the folder at commit 6e0740f. 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

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    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

Compliance Mapping loads about 1.1k tokens when it runs. Until then it costs about 113 tokens; SKILL.md has 506 words of instructions outside code blocks.

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

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 Owl-Listener/inclusive-design-skills at commit 6e0740f, republished under its MIT licence (© Owl-Listener). 506 words, ~1,064 tokens.

Download SKILL.mdSave it as .claude/skills/compliance-mapping/SKILL.md (or your agent's skills folder).
name
compliance-mapping
description
Map design decisions to accessibility standards and legal requirements. Use when documenting WCAG conformance, preparing for audits, tracking compliance status, or when legal or procurement requires accessibility documentation. Triggers on: WCAG, compliance, conformance, audit, VPAT, accessibility statement, legal requirement, ADA, EAA, European Accessibility Act, Section 508, EN 301 549, accessibility standard, success criterion.

Compliance Mapping

Map design decisions to specific accessibility standards so the team knows exactly where they stand — what's covered, what's not, and what's at risk.

Why Designers Need This

Compliance mapping is usually treated as an engineering audit task. But most conformance failures originate in design decisions made before code was written. A designer who understands which standards their decisions affect can prevent failures instead of discovering them.

Key Standards

WCAG 2.2 Level AA

The global baseline. Most laws reference this.

  • Level A: minimum (29 criteria)
  • Level AA: standard target (20 additional criteria)
  • Level AAA: aspirational (28 additional criteria)

Most organisations target Level AA. Some criteria in Level AAA are worth adopting even if not required (especially cognitive accessibility criteria).

  • ADA (US): requires accessible digital services, courts reference WCAG 2.1 AA
  • EAA (EU): European Accessibility Act, effective June 2025, references EN 301 549 which aligns with WCAG 2.1 AA
  • Section 508 (US government): references WCAG 2.0 AA, update expected
  • EN 301 549 (EU): the technical standard behind EAA, aligned with WCAG 2.1 AA plus additional requirements for software, hardware, and documentation

Design Decision to WCAG Mapping

Colour and Visual Design
Design decisionWCAG criteria
Text contrast ratios1.4.3 Contrast (Minimum) AA
Non-text contrast1.4.11 Non-text Contrast AA
Colour not sole indicator1.4.1 Use of Color A
Text resizing to 200%1.4.4 Resize Text AA
Content reflow at zoom1.4.10 Reflow AA
Text spacing override1.4.12 Text Spacing AA
Interaction Design
Design decisionWCAG criteria
Keyboard operability2.1.1 Keyboard A
No keyboard traps2.1.2 No Keyboard Trap A
Focus visible2.4.7 Focus Visible AA
Focus order logical2.4.3 Focus Order A
Touch target size2.5.8 Target Size (Minimum) AA
No motion-only input2.5.4 Motion Actuation A
Gesture alternatives2.5.1 Pointer Gestures A
Show full SKILL.md (213 more words)Show less
Content and Structure
Design decisionWCAG criteria
Page titles2.4.2 Page Titled A
Heading hierarchy1.3.1 Info and Relationships A
Link purpose clear2.4.4 Link Purpose (In Context) A
Language of page set3.1.1 Language of Page A
Consistent navigation3.2.3 Consistent Navigation AA
Error identification3.3.1 Error Identification A
Labels on inputs3.3.2 Labels or Instructions A
Motion and Timing
Design decisionWCAG criteria
Pause/stop/hide motion2.2.2 Pause, Stop, Hide A
No flashing content2.3.1 Three Flashes A
Timing adjustable2.2.1 Timing Adjustable A
Animation from interaction2.3.3 Animation from Interactions AAA

How to Use This

During Design

Before finalising a design decision, check which WCAG criteria it affects. This catches failures at the cheapest point to fix them.

During Review

Map the design against the relevant criteria table. Flag any decision that would cause a conformance failure.

For Audit Preparation

Use the mapping tables to create a pre-audit checklist specific to your product. This tells auditors exactly which decisions map to which criteria.

Assessment Questions

  1. Can the team map their key design decisions to WCAG criteria?
  2. Are there design decisions that would cause conformance failures?
  3. Does the team know which legal frameworks apply to their product?
  4. Is there a process for checking designs against standards before implementation?

© Owl-Listener, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in accessibility-decisions/skills/compliance-mapping of Owl-Listener/inclusive-design-skills.

Open the folder on GitHubat commit 6e0740f

Compare with similar skills

Compliance Mapping 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.

Compliance Mapping compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Compliance Mapping this skillOwl-Listener/inclusive-design-skills105—~1.1kAutomated safety check: PassMIT
Typeui Fundamentalsbergside/typeui2k—~861Automated safety check: PassMIT
Design Standardsrampstackco/claude-skills945—~2.4kAutomated safety check: PassMIT
Web Interface Guidelines Reviewervercel-labs/openreview1.7k97 repos~308Automated safety check: PassNone
Accessibility Reviewmarkmead/hyperui12k1 repos~1.1kAutomated safety check: PassMIT
Web Animation DesignbaptisteArno/typebot.io11k2 repos~2.7kAutomated safety check: PassCustom licence

Similar skills

  • Typeui Fundamentals

    bergside/typeui

    Universal UI/UX design principles covering visual hierarchy, interaction laws, typography foundations, and WCAG accessibility requirements.

    2k GitHub stars~861 tokensUpdated 3 mo ago
    Frontend & DesignAuto-check passed
  • Design Standards

    rampstackco/claude-skills

    Apply production-grade design standards when building or reviewing pages, components, or UI.

    945 GitHub stars~2.4k tokensUpdated 3 days ago
    Frontend & DesignAuto-check passed
  • 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

More from Owl-Listener/inclusive-design-skills

All 55 skills in this repo
  • Assistive Technology Scenarios

    Owl-Listener/inclusive-design-skills

    Writes usage scenarios, use cases and storyboards that show real people using screen readers, switches, voice control and other assistive technology to finish tasks.

    105 GitHub stars~1.1k tokensUpdated 4 mo ago
    Auto-check passed
  • Error Prevention and Recovery

    Owl-Listener/inclusive-design-skills

    Designs forgiving forms and flows: prevent input errors, write messages that say what happened and what to do, and add undo, confirmation and recovery paths.

    105 GitHub stars~739 tokensUpdated 4 mo ago
    Auto-check passed
  • Accessible Heading Structure

    Owl-Listener/inclusive-design-skills

    Designs heading hierarchies for screen reader navigation and cognitive accessibility on pages, articles, dashboards and forms.

    105 GitHub stars~763 tokensUpdated 4 mo ago
    Auto-check passed
  • Ability Spectrum Mapping

    Owl-Listener/inclusive-design-skills

    Maps a feature across a range of vision, hearing, motor and cognitive ability to find where the design starts to fail, and to explain accessibility scope to stakeholders.

    105 GitHub stars~917 tokensUpdated 4 mo ago
    Auto-check passed
  • Accessibility Debt Tracking

    Owl-Listener/inclusive-design-skills

    Track and manage accessibility debt — known accessibility issues that have been deferred.

    105 GitHub stars~869 tokensUpdated 4 mo ago
    Auto-check passed
  • Accessibility Testing Strategy

    Owl-Listener/inclusive-design-skills

    Plan what to test, how to test, and who should test for accessibility.

    105 GitHub stars~1k tokensUpdated 4 mo ago
    Auto-check passed

Questions about Compliance Mapping

What does Compliance Mapping do?

Map design decisions to accessibility standards and legal requirements. Compliance Mapping is an agent skill from Owl-Listener/inclusive-design-skills. Map design decisions to accessibility standards and legal requirements.

When should I use Compliance Mapping?

Compliance Mapping fits situations like: documenting WCAG conformance; preparing for audits; tracking compliance status; procurement requires accessibility documentation.

How do I install Compliance Mapping in Claude Code?

Run `npx skills add Owl-Listener/inclusive-design-skills --skill compliance-mapping -a claude-code`. Or copy the skill folder (accessibility-decisions/skills/compliance-mapping in Owl-Listener/inclusive-design-skills) into .claude/skills/compliance-mapping in your project. Claude Code loads it when a task matches its description.

How do I install Compliance Mapping in Codex?

Run `npx skills add Owl-Listener/inclusive-design-skills --skill compliance-mapping -a codex`. Or copy the skill folder (accessibility-decisions/skills/compliance-mapping in Owl-Listener/inclusive-design-skills) into .agents/skills/compliance-mapping in your project. Codex loads it when a task matches its description.

Can I use Compliance Mapping 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 Owl-Listener/inclusive-design-skills --skill compliance-mapping -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/compliance-mapping, .gemini/skills/compliance-mapping, .github/skills/compliance-mapping and .opencode/skills/compliance-mapping in your project.

What does Compliance Mapping need to run?

SKILL.md names no scripts, command-line tools or credentials: Compliance Mapping is instructions for the agent only.

Does Compliance Mapping access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Compliance Mapping 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 Compliance Mapping use?

Compliance Mapping 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 Compliance Mapping use?

About 1.1k tokens (SKILL.md is roughly 4.3k 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 Compliance Mapping?

Skills that share tags, products or a category with Compliance Mapping: Typeui Fundamentals (bergside/typeui, 2k stars), Design Standards (rampstackco/claude-skills, 945 stars), Web Interface Guidelines Reviewer (vercel-labs/openreview, 1.7k stars) and Accessibility Review (markmead/hyperui, 12k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Compliance Mapping?

Owl-Listener (a GitHub user) maintains it in Owl-Listener/inclusive-design-skills, which has 105 GitHub stars. The repository holds 55 skills in this directory. The repository was last updated on June 9, 2026.

Source: Owl-Listener/inclusive-design-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.