Closed HelenOsg closed 3 years ago
Take this to working group. Find examples of the way services currently do this? Is there a limitation technology-wise to where it is placed.
Just as something to bear in mind, almost every page I see with a Welsh language toggle fails WCAG 2.1 AA 3.1.2 Language of parts.
Basically 3.1.2 says that the human language of each part of the page needs to be programmatically determined, this helps things like screen readers to pronounce the content correctly.
Every page sets the language to English on the HTML attribute, eg: <html lang="en">
at the top of the page, but everyone forgets to tag the Welsh link.
The word Cymraeg needs to be tagged as cy
in order to pass 3.1.2. So it would need to be in the component but I think it would also be useful to call it out specifically in the guidance as it seems to be a really common error.
<html lang="en">
...
This page is also available in <a href="#">Welsh (<span lang="cy">Cymraeg</span>)</a>
...
Thanks to Colin for this one:
Worth adding to the list of "seen in use".
This has been published on the design system. If you have any research insights or have used the pattern, let us know on the GitHub discussion.
What
Most service seem to provide a text toggle for English/Welsh, but the placement seems to differ, from header bar, just under, in page, to footer.
Example: Find a job
Example: Find pension contact details
Example: Renew driving license
Example: New style JSA
Example: HMRC design system
https://design.tax.service.gov.uk/hmrc-design-patterns/welsh-language-toggle/
Why
Welsh translation are required on all services but the ability to switch to Welsh or toggle back and forth from English and Welsh is not consistent.
Original issue information: 14th May 2018 Chris Armstrong https://github.com/dwp/design-system-community-backlog/issues/34