Skip to main content
Table of contents

The GDS Way and its content is intended for internal use by the GDS community.

HTML coding style

Browser support

The GOV.UK Service Manual lists the minimum browsers that GOV.UK services are required to support. Tools such as GOV.UK Frontend, that are used to help build services, may have stricter standards of browser support. Therefore, you will need to test your code in different browsers depending on which part of GDS you are working in.

Your page should work with only HTML, before adding any CSS or JavaScript. Read building a resilient frontend using progressive enhancement.

Document structure

Use HTML5 to structure your page semantically. Use ARIA roles to help older assistive technologies map the sections correctly.

Léonie Watson explains how to use ARIA landmark roles to deliver the best experience for screen reader users.

This document does not prescribe whether to use single or double quotes in attributes, whether to omit values from attributes that do not need them or whether to add trailing slashes to void elements. However, the approach you adopt should be consistent throughout your code.

<header role="banner"> should be used to contain your home link, branding, search, and any global navigation you may have.

Main content

<main role="main"> should be used to identify the main content of your page.

A “Skip to main content” link should be added to help screen reader and keyboard users skip past your general site navigation and get straight to the content. You can use the skip link component from the GOV.UK Design System for this.

Sectioned content

Use the <section> tag to represent standalone, thematic groupings of content where a more specific semantic element would not be appropriate.

Examples of sections would be chapters, or various tabbed pages in a tabbed dialog box, or a home page split into sections such as introduction, news items and contact information.

You should add an aria-labelledby attribute linking to the id of the heading that identifies that section.

Example:

<section aria-labelledby="introduction">
  <h2 id="introduction">Introduction</h2>
  <p>People have been catching fish for food since before recorded history...</p>
</section>

<section aria-labelledby="equipment">
  <h2 id="equipment">Equipment</h2>
  <p>The first thing you'll need is a fishing rod or pole that you find comfortable
    and is strong enough for the kind of fish you're expecting to try to land...</p>
</section>

Use <nav role="navigation"> to wrap groups of links that are not already in another context (for example, <footer>). Common examples of navigation sections are menus, tables of contents, and indexes.

As with <section>, it is advisable to use aria-labelledby to label your <nav>. This helps to distinguish different <nav> blocks in the page.

The GOV.UK blog has more information regarding the use of the <nav> tag.

Aside

<aside role="complementary"> should be used for content related to the primary content of the webpage, but which does not constitute the primary content of the page.

Examples include author information, related links and related content.

<footer role="contentinfo"> should be used for the footer of the site.

Individual element guidance

Headings

Headings should be in order - for example <h1> then <h2>, but not <h1> then <h3>.

There should only be one <h1> element in a page.

Text emphasis

Italics should be avoided according to the GOV.UK content style guide.

Bold can be used sparingly, but can make large blocks of text difficult to read.

Semantically, words voiced with emphasis can be marked up with <em>, whereas words conveying a sense or urgency or warning should be marked up with <strong>. In theory screen readers could adopt a different tone of voice for this markup, though none of the major ones currently do.

Browsers will render em in italics and strong in bold by default, so you may need to override em to not use italics.

As a rule, avoid using <i> or <b>, which are only useful in rare cases. It is usually better to use the font-style and font-weight CSS properties.

Images

Read the Design System’s Images section.

Links should be used for navigating to another page. Buttons should be used for submitting forms or interactions within the page (for example, expanding an element). Empty links (<a href="#">) should be avoided.

Links should not open new tabs or windows by default, but if users choose to to so (through keyboard shortcuts or right-click context menu) then we should respect their choice.

Visually hidden elements

Sometimes it can be helpful to provide additional content for screen reader users that might not be needed for sighted users. For example, the ‘Skip to main content’ link covered earlier.

Do not use display: none on this text, as this will get ignored by screen readers.

Instead, use CSS which ensures the text gets ‘conceptually’ rendered, even if the result is not visible on the screen. You can use the Sass mixins from govuk-frontend or the classes govuk-visually-hidden and govuk-visually-hidden-focusable.

Visually hidden text is often a sign that something can be simplified or made visible to benefit sighted users too, so should be used sparingly.

This page was last reviewed on 1 October 2020. It needs to be reviewed again on 1 April 2021 by the page owner #gds-way .
This page was set to be reviewed before 1 April 2021 by the page owner #gds-way. This might mean the content is out of date.