Detailed answer
Check document structure, descriptive headings, working links, labeled fields, alternative text, and narrow-screen behavior.
Navigate using only the keyboard and verify resources from the deployed location. Share a minimal example when asking for help and remove private information. One successful visual check in one browser is only a starting point.
Example
<main><h1>My HTML project</h1><p>What this page does.</p><a href="/examples/">Explore examples</a></main>
Understanding the behavior
A release check should cover meaningful behavior, not just whether the homepage looks attractive. Test navigation, forms, missing pages, keyboard access, mobile layout, resource paths and metadata using the deployed URL. Local success does not prove production mail or HTTPS configuration.
Practical implementation notes
Keep a backup and a short deployment checklist, then verify the live version after upload. Record any remaining limitations honestly and avoid publishing test credentials, private configuration or placeholder legal and contact details.
How to check it
Test keyboard navigation, narrow layouts, resource paths, and meaningful structure before sharing a minimal example.
Expected result
A reviewer receives a reproducible HTML problem without private source data.
Watch out: Check both the rendered experience and the actual document structure.
Read the reference ↗