skills.rest
joe-watkins
joe-watkinsCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

web-standards

Analyze HTML, CSS, and ARIA code for static accessibility issues.

1|Updated Dec 17, 2025
Search Tags:#ARIA#wcag#static-analysis#analyze#semantic-html#landmarks
One-click install
npx skills add https://github.com/joe-watkins/a11y-devkit --skill web-standards
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: web-standards
Source: https://github.com/joe-watkins/a11y-devkit/tree/main/packages/web-standards
Command: npx skills add https://github.com/joe-watkins/a11y-devkit --skill web-standards

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill performs static analysis of HTML, CSS, and ARIA without requiring a browser, identifying semantic HTML issues, ARIA validity problems, landmark gaps, and heading hierarchy concerns early in the development process.

Core Features & Use Cases

  • Static analysis of semantic HTML, ARIA attributes, landmarks, and heading structure to surface accessibility issues in source code.
  • Use in code reviews, CI pipelines, and pre-deployment audits to ensure accessibility compliance before runtime.
  • Ideal for audits of existing codebases to map issues to WCAG criteria via aria-mcp and wcag-mcp integrations.

Quick Start

Analyze a codebase with the web-standards skill to surface static accessibility issues across HTML, CSS, and ARIA.

Frequently Asked Questions about web-standards

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

FAQPage Schema
How do I check ARIA validity and semantic HTML issues in a static codebase?▼

You can check ARIA validity and semantic HTML issues by running static analysis directly on your source code to identify accessibility problems without needing a browser environment.

Can I audit HTML and CSS for WCAG compliance in a CI pipeline?▼

Yes, you can audit HTML and CSS for WCAG compliance in a CI pipeline by integrating static analysis to catch semantic HTML problems, landmark gaps, and heading hierarchy concerns pre-deployment.

What is static ARIA analysis without a browser?▼

Static ARIA analysis without a browser is the process of examining HTML and CSS source code directly to identify ARIA validity issues, semantic gaps, and heading hierarchy concerns before runtime execution.

Does static accessibility analysis detect heading hierarchy and landmark gaps?▼

Yes, static accessibility analysis detects heading hierarchy and landmark gaps by examining the source code structure to ensure semantic HTML and ARIA attributes meet compliance standards.

How do I map ARIA errors to WCAG success criteria during a code review?▼

You can map ARIA errors to WCAG success criteria during a code review by integrating rule validation tools that deliver structured findings linking static accessibility issues to specific compliance requirements.

What are the limitations of static accessibility analysis for ARIA validation?▼

The limitations of static accessibility analysis include not catching runtime DOM modifications or dynamic JavaScript interactions, as it only examines static HTML, CSS, and ARIA source code without browser execution.

Related Skills

Explore More Software Engineering Skills→
WesleySmitsWesleySmits

html-standards

Standardize HTML accessibility and semantic guidelines for WordPress FSE themes.

Community
Intermediate
SAPSAP
294

a11y-audit

Audit UI components for WCAG AA accessibility compliance.

Official
Advanced
gc-da11yngc-da11yn
41

accessibility-rules

Map document accessibility rules to WCAG 2.2 success criteria.

Official
Advanced
pacphipacphi
14

Chrome DevTools

Debug web pages via Chrome DevTools MCP with performance, network, and DOM inspection.

Community
Advanced