Translation UX/Design feedback 2

Test with user #30 on 23 Aug 2012

 * Languages: German, English, French, Tetum, Spanish and Latin. Provides translations for German and Tetum.
 * Location: Germany

Sign-up prototype:
 * 01:40 - The user selects French as the proposed language.
 * The user tries to indicate his expertise level for the language and add more languages but that was not supported by the prototype.
 * 02:24 - When the user access to the second step, he identifies the example translation as being a captcha.
 * 03:00 - To complete step 2, the user selects a suggestion by clicking on "use this suggestion" link.
 * 04:23 - The user understands that the account is already created at step 2, but not activated until a translation is provided.
 * 05:30 - The user is able to complete the test scenario without problems and identifies the different interaction elements.
 * Some of the elements are familiar to the user because of previous use of the existing translation platform (the experience of a new user may differ).

Translate workflow test:
 * 08:05 - The user thinks it is a good idea to put the suggestions on the side and uses it in the first message.
 * 08:49 - The user notices that by saving, you access the next translation and likes that it avoids him to repeteadly open and closing messages all the time.
 * 09:27 - The user notices the "Request revision" action but cannot figure out its purpose (later when needed, he will).
 * 10:00 - The user skips the 3rd message since here is no suggestion.
 * 10:07 - The user understands the "outdated" concept and thinks that "it is a really good idea that you can simply click 'confirm translation' if you want to".
 * 10:47 - The user thinks that 'fuzzy' can be a bit confusing to new users, but the user thinks it may be useful to have a fuzzy flag for advanced translators.
 * 11:25 - The user discovers the expand action with joy.
 * 11:38 - The user marks a message as 'requires revision'. The feature is described as " a flag put on a message to say: It's not up to date but I personally can't update it. I think it is a really good feature to have"
 * 12:18 - For the last message, the user realizes he is reviewing a message that was marked for revision and confirms the translation is ok.
 * 12:42 - The user is shown the translation limit dialog and interprets it as a "kind of protection against spam".
 * 13:55 - The user was asked to look for more information about the skipped message, and he was able to find the comments about the message.
 * The user thinks it may not be much useful to just see comments from other translatos that cannot translate the message. But he guesses that developers are also supposed to reply to these comments.
 * 16:02 - The user is asked to access the cross-language translation link and he finds it useful since he usually provide translations in two languages: "I think this is a really good feature because when a message is not translated in both of the languages I edit the URL and write the right message code".

Search prototype:
 * 18:42 - The user performs the search and distinguishes the "original" and "translated" messages from the overview.
 * 19:41 - The user access to all translations from the overview.
 * 19:57 - The user intention would be to click on translate and start correcting all the typos (not possible in the prototype), so it becomes not clear for the user which is the purpose of this test.
 * 04:25 - The user finds strange to have information about other languages in translation messages when he is looking for a specific language.

Universal language selector:
 * 27:09 - The user was asked to use the ULS to change between some of the languages the user knows. The user is familiar with the selector and is able to find German quickly by browsing.
 * 2 seconds to go to the "Europe" region since the selector is open + 2 seconds to locate "Deustch" since the Europe list is displayed.
 * 27:38 - The user notices the undo tooltip as an easy way to go back to English.
 * 28:07 The user looks for the Tetum language. Tries first to browse and then to search, but he found the language in the list just when starting to search. For this case, the user found strange the scope of the search was not for the specific region.

General comments:
 * 30:00 - The first impression when the log-in interface was shown he perceived it as a complete overhaul. the user is not sure if this is necessary considering the current FirstSteps page "works quite good". Nevertheless, the user commented that including an initial translation and the translation limit will help people to get started more easily.
 * 31:35 - The user wanders if each message may be open in a new tab which is how he works now.
 * 36:30 - The user comments that he is used to the Monobook skin and finds that "the look of the workflow its a bit modern, but the concept of the new workflow is a good one".

Translate workflow

 * 01:07 - User initially do not recognize the string to translate but identifies the string to translate right after.


 * 02:49 - Although there was no problem in locating them, the user indicates that suggestions may be slightly more noticeable.


 * 03:29 - The user thinks it would be interesting to see an example with more strings to translate.


 * 03:59 - The user does not save the translation by mistake, but since the translation is marked as "unsaved" he realizes and is able to recover.


 * 04:30 - The user becomes surprised to going to next when saving the translation.


 * 10:04 - The user expects the prototype to support typing.


 * 12:12 - The user plays with the "flag feature" and finds it "quite good".


 * 15:05 - To get context info, the user considers the description as the main source and then the source code as the second. When the user is shown the integrated comments, the user finds them good to have.


 * 18:07 - When asked about the intended purpose of the "requires revision" feature, the flag makes the user think of the feature as abuse reporting.


 * 20:25 - The user finds interesting that "requires revision" allows asking other people to proofread a translation because "when you translate you aren't sure about yourself".


 * 21:38 - The user comments that normally does not translate a sequence of messages but individual ones. But he likes the labels (translated, outdated, to review) better than the current use of colors.


 * 23:00 - The user finds line height too tall.


 * 25:00 - The user finds the link for translating in a different language is not much useful. The user found it less useful since he do not speaks Italian (as used in the example) but found it a good way to get more translations.


 * 36:53 - The user finds the translation limit message a bit frustrating but considers it "a good compromise".

Sign-up prototype

 * 28:01 - The user finds the header too tall since it hides the rest of the content.
 * 28:53 - Finds it good to ask first for language and then for account data.
 * 29:20 - The user identifies step 2 as asking for translator rights at creation. Finds it good for activating purposes, but for general purpose it is preferred to allow the user to select what to translate.
 * 33:50 - The user considers that the sentence to translate should be more prominent.
 * 35:04 - The user considers that the progress bar for progression makes more sense to be displayed from left to right.

Search prototype

 * 41:45 - The user is able to access translation-only results.
 * 43:12 - It is not clear for the user the difference in purpose of "translate" and "details".
 * 44:10 - The user is not able to identify at first the project a message it belongs to.
 * 44:48 - Although the user did not noticed filters until he needed them. Once found, the user identifies filter categories, sub-categories and how to select them.

ULS

 * 48:20 - User changes language to English using search but seems a bit confused by having the language repeated for different regions.
 * 48:50 - The user finds it " a good idea" the tooltip to go back.
 * 49:20 - Likes autocompletion capabilities.
 * 49:40 - Expresses the preference for using flags as the icon for language change.
 * 51:15 - The user considers autocompletion to have "some minnor bugs" when the suggestion is unexpected.
 * 51:43 - The user founds disturbing to have no-localized region codes (na, eu, me, etc.).
 * 52:30 - Since he has been using search, the user does not consider the map to be that useful.

Test with user #20 on 23 Aug 2012
Technical issues: The user microphone was not working and several connectivity problems occurred.

Translation workflow

 * 01:40 - The user spend some time analyzing the UI for the first message but moves forward fluently from this point.

While users that are a little bit better in using computers might feel frustrated if this message arrives after just a few translations
 * 04:13 - User comments:
 * About the workflow: The new workflow seems quite comprehensive to me. I think the organisation of the screens and boxes is quite logic. I think it is meant to keep the attention of the tranlslator to the fact that the suggested translation does not really fit.
 * About the translation limit message: This can be interpretated positive if the transaltor does not feel comfortable with the tool.

Search prototype

 * 12:25 - The user access translations using the table header.
 * 12:27 - Comments about search: Although I had some difficulties to find the correct message I think this new function will be useful especially as there is for the moment just the special page "search" that helps a little bit to fix such errors.

ULS

 * 16:40 - The user starts browsing but ends up using search for the following tries.
 * Comments about ULS: I think that at first the titles of the groups like EU, .... is not that clear an explanation for this might be useful.