Background

The iOS team explored a prototype for adding alt-text in November. In our decision matrix to determine if we should proceed with making a "add alt-text" microtask the first suggested edit on iOS, we set a goal of 50 people trying the feature by the end of December. We did not reach 50 people testing the feature, so we need to pivot to ensure we can have an impact on our OKRs (see parent task). We are pivoting to building Image Recommendations and will then run a broader scale experiment for the "add alt-text" microtask. This sub-epic is focused on bringing Image Recommendations (Add an Image) to the iOS app. The alt-text experiment will be a separate body of work, which means a separate sub epic.

We want to measure:

• Metric specific Leading Indicators: Indicators to be captured after 15 days
• Image rejection rate does not exceed 29%
• Edit over-acceptance rate (never skip or reject recommended images) does not exceed 35%
• Task completion rate is not below 30%
• Revert rate does not exceed 18%

Validation

• KR 1.1: 600 articles have images in a 30 day period
• KR 1.2: Average at least 6 edits per day per unique user with 50+ edits
• KR 1.3: 10% of eligible Suggested Editors try image recommendations task
• KR 1.4: 30% of those users complete the task again on a separate day in a 15 day period
• KR 1.5: Accept rate does not deviate from Mobile Web or Android by more than 10 percentage points
• KR 1.6: 10% increase in unreverted edits from iOS in the main namespace

Guardrails

• KR 1.1: Less than 5% of users report NSFW or offensive content
• KR 1.3: All users spend at least 10s evaluating a task before publishing it
• KR 1.4: Bounce rate does not exceed 30%
  • Bounce rate defined as users that click Yes then abandon the flow before publishing
• KR 1.5: At least a 80% task completion rate
  • Defined as users that click on Add an image as a task, and actually clicks Yes, No or Not sure (interact with the feature)
• KR 1.6: Revert rate does not exceed 5%

Curiosities (nice to have)

• KR 1.1: Do these numbers differ by user tenure?
• KR 1.2: Are we seeing differences in these metrics when focusing on our target audiences as compared to general population?
• KR 1.3 At what point in workflow are most frequent dropoff events?
• KR 1.4 How often are users adding captions and alt-text (distinguish between the two)?
• KR 1.5 How often are reverted edits captioned?

Target Quant Regions and Languages

• Spanish, French and Portuguese speakers in the Americas (North, South and Central) and Caribbean
• Chinese speakers in North America

Target Qualitative Audience

• Spanish French and Portuguese speakers in LATAM and Caribbean countries
• Chinese Speakers in North America
• No more than 40% of our testers should identify as male
  • Low Bandwidth Users
  • Moderators

Must Haves for V1

• Entry point should reside in the Explore feed (not the first card- under top read) and a permanent home based on navigation work
• There should be a tooltip, notification or some sort of intervention to draw attention to the task for qualifying editors
• Users should have an option to add a caption and alt-text on the screen but it should not be prompted
• There must be a way for users to report issues with the feature, it should take them to the support email (pre-populated)
• Users should have an entry point in the task to the FAQ page (via overflow)
• There should be some sort of way to ensure users aren’t continuously hitting yes in a short (less than 5s) span of time to guard against bad faith edits
• There must be onboarding to the feature
• Users should be able to access full article (via read more) and image metadata
• Do not allow users to skip without providing some feedback (Yes, No, Not Sure)
• Preview the edit and provide an edit summary before publishing
• Selecting No triggers a survey (reasons should have parity with Android)
• Allow users to zoom/pinch on image
• Considerations for images running out or task not being available in certain languages
• Non-intrusive guidance for adding captions and alt-text (can take user out of the app)
• Accessibility in accordance with WCAG
• Interface must be translated in target languages prior to release
• Feature should not be available to users with less than 50 edits in the language they are editing
• Users should understand how the image was recommended (Parity with Android, Sentence noting whether it's related on Wikidata or it was used in another Wikipedia article)

Nice to Haves

• Users able to filter by topics
• Subtle positive reinforcement

User Stories

• As a Wikipedia iOS app user with a small screen and inconsistent internet, I would like to evaluate images and determine if they should go into an article, to contribute to Wikipedia articles that are in need of more content.
• When I am using the app, I want to be able to add images with one hand to many articles on my mobile device, so that I can be productive while riding the bus in Bogotà, and listening to music.

Designs

Figma file

Onboarding and main screen

1: Appears the first time someone opens that app after the feature has been added. Tapping 'Try now' takes you directly to the image recommendations.
2: Card located below the first card in the explore feed.
3: Appears once after someone opens the feature for the first time.
4 - 6: Show up the first time someone opens the feature. Get re-triggered after someone taps on 'Tutorial' from the overflow menu.
7: Default screen has the sheet pulled up halfway. Text behind the sheet is scrollable. Text inside the sheet is scrollable.
11: Overflow menu items include 'Learn more' that takes you to a FAQ page, 'Tutorial' that re-initiates the tooltips and 'Problem with feature' which opens up an email (you can find the copy below under 'Support email Copy').

Choosing 'Yes' from the sheet

1. When no information is added people may tap 'Next' but it is not progressive.
2. Once caption and/or alt text is added the 'Next' button becomes progressive.
3. Edit summary -> 'Publish' is disabled until edit summary is added.

Choosing 'No' from the sheet

1. People may select multiple options. Tapping cancel takes you back to the image recommendation.
2. Trying to type a reason automatically selects this option. Deselecting this option grey's out any left over text in the input field.

Choosing 'Not sure' from the sheet -> takes you to the next image suggestion.

Question: We agreed to use the iOS sheet. If we have control over the size of the title, could we have the title size be 'Headline/Bold' and the copy be 'Add this image to the article?'?

Todos

• Ensure copy is translated (OT)
  • Interface Translations
  • Email copy translations
• Update FAQ page (HN)

---

Support email Copy:

Subject:
Issue Report- Add an Image Feature

Body:
I’ve encountered a problem with the Add an Image Suggested Edits Feature:

• [Describe specific problem]

The behavior I would like to see is:

• [Describe proposed solution]

[Screenshots or Links]