Why are we doing this?
To get feedback on early native talk page designs via a multilingual survey with senior contributors. The participants will look at:
- Composition of the page header
- A page with talk page topics
- Cells on the topic page
- Different threading designs (A, B, C)
- Nested comments
- Content of the tab bar
- Contents of a ‘more menu’ card
- New user page redesign
The goal is to have contributors...
- Test whether the content on the pages is easily understood
- Help prioritize some of the content (like the 'more menu' actions and the content in the threads)
- Share whether they can easily access some key features (like nested comments and commonly used actions)
- Give feedback on the UI
Planning document
https://docs.google.com/document/d/1VQ1ParLiQrPZAHtUWEH9pIAyF7c7YHE_lR-CAgEM7js/edit
Testing plan
This online survey will ask for feedback from senior Wikipedia contributors that contribute on German (DE), Chinese (ZH), Hebrew (HE), and English (EN) wikis. The questions and the content of the wireframes will be translated using third-party translation services and checked by native speakers. The survey will be sent out via qualtrics.com which is a survey tool that allows for better multilingual abilities and RTL support than other survey tools. The survey will be posted on tech news and potentially other community spaces on Wikipedia with the hope that at least 5 people from each language wiki will give feedback on the early talk/user page designs.
The feedback will be processed and summarized and will help guide the next version of the talk page designs.
The survey can be found under: https://wikimedia.qualtrics.com/jfe/form/SV_9GBcHczQGLbQWTY
Results
😀 80% of participants understood the elements on the topic page.
😀 Participants found that the propsed header was: helpful=6, distracting=4, clarifying=3, confusing=3, other=2 (unclear/modern).
😀 64 % of participants prefered the threading that uses indentation (option A), 27% prefered option B with numbered comments and 9% prefered the option C that uses the editors usernames.
😀 64% of participants prefered to collapsed the text into topics.
😀 73% wanted to see all comments under a specific topic rather than collapsing nested comments.
😀 Participants voted for the features they would use most frequently from the ‘more menu’. The results were: history = 8, open all threads = 6, archive = 4, read on web = 4, page info. = 3, permanent link = 3, change language = 1, what links here = 1.
😕 57% of participants thought the image in the header was unnecessary, in part because you cannot edit the header area.
😕 A participant recommended a different labelling system for option B utilizing 1, 1.1, 1.2, 2, 2.1, etc.
😕 Participants were not iOS users and had difficulty with some of the icons/visual components and suggested to replace icons with labels.
😕 Participants recommended to add actions ‘Help’, ‘Report’, ‘Copy wikilink’ and ‘Download PDF’.
😕 3 participants recommended adding a message on the top of the article & user talk page explaining what the page is about.
😔 33% of participants were not sure if the timestap next to the topics indicated when the comment was posted or when it was last updated and whether the text in the cells was the first or most recent comment.
😔 17% of participants made suggestions about making the ‘add topic button’, more obvious. Currently it seems that it would add a new comment rather than a new topic.
😔 3 participants were confused by the purpose of actions like ‘read on web’ or ‘change language’.
Notes
A usability test has been run with new contributors using usertesting.com and the results of this usability test can be found under T305743.