Fundamental Library for Angular is an SAP-maintained Angular component library implementing SAP's design system and wrapping UI5 Web Components. Angular developers use its typed UI components and higher-level composites to build SAP-style web interfaces. Catalogue entries provide skills, agents, instructions, and a rule for working with the library.
Borrowing it
Nothing to install: this file belongs to SAP/fundamental-ngx. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/SAP/fundamental-ngx/main/.claude/skills/a11y-audit/SKILL.mdgit clone --depth 1 https://github.com/SAP/fundamental-ngxWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/sap/fundamental-ngx/a11y-audit)<a href="https://agentmods.dev/skills/sap/fundamental-ngx/a11y-audit"><img src="https://agentmods.dev/badge/skills/sap/fundamental-ngx/a11y-audit/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/sap/fundamental-ngx/a11y-audit"><img src="https://agentmods.dev/badge/skills/sap/fundamental-ngx/a11y-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00015 | $0.00876 |
| Opus 5.5 | $0.00006 | $0.00350 |
| Sonnet 5.5 | $0.00003 | $0.00175 |
| Haiku 4.5 | $0.00002 | $0.00088 |
Grade A, and why
a11y-audit 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 2mo 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.
How it starts
The opening of the file, as written. The whole thing — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Accessibility Audit: $ARGUMENTS
If $ARGUMENTS is empty, ask the user for a component path or folder before proceeding.
Audit the component(s) at $ARGUMENTS for WCAG AA compliance. Check both the component implementation and its documentation examples.
Checklist
1. Semantic HTML
- Interactive elements use native HTML (
<button>,<a>,<input>) — not<div>or<span>with click handlers - Lists use
<ul>/<ol>/<li>— not divs with list styling - Headings use
<h1>-<h6>with correct hierarchy - Tables use
<table>,<thead>,<tbody>,<th>with scope
2. ARIA Attributes
- Custom interactive components have appropriate
roleattribute -
aria-labeloraria-labelledbyon elements without visible text -
aria-expandedon expandable triggers (menus, dropdowns, accordions) -
aria-selectedon selectable items (tabs, list items) -
aria-disabledsynced withdisabledinput -
aria-haspopupon elements that open popups/menus -
aria-liveregions for dynamic content updates - No redundant ARIA (e.g.
role="button"on<button>)
3. Keyboard Navigation
- All interactive elements reachable via Tab
- Tab order follows visual/logical order
- Arrow keys for navigation within composite widgets (menus, tabs, grids)
- Enter/Space activates buttons and links
- Escape closes modals, popups, and dropdowns
- Focus trapped inside modals/dialogs when open
- Focus returns to trigger element when popup/modal closes
- No keyboard traps (user can always Tab out)
4. Focus Management
- Focus indicator visible on all interactive elements (
:focus-visiblestyles) - Focus moves to new content when dynamically added (e.g. dialog opens)
-
tabindex="0"only on elements that need to be in tab order -
tabindex="-1"for programmatically focusable elements not in tab order - No positive
tabindexvalues (breaks natural tab order)
5. Color and Contrast
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.
- 2mo ago First seen · 95 lines · 15 tokens per session scan A 16e88f5dafc8
a11y-audit is a skill published in the GitHub repository SAP/fundamental-ngx (296 stars, last pushed yesterday), licensed Apache-2.0. It adds 15 tokens to every session and 876 once invoked, about $0.0001 per session on Opus 5.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-30.
Other skills, from other repositories
igniteui-angular-figma-to-app
Builds Angular views from Figma designs with Ignite UI for Angular, supporting Indigo.Design kits, third-party kits, and plain frames. Uses Figma, Ignite UI CLI, theming, and Playwright MCP servers. WHEN TO USE: implementing a Figma design or artboard in an Ignite UI Angular project. WHEN NOT TO USE: screenshots or…
igniteui-angular-generate-from-image-design
Implements Angular application views from design images using Ignite UI Angular components. Uses MCP servers (igniteui-cli, igniteui-theming, angular-cli) to discover components, generate themes, and follow best practices. WHEN TO USE: the user provides a design image (screenshot, mockup, wireframe) and wants it built…
angular-best-practices
Official Angular v22 coding best practices — signals, standalone, native control flow, zoneless, host bindings, Signal Forms, inject(), and accessibility (WCAG AA / AXE). Use whenever writing, generating, or reviewing Angular/TypeScript code in this repo.
authoring-patterns
Convert validated playground templates or HTML compositions into reusable pattern files (.examples.ts) in the pattern library. Use this skill whenever the user wants to save, persist, store, or catalog a template, prototype, composition, or playground result as a reusable pattern. Trigger on phrases like "save as…
elements
Use this skill by default for any UI-related work or with NVIDIA Elements (nve-), including creating, editing, reviewing, or debugging HTML, CSS, layout, theming, components, applications, prototypes, Claude Artifacts, Codex Sites pages, and standalone UI artifacts.
audit-accessibility
Unified accessibility auditing workflow across static analysis, runtime testing, ARIA patterns, keyboard navigation, and color contrast. Use this skill whenever the user mentions accessibility, a11y, WCAG, ARIA roles, axe tests, screen readers, focus management, keyboard navigation, color contrast, or wants to audit…