Skip to content

Conversation

@selfthinker
Copy link
Contributor

@selfthinker selfthinker commented Jan 8, 2026

We learned that sometimes a Dragon command for using the file upload component works the first time, and sometimes it doesn't. This changes the guidance text to work for both scenarios.

For more context:
Someone from the NHS Design System contacted us that when they test the new file upload component with Dragon they cannot interact with it at all before performing another action. In our testing the first time always worked. As user activation is supposed to need another action after a page load, we assume that there is a bug somewhere on our side (probably in the Chrome browser).
The fact is that our testing results are different means we are keeping the language of "may" as different versions of Dragon/Chrome/Windows behave inconsistently.

@netlify
Copy link

netlify bot commented Jan 8, 2026

You can preview this change here:

Name Link
🔨 Latest commit 51553f9
🔍 Latest deploy log https://app.netlify.com/projects/govuk-design-system-preview/deploys/695fdb894e094a0008f17397
😎 Deploy Preview https://deploy-preview-5073--govuk-design-system-preview.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@selfthinker selfthinker requested review from a team, calvin-lau-sig7 and seaemsi January 8, 2026 13:47
With the improved File upload component, users can say commands for interacting with web page controls to choose files.

However, due to [browser security features](https://developer.mozilla.org/en-US/docs/Web/Security/User_activation), this may not work on subsequent interactions on the same page. If the component needs to be used more than once (for example, to correct a mistake), users will first need to perform another action, such as a mouse click.
However, due to [browser security features](https://developer.mozilla.org/en-US/docs/Web/Security/User_activation), this may not work immediately or on subsequent interactions on the same page. If users cannot interact with the component, they will first need to perform another action, such as a mouse click.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
However, due to [browser security features](https://developer.mozilla.org/en-US/docs/Web/Security/User_activation), this may not work immediately or on subsequent interactions on the same page. If users cannot interact with the component, they will first need to perform another action, such as a mouse click.
However, due to [browser security features](https://developer.mozilla.org/en-US/docs/Web/Security/User_activation), this may not work right away or on subsequent interactions on the same page. If users cannot interact with the component, they'll first need to perform another action, such as a mouse click.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thanks, I've made those changes and pushed.

Copy link
Contributor

@calvin-lau-sig7 calvin-lau-sig7 left a comment

Choose a reason for hiding this comment

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

Makes sense! How do these suggestions look to make it a bit more readable?

We learned that sometimes a Dragon command works the first time,
and sometimes it doesn't. This changes the text to work for both
scenarios.
@selfthinker selfthinker force-pushed the update-file-upload-dragon-guidance branch from 2c26914 to 51553f9 Compare January 8, 2026 16:29
@selfthinker selfthinker merged commit 45ec916 into main Jan 8, 2026
16 checks passed
@selfthinker selfthinker deleted the update-file-upload-dragon-guidance branch January 8, 2026 17:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants