|
|
Log in / Subscribe / Register

Separating legibility fact from myth

We're bad at marketing

We can admit it, marketing is not our strong suit. Our strength is writing the kind of articles that developers, administrators, and free-software supporters depend on to know what is going on in the Linux world. Please subscribe today to help us keep doing that, and so we don’t have to get good at marketing.

By Nathan Willis
November 11, 2015

ATypI

An interesting aspect of the annual ATypI conference is that it provides a forum for researchers working on text legibility and related problems to present their findings. The 2015 conference in São Paulo, Brazil was no exception; various sessions addressed font display in automotive navigation systems, the effectiveness of text markup, and how factors like spatial frequency impact users' ability to read text. There was also an entire session dedicated to debunking oft-repeated myths about how fonts can affect readability for users with dyslexia.

Fonts and combating dyslexia

Bruno Maag and Alessia Nicotra tackled the persistent myth that someone can create a font that counteracts the symptoms of dyslexia. Attempts to do so are a surprisingly common occurrence, they noted, with Chrisian Boer's Dyslexie, Robert Hillier's Sylexiad, and Abelardo Gonzalez's OpenDyslexic being just a few of the recent examples. But these projects invariably misunderstand the symptoms of dyslexia, attributing them (and, usually, limiting them) to visual confusion—such as having trouble distinguishing between "b" and "d" due to their similar-but-mirrored shapes. In fact, the research is clear that dyslexia impacts language processing in a different part of the brain altogether from where images are processed.

[Alessia Nicotra and Bruno
Maag]

Nicotra listed the clinically recognized symptoms of dyslexia, only a few of which are observable in a visual context. Rather than manifesting in the temporal lobe, where visual input is processed (and where letters are recognized, followed by syllables and words), dyslexia symptoms affect the language-processing center in the brain's phonological area. Consequently, the real symptoms of the condition also are observed in hearing (such as the inability to recognize alliteration or rhyme) and the semantic processing of language. Some say dyslexia is over-diagnosed, particularly by non-physicians, but it is fairly well defined in the medical community. Nevertheless, the myth persists that by using fonts with altered letterforms (as in the Dyslexie and OpenDyslexic fonts, in particular), patients can overcome the condition and improve their reading proficiency.

The research does not bear this out, however, Maag said. He then discussed several recent papers and doctoral dissertations that reported finding improved reading comprehension or comfort when certain changes were made to the way text on screen or paper is displayed. But the findings tend to underscore well-known principles of good, legible typography—such as increasing contrast, increasing stroke weight, and using a sufficiently large x-height. Thus, the changes that result in better legibility for readers with dyslexia also improve legibility for readers without dyslexia. He also pointed to a paper by Thomas Phinney that found there was no statistically significant difference found in readability tests of Dyslexie versus Arial. Finally, Maag noted that tests show that increasing the spacing between letters and between lines of text increase reading speed—again, both for readers with dyslexia and those without.

The takeaway, he said, is that there is not a magic bullet, especially not at the level of font design. Rather, improving the viewing conditions for the reader benefits legibility, comprehension, speed, and comfort—regardless of medical issues like dyslexia. The good news, he reminded the audience, is that reading is a learned skill for everyone, and everyone requires practice. While scientific research shows that font choices do not have a greater impact on people with dyslexia, research also shows that, with a degree of additional practice, the majority of children with dyslexia are able to achieve reading proficiency equal to their classmates.

Reading, legibility, and comfort

While Maag and Nicotra took on a long-held misconception, several other speakers presented work that looked at new ways of assessing or improving text readability. Kevin Larson from Microsoft's Advanced Reading Technologies (ART) group presented his work on how spatial frequency relates to text legibility. The central notion is that, as with all visual stimuli, the human eye's ability to distinguish important features in a line of text hinges on the size of those features when they strike the retina—which, in SI units, is measured in cycles per degree (cpd). A high spatial frequency corresponds to more details crammed into the same space, therefore it means a higher cpd.

Measuring text in cpd makes intuitive sense, since it normalizes measurements to the eye's frame of reference, but it is rarely what is done in practice. In research, reading tests often note the font size used, which does not indicate the physical size of strokes or of important features like the crossbar on "e" (which is the feature that distinguishes it from "c"), nor take into account the reader's distance from the display. Larson led ART studies that tested how accurately participants could read text as a function of spatial frequency. The results included some real-world numbers, like the fact that test subjects could read text with a spatial frequency of up to 50 cpd.

[Ann Bessemans and Kevin
Larson]

That 50 cpd number is averaged across all of the subjects and is the upper bound that readers may be able to see; the actual legibility threshold for any given reader varies continuously, since it is dependent on a number of other factors. The team found that high-contrast text was necessary to reach that 50 cpd upper bound, and that contrast proved to be more important than screen resolution—which is often cited as improving legibility. But the team also noted that real-world conditions can make achieving the required contrast impossible. Screen backlights, ambient lighting, and age-related loss of visual acuity can limit how much contrast is possible. Larson concluded that, ideally, text interfaces should be adjusted continuously to provide optimal contrast and optimal spatial frequency for the user.

Continuously adjusting text displays may sound far-fetched but, interestingly enough, the underlying idea was backed up by the findings of another speaker. Keitaro Sakamoto from Morisawa Type reported on that company's tests with changing the font weight of display text in automotive navigation systems, based on the ambient lighting conditions. The issue, he said, is that road tunnels in Japan are substantially brighter than in many other regions, and the brightness change causes problems for drivers at night.

The researchers tested a system where font weight was increased from light to medium to bold depending on whether the car was in daylight, a tunnel, or outside at night. They measured both the reaction time of the driver and the correctness of the driver's response (e.g., "change to the left lane now"). As expected, the responses were improved by adjusting the font weight, which would seem to align with the ART team's research. Interestingly, though, the team found significant differences between the effects when used on kanji and on kana text. It is not clear if the distinction has to do with the relative densities of the two scripts, or with the different semantic ways they are used in normal Japanese writing.

Larson also presented a shorter session that outlined some recent ART work exploring text mark-up. The research team explored comprehension, both with new readers (e.g., children) and with experienced readers when confronted with hard-to-parse text. It found three mark-up techniques that seem to improve reading comprehension. First, marking the syllable boundaries in a word (such as with a small or light-colored dot or tick mark) significantly improves readers' ability to recognize and decipher unfamiliar words.

Second, it found two techniques that helped readers parse garden-path sentences—semantically tricky constructions like "She knew the answer was not correct." On a first-time read-through, such sentences are often parsed incorrectly—for instance, "She knew the answer" is likely to be the reader's analysis of the first part of the sentence, only to be reversed when the second part is read. Interestingly enough, rendering all verbs in a different color and encasing subordinate clauses [in brackets] both improved comprehension without impacting reading speed. While these techniques might not appeal to publishers or software makers for general display usage, Larson felt that they could prove useful as accessibility aids.

Scientific research is, naturally, a continuous process. It is interesting to note, for example, that legibility researcher Ann Bessemans presented her own findings from a reading-comfort study that found a negative correlation between comfort and regular visual rhythms in a line of text. That is, a strong, regular pattern of light and dark—as one usually sees between the vertical strokes and the white spaces in text—seems to increase reader discomfort and fatigue. That would seem to conflict with established conventional wisdom, which teaches that irregular rhythm is bad for reader comfort. But, Bessemans noted, the historical research on reading comfort is frustratingly vague in its definitions, and measuring comfort is difficult to do in an artificial, laboratory-like setting. Her primary takeaway is that more rigorous research is called for, as is a more formal approach to defining and assessing reader comfort.

In the software industry, legibility issues often fall to online publishers and UI designers to deal with. But it is interesting to note how deeply some of the findings could affect software development. Better mark-up options for accessibility might not be difficult to implement, but continuously adjusting the text contrast in response to lighting conditions is another matter altogether. Yet there are few software interfaces that can afford to dispense with all concerns about text readability.

Index entries for this article
ConferenceATypI/2015


to post comments

Separating legibility fact from myth

Posted Nov 15, 2015 19:40 UTC (Sun) by huftis (guest, #58900) [Link] (1 responses)

Interestingly enough, rendering all verbs in a different color and encasing subordinate clauses [in brackets] both improved comprehension without impacting reading speed. While these techniques might not appeal to publishers or software makers for general display usage, Larson felt that they could prove useful as accessibility aids.

I think these techniques may be more useful for computer code. Syntax highlighting already uses the rendering all verbs in a different color trick, by highlighting strings, function names, variables and literals in different colours.

One can also imagine using different background colours for various levels of nested function calls. It can even be used for regular expressions. The RegExr site already does this. Here’s an example of /(?:#|0x)?(?:[0-9A-F]{2}){3,4}/ shown with background colours based on nesting level. (It matches 24 or 32 bit hex colours, with an optional leading # or 0x, and is taken from the RegExr examples).

Separating legibility fact from myth

Posted Nov 18, 2015 8:06 UTC (Wed) by nix (subscriber, #2304) [Link]

It would probably work better for simple garden-path headlinese sentences such as (to pick a recent one) "Donald Trump fights to break wind farm in Scotland" where you simply hit a point where you have to reparse the whole sentence to figure out what's going on: in that case, the correct parse falls into place fairly naturally once you have the whole sentence.

What might need a slightly differnt approach is monsters like the old famous one "Violinist linked to JAL crash blossoms" where you get to the end and go "what?" and reread it twice and still cannot figure out what on earth a valid parse might be. This is often linked to constructional problems: e.g. bizarre noun or verb phrases that you don't even know might *be* phrases at all (a 'JAL crash', in this case), so your parse tree is malformed and a proper parse is impossible. In that case you might want to try something like fairly subtle shadings of colour to denote the parse tree, so you can easily tell what the NPs and VPs are. (Another one, even more appalling, also from Language Log, which would definitely benefit: "Madonna Addicted to Sweat Dance Plugs Toronto Condos: Mortgages". I defy anyone to parse *that* without a parse tree pre-laid-out for them.)

Or so I guess based on, uh, no research at all other than reading Language Log :)


Copyright © 2015, Eklektix, Inc.
This article may be redistributed under the terms of the Creative Commons CC BY-SA 4.0 license
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds