The Written Exam

Ninety minutes on paper, and no code to write. Read HTML and CSS, tell the three languages apart, and find what is wrong.

When and where

Detail
DateFriday, 20 November 2026
Time14:00–15:30
Length90 minutes
Roomto be announced
Weight25 % of your grade (provisional)

You will not write code

Last year's paper asked for a whole HTML page from memory. This year's does not.

A machine can write an HTML page in a second. What it cannot do for you is know whether the page is right. That is what this exam tests — the same skill you use every time an AI hands you code:

  1. Read it. Say what a piece of HTML or CSS does, and what the browser will show.
  2. Tell the languages apart. Is this line HTML, CSS or JavaScript — and which file do you open when something breaks?
  3. Find what is wrong. Spot the errors in HTML and in CSS, and say what would fix them.
  4. Explain it. Short answers in your own words: how a page reaches you, why one choice is better than another.

Expect to mark up code — circle, underline, give line numbers — and to answer in short sentences.


What it covers

Everything here was taught in the lessons. The last column names the lesson it comes from — all of them are on the Lessons page.

TopicWhat you should be able to doLesson
How the web worksclient and server · the parts of a URL · what DNS does · a request and a response · status codes, and whose fault they are · Tim Berners-Lee's four inventions · why standards matterLesson 1 · What the Web Is
HTML, CSS, JavaScriptwhat each one is for · recognise each at a glance · which to open when something breaksLesson 1
Reading HTMLthe skeleton, and what each line prevents · <head> and <body> · <head> and <header> · headings as an outline · <strong> and <em> · <ul>, <ol> and <dl> · links and paths · images and alt · tables · labels · semantic elementsLesson 2 · Lesson 4 · Recap
Reading CSSthe parts of a rule · what a selector picks · class and id · three ways to apply CSS · color and background-color · margin, border and padding · what display: flex doesLesson 3 · Recap · The Quote Collection
Finding errorsunclosed tags and quotes · wrong nesting · a missing alt · broken paths · missing semicolons and braces · misspelled properties · selectors that match nothingRecap · Spot the Error
File names and URLsthe naming rules: all lowercase, no spaces (use -), index.html as the front page of a folder — and why breaking them works on your laptop but not on a server · a valid URL and an invalid one: a space, a \ instead of /, a missing https:// · relative and absolute pathsLesson 1 · Lesson 2 · Files, URLs and Formats
File types for the webwhat a browser can show, and what each one is for: JPEG or WebP for photos · PNG for transparency and the favicon · SVG for logos and icons · MP4 for video and animation, not GIF · WOFF2 for fonts — and what most browsers cannot show, so it is converted first: an iPhone .heic, a Photoshop .psd, a .tiff, a Word .docxLesson 4 · What the Web Is · Files, URLs and Formats
Page structure and design termsthe four parts of a page — header, nav, main, footer — and what goes in each · the hero, the first screen of the homepage · sections and articles · cards, and a grid of cards · an aside, or sidebar · responsive: one page that works on a phone and on a laptopLesson 4 · Recap · The Quote Collection
Your site's identityfavicon, app icon and Open Graph image — what each is for, and its sizeLesson 4 · Your Project
Planningsketching a page before writing it · the four questions that decide a projectLesson 4 · Your Project
Git and GitHubwhat Git is, what GitHub is, and why they are not the same · the words: repository, commit, stage, push, pull, clone, remote and origin, main · add, commit, push — in that order, and which of them need the internet · git status · what never goes in, and .gitignore · one repository per project, never in the outer folderGit & GitHub · What You Hand In

Not on the exam

  • Writing code. No page, no stylesheet, no script from memory.
  • Reading JavaScript line by line. You must recognise JavaScript, and know when it is the part that is broken — not explain what each line does.
  • Specificity and inheritance. You will not be asked which of two competing CSS rules wins.
  • Vue and frameworks.

What to bring

  • Allowed: a pen or pencil, and blank paper for rough work
  • Not allowed: phones, laptops, tablets, notes, books — anything electronic, anything printed

How to prepare

Six things, roughly in this order.

  1. Say the "done" slides out loud. Every lesson deck ends with a slide called What you should be able to say now. Go through each one and say the answers aloud, without looking. Whatever you cannot say is what you study next.
  2. Work through the four study pages: HTML, CSS or JavaScript?, Reading HTML and CSS, Files, URLs and Formats and Spot the Error.
  3. Break your own site on purpose. Delete a closing tag. Remove a semicolon. Give an image a capital letter. Misspell a class. Watch what the browser does, and what DevTools shows — then undo it with Git. Every error on the exam is one you can make, and see, on your own site in a minute.
  4. Read code you did not write. Right-click any page → View Page Source. Or ask an AI for a short HTML page with five mistakes in it, find them, then ask it to check your answers — and check its answer too.
  5. Run the validator. Paste your own pages into validator.w3.org and read every message until you understand it. The validator does exactly what this exam asks of you.
  6. Sit the Practice Paper on paper, with a 90-minute timer, before you open a single answer.

In the exam room

  • Read the whole paper first. Then start with what you know.
  • Count. "Find five errors" means there are five. Found three? Go through it again, line by line.
  • Check the pairs. Every <tag> with its </tag>, every " with its partner, every { with its }, every declaration with its ;.
  • Say what is wrong, and why. Not "line 19 is wrong", but "line 19: the <h2> is never closed, so the paragraph becomes part of the heading."
  • Write so it can be read. An answer nobody can read cannot be marked.
  • Keep five minutes at the end to check.

Test yourself

Can you, without looking:

  • name Tim Berners-Lee's four inventions, and spell out every acronym?
  • say what happens between typing an address and seeing a page?
  • say what a 404 means — and whose fault it is?
  • tell a valid URL from an invalid one — and say what is wrong with it?
  • name a file so it works on any server — and say why About Me.JPG will not?
  • choose the format for a photo, a logo, a video and a font — and name three files a browser cannot show?
  • look at a line of code and say whether it is HTML, CSS or JavaScript?
  • say what goes wrong without <!DOCTYPE html>, lang="en", the charset line and the viewport line?
  • explain the difference between <head> and <header>?
  • point at any website and name its parts: header, nav, hero, main, footer?
  • choose between <ul>, <ol> and <dl> — and say why?
  • say which elements a CSS selector picks — and what each declaration changes?
  • find an unclosed tag, a missing semicolon and a broken image path?
  • explain the difference between Git and GitHub — and say what add, commit and push each do?

If any answer is "not yet", the page that teaches it is linked above.