klytos-accessibility

Enforce WCAG 2.1 AA accessibility conformance on Klytos CMS pages.

12|2|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/joseconti/klytos --skill klytos-accessibility
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: klytos-accessibility
Source: https://github.com/joseconti/klytos/tree/main/.claude/skills/klytos-accessibility
Command: npx skills add https://github.com/joseconti/klytos --skill klytos-accessibility

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

All page content in Klytos CMS must be accessible, ensuring legal compliance and better user experience across assistive technologies.

Core Features & Use Cases

  • Provides WCAG 2.1 AA-compliant best practices for images, headings, tables, forms, and semantics.
  • Guides content authors and developers during page creation, admin UI, and styling to meet accessibility standards.
  • Use case: ensure a new page published meets alt text, keyboard navigation, color contrast, and proper landmark roles.

Quick Start

Assess a new page for accessibility conformance and apply WCAG 2.1 AA guidance to fix issues.

Frequently Asked Questions about klytos-accessibility

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

FAQPage Schema
How do I check if my CMS pages meet WCAG 2.1 AA accessibility standards?

To check WCAG 2.1 AA conformance for CMS pages, assess images, headings, forms, tables, video captions, and color contrast during content creation and rendering. This ensures semantic HTML, descriptive alt text, and keyboard accessibility meet compliance.

What is WCAG 2.1 AA conformance for web content?

WCAG 2.1 AA conformance requires pages to implement semantic HTML, descriptive alt text, keyboard navigation, ARIA best practices, proper landmark roles, and correct color contrast ratios to ensure assistive technology compatibility.

Does this accessibility guidance apply during admin UI design and page rendering?

Yes, WCAG 2.1 AA accessibility guidance applies during content creation, admin UI design, and page rendering, verifying that all page elements from forms to tables meet assistive technology standards.

How do I add descriptive alt text and fix keyboard navigation issues?

To fix keyboard navigation and alt text issues, apply WCAG 2.1 AA best practices during page creation, ensuring all images have descriptive alt text and interactive elements are fully keyboard accessible.

What's the best way to ensure ARIA best practices and language declarations are correct?

The best way to ensure correct ARIA best practices and language declarations is to verify them during page rendering, applying WCAG 2.1 AA standards to enforce proper landmark roles and locale declarations.