メニュー
Use when auditing websites or apps for Canadian accessibility law compliance, checking AODA (Ontario) or Accessible Canada Act (federal) requirements, or advising on CAN/ASC-EN 301 549 obligations.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Run a model through the omni-bench benchmark to MEASURE it — produce a run-artifact and score it, then read the numbers. Use when asked to run, benchmark, measure, evaluate, or "test the results of" a model with omni-bench — ASR (WER/CER, RTFx) or text generation (tok/s, TTFT, prefill tok/s, prompt-cache speedup). Covers the adapter seam (Transcriber/Generator), the prepare→run→score→diff CLI flow, the offline no-download smoke task, and how to interpret each metric. NOT for publishing to a leaderboard (use omni-bench-publish) or changing the framework itself (use omni-bench).
Publish a scored omni-bench result (ASR or text-generation) to a leaderboard platform (e.g. bench.bshk.app) via its write API. Use when asked to publish, upload, submit, or "send a report" for an omni-bench result.json or parity-report.json — sharing ASR WER/RTFx numbers or text-generation TTFT/tok-per-s/prompt-cache numbers. Covers the one modality-agnostic `omni-bench publish` command and the MANDATORY secret handling: the api-key is injected from a secrets manager (1Password `op run` / AgentVault `av run`) at runtime, never read into context, never hardcoded.
Develop the omni-bench benchmark framework (ASR/STT + text generation) built on a producer/scorer split with an open JSON spec as SSOT. Use when working in an omni-bench checkout — changing the JSON schemas, the prepare/producer/scorer/diff pipeline, the adapter seams (Transcriber / Generator), datasets, fixtures, or the Swift producer SDK; or when running and validating benchmark artifacts. Encodes the schema-evolution rules, determinism invariants, commands, and repo gotchas that are easy to get wrong.
Use when generating/managing the offline root signing key or signing & publishing Zamok product keysets from the terminal (the Swift CLI; the ZamokApp GUI is the co-equal interface). Triggers — "generate root key", "rotate root", "publish keyset", "sign keyset", "escrow root key", "zamokctl", "trusted-roots.json", Tish/Zamok license signature setup.
Use when auditing digital products or services for European Accessibility Act (EAA) compliance, checking EN 301 549 conformance, or advising on EU Web Accessibility Directive obligations.
Use when determining which accessibility law applies to an organization, comparing requirements across jurisdictions (US, EU, Canada, Japan), or planning multi-country accessibility compliance strategy.
| name | aoda-compliance |
| description | Use when auditing websites or apps for Canadian accessibility law compliance, checking AODA (Ontario) or Accessible Canada Act (federal) requirements, or advising on CAN/ASC-EN 301 549 obligations. |
Guides compliance with Canadian accessibility laws: the Accessibility for Ontarians with Disabilities Act (AODA) at the provincial level and the Accessible Canada Act (ACA) at the federal level. Covers technical standards, deadlines, reporting, and penalties.
When conducting a Canadian accessibility review:
Determine which law applies:
Identify the technical standard:
Evaluate digital properties against the applicable standard
Check reporting obligations — both laws require periodic accessibility plans and reports
Provide remediation guidance referencing specific WCAG criteria or EN 301 549 clauses
All organizations with 1+ employees in Ontario: private businesses, non-profits, public sector.
WCAG 2.0 Level AA, excluding:
| Obligation | Date |
|---|---|
| Public-facing web content meets WCAG 2.0 AA (50+ employees) | January 1, 2021 |
| All AODA standards fully met | January 1, 2025 |
| Next compliance report (designated public sector) | December 31, 2025 |
| Next compliance report (20+ employees) | December 31, 2026 |
Federally regulated entities: banks, telecom, transportation, broadcasting, federal government, Crown corporations.
CAN/ASC-EN 301 549:2024 — Canada adopted EN 301 549 v3.2.1 as a national standard in May 2024. This is broader than WCAG alone and covers:
| Obligation | Date |
|---|---|
| Federal public sector — new/updated web pages conform to CAN/ASC-EN 301 549 | December 2027 |
| Large/medium private businesses — new/updated web pages conform | December 2028 |
| Mobile apps and digital documents — phased rollout | 2028–2029 |
Administrative monetary penalties (AMPs) classified as "minor" for ICT non-conformance. Focus is on promoting compliance, not punishment.
| AODA | ACA | |
|---|---|---|
| Scope | Ontario only | Federal jurisdiction |
| WCAG version | 2.0 AA | 2.1 AA (via EN 301 549) |
| Beyond web | No | Yes (documents, apps, hardware) |
| Enforcement | Active, fines | AMPs, compliance-focused |
| Physical spaces | Yes (Design of Public Spaces) | No (ICT focus) |
| Reporting | Periodic compliance reports | 3-year plans + annual reports |
Input: "We're a 30-person company in Ontario, what do we need?"
Response approach:
Input: "Our bank needs to comply with Canadian accessibility law"
Response approach:
