Notes from Estimation:

• Advanced Mobile front-end is the only place that shows Categories so the numbers will be "low" due to this
• Search tracking may be hard to do

@MusikAnimal Do you mind linking to any scripts you last used to analyze similar data (namely the average edit count of participants we analyzed back in 2021?)

outline of a release plan here https://phabricator.wikimedia.org/T331933

Let's wait on deploying on this but glad it's done, will add it to my to do to make a plan to figure out when we can deploy these iteratively

@dmaza You asked about moved paragraph changes, those should remain the same if a paragraph was moved. Let me know if that answers your question!

@MusikAnimal thanks for writing this up. We asked for feedback on the talk page and will be monitoring at well before we make any changes.

@nayoub we heard that the OOUI comes with a built in loader status that is not like this, therefore we were considering removing scope-- mind chiming in if you see any risks?

We will notify you as soon as we get the above issues addressed!

@TheresNoTime do you believe a new task is needed to address what came of that investigation?

Hey there, we talked about this internally and we thought it looked great! cc @nayoub we are working on figuring out how to merge it in and incorporate, thanks for the ping and for the patch! Will move this to the In Review column for Sprint 41 so it can get reviewed over the next two weeks. Thanks Nardog!

Going to move to needs attention

Agree with your intuitions here @Samwilson I think for now it's ok not to include the list header message situation to the scope
Will resolve this ticket!

Closing per the two diff outcomes being different enough

harumi, i went into https://phabricator.wikimedia.org/T330245 and changed it so it is clear that it is only the tooltip for two columns and not the legend -- two columns should NOT have a legend since we have the symbols

Closing this Task as it adds accessibility concerns. The file should never be longer than seconds given the character caps we gave phonos and adding inline playback speed options would clutter the UI in a way that does not justify the tradeoff for this user story / occurrences. We will use a survey to ensure our assumption around people thinking is too fast does not occur

@Jdlrobson Feel free to remove from the Readers-Web-Backlog board

@Lena_WMDE Do the folks in the Technical Wishes who last touched this codebase have any capacity for reviewing this code? Thanks so much!

But we are here to knowledge share and definitely hope that the apps and mobile can match the Desktop!

@Samwalton9 we are only touching the Desktop Wikitext diff experiences, all other diffs (mobile, apps) are out of scope for his.

Thanks again for your great QA documentation Dom!

I'm leaning towards reverting. While I think the idea of the popup makes sense, Commuity Tech does not the design/technical bandwidth to give this the holistic user-research and technical-research fix it deserves and mitigate the risk of clutter that any alternative non linked solution could introduce.

thanks for fixing this accessibility bug!

Wow, the adrenaline of Resolving a 21 pointer ticket.

@GMikesell-WMF thanks for making this list, it's very helpful to see all the user actions that can warrant a "thank you" broken down like this.

If I enter invalid or unsupported IPA, the error message tells me Using the text parameter might help. (as per T324239), because the Google engine ignores the invalid/unsupported IPA and just reads the text. So I might as well not include the IPA at this point.

aria-label great job!