block-accessibility

Audit AEM Edge Delivery Services block markup for WCAG 2.1 AA accessibility failures.

Updated May 14, 2026

Search Tags:#accessibility #keyboard navigation #wcag #focus management #aria #eds blocks

Ready to run

npx skills add https://github.com/Focus-GTS/eds-content-ops-skills --skill block-accessibility

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: block-accessibility
Source: https://github.com/Focus-GTS/eds-content-ops-skills/tree/main/skills/block-accessibility
Command: npx skills add https://github.com/Focus-GTS/eds-content-ops-skills --skill block-accessibility

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It identifies accessibility failures caused by AEM Edge Delivery Services (EDS) block DOM transformations, then maps them to concrete ARIA, keyboard, and focus-management issues that break WCAG 2.1 AA compliance.

Core Features & Use Cases

Deep block-pattern auditing: Inspects rendered DOM to verify semantic HTML, correct ARIA roles/properties, and block-specific interaction patterns for common EDS block types.
Keyboard & focus verification: Checks tab order, keyboard controls, focus trapping, and focus return behavior for interactive blocks like tabs, accordion, carousel, and modal/dialog patterns.
Per-block fix reporting: Produces per-block reports with WCAG-referenced findings and code-level remediation guidance for both decorate() behavior and authored content gaps.

Quick Start

Use the block-accessibility skill to audit a published page’s rendered blocks for WCAG 2.1 AA issues and generate per-block remediation reports.

Frequently Asked Questions about block-accessibility

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I fix WCAG 2.1 AA accessibility issues in AEM Edge Delivery Services blocks?▼

Fix WCAG 2.1 AA accessibility issues in AEM Edge Delivery Services blocks by auditing the rendered DOM for semantic HTML, ARIA roles, and keyboard navigation failures, then applying code-level remediation to the decorate function and authored content.

Why does table-to-DOM transformation break keyboard navigation and focus management in EDS blocks?▼

Table-to-DOM transformation breaks keyboard navigation and focus management because the semantic structure changes, requiring ARIA roles and focus trapping patterns to restore interactive behavior for blocks like tabs, accordions, and modals.

How do I audit ARIA roles and focus trapping in interactive EDS blocks?▼

Audit ARIA roles and focus trapping in interactive EDS blocks by inspecting the rendered DOM to verify tab order, keyboard controls, and focus return behavior, generating per-block reports with WCAG-referenced remediation guidance.

Does block-accessibility work with common interactive block patterns like carousels and dialogs?▼

Yes, block-accessibility works with common interactive block patterns like carousels and dialogs by checking block-specific interaction patterns, verifying screen-reader compatibility, and mapping decoration issues to concrete WCAG failures.

What is the best way to generate per-block fix reports for EDS accessibility gaps?▼

The best way to generate per-block fix reports for EDS accessibility gaps is to analyze how DOM transformation affects semantic structure, producing WCAG-referenced findings with specific code-level remediation for both decorate behavior and content gaps.