Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make help text advice clearer in fieldset guidance #2145

Merged
merged 1 commit into from
May 6, 2022

Conversation

EoinShaughnessy
Copy link
Contributor

@EoinShaughnessy EoinShaughnessy commented Apr 20, 2022

Fixes #2143.

Current guidance:

Include any general help text which is important for filling in the form and cannot be written as hint text in the legend, but try to keep it as concise as possible.

This sounds like we're saying users can make help text look like a heading. If that's right, then maybe we should add an example.

Also, the current wording is on the long side, so I had a go at rewriting it.

@netlify
Copy link

netlify bot commented Apr 20, 2022

You can preview this change here:

Name Link
🔨 Latest commit 24379c5
🔍 Latest deploy log https://app.netlify.com/sites/govuk-design-system-preview/deploys/6260312abdb6380008e3bd3a
😎 Deploy Preview https://deploy-preview-2145--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 site settings.

@netlify
Copy link

netlify bot commented Apr 20, 2022

You can preview this change here:

Name Link
🔨 Latest commit d417ab3
🔍 Latest deploy log https://app.netlify.com/sites/govuk-design-system-preview/deploys/626960b80006260008aa4efe
😎 Deploy Preview https://deploy-preview-2145--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 site settings.

@EoinShaughnessy EoinShaughnessy force-pushed the update-fieldset-guidance branch from 283a10b to d417ab3 Compare April 27, 2022 15:26
@@ -31,4 +31,4 @@ Read more about [why and how to set legends as headings](/get-started/labels-leg

On [question pages](/patterns/question-pages/) containing a group of inputs, including the question as the legend helps users of screen readers to understand that the inputs are all related to that question.

Include any general help text which is important for filling in the form and cannot be written as [hint text](/components/text-input/#hint-text) in the legend, but try to keep it as concise as possible.
Include general help text in the legend if it would help the user fill in the form, and you cannot write it as [hint text](/components/text-input/#hint-text). However, try to keep it as short as possible.
Copy link
Contributor Author

Choose a reason for hiding this comment

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

@calvin-lau-sig7 Joe commented in the original issue that an example might be good under here. What do you think?

Copy link
Contributor

Choose a reason for hiding this comment

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

Hi @joelanman, when you have a chance, can we have a chat so I can understand what the situation for this might be?

Copy link
Contributor

Choose a reason for hiding this comment

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

We're going to release, happy to add an example as a further PR.

@calvin-lau-sig7 calvin-lau-sig7 merged commit 7a48ab5 into main May 6, 2022
@calvin-lau-sig7 calvin-lau-sig7 deleted the update-fieldset-guidance branch May 6, 2022 09:17
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.

Is the fieldset hint guidance correct?
3 participants