Skip to content

Callout component wording change - #14685

Merged
rtyley merged 6 commits into
mainfrom
ljh-calloutcomponent-words
Oct 16, 2025
Merged

rtyley merged 6 commits into
mainfrom
ljh-calloutcomponent-words

Conversation

@hoyla

@hoyla hoyla commented Oct 15, 2025

Copy link
Copy Markdown
Contributor

What does this change?

@rtyley knows the background to this.

Excises the phrase:

"for true anonymity use Secure Messaging".

and replaces it with:

Formstack context:

"For alternative ways to get in touch securely, see our tips guide"

Messaging app context:

"For fully anonymous communication, please use our Secure Messaing service"

Why?

After discussion with GNM legal counsel we decided we needed to:

  • Avoid the unqualified phrase "true anonymity" because it could be interpreted of having broader meaning than simply within the context of communication via Secure Messaging. Prior or subsequent events may not be under our control so we should avoid ambiguity.
  • In the Formstack flavour, we say in the sentence before this that people can be anonymous if they wish. To subsequently assert that people should use something else for "true anonymity" might wrongly be interprested as meaning we're not committed to keeping formstack users anonymous from third parties, which of course we are.

hoyla added 6 commits October 15, 2025 16:10
Discussed with Zoe Norden who didn't want to suggest that anonymity was guaranteed in perpetuity: only the Secure Messaging service has sufficient protections for full anonymity and the lifecycle of a correspondence may extend beyond that. Because there isn't space to explain all that we opted to just refer to "alternative methods" without making promises that go beyond technology.
Revise anonymity claim to be specific to comms within Secure Messaging
dotcom reword per zoe norden advice (see prior commits)
remove 'true anonymity'
make dotcom match apps
@hoyla
hoyla requested a review from a team as a code owner October 15, 2025 15:46
@hoyla hoyla changed the title Ljh calloutcomponent words Callout component wording change Oct 15, 2025
@github-actions

Copy link
Copy Markdown

Hello 👋! When you're ready to run Chromatic, please apply the run_chromatic label to this PR.

You will need to reapply the label each time you want to run Chromatic.

Click here to see the Chromatic project.

@rtyley rtyley left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good! This follows on from PR #14598 .

I'll add the run_chromatic label as I think it's required to get these tests to run:

Image

...as this change will make visual changes, I think you'll then need to approve the changes in Chromatic (I'm not very au-fait with this process, but it's what happened to me last time!).

@rtyley rtyley added the run_chromatic Runs chromatic when label is applied label Oct 16, 2025
@github-actions github-actions Bot removed the run_chromatic Runs chromatic when label is applied label Oct 16, 2025
@rtyley

rtyley commented Oct 16, 2025

Copy link
Copy Markdown
Member

I'll add the run_chromatic label as I think it's required to get these tests to run:

Now that the tests have run, you'll notice that there's still one that's pending- but now it has a slightly different message: "Waiting for status to be reported — 2 changes must be accepted as baselin..."

image

...those 2 changes are where the appearance of the site has changed! If you click on the three-dots to the right of the test - highlighted in blue in the screenshot above, and go View details, you'll get taken to the Chromatic run for this build, where you can examine those 2 different changes, and approve them.

There are quite a few little steps to go through here, let me know if you'd like to pair on them!

@rtyley
rtyley merged commit 4b34eb5 into main Oct 16, 2025
33 checks passed
@rtyley
rtyley deleted the ljh-calloutcomponent-words branch October 16, 2025 16:15
@gu-prout

gu-prout Bot commented Oct 16, 2025

Copy link
Copy Markdown

Seen on PROD (created by @hoyla and merged by @rtyley 14 minutes and 26 seconds ago) Please check your changes!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants