Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

Começar

aem-accessibility

Estrelas8

Forks2

Atualizado20 de março de 2026 às 15:57

AEM accessibility review — WCAG 2.1 AA compliance in HTL templates, Coral UI dialogs, and frontend components

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

techforum-repo

techforum-repo/aem-claude-code

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores webInformática e Matemática·SOC 15-1254

SKILL.md

readonly

name	aem-accessibility
description	AEM accessibility review — WCAG 2.1 AA compliance in HTL templates, Coral UI dialogs, and frontend components
allowed-tools	Read, Grep, Glob
argument-hint	[file or component path]

Review $ARGUMENTS for WCAG 2.1 Level AA accessibility issues. Report each finding as Blocking / Warning / Suggestion.

HTL templates

<img> without an alt attribute, or alt hardcoded to a non-descriptive string — Blocking
Interactive elements (<a>, <button>) with no visible text or aria-label — Blocking
Non-semantic <div>/<span> used for interactive behaviour instead of native elements — Blocking
Form inputs without an associated <label> or aria-labelledby — Blocking
Focus ring suppressed (outline: none) with no custom focus indicator replacement — Blocking
Heading levels that skip (e.g. <h2> → <h4>) or chosen for visual weight rather than document structure — Warning
Dynamic content (carousels, tabs, dialogs) with no aria-live or role-based announcement — Warning
Multiple landmark regions of the same type with no distinguishing aria-label — Warning
ARIA roles overriding native semantics when a correct native element exists — Suggestion

Coral UI dialogs (_cq_dialog/.content.xml)

Dialog field with empty or missing fieldLabel — Blocking
Relying solely on placeholder text for authoring guidance instead of fieldDescription — Warning

Frontend / SPA components

Image rendered via React/SPA with alt defaulting silently to empty string — Blocking
Modal dialog with no focus trap or no focus restoration to the trigger on close — Blocking
Tab or accordion with no keyboard navigation (ArrowLeft/ArrowRight, Enter/Space) — Blocking
Custom interactive component with no ARIA role, state, or keyboard operability — Blocking
Information conveyed by colour alone with no accompanying text, icon, or pattern — Warning

Mais deste repositório

mesmo repositório

aem-cloudmanager

techforum-repo/aem-claude-code

Cloud Manager and OakPAL review — package filters, embed order, Dispatcher SDK, deployment safety

2026-03-188

aem-headless

techforum-repo/aem-claude-code

AEM headless review — Content Fragment models, GraphQL persisted queries, CF Java integration, CORS, and Dispatcher rules for headless delivery

2026-03-188

aem-oak-index

techforum-repo/aem-claude-code

Oak index review and creation — index type selection, property coverage, evaluatePathRestrictions, async configuration

2026-03-188

aem-performance

techforum-repo/aem-claude-code

AEM performance review — JCR queries, traversal, resolver lifecycle, PostConstruct overhead

2026-03-188

aem-project-conventions

techforum-repo/aem-claude-code

Always-loaded AEM project conventions — naming patterns, package structure, utility library usage, and team-specific standards that Claude applies silently on every task

2026-03-188

aem-security

techforum-repo/aem-claude-code

AEM security review — admin resolver, query injection, path validation, exposed endpoints, hardcoded secrets

2026-03-188

name	aem-accessibility
description	AEM accessibility review — WCAG 2.1 AA compliance in HTL templates, Coral UI dialogs, and frontend components
allowed-tools	Read, Grep, Glob
argument-hint	[file or component path]

Review $ARGUMENTS for WCAG 2.1 Level AA accessibility issues. Report each finding as Blocking / Warning / Suggestion.

HTL templates

<img> without an alt attribute, or alt hardcoded to a non-descriptive string — Blocking
Interactive elements (<a>, <button>) with no visible text or aria-label — Blocking
Non-semantic <div>/<span> used for interactive behaviour instead of native elements — Blocking
Form inputs without an associated <label> or aria-labelledby — Blocking
Focus ring suppressed (outline: none) with no custom focus indicator replacement — Blocking
Heading levels that skip (e.g. <h2> → <h4>) or chosen for visual weight rather than document structure — Warning
Dynamic content (carousels, tabs, dialogs) with no aria-live or role-based announcement — Warning
Multiple landmark regions of the same type with no distinguishing aria-label — Warning
ARIA roles overriding native semantics when a correct native element exists — Suggestion

Coral UI dialogs (_cq_dialog/.content.xml)

Dialog field with empty or missing fieldLabel — Blocking
Relying solely on placeholder text for authoring guidance instead of fieldDescription — Warning

Frontend / SPA components

Image rendered via React/SPA with alt defaulting silently to empty string — Blocking
Modal dialog with no focus trap or no focus restoration to the trigger on close — Blocking
Tab or accordion with no keyboard navigation (ArrowLeft/ArrowRight, Enter/Space) — Blocking
Custom interactive component with no ARIA role, state, or keyboard operability — Blocking
Information conveyed by colour alone with no accompanying text, icon, or pattern — Warning