メニュー
Use when auditing websites for Japanese accessibility compliance, checking JIS X 8341-3 conformance, or advising on Japan's Act for Eliminating Discrimination against Persons with Disabilities.
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 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.
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.
| name | jis-accessibility |
| description | Use when auditing websites for Japanese accessibility compliance, checking JIS X 8341-3 conformance, or advising on Japan's Act for Eliminating Discrimination against Persons with Disabilities. |
Guides compliance with Japan's web accessibility standard JIS X 8341-3:2016 and the legal framework under the Act for Eliminating Discrimination against Persons with Disabilities. JIS X 8341-3:2016 is identical to ISO/IEC 40500:2012 (WCAG 2.0).
When conducting a Japanese accessibility review:
Determine organization type:
Evaluate against JIS X 8341-3:2016 (= WCAG 2.0 Level AA)
Note that WCAG 2.1/2.2 are not yet incorporated — JIS update depends on ISO/IEC 40500 revision
Provide remediation guidance using WCAG 2.0 success criteria
Recommend targeting WCAG 2.1 AA as practical future-proofing
The Ministry of Internal Affairs and Communications (MIC) publishes "Everyone's Public Website Operational Guidelines (2016)" recommending JIS X 8341-3:2016 Level AA for public sector websites.
Japan's Digital Agency maintains the "Web Accessibility Introduction Guidebook" with practical implementation guidance.
| Aspect | Detail |
|---|---|
| Standard | JIS X 8341-3:2016 |
| Equivalent to | ISO/IEC 40500:2012 = WCAG 2.0 |
| Target level | Level AA |
| Update cycle | Every 5 years (dependent on ISO/IEC 40500 update) |
| Expected update | WCAG 2.2 incorporation pending ISO update |
JIS X 8341-3:2016 does not include criteria added in WCAG 2.1 or 2.2:
| Sector | Obligation | Standard |
|---|---|---|
| Public sector | Strongly recommended (MIC guidelines) | JIS X 8341-3:2016 AA |
| Private sector | Reasonable accommodation required (2024) | No specific technical standard mandated |
Compliance with JIS X 8341-3 itself is voluntary — there is no direct mandate requiring conformance to a specific WCAG level. However, failure to provide reasonable accommodations for digital access may violate the discrimination law.
Input: "Our prefecture website needs accessibility review"
Response approach:
Input: "Our online store operates in Japan, what accessibility rules apply?"
Response approach:
