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

Improve responsive styles for secondary navigation component #270

Open
benfraserdesign opened this issue Dec 17, 2024 · 3 comments · May be fixed by #275
Open

Improve responsive styles for secondary navigation component #270

benfraserdesign opened this issue Dec 17, 2024 · 3 comments · May be fixed by #275
Assignees

Comments

@benfraserdesign
Copy link

We're exploring using this component at HMRC for a project exploring a new personal tax account for individuals (coming out of alpha as we speak). It has tested well in our 5 rounds of research - which included participants with accessibility needs and participants using a mobile/tablet.

As part of this work, we identified that the responsive styles could be improved - as noted in the component documentation. As a result, we made some minor adjustments (up to tablet dimensions) which resizes the navigation items to equal sized, centre-aligned elements.

Our service includes 4 items, which works well in user testing - but we'd recommend to not feature any more than 4 elements in the secondary navigation for it to work on smaller screens.

@benfraserdesign
Copy link
Author

Can I be assigned to this issue so that I can push our additional responsive code in a branch please?

@paulrobertlloyd
Copy link
Contributor

paulrobertlloyd commented Dec 27, 2024

Hi @benfraserdesign, sounds like a very useful contribution; have assigned you to this issue, let me know if you need any other help or guidance to contribute this change.

@benfraserdesign
Copy link
Author

See pull request #273

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 a pull request may close this issue.

2 participants