Reference guide #1

Core principles of web design and development

A reference guide for web design students. Good work on the modern web is shaped by twelve broad principles. Each of them contains several lower-level principles of its own, and together they determine the way we plan, design, build and maintain a website.

The short version

Build to standards, with clean code and meaningful structure. Start with people and their content, make sure it works on any screen, and make it clear, accessible, fast and light on the planet.

1 Standards 2 Clean code 3 Semantics 4 Users 5 Content-first 6 Original content 7 Responsive 8 Mobile-first 9 Visual design 10 Accessibility 11 Sustainability 12 Performance
In this reference guide

How to use this reference guide

Think of these twelve principles as umbrella ideas. Each one contains several narrower principles, which are listed under its heading. For example, “Web standards” includes the Web Standards Model, progressive enhancement and the separation of concerns, while “Clear, consistent visual design” includes principles for colour, typography and layout.

Every principle follows the same pattern. There is a brief description, followed by how it influences the design process, the lower-level principles it includes, and some reference links for further reading. Where a principle connects to one or more of our cheat sheets, it says so.

Note that the principles overlap, and sometimes they pull in different directions. Good designers don’t follow them one at a time — they balance all twelve. See Balancing the principles.

The twelve principles at a glance

Design process mapping

Where each principle has the most influence in a typical project. Note that this is a guide, not a rule.
PrincipleResearch and planDesignBuildTest and launchMaintain
1. Web standardsYes●Yes●Yes●
2. Best practice codingYes●Yes●Yes●
3. Semantic codeYes●Yes●Yes●
4. User-centred designYes●Yes●Yes●Yes●
5. Content-firstYes●Yes●
6. Original and engaging contentYes●Yes●
7. Responsive web designYes●Yes●Yes●
8. Mobile-first / device-agnosticYes●Yes●Yes●
9. Clear, consistent visual designYes●Yes●
10. AccessibilityYes●Yes●Yes●Yes●Yes●
11. SustainabilityYes●Yes●Yes●Yes●
12. PerformanceYes●Yes●Yes●Yes●

The principles

1Web standards

Web standards are shared technical specifications that define how HTML, CSS, JavaScript, HTTP and other web technologies work. They are developed by bodies such as the W3C, the WHATWG, the IETF and Ecma. Because every browser implements the same standards, a page written to them will work across browsers, devices and assistive technologies, both today and in the future.

How it influences the design process

Lower-level principles included

Learn more

Connects to: cheat sheet 3 (element syntax) and cheat sheet 6 (selectors).

2Best practice coding: clean, readable and consistent

This principle is about writing code that is clean (free of clutter, duplication and anything unnecessary), readable (a person can follow its structure, names and comments) and consistent (the same conventions are used throughout, by everyone on the project). Why does this matter so much? Well, code is read far more often than it is written — by teammates, by clients, and by your future self.

How it influences the design process

Lower-level principles included

Learn more

Connects to: cheat sheet 1 (naming), cheat sheet 3 (syntax), cheat sheet 6 (selectors) and cheat sheet 10 (custom properties and DRY).

3Semantic code

Semantic code uses markup to describe what content means, not just how it looks, so that the intent behind each part of a page is explicit. That meaning can then be understood by every kind of reader:

How it influences the design process

Lower-level principles included

Learn more

Connects to: cheat sheet 3 (semantics), cheat sheet 4 (headings), cheat sheet 1 (naming), and principles 1 and 10.

4User-centred design

User-centred design is an approach in which the needs, goals, abilities and context of real users drive decisions at every stage, rather than assumptions or personal taste. It is an iterative process: we research, design and test, and then we refine. Above all, remember that you are not your user.

How it influences the design process

Lower-level principles included

Learn more

Connects to: principles 5 (content-out), 8 (mobile-first) and 10 (accessibility).

5Content-first

Content-first means designing from the content outwards, which is why it is also known as “content-out”. The real words, images, data and functions that users came for come first, and the layout, navigation and styling are shaped around them. The opposite approach is to build an empty template and pour the content into it later. As Jeffrey Zeldman put it in 2008:

“Design in the absence of content is not design, it’s decoration.”

How it influences the design process

Lower-level principles included

Learn more

Connects to: cheat sheet 4 (headings and outlines), and principles 6, 7 and 8.

6Original and engaging content

This principle is about content that is yours and that is worth people’s time. Original means it is created or curated with real insight, experience or imagery, rather than being copied, duplicated or generic. Engaging means it is relevant, clear and interesting, and easy to read and act on. After all, content is the reason people visit a website in the first place. Google’s guidance asks for “people-first” content, made to benefit readers rather than to manipulate search rankings.

How it influences the design process

Lower-level principles included

Learn more

Connects to: cheat sheet 7 and cheat sheet 8 (images), and principles 3, 5 and 10.

7Responsive web design (RWD)

Responsive web design is an approach in which one website adapts to the size and capabilities of whatever viewport it is shown in, rather than building separate sites for separate devices. The term was coined by Ethan Marcotte in 2010, and its three original ingredients are flexible grids, flexible images and media, and media queries.

How it influences the design process

Lower-level principles included

Learn more

Connects to: cheat sheet 8 (images), cheat sheet 9 (background sizing), and principles 8 and 12.

8Mobile-first and device-agnostic design

Mobile-first means designing and coding for the smallest screen and the most constrained situation first, and then enhancing the experience as more space and capability become available. The approach was popularised by Luke Wroblewski around 2009. Device-agnostic (also known as screen-agnostic) means never assuming a particular device. In other words, your site should work for any screen size, input method, connection speed or technology, including devices that don’t exist yet. Put simply, mobile-first is the order of work, responsive design is the technique, and being device-agnostic is the goal.

How it influences the design process

Lower-level principles included

Learn more

Connects to: principles 4, 5, 7, 11 and 12.

9Clear, consistent visual design

This principle is about organising colour, typography, layout and imagery so that a site communicates clearly, guides the user’s attention and feels like one coherent whole. Clear means that information is easy to read and understand at a glance. Consistent means that the same things look and behave the same way everywhere, so that users learn a pattern once and can then trust it.

How it influences the design process

Lower-level principles included

Learn more

Connects to: cheat sheet 5 (colour), cheat sheet 9 (backgrounds), cheat sheet 10 (custom properties), and principles 7 and 10.

10Accessibility (a11y)

Accessibility means designing and building so that everyone can perceive, understand, navigate and interact with our websites. That includes people with visual, hearing, motor and cognitive disabilities, as well as people with temporary or situational limitations, such as a broken arm or a screen in bright sunlight. (“a11y” is shorthand: a, then 11 letters, then y.) Accessibility is the right thing to do, it improves the experience for all users, and in many countries it is also a legal requirement. In the UK, the Equality Act 2010 applies, and public sector websites must meet specific accessibility regulations.

How it influences the design process

Lower-level principles included

Learn more

Connects to: cheat sheet 4 (headings), cheat sheet 5 (contrast), cheat sheet 3 and cheat sheet 7 (alt text and titles), and principles 3, 4 and 9.

11Sustainability

Sustainable web design means designing and building websites that minimise harm to the planet and to people. Every page view uses electricity — in data centres, in networks and on the user’s device — so a heavier site means more energy and more carbon. Sustainable web design also considers social impact: privacy, fairness and inclusion. The W3C’s Web Sustainability Guidelines frame this as planet, people and prosperity. Note that estimates of a site’s footprint vary between tools, so treat the numbers as indicators rather than exact measures.

How it influences the design process

Lower-level principles included

Learn more

Connects to: cheat sheet 7 and cheat sheet 8 (images and SVG), and principles 8, 10 and 12.

12Performance (page speed)

Performance describes how quickly a page loads, becomes usable and responds to input. Slow pages frustrate users, particularly on mobile devices and slow connections, and they cost sales and trust. Google’s Core Web Vitals measure three things: loading (Largest Contentful Paint, which is good at 2.5 seconds or less), responsiveness (Interaction to Next Paint, 200 milliseconds or less) and visual stability (Cumulative Layout Shift, 0.1 or less).

How it influences the design process

Lower-level principles included

Learn more

Connects to: cheat sheet 7 and cheat sheet 8 (images), cheat sheet 9 (large background images), and principles 7, 8 and 11.

Balancing the principles

The principles reinforce each other. For example, semantic HTML helps accessibility, search, AI systems and standards compliance, all at the same time. Mobile-first thinking tends to improve performance, sustainability and content focus. Lighter pages are faster, greener and more inclusive. In other words, work that serves one principle well will often serve several.

However, sometimes they conflict, and when that happens, the skill lies in making a deliberate trade-off.

TensionA good way to resolve it
Rich visual design and video versus performance and sustainability (9 vs 11, 12)Use heavy media only where it earns its place. Optimise it, load it lazily, and provide a light default.
Content-first design versus a consistent design system (5 vs 9)Build a system of flexible components that adapts to real content, rather than forcing content into rigid boxes.
Engaging media versus accessibility (6 vs 10)Pair every image, video and animation with alt text, captions, transcripts and a reduced-motion option.
The newest CSS and JavaScript features versus web standards and wide support (1 vs 8)Use progressive enhancement: a solid baseline for everyone, with new features layered on where they are supported.
Fast delivery versus clean code (2)Agree conventions, and automate formatting, linting and checks at the start, so that speed doesn’t build up technical debt.

Common misunderstandings

MisunderstandingThe reality
Web standards make every site look the sameStandards define the technologies, not the design. They leave you free to be as creative as you like.
Mobile-first means mobile-onlyIt describes the order in which you work. Larger screens are still fully supported.
Accessibility is only for blind usersIt covers vision, hearing, movement and thinking, as well as temporary and situational needs. It helps everyone.
SEO means stuffing in keywordsSearch engines reward clear, helpful, well-structured content that is made for people.
Content-first means writing every word before designingIt means understanding the real content early and designing with it, not waiting for a perfect final draft.
Performance is a final polishEarly decisions about images, fonts and scripts set a page’s weight. Late fixes can only reduce the damage.
Sustainability just means green hostingHosting is only one part. Page weight, features, content and device longevity all count.
AI can read messy pages, so structure doesn’t matterMachines can cope with untidy HTML, but a clear structure helps them, and every other user too.

Check before you launch

Learn more

External sites change over time, so if a reference link has moved, search for the page title. The figures quoted for the Core Web Vitals and the current WCAG version were correct at the time of writing, but check the sources for any updates.