The current validation messages use parenthetical alternations (e.g., a(n) in English, un(e) in French) to handle article/gender agreement.
This creates awkward, less readable messages. As accessibility standards evolve, validation messages should be clear and natural-sounding for all users, including those using screen readers.
All thoses translations could be rewrited to avoid it.
For example:
From production:
Example of rewriting:
Required: 'Please provide a value for {fieldName}.',
Required: 'Veuillez renseigner le champ {fieldName}.'
Required: 'Por favor, indique un valor para {fieldName}.'
This should be applied to all language files using this kind of parenthetical alternations
The current validation messages use parenthetical alternations (e.g., a(n) in English, un(e) in French) to handle article/gender agreement.
This creates awkward, less readable messages. As accessibility standards evolve, validation messages should be clear and natural-sounding for all users, including those using screen readers.
All thoses translations could be rewrited to avoid it.
For example:
https://github.com/ing-bank/lion/blob/master/packages/ui/components/validate-messages/translations/en.js
Required: 'Please enter a(n) {fieldName}.',https://github.com/ing-bank/lion/blob/master/packages/ui/components/validate-messages/translations/fr.js
Required: 'Veuillez également indiquer un(e) {fieldName}.',https://github.com/ing-bank/lion/blob/master/packages/ui/components/validate-messages/translations/es.js
Required: 'Introduzca también un/a {fieldName}.',From production:
Example of rewriting:
Required: 'Please provide a value for {fieldName}.',Required: 'Veuillez renseigner le champ {fieldName}.'Required: 'Por favor, indique un valor para {fieldName}.'This should be applied to all language files using this kind of parenthetical alternations