This document will describe our recommendations for building out content in WiscWeb in multiple languages.
Our general recommendations for including multiple translations for your content are as follows:
It is recommended that you focus on translating the most important pages first. Specifically, the pages you think will be trafficked the most. This ensures that the important content is available to those who need it, in the format they expect it in.
Our recommendation is to include both English and translations right in the same page by alternating paragraphs between the languages.
A note at the top of the page that makes the user aware that the page offers multiple translations of the content is very helpful - especially for users who may be navigating the page using a screen reader.
Note: This page is offered in both English and ___ languages.
A LANG attribute should be added to the HTML - inline - to indicate where changes in languages occur. This is a nice reference for both screen readers and browsers.
<p>This sentence will be read in English.</p>
<p lang="en-GB">This sentence will be read in English, but with a British accent.</p>
<p lang="es">Esta frase es en Español.</p> (Spanish - “This sentence will be read in Spanish”)
More information on the LANG attribute (including the various language codes) can be found on the W3Schools website.
The Cultural Linguistic Services group can assist you with your translations to make sure they are accurate and make sense. We recommend connecting with them if you require assistance with your translations.
The DoIT Center for User Experience team can assist with answering questions related to accessibility and user-experience.
Changing the color of the text to differentiate between the different language translations can be tricky for the following usability/accessibility reasons:
Therefore, we would caution against using this approach in general.
If these options do not fit your needs, please reach out to further discuss how to deliver your content to your audience: email@example.com