Parts of an ONS webpage Warnings

Overview

Warnings highlight limitations that affect how users interpret the data, analysis or methods in a release. Warnings prevent the misuse of data, with minimal interruption to the content. Warnings are written in bold text and are preceded by an exclamation mark symbol.

Where to use warnings

Warnings can be used in bulletins, headline releases and articles. They should not be used in methodology pages, where there is already space to write about limitations and quality caveats in more detail. Headline releases should include a maximum of one short warning to explain essential caveats.

Warnings are designed to stand out from the surrounding text so that users notice them. Using too many, or including too much detail, distracts users. Warnings should only be used at the end of the Main points or in the analysis sections. They should not be used before your analysis, as testing has shown that users find it confusing to read warnings before commentary. They should also be avoided immediately before or after a table, chart or diagram.

Avoid using hyperlinks in warnings, unless the link is directing users to more information in the Data sources and quality section (opens in a new tab) 

If your release contains official statistics in development (opens in a new tab) , include a standard warning at the end of the Main points section. More information is available in our Warnings about official statistics in development subsection (opens in a new tab)  on this page, and our Guide to official statistics in development (opens in a new tab) 

For an example of how to include a warning box, see our Labour market overview, UK bulletin (opens in a new tab) 

How to write a warning

Do

• Keep warnings short and clear to help users retain the information.
• Only use warnings when they have a direct effect on how users interpret the content around them.
• Use the Data sources and quality section, which you can link to in the warning, to add detail.
• Only include warnings at the end of the Main points section, and in the analysis sections.

Do not

• Use warnings too often as it reduces their effectiveness.
• Place warnings next to each other, as they overwhelm users.
• Position warnings before your analysis.
• Position warnings immediately before or after a table, chart or diagram.
• Provide definitions in warnings; instead, define terms briefly in your analysis, and use the glossary section to provide more detail.
• Include hyperlinked text, except a single link to more detailed information in the Data sources and quality section.

Warnings should be short

Warnings have a character limit of 280 characters, including spaces. The shorter the warning, the more effective it will be. Presenting too much information to users makes it less likely that they will understand and retain the warning. Long warnings are also problematic for users on mobile devices or with accessibility needs.

You can explain limitations in more detail in the Data sources and quality section.

Warnings about official statistics in development

Official statistics in development (previously known as “experimental statistics”) should always be primarily published as a bulletin where they are the first release of new data. An article using the data can be published alongside the bulletin if more detailed analysis is needed.

Use the following standard warning box text at the end of your Main points section, if your release contains official statistics in development.

Use the following template for releases that include statistical research and methods in development.

More information on the methods used, quality limitations of the data and ongoing improvements can then be included in the Data sources and quality section. Provide links in this section to more detailed explanations in any accompanying methodology pages