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

Update links to Design System from READMEs #528

Merged
merged 6 commits into from
Feb 15, 2018

Conversation

36degrees
Copy link
Contributor

Update the links from each component README to the relevant page in the current private-alpha 'production' Design System.

Remove the link to guidance from the label component, which does not have corresponding guidance in the Design System.

Improve the title text to use the human-friendly version of the component name ("Back link" rather than "back-link") and to remove a redundant "Link to read " from the start.

Add a full-stop to the end of the sentence.

@govuk-design-system-ci govuk-design-system-ci temporarily deployed to govuk-frontend-review-pr-528 February 13, 2018 16:56 Inactive
@govuk-design-system-ci govuk-design-system-ci temporarily deployed to govuk-frontend-review-pr-528 February 13, 2018 16:57 Inactive
<h2 class="govuk-heading-l">Guidance</h2>
<p class="govuk-body">
More information about when to use {{ componentName }} can be found on <a href="{{- componentGuidanceLink -}}" title="Link to read guidance on the use of {{ componentName }} on Gov.uk Design system website" class="govuk-link">GOV.UK Design System</a>
More information about when to use {{ componentName }} can be found on <a href="{{- componentGuidanceLink -}}" title="Guidance on the use of {{ componentName | replace("-", " ") | capitalize }} on GOV.UK Design System" class="govuk-link">GOV.UK Design System</a>.
Copy link
Contributor

Choose a reason for hiding this comment

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

Should we be using title here? It doesn't improve accessibility as far as I understood?

https://silktide.com/i-thought-title-text-improved-accessibility-i-was-wrong/

Copy link
Contributor

@alex-ju alex-ju left a comment

Choose a reason for hiding this comment

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

@NickColley's point seem valid to me. otherwise good to be merged.

@govuk-design-system-ci govuk-design-system-ci temporarily deployed to govuk-frontend-review-pr-528 February 15, 2018 09:53 Inactive
@36degrees 36degrees force-pushed the update-links-to-design-system branch from 7ae07f3 to 4fbdcd0 Compare February 15, 2018 09:54
@govuk-design-system-ci govuk-design-system-ci temporarily deployed to govuk-frontend-review-pr-528 February 15, 2018 09:54 Inactive
@36degrees
Copy link
Contributor Author

@NickColley I've talked to Amy and she's requested some copy changes which I've made, removing the title attribute in the process.

Replace the placeholder links (http://www.linktodesignsystem.com) with links to the current private beta production Design System (https://govuk-design-system-production.cloudapps.digital)
The Design System does not have any guidance for the label component, as the label component is only a component because it provides a way to avoid repetition between components, and as such does not need documenting.
There is currently a discrepancy between the Design System and Frontend on the name of this component – until this is resolved, we’ll need to manually override the link so that it points to the right place.
Remove the title text from the link to the Design System, as title attributes don't actually improve accessibility [1]. Update the copy as agreed with @amyhupe, to make sure users understand that they are going to go to the Design System and to help them to understand what the Design System will tell them that the README doesn't.

[1]: https://silktide.com/i-thought-title-text-improved-accessibility-i-was-wrong/
@36degrees 36degrees merged commit 00dde2e into master Feb 15, 2018
@36degrees 36degrees deleted the update-links-to-design-system branch February 15, 2018 11:15
@alex-ju alex-ju mentioned this pull request Feb 20, 2018
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.

4 participants