Reading/Web/Accessibility for reading
 | This page is under construction Please help review and edit this page. |
|
Accessibility for reading
Typographical changes and preferences making the site more accessible
|
The interface of Wikimedia projects must be easily accessible and readable for all, regardless of language, script, or specific needs. The current site typography on desktop and mobile makes readability difficult.
We are studying the issues in typography. Next, we will work on typography and typographical preferences that make the site more accessible and easier and more efficient to use.
Background
Why it is important to work on this
To enable the distribution of knowledge worldwide, the interface must be easily accessible and readable for all. This includes both the majority as well as individuals with specific needs.
Over the past few years, we have introduced the Vector 2022 skin across wikis. The skin is designed to improve the reading experience and provide an experience which is comfortable for existing users and more welcoming to new users. However, there are still issues with readability we have yet to address. During the research for that project, one of the issues with readability we recognized was the size of the text itself.
Our desktop and mobile sites currently have typography which makes it difficult to read comfortably. This means that, compared to other more accessible digital text, it takes longer to read our content. Retention, or the ability to remember text that was read, is also affected. An important factor to keep in mind when determining what is optimal for our projects is that people engage both in in-depth reading, as well as scanning of text. We would like to improve our typography to take into consideration and optimize for both of these important ways of using the projects.
In addition, our desktop site does not allow for setting a font size that is comfortable for the user, requiring readers with specific needs and preferences to depend on browser functionality to alter font size. These capabilities vary widely by browser and are not always supported by the remainder of our user interface, often causing issues with tools or navigation.
Annual Plan Context
Ensure a quality reading experience for all users by adapting the default experience for 15% of pageviews, based on the individual needs and constraints of the user. This KR (key result) is focused on allowing the opportunity for our interface to adapt to individual needs when necessary. The theory here is that people will feel more engaged with a website and interface that can adapt based on their needs. This can include work such as dark mode, text and page density, and font size customizations. Some of this adaptation can be done automatically by the interface – for example, creating responsive versions of a feature or tool, or ensuring that dark mode turns on based on the browser or device settings of the user. In other cases, this adaptation can be done through intentional customization – allowing users to select non-default states in specific (but limited) cases. From an accessibility perspective, it will focus on the features that need to be built as standalone to allow for more accessibility, or to allow for setting defaults that are more accessibility friendly, while leaving the opportunity for customization to users who have different preferences. To set the specific number "15%", we looked at how users adapt the default experience in the Wikipedia iOS app. 59% of users of the app are using a non-default theme (dark, black, or sepia). We used this number as a baseline, but factored in our assumption that it is more likely that habitual users of Wikipedia on the web take the time to adapt their reading experience, as opposed to sporadic users.—Wikimedia Foundation, Annual Plan/2023-2024. Wiki Experiences: Reading and media experience. Objective 2.1
Project overview
As part of the accessibility for reading projects, we will focus on two main initiatives to improve readability and accessibility:
- Improving the typography of the site and allowing users to set their preferred typography
- Introducing dark mode that users can opt-in to
Goals for Typography Improvements
The goals of this project are:
- To identify and better understand problems. Review and classify issues with the current typography on our sites
- To make the site easier to read. Improve readability on mobile and desktop sites
- To provide typography that better suits different languages and scripts. Optimize readability for multiple scripts and languages with the support and expertise of the communities
- To allow readers to customize typography. Introducing typographical preferences, useful mostly for people with distinct needs and preferences
Project overview
Typography Improvements
| Phase | Timeframe | Description | |
|---|---|---|---|
| 1a | Research and literature review | July– | This helps us identify existing research into optimized typography settings for digital medium (desktop and mobile) |
| 1b | Discussing font size with various communities | In our previous user testing, we identified that most users taking part in the testing, coming from different communities, were open to a font size increase. We would like to continue this conversation with communities, specifically focusing on various languages and scripts to determine whether and how defaults should change based on language and project | |
| 2a | Prototype testing | We plan on testing prototypes for typography changes and typography preferences with both logged-out and logged-in users | |
| 2b | Iteration based on testing results | ||
| 3 | Release to pilot wikis | Not defined | |
| 4 | Release to all wikis | Not defined | |
Earlier research and explorations
- Literature Review: Readability and Optimal Text Settings
- Typography: Apply consistent font sizes across Vector 2022 (T313828)
- Hypothesis: Typographical and palette customizations (T341631)
- Typography: Increased font-size design for Vector 2022 (T254055)
- User research from Vector 2022 (Fifth prototype testing)
- Fifth prototype testing reasoning (Fifth prototype testing#Font size)
Project evaluation
The success of this project will be measured by a combination of qualitative and quantitative methods. In particular, we will be looking at the following:
- Research-supported decisions in prototype creation and development
- Qualitative improvements in overall readability based on user testing and community conversations
- At least X% of all sessions longer than Ys who customize typography
- Note: exact variables TBD
- No significant change to reading depth