angular-a11y

A guide for making Angular applications easier to use with keyboards and screen readers. Angular is a framework for building web applications, while WCAG 2.2 AA is a widely used accessibility standard.

In plain words
What is it for?
Applying semantic HTML, appropriate ARIA, focus management, keyboard navigation, skip links, colour-contrast checks, and screen-reader announcements in Angular apps.
Why use it?
It helps find and prevent accessibility problems such as missing keyboard controls, poor focus handling, weak colour contrast, and unclear screen-reader announcements.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/agenticpawan/fullstack-pilot/angular-a11y
Any agent
npx skills add AgenticPawan/FullStack-Pilot --skill angular-a11y
Clone the repo
git clone --depth 1 https://github.com/AgenticPawan/FullStack-Pilot

Made for: Claude Code, Codex.

Per session 67 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,118 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00067 $0.02118
Opus 5 $0.00034 $0.01059
Sonnet 5 $0.00013 $0.00424
Haiku 4.5 $0.00007 $0.00212

Measured 2d ago against content hash 02e8320763b8, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

angular-a11y scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/pilot-angular/skills/angular-a11y/SKILL.md · 291 lines

How it starts

The opening of the file, as written. The whole thing — 291 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Principle 1 — Semantic HTML first, ARIA second

Use native elements before ARIA. A <button> is always better than <div role="button">.

BAD — div masquerading as a button

<!-- Missing: keyboard access, focus, role, state — must add all manually -->
<div class="btn" (click)="save()">Save</div>

GOOD — native element

<button type="button" (click)="save()">Save</button>

BAD — redundant ARIA on semantic elements

<nav role="navigation">…</nav>   <!-- <nav> already has the role -->
<main role="main">…</main>       <!-- <main> already has the role -->

GOOD — let semantics do the work

<nav aria-label="Main navigation">…</nav>
<main>…</main>

Principle 2 — ARIA only when no semantic element exists

BAD — custom tab panel without ARIA

<div class="tab" (click)="select(0)">Tab 1</div>
<div class="panel">Content 1</div>

GOOD — ARIA roles with keyboard bindings [AA]

<div role="tablist" aria-label="Settings sections">
  <button role="tab"
          [attr.aria-selected]="selectedTab() === 0"
          [attr.aria-controls]="'panel-0'"
          (keydown)="onTabKey($event)">
    Tab 1
  </button>
</div>
<div role="tabpanel"
     id="panel-0"
     [attr.aria-labelledby]="'tab-0'"
     [hidden]="selectedTab() !== 0">
  Content 1
</div>

Focus management on route change [AA]

Without management, focus resets to <body> after navigation — disorienting for keyboard and screen reader users.

GOOD — focus main heading on NavigationEnd (Angular 17+)

@Component({ selector: 'app-root', ... })
export class AppComponent {
  private router  = inject(Router);
  private mainRef = viewChild<ElementRef>('mainContent');

  constructor() {
    this.router.events.pipe(
      filter(e => e instanceof NavigationEnd),
      takeUntilDestroyed()
    ).subscribe(() => {
      // Move focus to the main content heading, not the page top
      this.mainRef()?.nativeElement.focus();
    });
  }
}

Read the full file on GitHub · 291 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 291 lines · 67 tokens per session scan A 02e8320763b8

Subscribe to this mod's changes

angular-a11y is a skill published in the GitHub repository AgenticPawan/FullStack-Pilot (2 stars, last pushed 1mo ago), licensed MIT. It adds 67 tokens to every session and 2,118 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

spartan

Manages spartan/ui, the Angular UI library - adding, composing, fixing, debugging, and styling UI with the Brain (headless primitives) and Helm (styled) layers. Provides project context, component APIs, and usage examples. Applies when working with spartan/ui, @spartan-ng/brain, @spartan-ng/helm, the @spartan-ng/cli…

spartan-ng/spartan · 115 tokens

design-everyday-things

Apply foundational design principles: affordances, signifiers, constraints, feedback, and conceptual models. Use when the user mentions "why is this confusing", "affordance", "error prevention", "discoverability", "human-centered design", "mental model", "mapping", "seven stages of action", "users keep making…

wondelai/skills · 132 tokens

design-sprint

Run a structured 5-day process to prototype, test, and validate product ideas with real users. Use when the user mentions "design sprint", "validate before we build", "rapid prototype", "test with users", or "should we build this". Also trigger when a team is stuck in endless debate over a high-stakes product…

wondelai/skills · 137 tokens

create-website

Guided journey from a blank page to a live, high-converting website, built message-first, then design, then conversion. Orchestrates ten skills phase by phase - one-page-marketing, storybrand-messaging, made-to-stick, top-design, web-typography, refactoring-ui, ux-heuristics, cro-methodology, scorecard-marketing…

wondelai/skills · 228 tokens

improve-app

Guided journey from a shipped app that works but feels rough to a product that fits the job, flows without friction, reads clearly, and persuades honestly. Orchestrates nine skills phase by phase - jobs-to-be-done, ux-heuristics, design-everyday-things, refactoring-ui, microinteractions, made-to-stick…

wondelai/skills · 236 tokens

influence-psychology

Apply the seven principles of ethical persuasion (reciprocity, commitment, social proof, authority, liking, scarcity, unity) to product design, copy, and sales. Use when the user mentions "social proof", "persuasive copy", "why users dont convert", "ethical persuasion", "reciprocity", "scarcity tactics", "commitment…

wondelai/skills · 156 tokens