Build a neighbourhood library website.

Brief: a fictional community library needs a simple website that helps first-time visitors decide when to visit and how to join. Use these supplied practice details: open Tuesday–Sunday, 10am–6pm; closed Monday; free on-site reading; borrowing membership ₹300 per year; bring one photo ID to register. Do not invent an address, phone number, reviews or visitor counts.

Map three journeys: checking opening hours, finding membership information, and learning about access. Draft a one-page wireframe and plain-language copy. Include an accessibility information section that clearly marks details needing confirmation, rather than claiming facilities exist.

Submit a document, images, presentation or spreadsheet containing the journeys, wireframe and final copy. Review criteria: essential information is easy to find on a phone; the supplied facts are accurate; headings follow a clear order; unverified details are identified.

Use the library brief from task 1 to build a single page with semantic HTML and CSS. A framework is optional. Include opening hours, membership, getting started and access information. Keep the main content readable at 320px, 768px and 1280px.

Provide visible keyboard focus, descriptive links, useful alternative text for informative images, and a clear empty or unavailable state for unconfirmed information. Use your own image or a properly licensed image with attribution; the page must remain usable when images fail. No signup backend, paid hosting or real personal data is required.

Submit a document, images, presentation or spreadsheet with three viewport screenshots, a keyboard walkthrough and a source repository link. Review criteria: no horizontal scrolling at the stated sizes; every interactive element is usable by keyboard; text remains readable when enlarged; the page stays understandable without its image. Label the site as a fictional practice project.

Review your library page on a phone-sized viewport and a desktop. Check the opening hours against the brief, follow every link, navigate without a mouse, enlarge the text, and temporarily block images. Record the actual result of each check.

Measure a fresh page load using browser developer tools and record your test conditions. Make at least two improvements based on what you observed. Report measurements as your own local results, not universal performance guarantees. Add a README explaining how to run the page and where content can be updated.

Submit a document, images, presentation or spreadsheet with your checklist, before/after evidence, remaining limitations and repository link. Review criteria: reproducible checks, clear evidence of fixes, an honest limitations list and a handover another developer can follow.