diff --git a/.github/actions/deploy-to-heroku/action.yml b/.github/actions/deploy-to-heroku/action.yml index 789ebdb4..b5e4a3df 100644 --- a/.github/actions/deploy-to-heroku/action.yml +++ b/.github/actions/deploy-to-heroku/action.yml @@ -17,7 +17,7 @@ runs: steps: - name: Login to Heroku - uses: AkhileshNS/heroku-deploy@v3.12.14 + uses: AkhileshNS/heroku-deploy@v3.13.15 with: heroku_api_key: ${{ inputs.heroku-api-key }} heroku_app_name: '' diff --git a/.github/actions/deploy-to-netlify/action.yml b/.github/actions/deploy-to-netlify/action.yml index e402ef0c..8b31c565 100644 --- a/.github/actions/deploy-to-netlify/action.yml +++ b/.github/actions/deploy-to-netlify/action.yml @@ -31,7 +31,7 @@ runs: - id: deploy name: Deploy - uses: nwtgck/actions-netlify@v2.0.0 + uses: nwtgck/actions-netlify@v3.0.0 with: publish-dir: "${{ inputs.app && format('apps/{0}/', inputs.app) }}pkg/netlify/publish/" functions-dir: "${{ inputs.app && format('apps/{0}/', inputs.app) }}pkg/netlify/functions/" diff --git a/.github/actions/scan-app/action.yml b/.github/actions/scan-app/action.yml index dbbd63de..a22df3d8 100644 --- a/.github/actions/scan-app/action.yml +++ b/.github/actions/scan-app/action.yml @@ -31,13 +31,13 @@ runs: run: | PRETTY_TARGET="${TARGET#https://}" echo "write-issue=$([[ \"${GITHUB_REF#refs/heads/}\" != \"${BASELINE_BRANCH}\" ]] && echo 'false' || echo 'true')" >> ${GITHUB_OUTPUT} - echo "fail-action=$([[ \"${GITHUB_REF#refs/heads/}\" != \"${BASELINE_BRANCH}\" ]] && echo 'true' || true)" >> ${GITHUB_OUTPUT} + echo "fail-action=$([[ \"${GITHUB_REF#refs/heads/}\" != \"${BASELINE_BRANCH}\" ]] && echo 'true' || echo 'false')" >> ${GITHUB_OUTPUT} echo "prefix=${PRETTY_TARGET:-${APP}}" >> ${GITHUB_OUTPUT} echo "target=${TARGET:-http://localhost:8080}" >> ${GITHUB_OUTPUT} - name: ZAP Scan (baseline) if: inputs.smoke - uses: zaproxy/action-baseline@v0.7.0 + uses: zaproxy/action-baseline@v0.12.0 with: token: ${{ inputs.token }} target: ${{ steps.info.outputs.target }} @@ -49,7 +49,7 @@ runs: - name: ZAP Scan (full) if: ${{ !inputs.smoke }} - uses: zaproxy/action-full-scan@v0.4.0 + uses: zaproxy/action-full-scan@v0.10.0 with: token: ${{ inputs.token }} target: ${{ steps.info.outputs.target }} diff --git a/.github/actions/scan-code/action.yml b/.github/actions/scan-code/action.yml index f14924d0..416d831c 100644 --- a/.github/actions/scan-code/action.yml +++ b/.github/actions/scan-code/action.yml @@ -5,9 +5,9 @@ runs: steps: - name: Initialize CodeQL - uses: github/codeql-action/init@v2 + uses: github/codeql-action/init@v3 with: languages: 'javascript' - name: Perform CodeQL Analysis - uses: github/codeql-action/analyze@v2 + uses: github/codeql-action/analyze@v3 diff --git a/.github/actions/scan-dependencies/action.yml b/.github/actions/scan-dependencies/action.yml index 2ba00105..025a9ddd 100644 --- a/.github/actions/scan-dependencies/action.yml +++ b/.github/actions/scan-dependencies/action.yml @@ -9,7 +9,7 @@ runs: steps: - name: Cache vdb - uses: actions/cache@v3 + uses: actions/cache@v4 with: path: | ${{ github.workspace }}/vdb diff --git a/.github/actions/setup/action.yml b/.github/actions/setup/action.yml index 50f75241..c7558a19 100644 --- a/.github/actions/setup/action.yml +++ b/.github/actions/setup/action.yml @@ -19,19 +19,19 @@ runs: sudo update-locale LANG=${{ env.LANG }} - name: Setup PNPM - uses: pnpm/action-setup@v2.2.4 + uses: pnpm/action-setup@v3.0.0 with: version: 7.33.6 run_install: false - name: Setup Node.js - uses: actions/setup-node@v3 + uses: actions/setup-node@v4 with: node-version: ${{ inputs.node }} cache: 'pnpm' - name: Cache Cypress.io - uses: actions/cache@v3 + uses: actions/cache@v4 env: cache-hash: ${{ hashFiles('pnpm-lock.yaml') }} with: @@ -40,7 +40,7 @@ runs: - name: Pull dependencies if: ${{ !inputs.frozen-lockfile || inputs.frozen-lockfile == 'false' }} - uses: pnpm/action-setup@v2.2.4 + uses: pnpm/action-setup@v3.0.0 with: version: 7.33.6 run_install: | @@ -49,7 +49,7 @@ runs: - name: Pull dependencies (frozen lock-file) if: ${{ inputs.frozen-lockfile && inputs.frozen-lockfile != 'false' }} - uses: pnpm/action-setup@v2.2.4 + uses: pnpm/action-setup@v3.0.0 with: version: 7.33.6 run_install: true diff --git a/.github/workflows/change-assurance.yml b/.github/workflows/change-assurance.yml index 8b4c3a76..3f45ee61 100644 --- a/.github/workflows/change-assurance.yml +++ b/.github/workflows/change-assurance.yml @@ -16,7 +16,7 @@ jobs: steps: - name: Checkout repository - uses: actions/checkout@v3 + uses: actions/checkout@v4 - name: Scan code-base uses: ./.github/actions/scan-code @@ -30,7 +30,7 @@ jobs: steps: - name: Check out repository - uses: actions/checkout@v3 + uses: actions/checkout@v4 - name: Setup uses: ./.github/actions/setup @@ -50,7 +50,7 @@ jobs: steps: - name: Check out repository - uses: actions/checkout@v3 + uses: actions/checkout@v4 - name: Setup uses: ./.github/actions/setup @@ -71,7 +71,7 @@ jobs: steps: - name: Check out repository - uses: actions/checkout@v3 + uses: actions/checkout@v4 - name: Setup uses: ./.github/actions/setup @@ -84,7 +84,7 @@ jobs: app: ${{ matrix.app }} - name: Save build directory - uses: actions/upload-artifact@v3 + uses: actions/upload-artifact@v4 with: name: 'build-${{ matrix.app }}' path: "${{ matrix.app && format('apps/{0}/', matrix.app) }}dist" @@ -103,7 +103,7 @@ jobs: steps: - name: Check out repository - uses: actions/checkout@v3 + uses: actions/checkout@v4 - name: Setup uses: ./.github/actions/setup @@ -111,7 +111,7 @@ jobs: node: 18 - name: Download build directory - uses: actions/download-artifact@v3 + uses: actions/download-artifact@v4 with: name: 'build-${{ matrix.app }}' path: "${{ matrix.app && format('apps/{0}/', matrix.app) }}dist" diff --git a/.github/workflows/deploy-to-heroku.yml b/.github/workflows/deploy-to-heroku.yml index 0abbc91f..1afa91ac 100644 --- a/.github/workflows/deploy-to-heroku.yml +++ b/.github/workflows/deploy-to-heroku.yml @@ -27,7 +27,7 @@ jobs: steps: - name: Check out repository - uses: actions/checkout@v3 + uses: actions/checkout@v4 - name: Setup uses: ./.github/actions/setup @@ -58,7 +58,7 @@ jobs: steps: - name: Check out repository - uses: actions/checkout@v3 + uses: actions/checkout@v4 - name: Setup uses: ./.github/actions/setup diff --git a/.github/workflows/deploy-to-netlify.yml b/.github/workflows/deploy-to-netlify.yml index 5b2c264c..39067c53 100644 --- a/.github/workflows/deploy-to-netlify.yml +++ b/.github/workflows/deploy-to-netlify.yml @@ -31,7 +31,7 @@ jobs: steps: - name: Check out repository - uses: actions/checkout@v3 + uses: actions/checkout@v4 - name: Setup uses: ./.github/actions/setup @@ -64,7 +64,7 @@ jobs: steps: - name: Check out repository - uses: actions/checkout@v3 + uses: actions/checkout@v4 - name: Setup uses: ./.github/actions/setup diff --git a/.github/workflows/deploy.yml b/.github/workflows/deploy.yml index 9296f130..87d795d8 100644 --- a/.github/workflows/deploy.yml +++ b/.github/workflows/deploy.yml @@ -12,7 +12,7 @@ jobs: steps: - name: Check out repository - uses: actions/checkout@v3 + uses: actions/checkout@v4 with: fetch-depth: 0 @@ -22,7 +22,7 @@ jobs: node: 18 - name: Push Storybook to Chromatic - uses: chromaui/action@v1 + uses: chromaui/action@v11 with: token: ${{ secrets.GITHUB_TOKEN }} projectToken: ${{ secrets.CHROMATIC_PROJECT_TOKEN }} diff --git a/.github/workflows/publish.yml b/.github/workflows/publish.yml index fb36d646..d61c8fe8 100644 --- a/.github/workflows/publish.yml +++ b/.github/workflows/publish.yml @@ -12,7 +12,7 @@ jobs: steps: - name: Check out repository - uses: actions/checkout@v3 + uses: actions/checkout@v4 with: token: ${{ secrets.PAT }} diff --git a/.github/workflows/static-security-analysis.yml b/.github/workflows/static-security-analysis.yml index 5e44cf55..c3beefcf 100644 --- a/.github/workflows/static-security-analysis.yml +++ b/.github/workflows/static-security-analysis.yml @@ -14,7 +14,7 @@ jobs: fail-fast: false steps: - name: Checkout repository - uses: actions/checkout@v3 + uses: actions/checkout@v4 - name: Scan code-base uses: ./.github/actions/scan-code diff --git a/.github/workflows/update-built-files.yml b/.github/workflows/update-built-files.yml index 17f222c3..6f602378 100644 --- a/.github/workflows/update-built-files.yml +++ b/.github/workflows/update-built-files.yml @@ -12,7 +12,7 @@ jobs: steps: - name: Check out repository - uses: actions/checkout@v3 + uses: actions/checkout@v4 with: token: ${{ secrets.PAT }} @@ -41,7 +41,7 @@ jobs: steps: - name: Checkout repository - uses: actions/checkout@v3 + uses: actions/checkout@v4 - name: Scan code-base uses: ./.github/actions/scan-code diff --git a/README.md b/README.md index bcfb219e..2ba766bb 100644 --- a/README.md +++ b/README.md @@ -104,6 +104,6 @@ We publish our documentation site when pushing to the `master` branch. [components/]: ./components/ [pnpm-workspaces.yaml]: ./pnpm-workspaces.yaml [plopfile.js]: ./plopfile.js -[install pnpm]: https://pnpm.js.org/en/installation +[install pnpm]: https://pnpm.io/installation [PLOP]: https://plopjs.com/ [documentation application]: ./apps/docs diff --git a/apps/docs/assets/images/content-style-guide/Biometrics sign.png b/apps/docs/assets/images/content-style-guide/Biometrics sign.png new file mode 100644 index 00000000..51e0d353 Binary files /dev/null and b/apps/docs/assets/images/content-style-guide/Biometrics sign.png differ diff --git a/apps/docs/src/common/pages/accessibility/inclusive-language.tsx b/apps/docs/src/common/pages/accessibility/inclusive-language.tsx index d94c6881..c49319d7 100644 --- a/apps/docs/src/common/pages/accessibility/inclusive-language.tsx +++ b/apps/docs/src/common/pages/accessibility/inclusive-language.tsx @@ -132,7 +132,7 @@ const Page: FC = ({ location }) => (

Download the posters for your office space and help colleagues think about how to write inclusively.

Help improve this guidance

-

To contribute, send your request to design@digital.homeoffice.gov.uk, or add it to the GitHub discussion.

+

To contribute, send your request to ucdops@homeoffice.gov.uk, or add it to the GitHub discussion.

diff --git a/apps/docs/src/common/pages/content-style-guide.tsx b/apps/docs/src/common/pages/content-style-guide.tsx index 434de8d1..66b62520 100644 --- a/apps/docs/src/common/pages/content-style-guide.tsx +++ b/apps/docs/src/common/pages/content-style-guide.tsx @@ -7,6 +7,26 @@ import { AZNavigation } from '@hods/components'; export const title = 'Content style guide'; const description = 'How to write content for Home Office services.'; +export const menu = ( + + + + +); + const Page: FC = ({ location }) => ( @@ -17,20 +37,25 @@ const Page: FC = ({ location }) => ( -

{title}

- +
+ {menu} +
+

{title}

+

A

abroad

'Abroad' and 'overseas' can cause confusion. Try to use plain English. For example, 'apply from outside the UK' or 'working in another country'.

account

-

Use 'create an account' rather than 'register an account' or ‘set up an account’.

+

Use 'create' instead of 'register' or 'set up' when you want people to create an account. 'Create an account' tested well in user research and is used by other government departments.

acronyms

Write out an acronym in full the first time you use it on a new page or screen, unless it is well known to your users, like UK, US or NHS. Research has found that some users struggle to remember the meaning of an acronym they saw on a previous screen. For example, write 'biometric residence permit (BRP)' on each screen of your service at first mention and use 'BRP' if it appears again on the same screen. If available, use a tooltip like acronym Markdown to make the acronym appear in full as hover text. See more guidance on abbreviations and acronyms in the GOV.UK style guide.

alter

Use 'change' rather than 'alter', 'modify' or 'switch'.

+

authorising officer

+

Lower case. You can use the acronym 'AO' after the first full mention.

asylum claimant

You can use either 'asylum claimant' or 'asylum applicant' to describe someone who has applied for asylum in the UK. Do not use both in the same product or service.

Back to top @@ -199,7 +224,7 @@ const Page: FC = ({ location }) => (

Life in the UK Test

Capitalise the ‘L’ and ‘T’. After first mention, you can refer to ‘the test’, using lower case.

log in

-

Use ‘sign in’ rather than ‘log in’, ‘login’ or ‘logon’.

+

Use 'sign in' rather than 'log in' or 'login'. Use 'sign in to' rather than 'sign into'.

Back to top

M

@@ -259,7 +284,7 @@ const Page: FC = ({ location }) => (

rank (police and armed forces)

Capitalise the rank before the name, as in 'Detective Inspector Joan Smith'. Use lower case when it follows the name, as in 'Joan Smith, a detective inspector'.

register

-

Use ‘create an account’ rather than ‘register’ or ‘set up’ an account.

+

Use 'create' instead of 'register' or 'set up' when you want people to create an account. 'Create an account' tested well in user research and is used by other government departments.

Use ‘correct’ rather than ‘right’. For example, ‘Select the correct settlement route’.

Back to top @@ -274,11 +299,13 @@ const Page: FC = ({ location }) => (

settlement

'Indefinite leave to remain' and 'indefinite leave to enter' are officially called 'settlement'. For example, 'apply for UK settlement'.

set up

-

Use 'create an account' rather than 'register' or 'set up' an account.

+

Use 'create' instead of 'register' or 'set up' when you want people to create an account. 'Create an account' tested well in user research and is used by other government departments.

sex

Find out how to ask users for their sex in the Home Office sex and gender pattern.

sign in

-

Use 'sign in' rather than 'log in' or 'login'.

+

Use 'sign in’ rather than 'log in' or 'login'. Use 'sign in to' rather than 'sign into'.

+ +

Lower case. A company or person sponsoring an individual to work in the UK and supporting their visa application.

sorry

Avoid using 'sorry'. See guidance in Writing for user interfaces on GOV.UK.

Sovereign Base Areas

@@ -329,7 +356,7 @@ const Page: FC = ({ location }) => ( Back to top

Help improve this guide

-

To contribute, send your request to design@digital.homeoffice.gov.uk, or add it to the GitHub discussion.

+

To contribute, send your request to ucdops@homeoffice.gov.uk, or add it to the GitHub discussion.

 diff --git a/apps/docs/src/common/pages/content-style-guide/designing-for-limited-english.tsx b/apps/docs/src/common/pages/content-style-guide/designing-for-limited-english.tsx new file mode 100644 index 00000000..2e2a7f88 --- /dev/null +++ b/apps/docs/src/common/pages/content-style-guide/designing-for-limited-english.tsx @@ -0,0 +1,230 @@ +import { FC, createElement as h } from 'react'; +import { Helmet } from 'react-helmet-async'; +import { PageProps } from '@not-govuk/app-composer'; +import { A } from '@not-govuk/components'; +import { menu } from '../accessibility' + +export const title = 'Limited English'; +const description = 'Designing for people with limited English'; +export const section = 'Accessibility'; + +const biometricsSign = require('../../../../assets/images/content-style-guide/Biometrics sign.png'); + +const Page: FC = ({ location }) => ( +
+ + {title} - Home Office Design System + + + + + +
+ {menu} +
+
+

+ Content style guide + Designing for people with limited English +

+

People who depend on Home Office services, such as visas, passports and asylum, are often not fluent in English.

+

This means important information in application forms, guidance pages and other tasks may be difficult to understand.

+

We have identified 10 evidence-based principles to follow when designing content for people with limited English:

+ +

Most of these principles also make your content accessible and inclusive for everyone.

+ + +

Use clear language

+

People with limited English need to read every word, unlike fluent speakers who often skim read. They may need to stop regularly to translate something. Reading this way takes a lot longer and can make information harder to remember.

+

Some plain English words may not be clear to people with limited English. Home Office researchers found that words like 'identity', 'dialect' and 'immediate family' were not always well understood. The 'Home Office' ministerial department is sometimes confused with a spare room or home office.

+

Research has found that technical language and long documents make people with limited English anxious. If you need to use technical language, provide a clear language explanation. For example, 'biometrics (your fingerprints and photo)'.

+

When designing for people with limited English, try to:

+
    +
  • match your writing to your users’ language levels
    • +
  • keep sentences short and on average 15 words
    • +
  • use the active voice
    • +
+ +

For more advice, read the GOV.UK guidance on using plain English.

+ +

Check how it translates

+

People with limited English often use online translators, like Google Translate, DeepL, Bing Translator or a native phone app. Use a translation tool to translate your text into some of the languages used by your main user groups. Then translate it back into English using a different translator to sense check it. You may find that some words translate better than others.

+

Examples of words that may not translate well into the languages of your main user groups:

+
    +
  • deadline
    • +
  • get in touch
    • +
  • ethnicity
    • +
  • dependant
    • +
+ +

Content designers working on visa application forms have been using 'money' instead of 'maintenance' or 'financial support' because it translates better in some of the languages used by their users.

+

Use online translators for guidance purposes only. These are external websites which can change at any time. While they are improving, they are far from perfect. Do not put sensitive information into online translators because that information can be stored and you have no control over how it is used.

+ + +

Test language with users

+

Guidance cannot replace the insight gained from testing your content with people with limited English. Content designers creating an asylum application form found that 'medicine' tested better than 'medication'. The NHS style guide also advises using medicine.

+

Test all important content in your service, including, but not limited to:

+
    +
  • headings
    • +
  • labels
    • +
  • hint text
    • +
  • buttons
    • +
  • guidance text
    • +
  • error messages
    • +
  • alt text
    • +
  • conditional reveals
    • +
+

Recruit participants with limited English and choose the most appropriate method for testing your content. For example, if some users need an interpreter to use your service, consider testing the service with an interpreter alongside a user.

+

+ +

Avoid idioms

+

The English language has many idioms. We use them to make our services more conversational. Common expressions like 'by the book', 'red tape' or 'touch base' are not always clear to people with limited English and do not always translate well using translation tools like Google Translate or Bing Translator.

+

Designers working on the passport application service found that users with limited English did not recognise 'wear and tear' as an expression to mean damage. Instead, they translated these words individually and mistakenly thought the statement did not apply to their passports as they were not torn.

+ +

Avoid phrasal verbs

+

A phrasal verb is where you combine a verb with other words to make it mean something different, such as ‘carry out’, ‘get over’ or ‘look after’. English is full of them. But their meaning is not always clear until you have learned them.

+

There is nearly always a one-word alternative to a phrasal verb that is easier to translate.

+ +
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Instead ofUse
carry out do, implement
fill in complete
call offcancel
get over recover
look into research, investigate
look up search
look after care for, be responsible for
turn down reject
make outunderstand
sort out solve
point outshow
come up withsuggest
go over check, examine
come acrossfind
stick tofollow, maintain
+ +
+
+

Use clear language whenever possible but if the alternative word translates better, consider using that instead.

+ +

Use simple tenses

+

The present and past tenses are the easiest to understand. Avoid sentences with complex tenses like ‘it will have worked’.

+

You will often have to use the future tense. But you can sometimes avoid it by writing in the active voice. For example, 'how your information will be used' may be easier to understand written in the present tense: 'how we use your information'.

+

To make your content more direct, use the present tense instead of 'should have' or 'would have'.

+

For example, instead of:

+
    +
  • Before submitting this form, you should have completed the following steps.
+

Use

+
  • Complete the next steps before you submit this form.
+ +

Write acronyms in full

+

Research has found that some users struggle to remember the meaning of an acronym they saw on a previous screen. Write an acronym in full the first time you use it on a new page or screen, unless it is well known to 80% of your users, like UK, US or NHS. For example, write 'biometric residence permit (BRP)' on each screen of your service at first mention and use 'BRP' if it appears again on the same screen.

+

Translation tools do not translate acronyms. For example, 'biometric residence permit (BRP)' translates to 'permesso di soggiorno biometrico (BRP)' in Italian. Italian speakers may not remember the meaning of 'BRP' if they see it on a later screen.

+

If available, use a tooltip, like acronym Markdown, so that when a user hovers over the acronym they see it written in full as 'alt text'.

+

See more guidance on abbreviations and acronyms in the GOV.UK style guide.

+ +

Avoid all contractions

+

Avoid all contractions, including positive contractions like 'we'll', 'you've' or 'they're', if your users have limited English. Research suggests that contractions make content difficult to understand for people with limited English. See general guidance on contractions in the GOV.UK style guide.

+ + + +

Consider images or video

+

In some cases, an image, diagram or video can communicate information more clearly. Research at UK arrival centres found that some people had difficulty finding their way using the text-only signage. To address this issue, designers produced a new signage system using text supported by images.

+ + Sign showing camera and fingerprint icons to explain in different languages how biometric information is taken. +

+

Make sure you include text alternatives with images for users with visual access needs.

+ +

Research with vulnerable users on the eVisa service found that most participants, including fluent English speakers, found the written guidance too long and technical. They said the information in the What is an eVisa video was easier to understand.

+ + + +

Consider translation services

+

Could your service benefit from having professional translation and interpretation support to make it more accessible?

+

If you identify a need to translate your content, consider:

+
    +
  • the number of alternative languages needed
    • +
  • if responses need to be translated
    • +
  • if content will be translated by a human or a machine
    • +
  • how translated content will be kept up to date
    • +
  • how to assure the quality of translated content
    • +
  • error messages
    • +
  • what happens when funding for translation ends
    • +
+ +

Work with your team and stakeholders to understand the benefits and costs of hiring translation services. This is not just about business pressures. There may be risks if a service is only partially translated or something has been mistranslated.

+ +

Help improve this guidance

+

To contribute, join the GitHub discussion.

+
+
+); + +export default Page; diff --git a/apps/docs/src/common/pages/contribute.tsx b/apps/docs/src/common/pages/contribute.tsx index 2f4924bc..1d0568a7 100644 --- a/apps/docs/src/common/pages/contribute.tsx +++ b/apps/docs/src/common/pages/contribute.tsx @@ -57,7 +57,7 @@ const Page: FC = ({ location }) => (

Consider giving your discussion topic a deadline of a few weeks.

4. Summarise the discussion

Use the comments to make a suggestion for an improvement or a new entry.

-

Contact design@digital.homeoffice.gov.uk if you'd like feedback on your discussion or for the design system working group to review it.

+

Contact ucdops@homeoffice.gov.uk if you'd like feedback on your discussion or for the design system working group to review it.

5. Updating the design system

The design system working group regularly assess discussions using the GOV.UK design system contribute criteria.

If the pattern or component is ready to be published, the working group will then raise an issue and progress this work further.

diff --git a/apps/docs/src/common/pages/contribute/design-system-working-group.tsx b/apps/docs/src/common/pages/contribute/design-system-working-group.tsx index be810096..2326ed0b 100644 --- a/apps/docs/src/common/pages/contribute/design-system-working-group.tsx +++ b/apps/docs/src/common/pages/contribute/design-system-working-group.tsx @@ -42,7 +42,7 @@ const Page: FC = ({ location }) => (

If you have a question or idea, you can contact the working group:

diff --git a/apps/docs/src/common/pages/get-started.tsx b/apps/docs/src/common/pages/get-started.tsx index 4035482b..b60d71b3 100644 --- a/apps/docs/src/common/pages/get-started.tsx +++ b/apps/docs/src/common/pages/get-started.tsx @@ -80,7 +80,7 @@ const Page: FC = ({ location }) => (

Support

If you have a question or need support you can:

    -
  • email design@digital.homeoffice.gov.uk
    • +
  • email ucdops@homeoffice.gov.uk
  • get in touch on Slack #ho-design-system
  • read and create GitHub discussions
  • view known issues on GitHub
    • diff --git a/apps/docs/src/common/pages/index.tsx b/apps/docs/src/common/pages/index.tsx index 1450781f..1e4130eb 100644 --- a/apps/docs/src/common/pages/index.tsx +++ b/apps/docs/src/common/pages/index.tsx @@ -23,9 +23,11 @@ const Page: FC = props => (
    diff --git a/docs/accessibility-statement.md b/docs/accessibility-statement.md index ad35a204..3aee0aaa 100644 --- a/docs/accessibility-statement.md +++ b/docs/accessibility-statement.md @@ -26,7 +26,7 @@ You can see a full list of any issues we currently know about in the Non-accessi If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille: -- email design@digital.homeoffice.gov.uk +- email ucdops@homeoffice.gov.uk - contact us via the methods listed at https://design.homeoffice.gov.uk/contribute We'll consider your request and get back to you in 30 days. @@ -35,7 +35,7 @@ We'll consider your request and get back to you in 30 days. ## Reporting accessibility problems with this website We're always looking to improve the accessibility of this website. -If you find any problems not listed on this page or think we're not meeting accessibility requirements, contact the Design Operations team on email: design@digital.homeoffice.gov.uk +If you find any problems not listed on this page or think we're not meeting accessibility requirements, contact the Design Operations team on email: ucdops@homeoffice.gov.uk [Read tips on contacting organisation about inaccessible websites][contact-tips]. diff --git a/reports/.sastscan.baseline b/reports/.sastscan.baseline index 1b1bcef0..07f1197d 100644 --- a/reports/.sastscan.baseline +++ b/reports/.sastscan.baseline @@ -3,5 +3,5 @@ "scanPrimaryLocationHash": [], "scanTagsHash": [] }, - "created_at": "2024-06-05 18:53:46.589624" + "created_at": "2024-07-30 13:19:14.310828" } \ No newline at end of file