...
When designing a language selector, use plain text despite its lack of visual appeal. Only use flags to represent countries, not languages. <<Include recommended pattern for language name localization>>Language names in the select component should always appear in that language in order to make it easy for users to always be able to return to their language of chose regardless of the current language selected. e.g English will always be labelled as ‘English’ even if Hebrew is selected as the current language.
Right to Left
In certain languages like Arabic and Hebrew, text is read from right-to-left (RTL) necessitating your entire design to be flipped. A modular design approach will come in handy while accommodating RTL languages. For example, the application below is designed to flip neatly for Hebrew and other RTL languages as shown below:
...
Effective form labelling helps users understand what information to enter into a form Input. Using a placeholder text as a label is often applied as a space-saving method. However, this is not recommended because it hides context and can present accessibility issues. Use of placeholder labels should be restricted to forms in which field purpose is a universal standard and accessibility can be guaranteed e.g. login forms.
Provide a text label, left aligned to its associated field. Checkbox and Radio buttons are exceptions to this rule.
In situations when horizontal UI real estate is scarce or responsive design is used, render the label above it’s associated field.
Ensure that all labels and associated fields are vertically aligned as columns in a table
...
We use different capitalization styles for different types of content to improve scannability, organize information, and guide users to key actions.
When building new LUX productsapplications, also align capitalization practices with platform conventions to match user expectations (e.g. IOS specific conventions).
...