The Hand Talk Website Translator is a practical tool that translates text content and images with alternative descriptions implemented in HTML structure into Brazilian Sign Language (Libras), helping to break down digital barriers and provide greater autonomy for people who communicate through this language.
After activating the accessibility window in Libras, the user is introduced to Hugo or Maya, our charismatic virtual translators responsible for signaling the content.
To ensure a high-quality translation for your website visitors, it’s essential to follow some requirements and recommendations when creating and publishing content.
Below is everything you need to know to ensure that Hugo and Maya translate as effectively as possible!
Requirements for the Website Translator
There are some standards you must implement on your site to make your pages accessible in Libras. These standards are the basic conditions that must be met for the plugin to perform automatic translation.
You can find more details about the requirements by accessing the Website Translator Technical Documentation.
Links
The links on your website need to have a path, and for that, you must use the href attribute. This not only improves usability for deaf individuals but also helps those who use screen readers, such as blind people.
The href attribute is indispensable! It indicates where the link is pointing and allows the "access link" modal to be displayed. Without it, the modal won’t appear, making navigation between pages difficult for users.
Image: using Href allows deaf people to translate the text of a link into Libras and navigate between pages using the "access link" modal.
Another important point is to avoid having scripts and frameworks manipulate the click events of links, as this can also hinder the usability of the Translator.
Best Practices for Optimizing Translation on Your Website
Unlike the requirements, the following recommendations are not mandatory for the plugin to function, but adhering to them can significantly improve the quality of the automatic translation, providing a better experience for your users!
Text Translation
The way the texts on your website are written can also influence better understanding and signaling by Hugo and Maya!
Try to use direct sentences and break large blocks of text into smaller paragraphs aiming not to exceed 800 characters. Always try to maintain cohesion between paragraphs to provide context for the Translator, and strategically use bold and italics to highlight important information.
To maintain good readability and accessibility in content, the Hand Talk Plugin reads paragraphs of up to 800 characters. Keeping paragraphs short not only improves user experience but also enhances your website’s search engine ranking.
IMPORTANT: By default, the Hand Talk Plugin is limited to capturing only 800 characters at a time for translation. However, this number can be increased to a maximum of 1000 characters per text block. To do this, simply configure the maxTextSize parameter.
Example:
<script src="https://plugin.handtalk.me/web/latest/handtalk.min.js"></script>
<script>
var ht = new HT({
token: "TOKEN",
maxTextSize: 1000
});
</script>
Image Descriptions (Alt Attribute)
The alternative text is used to describe the visual elements of an image. It is inserted through the alt attribute in the <img> tag, and it allows screen readers to identify and describe the content of a particular image to visually impaired people.
When an image contains text, using the alt attribute also helps deaf individuals because it allows our translators to translate the content into Libras. In other words, using the alt attribute makes your website more accessible to different audiences!
The tip when writing a description is to be objective, as shown in the example below.
Correct Example:
By following these tips, you can't go wrong! You’ll provide a better experience for people who rely on Hugo and Maya to navigate your website!
Still have questions? Consult the Website Translator Technical Documentation or submit a request.
Comments
0 comments
Please sign in to leave a comment.