HotDocumentsOutlinesHeadingsLinksAlternative textForms
Latest A web page is a structured document first and a picture only afterwards.
Launch issue

The page you are reading is a document before it is a design

Every web page carries two lives at once: the one you see and the one you describe. This magazine is about the second one, because it is the one that decides whether the first one works.

Most people meet the web through its surface. You open a page, you see a column of words, a picture, a coloured rectangle that says the word Continue, and you form an impression of the whole thing in about a second. That impression is real, but it is not the page. Underneath it sits something quieter and far more consequential: a description. Someone, at some point, wrote down what each part of that page actually is. This is a heading. This is a list of three items. This is a link that goes elsewhere. This is a control that submits what you typed. The visual surface is assembled from that description, and never the other way around.

That distinction sounds academic until you notice how many different things read the same page. A browser on a laptop reads it. A browser on a phone with a cracked screen reads it. A screen reader, speaking aloud to somebody who is not looking at the screen at all, reads it. A search engine reads it and decides what the page is about. A reading mode strips away everything decorative and keeps what it believes is the article. A device that has not been invented yet will read it too, and it will not have your stylesheet, your fonts or your assumptions. Each of those readers is working from the description, not from your impression of the design.

Continue reading

A Document, Not a Picture

Choosing an element for how it looks is the original sin

Almost every structural problem on the web traces back to one decision made for the wrong reason.

One page, many readers, none of them identical to you

You build on one screen with one set of abilities, and then the page goes out to everyone else.

Structure and Outline

A list is a list, and saying so changes what readers get

Three related things marked as three related things behave differently from three lines that happen to sit together.

The difference between a paragraph and a line that is alone

Not every block of text with space around it is a paragraph, and the distinction is not pedantry.

The Elements That Carry Meaning

What alternative text is genuinely for, and when to leave it empty

A description of a picture is not a caption, a title or a place to put keywords.

Tables are for data, and using them for layout hurts

A table makes a promise about relationships between rows and columns. Keep the promise or use something else.

The Page as a Contract

What happens when something fails to arrive

Networks drop, images do not load, and decoration goes missing. A well described page degrades gracefully.

Accessibility is mostly ordinary correct markup, not an extra layer

The great majority of what makes a page usable to everyone is already yours for free, if you describe things honestly.

About HTML Child

HTML Child is a magazine about markup as meaning. Its subject is the description that sits underneath every web page: the quiet document that says this is a heading, this is a list, this is a link, this is a field and here is its name. That description is what a browser builds its model from, what a screen reader speaks, what a search engine interprets, and what a device nobody has invented yet will one day receive. We treat it as the primary artefact and appearance as the thing layered on top, because that is the order in which the machinery actually works.

The approach here is deliberately unusual in one respect: there is no code in these pages. Not a tag, not an attribute, not a line of syntax. This is a choice rather than an omission. Syntax is abundant, quickly learnt and easily copied, and it is not where beginners come unstuck. What is scarce is the habit of thinking structurally: looking at a piece of content and naming it honestly, seeing an outline where others see font sizes, and recognising when a visual instinct is about to be dressed up as a structural claim. We write about that habit, in ordinary words, for the ordinary names of things.

The intended reader is an adult who is starting out and would rather understand than memorise. Nothing here assumes prior study, and nothing here is written down to you. Where a topic is genuinely subtle we say so and take our time with it. Where a common practice is a mistake we explain what it costs and who pays, because that is more persuasive than a rule. A sister publication takes up appearance and the visual model, which is a real and worthy subject in its own right. This one stays with structure, meaning and the promises a page makes to everybody who reads it.