ValidateHTML: validate HTML, CSS and accessibility

    1

    Makes your agent validate HTML, CSS, JSON, XML and common WCAG failures before it calls front-end work done, then fix spec errors without rewriting valid modern code. Free MCP server or npx CLI, no account.

    Free

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    ValidateHTML: validate HTML, CSS and accessibility

    Example session with this skill installed

    I just built the signup page. Validate signup.html (HTML and accessibility) and theme.css, fix what is wrong, and tell me what is left.

    • Read your context and instructions
    • Compiled the validatehtml
    • Generated the UI component

    I validated both files with ValidateHTML, fixed the errors, and ran the checks again.

    First run

    FileCheckResult
    signup.htmlHTML2 errors, 4 warnings
    signup.htmlAccessibility1 error, 3 warnings
    theme.cssCSS2 errors, 0 warnings

    Errors (spec violations, all fixed):

    • signup.html 5:12 <img> is missing required "alt" attribute (wcag/h37)
    • signup.html 10:34 Duplicate ID "email" (no-dup-id): the password field reused the email field's id
    • theme.css 5:20 Invalid value for display property (flexbox is not a value; changed to flex)
    • theme.css 5:29 Unknown property colr (typo for color)

    Warnings (best practice, fixed because the fix is clearly better):

    • The logo link had no text: moved the image inside it, with alt="Acme home"
    • Both inputs had no <label>: added labels tied with for
    • <button> had no type: set type="submit"

    Your CSS nesting (& h2, &:hover) is valid modern CSS and was not flagged, so I left it as is.

    Second run

    FileCheckResult
    signup.htmlHTMLPassed, 0 errors, 0 warnings
    signup.htmlAccessibilityPassed, 0 errors, 0 warnings
    theme.cssCSSPassed, 0 errors, 0 warnings

    Next steps: no automated accessibility issues remain. That does not make the page fully accessible: keyboard order, focus and whether the alt text is meaningful still need a quick manual pass.

    signup.html

    TSX · React component

    Generated

    Example file from a real run - the skill writes it into your workspace.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Broken markup and invalid stylesheets lead to unpredictable rendering and silent accessibility failures. This skill provides an automated validation layer for your frontend code. It checks every file against the WHATWG and CSS specs and flags common WCAG failures before you commit.

    What it does

    • Multi-format validation checks HTML, CSS, JSON, XML, and SVG files against official specifications.
    • Accessibility auditing identifies common WCAG failures and ARIA role misconfigurations.
    • URL scanning validates live pages or local dev server outputs to catch issues in rendered framework code.
    • Automated reporting distinguishes between spec-breaking errors and best-practice warnings.

    How it works

    1. Validate code by passing snippets directly from the conversation, before writing them to disk.
    2. Scan files by providing a local path to the CLI or MCP tool for a direct file-system check.
    3. Audit URLs by pointing the tool at localhost or a staging environment to validate final rendered output.
    4. Site scanning generates links for comprehensive full-site reports when deep analysis is required.

    Frameworks & tools

    This skill utilizes the validatehtml MCP server or CLI and supports Node 18+. It is designed for projects using HTML5, CSS3, SVG, and data formats like JSON and XML. It is particularly effective for validating the output of Next.js, Astro, or Vue during local development.

    Why this beats prompting it yourself

    LLMs frequently hallucinate spec compliance or suggest outdated attributes. This skill uses the validatehtml engine to perform real-time spec checks, catching unclosed tags and duplicate IDs that a standard prompt would likely miss.

    Use cases

    • Validate a new React component's rendered HTML for spec compliance.
    • Audit a local dev server URL for automated accessibility failures before a PR.
    • Check a JSON configuration file for syntax errors before deployment.
    • Verify that a complex SVG icon preserves valid XML structure after editing.

    Known limitations

    Does not support files over 1 MB or non-web extensions like .env. Automated accessibility checks cannot verify keyboard flow, focus order, or meaningful alt text.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Frontend & Web Apps.

    Files must be under 1 MB. CLI requires Node 18 or later. Cannot validate logic-heavy source templates (e.g., .jsx, .vue) directly; requires rendered output or URLs.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Free to use

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 7 days ago

    • Free with an Agensi account

    Accounts
    Validatehtml
    Software
    Node.js
    Optional
    VALIDATEHTML_API_KEY (only for audit_page)

    Permissions

    Terminal / Shell
    Read Files
    Network Access

    Allowed Hosts

    validatehtml.com

    The code, file or page being checked is sent to validatehtml.com, checked in memory and not stored. Only .html, .htm, .css, .json, .xml and .svg files up to 1 MB are read. The API key is optional and only used by audit_page.

    Listed7 days ago

    What's inside

    Frequently Asked Questions

    It acts as a quality gate before you commit: the agent checks HTML, CSS, JSON and XML against their specs, flags common WCAG failures, fixes the errors and validates again.

    The tool supports HTML5, CSS3, SVG, XML, and JSON, making it ideal for validating both static assets and the rendered output of frameworks like Next.js, Astro, or Vue.

    Unlike LLMs that may hallucinate spec compliance, this skill uses a dedicated validation engine to catch technical errors like unclosed tags, duplicate IDs, and ARIA role misconfigurations that a standard prompt would likely miss.

    The skill requires Node 18+ and can be accessed via an MCP (Model Context Protocol) server or a CLI tool, allowing your AI agent to scan local file paths or live URLs like localhost.

    While it identifies common WCAG failures and ARIA issues, it cannot verify manual UX factors such as logical tab order, keyboard flow, or whether alt text is contextually meaningful.

    The skill is limited to files under 1 MB in size and does not support non-web extensions such as .env or binary files.

    New in Frontend & Web Apps

    Free