User talk:JScherer-WMF/drafts/Reading accessibility research report DRAFT

WMF internal feedback
Please leave feedback on the draft below before 25 August 2023.

Some areas where I could use feedback JScherer-WMF (talk) 23:00, 17 August 2023 (UTC)
 * How might I make the report more clear?
 * Is there a clear connection between the research findings and the implications for design?
 * What important threads and sources have I missed?
 * What implications does the report raise for your areas of expertise or teams? We can follow up on these.


 * How might I make the report more clear?
 * It might be helpful to link out to relevant Wikipedia articles for terms that might not be clear to all readers (eg. HCI, and ergonomics)
 * As you have a TL;DR at the start of the report, perhaps the round up of Design implications could include a brief summary of what each of these updates might look/feel like / what would be included in these changes?
 * Is there a clear connection between the research findings and the implications for design?
 * Yes! Curious how a quick web prototype or imagery could help with illustrating these potential implications for readers who might have a hard time visualizing on their own though...
 * What important threads and sources have I missed?
 * Curious about if there are stark differences in reading on desktop web vs. reading on mobile web and also the contexts that people tend to be in on each platform. You noted that the text size is larger on mobile web -- is this common for mobile websites vs. desktop websites? Are there patterns or behaviors that are more common on mobile vs. desktop? How does line length affect scanning when reading on mobile?
 * CMadeo (WMF) (talk) 18:51, 22 August 2023 (UTC)
 * Thanks! This is super helpful! JScherer-WMF (talk) 19:32, 29 August 2023 (UTC)
 * From AA
 * while reading your draft Justin i was also wondering if it would be worth to consider non-scientific insights. for instance, what about personal subjective preferences? e.g. i feel i read faster in a monospace font, or i feel content is more scannable with a very long measure/line length. this discourse reminds me of this tweet from geoffrey litt on user agency"“I don’t like the color of that wall in my house”“Thanks for the feedback! We’ll consider repainting everyone’s walls if enough house owners agree with you!”The lack of agency we have over our software would seem absurd in other contexts."while i agree with your statement"[...] customization features would only benefit engaged readers. The quick scanning readers who spend less than a minute on an article will not benefit from customization because their individual reading sessions tend to be too short and task oriented to find and change reading settings."i would also be curious to learn more about the potential impact of customization to returning quick scanning readers. if i can set my reading settings "for life" i then feel even more quicker every time i look for a piece of information.another potential reference is the boost feature from the arc browser. for instance, setting wikipedia to papyrus will probably not make your reading experience more scientifically accessible, but for people who love it, it would make their reading experience feel more pleasant, even for quick scanning (?). JScherer-WMF (talk) 19:18, 30 August 2023 (UTC)