accessibility-wcag
Skill2 starsChanged 5 months agoMITView on GitHub
Accesibilidad WCAG 2.2 nivel AA aplicada: semántica HTML, ARIA cuando hace falta, navegación por teclado, foco visible, contraste, textos alternativos, formularios accesibles. Cargá al crear o auditar UI.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- mahdy-gribkov/arcanatheir own version, first seen Nov 8, 2026
- medy-gribkov/arcanatheir own version, first seen Nov 1, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- mahdy-gribkov/arcana★ 1same name
- medy-gribkov/arcana★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository25 other files it gives its agents.
- agent-orchestrationSkill
- backend-api-designSkill
- backend-data-modelingSkill
- backend-observabilitySkill
- backend-performanceSkill
- blossom-carouselSkill
- browser-qaSkill
- commit-hygieneSkill
- discovery-intakeSkill
- frontend-component-patternsSkill
- geo-seoSkill
- gh-cliSkill
- glosario-vivoSkill
- llm-councilSkill
- pedido-claroSkill
- ponytailSkill
- reporte-comprensibleSkill
- sdd-flowSkill
- secure-by-defaultSkill
- security-authn-authzSkill
- security-owaspSkill
- security-secretsSkill
- security-supply-chainSkill
- turtle-protocolSkill
- ui-ux-pro-maxSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 64
No autoplay con sonido. Pausa accesible en cualquier animación >5 s.
- Distinctive: line 75
No usar ARIA si hay HTML nativo equivalente.
- Very specific: line 76
No cambiar la semántica nativa (role="button" en <a> casi nunca).
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Accesibilidad — WCAG 2.2 AA
Cuándo usar
- Cualquier UI con la que interactúe una persona.
- Antes de mergear un PR que toca componentes interactivos.
- Auditoría de una pantalla existente.
Principios POUR
- Perceivable — todo contenido tiene alternativa textual o auditiva.
- Operable — todo se puede usar con teclado, sin tiempo límite duro.
- Understandable — lenguaje claro, errores con instrucción.
- Robust — válido sintácticamente, compatible con asistivas.
Semántica primero
Antes de ARIA, HTML nativo:
| Necesitás | Usá | No uses |
| Botón clickeable | <button> | <div onClick> |
| Link | <a href> | <button> que navega |
| Lista | <ul>/<ol> | <div> con bullets |
| Encabezado | <h1>..<h6> jerárquico | <div class="title"> |
| Formulario | <form> + <label for> | inputs sueltos |
| Tabla de datos | <table> con <th> y scope | grid de <div> |
| Diálogo modal | <dialog> | <div> flotante |
ARIA solo cuando el HTML nativo no alcanza. No ARIA es mejor que ARIA mal.
Teclado
Tabrecorre todo lo interactivo en orden lógico (DOM = visual).Esccierra modales, dropdowns, popovers.Enter/Spaceactivan botones; flechas para menús, tabs, sliders.- Foco visible siempre. Outline ≥2 px, contraste ≥3:1 con el fondo.
- Sin trampas de foco salvo dentro de un modal abierto (y restaurar al cerrar).
Contraste
- Texto normal: 4.5:1 mínimo.
- Texto grande (≥18 pt o ≥14 pt bold): 3:1.
- Componentes UI y bordes de foco: 3:1 contra fondo adyacente.
- Verificá con axe DevTools o WebAIM Contrast Checker.
Imágenes y media
altdescriptivo si la imagen aporta info;alt=""si es decorativa.- Video: subtítulos sincronizados. Audio: transcripción.
- No autoplay con sonido. Pausa accesible en cualquier animación >5 s.
Formularios
<label for>en cada input. No "placeholder como label".- Errores en texto + ícono + color (no solo color).
aria-invalid+aria-describedbyal mensaje. - Agrupá relacionados con
<fieldset>+<legend>. - Autocompletar:
autocomplete="email",autocomplete="given-name", etc.
ARIA — reglas básicas
- No usar ARIA si hay HTML nativo equivalente.
- No cambiar la semántica nativa (
role="button"en<a>casi nunca). - Todo control interactivo debe tener nombre accesible.
aria-hidden="true"nunca en algo que recibe foco.- Usar landmarks:
<header>,<nav>,<main>,<aside>,<footer>.
Validación
axe-core(DevTools o CLI) sin violaciones críticas/serias.- Recorrer la página solo con teclado: ¿llegás a todo? ¿salís de todo?
- Probar con lector de pantalla (NVDA en Windows, VoiceOver en macOS, TalkBack en Android).
- Lighthouse Accessibility ≥95.
Reglas duras
- Nunca
outline: nonesin reemplazo visible. - Nunca
tabindex>0: rompe el orden natural. - Nunca
<div onClick>para algo que se ve como botón o link. - Nunca color como único indicador (rojo = error, verde = ok no alcanza).
Relacionadas
[[ui-ux-pro-max]] · [[frontend-component-patterns]]
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

