Reduce cognitive load in data-rich repositories with EASE

A practical checklist for data repositories

This checklist is a practical design and review aid. It contains a set of questions to keep in mind while designing or reviewing a page, feature, or workflow.

It is not a full accessibility audit.

For more detail, see the COGA guidance and the GOV.UK cognitive accessibility guidelines in the resources below.

ExplainHelp users understand what things are and how to use them.

ArrangeHelp users find what they need and follow a clear structure.

SimplifyUse clear content and remove unnecessary complexity.

EnableSupport users with errors, memory, help, and personalisation.

How to use this checklist

Use it as a quality standard: ask these questions during design, and ask them again when reviewing the page. Tick the checkbox next to each statement if it is true for your website or service. If you are not sure, treat it as something to investigate.

Done is better than perfect: even a few improvements can make a real difference to users.

COGA guideline areas

Help users understand what things are and how to use them.
Help users find what they need.
Use clear and understandable content.
Help users avoid mistakes and know how to correct them.
Help users focus.
Ensure processes do not rely on memory.
Provide help and support.
Support adaptation and personalisation.

Checklist by page or component

Open a section to review the questions for that page or part of the service. Each question includes its related guideline references in brackets.

1. Home / entry page

2. Global header and navigation

3. Search page - General

Is the search input easy to find and easy to recognise?G2

Does the page make it clear what content is being searched, for example articles, journals, datasets, or all records?G1, G3

Does the page show only the search options most users need first, with advanced search easy to find when needed?G2, G5

Are search tips or examples available close to the search box when needed?G6, G7

Can users tell how to start a basic search without reading long instructions?G1, G5

Can users keep or share the current search, for example through a stable URL or a saved query?G6, G7

3.1 Search page - Facets and filters

3.2 Search page - Search results list

4. Record landing page

5. Metadata form

6. Review and publish step

7. Account dashboard

8. Information pages

Is the page purpose clear from the title and heading?G2, G3

Is the content written in plain language and does it avoid unnecessary jargon?G3

Is long text broken into short sections with headings?G2, G3

Are instructions written as clear steps where needed?G3, G7

Are links descriptive and meaningful out of context?G1

Is supporting documentation linked from the point where users need it?G7

Are contact routes or support options easy to find?G7

Are important dates, policies, and requirements explained in an unambiguous format?G3