Language navigation component is now in Trial: share your research

[lamiece-gds]

We’ve introduced a new language navigation component which is in ‘Trial’. The component allows users to navigate between two languages.

To move this component out of ‘Trial’ status to become a stable component, we need your feedback. Please tell us about your experiences and research using this component in your service.

In particular, we want to know:

• Is consistent positioning helping users find these options? (e.g. have you observed any changes in completion times, support requests or user feedback)
• How are you choosing to position the component and what informed that decision? (e.g. User research findings, analytics)
• In which services do users need multiple languages?
• Have you identified any user pain points where user information is lost, or users need to start the service again when users change language?
• Have you identified any language specific layout or typography issues? (e.g. How many issues have been reported and what impact did it have on users?)
• What proportion of users leave or fail to complete a journey when their preferred language is unavailable? (e.g. Do you have any analytics, user research findings or support enquires)

Any user feedback, learnings, challenges or data that you can share would be helpful.

To provide feedback, you can add a comment to this discussion or send feedback to the Design System Team by email.

We also have a previous community discussion which helped support building this component.

The Design System team will continue to review and consider your feedback as we iterate on this component. We expect to move the component to stable status by February 2027 and welcome any further feedback to inform that decision.