Checklist

Content/Context

• Validate all content: all new error messages and file export scenarios should be reproduced for testing, not just the visible labels;
• Validate adherence to the defined glossary/terminology for new terms introduced, as well as consistency with existing terminology;
• Validate that the available space for the label is appropriate and the text is not cut off;
• Verify there are no typing errors;
• Verify if the label is unambiguous in English/Portuguese/Spanish. If this cannot be avoided, ensure the resource path contextualizes the label (whether it is a menu entry, button, description, etc.) and validate the translation with the eXA team via the ID.

Example: Be careful with verbs in EN, which can be verbs or nouns in PT. For example, “View” can be “Ver” or “Vista”, “Process” can be “Processar” or “Processo”.

Structure

• Verify whether product messages are easy to understand, clear, short and incisive;
• Validate that the action buttons are verbs in the infinitive (e.g. “Edit” and not “Editing”);
• Validate the correct formatting of the Cegid products’ names;
• Confirm that abbreviations are only used as a last resort and validate their correct implementation;
• Validate the use of initialisms;
• Validate the punctuation used in the text of the product;
• Validate the correct date and time formatting;
• Validate the correct formatting of numbers and initialisms;
• Verify the use of uppercase and lowercase letters corresponds to what is defined in Compose..

Labels: initial capitalization of all words except articles, pronouns, prepositions and adverbs which are not at the beginning of the label;

Product messages: uppercase only in the first letter of the first word;