Reading/Web/Desktop Improvements/Fifth prototype testing/id

Kami mengharapkan umpan balik Anda perihal desain yang akan diterapkan di kulit Vektor 2022. Desain yang diterapkan tersebut berupa penyempurnaan teks, tombol, garis tepi, latar belakang, hingga pemberian jarak.

Panduan
Harap perhatikan hal berikut ini:
 * 1) Bacalah seluruh halaman ini terlebih dahulu agar Anda memahami konteksnya
 * 2) Buat bagian baru pada halaman ini menggunakan formulir yang tersedia di bawah (pertanyaan akan terisi secara otomatis dan Anda hanya perlu menjawab pertanyaan tersebut)
 * 3) Isi umpan balik Anda pada bagian titik-titik (...) yang tersedia di sana.
 * Semua desain dan fitur yang Anda lihat saat ini masih dalam tahap uji coba, jadi sangat besar kemungkinannya terjadi galat maupun kendala di dalamnya.
 * Untuk "formulir bagian baru", saat ini masih belum kompatibel dengan VisualEditor. Apabila Anda menggunakan VisualEditor, silakan buat bagian baru secara manual dan lakukan salin tempel (copy paste) dari daftar pertanyaan umpan balik yang terdapat di bawah subjudul ini.
 * Anda tidak perlu mencoba semua fitur yang ada di sini, silakan fokus kepada fitur yang menarik perhatian Anda.
 * Estetika desain maupun visual merupakan penilaian subjektif bagi setiap orang. While we are all entitled to our own opinions we ask that you do your best to explain yours, and how they relate to our design goals of simplicity and usability.
 * Pilihan yang Anda inginkan mungkin tidak tersedia pada halaman ini. Maka dari itu, kami dengan senang hati menerima masukan perihal pilihan yang mungkin sesuai untuk berusaha kami wujudkan. Apabila Anda memiliki kemampuan dalam desain dan/atau pemograman, silakan tambahkan prototipe yang Anda buat sendiri (opsional). Berkas desain Vektor 2022: Figma, Sketch, Google Drawing. Prototipe Vektor 2022: GitHub.
 * Jika Anda ingin mengirimkan ide milik Anda, jangan sunting halaman ini. Silakan kirimkan ide Anda melalui formulir umpan balik yang tersedia.
 * Kami sangat mengapresiasi siapa saja, baik mereka yang masih pemula hingga sudah berpengalaman. Kami akan memeriksa seluruh umpan balik dan ide yang masuk, serta keputusan final akan diambil berdasarkan penilaian dari mereka yang sudah ahli/berpengalaman.
 * Apabila Anda memilih untuk mengirim umpan balik via surel (email), silakan menghubungi Olga Vasileva di [mailto:Olga@wikimedia.org olga@wikimedia.org].

Daftar pertanyaan umpan balik

 * 1) Menu — silakan membuka prototipe berikut di tab baru: https://di-visual-design-menus.web.app/Brown_bear. Dari pilihan yang tersedia, mana yang sesuai dengan keinginan Anda? Pastikan untuk memeriksa menu pencarian, pengguna, bahasa, hingga peralatan.
 * 2) Garis tepi dan latar belakang — silakan membuka prototipe berikut di tab baru: https://di-visual-design-borders-bgs.web.app/Zebra. Dari pilihan yang tersedia, mana yang sesuai dengan keinginan Anda?
 * 3) Subjudul yang terpilih/tersorot di bagian daftar isi — silakan membuka prototipe berikut di tab baru: https://di-visual-design-toc-active.web.app/Otter. Dari pilihan yang tersedia, mana yang sesuai dengan keinginan Anda?
 * 4) Logo di bagian atas — silakan membuka prototipe berikut di tab baru: https://di-visual-design-header-logo.web.app/Panda. Dari pilihan yang tersedia, mana yang sesuai dengan keinginan Anda?
 * 5) Warna pranala — silakan membuka prototipe berikut di tab baru: https://di-visual-design-link-colors.web.app/Salmon. Apakah ada beberapa hal yang perlu kami perbaiki sebelum kami menerapkan perubahan tersebut?
 * 6) Ukuran teks — silakan membuka prototipe berikut di tab baru: https://di-visual-design-font-size.web.app/Hummingbird. Apakah ada hal yang menjadi perhatian Anda perihal ukuran teks di prototipe tersebut?

Latar belakang dan konteks
Selama dua tahun terakhir, kami melakukan berbagai macam perubahan dan pembaruan tampilan antarmuka. Kami sudah mengatur posisi dari kotak pencarian, ubah bahasa, hingga daftar isi. Selain itu, kami juga merapikan beberapa pranala dan peralatan ke dalam bagian menu. And we have limited the content width, added a sticky header, and moved the page title above the page toolbar. Now, with all of these various elements situated in the updated interface, we are turning our attention to the overall look. Some initial questions our team has been considering are:
 * How can we use visual design to improve the interface?
 * Do we think there is value in the skin having some additional personality (like the blue lines and gradients in Legacy Vector)?
 * At what point there's too much of it, such that it might become distracting or make the interface confusing?
 * What if we do as little as possible, and take a super minimalist approach similar to the original Wikipedia interface?

Historically our approach has been simple and functional. There is little styling (if any) to the HTML elements, which simplifies the interface both for people using it and for people designing and building it. It also means that our visual design is rather timeless. We don't chase the trends and don't need to make changes every couple of years. Looking at the screenshots below we can see how Monobook and Legacy Vector use visual design sparingly (mainly borders and background colors).

Menu
We use several menus in our interface. Thus far our approach to how we style menus has not been consistent. We have an opportunity, with Vector 2022, to develop a more accessible and consistent approach to the styling of our menus. In their most simple form menus have two elements: a menu trigger, and menu items. We're considering blue vs. black (for both the menu trigger, and the menu options), and bold vs. non-bold (for the menu trigger).

Link to prototype with options: https://di-visual-design-menus.web.app/Brown_bear

Garis tepi dan latar belakang
Should we add borders and backgrounds to help divide up the regions of the interface, and if so how should they look? As we mentioned in the Background and context section above, both Monobook and Vector use backgrounds and borders to separate the interface from the content. Backgrounds and borders can also add personality to the interface. However, it is difficult to know how functional or necessary they are. We've created several options with progressively more/darker borders and backgrounds.

Link to prototype with options: https://di-visual-design-borders-bgs.web.app/Zebra

Subjudul yang terpilih/tersorot di bagian daftar isi
The table of contents is now on the (left) side of the article, and is fixed in place so it remains visible as you scroll down the page. A new feature is that the table of contents indicates which section of the article you are currently reading (we call this the "active section"). Currently, following from a pattern used on the Article/Talk tabs, the active section in the table of contents is black, and the non-active sections are blue. We like this pattern because it is simple, not distracting, and used elsewhere. We could also use additional styling to indicate the active section.

Link to prototype with options: https://di-visual-design-toc-active.web.app/Otter

Logo di bagian atas
Monobook and Legacy Vector both feature a square Wikipedia logo with a large globe. Given the various changes to Vector 2022 a smaller, rectangular logo in the corner may fit the layout better. However, we wanted to make sure to try various options. Please remember to try these options at various screen sizes, as the balance of the layout shifts depending on your screen size.

Link to prototype with options: https://di-visual-design-header-logo.web.app/Panda

Warna pranala
The World Wide Web Consortium (W3C) have Web Content Accessibility Guidelines. These guidelines define a minimum contrast level for links: "For usability and accessibility, links should be underlined by default. Otherwise, link text must have at least 3:1 contrast with surrounding body text, and must present a non-color indicator (typically underline) on mouse hover and keyboard focus." Since we do not underline links by default, our link color choice must meet the 3:1 contrast requirement. In order to check the contrast of our links with our body text we can use the contrast checker provided by WebAIM.

Additionally, the proposed blue link color is already part of the Wikimedia Design Style Guide, and is used on our mobile websites as well as in various project logos, so we would be gaining consistency.

Link to prototype with proposed colors: https://di-visual-design-link-colors.web.app/Salmon

Ukuran tulisan
The mission of our movement is to provide all of the world's knowledge to as many people as possible. Currently the majority of the knowledge we offer is in the form of text. Research has shown that typographic settings (such as font size, line length, and line height) influence the experience of reading, both in terms of general comfort (i.e. eye strain and fatigue), and comprehension and retention. Therefore it is important for us to use optimal typographic settings in our interface. 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.

In a previous phase of the project we read research studies regarding the line length and concluded that between 90–140 characters per line is optimal for our projects (link to writeup). Recently we have spent time reading research studies about font size. The most convincing, and directly applicable, research we have found thus far is a 2016 study that used eye-tracking to evaluate the affects of font size and line spacing for people reading Wikipedia:

Using a hybrid-measures design, we compared objective and subjective readability and comprehension of the articles for font sizes ranging from 10 to 26 points, and line spacings ranging from 0.8 to 1.8 (font: Arial). Our findings provide evidence that readability, measured via mean fixation duration, increased significantly with font size. Further, comprehension questions had significantly more correct responses for font sizes 18 and 26. These findings provide evidence that text-heavy websites should use fonts of size 18 or larger and use default line spacing when the goal is to make a web page easy to read and comprehend. Our results significantly differ from previous recommendations, presumably, because this is the first work to cover font sizes beyond 14 points.

Firstly, we need to convert the measure used by the researchers (points) into the measure that browsers ultimately render (px). The conversion is: 1px = 72pt / 96. So the range studied in the research (10–26 points) is equivalent to 13.3–34px. Their conclusion, 18 points, is equal to 24px. So should we increase the font size to 24px? The research studied in-depth reading, however people often scan the page in order to find a certain piece of information. This is a different reading behavior, that arguably benefits from a smaller font size than in-depth reading does. Our conservative proposal, taking into account scanning, is to increase the font size to 16px to begin with. (We would be increasing the maximum width of the article as well, from 960px to 1050px.) As a next step, we will plan to conduct our own research to further study font size on Wikimedia wikis.

Annotated bibliography of typography and readability research

Link to prototype with proposed font size: https://di-visual-design-font-size.web.app/Hummingbird