Lower Literacy: It’s Not the User, It’s the Product! | Accessibility NYC Meetup Recap

On June 4, 2019, Accessibility New York City hosted a Meetup entitled “Lower Literacy: It’s Not the User, It’s the Product!” Presenter Damien Senger, Design Systems & Accessibility Lead in the healthcare industry for Castor EDC in Amsterdam, described the complexity of reading for the human brain. They shared small improvements and tips every designer, content-writer and developer can use in a project to increase literacy for all users.

Here are five areas of focus for enhanced readability from the presentation:

Transcript: A11yNYC - June 4 2019 - Lower Literacy: It’s Not the User, It’s the Product! - Damien Senger

Good evening, everybody. So glad to welcome you all tonight to tonight's accessibility NYC Meetup. I'm Stacy Smith. I'm one of the coorganizers of the meetup and I also work at Equal Entry. I'm pleased to welcome you tonight and present Damian Simmer who is going to give us a great presentation tonight.

Before we get started, a couple of housekeeping announcement type things. We live caption these meetups. So we use CART, communication access relative translation. And we're very grateful to have our partners with us from White Coat Captioning and Diane Scott is doing the live captioning. Big thank you to Diane.

And also, we'll be live streaming this. And as we do for all of our meetups, you can check our YouTube page for past examples of our meetups. We're grateful for Joly Mcfie doing the live stream producing. And our sponsors thotbot, Equal Entry and Level Access. I'll hand it over. And let's get started.

Thanks. [ Applause ]

Thank you. So I hope that this goes correctly. It was a challenge to make it work. So let's see. Lower literacy, it's not the user, it's the product.

Now, yes. So if I'm asking you to think about what would be the perfect reading experience for you, most of the time, like when I'm with my friends I'm getting the same kind of answer. I'm sorry for the, I'm getting the same kind of answer. You can think of the kind of experience being on your couch, just with a book, in your home place.

Some other people prefer to be in a park, completely disconnected from everything else in your life. You can also prefer to go to a nice and warm coffee shop to get a warm cup of tea, for example, and to read with a light atmosphere and the light music. If you ask me what is my perfect reading experience, it's something like this. It's a crowded train when I'm going back from work with a lot of people around me reading other books, or a newspaper, being on the phone, having a discussion, something loud.

Something just switching off my mind. But there is one common thing with all of the experiences, they are about books. And lots of the time when we're reading, in fact, it's on our screens. So let's see how you can read on screens.

And by the way, hi, I'm Damien. I'm a digital designer, specializing in accessibility. I work next to Amsterdam in Netherlands, and I work if Castor EDC, doing medical and health studies where I'm doing design system and accessibility. And I use data products.

So in general, I try to never speak with people. It's kind of a small break today, feel free to ask me questions. And all of the slides of the talk will be available online. If you're interested in following up, or whatever, it's already on speaking.raccoon.studio.

Let's talk about readability. Reading is everything except an easy thing. It's something we're doing our age, like most of us learn how to read, speak English in primary school or in high school or whatever. But it's something we're doing for a lot of time.

In fact, even if it's something we can see as quite easy because it's almost all of the time our brain cannot stop reading stuff on the phone, advertisements everywhere. It's not easy. It's involving a lot of processes in your brain. And one of the issues of this is the fact that the web is mainly textbased. Mainly based on reading. And a text is not accessible per se. Everything we're doing to make it accessible, the text can be a barrier because essential language or if you struggle to read the text.

And to be really quick on this, there are two big kinds of impairments. Group of impairments that we can talk about. The first one is, obviously, the visual impairments. These are the ones I will not talk about today. Going from visual distraction to blindness.

But the one I will focus more about are the cognitive impairments. I like to use the Microsoft, the design framework. And going from, like, the primary impairments to the more situational one. Like, example of permanent, dyslexia, autism and ADHD, the ones we're focusing on today.

But it can be an issue when you try to read a text because you're not maybe used to all of the vocabulary in a specific text or just stressful content. I will talk a lot about airports. Airports are definitely the kind of stressful context, where if you don't have literacy issue, you can be in a context where it's difficult to find information, to read information or just to, like, find where is the gate for your plane.

So a quick focus on dyslexia. And lower literacy. Why? Because in 2013, one of the statistics made by the Department of Education, 43% of the US population has a degree of lowliteracy.

It doesn't mean they can't read, but people can experience difficulty reading and looking and finding information in a text. It can be, like, a lot of different experiences. Basically, almost half of the population. And not all of the population is online. From the Nielsen group, a statistic something like onethird of web users are having a degree of low literacy.

And if you take one specific part of this, which is dyslexia, it's more or less 10% of the global population of, like, a degree of dyslexia. So like a lot of cognitive impairment, it's a spectrum. Going from having some issues recognizing some words to really struggling to analyze a text. It's more or less 10%.

It's kind of the same in all of the western countries, except for the Nordics in Europe, like Sweden, Norway, Denmark, it's almost 15% to 17% and mainly due to the way the languages are built. And like a lot of cognitive disabilities or impairment, it's always coming in groups. So a lot of times, it's associated with ADHD, autism, dyscalculia. It's really something going in groups. And, yeah. That's quite enough. And also, I was saying most of us are reading, for example, English, travel, not always coming from childhood.

It can also appear, this kind of reading impairment after stroke, after traumatic brain injuries, these kind of cognitive issues you can have during your life. And because we are all going to grow old, we may all experience this. So yeah. This was about statistical dyslexia. But one of the things I would love people to understand is the fact that dyslexia is not only about reading. It's a struggle with associating sounds with meaning. But it's not only an issue for people when they start to read text.

For example, there is, like, a lot of interesting different way to challenge like to solve the challenges for people with dyslexia. If you're asking dyslexic people, like me, to answer a problem or to find information on the websites, we can see that the, for example, the trackings or the journalism on websites are completely different from regular users that we can have on our websites. It's not only about reading, it's more about finding information. And because on the web we're not reading, like, (inaudible), trying to find a different way to access information.

And why I'm interested about dyslexia is because if you, like every time in accessibility, if you manage to find a good experience for people having permanent disabilities or impairments, you can experience for everybody. So now, how do we read? And the first thing about how do we read, for me, is the fact that reading is not about letters. It's about sounds. Reading is a music. And it's the case when you're reading out loud. But it's also the case when you're just reading a book.

When you're reading a book or reading on the screen, you're hearing what is the text that you're currently reading. Reading is about sound. And dyslexia is a phonological issue. It's a struggle between the association of sound and meaning. Reading is mainly is a phonological process.

And that's one of the reasons why the reading experience changed a lot depending on the context. And it depends on what you prefer. But because you need to hear your voice and focus on your voice or on the voice that you're projecting on the specific text, this can be altered by the context. And it's not always about your voice. And that way, the context can be important. It's also about what kind of emotion you want to project in the text. And if you start to look at an advertisement and, like, thinking about the voice of one of your favorite actors, the kind of emotion you will get from the text will become completely different from just your voice.

So this is the kind of element to understand about reading. And reading is everything except linear. It's mainly because our eyes are, like, kind of a ball with six different muscles. And the way we need to move the eyes to read the line is doing small rotations. And because of that, we're reading with something called ssaccades. Moving from one position to the other in the sentence.

And during, like, this we are starting at a specific group of letters. And this is called a fixation. Fixation is something really quick. It's like less than a third of a second. Really, really quick. But it's really important for the reading experience. Because, basically, it's where the reading is happening.

During a fixation, the idea is that we are jumping in a group of letters and everything else is becoming blurry. And we will mainly see what is a group of letter. But just shape around the group of letters. And every few fixations, we need a small break. All of this is taking a lot of energy for our brain. It's like a lot of different movement for our muscle. So we need a small break.

And this break always happens in white space in a page or white space in a screen. So saccades, fixations and breaks. And in the reading experience, what is really important is the size of the saccades and the duration of the fixation. And when we try to do eye tracking, for example, and to see what is the most readable experience, the idea is to check the, like, the duration of a fixation.

The shorter the fixation is, the better the experience is. If you don't leave a lot of time to understand what is the group of letter, what is the sound and what's the meaning of everything around, you can easily go to something else. So duration of fixation and size of saccades, and on websites, the idea, we're not reading sentences, we're looking for information. And we can see that in tracking. We're using something called the exploratory reading pattern. And we're going from specific part of the text to other parts. We will see that.

This is one really important part of the reading experience. When your users are lower literacy, you cannot jump from one part of the text to another one because to do that and to jump from group of words to other group of words, we need to understand what's the meaning of the text? But you also need to understand your expectation about it. And like when your users have lower literacy, the idea is we'll never see an exploratory reading pattern. We'll see more something, like, in a book. Reading a full sentence.

And rereading, again, to find the meaning of the sentence. And so, two different reading behaviors. One which will be scanning and the other, which will be plowing, I don't know if I can say that this way. The idea is that when you're scrapping for the information, you're also, all your view is narrow to really detect that you're trying to, like, to read and understand.

Which is, having some kind of issues for users to find information which are not part of the text. So navigation, information in a site's block and all of this kind of thing. If you take a paragraph, like this one, which is the introduction of the WCAG, which I hope people know by heart. The idea is you have first eye tracking with the exploratory pattern. People going from one part of the paragraph to the other part and trying to understand what is the shape and what is the information within the paragraph.

And once you have a good idea of what other kind of information in the paragraph, people will focus on what is interesting for them. Like the cooperation, goal of providing, everything around the goal work, for example, because trying to understand what is this text about. Then, you need a break because this is a lot of energy for our brain. And then, before coming back, looking for other information, seeing if you're finding what you're looking for before going to the next paragraph.

So online tracking, this is the pattern we're seeing most of the time on the internet. Because first analyzing and then reading only what's interesting for us. So basically, we are not reading on the wordbyword manner. And that's the reason why you can definitely read this quite easily despite the misspelling because, basically, you don't have to read every word.

And this is due to the letters and identifying features. The identify features are the (speaker off mic) letters. The upper part and the lower parts. And these are the letters, like the creating the shape of the word.

And the shape that we can easily read the second line but not the first one when we remove some part of the content. Most of the time in the western languages, the identifying features on the top level, it's the case for most of the dialect. All of the accents in French are in Swedish. And there's not too much meaning in the lower part of the letter.

On the first line, it can be difficult to see the difference between an "I" and an "R," for example. You don't see what it is if you don't understand the words. And these identifying features are really important. That's what we're trying to analyze to analyze the meaning of the word.

If you take "readability," for example. We have a system where there is, like, a sentence and it's a shape we can easily recognize, there's a shape. If you write upper case, oh, there is not real shape and that's one of the reasons upper case is really hard to read. But for the misspellings we were discussing before, it's using this kind of shape, but not always. If you can recognize as problem, if you have a misspelling it's mainly because of the shape. The shape is almost exactly the same for porbelm, almost like it's a bit bigger for, like, the top part. But it's almost the same. Which is not the case for pbleorm.

As I told you before, reading is about sounds. It's not only the shape that we need to look here. But also, the sound. And we are two syllables for problem. And also, for porbelm.

But three different syllables for pbleorm. This is the kind of issues with dyslexia, for example. For most of the user, it will be quite easy to identify problem as problem because the sounds are almost the same. But because dyslexia is a struggle associating sounds with meaning, the fact that they are different will create a different experience and a different meaning for users with dyslexia.

And it's one of the reasons why, like, when letters are looking a lot the same, like, M/N or B and D, people with dyslexia will struggle to identify clearly what is the meaning of this word. The sound is almost the same in your mouth. In your mouth like the way doing a B and D is almost the same and the letter is writing almost the same. That is one of the reasons why, yeah. Finding meaning for dyslexic people can be harder.

So this is one tracking showing the fixation and the saccade I showed you before. And it's on the article. But what we can see and what is interesting for me on this one is to see the pattern of reading, which is not only the pattern we've seen before in the paragraph, but also, like, how people are reading the text. And it's not working because it's not making notes. But one of the interesting stuff. One second. Oops. Okay. Sorry. I will show you at the end. It's the fact that people are reading the first two paragraph, like the first part of the first paragraph and the first part of the second paragraph. But in the rest of the eye tracking, people are only focusing on both texts and the beginning of each list item.

Because people are looking for information, seeing in the first paragraph, is it really about what I'm looking for? And if it's the case, just trying to find the information. Minimal effort to get access to it. So based on how do we read and the idea of minimal effort to access information, how can we make our experience readable? And for me, the best way to learn how to make, like, an experience readable, it's to look at airport signs.

I love airports. I definitely love these kind of places because it's a stressful place, one of the only places where my brain can switch off and not, like, bother me anymore. And other times, it's a place where there is something you need to do. Get to your plane or look for someone.

So everything is explained on signs. You don't have to think, just follow. And a lot of effort was put into these kind of signs. Mainly, because you will never know the language of someone in your airport. Especially, for example, in Amsterdam, we have the international airports.

So basically, a transfer airport, you will never know what is the language spoken by someone. Airport sign, understood by virtually everybody. And if we're taking a closer look to the kind of signs, we can learn a lot. Even without the language you need to find the information. To do that, the only way that they manage to find is using images and signs. So every time there's an important information, you will always have a sign with it, a small image, small icon.

And it will always be the same. So all across the journey. Like, when you walk into the airport, it will always be the same icon. Then, you will find exactly the kind of information you're looking for and quite quickly. If you have your boarding pass, you need to go to C5, for example.

You know that you need to look for Csomething. And that's here. And all of the letters people are looking for are just incredibly big. Whereas, the small size, what is exactly the information related to that.

But there is a good variety of information. And then, a bit after, you can see, like, bigger size. Bigger signs. Why? Because they need to adapt to the environment. They need to adapt to the context. You're not anymore, like, saying it will be in this direction.

It's here, you need to see it's here. So big sign. And all of the information which is not useful is removed. So adapting the information to the context. And if you take a step back, again, you can see that the information is also always the same with the same warning. So it's gates, gates.

You can find this, for example, inside a bathroom. The toilet if it was a toilet in the beginning will stay a toilet and will not become bathroom. There's always a consistency in the wording. If you don't speak the language, you're looking for the shape of it. You're looking for something which is closely with the same letters, even if you don't realize the meaning of it.

So from this kind of view, there is the idea of the four Cs of readability. And the first one is the idea of continuity. So you're repeating the information from the beginning to the end. And like just behind the closed captioning, you would see, like, three different signs, this sign, again. Right?

Between each sign, there's a new door. And there's new people coming from the plane, joining this hallway. And they need to access the information. But also, people, it's an airport are tourists. They need to be reassured. And to do that, it's the same information.

It's the good way you can continue. And repeating information over and over and over, again. And you can do the same with a checkout, for example. When you're repeating the information exactly the same way, it's the same idea. Like, even if people are, like, understanding they need to go this way, it's decreasing the amount of stress by explaining the information the same way to not create confusion.

The second one is the idea of conspicuity. There's a lot of signs on this picture. There is a sign for the train, the plane, for the baggage storage, the toilet, the emergency exit, the information airport, and there's another one on here, which is exactly the same as the train one. A lot of information.

But still, you can easily see what kind of information is what. You can see the yellow is everything related to plane. Even if you don't see what is written on the other sign, you can see it's now tied to the train because it's exactly the same sign as this one. And that's the idea of the conspicuity with the continuity. It's easy to see from afar. And it's the same sign, same text, you can understand it.

Then, the consistency. As I said before, a toilet will stay a toilet. If people are looking for a bar or a restaurant and you're, like, getting the information one restaurant and then bar, they will not know if they're still following the thing. They could ask themselves, did I miss the restaurant and it's another bar I'm going to?

So always the same wording from one to the other. It's not SEO friendly, but userfriendly. And the last one, clarity. Here, they really want you to understand that please don't go to the left. Because you cannot transfer. And to be sure, there's transfer on the right.

But there's also the fact that it's an exit and you cannot transfer. There is transfer which is crossed and red signs, you cannot. It's maybe a bit too much, maybe? But it's clear. And if you don't understand that what is a connecting flight, you can see transfer. You can see the plane on the other side. There's explanation a lot, but to be sure that people, whatever the kind of information they're looking for about the transfer, they will at least understand one.

The icon, the wording or the fact that you need to be careful and ask someone before doing a mistake. That's the idea behind clarity. Just being clear and removing everything else. Speak about the train on the platform after the exits, they don't say something about the buses, don't say something, like, all of the experience you have after the two doors.

Just the fact that now there's a choice to make. And these are just the information you need to do that. The idea of clarity. And for that, I love airports. So thanks for Mijiksenaar who created the signage and created a book on readability. Thanks to that.

Now, the question is, we have principles, how can you apply this to our web content? First, please, open dyslexia is not a solution. It can help some people. It's a good place.

But it's not a solution to people to find information. If the user needs open dyslexia, they will have it on their computer and they will already, like, replace all of the fonts on the browser with this one. So offering a button on the website to say dyslexia version, that's not a solution. And it's not a solution, especially because when it's about cognitive disabilities or literacy, there's no onefitsall solution. Like, basically, always training with this because I like the idea that internet is one medium.

Web design is an amazing product. A lot of different base on the same experience. Same content, remove all of this. If you want an experience which is really readable, the idea is to also offer a different way to access information. It can be offering PDF for some people, for example, because in this case, they can download the information because you can access it.

There is amazing ebook readers for dyslexic people which are removing most of the information that is not useful. Changing the backgrounds and all of this kind of stuff. There is a lot of bloggers that are doing this. The onefitsall is not this one. And just to think about all of the different way you can offer the content to people.

And something is not about creating a new format, PDF or ebook. It's also about the information on the page. How can you offer it differently? Other than text? It can be adding images, it can be adding shots, for example, or providing video or audio.

It's a real cost if you want to be (inaudible). It's just offering a way for people to choose what they're the most comfortable with. And this is quite important. And one of the things with readability is this, the fact that readability is offering all of the different possible ways to get access to the information. Not only through text.

So what? Is it done? No. There's a lot of studies made in Barcelona and really nice university. The first one is a good contrast is really needed.

But not too much contrast. That's one of the things. Black and white is what people prefer. And when you're trying to do eye tracking and ask people to give or render their experience, they'll choose black and white. But if you do eye tracking and see what is the average duration of fixation, we can see that in fact, black text on white is not what is the most, like, restful for the eye.

But sometimes, using, like, shade of grays is most, more readable or at least more restful for people. And especially because black on white on screen can create this kind of blur effect around the letters. You send a lot of light, you activate, like, a lot of small, I don't know the English word for, yeah, like in your eyes.

(Speaker off mic).

Yes. You're sending a lot of lights. Which is, like, asking your brain and your eyes to do a lot of work to get access to information and blurs it. And I think some shade of black.

So it's something coming from the transference. You have different kinds of black in the print world. The full black, which is when we use black ink or the three primary ink together. And the idea of, like, a more grayish black, which is just using black ink.

And it's the same, a bit, for the web. We cannot use a shade of black, we need to use a shade of grays. And the study from the University of Barcelona is showing that most of the time, like, something really close to black. The accessibility code, 111 or this kind of colors can be more restful for the eye. But what is really helpful is not choosing white. Because the idea is still to send less light to our eyes. And for this using beige or this kind of yellowish color, like old paper, for example, is way more readable and people start, like, especially dyslexic people have a better reading experience in this.

And the color, the fonts also has an impact. For a lot of time, serification was great. All of the big books were this kind of fonts. But sansserif is the most readable now. The difference is not a lot. It's just if you want to have the optimal experience for someone, sansserif and monospace fonts are better for dyslexic people. It's easier to detect what is an M from an N, for example.

So please don't do all your website in serif, it's not the best. It's definitely not, at least, the nicer fonts. And all of the studies, helvetica was one of the best one. It's not the shape of the letters, serification is harder to read for the eyes. We're used to having a web with sansserif everywhere. We train our eyes to read these kind of fonts.

It's the most readable font nowadays. But italic is a nightmare for readability. So the idea is more to use, like, colors and bold to show and to really put the focus on specific information. But yeah. So sansserif, Roman and fontsize are imperative.

And this one is a trouble I discuss with my dear designer friends. But the most optimal font size is around 14 points. Which means in pixels, something like 18 pixels. It's somewhere around, if you have two different studies you can access from the slide, the first one was made in 2007, which is kind of old now. But it was suggesting, like, 12 to 14 points. So 16 to 18 and that's where the 16 font size came from. And was used.

But for dyslexic family, the websites heavy in content for the websites, this study is showing, like, the size matters study is showing it's like 18 points. And if you're doing more like 18 points, 18 points, it's 22 pixels. Everything above that is not more readable. It's not degrading the experience. It's not more readable. Let's not make our websites with 22 pixels like that will be a bit complex for the design. But at least, that's one of the reasons why we need to offer a way that you can zoom in your devices.

And that's one of the issue in this. Yes, obviously, we can also in our browser. But there was a study on this. Seeing if people are zooming with this. And unfortunately, many of us are not getting access to information. It's possible that people are not always doing it even when they struggle to read if there's not an easy way to do it on the website.

Our brains don't think about solutions, sometimes, if we're not in front of the solution. So that's why font size, the bigger, the better. And you can see after 18, it's basically the same. But, yeah, it's more complex and especially with a bigger variation.

And the line spacing impact. A really huge impact on visibility. That's one of the things I'm surprised about. But there's several studies now showing that even if we're readable because of more space in the paragraphs, the impact on the energy that you need to spend reading a text is not so big.

So basically, if I can have a quotation from the research related study is the fact that size matters, the spacing doesn't except when it does. It's really important for, hmm. It's really important, first, because we need resting space. It's what we see before with a small break. Saccade fixation, break. You need bright space.

But also, you need to understand what is going together. And for this, you need, like, white space, but not too much to really understand what blocks are going together. And, like, there is now good guidelines on this. The good guideline spacing is 1.4 times, the font size. And then two times the paragraph spacing. So basically, give me two lines.

One for, like, line how it's between a paragraph and the next one. So this was on a really broad level. But also, like, the paragraph itself. And here, it's more complex. Especially, when we're discussing about, like, the size of a line. There's always a big debate between 60 characters per line to 120 depending on the article that you're reading. It's clearly the case. You can go back easily to the next line. You can easily look for information and analyze.

But in all of the studies, when we were not, like, checking exactly what are the fixation duration, but asking just people, how do you feel about the paragraph? Most of the time, people if they have a choice, going for something really wider. Because it's not more readable but it's giving you the impression that there is less content. It's doing less line so you're like, yeah, it's smaller. I will spend less energy to find the information. Even if in the end there's the exact same number of words. It's complex but a good compromise most of the time is around 80 characters per line.

It's not too big so they know where they are in the line, but sometimes, it's not, like, too small so people don't have the impression it's really a lot of information. Another really important thing using bold and colors. If you want to be highly readable, you cannot choose, it's changing too much of the words. The difference between most of the time between fronts. The case was A, for example, it's completely different design for the letters. So that's one of the reasons why italic should be avoided. It's a really good way to get someone, like to show to someone this information is really important.

And italic also the underlining. If it's underlined, people will see it's a link. But also, because when you have underlines too close from the letters, you can just impact the shape of the words. And sometimes, with some spaces, it can be hard to see in letters if it's a G or P, next to another one. Like, the end of the loop will be directly on the line so you can just see the fact that there is two bars going at the bottom. It's not always highly readable. There's a way to avoid it which is what Chrome is doing, which is having stop, like, just stop the letter. To stop the line just before and just after the letter.

So you'll always have some white space in between, which is really good for, in this case, readability because you can see the words. But which can be quite hard for some users. Most of the time, it is easy or is it the same? Because there's a break in the line.

Quite interesting to see how you can solve that. But most of the time, if it's a link, try to underline. And I said before, no upper case, or small caps, it's exactly the same issue. You have a big one and then a block of letters. Really hard to identify what exactly is the word.

And my favorite one, please, please, please never disallow highlighting text. It's really important. Firstly, lower literacy is sometimes about lack of fluency. So you need to get access to the text and be able to copy/paste into a translate system. Some users are using the highlighting system just to follow the text to understand where you are in a text.

What is exactly your position? What did you read or not? So highlighting is not just to copy/paste a text, it's also to keep track of the information. And basically, it's a default behavior. Don't change default behavior. And content avoiding generic content. It's also important for readability not only for screen readers.

Because on the link, if you just read more, like a link will be this color and then the line. It's definitely what a link is. So if the only thing you're seeing on the page is going back is going from bold text to, like, the link because it's shiny, with color and on the line. One of the things with lower literacy, is you're afraid what you're seeing on the screen is lower for your brain so you get lower access to the information. So even finding the title can be more challenging. So link with content, meaningful content.

On the more layout level. The text alignment is really, really, really important. And because our language is most of the time left to right, aligning on the left. It's the only way for someone to see where I should go when the line is done.

So going on the next line on the left, on the left because that's what a paragraph is. And that's one of the reasons why we should avoid having centered text except for title. You will never know for sure when the line began. And the justification is the same with the right edge.

Like, if you look at someone else for a second, the main, like, one of the main, the way to get access to information, again, is to know where were you on the paragraph? So to see the shape of the paragraph and knowing you are somewhere around this place. But if it's justified, you don't know. It's just a huge block of text. And when there's reverse, it's even worse. Because, you really don't know where you were or where the sentence ends.

So justification is a pain. Always. Except on prints because you can manage it. But on the web, it's a pain.

It's a bit the same with multicolumns. It's quite amazing, it's well supported. But it's complicated. On design, multicolumn is used to really narrow text. But narrow can be more complex, especially if it's only 20 to 25 character a line.

But also, it's confusing. If you don't have a lot of content, you will have, for example, five lines and then five lines on the other side. Like, it's not understandable that things are going together. Our brain is trained to see content as groups. One group, out of the group. You see two columns, thinking about two different contents. That's one of the reasons why multicolumn, sometimes, newspapers, can be really hard to understand for someone which is not having all the culture.

And related to that, group the small related content together with a strong visual system. If you're doing columns, it's not for the same text, it's for different thoughts, different type of information grouped together. And really important, like, heading and information hierarchy. And what we can see from the tracking from before, the interesting stuff from before, people were mainly reading the two first lines of each paragraph. And it's the same for title.

Because the only thing you can be sure about is that people will read the first word of a title and then, they will do a saccade. You will not know if it's at the end of the line or the next word. They will read the first word. And this is where you should have the information. So in the first paragraph so people can find it. But also, starting the heading with really the most word carrying most of the information.

And because people are mainly analyzing pages, the idea is to break up the content with a lot of headings. Because that's the best way for people to get access to what is the meaning of the different paragraphs? If you see a title with something interesting for you, you read the paragraph. If you see one title and then seven or eight different paragraphs, most of the time you will not know what to expect from this text.

Really important for readability. And because you cannot be, you cannot detect what will be the title in the page. You need outline, like you just at the beginning, that's what Wikipedia is doing, for example, to offer the best reading experience. They're offering an outline. Because the idea is to say, this is the information that you will find if you want something specific, you can just go there and get it.

And for that, one of the ideas is just to use HTML and design accordingly. People have expectations. For example, lists are amazing for readability. But in this case, please use a list. Meaning having a sign, bullet point or number, and also, using it in HTML.

Because most of the people, and especially, like, dyslexic people are using screen readers to get access to the information. So in this case, they need to understand what is, like, the contents. And what's the shape of the content? And how to easily navigate to it. So use HTML and design accordingly to match the expectation. They can have this and see the page at the same time. And this is where when you use it, you need to design accordingly.

And really important, especially, also with cognitive disabilities like autism, it's to keep consistent layouts. Because you will never know, like, how people will find information. Once they found a way to get access to information, they will expect between different pages to get access to the same kind of information at the same place, consistency. And that's why, like, a lot of blogs in the early ages of internet, using this kind of twocolumn system, there is one showing the most readable pattern on the web pages is having twoword, oneword layouts. The main information and the main information and content.

And oneford, people can just focus and narrow all of their energy in the main content. Most important content in a single main column. And related to that because you will never know how people will find information. The idea is also to simplify the navigation as possible. Big menus are okay when you know what you're looking for. But when you don't know exactly how a website is, like, created and what is exactly the information architecture, you need help. And most of these will not open a menu to see the help. They just want help. And that's why, like, having linear menus with at least the main choices is important also for readability.

People will see this. It's big, it's on the top. You will see what is the website about. It's also readability.

And because most of the time, you're never sure people will get access to the information in the way that you're thinking. This is not the only way to access information. The best thing is to provide a second way. A second, different way to access the information. On the run page, for example, it's having at the top, like, navigation. And then, if you stop reading because people just don't always know what they're looking for, having another way to get access, sometimes, to the same links.

Just because it's not the same context. First, people, someone who wanted to know about it can go directly to it. If they don't know what they're looking for, it's easy to give open text and trigger some interest and then to say, again, by the way, there is a way to access small information over there. But not by seeing "read more," please.

And one of the last things is adopting an inclusive writing style. And inclusive in a lot of ways, in this way, it's stated that to be easily understandable by people, you need to change, sometimes, the way you're writing text. One of the first things is, one of the most readable thing is using active voice. First, one of the most easier to translate for automatic translation tool. People, whatever they level in the language can get access to it.

But for everybody, it's the easiest way to understand a sentence. The active voice. And especially, if you're using short and simple sentence, easily translatable. If it's easily translatable, it's understood by everybody. So active voice short and simple. If you can use images, graphics or rich media, it's even better, you can offer a lot of different ways to access the same information.

More, the merrier on this one. And a list is always clearer than the paragraph. Most of the time, when you have, like, a lot of information, there is, which is if you have more than foror five information in the paragraph, go for a list. It will be easily scannable for people so they can get access to the main element of the information. And if they want to know more, you can add the more paragraph afterwards.

A good way, title, starting with the list of information, and then, giving more information after in paragraphs. And I know that, at least, like in France, we love our abbreviations for everything. But that's a nightmare. Because it's highly cultural. So if you don't have access to, like, the culture, the knowledge of the culture you're living in, for example. Or if you just are not technical enough about trying to get information, it's not understandable.

Abbreviation, domainspecific jargon and my nightmare in English double negatives. Like, I don't know who invented that. But that's a nightmare. Like, most of the time you need to reread like several times to get access to it.

First, because, like, dyslexia is not the best way to read a sentence, so you need to rethink. Was it a double negative? Are you sure? So, people, double negative, never.

Never, never, never, ever. These are, the readability improvement in text. There's always experiences next to text. And try to avoid that. And obviously, yes, it's working. It's a French website.

Just by the language, it's almost impossible to get access to information. Everything is moving. Like, my brain is going in all direction. There is taxis, signs, everything, except the phone. There is a phone. And it's not a good experience.

Especially, if you have users with ADHD, it's going in all direction. It's opening a lot of doors. Please, try to be careful with distractions. And this is maybe, like, obvious, but sometimes it's about this. Like, I'm trying to look for my next, two years ago, but I tried to look for my next weekend. And I had, like, this really nice person here. Like over there. Trying to, no, thank you, you're nice, but no thank you. I just want to focus on what is my next experience.

So just try to be careful with this. And it's not on the list. Also, like, it can be an open door for a lot of people to exit your website because, oh, this person is saying something and it's making me think about something else, so I'm going to find information. And coming back, or not. But trying to avoid this kind of stuff. And also, in my case because, remember, in general, I try never to speak with people.

Even people in videos. One of the other way to do distractionfree experience is it's to avoid, like, this kind of thing. There is a text. There is a video, but this one is not too visible, it's quite nice. It's moving automatically to something else without asking me to go to the next slide.

And that's one of the things. There's not a lot of text. So you could say that, people have time to read but you never know. If someone needs to translate and to copy/paste and to go somewhere else, coming back on your website, hmm, where's the content I was looking for?

So you can never do assumption on the time needed by someone to get access and to understand the content. And this is something we need to be really careful about. The web is full of timed experience. And my favorite one and I'm really sorry if there's content people. The scissors. Cut the unnecessary content. Remove half of your content.

You can always remove half of your content. And even when you remove half of your content, you can remove, again, half of it. There's always too much content. Way too much content.

So if you want to provide something clearly readable, just cut. That's something a lot of websites start to do now with services, for example. It's like offering one of the versions, which is half or less of the content just saying, this is what you will get access to, this is what you engage yourself to. So this is the same for all of your contents. I discussed with, like, a Dutch municipality a few days ago in the conference and that was one of the challenges. They were, like, I cannot cut my content. Everything is important for people. Yes, you can. You can always offer an abstract at the beginning, basically, you want to renew your passport, this is in most of the case what you need. This, this, this and this.

And then, offering all of the content after. You can always find a way to provide two different experiences depending on timing of people or the level of literacy. You want to go to the airport, go to the airline, get the number of baggage you can check in. You're in front of the checkin counter and you're not sure anymore, you need to get access just to this information and not to all of the explanations.

Always find a way to remove a lot of content. So to finish on this, you can easily experiment with mouse heatmap. It's not the best, but most of the time people are using the mouse to follow what they're reading. It's a good indication on where is activity on your page by tracking.

Tracking is complex. But check out this kind of thing. It's from the first work I've made. You are looking on how people get access. What people are looking for stock moment.

Offering information about when the product will be back in stock and wanting to know what are people interested by. You can see the activity. At the end of the page, they were, like, a lot of activity. And when you see that, it's the moment where you can think about the readability of your page and what you can do.

And what you can do is not always taking this paragraph and putting it at the top. One of the risks is that people will not continue to get access to other information because they got the information. What you can do is taking the information with people especially looking for. Here, it was popular and seeing at the top, like, in the introduction paragraph that you can find this product, but you can also learn why you need to wait and have all of the information after, why you need to wait on this website before getting it.

And just finding a way to get people to stay on the page by what will be the content. You can get your answer but also can know more about it. This kind of solution can be a way to not remove the content. The second way to experiment is to use a screen reader. Like, especially on Mac.

The idea that you can have a list of all of the landmark and all of the data. You can do the list of headings. And I know there's an H6. All of the links. And you can see this information without the context. You can easily spot if there's a read more somewhere or if there's something which is important but not understandable without the context. And in this case, you can use ARIA label, all of this stuff to provide the information for the screen reader if you want to narrow this to the screen reader.

Or you can just, like, go back to this, think about it and find another way to provide this information in a better way. Using the web portal, for example, it's really amazing. You can do the same with Nvidia, just use it. Yeah, I wasn't sure. And the last one is something which is working really great in English, really badly in a lot of other languages but it's calculate readability scores.

Basically, readability, readability scores, a lot of websites are doing it. But basically, there's a lot of different news. The most known is the (inaudible). And the idea is most of the reading skills are trying to match the text you're writing with an age needed.

I tried a technical one and the idea that it was difficult to read. Because basically, you need to be in college or 12th grade or 18, 19 years old to understand what is the context and what is the text about. And it's not about the vocabulary you're using because, like, there is no dictionary use for that. It's only based on the idea that the language is phonological. It's only based on the idea of seeing the average size of words, the average number of syllables and the average number of sentences and the average number of sentences per paragraph. It's not always precise, but it's a good information to get about your text.

And most of the time, if you're like, using active voice, using, like, smart and consistent sentences, you'll have something highly readable. It's a good try to run your website like this and not always having the most readable one. But just to see where people can struggle and identify what are the content you can work on. And to finish, I have some good example for you. The first one is, sorry for the contrast.

The green is terrible. But everything else is great. The green is terrible. Websites they made. So it's the idea that the fact that they have illustrations with animation, but the animation was never longer than one second and it was done.

The text is mainly lists with huge title with almost no upper case. If you're really, like, don't think about the green, which is terrible. It's highly readable. So that's one of the good things you can do, which is stylish. It's nice to see, but at the same time, it's readable. There's a lot of work in this and you can find the information.

Smashing Magazine, which I love more than anything else on the web is also having something quite readable. I'm really sorry for the quality of the (inaudible). And something highly readable, but for that they're using bold and colors. They're using "read more," we had this discussion, it would be better. But that's nice, that's using bold, that's using huge title, a lot of white space and still, like, having a personality.

You can do design which is readable and nice at the same time. And even with a lot of colors, yeah, we cannot see here. But there's a lot of tags going together because having the same style. They manage to create an experience which is highly readable. Offscreen, which is coming back this summer, is doing the same with blocks of colors. When you scroll, see where is the information, what is going together, it's quite interesting to see this kind of big blocks of colors using, also, like illustration when there is too much white space but also providing information about lists. It's information on the shop.

And a lot of small information going together, we cannot see to here. If there's a gray background and then white specific blocks. And the idea is also to create this idea of content going together because the same purpose. And the last one terrible is an eCommerce website. It's quite nice you can also do something highly readable. It's a long page, you will see. Even with a really low quality, you can see that, no, you cannot.

There's a huge title, small paragraph, a lot of images related directly to the product. Like, they played a lot, I haven't screen these big pixels for years. They played a lot with, like, huge title, giving you exactly the information that you're looking at and if you really want to know more, there's one or two lines. And you will see it's really, really, really, really low page. Here with the list, for example.

And yeah. I realize it's using significant memory. But, like, it's really long, long, long, long page. Starting with a lot of pictures and they're using upper case but still highly readable. It's on title with one, two, or three words.

When you have a lot of information and you want to sell your product and there is a lot of things you want to say, you can still do something highly readable. And you cannot see it's written "ready for adventure" are you ready for the adventure of readability now? Merci beaucoup. Thank you.

[ Applause ]

I think we have some time for Q & A right now. If you have any questions just wave and I'll give you the microphone and we can have some questions.

It was not readable as a presentation.

Hello. I'm just curious what you would say is the biggest blocker that you see on websites now in terms of preventing readability. Is there, like, a common theme is happening everywhere?

Yes. It's not about the text itself for me, it's really about the layouts and the fact it's more and more, especially on eCommerce, breaking the layout and doing experiences with text running everywhere. We're back from, what was the name of this? When the scroll was going the same speed. So this is an amazing thing and I don't care about that. But the basically the layouts. Breaking more and more of the layouts. You can do amazing stuff with grids. It's amazing. It's bringing back creativity to the web. We need to be careful by adding a layout, which is readable. When people, like, when you see all of the books the trends in the print industry, you can see at one point the star was going in the directions, and the layout going out to the page.

We are, like, prints capabilities now we can do, like, different format of paper into the same book and having 4D on this stuff. People were creating crazy stuff but not having the readability. And on the web, we're doing the same, like, breaking the layouts, breaking the information to small pieces, going in a lot of different page place of the pages. And this is not an easy way to find information for people. So being creative but still thinking about the fact that people mainly want to look for information.

How do you resolve other accessibility challenges? Like, you know, there's a recommendation that you underline all links for readability but you said that can make readability difficult for dyslexia and also using color to provide contrast instead of italics or other style when people have color blindness, those kind of things.

Accessibility's complicated. That's always a thing. But most of the time one of the issue is, like, there's no onefitsall solution. And one of the way for me now and where the web should go is being entirely under the customization and offering a nice way to go in the direction now.

And this is, for me, the way that you can easily, like, solve for a lot of different impairments on accessibility issues. It was complicated. We have guidelines in WCAG, we need to be careful providing the, not careful, but the guidelines are making complex the idea of having rich medias. Because there is a lot of challenges with rich media. But at the same time, the best way to make content readable is to not use text, but to use rich media.

There is no good answer from me on, on how to make a choice between guidelines. But that's also, like, one of the reasons why in the WCAG, for example, there is really few guidelines regarding cognitive impairments. There is a bit more now with the 2.1, they added some interesting ones. But there is always a struggle, the fact that even between disabilities, cognitive disabilities and impairments, it's complicated. Because, like, you want to hire contrast if you want to be WCAG compliant.

But at the same time for autism and dyslexia, you need to be careful with contrast. It can be hurtful. It can hurt the experience of autistic users, for example, but that's really where for the answer is customization. We need to offer customization. And the only way to have everybody having the best experience is to listen what are the settings into the different systems.

For example, I was showing a lot about videos and this kind of stuff and animations. For example, you have a cut with a lot of animations. You can use the media query in CSS, prefer reduced motion. And this is the kind of stuff now we need to push more for, also, as an accessibility community to explain to, like, now the working group and the WBC because they're working together. We need more of this, the custom queries. It's amazing there's CSS custom properties, but we need also help on this.

If each website is using its own variable system, we can miss something, which is having a standout in the industry of what should be the variables. In this case, if there's a standout industry for variables, people could just have, like, override of styles and variables in the browsers. If, like, Windows is having the same reduced motion via query as map, we can easily offer a way for people not to have access to the information triggering a disorder.

The same, and like, I'm saying that Windows is also doing amazing stuff with the inverted color system and all of these kind of night mode is kind of the same idea. It's providing ways for people to customize. And in this case, the way we're building our websites, we need to listen all the settings through CSS and adapt our experience. And adopt around this.

Hi. So you advocate enabling customization. Would you say we should have a plus button, minus button to control font size? A night mode, day mode to control contrast? And then, low accessibility button that would be like five buttons on your website before you've done anything.

That's complicated. Yeah. Like, my favorite answer to every question is it's complicated. But it's complicated because a lot of people don't know that they can increase and decrease the font size in the browser. So this button is legitimate. But at the same time, changing color is also legitimate. So yes, but I would say, no, for me, the best way would be to have my dream, I will say this way. I would love for people when they get on the computer to have how to use the browser.

The fact that you can change the font size here, you can override something here. And I think, for example, for overriding, overriding is really complex in browsers nowadays. You need to know css to override some information or to use planes. This should be and would be part of the process. When you start Your Fire Fox, please use FireFox. In FireFox, for example, it could be great when you install this browser, you have first interaction with it, which is what would you prefer?

Like, do you really want the white screen when there is a white background, do you prefer having yellow, for example? Because it's better for readability. What is the base font size on your websites? Is it really 16 pixel? We will all age. I'm not the only one with glasses tonight. And I'm really wishing you will not need glasses for all of the other people after.

But we will age and we will also need, like, bigger font sizes. Offering a way right at the beginning to customize would be a way. And having all of these multiple button and accessibility Widgets. Helpful because there is no other way to improve, like, the experience.

It's not only the browser to fix that, it's also back on CSS, people to do this also on the CSI, on the queries to what are the different settings and to do CSS in the way it's not blocking people to override with specific custom styles. I would say, yeah, it's a great solution now, but it shouldn't be a browserspecific setting and not... Plugins. Sorry, I'm always doing long answers.

Hi. Thank you so much for all of the information you're sharing. It's very, very helpful and insightful. I read recently that you were certified in web accessibility and wanted to ask if you could share what that process was like.

Um, like there is, there is, no we cannot call it, there's an organization of international accessibility professionals. The IAAP. And basically, you can, I think, twice a year or three times a year, something like this. You can join, like, certification session.

And there is 75 questions. Mainly tech. There is kind of sophistication. I've passed the tech one. It's really techie. It's really about WCAG, like, all the technical implementation for all of these kind of things. It's really, really technical. It was a bit complicated. I learned stuff, I must say, doing this certification, a few questions I was like, okay, okay, why not?

But so it's really technical one based on the code. It's just that it's required by some companies, especially if you want to work on full accessible positions. And that's definitely where I'm trying to go with my current carrier. It can be useful, but outside of that, yeah. If you think you need it for your cover, it's nice, do it. But if you want to actually just know more about the accessibility, I never know how to pronounce it in English but DCAC, doing accessibility training, accessibility workshop in the university is providing a lot of content and basically, if you don't want to pay for the certification, you can access all of the information and selftrain yourself.

I will not say it's, it's just great because someone saying, like, basically you know about things. So that was great for me and that solved one of my personal issues. But because it's still a cost and I'm really glad my company paid for it. I would just say if it's about knowing what your knowledge is and just being, like, more comfortable with your skills, it's amazing.

If it's about getting the skills, WCAG University. It's absolutely amazing. And they have a sponsorship system. So if you have any kind of disability, you can access it for free because the idea is that people should be empowered with their impairments and to also to use that in their professional career if they want to. Yep. I definitely need to do, like, smaller answers.

Any other questions?

Could you spell the name of that university?

Yeah. Yep. Yep. Yep. Sorry for the. Okay. Deque University. Yeah. There's online courses.

And, yeah. If you have any kind of disability, dyslexia is part of the list. You can access it for free. It's amazing. Yep. Sorry.

Actually, I just want to add, Deque is also the engine that runs lightning for Google accessibility and also Microsoft Accessibility.

Yeah. They're doing tremendous work. The plugin is absolutely amazing. And you can use it in all of the technical stack. There's plugin for directly in the browser, like, the tool made by Microsoft that you run engine is absolutely tremendous. It's, like, one of the best plugin you can find. Not only it's doing, like, the automatic checks, but it's also offering you a way to do the full accessibility audits by yourself.

So it's explaining what you need to test and how to test it. So yeah. Not only the university, they're doing a tremendous job.

Thank you, so much, Damien, I really appreciate this presentation. And we have some time for some networking and mingling afterwards after we finish up the stream. If you have any other questions or want to speak oneonone or get to know some of the folks in the room, please stick around. One quick announcement, we actually have two meetups in June. So we have one scheduled for June 13th, Data Visualization, tips for making graphic content accessible to all.

So I hope you all will be there. And keep in touch with us through our Meetup web page. If you're not members, I hope you'll consider joining and all of the information for future events are on that page. Hope you'll join me and Damien, again, for a presentation and we'll see you next time.

[ Applause ]