From b247c04ab2b41800f45f2a986e60b60236b3fc3a Mon Sep 17 00:00:00 2001
From: Steve Shukor <101883702+sshukor@users.noreply.github.com>
Date: Wed, 12 Jun 2024 11:22:23 +0100
Subject: [PATCH] Images and video section updated
Updates throughout including:
-punctuation
-external links
-new copy:
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.
---
.../designing-for-limited-english.tsx | 30 ++++++++++---------
1 file changed, 16 insertions(+), 14 deletions(-)
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
index 829148b0..c23739cd 100644
--- 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
@@ -34,8 +34,8 @@ const Page: FC 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. 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. Guidance cannot replace the insight gained from testing your content with low-fluency English speakers. Content designers creating an asylum application form found that ‘medicine’ tested better than ‘medication’. The NHS style guide also advises using medicine. Guidance cannot replace the insight gained from testing your content with low-fluency English speakers. 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: Recruit participants with limited fluency 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. 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. 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. 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. 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. Use clear language whenever possible but if you have an alternative that translates better, consider using that instead. Test language with users
-
- Avoid idioms
@@ -93,8 +93,8 @@ const Page: FCAvoid phrasal verbs
-
Use clear language whenever possible but if the alternative word translates better, consider using that instead.
+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'.
+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:
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, 'National Health Service (NHS)' translates to 'Serviço Nacional de Saúde (NHS)' in Portuguese. Users may not recognise 'NHS' on a later 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.
+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, 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 fluency. See general guidance on contractions in the GOV.UK style guide.
+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.
@@ -193,7 +193,9 @@ const Page: FCMake sure you include text alternatives for users with visual access needs.
+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.
@@ -210,7 +212,7 @@ const Page: FCWork with your team and stakeholders to understand the benefits and costs of hiring translation services. This isn’t just about business pressures. There may be risks if a service is only partially translated or something has been mistranslated.
+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.
To contribute, join the GitHub discussion.