accessibility-agents: Skill for Gemini CLI

.gemini/extensions/a11y-agents/skills/legal-compliance-mapping/SKILL.md

legal-compliance-mapping is a skill for Gemini CLI from Community-Access/accessibility-agents. It costs 0 tokens per session (1,191 once invoked), scanned A, original, MIT.

A mapping of accessibility review results to legal and accessibility frameworks, including Section 508, the ADA, EN 301 549, the European Accessibility Act, and AODA. It also supports VPAT 2.5 conformance tables, which document how a product meets accessibility criteria.

In plain words
What is it for?
Use it to prepare compliance comparisons, accessibility conformance reports, and VPAT tables for websites, software, or digital services.
Why use it?
It translates technical accessibility findings into the requirements used by different countries, governments, and regulated organizations.

Skill for Gemini CLI

Written for Gemini CLI: installed under .gemini/.

This is Community-Access/accessibility-agents's own configuration. It tells Gemini CLI how to work on accessibility-agents itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything accessibility-agents configures →

Reuse

Borrowing it

Nothing to install: this file belongs to Community-Access/accessibility-agents. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/Community-Access/accessibility-agents/main/.gemini/extensions/a11y-agents/skills/legal-compliance-mapping/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/Community-Access/accessibility-agents

Made for: Gemini CLI.

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.

agentmods badge for legal-compliance-mapping

README.md
[![agentmods](https://agentmods.dev/badge/skills/community-access/accessibility-agents/legal-compliance-mapping/github.svg)](https://agentmods.dev/skills/community-access/accessibility-agents/legal-compliance-mapping)
Your own site
<a href="https://agentmods.dev/skills/community-access/accessibility-agents/legal-compliance-mapping"><img src="https://agentmods.dev/badge/skills/community-access/accessibility-agents/legal-compliance-mapping/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.

agentmods 80×15 button for legal-compliance-mapping

Your own site · 80×15
<a href="https://agentmods.dev/skills/community-access/accessibility-agents/legal-compliance-mapping"><img src="https://agentmods.dev/badge/skills/community-access/accessibility-agents/legal-compliance-mapping.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,191 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. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 1 finding, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Agent Snooping · line 5
    Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.
    Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
How audits are shown
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.01191
Opus 5 $0.00000 $0.00596
Sonnet 5 $0.00000 $0.00238
Haiku 4.5 $0.00000 $0.00119

Measured 11d ago against content hash 343099ac6bf5, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

legal-compliance-mapping 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 11d 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.

.gemini/extensions/a11y-agents/skills/legal-compliance-mapping/SKILL.md · 98 lines

How it starts

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

Maps accessibility legal frameworks across jurisdictions. Used by compliance-mapping agent and any agent generating compliance reports.


Framework Comparison

Framework Jurisdiction WCAG Version Scope Enforcement
Section 508 (Revised) US (Federal) WCAG 2.0 AA Federal agencies and their ICT Administrative complaints, lawsuits
ADA Title II US (State/Local) WCAG 2.1 AA (DOJ 2024 rule) State and local government websites DOJ enforcement, lawsuits
ADA Title III US (Private) No explicit WCAG version; courts use 2.0/2.1 AA Public accommodations Private lawsuits, DOJ enforcement
EN 301 549 v3.2.1 EU WCAG 2.1 AA (Chapter 9-11) Public sector + private sector ICT EU member state enforcement
European Accessibility Act (EAA) EU WCAG 2.1 AA (via EN 301 549) Private sector products and services (June 2025) Market surveillance, fines
AODA Ontario, Canada WCAG 2.0 AA Ontario organizations (50+ employees) Administrative penalties
Accessible Canada Act Canada (Federal) WCAG 2.1 AA (guidance) Federally regulated entities CRTC/CTA enforcement, penalties
Israeli Standard 5568 Israel WCAG 2.0 AA Public websites and apps Civil lawsuits
JIS X 8341-3:2016 Japan WCAG 2.0 AA Government websites (recommended) No enforcement (voluntary)
Chinese GB/T 37668-2019 China Based on WCAG 2.0 Government websites Administrative guidance

Additional Non-WCAG Requirements

Some frameworks require more than WCAG conformance:

EN 301 549 Additional Requirements

Chapter Requirement Beyond WCAG
Chapter 5 Closed functionality (kiosks, ATMs) Yes — no WCAG equivalent
Chapter 6 Real-time text (RTT) communication Yes — no WCAG equivalent
Chapter 7 Video capabilities (captions, audio description) Extends WCAG 1.2
Chapter 8 Hardware accessibility Yes — physical product requirements
Chapter 10 Non-web documents Maps WCAG to document formats
Chapter 11 Non-web software Maps WCAG to native applications
Chapter 12 Documentation and support services Accessible help documentation
Chapter 13 ICT providing relay or emergency services Yes — no WCAG equivalent

Read the full file on GitHub · 98 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.

  1. 11d ago First seen · 98 lines · 0 tokens per session scan A 343099ac6bf5

Subscribe to this mod's changes

legal-compliance-mapping is a skill published in the GitHub repository Community-Access/accessibility-agents (405 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,191 tokens. 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-08-30.

Related

Other skills, from other repositories

accessibility-commerce

Make your store usable by everyone with WCAG 2.1 AA compliance — screen reader support, keyboard navigation, and accessible cart and checkout flows.

finsilabs/awesome-ecommerce-skills · 33 tokens

accessibility

Accessibility patterns for WCAG 2.2 compliance, keyboard focus management, React Aria component patterns, cognitive inclusion, native HTML-first philosophy, and user preference honoring. Use when implementing screen reader support, keyboard navigation, ARIA patterns, focus traps, accessible component libraries…

yonatangross/orchestkit · 65 tokens

Accessibility Auditor

Comprehensive WCAG 2.1 AA compliance testing combining automated axe-core scans with manual keyboard navigation, screen reader compatibility, and focus management verification.

PramodDutta/qaskills · 32 tokens

Accessibility A11y Enhanced

Comprehensive WCAG compliance and accessibility testing covering ARIA, keyboard navigation, screen readers, color contrast, and automated a11y validation.

PramodDutta/qaskills · 34 tokens

accessibility

Use when making a web UI conform to WCAG 2.2 Level AA — axe-core or Lighthouse a11y violations, keyboard operability, focus management, ARIA roles/names/live regions, contrast, tap-target size. NOT palette or visual intent (that is design), NOT test-runner setup (that is testing-web), NOT LCP/page-speed (that is…

ericrisco/rsc-harness · 86 tokens

accessibility-expert

Build interfaces usable by everyone: WCAG 2.2 conformance, semantic HTML, ARIA, keyboard navigation, screen readers and accessible forms. Use when the user mentions accessibility, a11y, WCAG, ARIA, screen readers, keyboard navigation, colour contrast, focus management, the European Accessibility Act or Section 508, or…

personamanagmentlayer/pcl · 98 tokens