For: Product and delivery
Ask yourself:
For: Design, Development
-Accessibility widgets are plugins that display as buttons, toolbars or overlays.
The widgets let users adapt the display to make it easier to read the text or have it read out to them. Some widget providers claim they make your website accessible.
diff --git a/app/views/accessibility/partials/check-autocomplete-in-forms.njk b/app/views/accessibility/partials/check-autocomplete-in-forms.njk index 275080da3..93c396e77 100644 --- a/app/views/accessibility/partials/check-autocomplete-in-forms.njk +++ b/app/views/accessibility/partials/check-autocomplete-in-forms.njk @@ -1,5 +1,4 @@For: Testing
If you need information only from the person who is filling the form, make sure it has the autocomplete attribute.
The W3C autofill table tells you which attribute to use for each type of form field.
If the form can be filled in for someone else, this isn't necessary.
diff --git a/app/views/accessibility/partials/check-colour-contrast.njk b/app/views/accessibility/partials/check-colour-contrast.njk index 134a29074..ea8ced412 100644 --- a/app/views/accessibility/partials/check-colour-contrast.njk +++ b/app/views/accessibility/partials/check-colour-contrast.njk @@ -1,5 +1,4 @@It's easier for people to read and interact with content if you use colours that contrast well. The NHS meets at least level AA for contrast and we aim for AAA where possible.
Find out more about colour contrast in the accessibility section of the colour page in the design system.
diff --git a/app/views/accessibility/partials/check-flashes-and-animation.njk b/app/views/accessibility/partials/check-flashes-and-animation.njk index b48236eff..a4ae4b3d9 100644 --- a/app/views/accessibility/partials/check-flashes-and-animation.njk +++ b/app/views/accessibility/partials/check-flashes-and-animation.njk @@ -1,5 +1,4 @@For: Testing
Make sure that users can pause, hide or stop anything that moves, blinks or scrolls automatically and lasts more than 5 seconds.
Pages should not contain anything that flashes more than 3 times in any 1 second. Or the flash should be below the general flash and red flash thresholds.
Read more about the 3 flashes or below threshold on the W3C website.
diff --git a/app/views/accessibility/partials/check-keyboard-accessibility.njk b/app/views/accessibility/partials/check-keyboard-accessibility.njk index b2364e805..5da9cd9c0 100644 --- a/app/views/accessibility/partials/check-keyboard-accessibility.njk +++ b/app/views/accessibility/partials/check-keyboard-accessibility.njk @@ -1,5 +1,4 @@For: Development, Testing
Keyboard accessibility is one of the most important parts of accessibility. It enables other input methods, including switches, speech input and screen readers.
The starting point for keyboard accessibility is to use the correct HTML for links, buttons and form controls. Use components from the service manual, if you can. They've already been tested for keyboard accessibility.
diff --git a/app/views/accessibility/partials/check-orientation-is-not-locked.njk b/app/views/accessibility/partials/check-orientation-is-not-locked.njk index d25958dbd..bc0089823 100644 --- a/app/views/accessibility/partials/check-orientation-is-not-locked.njk +++ b/app/views/accessibility/partials/check-orientation-is-not-locked.njk @@ -1,4 +1,3 @@For: Testing
Use a mobile device and switch from portrait to landscape and back again. You should be able to see all the content and functionality.
diff --git a/app/views/accessibility/partials/check-that-accessibility-is-done.njk b/app/views/accessibility/partials/check-that-accessibility-is-done.njk index c689bb01a..d50ff7b59 100644 --- a/app/views/accessibility/partials/check-that-accessibility-is-done.njk +++ b/app/views/accessibility/partials/check-that-accessibility-is-done.njk @@ -1,5 +1,4 @@For: Product and delivery
It's the product or delivery manager's responsibility to make sure that the product or service is accessible. In most cases it's a matter of making sure that the team is checking their work as they go along.
If in doubt, ask questions early. The sooner you consider accessibility requirements, the easier it is.
diff --git a/app/views/accessibility/partials/define-focus-styles.njk b/app/views/accessibility/partials/define-focus-styles.njk index da24407ec..96094f632 100644 --- a/app/views/accessibility/partials/define-focus-styles.njk +++ b/app/views/accessibility/partials/define-focus-styles.njk @@ -1,5 +1,4 @@For: Design
Everyone should be able to access all interactive components with a keyboard or a similar device. It must be obvious to them which element or link is the current focus position on the page. The browser default is generally not good enough.
Make sure that the focus is clearly visible. You can do this by adding something, like an outline or icon, or changing the colour of part of the component. Check the colour contrast.
We recommend the focus state styles in the service manual.
diff --git a/app/views/accessibility/partials/define-page-structure.njk b/app/views/accessibility/partials/define-page-structure.njk index d7ced8974..bcdfaeb37 100644 --- a/app/views/accessibility/partials/define-page-structure.njk +++ b/app/views/accessibility/partials/define-page-structure.njk @@ -1,5 +1,4 @@You can help people who use assistive technologies understand the structure of the page and navigate it by including "landmarks" (hidden labels for sections of the page). Landmarks also help users looking at multiple pages skip repetitive sections.
Use ARIA landmarks to identify the regions of a page.
diff --git a/app/views/accessibility/partials/define-skip-links.njk b/app/views/accessibility/partials/define-skip-links.njk index e6405b25a..769fd216a 100644 --- a/app/views/accessibility/partials/define-skip-links.njk +++ b/app/views/accessibility/partials/define-skip-links.njk @@ -1,5 +1,4 @@Use a skip link to help keyboard-only users skip to the main content on a page.
Also add a skip link at the start of a long list of links or form fields (for example, over 20 checkboxes in a filter). This lets people who use keyboard-style access with a switch or head-wand skip to the end and avoid having to keep pressing the same key.
Skip links can be invisible by default, but must be very visible when focused.
diff --git a/app/views/accessibility/partials/discuss-any-custom-components.njk b/app/views/accessibility/partials/discuss-any-custom-components.njk index fa5ee7111..32b364b92 100644 --- a/app/views/accessibility/partials/discuss-any-custom-components.njk +++ b/app/views/accessibility/partials/discuss-any-custom-components.njk @@ -1,5 +1,4 @@For: Design, Development
The components in the service manual are well tested and ready to use. Before you design a new component, please test an existing component and show that there's a clear need for something new.
Discuss any new components with other members of your team. You need to make sure that:
For: Testing
Do not use single letter keyboard shortcuts. (Gmail, for example, uses the "j" and "k" keys to move between emails.)
Keyboard shortcuts which use single numbers, punctuation, lowercase letters, uppercase letters or symbol characters can interfere with voice input software.
diff --git a/app/views/accessibility/partials/do-not-include-text-in-images.njk b/app/views/accessibility/partials/do-not-include-text-in-images.njk index c9d3b02fe..93fbb7635 100644 --- a/app/views/accessibility/partials/do-not-include-text-in-images.njk +++ b/app/views/accessibility/partials/do-not-include-text-in-images.njk @@ -1,5 +1,4 @@Users need as much information as possible in text format, so that they can adjust its size, spacing or formatting.
Do not include text in graphical (raster) formats like PNG, JPEG or GIF. They do not work well when users zoom in. Instead put text in HTML (styled with CSS) or use SVG.
This does not apply to logos.
diff --git a/app/views/accessibility/partials/do-not-override-visible-labels.njk b/app/views/accessibility/partials/do-not-override-visible-labels.njk index 7ce675c20..bcf7d7dfb 100644 --- a/app/views/accessibility/partials/do-not-override-visible-labels.njk +++ b/app/views/accessibility/partials/do-not-override-visible-labels.njk @@ -1,4 +1,3 @@For: Testing
Make sure that ARIA or HTML labels for buttons, links or anchors match or contain the same words as visible labels. That applies whether the visible label is in text or an image of text.
diff --git a/app/views/accessibility/partials/do-not-play-audio-automatically.njk b/app/views/accessibility/partials/do-not-play-audio-automatically.njk index a2419cc94..44ae649f9 100644 --- a/app/views/accessibility/partials/do-not-play-audio-automatically.njk +++ b/app/views/accessibility/partials/do-not-play-audio-automatically.njk @@ -1,4 +1,3 @@For: Testing
Audio must not play automatically for more than 3 seconds. It makes it hard for people to hear their screen reader.
diff --git a/app/views/accessibility/partials/do-not-rely-on-colour-or-position-alone.njk b/app/views/accessibility/partials/do-not-rely-on-colour-or-position-alone.njk index 4f51f2921..124a9d584 100644 --- a/app/views/accessibility/partials/do-not-rely-on-colour-or-position-alone.njk +++ b/app/views/accessibility/partials/do-not-rely-on-colour-or-position-alone.njk @@ -1,5 +1,4 @@Do not rely on colour to convey meaning, for example, an instruction. To communicate with people who cannot see well or distinguish colours, you may need to:
For: Testing
If you have any functionality that is triggered by device or user motion (like shaking or tilting), you must provide another way for users to activate it. For example, let the user press a button.
Also make sure that users can disable motion actions.
diff --git a/app/views/accessibility/partials/do-not-rely-on-touch-gestures.njk b/app/views/accessibility/partials/do-not-rely-on-touch-gestures.njk index 2ace0367d..5611a2609 100644 --- a/app/views/accessibility/partials/do-not-rely-on-touch-gestures.njk +++ b/app/views/accessibility/partials/do-not-rely-on-touch-gestures.njk @@ -1,5 +1,4 @@For: Testing
Do not rely on touch, even for interfaces designed for touch screens. You can use touch gestures but you need a standard fallback.
For example, if you swipe between images, you also need a button that does the same thing for people using switch access or screen readers.
diff --git a/app/views/accessibility/partials/do-not-trigger-pop-ups-by-hover-or-focus.njk b/app/views/accessibility/partials/do-not-trigger-pop-ups-by-hover-or-focus.njk index 41fcd5ae7..b09333a18 100644 --- a/app/views/accessibility/partials/do-not-trigger-pop-ups-by-hover-or-focus.njk +++ b/app/views/accessibility/partials/do-not-trigger-pop-ups-by-hover-or-focus.njk @@ -1,5 +1,4 @@For: Testing
Do not trigger additional content by mouse hover or keyboard focus. It causes problems for people using zoom or a screen magnifier.
If you use 3rd party content which does this, make sure you give users a way to dismiss the content without moving the mouse or focus. For example, use the ESC key.
diff --git a/app/views/accessibility/partials/do-not-use-onkeydown-or-onmousedown-for-links-and-buttons.njk b/app/views/accessibility/partials/do-not-use-onkeydown-or-onmousedown-for-links-and-buttons.njk index 1c5fbe1a1..f63f4952a 100644 --- a/app/views/accessibility/partials/do-not-use-onkeydown-or-onmousedown-for-links-and-buttons.njk +++ b/app/views/accessibility/partials/do-not-use-onkeydown-or-onmousedown-for-links-and-buttons.njk @@ -1,4 +1,3 @@For: Testing
For interactive elements, only trigger actions once the user takes their finger or pointer away from the activation target. This gives users a chance to cancel or avoid activating the trigger.
diff --git a/app/views/accessibility/partials/for-small-or-specialist-user-groups-focus-on-testing-the-interface.njk b/app/views/accessibility/partials/for-small-or-specialist-user-groups-focus-on-testing-the-interface.njk index ff3414a41..0241ab623 100644 --- a/app/views/accessibility/partials/for-small-or-specialist-user-groups-focus-on-testing-the-interface.njk +++ b/app/views/accessibility/partials/for-small-or-specialist-user-groups-focus-on-testing-the-interface.njk @@ -1,5 +1,4 @@For: User research
It can be difficult to find people in small or specialist target audiences who also have access needs. In that case, focus on testing the interface with people with access needs.
For: Design, Development, Testing
If you have set a time limit for inactivity (for example, on a multi-step form), make it at least 20 hours.
If you use 3rd party content that has a time limit, it should warn users clearly how much time they have left and let them extend or turn off the time limit.
There are exceptions to this when the time limit is essential, for example, for an online test or real-time event.
diff --git a/app/views/accessibility/partials/highlight-errors-in-forms.njk b/app/views/accessibility/partials/highlight-errors-in-forms.njk index c49f4b1f6..3a1f063bd 100644 --- a/app/views/accessibility/partials/highlight-errors-in-forms.njk +++ b/app/views/accessibility/partials/highlight-errors-in-forms.njk @@ -1,5 +1,4 @@Make sure that error messages clearly describe what went wrong and how to fix the problem.
Include an error message wherever there's a problem with the input and check that it's visibly obvious that the message is connected to that input.
If you have an error summary at the top of a form, check that each error in the list has a link that moves the focus to the relevant form field. This helps users who rely on keyboard navigation.
diff --git a/app/views/accessibility/partials/identify-target-groups-and-accessibility-challenges.njk b/app/views/accessibility/partials/identify-target-groups-and-accessibility-challenges.njk index 7947e3705..7eee2faec 100644 --- a/app/views/accessibility/partials/identify-target-groups-and-accessibility-challenges.njk +++ b/app/views/accessibility/partials/identify-target-groups-and-accessibility-challenges.njk @@ -1,5 +1,4 @@For: User research
In the discovery part of the project, you need to understand how it will affect people with access needs. Consider:
For: User research
In the UK, almost 1 in 5 people have a disability of some kind. Many more have a temporary impairment like an illness or injury. Try to include 1 person with access needs in every 5 people you research with.
Involving people with access needs in user research doesn't just help identify accessibility issues. It shows up general issues that affect everyone.
diff --git a/app/views/accessibility/partials/label-form-fields-clearly.njk b/app/views/accessibility/partials/label-form-fields-clearly.njk index 772883349..4c070c4f3 100644 --- a/app/views/accessibility/partials/label-form-fields-clearly.njk +++ b/app/views/accessibility/partials/label-form-fields-clearly.njk @@ -1,5 +1,4 @@Make sure that every form field has a label that tells users what information they need to enter.
For: User research
It's important that the team supports one another. User research in health can be tiring and emotional. Sometimes users might tell you stories that are hard to hear or you might see them struggle.
It's OK to take some time out during a day of research or, as a user researcher, to ask for someone to stand in for you.
Check in with your team mates during and after research and take time to reflect together.
diff --git a/app/views/accessibility/partials/make-sure-everyone-knows-their-responsibilities.njk b/app/views/accessibility/partials/make-sure-everyone-knows-their-responsibilities.njk index 3639ecddf..e74ab3079 100644 --- a/app/views/accessibility/partials/make-sure-everyone-knows-their-responsibilities.njk +++ b/app/views/accessibility/partials/make-sure-everyone-knows-their-responsibilities.njk @@ -1,4 +1,3 @@For: Product and delivery
Make sure everyone in the team knows what they need to do and is checking their work, using the guidance for different activities.
If a team member doesn't have a basic understanding already, help them get started with accessibility.
diff --git a/app/views/accessibility/partials/make-sure-navigation-is-consistent.njk b/app/views/accessibility/partials/make-sure-navigation-is-consistent.njk index 319f7025d..78b604d6a 100644 --- a/app/views/accessibility/partials/make-sure-navigation-is-consistent.njk +++ b/app/views/accessibility/partials/make-sure-navigation-is-consistent.njk @@ -1,5 +1,4 @@For: Testing
Identify any navigational mechanisms (navigation bars, search fields, and skip links) that appear on multiple pages.
Check that the links or buttons are presented in the same order each time they appear, even if other items are removed or added between them.
If the navigation is defined by templates, you only need to check 1 or 2 pages.
diff --git a/app/views/accessibility/partials/make-sure-your-service-meets-wcag-2-2.njk b/app/views/accessibility/partials/make-sure-your-service-meets-wcag-2-2.njk index fa558f698..e7b3c2d1d 100644 --- a/app/views/accessibility/partials/make-sure-your-service-meets-wcag-2-2.njk +++ b/app/views/accessibility/partials/make-sure-your-service-meets-wcag-2-2.njk @@ -1,6 +1,4 @@For: Design, Development, Product and delivery, Testing
-
WCAG 2.2
diff --git a/app/views/accessibility/partials/make-users-aware-of-status-updates-away-from-current-focus.njk b/app/views/accessibility/partials/make-users-aware-of-status-updates-away-from-current-focus.njk
index c18a6e597..724401112 100644
--- a/app/views/accessibility/partials/make-users-aware-of-status-updates-away-from-current-focus.njk
+++ b/app/views/accessibility/partials/make-users-aware-of-status-updates-away-from-current-focus.njk
@@ -1,5 +1,4 @@
For: Testing Make screen reader users aware of important changes in content during an action in a way that does not interrupt their journey. If you need to let users know the results of an action (for example, updated search results or that they have successfully submitted a form), convey this information programmatically. For: Content, Design, Development, Testing Consider using video as well as text. Some people find it easier to understand. With all video and animation, make sure that: For: User research For: Product and delivery You must show that your team: For: Product and delivery All websites must have an accessibility statement, in line with with accessibility regulations. Read more about the accessibility requirements for public sector bodies on GOV.UK. For the statement, you must test every area of your product or service and report on issues that people with access needs might face. You should have as few accessibility issues as possible. Following this accessibility guidance will help you with that. GOV.UK has published a sample accessibility statement. You can see a live example on the NHS Your data matters service. For: User research Ask your agency to include people with access needs. If they say it's too hard or want to charge extra for this, get quotes from other recruiters. You should be able to find an agency that will recruit people with different needs at no extra cost.Make users aware of status updates away from current focus
-Make video and other multimedia content accessible
-
diff --git a/app/views/accessibility/partials/make-your-research-more-accessible-on-the-day.njk b/app/views/accessibility/partials/make-your-research-more-accessible-on-the-day.njk
index 7a00e9952..d7beb8eea 100644
--- a/app/views/accessibility/partials/make-your-research-more-accessible-on-the-day.njk
+++ b/app/views/accessibility/partials/make-your-research-more-accessible-on-the-day.njk
@@ -1,5 +1,4 @@
Make your research more accessible on the day
-
Monitor and record your work
-
-Publish an accessibility statement
-Recruit people with access needs
-Recruitment agencies
For: User research
Check that the thing you're testing is technically accessible - for example, that it works for people who use screen readers or voice input.
This applies to your survey software too. If you're using Qualtrics, as many user researchers do, be aware that it's not fully accessible.
diff --git a/app/views/accessibility/partials/set-language.njk b/app/views/accessibility/partials/set-language.njk index e5d5651dd..3b77848c8 100644 --- a/app/views/accessibility/partials/set-language.njk +++ b/app/views/accessibility/partials/set-language.njk @@ -1,5 +1,4 @@For: Development, Testing
You need a small bit of markup on every page for screenreaders (and search engines) to know what language the content (or a part of the content) is in.
For: Content, Development, Testing
A good page title helps users find what they want and recognise they're in the right place. It's the link that shows in search results and the first thing a screenreader will read out when the user lands on a page.
Each page title must be unique and descriptive. Keep it concise and consider putting important keywords near the beginning.
diff --git a/app/views/accessibility/partials/share-your-research.njk b/app/views/accessibility/partials/share-your-research.njk index aaeaa076d..3c3ab8ad0 100644 --- a/app/views/accessibility/partials/share-your-research.njk +++ b/app/views/accessibility/partials/share-your-research.njk @@ -1,5 +1,4 @@For: User research
Share your research findings with colleagues, taking out any personal information.
Feedback about NHS components and help us improve this guidance.
diff --git a/app/views/accessibility/partials/test-that-text-sizes-and-zooms-correctly.njk b/app/views/accessibility/partials/test-that-text-sizes-and-zooms-correctly.njk index a3660c0b0..45b9a348a 100644 --- a/app/views/accessibility/partials/test-that-text-sizes-and-zooms-correctly.njk +++ b/app/views/accessibility/partials/test-that-text-sizes-and-zooms-correctly.njk @@ -1,5 +1,4 @@For: Development, Testing
People use their browser to change the size of content, and people with low vision may use that to a more extreme level. The guidelines specify a level of 320 (CSS) px wide. That is equivalent to 400% for a 1280px wide browser.
Users can also override the font-family and spacing for text, which can break a fragile layout. We use this text spacing bookmarklet to test with.
diff --git a/app/views/accessibility/partials/understand-participants-needs-before-you-test.njk b/app/views/accessibility/partials/understand-participants-needs-before-you-test.njk index ec14f6c89..ebeb0d8ef 100644 --- a/app/views/accessibility/partials/understand-participants-needs-before-you-test.njk +++ b/app/views/accessibility/partials/understand-participants-needs-before-you-test.njk @@ -1,5 +1,4 @@For: User research
Make it easy for people with access needs to take part in the research by planning the venue, the tech and the "paperwork" around their needs.
For: Testing
There are 3 types of accessibility testing:
For: Design, Development, Testing
Some images are "functional". That means that they trigger an action. If people can't see the image, they need an alternative.
Use "alt‑text" for images like PNG or JPEG. W3C has information about how to deal with different kinds of functional image, including logos.
The NHS website (nhs.uk) prefers inline SVG files for functional images. SVGs don't have an alt attribute. Instead we use aria-hidden="true" and, if there is no link text, "visually-hidden" in span tags.
diff --git a/app/views/accessibility/partials/use-alternative-text-for-images-in-content.njk b/app/views/accessibility/partials/use-alternative-text-for-images-in-content.njk index c0f35bc3c..5d6929153 100644 --- a/app/views/accessibility/partials/use-alternative-text-for-images-in-content.njk +++ b/app/views/accessibility/partials/use-alternative-text-for-images-in-content.njk @@ -1,7 +1,7 @@People who cannot see a meaningful image need an alternative to understand the content. You need to add "alt-text" to explain what's in the image. Alt-text is not usually visible but is read out by screen readers or displayed if an image does not load or if images have been switched off.
You can see what alt-text an image has by viewing it with Chrome's Web Developer toolbar.
+For: Development, Testing
ARIA (Accessibility Rich Internet Applications) adds extra information that lets people who use assistive technologies know what's going on. If a component needs more description than HTML provides, you need to mark it up with an ARIA pattern.
We use simple examples of ARIA in some of the service manual components, such as details, breadcrumbs and error messages.
diff --git a/app/views/accessibility/partials/use-headings-correctly.njk b/app/views/accessibility/partials/use-headings-correctly.njk index e4e7b1d98..e3c2571df 100644 --- a/app/views/accessibility/partials/use-headings-correctly.njk +++ b/app/views/accessibility/partials/use-headings-correctly.njk @@ -1,5 +1,4 @@Everyone relies on meaningful headings to navigate the page but they are especially important for some people with access needs. Make sure your headings reflect the page structure.
Avoid using PDFs as they are not accessible. If you must use a PDF, make sure the content is also available in HTML form.
Read more about PDFs and other non-HTML documents in the content guide.
diff --git a/app/views/accessibility/partials/use-tables-to-show-relationships-between-data.njk b/app/views/accessibility/partials/use-tables-to-show-relationships-between-data.njk index 4055068d7..80fd7869d 100644 --- a/app/views/accessibility/partials/use-tables-to-show-relationships-between-data.njk +++ b/app/views/accessibility/partials/use-tables-to-show-relationships-between-data.njk @@ -1,5 +1,4 @@For: Content
Tables make it easier for users to understand logical relationships between bits of data or information.
Only use tables when there is a relationship between the "header" cells and the "data" cells in the grid. Assistive technologies announce the header with the data it refers to.
diff --git a/app/views/accessibility/partials/write-content-thats-easy-to-understand.njk b/app/views/accessibility/partials/write-content-thats-easy-to-understand.njk index df83d1942..81402cb19 100644 --- a/app/views/accessibility/partials/write-content-thats-easy-to-understand.njk +++ b/app/views/accessibility/partials/write-content-thats-easy-to-understand.njk @@ -1,4 +1,3 @@For: Content
Clear content helps everyone and it's the most important thing you can do to make things accessible. It will help more people than any other accessibility requirement.
NHS services should follow the content guide, including the guidance on health literacy and inclusive content.
diff --git a/app/views/accessibility/partials/write-good-link-and-form-control-names.njk b/app/views/accessibility/partials/write-good-link-and-form-control-names.njk index 2a60a3438..894cb9b67 100644 --- a/app/views/accessibility/partials/write-good-link-and-form-control-names.njk +++ b/app/views/accessibility/partials/write-good-link-and-form-control-names.njk @@ -1,15 +1,14 @@Links or buttons need to make sense out of context as some people experience them that way.
-| Section | +Update | +
|---|---|
| Accessibility | +
+ Removed same-page profession links as they have caused confusion in testing + |
+
| Section | +Update | +
|---|---|
| Accessibility | +
+ Removed same-page profession links as they have caused confusion in testing + |
+
| Section | -Update | -||
|---|---|---|---|
| Design system | -
- Replaced image in image component - |
+ ||
| Section | +Update |
Replaced image in image component
+| Section | -Update | -||
|---|---|---|---|
| Community and contribution | -
- Added Community resources page to list resources based on the NHS design system. - |
- ||
| Design system | -
- Added a task list component and a pattern to help users complete multiple tasks -Changed side navigation in patterns - |
+
| Section | +Update |
|---|
Added Community resources page to list resources based on the NHS design system.
+Added a task list component and a pattern to help users complete multiple tasks
+Changed side navigation in patterns
+