Wikipedia:WikiProject Usability/Readability guidelines: Difference between revisions

Content deleted Content added
add how-to template
 
(28 intermediate revisions by 9 users not shown)
Line 1:
{{Wikipedia:WikiProject Usability/Navigation menu | Layout}}
{{Wikipedia how-to|pages=at [[Wikipedia:Manual of Style/Accessibility]].}}
 
== Size of text ==
<div style="color:black;"><strong>Status: Under construction, but necessary informations are present. Needs to be organized into a guideline.</strong></div>
 
Small text affects readability a lot and has been thoroughly studied by usability experts: [http://www.laurenscharff.com/research/SWExp.html 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 (for example, to 75%) causes usability and accessibility issues:
#The first usability issues to consider is [[readability]]. An extensive number of usability studies were made about the impact of text size on readability. It was clearly stated that small text makes it way harder to read, for example by reducing reading speed: if a text with comfortable size would be read by average users in 15 seconds, the same small size text 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.
#The second and third issues are both usability and accessibility issues. First, users with low vision that have severe low vision (but are still able to read really large fonts) use dedicated software to enlarge or reduce the text size. So they will be able to read it. But when the normal text size changes to a very small text size, they may have to adjust their zoom level only for this particular text, and readjust it afterwards. It's suboptimal, but not detrimental.
#The biggest usability issue is for elders (and possibly anyone older than 40), normal users with small low vision and normal users with a particular resolution, device, and such. Truth is, most of these users doesn't know how to zoom with their browser. Yes, they don't know "Ctrl +/-" even exist, or they forget it. So when they encounter such small text they have trouble to read, 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 because of too much strain.
 
Reducing text size causes usability issues:
It would be way easier for everyone to not have to think about such issues, and simply don't ever reduce the font size. It also removes unnecessary code.
# 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.
# 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 ====
{{strong|Note}}: when viewing those examples, result may vary if you have customized your 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.
 
{{strong|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.
*<span style="font-size:9pt;">Font size sample: 9 points. This is the default text size on Wikipedia, and it's way too small.</span>
*<span style="font-size:12pt;">Font size sample: 12 points. This is the recommended text size by usability experts, it enhances readability.</span>
*<span style="font-size:14pt;">Font size sample: 14 points. This is the recommended text size for elders.</span>
 
* <span style="font-size: 13px;">Font size sample: 13 pixels. This is the default text size on Wikipedia.</span>
=== Examples using ems and relative sizes ===
* <span style="font-size: 16px;">Font size sample: 16 pixels. The browser default. This is the recommended text size by usability experts, it enhances readability.</span>
* <span style="font-size: 19px;">Font size sample: 19 pixels. This is the recommended text size for elders.</span>
 
==== Adjusting ems and relative sizes ====
*<span style="font-size:75%;">Font size sample: 75%. The result is similar to <nowiki><small></nowiki>, and really too small to be read comfortably. Users without particular vision impairments might have a lot of trouble to read it.</span>
*<span style="font-size:0.95em;">Font size sample: 0.95 em. Similar to the default text size.</span>
*<span style="font-size:105%;">Font size sample: 100%. Similar to the default text size.</span>
*<span style="font-size:1.3em;">Font size sample: 1.3em. Similar to 12 points, the recommended size.</span>
*<span style="font-size:130%;">Font size sample: 130%. Similar to 12 points.</span>
*<span style="font-size:1.5em;">Font size sample: 1.5em. Similar to 14 points.</span>
*<span style="font-size:150%;">Font size sample: 150%. Similar to 14 points.</span>
 
* <span style="font-size: 75%;">Font size sample: 75%. The result is similar to <nowiki><small></nowiki>, and really too small to be read comfortably. Users without particular vision impairments might have a lot of trouble to read it.</span>
=== Resources on readability ===
* <span style="font-size: 0.95em;">Font size sample: 0.95 em. Similar to the default text size.</span>
Small text affects readability a lot, and has been thoroughly studied by usability experts: [http://www.laurenscharff.com/research/SWExp.html small text is way harder to read for everyone]. Usability guidelines recommend a default font size of at least 12 points (about 16 pixels, but pixels are evil).
* <span style="font-size: 105%;">Font size sample: 100%. Similar to the default text size.</span>
* <span style="font-size: 1.3em;">Font size sample: 1.3em. Similar to 12 points, the recommended size.</span>
* <span style="font-size: 130%;">Font size sample: 130%. Similar to 12 points.</span>
* <span style="font-size: 1.5em;">Font size sample: 1.5em. Similar to 14 points.</span>
* <span style="font-size: 150%;">Font size sample: 150%. Similar to 14 points.</span>
 
=== How to adjust font size for yourself ===
There is any number of useful resource about readability on the Web. But those three stand out:
 
*[http://www.webcredible.co.uk/user-friendly-resources/web-usability/web-page-readability.shtml An overview of readability best practices]
For example, to set the font size of references back to 100% (instead of 90%), add the following code to [[Special:Mypage/skin.css|your CSS page]].
*[http://www.laurenscharff.com/research/web_read_lvs.html Research on readability], for advanced users or Wikiproject members
<syntaxhighlight lang="css">
*[http://www.deyalexander.com.au/resources/uxd/readability.html List of further references]
div.references
{
font-size: 100% !important;
}
</syntaxhighlight>
 
==== Templates used to resize text ====
 
* [[Template:Resize]]
 
== Resources on readability ==
 
There are many useful resources about readability on the Web, but these stand out:
* [http://www.webcredible.co.uk/user-friendly-resources/web-usability/web-page-readability.shtml An overview of readability best practices]
* [http://www.laurenscharff.com/research/web_read_lvs.html Research on readability], for advanced users or Wikiproject members
* {{webarchive|url=https://web.archive.org/web/20071006195750/https://deyalexander.com.au/resources/uxd/readability.html|title=List of further references}}
 
== Overuse of color, and too many contrast changes ==
 
<div style="color:black;"><strong>Status: Completely under construction.</strong></div>
Needs to be expanded, needs references, etc. But this topic is also important.
 
Introducing {{tl|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. [[User:Dodoïste|Dodoïste]] ([[User talk:Dodoïste|talk]]) 00:40, 29 September 2010 (UTC)
:: Only if use with stoopid colors. <span style="font-family: verdana;"> — [[User:Edokter|<b style="color:#008"><i>E</i>dokter</b>]] • [[User_talk:Edokter|<span style="color:#080">Talk</span>]] • </span> 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. [[User:Dodoïste|Dodoïste]] ([[User talk:Dodoïste|talk]]) 01:12, 29 September 2010 (UTC)
 
[[Category:WikiProject Usability]]
== Not to be conflated with accessibility/length ==
 
"Accessibility" is related to [[WP:Article size|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 [http://en.wikipedia.org/w/index.php?title=Wikipedia%3AVillage_pump_%28proposals%29&action=historysubmit&{{diff=|Wikipedia:Village pump (proposals)|387661236&oldid=|387657814 |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. --[[Utilisateur:Temesis|Temesis]]
: First input received, about dyslexia – a sizable portion of our audience:
: <blockquote><p>> Does this layout with its border and alternating background color makes reading easier from your point of view?</p><p>Without any hesitation, YES, and its a passionate outcry!</p><p>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.</p><p>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.</p></blockquote>
: 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. --[[Utilisateur:Temesis|Temesis]] ([[Discussion utilisateur:Temesis|d]]) 3 février 2010 à 14:45 (CET)
 
==== Needs translation ====
 
{{hat|Accessibility review of the French layout for discussions (needs to be translated)}}
{{lang|fr|
: Un autre retour, de portée plus générale:<blockquote><p>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)</p></blockquote>
: --[[Utilisateur:Temesis|Temesis]] ([[Discussion utilisateur: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.--[[Utilisateur:MoniqueBrunel|Monique Brunel]] ([[Discussion utilisateur:MoniqueBrunel|d]]) 3 février 2010 à 19:56 (CET)
}}
{{hab}}{{clear}}
 
=== Delimitation: What "readibility" is not ===
{{done}}
At Wikipedia, the typical standard [[readability]] description applies:
 
{{quotebox|'''Readability''' is the ease with which a [[reading (process)|reader]] can [[understanding|understand]] a [[writing|written text]]. In [[natural language]], the readability of text depends on its [[content (media)|content]] (the complexity of its [[vocabulary]] and [[syntax]]) and its presentation (such as [[typography|typographic]] aspects that affect [[legibility]], like [[font size]], [[line height]], [[Kerning|character spacing]], and [[line length]]).<ref>{{Cite web|title=Typographic Readability and Legibility|url=https://webdesign.tutsplus.com/articles/typographic-readability-and-legibility--webdesign-12211|access-date=2020-08-17|website=Web Design Envato Tuts+}}</ref>}}
 
Unfortunately, some fringe editors try to use the argument that readability applies to article length, and they do it as part of their [[WP:IDONTLIKEIT|"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.
{{hidden|style = border:1px solid black; width: 65%;|header=Accessibility review of the French layout for discussions (needs to be translated)|contents=
{{lang|fr|les gens qui évaluent sont des experts contactés sur le mode « Puis-je te déranger avec un cas d'école si tu as 5mn ? ». A priori, WP ne les intéresse pas plus que cela en soit. Par contre, le cas précis peut les intéresser et les amener à donner un avis qui sera relayé ici.
 
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.
la délimitation visuelle des blocs de texte et des lignes a un impact majeur pour les lecteurs dyslexiques. Parmi les cas les plus couramment abordés, il y a la justification du texte, le contraste trop poussé et l'interlignage/inter-paragraphage (sic). la dyslexie, cela dit, n'est qu'un cas parmi d'autres, mentionné ci-dessus parce qu'il était le plus évidemment concerné.
 
Could we add this "not article length" delimitation? We need something we can point to in discussions with such fringe editors. -- [[User:Valjean|Valjean]] ([[User talk:Valjean|talk]]) ('''''[[Help:Notifications|PING me]]''''') 02:50, 26 August 2022 (UTC)
il n'y a là rigoureusement rien de nuisible pour lecteur dit moyen, si tant est que cette notion soit valide en ergonomie : si les bordures et l'alternance d'arrière-plan constitue selon vous une nuisance pour des utilisateurs, la charge de la démonstration est... à votre charge ;-) Mais c'est extrêmement peu consistant, jusqu'à preuve du contraire.
: {{Done}} at [[#Not to be conflated with accessibility/length]]. -- [[User:Valjean|Valjean]] ([[User talk:Valjean|talk]]) ('''''[[Help:Notifications|PING me]]''''') 15:31, 29 August 2022 (UTC)
 
[[Category:WikiProject Usability|Readability guidelines]]
Bref, ce n'est bien-sûr pas dramatique, mais je crois que vous vous êtes planté sur le fond, pour dire les choses simplement. cela arrive à tout le monde, ce n'est pas grave. Tout comme il peut arriver à un administrateur de faire une modification d'interface unilatérale, mais avisée : on ne va pas lui demander de revenir en arrière, de procéder à un sondage, etc. Ce qui est bien fait est bien fait, c'est la base d'un wiki.--[[Utilisateur:Temesis|Temesis]] ([[Discussion utilisateur:Temesis|d]]) 3 février 2010 à 13:25 (CET)
:Premier retour recueilli, côté dyslexie (une part très loin d'être non négligeable des lecteurs) :
:<blockquote><p>> Est-ce que la mise en forme avec bordure et grisé facilite la lecture de ton point de vue ?</p><p>Sans hésitation, OUI, et c'est le cri du coeur !</p><p>Je dirai même que c'est le jour et la nuit. Avec la simple indentation je suis vite perdue, je distingue mal les différentes interventions, je retrouve difficilement qui répond à qui...</p><p>L'effort de lecture prend le pas sur l'effort de compréhension de ce que je lis. A très petite dose cela reste gérable mais la fatigue s'installe vite et il m'arrive de renoncer.</p></blockquote>
:je ne pense pas qu'il y ait à chercher beaucoup plus loin pour valider, puis systématiser cette modification du rendu, faite sur une base purement intuitive et personnelle, mais très bien vue.
:une remarque simple, en complément: la lisibilité des discussions gagne considérablement dans un contexte utilisateur lambda: celui où l'on est en déplacement, avec des conditions de consultation mobiles pas optimales (smartphone, bientôt ipad). Pour ma part, c'est la première fois qu'une discussion sur WP est déchiffrable dans le train, pour être très prosaïque. --[[Utilisateur:Temesis|Temesis]] ([[Discussion utilisateur:Temesis|d]]) 3 février 2010 à 14:45 (CET)
:Allez, un autre retour, de portée plus générale:<blockquote><p>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 drole de voir ça aujourd'hui sur un site comme wikipedia. Quand c'est évident qu'on peut faire beaucoup mieux (ton 2ème exemple)</p></blockquote>
:On peut s'arrêter là ou est-ce qu'il faut convoquer un colloque {{clin d'oeil}} ? --[[Utilisateur:Temesis|Temesis]] ([[Discussion utilisateur: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.
::Rien que répondre ici me demande un effort considérable. Je suis démunie face à la syntaxe Wiki qui perturbe mes acquis fondamentaux de lecture. Retrouver une intervention dans un long bloc de texte sans aucun point de repère, respecter le fil des réponses, respecter la syntaxe des indentations et le nombre de signes :... je ne veux pas faire le procès d'une syntaxe dont je reconnais l'utilité, juste montrer quelques difficultés liées à la dyslexie.
::S'il n'est pas possible de remédier à ces problèmes dans les blocs d'édition, il n'en va pas de même des pages Web.
::Tout ce qui peut améliorer le confort de lecture est bienvenu : titres et sous-titres clairement identifiables comme tels, paragraphes courts et suffisamment espacés, pas de texte justifié, pas de contenu en majuscules...
::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.--[[Utilisateur:MoniqueBrunel|Monique Brunel]] ([[Discussion utilisateur:MoniqueBrunel|d]]) 3 février 2010 à 19:56 (CET)
}}}}