accessibility-fix

Identify WCAG 2.1 AA violations on Adobe Edge Delivery Services pages and generate remediation actions.

Updated May 14, 2026
One-click install
npx skills add https://github.com/Focus-GTS/eds-content-ops-skills --skill accessibility-fix-focus-gts
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility-fix
Source: https://github.com/Focus-GTS/eds-content-ops-skills/tree/main/skills/accessibility-fix
Command: npx skills add https://github.com/Focus-GTS/eds-content-ops-skills --skill accessibility-fix-focus-gts

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you find and remediate WCAG 2.1 AA accessibility violations on published Adobe Edge Delivery Services (EDS) pages by producing actionable, location-specific fix instructions.

Core Features & Use Cases

  • WCAG 2.1 AA audit with mapped findings: Checks common accessibility issues including images (alt text), heading structure, link purpose, color contrast, language/title, and EDS-specific patterns.
  • Actionable fixes split by ownership: Separates document-level fixes (Google Docs / Word / da.live) from code-level fixes (block JavaScript, CSS, header/head.html).
  • Block-focused accessibility review: Evaluates common EDS blocks (cards, columns, navigation, carousel, accordion, modal/dialog, tabs) and flags what needs manual validation for interactive behavior.
  • Safety-conscious page fetching: Uses guardrails for fetching only user-provided URLs or directly linked URLs, treating fetched content as untrusted input.

Quick Start

Use the accessibility-fix skill to scan your target EDS page URL and generate a fix report separated into document and code changes.

Frequently Asked Questions about accessibility-fix

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

FAQPage Schema
How do I fix WCAG 2.1 AA accessibility violations on an Adobe Edge Delivery Services page?

To fix WCAG 2.1 AA accessibility violations on an Adobe Edge Delivery Services page, you scan the published URL to identify issues like missing alt text or poor color contrast, then apply specific remediation actions separated into document-level fixes and code-level block updates.

What is the best way to remediate Lighthouse or axe accessibility findings on EDS pages?

Remediating Lighthouse or axe accessibility findings on EDS pages is best handled by generating a structured report that maps each violation to specific fix locations, separating content updates in Google Docs or Word from CSS and JavaScript block code changes.

How do I check color contrast and heading hierarchy in Adobe Edge Delivery Services?

Checking color contrast and heading hierarchy in Adobe Edge Delivery Services involves validating document-level constraints and CSS-level styles against WCAG 2.1 AA standards, producing severity-scoped findings that pinpoint exactly where to adjust block code or source content.

Can I audit EDS blocks like cards and accordions for interactive accessibility behavior?

You can audit common EDS blocks like cards, columns, navigation, carousels, accordions, and tabs for accessibility, which flags specific elements requiring manual validation for interactive behavior compliance alongside automated WCAG 2.1 AA checks.

Does the WCAG AA accessibility audit split fixes by content author and developer ownership?

The WCAG AA accessibility audit splits fixes by ownership, providing document-level remediation actions for content authors using Google Docs or da.live, and code-level fixes for developers modifying block JavaScript, CSS, and header files.

What are the limitations when fetching live EDS pages for an accessibility audit?

When fetching live EDS pages for an accessibility audit, the process operates under safety guardrails by only scanning user-provided URLs or directly linked URLs, treating all fetched content as untrusted input to prevent external data injection.