Fitur Baca/Situs/Keteraksesan Fitur Baca/Pembaharuan
|
Pengujian aksesibilitas
 Typographical changes and preferences making the site more accessible
|
The interface of Wikimedia projects must be accessible and readable, regardless of language or script. This includes both the majority as well as individuals with specific needs. The current typography on desktop and mobile makes readability difficult, though. Also, night mode can be helpful in low-light settings and for users who prefer low-contrast reading environments. Our interfaces do not provide this functionality now.
We would like to change the default typography. We will also build additional settings for typography and night mode as preferences. These changes will be available for both logged-in and logged-out users.
Project overview
As part of the 23/24 annual plan, the Web team's goal is to bring appearance settings for all users and change the default typography of all wikis. The default font size and text line height for all users across wikis will increase. This increase will improve readability for the majority of users. The team plans to make this deployment alongside the deployment of a new appearance menu which allows controls for page width, typography, and the upcoming dark mode – meaning that users will easily be able to adjust the font size back to the previous default.
The team plans to initiate discussions across all wikis, focusing on debugging current features and generating ideas for future enhancements. Then, the team will proceed with deployments, bringing the appearance menu to all users and the new typography defaults to logged-in users only. The deployment will be conducted in two steps, initially targeting a small set of wikis for testing before implementing changes across all wikis.
The decision to modify default typography is informed by research findings and accessibility recommendations. Currently, the WCAG recommendations for font size start with a minimum of 16 pixels and a AAA recommendation of 18 pixels for easy reading. Our current default is 14 pixels. This makes it more difficult to read (when compared to similar sites for long-form reading that are following these guidelines). On the other hand, we are aware that scannability (being able to scan and quickly find specific information within the page) is important for Wikipedia and that we should limit changes in text density when setting a new font size. The planned default font size is 16 pixels. This is based on:
- Readability research, academic studies, and market research: these sources indicated that generally bigger is better in terms of font size.
- Most long-form reading websites (such as news websites or social media) opt for somewhere between 16 and 18 pixels. In the two studies that specifically focused on increasing the font size of Wikipedia, researchers determined that increasing size improves comprehension.
- Our own research has shown that most reading sessions are 20–30 seconds long. This isn't enough to digest and change a type setting. This option gives the readability benefits of the new default to the most people possible with the least amount of user effort.
- Accessibility recommendations
Community-proposed designs: 632 logged-in users from 13 Wikipedias submitted designs with typography settings that they considered as comfortable for them. While many designs focused on keeping the default the same, the majority of designs chose a larger font size.
Updates
Juni 2024: Typography and dark mode deployments, new global preferences
Earlier this month: Appearance menu available for everyone and typography changes for logged-out users
In early June, we increased the default font size for logged-out users in Vector 2022. Learn more about this deployment. In a few months, we will study how many logged-in users switch to standard and start a conversation on whether it makes sense for logged-in users to make the switch as well.
Global preferences for the Appearance menu
It is now possible to select a preference for the text size, page width, and color applying to all wikis. To do that, go to your global preferences. Thank you all for questions and patience!
Dark mode coming out of beta!
- Dark mode will soon be available for logged-in users on all Wikipedias, and for logged-out users on select Wikipedias. This will apply to the mobile web version first, and then desktop. The default will remain as "light mode", and we will ask users to opt into dark or automatic mode.
- The audience that will receive dark mode will vary based on the wiki:
- Tier 1 and 2 Wikipedias: wikis where the number of issues in dark mode when compared to light mode is not significant. These wikis will receive dark mode for both logged-in and logged-out users. Some small issues might still exist within templates, though. We will be adding ways to report these issues so that we can continue fixing templates together with editors.
- Tier 3 Wikipedias: wikis where the number of issues in dark mode when compared to light mode is significant. These wikis will only receive dark mode for logged-in users. We would like to make dark mode available to all users. However, some wikis still require work from communities to adapt templates. Similar to the group above, these wikis will also receive a link for reporting issues that will help identify remaining issues.
- Currently, we are aiming for the following dates for deployment:
- Week of July 1: mobile website (Minerva skin) on the Tier 1 Wikipedias
- Week of July 15:
- desktop website (Vector 2022 skin) on all Wikipedias
- mobile website: logged-in and logged-out on the Tier 2 Wikipedias, logged-in only on the Tier 3 Wikipedias
Work on dark mode continues
Next, we will turn dark mode on automatically based on the device preference. We also want to make dark mode available to logged-out users on all wikis. To do that, we continue to need your help updating templates and colors to be accessible in dark mode. As before, we encourage everyone to work on and report any issues with dark mode. Please see our FAQ and previous messages for details on how to help. Reach out to us if you have any questions!
Background
Why it is important to work on this
Over the past few years, we have introduced the Vector 2022 skin across many wikis. We have designed it to improve the reading experience. Another goal was to provide an experience that 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 we recognized was the size of the text itself.
Compared to the more accessible digital text, it takes longer to read our content on desktop and mobile. The ability to remember text that was read is also affected. An important factor to keep in mind is that people engage both in in-depth reading and skimming of text.[1] We would like to improve our typography for both of these ways of using the projects.
Also, our desktop site does not allow to set a font size that is comfortable for the user. Instead, readers with specific needs and likings depend on browser functionality to alter the font size. These capabilities vary by browser and are not always supported by the rest of our user interface. This causes issues with tools or navigation.
Annual plan context
Quotation from the Foundation's 2023/2024 annual plan
|
|---|
|
Goals
Typography improvements
The goals of this project are:
- To identify and better understand problems. Review and classify issues with the current typography on wikis
- 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 with the support and expertise of the different communities
- To allow readers to customize typography. Introducing typographical preferences, useful mostly for people with distinct needs and likings
Night mode
- Improving the readability of articles in low-light settings
- Making night mode options and settings easily discoverable and usable
Timeline and phases
Typography improvements
| Phase | Timeframe | Description |
|---|---|---|
| Research and literature review | Juli– | We learned what researchers say about typography for desktop and mobile |
| Prototype testing + discussing with communities | Oktober– | Most editors taking part in the previous testing were open to a font size increase. They came from different communities. |
| Beta feature deployment | Desember 2023 | We released the typography improvements as a beta feature to all wikis and encouraged communities to try it out and give us their feedback |
| Release to pilot wikis | Iteration based on testing results in collaboration with testing communities | |
| Discussions with communities | April/ | Announcing the upcoming change and answering questions. This will take 2-3 weeks |
| Release to all wikis | Mei/ |
|
Night mode
| Phase | Timeframe | Description |
|---|---|---|
| Technical review | September– | We reviewed ideas for implementation of night mode and decided what implementation we want to use. We reviewed the dark mode gadget, night mode on the apps, etc. |
| Discussing with communities | We started working with technical editors to adjust the community-controlled code (like templates) so that night mode works well. | |
| Pilot release | Maret– | The first version is only available for logged-in users. On mobile, it's only available in the advanced mode. On desktop, it will be a "beta feature". |
| Release for all users | Not defined | When community-controlled code is adjusted, night mode will be available for logged-out users. |
Get involved and Contact
- Promote and adjust the code on wiki, following our recommendations: to roll out our changes for logged-out users, community-controlled code, like templates, needs to be adjusted. It may need discussions on village pumps. It will also need many edits. Help us by starting such conversations and making such edits.
- See the recommendations for night mode compatibility on Wikimedia wikis
- Review and address issues with color contrast on your project using our night mode checker tool
- Review and fix issues with ambiguous colors using our linting tool
- Review error reports from users on your project on our reporting page (note you can modify where these reports go to by editing the page MediaWiki:vector-night-mode-issue-reporting-notice-url).
- Report bugs: create a task in Phabricator and add #fy2023-24-we_2.1_typography_and_palette_customizations project.
.jpg)
Project evaluation
We will measure the success of this project with qualitative and quantitative methods. In particular, we will be looking at:
- Research-supported decisions in prototype creation and development
- Qualitative improvements in readability based on user testing and community conversations
- At least X% of all sessions longer than Ys who customize typography
- Note: exact variables TBD
- At least X% of all sessions use night mode
- No significant change in reading depth