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.

Sign up for GitHub

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

Jump to bottom

Review touch target sizes on GOV.UK Frontend, and update components accordingly #1817

Open
36degrees opened this issue May 27, 2020 · 1 comment
Open

Review touch target sizes on GOV.UK Frontend, and update components accordingly #1817

36degrees opened this issue May 27, 2020 · 1 comment
Labels
accessibility breadcrumbs

Comments

@36degrees
Copy link
Contributor

What

Review the touch target changes originally proposed in #1754, and understand how to implement them in a way that does not make the position of the breadcrumb inconsistent with the back link.

Further detail

Questions:

  • How do the touch target size and the collapse on mobile behaviour interact with each other?
  • Do we need to change the touch target size on tablet/desktop as well?

Why

We want to ensure that the target size of the links in the breadcrumb component meets WCAG 2.1 2.5.5 Target Size.

Who needs to know about this

@vanitabarrett, @miaallers
@36degrees 36degrees mentioned this issue May 27, 2020
Merged
@kellylee-gds kellylee-gds removed the awaiting triage Needs triaging by team label May 27, 2020
@kellylee-gds
Copy link
Contributor

kellylee-gds commented May 27, 2020 •
edited
Loading

Run an investigation/SPIKE and take a proposal to GOV.UK

@timpaul timpaul changed the title Review touch target size of breadcrumb component Review touch target sizes on GOV.UK Frontend, and update components accordingly Jun 17, 2020
@36degrees 36degrees mentioned this issue Dec 9, 2020
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
accessibility breadcrumbs
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@36degrees @kellylee-gds