diff --git a/src/accessibility/accessibility-strategy/index.md b/src/accessibility/accessibility-strategy/index.md
index 5b75011233..4b5fad5594 100644
--- a/src/accessibility/accessibility-strategy/index.md
+++ b/src/accessibility/accessibility-strategy/index.md
@@ -149,7 +149,7 @@ If the GOV.UK Design System team can confirm the accessibility concern internall
If the GOV.UK Design System team is unable to confirm the accessibility concern or disagrees with the raised concern, then the following steps are taken to resolve the disagreement:
1. Assess the severity of the accessibility concern (as defined in the section above)
-2. If the accessibility concern is not [high-severity](#determining-severity-of-an-accessibility-concern), continue to hold discussions within the team and any frontend and accessibility communities where applicable
+2. If the accessibility concern is [not determined to be high-severity](#determining-severity-of-an-accessibility-concern), continue to hold discussions within the team and any frontend and accessibility communities where applicable
#### Level 3 for disagreement escalation
@@ -221,7 +221,7 @@ The team uses a variety of tools during the development process, including, but
The team also uses general inspection techniques, including:
-- [sensory inspection](https://web.dev/a11y-tips-for-web-dev/) (visual, auditory, etc.)
+- sensory inspection (visual, auditory, etc.)
- HTML inspection using [browser developer tools](https://developer.mozilla.org/en-US/docs/Learn/Common_questions/What_are_browser_developer_tools)
- [accessibility tree](https://developer.mozilla.org/en-US/docs/Glossary/Accessibility_tree) inspection
@@ -238,15 +238,15 @@ As of May 2023, we have improved our automated accessibility testing processes:
3. We now run our tests in [@axe-core/puppeteer](https://github.com/dequelabs/axe-core-npm/blob/develop/packages/puppeteer) to include colour contrast checks, but we still use [jest-axe](https://github.com/nickcolley/jest-axe) to report issues.
4. We added [html-validate](https://html-validate.org/) to our automated tests. This helps us test for HTML compliance, including [various WCAG 2.1 checks available through html-validate](https://html-validate.org/wcag.html).
-We have an accessibility activity issue in GitHub where we track our efforts to [enhance automated testing in our development pipeline](https://github.com/alphagov/govuk-frontend/issues/3041).
+We have [an accessibility activity issue in GitHub where we track our efforts to enhance automated testing in our development pipeline](https://github.com/alphagov/govuk-frontend/issues/3041).
### Manual testing
-Manual testing for a style, component or pattern follows our own [accessibility acceptance criteria](https://github.com/alphagov/govuk-frontend/blob/main/docs/contributing/test-components-using-accessibility-acceptance-criteria.md).
+Manual testing for a style, component or pattern follows our own [guidance on establishing accessibility acceptance criteria](https://github.com/alphagov/govuk-frontend/blob/main/docs/contributing/test-components-using-accessibility-acceptance-criteria.md).
Additionally, the team follows the [GOV.UK Service manual guidance on testing with assistive technologies](https://www.gov.uk/service-manual/technology/testing-with-assistive-technologies).
-The team records results on our [accessibility testing spreadsheet (Google Sheet)](https://docs.google.com/spreadsheets/d/1O0rWoH3ah_rj2iJ2We9VfyHNOr0gOVItXRy3vKzuYSw/edit?usp=sharing), which lists the specific browser and assistive technology combinations with which we test.
+The team records results on our [accessibility testing template spreadsheet (Google Sheet)](https://docs.google.com/spreadsheets/d/1O0rWoH3ah_rj2iJ2We9VfyHNOr0gOVItXRy3vKzuYSw/edit?usp=sharing), which lists the specific browser and assistive technology combinations with which we test.
Currently, the team uses desktop-type devices to access assistive technologies in the following ways:
@@ -255,7 +255,7 @@ Currently, the team uses desktop-type devices to access assistive technologies i
- high contrast and other display modes through Assistiv Labs and browsers
- speech recognition software through Windows testing computers and macOS
-As of November 2022, there are limitations to how the team performs and records manual testing. These limitations may be addressed by the proposed ‘[Standardise and improve our manual testing methodology](https://github.com/alphagov/govuk-design-system/issues/2456)’ activity.
+As of November 2022, there are limitations to how the team performs and records manual testing. These limitations may be addressed by [the proposed ‘Standardise and improve our manual testing methodology activity](https://github.com/alphagov/govuk-design-system/issues/2456)’.
### User research and usability testing
@@ -265,7 +265,7 @@ Accessibility user research often includes activities such as:
- user interviews
- surveys
-[User research must include disabled people](https://www.gov.uk/service-manual/helping-people-to-use-your-service/making-your-service-accessible-an-introduction#meeting-government-accessibility-requirements) and should also include people with a variety of access needs and impairment types.
+To ensure services are accessible, user research must include disabled people](https://www.gov.uk/service-manual/helping-people-to-use-your-service/making-your-service-accessible-an-introduction#meeting-government-accessibility-requirements) and should also include people with a variety of access needs and impairment types.
The majority of accessibility user research results are contributed by service teams and the broader communities that use the GOV.UK Design System.
@@ -275,9 +275,9 @@ The team might determine that further accessibility user research is necessary f
Examples of when the team and other service teams have completed additional accessibility user research include:
-- [Focus state](https://designnotes.blog.gov.uk/2019/07/29/weve-made-the-gov-uk-design-system-more-accessible/) (2019)
-- [General component accessibility research](https://github.com/alphagov/govuk-design-system/issues/1377) (2020)
-- [Hide this Page component](https://github.com/alphagov/govuk-design-system/issues/2195) (2022)
+- [Making the focus state more accessible](https://designnotes.blog.gov.uk/2019/07/29/weve-made-the-gov-uk-design-system-more-accessible/)
+- [Externally testing our components with a research prototype](https://github.com/alphagov/govuk-frontend/issues/2000)
+- [Exit this page accessibility research](https://github.com/alphagov/govuk-design-system/issues/2195)
## Recording accessibility concerns
@@ -299,7 +299,7 @@ If the GOV.UK Design System does not meet the requirements of level AA accessibi
One of the goals of this strategy is to outline the work needed to improve the accessibility of the GOV.UK Design System. We document this work as a set of proposed activities, presented in a GitHub project.
-[Accessibility strategy: proposed activities](https://github.com/orgs/alphagov/projects/46)
+[View the Accessibility strategy: proposed activities GitHub project](https://github.com/orgs/alphagov/projects/46).
This GitHub project allows service teams to see the areas of work under consideration, and is intended to enhance the success of the included activities. The project will be reviewed quarterly, to align with quarterly planning.
diff --git a/src/accessibility/index.md b/src/accessibility/index.md
index f04f3e8446..07515c3dbc 100644
--- a/src/accessibility/index.md
+++ b/src/accessibility/index.md
@@ -5,7 +5,7 @@ description: How we make the GOV.UK Design System accessible and our strategy fo
showSubNav: true
---
-Our work to make the GOV.UK Design System meet public sector accessibility regulations is a continuous and iterative process. You must [make sure your service is accessible](https://www.gov.uk/guidance/accessibility-requirements-for-public-sector-websites-and-apps). We outline our approach on our [accessibility strategy](/accessibility/accessibility-strategy/).
+Our work to make the GOV.UK Design System meet public sector accessibility regulations is a continuous and iterative process. You must [make sure your service is accessible](https://www.gov.uk/guidance/accessibility-requirements-for-public-sector-websites-and-apps). We outline our approach on [our accessibility strategy](/accessibility/accessibility-strategy/).
Using the GOV.UK Design System in a service does not immediately make that service accessible. You’ll need additional research, design, development and testing work to make sure your service is accessible, even when using accessible styles, components and patterns.
diff --git a/src/accessibility/wcag-2.2/index.md b/src/accessibility/wcag-2.2/index.md
index 357c6c0d63..1d6cb4ada3 100644
--- a/src/accessibility/wcag-2.2/index.md
+++ b/src/accessibility/wcag-2.2/index.md
@@ -21,10 +21,10 @@ WCAG 2.2 was published in October 2023. You’ll need to comply with the new cri
## What you need to do
-1. Revisit the [Government Digital Service (GDS) guidance](https://www.gov.uk/guidance/accessibility-requirements-for-public-sector-websites-and-apps) on what accessibility is and why your service needs to invest in it
+1. Revisit the [Government Digital Service (GDS) guidance on what accessibility is and why your service needs to invest in it](https://www.gov.uk/guidance/accessibility-requirements-for-public-sector-websites-and-apps)
2. Read [What’s new in WCAG 2.2](https://www.w3.org/WAI/standards-guidelines/wcag/new-in-22/) to understand the new criteria your service will need to comply with
3. Ask your wider organisation for support to prepare for work needed to meet WCAG 2.2
-4. Update your service to use [GOV.UK Frontend v5.0.0](https://frontend.design-system.service.gov.uk/changes-to-govuk-frontend-v5/) or later, to make it easier to make changes in your service
+4. [Update your service to use GOV.UK Frontend v5.0.0 or later](https://frontend.design-system.service.gov.uk/changes-to-govuk-frontend-v5/), to make it easier to make changes in your service
5. Review the lists on this page of affected components and patterns in the Design System
6. Assess your service to see how many affected components and patterns are in use
7. Plan and implement the changes needed to your service
@@ -37,7 +37,7 @@ We've made changes to these components and patterns to comply with WCAG 2.2 leve
See an [explanation of every success criteria in WCAG 2.2](https://www.w3.org/WAI/standards-guidelines/wcag/new-in-22/) on the W3C website.
-[Images](/styles/images/) also includes guidance to help ensure icons and images in your service meet Target size (minimum).
+[Our Images page](/styles/images/) also includes guidance to help ensure icons and images in your service meet Target size (minimum).
{{ govukTable({
caption: "Components",
diff --git a/src/community/code-of-conduct/index.md b/src/community/code-of-conduct/index.md
index e2947d5ebb..d72f945ff7 100644
--- a/src/community/code-of-conduct/index.md
+++ b/src/community/code-of-conduct/index.md
@@ -43,4 +43,4 @@ List of organisers:
- Romaric Pascal
- Trang Erskine
-(These guidelines are adapted from the [Practical Service Design](http://www.practicalservicedesign.com/getting-started-on-slack/) community guidelines, [Afrotech Fest](https://www.afrotechfest.co.uk/coc/), [Code for America](http://www.cvent.com/events/code-for-america-summit-2018/custom-40-e12d85b157b94d69b80d8911cc641d36.aspx), [UKGovcamp](https://www.ukgovcamp.com/code-of-conduct/), and [Services Week 2021](https://docs.google.com/document/d/1vQchJh-s6Fu6F4bN8UFM4lvRChe8ERgsE5whf9pUfjA/edit?usp=sharing) codes of conduct.)
+(These guidelines are adapted from the [Practical Service Design](http://www.practicalservicedesign.com/getting-started-on-slack/) community guidelines, [Afrotech Fest code of conduct](https://www.afrotechfest.co.uk/coc/), [Code for America code of conduct](http://www.cvent.com/events/code-for-america-summit-2018/custom-40-e12d85b157b94d69b80d8911cc641d36.aspx), [UKGovcamp code of conduct](https://www.ukgovcamp.com/code-of-conduct/), and [Services Week 2021 code of conduct](https://docs.google.com/document/d/1vQchJh-s6Fu6F4bN8UFM4lvRChe8ERgsE5whf9pUfjA/edit?usp=sharing) codes of conduct.)
diff --git a/src/community/contribution-criteria/index.md b/src/community/contribution-criteria/index.md
index 57def41466..85ca815057 100644
--- a/src/community/contribution-criteria/index.md
+++ b/src/community/contribution-criteria/index.md
@@ -97,7 +97,7 @@ Before a new component or pattern is published the working group reviews the imp
{
html: 'The implementation is versatile enough that the component or pattern can be used in a range of different services that may need it.
For example, a versatile date input component could be set up to ask for a year only, a month and year only, a precise date, or any other combination you may need.
- The component or pattern must also have been tested and shown to work with a range of browsers, assistive technologies and devices.
'
+ The component or pattern must also have been tested and shown to work with a range of browsers, assistive technologies and devices.
'
}
]
]
diff --git a/src/community/design-system-day-2023/index.md b/src/community/design-system-day-2023/index.md
index e4b20898a0..60a8693dfe 100644
--- a/src/community/design-system-day-2023/index.md
+++ b/src/community/design-system-day-2023/index.md
@@ -28,7 +28,7 @@ order: 14
text: "Location"
},
value: {
- html: 'Dynamic Earth, Edinburgh, and online'
+ html: 'Dynamic Earth, Edinburgh, and online'
}
}
]
@@ -38,7 +38,7 @@ order: 14
### Day 1
-You can now watch (or re-watch) the [talks and panel discussions](/community/design-system-day-2023/session-information/#day-1-sessions) that happened on day 1 of Design System Day 2023 in Edinburgh.
+You can now [watch (or re-watch) the talks and panel discussions](/community/design-system-day-2023/session-information/#day-1-sessions) that happened on day 1 of Design System Day 2023 in Edinburgh.
You can also read [speaker and panelist biographies](/community/design-system-day-2023/speaker-information/#day-1-speakers) for those who talked and presented at the event.
diff --git a/src/community/develop-a-component-or-pattern/index.md b/src/community/develop-a-component-or-pattern/index.md
index aaa47ccafd..4a3dc2f397 100644
--- a/src/community/develop-a-component-or-pattern/index.md
+++ b/src/community/develop-a-component-or-pattern/index.md
@@ -11,7 +11,7 @@ The Design System team focuses on developing [prioritised components and pattern
If you see something you'd like to work on, join the discussion in the contribution's issue page or email the Design System team at .
-If you have an idea for a new component or pattern that’s not already on the list, [propose it](/community/propose-a-component-or-pattern/).
+If you have an idea for a new component or pattern that’s not already on the list, [see how to propose a component or pattern](/community/propose-a-component-or-pattern/).
## Plan your work with the Design System team
diff --git a/src/community/propose-a-component-or-pattern/index.md b/src/community/propose-a-component-or-pattern/index.md
index 908644fd0a..3ad1db6ce7 100644
--- a/src/community/propose-a-component-or-pattern/index.md
+++ b/src/community/propose-a-component-or-pattern/index.md
@@ -9,7 +9,7 @@ order: 3
Anyone can propose a new component or pattern for the GOV.UK Design System.
-Proposals need to show that the component or pattern being suggested would be [useful and unique](/community/contribution-criteria/).
+Proposals need to show that the component or pattern being suggested would [meet our contribution criteria](/community/contribution-criteria/).
Follow the steps to propose a component or pattern for the Design System.
@@ -23,7 +23,7 @@ If you'd like to work on it, read how to [develop a component or pattern](/commu
## 2. Raise an issue
-If your idea is not on the list, [raise an issue](https://github.com/alphagov/govuk-design-system-backlog/issues/new). Once you do, [let us know](/get-in-touch/) so a member of the Design System team can review your proposal and add it to the list.
+If your idea is not on the list, [raise an issue](https://github.com/alphagov/govuk-design-system-backlog/issues/new). Once you do, [contact us](/get-in-touch/) so a member of the Design System team can review your proposal and add it to the list.
At this stage, you just need to present your idea and evidence of the user needs. You can include screenshots or links to versions of the component or pattern in use, but avoid spending time working on a specific design or writing code.
diff --git a/src/community/resources-and-tools/index.md b/src/community/resources-and-tools/index.md
index 2959006dec..cd4d6020c0 100644
--- a/src/community/resources-and-tools/index.md
+++ b/src/community/resources-and-tools/index.md
@@ -38,16 +38,16 @@ SVG images for creating flow diagrams of GOV.UK services.
## Create prototypes and wireframes
-[Balsamiq wireframes](https://github.com/enoranidi/govuk-design-system-balsamiq) -
+[GOV.UK Balsamiq wireframes](https://github.com/enoranidi/govuk-design-system-balsamiq) -
Balsamiq wireframes based on the GOV.UK Design System.
-[Figma resources](https://www.figma.com/file/NWuFffKvPQhl3aJ9nKU0p3/GOV.UK-Design-System) -
+[GOV.UK Figma resources](https://www.figma.com/file/NWuFffKvPQhl3aJ9nKU0p3/GOV.UK-Design-System) -
Figma library of styles and components based on the GOV.UK Design System.
-[Mural resources](https://github.com/vickytnz/govuk-elements-mural) -
+[GOV.UK Mural resources](https://github.com/vickytnz/govuk-elements-mural) -
Mural template based on the GOV.UK Design System.
-[Sketch Wireframing Kit](https://github.com/dwp/sketch_wireframing_kit) -
+[GOV.UK Sketch Wireframing Kit](https://github.com/dwp/sketch_wireframing_kit) -
Sketch wireframes based on the GOV.UK Design System.
## Build front ends
@@ -100,13 +100,12 @@ A Vue 3 component library for GOV.UK Frontend
## Write code
-You can download GOV.UK Frontend Nunjucks macro snippets for:
+[GOV.UK Design System snippets for Nova](https://extensions.panic.com/extensions/ca/ca.GOVUKDesignSystemSnippets/).
-- [Nova](https://extensions.panic.com/extensions/ca/ca.GOVUKDesignSystemSnippets/)
-- [Visual Studio Code](https://marketplace.visualstudio.com/items?itemName=simonwhatley.govuk-design-system-snippets)
+[GOV.UK Design System snippets for Visual Studio Code](https://marketplace.visualstudio.com/items?itemName=simonwhatley.govuk-design-system-snippets).
## Help improve this page
-To help make sure that this page is useful, relevant and up to date, you can [propose a change](https://github.com/alphagov/govuk-design-system/edit/main/src/community/resources-and-tools/index.md) – read more about [how to propose changes in GitHub](/community/propose-a-content-change-using-github/).
+To help make sure that this page is useful, relevant and up to date, you can [propose a change to this page](https://github.com/alphagov/govuk-design-system/edit/main/src/community/resources-and-tools/index.md) – read more about [how to propose changes in GitHub](/community/propose-a-content-change-using-github/).
If you want to submit a resource or tool, check that it meets the [contribution criteria for resources](/community/contribution-criteria/#developing-a-community-resource-or-tool) first.