- Home
- Skills
- Frontend & Web Apps
- ValidateHTML: validate HTML, CSS and accessibility
ValidateHTML: validate HTML, CSS and accessibility
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
Works with the AI Agents you already use
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
| File | Check | Result |
|---|---|---|
signup.html | HTML | 2 errors, 4 warnings |
signup.html | Accessibility | 1 error, 3 warnings |
theme.css | CSS | 2 errors, 0 warnings |
Errors (spec violations, all fixed):
signup.html5:12<img>is missing required "alt" attribute (wcag/h37)signup.html10:34 Duplicate ID "email" (no-dup-id): the password field reused the email field's idtheme.css5:20 Invalid value fordisplayproperty (flexboxis not a value; changed toflex)theme.css5:29 Unknown propertycolr(typo forcolor)
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 withfor <button>had notype: settype="submit"
Your CSS nesting (& h2, &:hover) is valid modern CSS and was not flagged, so I left it as is.
Second run
| File | Check | Result |
|---|---|---|
signup.html | HTML | Passed, 0 errors, 0 warnings |
signup.html | Accessibility | Passed, 0 errors, 0 warnings |
theme.css | CSS | Passed, 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
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
- Validate code by passing snippets directly from the conversation, before writing them to disk.
- Scan files by providing a local path to the CLI or MCP tool for a direct file-system check.
- Audit URLs by pointing the tool at
localhostor a staging environment to validate final rendered output. - 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.
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
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
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
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 forever
No account required to browse
Trust & safety
Security scan
Security scan passed 7 days ago
- Free with an Agensi account
Requires
Permissions
Allowed Hosts
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.