Essential session storage is required to sign in. Optional analytics remain off unless you allow them.
Build a single well-structured HTML page (a personal profile, a recipe, or an article) using ONLY HTML — no CSS or JavaScript. It must: start with a correct boilerplate (<!DOCTYPE html>, <html lang>, <meta charset>, viewport, a descriptive <title> and meta description); use SEMANTIC landmarks (header, nav, main, article/section, footer) instead of divs; have a correct heading hierarchy (one <h1>); include a list, a table for some tabular data (not layout), links with meaningful text, and at least one image with a proper alt attribute. Validate it with the W3C validator and fix every error.
Correct landmarks (header/nav/main/footer), one <h1> + sane heading order, list + a data table (not layout); no div soup.
Doctype, lang, charset, viewport, descriptive title + meta description; images have proper alt.
Passes the W3C validator with no errors; well-formed, quoted, lowercase markup.
Use this README structure to make the work reviewable.
DevPath fetches a read-only, size-capped snapshot. Submitted code is never executed.
# A semantic, accessible content page ## Goal Build a single well-structured HTML page (a personal profile, a recipe, or an article) using ONLY HTML — no CSS or JavaScript. It must: start with a correct boilerplate (<!DOCTYPE html>, <html lang>, <meta charset>, viewport, a descriptive <title> and meta description); use SEMANTIC landmarks (header, nav, main, article/section, footer) instead of divs; have a correct heading hierarchy (one <h1>); include a list, a table for some tabular data (not layout), links with meaningful text, and at least one image with a proper alt attribute. Validate it with the W3C validator and fix every error. ## Acceptance criteria - [ ] Semantic structure: Correct landmarks (header/nav/main/footer), one <h1> + sane heading order, list + a data table (not layout); no div soup. - [ ] Correct boilerplate & metadata: Doctype, lang, charset, viewport, descriptive title + meta description; images have proper alt. - [ ] Valid: Passes the W3C validator with no errors; well-formed, quoted, lowercase markup. ## Verification - [ ] Document installation and run commands. - [ ] Record automated checks and their exact commands. - [ ] Add representative output, screenshots, or a short demo where useful. - [ ] Confirm failure paths and known constraints. ## Decision log ### Decision title - Context: - Choice: - Alternatives considered: - Tradeoffs: ## Evidence - Link each rubric criterion to the file, test, or artifact that demonstrates it. ## Known limitations - List what is intentionally out of scope and what should be improved next.