Universal Language Selector/Testing

Summary of the insights obtained from the usability testing sessions performed for the Universal Language Selector.

Language list: Which mechanisms are most useful for looking for a language?

 * Short lists work. When the language that the user is looking for is anticipated in a short list, it is noticed and used by the user.
 * Search is most of the time the first option for search.
 * Users are more prone to search when the search box takes the input focus once the selector is opened.
 * Users try 2 to 3 times to adjust the search query before give up. The first attempt is the language name (using local name or English name). The second may be: try it again (in case of a typo), ISO code, name in a different language, or even country name.
 * The "no results found page" helped users to continue the search by region.
 * The map is used as a backup mechanisms.
 * Some users make use of it as first option for filtering.

Language settings

 * When users select a different input language, they do not normally pay attention to the available input methods. This is expected to be alleviated by:
 * Providing feedback on language change
 * Using a different method than "default" as the initial default.

Location for the Selector

 * Editing support was appreciated and understood.
 * For tests where editing support was not provided, users expected the input language configuration closer to the editing.
 * Confusion how to disable the current input method. Options considered: Better convey that the check mark can be unchecked or include an explicit option.