What is accessibility-compliance?

A tool for mapping accessibility laws across several markets, including the ADA, Section 508, the European Accessibility Act, and laws in the UK and Canada. It connects those legal duties with WCAG, a widely used set of web accessibility guidelines, and suggests remediation steps.

Use it to assess multi-market accessibility obligations, identify required WCAG conformance levels, plan fixes, and draft an accessibility statement.

It helps organisations selling in multiple countries understand which accessibility rules may apply and where their product or service may fall short.

accessibility-compliance — Skill for Claude Code by bromso/metapowers

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add bromso/metapowers --skill accessibility-compliance

Clone the repo

git clone --depth 1 https://github.com/bromso/metapowers

Made for: Claude Code.

Or install legal, the plugin that ships this one along with the rest of its 35 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/bromso/metapowers/accessibility-compliance/github.svg)](https://agentmods.dev/skills/bromso/metapowers/accessibility-compliance)

Your own site

<a href="https://agentmods.dev/skills/bromso/metapowers/accessibility-compliance"><img src="https://agentmods.dev/badge/skills/bromso/metapowers/accessibility-compliance/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/bromso/metapowers/accessibility-compliance"><img src="https://agentmods.dev/badge/skills/bromso/metapowers/accessibility-compliance.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 90 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,397 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00090	$0.01397
Opus 5.5	$0.00036	$0.00559
Sonnet 5.5	$0.00018	$0.00279
Haiku 4.5	$0.00009	$0.00140

Measured 3d ago against content hash 865f501cc1d7, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

accessibility-compliance scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/legal/skills/accessibility-compliance/SKILL.md · 107 lines

How it starts

The opening of the file, as written. The whole thing — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Accessibility Compliance

Assess legal accessibility requirements for "$ARGUMENTS". Identify applicable accessibility laws, determine WCAG conformance requirements, assess current compliance, and create a remediation plan.

See also /accessibility:scope for the audit itself, or /compliance:ada-wcag for a single-market (ADA) legal risk assessment, instead of this multi-market legal map.

Note: AI-generated legal content does not constitute legal advice. Consult a qualified attorney.

Arguments. $ARGUMENTS may contain the project name and optional flags. Take the first token as <project> and treat --skip-checks as a flag; never include flags in file paths. All paths below use <project>. If --skip-checks is present, skip the prerequisite check and, before writing any artifact, append one line to .metapowers/legal/<project>/skip-log.md: - <ISO timestamp> — <skill name> skipped prerequisite check for <artifact file> — reason: <reason or "none given">.

Prerequisites

Check that .metapowers/legal/<project>/00-assess.md exists. If it does not exist, stop and tell the user:

"Run an Assess skill first (e.g. /legal:risk-assessment <project>) to generate the prerequisite assessment artifact."

Process

Read inputs:
- Read .metapowers/legal/<project>/00-assess.md for risk, jurisdiction, and data practice context
- Read any existing accessibility audit or review artifacts in .metapowers/legal/<project>/ for additional context
Identify applicable accessibility laws by jurisdiction:
- United States:
  - ADA Title III — public accommodations, DOJ web accessibility guidance, case law trends
  - Section 508 (Rehabilitation Act) — federal agencies and recipients of federal funding
  - State laws (California Unruh Act, New York accessibility requirements, etc.)
- European Union:
  - European Accessibility Act (EAA) — effective June 2025, products and services requirements
  - Web Accessibility Directive — public sector websites and mobile apps
  - EN 301 549 standard
- United Kingdom:
  - Equality Act 2010 — reasonable adjustments obligation
  - Public Sector Bodies Accessibility Regulations 2018
- Canada:
  - Accessibility for Ontarians with Disabilities Act (AODA) — WCAG 2.0 AA for Ontario
  - Accessible Canada Act (ACA) — federal regulated organizations
- Other applicable jurisdictions — document requirements based on assessment context

Read the full file on GitHub · 107 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

3d ago First seen · 107 lines · 90 tokens per session scan A 865f501cc1d7

Subscribe to this mod's changes

accessibility-compliance is a skill published in the GitHub repository bromso/metapowers (2 stars, last pushed 2d ago), licensed MIT. It adds 90 tokens to every session and 1,397 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-21.

CSS and styling Claude Code Frontend Legal and compliance claude-agent claude-code-plugin claude-skills context-design context-engineering

laravel-blade

Create Blade templates with components, slots, layouts, and directives. Use when building views, reusable components, or templating.

fusengine/agents · 30 tokens

design-motion

Use when adding or reviewing motion on an already-settled layout or component — never to hide or compensate for an unfinished one.

fusengine/agents · 29 tokens

nextjs-shadcn

Use when building UI components in Next.js App Router with shadcn/ui — forms, dialogs, tables, toasts, accessible components.

fusengine/agents · 34 tokens

astro-styling

Use when styling Astro components — scoped CSS, CSS Modules, Tailwind CSS, UnoCSS, Sass, the class:list directive, or global styles.

fusengine/agents · 35 tokens

react-shadcn

Builds UI components for a React SPA (Vite) with shadcn/ui (CLI 4.21.0) and Tailwind CSS v4 on whichever component base the project uses — Base UI (default for new projects since July 2026), Radix UI (unified radix-ui package, fully supported) or React Aria (added July 2026): forms (Field/FieldLabel/FieldError pattern…