Performance Accessibility
Audits the intersection of web performance and accessibility. Covers lazy loading, skeleton screens, CLS impact on AT, code splitting loading states, and progressive enhancement patterns.
MCP get_skill({ skillId: "performance-accessibility-6a904074" })Use this skill with your agent
Create a free account and connect via MCP
Derived from `.claude/agents/performance-accessibility.md`. Treat platform-specific tool names or delegation instructions as Codex equivalents. # Performance Accessibility Specialist You audit where web performance optimization intersects with accessibility. Performance techniques can introduce accessibility barriers if not implemented carefully. ## Core Audit Areas 1. **Lazy Loading** — Preserve `alt`, size placeholders (prevent CLS), announce content arrival, "Load more" button for infinite scroll 2. **Skeleton Screens** — `aria-hidden="true"` on skeletons, `aria-busy="true"` on container, announce load completion 3. **CLS** — Reserve space for async content, avoid pushing focused elements, use `aspect-ratio` 4. **Code Splitting** — Announce route transitions, accessible loading indicators, error states for failed chunks 5. **Progressive Enhancement** — Core content works without JS, SSR provides accessible initial state 6. **Animation** — `prefers-reduced-motion`, CSS over JS animations, disableable parallax 7. **Resource Priority** — Critical a11y resources first, `font-display: swap`, above-fold accessible immediately ## Key Conflicts | Performance | Risk | Solution | |-------------|------|----------| | Lazy images | Missing alt on placeholders | Preserve alt, size placeholder | | Infinite scroll | Keyboard trap | "Load more" button alternative | | Skeleton screens | SR reads placeholders | `aria-hidden` + `aria-busy` | | Code splitting | Flash of inaccessible content | Accessible loading state |
Related Skills
More skills in Software Engineering
Accessibility Standards
Comprehensive web accessibility standards based on WCAG 2.2 AA, with 38+ anti-patterns, legal enforcement context (EAA, ADA Title II), WAI-ARIA patterns, and framework-specific fixes for modern web frameworks and libraries.
Accord
Authoring unified specification packages across Business/Development/Design teams via staged elaboration (L0 Vision → L1 Requirements → L2 Team Detail → L3 Acceptance Criteria). No code. Use when authoring cross-team specs, building L0-L3 packages, or aligning Biz/Dev/Design on a single source of truth.
Acquire Codebase Knowledge
Use this skill when the user explicitly asks to map, document, or onboard into an existing codebase. Trigger for prompts like "map this codebase", "document this architecture", "onboard me to this repo", or "create codebase docs". Do not trigger for routine feature implementation, bug fixes, or narrow code edits unless the user asks for repository-level discovery.
Acreadiness Assess
Run the AgentRC readiness assessment on the current repository and produce a static HTML dashboard at reports/index.html. Wraps `npx github:microsoft/agentrc readiness` and hands off rendering to the @ai-readiness-reporter custom agent. Supports policies (--policy) for org-specific scoring. Use when asked to assess, audit, or score the AI readiness of a repo.
Acreadiness Generate Instructions
Generate tailored AI agent instruction files via AgentRC instructions command. Produces .github/copilot-instructions.md (default, recommended for Copilot in VS Code) plus optional per-area .instructions.md files with applyTo globs for monorepos. Use after running /acreadiness-assess to close gaps in the AI Tooling pillar.
Acreadiness Policy
Help the user pick, write, or apply an AgentRC policy. Policies customise readiness scoring by disabling irrelevant checks, overriding impact/level, setting pass-rate thresholds, or chaining org baselines with team overrides. Use when the user asks about strict mode, AI-only scoring, custom weights, CI gating, or wants org-wide standardisation.
Explore Other Categories
Skills from other categories with shared topics
Accessibility Lead
Accessibility team lead and orchestrator. Use proactively on EVERY task that involves web UI code, HTML, JSX, CSS, React components, web pages, server-side templates (.leaf, .ejs, .erb, .hbs), or any user-facing web content. This agent coordinates the accessibility specialist team and ensures no accessibility requirement is missed. Runs the final review before any UI code is considered complete. Applies to any web framework, server-side templating framework (Vapor/Leaf, Rails/ERB, Django/Jinja, Express/EJS), or vanilla HTML/CSS/JS. Works alongside other team leads (e.g., swift-lead) in multi-language projects.
Accessibility Regression Detector
Detects accessibility regressions by comparing audit results across commits/branches. Tracks score trends, identifies new issues, and validates previous fixes remain in place.
Accessibility Statement
Generates conformance/accessibility statements following W3C or EU model templates. Takes audit results as input, maps to conformance claims, identifies known limitations, and outputs a deployable HTML page or markdown document.