Wikipedia:WikiProject Usability/Readability guidelines

Size of text

Small text affects readability a lot and has been thoroughly studied by usability experts: Small text is much harder to read for everyone. Usability guidelines recommend a default font size of at least 12 points (about 16 pixels, but pixels are evil).

Reducing text size causes usability issues:

1. The first usability issue to consider is readability. An extensive number of usability studies were made about the impact of text size on readability. They found that small text is much harder to read, for example by reducing reading speed: if a text with a comfortable size would be read by average users in 15 seconds, the same text in a smaller size would be read in 27 seconds. The default font size on Wikipedia is already too small (9 points instead of 12 points), so we don't want to make it even smaller.
2. The biggest usability issue is for elders (and possibly anyone older than 40), normal users with low vision and normal users with a particular resolution, device, and such. A significant number of these users don't know how to zoom with their browser. They might not know how to use "Ctrl +/-", or they forget it. So when they encounter such small text they have trouble reading, their only option is to come very close to the screen and strain their eyes as much as they can. Until they succeed or give up.

For these reasons, it is better to not reduce the size of the body text.

Note that people with significant visual handicaps often use special software, so they are not the main targets for this guideline.

Examples

See also: user:Edokter/fonttest

Adjusting pixels

Note: when viewing these examples, results may vary if you have customized the font size in your browser or style sheet, if you are using the zoom ("Ctrl +/-") – note that "Ctrl 0" resets zoom to default – or depending on your screen and its resolution.

• Font size sample: 13 pixels. This is the default text size on Wikipedia.
• Font size sample: 16 pixels. The browser default. This is the recommended text size by usability experts, it enhances readability.
• Font size sample: 19 pixels. This is the recommended text size for elders.

Adjusting ems and relative sizes

• Font size sample: 75%. The result is similar to <small>, and really too small to be read comfortably. Users without particular vision impairments might have a lot of trouble to read it.
• Font size sample: 0.95 em. Similar to the default text size.
• Font size sample: 100%. Similar to the default text size.
• Font size sample: 1.3em. Similar to 12 points, the recommended size.
• Font size sample: 130%. Similar to 12 points.
• Font size sample: 1.5em. Similar to 14 points.
• Font size sample: 150%. Similar to 14 points.

How to adjust font size for yourself

For example, to set the font size of references back to 100% (instead of 90%), add the following code to your CSS page.

div.references
{
  font-size: 100% !important;
}

Templates used to resize text

• Template:Resize

Resources on readability

There are many useful resources about readability on the Web, but these stand out:

• An overview of readability best practices
• Research on readability, for advanced users or Wikiproject members
• List of further references at the Wayback Machine (archived 2007-10-06)

Overuse of color, and too many contrast changes

Status: Completely under construction.

Needs to be expanded, needs references, etc. But this topic is also important.

Introducing {{Gradient}}. Edokter

It is beautiful. But from a usability point of view, overuse of gradient is quite distracting for the eye and reduces readability. Too much useless strain on the eye. Dodoïste (talk) 00:40, 29 September 2010 (UTC)

Only if use with stoopid colors. — Edokter • Talk • 00:43, 29 September 2010 (UTC)

Not only. I meant overuse in a matter of quantity. Not really in a matter of color choice quality because soccer projects will have their way anyway (as well as many other projects, its just an example so don't take it personally). Do you consider Template:Gradient/testcases as good examples? I absolutely don't. There are too may contrast and color variations, and the eye needs to get adapted at every change of contrast. In the end, it simply makes it waaay longer to read.

It would be great if it was only used in table headers, for example. Thus, it would not disturb the reading of the main content. Dodoïste (talk) 01:12, 29 September 2010 (UTC)

Not to be conflated with accessibility/length

"Accessibility" is related to article length, not readability (see WP:NOTPAPER). We do not delete content because an article is "too long." That violates WP:Preserve, a policy, not a guideline. Instead, we split/fork off aspects of the whole topic that have become an undue weight problem. Splitting long articles and leaving adequate summaries is a natural part of growth for a topic (see WP:Summary style).

Discussions

See this layout proposal. This layout used on the French Wikipedia was reviewed by an accessibility expert and another accessibility expert specialized in dyslexia.

Accessibility review of the French layout for discussions

The visual delimitations provided by blocks of text and lines have a major impact for users with dyslexia. Among the most commons cases are text justification, too much contrast and interline spacing within a paragraph. However, dyslexia is only one case among many others, mentioned here because it is the most evidently concerned. --Temesis

First input received, about dyslexia – a sizable portion of our audience:

> Does this layout with its border and alternating background color makes reading easier from your point of view?

Without any hesitation, YES, and its a passionate outcry!

I'd even say it's like the difference between day and night. With the indentation alone I find myself quickly lost, I have a hard time to distinguish the different users posting, I have a hard time to see who is replying to who.

It requires more effort to read the text than to understand it's meaning. In small doses its manageable, bot tiredness comes quickly and there comes a time when I renounce.

A simple complementary remark: discussions readability is considerably improved several contexts of the everyday users: when the user is traveling, with suboptimal means of consultation such as a Smartphone and Ipad. For example, it's the first time discussions on Wikipedia is decipherable in the train, to be very prosaic. --Temesis (d) 3 février 2010 à 14:45 (CET)

Needs translation

Accessibility review of the French layout for discussions (needs to be translated)
The following discussion has been closed. Please do not modify it.
Un autre retour, de portée plus générale: L'indentation toute seule pour des threads ? L'ergonomie limitée par la technique il y a longtemps, tu connais evidement ? Je voyais ça oublié. C'est drôle de voir ça aujourd'hui sur un site comme wikipedia. Quand c'est évident qu'on peut faire beaucoup mieux (ton 2ème exemple) --Temesis (d) 3 février 2010 à 16:13 (CET) C'est ma réponse que Temesis cite dans son premier exemple. L'accessibilité des sites Web est mon domaine depuis des années et je suis dyslexique... j'ai donc cherché à comprendre pourquoi tant de sites me posaient des problèmes, quelles solutions pouvaient y remédier. Il est particulièrement important de guider le regard, et cela me ramène au sujet de cette discussion, les bordures qui délimitent clairement les différentes interventions.--Monique Brunel (d) 3 février 2010 à 19:56 (CET)

Delimitation: What "readibility" is not

 Done At Wikipedia, the typical standard readability description applies:

Readability is the ease with which a reader can understand a written text. In natural language, the readability of text depends on its content (the complexity of its vocabulary and syntax) and its presentation (such as typographic aspects that affect legibility, like font size, line height, character spacing, and line length).

Unfortunately, some fringe editors try to use the argument that readability applies to article length, and they do it as part of their "I don't like it" attempts to get rid of content (and whole articles if they can get away with it) they don't agree with. Article length is determined by many factors, especially complexity, notability, controversiality, and the sheer amount of RS coverage. Some topics are not worthy of a long article, and others are worthy of a large mother article and many daughter sub-articles.

They also conflate the issue with "accessibility", which does relate to article length (see WP:NOTPAPER). We do not delete content because an article is "too long". Instead, we split/fork off (see Wikipedia:Summary style) content that creates an undue weight problem for a mere aspect of the whole topic.

Some topics lend themselves to easy reading, like reading a novella, and are accessible to even grade school readers. People will often sit down and read the whole article. Other topics are more accessible to university graduates, and yet others are so long and complicated that they are only of interest to researchers seeking information, facts, historical context, and opinions/reception, and such articles are definitely not "easy reading". They are best used to find information by searching for specific words and phrases on the page. Few people sit down and read them from top to bottom, sometimes 50-80 printed pages, maybe more. Their readability can be perfect, but their sheer length and complexity make them harder to than a novel. That's okay.

We simply have myriad types of articles, and we should not dumb down a complex and long topic to read like a short novella read by fourth graders. "Readability" applies to the things mentioned in the lead quote above and does not refer to article length.

Could we add this "not article length" delimitation? We need something we can point to in discussions with such fringe editors. -- Valjean (talk) (PING me) 02:50, 26 August 2022 (UTC)

 Done at #Not to be conflated with accessibility/length. -- Valjean (talk) (PING me) 15:31, 29 August 2022 (UTC)