skills.rest
alexander-kastil
alexander-kastilCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

angular-a11y

Design Angular components conforming to WCAG 2.2 Level AA accessibility standards.

Updated Mar 5, 2026
Search Tags:#accessibility#a11y#angular#wcag#focus#keyboard#landmarks
One-click install
npx skills add https://github.com/alexander-kastil/advanced-angular-agentic-swe --skill angular-a11y
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: angular-a11y
Source: https://github.com/alexander-kastil/advanced-angular-agentic-swe/tree/main/.github/skills/angular-a11y
Command: npx skills add https://github.com/alexander-kastil/advanced-angular-agentic-swe --skill angular-a11y

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures Angular applications meet WCAG 2.2 Level AA accessibility standards by providing structured guidance on component architecture, keyboard navigation, focus management, color contrast, and inclusive UI patterns. It helps teams avoid accessibility gaps during UI development and reviews.

Core Features & Use Cases

  • Conforms Angular components and patterns to WCAG 2.2 AA.
  • Encourages using existing UI libraries and native semantics rather than recreating components with ARIA.
  • Guides correct naming, roles, values, keyboard operation, visible focus, and meaningful semantic structure.
  • Use Case: audit an Angular app, refactor components for accessible labels, landmarks, skip links, and responsive behavior.

Quick Start

Follow the guidelines to audit and refactor an Angular project to enforce WCAG 2.2 AA accessibility throughout the UI.

Frequently Asked Questions about angular-a11y

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

FAQPage Schema
How do I make Angular components WCAG 2.2 AA compliant?▼

Make Angular components WCAG 2.2 AA compliant by applying native semantics, correct ARIA roles, visible focus management, and keyboard navigation rules to your UI patterns. This ensures inclusive interfaces and proper semantic structure.

What is the best way to manage focus in Angular composite widgets?▼

The best way to manage focus in Angular composite widgets is implementing roving tabindex or aria-activedescendant. This ensures proper keyboard operation and visible focus alignment with WCAG 2.2 AA accessibility standards.

How do I add accessible landmarks and skip links in Angular?▼

Add accessible landmarks and skip links in Angular by structuring your responsive UI with correct semantic naming and meaningful HTML5 regions. This guides screen readers efficiently and satisfies WCAG 2.2 AA structural requirements.

Should I use ARIA or native Angular UI libraries for accessibility?▼

You should use existing native Angular UI libraries and native semantics rather than recreating components with ARIA. This approach ensures correct naming, roles, values, and keyboard operation without introducing accessibility gaps.

How do I audit an Angular application for accessibility gaps?▼

Audit an Angular application for accessibility gaps by reviewing component architecture, color contrast ratios, keyboard navigation, and inclusive language. Refactoring components to enforce WCAG 2.2 AA standards resolves identified high-contrast and structural issues.

Does Angular accessibility require high-contrast considerations for UI patterns?▼

Angular accessibility requires high-contrast considerations for UI patterns to meet WCAG 2.2 AA standards. Evaluating color contrast ratios alongside responsive structure ensures interfaces remain readable and inclusive for all users.

Related Skills

Explore More Software Engineering Skills→
tsuji-tomonoritsuji-tomonori

a11y-semantic-html

Correct HTML semantics, ARIA attributes, and accessible names to meet WCAG 2.2 AA.

Community
Intermediate
matteocervellimatteocervelli
25

accessibility-checker

Identify and report WCAG 2.1 Level AA accessibility violations on web pages.

Community
Advanced
imkdwimkdw
1

Frontend Accessibility

Implement accessible React components with ARIA, keyboard navigation, and WCAG compliance.

Community
Intermediate
JansenAnalyticsJansenAnalytics
5

a11y-audit

Audit web content for WCAG accessibility issues and generate remediation reports.

Community
Intermediate