Context
During multi-lingual usability testing (with experienced editors for iOS talk pages) we came across a couple of difficulties. Below is the list of difficulties we came across and a column of thoughts/ideas to solve for these difficulties (they need a further inquiry to see if they could be possible solutions) for future usability tests.
| Current difficulties | Possible solution/idea | |
| The test wiki's chrome/UI (buttons, titles, etc.) are available only in English, making it difficult to test in other languages. | On desktop, you can change the test.wiki's chrome/ui by adding 'uselang=ar'; 'uselang=de', etc. to the URL. Is it possible to access these sites in the app so that participants could test on test.wiki with the appropriate UI/chrome language? | |
| Posting on the actual language wikis is not allowed so if participants need to test in their language they are not able to make any contributions on the language wikis (no posting, commenting, etc.) making the experience less realistic. | This is why, giving participants access to test.wiki spaces with that have different chrome/UI languages would be beneficial (this could also helped by allowing iOS to access the test.wikis with different chrome languages via the 'uselang=ar'; URL addition. | |
| The chrome/UI of the new feature is only available in the different languages once the strings are translated in translate.wiki, which can take some time. | Is it possible to have a script that allows iOS to access the translations that are already translated for web? Currently, we cannot access these. | |