AI generated image by ChatGPT
The report flagged it in amber:
Elements marked as presentational should be consistently ignored. Jun had no idea what that meant. It sounded more like philosophy than code. But next to the issue there was a link to a guide, so she clicked it. Two minutes later she understood the problem and had a clear fix. Done.She went back to the report. Forty-seven issues to go. She clicked the next guide link, then the next. Each one laid it out the same way: what’s wrong, why it matters, how to fix it.
Jun smiled. “I could get used to this.”
Every Guide, Revisited from the Ground Up
We’ve just finished a complete overhaul of our HTML and accessibility validation guides — over 750 of them. Every single guide has been reviewed, corrected, and expanded to give you clearer explanations, better code examples, and practical steps to fix each issue.
These aren’t just minor tweaks. We went back to the fundamentals and asked: if a developer or QA engineer encounters this issue for the first time, will this guide actually help them fix it? If the answer was “not quite,” we rewrote it.
Here’s what changed:
Clearer explanations of what each issue means and why it matters. Not just the technical definition — the real-world impact on users. Why a missing lang attribute isn’t a nitpick but a barrier for screen readers. Why duplicate IDs can silently break form interactions. Every guide now connects the rule to the people it protects.
Practical code examples you can adapt right away. Each guide includes before-and-after code snippets showing the problematic pattern and its corrected version. No more guessing what “ensure adequate contrast” actually looks like in your markup.
Coverage for every issue Rocket Validator can detect. HTML validation issues and WCAG accessibility violations — if it shows up in your report, there’s a guide ready to walk you through the fix.
Built for Humans, Not Just Validators
One thing we kept hearing from users was that validation guides tend to be written for people who already understand the spec. That’s backwards. The people who need guides the most are the ones encountering an issue for the first time.
So we rewrote with that audience in mind. A junior developer seeing aria-hidden="true" on a focusable element for the first time will find a guide that explains what ARIA is, why this combination is a problem, and exactly how to fix it — without assuming they’ve memorized the WAI-ARIA spec.
At the same time, experienced developers get what they need too: concise issue descriptions, direct code fixes, and links to the relevant specifications for deeper context.
Tell Us What You Think — Right from the Guide
We’ve also added something we should have built a long time ago: a feedback widget on every guide.
At the bottom of each guide page, you’ll find a quick way to let us know whether the guide was helpful, whether something was unclear, or whether you think it needs improvement. It takes a few seconds. No login required.
This matters to us. With over 750 guides to maintain, your feedback is the fastest way for us to find what’s working and what still needs attention. Found a code example that doesn’t quite apply to your framework? Let us know. Think an explanation could be clearer? Tell us. Want a guide to cover an edge case it currently doesn’t? We want to hear it.
We read every single piece of feedback, and we’ll use it to keep improving the guides over time.
Better Guides, Better MCP Conversations
If you’re using our MCP Server integration with Claude, this update makes your AI-assisted workflows even more powerful. When Claude retrieves a guide to help you fix an issue, it’s now pulling from a richer, more accurate, and more detailed knowledge base. The better the guides, the better the answers.
Ask Claude “how do I fix this contrast issue?” and the response will draw from a guide that’s been carefully reviewed for accuracy and completeness.
Start Exploring
You can browse the full collection of guides right now:
- Accessibility validation guides — WCAG-based rules covering everything from alt text and ARIA attributes to keyboard navigation and color contrast.
- HTML validation guides — standards-based HTML rules covering document structure, element nesting, attribute usage, and more.
And when you find a guide that helps, hit that feedback button at the bottom of the page — it helps us know what’s working and where to focus next. Jun would appreciate it, and so would we.