القائمة
Applies WCAG 2.2 AA-aligned accessibility checks to interfaces, forms, dashboards and components. Use when building or reviewing any user-facing UI, content, or agent supervision screen.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when reviewing code before merge to assess correctness, tests, maintainability, security and user impact.
Use when reviewing plans, recommendations, prioritisation, risk registers, retrospectives or agent outputs for judgement distortion from cognitive bias — not for checking whether an argument's premises validly support its conclusion.
Use when evaluating whether premises in plans, ADRs, reviews, security justifications or agent recommendations validly support their conclusions — for logical fallacies, not judgement distortion from cognitive bias.
Use when a coding agent needs robust problem solving, explicit decomposition, alternative-path exploration, program-aided reasoning, ReAct loops, or self-correction.
Use when generated code, plans, tests, prompts or architecture need critique, repair and verification before completion; especially for coding tasks requiring self-review, test-driven repair or quality gates.
Identifies risks, scores likelihood and impact, selects treatment, assigns owners and review cadence. Use when building or updating a risk register, treating agent autonomy risks, or deciding mitigate, transfer, accept or avoid.
| name | accessibility-wcag |
| description | Applies WCAG 2.2 AA-aligned accessibility checks to interfaces, forms, dashboards and components. Use when building or reviewing any user-facing UI, content, or agent supervision screen. |
| aliases | ["accessibility","wcag"] |
Use this skill for any user-facing work: pages, forms, dashboards, tables, modals, navigation, charts, notifications, approval workflows, agent supervision interfaces and design-system components.
Ensure interfaces are perceivable, operable, understandable and robust, with practical alignment to WCAG 2.2 AA expectations.
For WCAG 2.2 AA alignment, explicitly check the newer AA success criteria as well as the long-standing basics:
2.4.11 Focus Not Obscured (Minimum): author-created content must not fully hide the focused component.2.5.7 Dragging Movements: functionality using dragging should also support a single-pointer alternative unless dragging is essential.2.5.8 Target Size (Minimum): pointer targets must meet the minimum target-size expectation or a documented exception.3.3.8 Accessible Authentication (Minimum): authentication should not require a cognitive-function test unless an accessible alternative or assistance mechanism exists.Also check Level A criteria that commonly affect agent and approval UIs:
3.2.6 Consistent Help: help mechanisms (contact, chat, self-help, human contact) appear in the same relative order across pages when present.3.3.7 Redundant Entry: do not require users to re-enter information already provided in the same process unless essential or security-related.Source: W3C WCAG 2.2.
div or span elements where a button or link is appropriate.For product-specific DataOps/MCP examples, load skills_docs/overlays/mas-dataops-mcp-overlay.md.
ux-design-principles — task-centred design before a11y checksui-component-design — accessible component primitivesfrontend-state-and-interaction-design — keyboard and state accessibility