Accessibility Audit: WCAG Compliance & Inclusive Design Assessment

Generic, brand-neutral engineering capability; deep, sourced playbooks live in references/ and knowledge/. [DOC]

Generic, brand-neutral engineering capability; sourced playbooks in references//knowledge/. [DOC]

TL;DR

Accessibility audit evaluates digital products against WCAG 2.1/2.2 standards and inclusive design principles. The skill produces accessibility scorecards, violation inventories, and remediation roadmaps that ensure digital experiences are usable by people with diverse abilities [EXPLICIT]

When to use

• Use for the accessibility audit capability. [EXPLICIT]
• NOT for adjacent domains — route to the matching skill. [INFERENCE]

Sub-capabilities (resource map)

Deep, evidence-tagged playbooks — open the one the task needs (ICM Layer 3, on-demand). [INFERENCE]

Procedure

1. Resolve the sub-capability; open the matching references/ playbook. [EXPLICIT]
2. Apply its decision tables; pick the strategy explicitly. [EXPLICIT]
3. Validate against the Quality Criteria and tag every claim. [EXPLICIT]

Quality Criteria

• Sub-capability resolved to one playbook. [INFERENCE]
• Claims evidence-tagged. [EXPLICIT]

Contract

• Aceptación: capability resolved to its reference playbook, applied, validated, evidence-tagged. [EXPLICIT]
• Límites: · Automated tools detect only 30-40% of accessibility issues — manual testing is essential · Full WCAG AAA conformance is aspirational; AA is the standard legal/regulatory target -. [EXPLICIT]
• Casos borde: 1. Aplicacion legacy sin semantica HTML — Cuando el producto usa tablas para layout o divs sin roles ARIA, el skill genera un inventario de deuda semantica y prioriza remediaci. [EXPLICIT]
• Supuestos: · Automated tools detect only 30-40% of accessibility issues — manual testing is essential · Full WCAG AAA conformance is aspirational; AA is the standard legal/regulatory target -. [SUPUESTO]
• Trade-off: 1. Auditoria automatizada + manual vs. solo automatizada — Se requiere ambas porque las herramientas automaticas detectan solo 30-40% de issues; el costo adicional de testing m. [EXPLICIT]

Packet

Capas del packet, cargables bajo demanda (disciplina ICM: una capa por vez, nunca todas juntas): references/ guías de profundidad (cargar UNA por etapa) · knowledge/ cuerpo de conocimiento · prompts/ prompts listos · examples/ salida de ejemplo · agents/ subagentes del packet · assets/ recursos estáticos.