HTML Foundations
Baseline document, semantic, and form checks that keep pages robust, crawlable, and accessible.
Use this checklist when
Use when building new templates, shared layout primitives, or form-heavy pages and you want a reliable starting pass.
Expected outcome
You lock in the HTML decisions that quietly shape accessibility, browser behavior, and crawlability.
Best for
Done looks like
Document shell, landmarks, input semantics, validation, and markup correctness are stable before deeper review.
How this differs
This is the cleanest onboarding checklist for someone learning what a solid page foundation looks like.
This checklist focuses on the HTML decisions that quietly shape everything else: accessibility, browser compatibility, crawlability, and form reliability. It is a good first pass for new pages, templates, and design-system primitives.
Who It's For
- Junior developers who need a reliable first checklist
- Teams building new templates or shared UI primitives
- Reviewers fixing repeated markup issues at the source
Done Looks Like
You should finish with a page shell that is semantically solid, browser-friendly, and easier to layer accessibility, SEO, and framework behavior on top of.
What It Covers
- Document setup and metadata the browser expects
- Semantic structure and landmarks for navigation
- Form and input behavior that reduces avoidable UX failures
- Valid, predictable markup that is easier to test and maintain
When To Use It
- Before shipping a new page template
- When refactoring shared layout or form components
- During audits where frontend bugs feel “small” but recur across the site
Review Tips
- Check templates before checking page-specific content.
- Verify the DOM output in the browser, not only JSX or templating code.
- Treat repeated HTML mistakes as design-system or framework issues, not isolated page bugs.