القائمة
Accessibility lens (WCAG) over a UI feature's changed code — read-only. Appended to review-and-simplify's lens registry by the ui-review pack. Also usable standalone.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Ingest a raw source into the project's OKF knowledge bundle — distill it into concept pages, refresh the index, and log the change. keel's compounding "LLM wiki" loop.
Use when implementation is complete, gates pass, and you need to decide how to integrate the work — presents structured options (merge, PR, keep, discard) and handles the chosen workflow, including worktree cleanup. Closes the SDD cycle after review-and-simplify.
Use when executing implementation plans with independent tasks in the current session
Orchestrates the implement-feature, evaluator, fix-runner loop for the active feature until all Criterios de Aceitacao are met and quality gates are green.
Use after the plan is approved to break the active feature's plan into a concrete task checklist, written into specs/<feature>/tasks.md from the tasks template.
Use while implementing a feature that has retries, queues, background jobs, external calls, or any critical path an on-call engineer will need to reason about in production. Invoke when adding a new endpoint, dependency, or async flow, and before considering such a feature done — instrumentation is developed alongside the code, like tests, not bolted on after.
| name | a11y-review |
| description | Accessibility lens (WCAG) over a UI feature's changed code — read-only. Appended to review-and-simplify's lens registry by the ui-review pack. Also usable standalone. |
When: dispatched by review-and-simplify as one of its parallel lenses, on the feature's diff, in projects where the ui-review pack is installed. Also usable standalone for a focused accessibility pass.
Scope: the changed UI code only — the feature's tree-snapshot diff (git diff BASE_TREE HEAD_TREE, per subagent-driven-development's no-commit-rule snapshotting) or, if no snapshots exist, the working tree diff. Never the whole repo. If the diff touches no UI surface (markup, components, styles, templates), report "no a11y-relevant changes" and stop — do not manufacture findings.
Output: findings by severity (Critical/Important/Minor) with file:line, reported inline. Makes NO edits.
Judge against WCAG 2.2 Level AA. Flag only what the changed code actually introduces or regresses — not pre-existing debt in untouched code.
alt, aria-label); meaningful color as the only signal; contrast below AA on new text/controls; media without captions.div/span) used as buttons/links without role + keyboard handlers; wrong or missing ARIA (invented roles, aria-* on elements that don't support them); state not exposed (aria-expanded, aria-checked, aria-invalid).Native mobile (iOS/Android) equivalents count too: missing accessibility labels/traits, focus order, and Dynamic Type / large-text support on changed screens.
Prefer a real barrier over a lint-style nit: a div onClick with no keyboard path is Critical; a slightly terse alt is Minor. Do not restate what a deterministic linter (eslint-plugin-jsx-a11y, etc.) already gate-blocks — this lens is for the judgment a linter can't encode (is the label meaningful? is focus order sensible?).
Next: findings return to review-and-simplify, which aggregates them with the other lenses; Critical/Important must be fixed before the pre-commit gate.