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.
npx skills add Dragoon0x/canon --skill canon-accessibilitygit clone --depth 1 https://github.com/Dragoon0x/canonWrote 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.
[](https://agentmods.dev/skills/dragoon0x/canon/canon-accessibility)<a href="https://agentmods.dev/skills/dragoon0x/canon/canon-accessibility"><img src="https://agentmods.dev/badge/skills/dragoon0x/canon/canon-accessibility.svg" alt="Measured on agentmods" height="20"></a>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.00066 | $0.02941 |
| Opus 5 | $0.00033 | $0.01470 |
| Sonnet 5 | $0.00013 | $0.00588 |
| Haiku 4.5 | $0.00007 | $0.00294 |
Grade A, and why
canon-accessibility 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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 294 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CANON · Accessibility
Accessibility is not a layer applied at the end. It is the substrate. Every other design decision either supports it or undermines it. WCAG 2.2 AA is the floor.
The Four POUR Principles
WCAG organizes everything around four principles:
| Principle | Means |
|---|---|
| Perceivable | Information must be presentable in ways users can perceive (text, alt text, captions, contrast) |
| Operable | UI components must be operable by all users (keyboard, time, no seizure triggers) |
| Understandable | Information and operation must be understandable (predictable, error prevention) |
| Robust | Content must work with current and future assistive tech (semantic HTML, valid markup) |
Semantic HTML First, ARIA Second
| Need | Use this | Not this |
|---|---|---|
| Clickable action | <button> |
<div onclick> |
| Navigation to URL | <a href> |
<button> or <div> |
| Form input | <input>, <textarea>, <select> |
custom div with contenteditable |
| Heading | <h1>–<h6> |
<div class="heading"> |
| List | <ul>, <ol>, <li> |
<div> collection |
| Section | <section>, <article>, <nav>, <aside>, <main>, <header>, <footer> |
<div> |
| Table of data | <table>, <thead>, <tbody>, <th scope> |
<div> grid |
The first rule of ARIA: don't use ARIA. If a native element does the job, use it. ARIA is for what HTML can't express.
Required Page Structure
<!DOCTYPE html>
<html lang="en"> <!-- lang is mandatory -->
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>Page-Specific Title</title>
</head>
<body>
<a href="#main" class="sr-only-focusable">Skip to main content</a>
<header>
<nav aria-label="Primary"> ... </nav>
</header>
<main id="main">
<h1>One H1 per page</h1>
...
</main>
<footer> ... </footer>
</body>
</html>
| Element | Why |
|---|---|
lang attribute |
Screen reader pronunciation |
| Skip link | Keyboard users bypass nav |
One <h1> per page |
Document outline |
<main> landmark |
Screen reader jump-to |
<nav aria-label> |
Distinguish multiple navs |
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.
- 8d ago First seen · 294 lines · 66 tokens per session scan A 09e7a06c3e44
canon-accessibility is a skill published in the GitHub repository Dragoon0x/canon (5 stars, last pushed 4mo ago), licensed MIT. It adds 66 tokens to every session and 2,941 once invoked, about $0.0003 per session on Opus 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-08-31.
Other skills, from other repositories
accessibility
Accessibility (a11y) workflow skill. Use this skill when the user needs Audit and improve web accessibility following WCAG 2.1 guidelines. Use when asked to "improve accessibility", "a11y audit", "WCAG compliance", "screen reader support", "keyboard navigation", or "make accessible". Do NOT use for SEO (use seo)…
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…
accessibility-audit
Use when wCAG compliance audit — semantic HTML, ARIA, keyboard navigation, color contrast, and screen reader testing. Use when working with accessibility audit.
token-architecture
Design token architecture — multi-tier token systems, semantic naming, theme switching, CSS custom properties, Tailwind mapping, and Figma variable sync.
figma-generate-library
Generate Figma component library from React/shadcn codebase with Code Connect parity.
figma-sync
Figma sync workflow patterns — bidirectional design-code sync, conflict resolution, incremental updates, multi-file orchestration.