skills.rest
hjemmesidekongen
hjemmesidekongenCOMMUNITY
Explore all skills by this author →
GitHub

accessibility-wcag

Validate web content against WCAG 2.1 AA accessibility standards.

1|Updated Mar 1, 2026
Search Tags:#accessibility#a11y#screen reader#keyboard navigation#compliance#wcag#aria
One-click install
npx skills add https://github.com/hjemmesidekongen/ai --skill accessibility-wcag-hjemmesidekongen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility-wcag
Source: https://github.com/hjemmesidekongen/ai/tree/main/plugins/smedjen/skills/accessibility-wcag
Command: npx skills add https://github.com/hjemmesidekongen/ai --skill accessibility-wcag-hjemmesidekongen

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the critical need to make digital content accessible to all users, preventing discrimination and ensuring compliance with legal standards by identifying and rectifying accessibility barriers.

Core Features & Use Cases

  • WCAG 2.1 AA Compliance: Enforces standards for Perceivable, Operable, Understandable, and Robust (POUR) principles.
  • Semantic HTML & ARIA Guidance: Promotes the use of native HTML elements first, with ARIA as a supplement.
  • Practical Testing Workflows: Provides checklists and guidance for keyboard navigation, screen reader testing, and color contrast verification.
  • Use Case: A development team can use this Skill to audit their web application's accessibility, ensuring it meets AA standards before launch, thereby avoiding potential legal issues and expanding their user base.

Quick Start

Run the accessibility-wcag skill to verify that all interactive elements are keyboard-operable and have visible focus indicators.

Frequently Asked Questions about accessibility-wcag

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

FAQPage Schema
How do I ensure my web content meets WCAG 2.1 AA compliance standards?▼

To ensure WCAG 2.1 AA compliance, validate your web content against POUR principles, focusing on semantic HTML, ARIA best practices, keyboard navigation, screen reader compatibility, and color contrast ratios.

What is the best way to test keyboard navigation and screen reader compatibility?▼

The best way to test keyboard navigation and screen reader compatibility is to follow practical testing workflows that verify all interactive elements are keyboard-operable and have visible focus indicators.

When should I use ARIA attributes instead of native HTML elements for accessibility?▼

You should use ARIA attributes as a supplement to native HTML elements, prioritizing semantic HTML first to provide a robust accessibility foundation before adding ARIA for enhanced screen reader support.

How do I audit a web application's accessibility before launch?▼

You can audit a web application's accessibility by applying detailed checklists and testing methodologies to verify color contrast ratios, semantic structure, and operability, ensuring it meets AA standards before launch.

Does WCAG 2.1 AA compliance require visible focus indicators for interactive elements?▼

Yes, WCAG 2.1 AA compliance requires visible focus indicators for all interactive elements to ensure they are fully operable and accessible via keyboard navigation.

Related Skills

Explore More Software Engineering Skills→
8GG-Git8GG-Git

interactive-dashboard-builder

Generate self-contained HTML dashboards with Chart.js and dropdown filters.

Community
Intermediate
Montte-erpMontte-erp
6

wcag-audit-patterns

Audit web pages for WCAG 2.2 violations with automated and manual checks.

Official
Intermediate
leboncoinleboncoin
92

check-accessibility

Automate WCAG 2.1 AA accessibility testing of Spark UI components with Playwright.

Official
Intermediate
dylantarredylantarre
38

color-contrast

Validate color combinations against WCAG 2.1 contrast requirements and generate accessible pairings.

Community
Basic