HTML Case Study I — Alex Jackson

Overview

This page fulfills the IT 104 Module 7 — HTML Case Study I lab. It is a single, standards-compliant HTML file named index.html. It is currently hosted on Neocities for accessibility and validation; it will be mirrored to Mason’s student web space when available.

Topic: HTML structure, lists, links, and semantic sections.
Deliverable: A hosted web page demonstrating correct HTML syntax and organization.
Tools: Any text editor; FileZilla (for upload to public_html).

Project Requirements

The original starter file (index.txt) included a basic scaffold. Below is a corrected and expanded requirements list reflecting typical expectations for HTML Case Study I.

Title Page with Honor Code
1. Add a meaningful <title> value.
2. Include your name, course, and university.
3. Honor Code statement (see below).
Clean Structure
1. Valid nesting of ul and ol lists.
2. Proper closing tags.
3. Internal CSS in <style> (no external files).
Working Links
1. Include at least one external hyperlink (e.g., GMU home page).
2. Use descriptive link text (avoid “click here”).

Honor Code: “I pledge that I have neither given nor received unauthorized aid on this assignment.” — Alex Jackson

From Starter File → Final Page

The provided scaffold contained placeholder text, an empty <style> block, and an improperly nested ordered list. This final page corrects those issues and adds semantic sections for clarity.

Key Fixes

Set a descriptive document title and meta description.
Replaced placeholder headings with real content (name, course, university).
Fixed list markup (properly closed <ol> tags and nested lists).

Example Markup

Sample snippet illustrating valid HTML (indented and closed correctly):

<ul>
  <li>Syllabus</li>
  <li>Project Requirements
    <ol>
      <li>Title Page with Honor Code</li>
      <li>Clean Structure</li>
      <li>Working Links</li>
    </ol>
  </li>
</ul>

Findings & Discussion

Organizing content with semantic sections (header, main, section, footer) and clean list markup improves readability and accessibility, while a minimal internal stylesheet keeps the file self-contained for easy hosting.

Summary
Criterion	Implementation	Result
Semantics	Used header/main/section/footer	Clear structure for readers and screen readers
Lists	Properly nested ul/ol	No validation errors from list structure
Hosting	Single-file HTML with internal CSS	Straightforward upload to `public_html`

External resource example: George Mason University website.

References

CCA e-book on KHPContent — HTML Case Study I
IT 104 Lab Class Notes — HTML lab videos
W3C HTML Validator (for optional validation)

Contact

Questions about this page? Email: ajacks72@gmu.edu