A Practical HTML Review Checklist

Before publishing a page, review it as a visitor and as the person who will maintain it later.

Document basics: Does it have a doctype, a meaningful title, a correct language, UTF-8 encoding, and a viewport declaration? Is the visible content inside the body?

Structure: Is there a clear main region? Do headings describe the content hierarchy? Are lists and tables used for the right kind of information? Are generic containers used only where they make sense?

Links and media: Do links have descriptive text and working destinations? Do informative images have useful alternative text? Are decorative images marked with an empty alternative? Are captions provided where needed?

Forms: Does every field have a label? Are control names meaningful? Are required formats explained? Does the server validate data independently?

Accessibility: Can a keyboard user reach and operate every control? Is focus visible? Is the page language correct? Are embedded frames titled?

Quality: Does the page pass an HTML validator? Are there console errors or missing network resources? Does it remain usable on a narrow screen?

A checklist helps catch common issues, but it does not replace testing with real users or assistive technology. Use it as a repeatable baseline, not as a certificate that the page is perfect.