 I think we're still going to have people joining in quite early. We're going to talk about designing digital experiences for inclusion. Over the last couple of days, we've been talking a lot about amazing digital experiences that we can build in Drupal. What we're going to talk today about why is it important to bring inclusivity into your digital experiences, and the benefits, and how exactly can you start doing that. So quick look at the agenda for today. You're going to do some introductions. This is going to be a very interactive session, so just heads up on that. We're going to look at what is an inclusive digital experience. What do we mean when we say digital? What is it that characterizes a inclusive digital experience? We're going to also look at some of the pillars of inclusive design. So if you were to bring inclusivity into your digital experience that you're building in your applications, what is it that you need to, how is it that you can do that? We're going to look very briefly also at what is a situational versus a permanent exclusion, and then also a very, very frequently asked discussed topic about, do I do inclusion or do I design for accessibility? So we're going to look at what are really the differences between the two. Then we're going to wrap up the session with some of our learnings when we designed an inclusive digital experience using Drupal for one of our clients. Quick introduction on myself. I'm Arunama. I'm a senior product manager with Shreejan Technologies. I like to call myself a product solutionist because product manager has a certain image attached to it. I'm also a storyteller and a published author of fiction. So I love writing and telling stories and we're going to bring that element into our session today as well. Three things that I'm passionate about, I'm passionate about storytelling, I'm passionate about product design and sustainability. Some of you might have heard the session I was in yesterday on sustainability as well, and also learning for all. When we say learning, we talk about e-learning, digital learning, and I like to say that doing that for everyone for again, talking about inclusion there. So that's me and those are my handles in case you want to reach out to me later on. So yeah, disclaimer, there will be some interaction, find a neighbor, make sure you're sitting with a neighbor because there will be some interaction in this session with your neighbors and it's a small group. So I don't know how much walking around we're going to do because we're all sitting pretty close by, but there might be some moving around. Why am I talking of inclusion? Why did I pick this topic here today? So like I said, one of my alter egos is that of a storyteller. As a storyteller in the offline world, we interact with a very diverse range of people, very diverse audiences when we tell stories. I have some pictures here from some of my fellow storytellers, and you can see their names in the credits. This is Ratuparna doing a session, post a session with students of a deaf school. Now just think, students of a deaf school and she did a storytelling session with them. She doesn't know the sign language, but she did it. This is Shalini, she's doing a session with kids from a rural area, a school in a rural area in India. And then there is, again, I think that's Ritu again, doing a session with autistic kids in Nagaland. It's one of the states in India. And then we have again, I think this is Shalini doing another session as part of the Pratham. So there's an enterprise, it's called Pratham Books in India, and they go to all kinds of remote corners of country doing storytelling sessions. Why am I talking of this? One of the things that we notice is when we are sitting in an offline space, we're very much inclusive. And we interact, even this DrupalCon, we've got like hundreds of people here, right? And they come from all kinds of background. So in the offline world, we're very inclusive. Why is it that when we translate that to the digital world, there is a gap? And what is it that now we need to do to translate this inclusivity that we have in the offline world into the digital world, which is what I'm passionate about and that's why this session. That, by the way, is Indian Barley Art, which we sort of morphed into inclusion. We're going to do a quick ice breaker. I've been talking a lot. So everybody, I think, has a phone or a notebook or something. Let's try and identify. How will you identify yourself? And I'll give you some markers to help you do that. It could be your age, gender, your family status, your occupation. And I want one volunteer to speak up. I'll just give you an example. For instance, I'm a 40-year-old female. Identifying myself with the pronouns she, her, married with a kid, working in the IT industry as a product manager. So that's me. That's my identity. Any volunteer for their identity? No volunteers. OK, cool. I'm a 24-year-old male. I identify as a he-him. I'm just single and I started as a junior front-end developer recently. Awesome. So that's one identity we got here. I'm going to come to you, the gentleman in the next row. Let me add some more markers. Another volunteer. I'm a 23-year-old man. I introduce pronouns he, him. I'm married with an adopted child. My child is born Black African. I work in the IT sector. And I help my wife's business. So I'm an IT worker and entrepreneur in a way. I have a university background. I'm Finnish, so I'm from a small country. And I do a lot of things with dogs and also do with Japanese sports. That's very interesting. So you see that we added another layer to our identities when we spoke of this. And we can go on this way. We could add our abilities into our identity. We could add any addictions. We could add our religion, our political affiliations. And this is a huge list. How you identify yourself is a huge list. It could go on. What have we done here? I know two people have spoken, but I'm hoping the others have thought about their identities as well. And if you do that, what you'll realize is even within the small group, we are a very diverse audience. And when we talk of inclusion and digital experiences, this identity mapping is a very crucial or a key element of designing a digital experience. Really an inclusive design. What is it? It's one that addresses the needs of all individuals from very diverse identities. So we have a gentleman who's Finnish and who has interest in Japanese sports. We've got somebody who is interested, whose interest may be something totally different and may be coming from a very different background. So when we talk about designing here, we're talking about the three key elements that we always keep in mind when we are designing for such a diverse audience. Designing with empathy, that's the most crucial element. Empathy is the most crucial element for any product manager. And this is something that we guys often quote. A product manager is a mix of two things. Empathy and a lot of data. That's like that characterizes and a little bit of intuition, of course. So what do we mean by designing with empathy? So an inclusive digital experience that is designed with empathy understands and empathizes with a diverse range of lived experiences and backgrounds. So go beyond backgrounds, right? Not just where are your users coming from, but what are their lived experiences? What are their needs? What are their frustrations? What are their desires? What are their shortcomings? That's something we do extensively when we are designing any solution in the user research, when we do our user research and when we do our market research, that's something we really dive into very deeply. And why empathy? Because you need to understand that, right? It's one thing, hearing somebody, and we're gonna see very interesting examples in later slides, right? One thing is understanding that, the other is being able to pick up the key nuggets from that, put that into your solution. The second thing when we look at designing here is co-designing with people. What we should be looking at is building digital experiences, not for people, but with them, right? That's like the heart of co-designing. And it's very interesting when you start co-designing your solution with people, there will be so many facets that you will start thinking of, which probably never came to your mind earlier, right? And again, we're gonna see examples of that and we're gonna probably even do some of them, right? The third aspect is designing for diverse needs, right? So if we go back to the activity we did earlier, how people identifying themselves, that is, you know, and what their needs could be, right? That's identifying the diverse needs and being able to design for them, designing the solution that fulfills, you know, their needs. And the more diverse audiences that you look at during your user research, when you're getting into designing your solution, the more richer your experience, the DXP that you design will come out to be. So this sort of, the three stages of the design and build process, right? Inspiration, when you're looking and empathizing with your audiences, the ideation stage where you are basically thinking of brainstorming on what are the needs that these people, you know, that the people you co-designing with will, you know, those needs, how are you gonna fulfill those needs via your application? And the third is obviously the build stage, when you're creating the solution. And unlike, you know, popular opinion, inclusion does not stop at the design process. It goes on into the build process. It goes on into how you're architecting your system. It goes on into what are the non-functional requirements you're gonna look at, right? That is a very common term which is used for all of this, human-centered design. We've heard about it yesterday also in the session on AnuLMS. And of course, it's a common term. What is human-centered design? It's all of this. It's beyond just designing a graphic experience or a digital experience. It goes into designing of the entire solution for your users. Sorry. So basically, yeah, designing systems around people and not people around systems. Very popular quote by Don Norman. Okay, quick activity. Just making sure nobody's sleeping. Is this inclusive? What is this? Sorry, what is this? I did an exclusion just now. Everybody knows what this is? Anybody who does not know what this is? It's okay, it's a small group. You can say no. Okay, this is the WhatsApp smiley set. Is this inclusive? Yes, no, no. Okay. What about this? Is this? No. Why not? Stereotypes, okay. What about if I say that now, and this is like the very old version, by the way of the WhatsApp smileys. This is the newer version. And what now you do have is being able to select your color tones, being able to select something that represents you, right? So partially inclusive. A step closer. And now what they have is even closer in a way, but they're still getting there. So we can say this is totally exclusive. This is kind of inclusive. And they still need to get closer to being more inclusive. Okay. Moving on to the principles of inclusive design. And this is gonna be quite a bit of theory. So I'm gonna try and make it as interesting as possible. When we talk of inclusive design, there are certain design challenges that we always look at, right? And when I say design challenges, again, not UIUX, the entire solution. We have to, we assume what we call as, when we sit down to design a solution, and I've been hearing sessions throughout yesterday, and quite a few of them did this blunder. You're designed for what we call as the typical audience. Typical audience, you, me, people who know what these systems, how these systems work, they know how to read and write. There are some basic assumptions that we always make. When we start creating an application, creating a system, creating a software for our users, right? But is that true for all audiences? So understanding what is the literacy level of your audience, both text and numerical, they can be different. Exploring what their connectivity challenges are. Understanding which includes like, do they have, do they even have internet availability? What is the kind of speed they're sitting at? When we'll dive deeper into each of these. Understanding what is their digital literacy level, right? Respecting culture, identity and ethics, right? Anticipating auditory, visual, motor and cognitive challenges. Anticipating onboarding challenges and understanding language barriers. We're gonna go deeper into each of these design challenges and see, you know, what they mean and how we can bring them into our system. So we'll start with the first one. This is an actual persona, actual user. We reserve, when we were doing our user research for one of the applications we built. Alia is, she's a 16-year-old girl, living in Iraq. And here are some of her challenges when we spoke to her about our application, right? I'm able to use my mobile a little by following the shapes. I even search for difficult words using the sound search. These are actual statements. I can't read or write, but I know my mother's name by the shape and I know how to call, so I can talk to her. I wish I could find information in Turkman as it's my mother tongue. I can find information in Turkish, but it's not really the same. I want to learn. I feel shy asking others all the time. I do not have any sources. So Iraq, a border of Iraq, actually, and she is what we call a refugee. She's living in a refugee camp, actually. These are her challenges, okay? She does use applications, by the way. She's a big user of Snapchat and TikTok, okay? So it's not that she doesn't use applications, but here are her actual challenges, right? So this is the design challenge that we started with. What are the design tools that we adopted in such a situation? Voice support, Drupal does it in a lovely manner, right? Speech to text and text to speech. Enabled via VoicePorts, voice search. So when she gets into the application, she doesn't really need to write anything. She doesn't even need to be able to read too much there. She can just talk into it. Sounds and vibrations, using familiar signals, such as the ringer sound, the buzzer sound, vibrations as signals. So, okay, here's your search results. Here's what you have a notification, right? Don't just write notification, buzz it, right? Using familiar symbols and illustrations for call-to-actions to clearly indicate the intent. This was very critical for us when we were designing for these people because images and symbols is something they relate to. And again, we'll see how those images and symbols are not the ones that we understand really, right? So these are some of the design tools we employ. Looking at low literacy levels may not always be on your radar, to be very honest, right? It depends on, you know, is your application, where are you designing your application for? So if you're designing your application for, let's say, views in just Czech Republic or just, let's say, North America, you may not want to do this. But question is, are you sure you don't want to do this? Because are you sure you don't have people like Alia sitting in your target geography? The second design challenge, and this is important and interesting because I come from one of the countries in that red box. The internet connection speeds, right? You can see that, this is a graph, this is from, this data is from Jan 2022. And you'll see that out of, you know, I think we have 196 countries, 31 of them are lying here. Rest of the users sitting in those other 164 countries are either struggling to get into your application, access your application to its full utility or probably are not even looking at the beautiful experiences you're building, right? So that's the audience we designed for. But are we looking at the other set of the audience? The one that lies on the other side of the red box, right? This is the second design challenge, which as product designers, as developers, it's critical for us to look at this. And the solution to this will never lie in your UI UX, right? It might, a little bit. But this particular thing is heavily handled by how you develop your application. So some of the design tools that we did here, we offered offline support. We allowed them to download their content, access it anywhere, and once they went online, which used to be, you know, which could be when they get into, let's say, for instance, we in India, when we get back home, we have a high speed internet. So we go back and sync our activities, right? There are people who may not have Wi-Fi at home, so they might go to a community center, or if you're talking of further countries who have very low internet bandwidths. Warnings and errors. This, of course, is something that we handle from a design side. Making sure the user's alerted, right? Oftentimes, you've got like the wheel going, going, going, going, and you're just wondering what's happening, what do I do? And then all the data you saved, it's just gone. The form you filled is gone, right? Making sure that you're capturing, catching that lost internet connectivity in time, throwing the user the right error message. The right warning saying, okay, you know, here, this is what happened in India that does it beautifully. They'll give you a warning saying, you know, you're in a low internet zone, don't do this activity, don't place your order, don't start a bank transaction, right? So that's warning and errors. And again, something that's more deeply technical is more done from, let's say, the development side than from a UI-OX side. The third design challenge, and I don't know I don't know why that icon is floating there, sorry about that, but just look at the image on the left. Low digital literacy is the third design challenge and anybody wants to take a shot at what's wrong with this. This is from a shopping application in India and anybody wants to take a guess at why is this wrong? Yeah, just more to tap, that's interesting. Okay, very good. Anything else? Yeah, okay, close, very good. Anything, any other guesses? Awesome, yes, very good. These are, all three of them are actually very correct points. One, use of icons which are not recognized. Most users, apart from, let's say, the top, you know, the high internet connectivity countries, they'll mostly be sitting on Android phones. So Google provides this entire set of material icons which Android phones use, and internationally, most people recognize those icons. So if you pick up an icon outside of the Material Library or pick up an icon which does not even, that looks like a bag or, I don't know what to me, if I've never accessed an application, I don't know what that icon looks like. Second thing, very valid point, some of these icons, a person who has never used an application will not even know what this icon is. And again, so all valid points. And one more point which I want to add here, what do you feel about the busyness of this page? There's just so much to do. For somebody who's a first time internet user, this experience is overwhelming. I just don't know what do I click? Do I click here? Do I go there? Do I go there? I, as a, you know, if put yourself in the shoes, the empathy part, put yourself in the shoes of somebody who's using internet for the first time. What will go through their head here, right? I don't know what to do, and what is the result of that? It's just give up, too confusing, I don't know. I don't want to use it, right? And we've seen this happening, right? When we've created the first prototype of the application for these users, for this line, when we gave it, I mean, obviously we were, we made that pitfall of designing for the typical customer, we gave it to them. It was a learning side. They rejected it so badly, we came back and we were like, we were holding heads, and oh, why did we spend like the last two weeks sitting and designing this? They didn't even look at it. They're like, we don't understand it. It's just too busy. I don't know what to do in this application. This is precisely what happens. So when you're designing for low digital literacy, these are some of the things that you have to keep in mind. You have to make sure that your layouts and iconography, it's minimalist, it's uncluttered, right? At most, pre-call to actions per fold, and again, material does an awesome job of providing guidelines for what kind of layouts to use, what kind of iconography. The second thing is detailed messages. Again, making sure that you're placing alerts, confirmations, acknowledgement messages, give them messages left, right and center. It helps them. For somebody like us who use internet day in, day out, it might be a little irritating to have so many confirmations, but your confirmations can be very subtly placed and even system generated at times just to make sure that your users are actually being able to get confirmation. It gives them that trust that, yeah, I'm interacting with an application and it's doing the right thing for me. The other thing that that does is also reduce the possibility of mistakes, right? If they're going in a wrong path, they're not taking the happy path that you want them to take, just give them the warning, right, that you're doing something wrong. Okay, again, quick activity. How many of you guys see two numbers in these circles? Everybody? Great. I didn't see one hand raised. How many of you see six in one of these numbers? Okay, how many of you see a five? Great. Do you see a five in the left or the right? You don't see a five. Okay, awesome. This is not, that's not awesome, but I'm glad to have somebody be, because I've had audiences when I did this, everybody could see everything and then it got boring, but sorry about that. Okay, what is the color of the flowers? How many of you see blue flowers here? How many of you see lavender flowers here? Lavender purple, right? This goes a little deeper, right? So this, most people who will, most people will see, will not be able to see the five over here. That almost 50% of the populations are lavender, there's 50s of blue here, right? So what is this? This is, these are challenges with being able, so are you able, if you're going to use these colors on your application, and this is again a little UIU eccentric, right? Half the people are not going to be able to read it. They won't be able to make out what you put there. So here are the design tools that we used, and yeah, this was a big challenge because we saw 50% blue and lavender. So some of the design tools that we used to make sure, of course, I mean, I just put those for the AV part of it, but then there are often challenges you'll come across with audio limitations, right? You might have people who have some motor limitations, right? Especially when you're looking at designing for smaller age groups, right? Learning applications, very important design challenge to solve for learning applications, cognitive and motor limitations. What were the design, what are the design tools you can use, right? You can use transcriptions and narrations, right? Enabling the automated narration tools and transcription service. Again, something that Drupal does amazing, great modules available to do transcriptions and narrations. Readability and interaction, right? Making sure your colors, your typography, the screen mode, you brought up the point of the icons being too small, right? Making sure whatever elements, every element on your screen has its place is important to that page, is gonna load correctly and for all the right audiences, making sure it is clickable and readable, right? Using standard typographies, again, is extremely important. A lot of the times you will come across applications which is using things like, you know, very beautiful fonts but hardly readable. So that's the next design challenge. And then we come to the final design challenge of which sort of bundles around all the ones that we have spoken of so far. The diverse culture, the diverse identities and ethics. And again, kind of from the client we work for, we did a color study which was very interesting because the application was being designed for girls, young girls and we said, okay, you know, let's pick up something that's nice, cheerful, happy colors. We picked up four, five colors, did a color study around it and sent back samples to the user research team to go through with all the girls. What we found is, and when we did this color study, we studied about 12 different colors, primary and secondary colors, and we found like every color has a different connotation in different places of the world, right? And we eventually, hence, zeroed down to blue and pink, right? Pink was rejected by the way by all the girls. They said, we don't want pink, surprising. We all think that pink is something that girls like but they did not. So we settled on blue there. Probably one of the reasons you see blue very frequently is because it's got positive connotations in almost every region of the world, right? But yeah, I mean, doing these things, right? This is, again, one of the illustrations we used in the application, again, because it was supposed to be like a support app. We had to make sure that our illustrations were capturing very diverse audiences because it was a refugee camp. It was a refugee population and it had a mix of all kinds of people there. So again, a design tool that you can use to solve this design challenge is meaningfulness, making sure that your images and illustrations are designed in a way that the actual target audience can connect with it, not you or I. It has to be your target audience for the application that should be able to connect with it. It should evoke the right thought. It should not make them feel, it should not make them feel offended, right? One of the things that we had, you see the specs on that girl's face. We added that in later. When we first created this illustration, we didn't have specs on that girl. But then the girls came back saying, we feel that if you're wearing specs, you're intelligent and you're knowledgeable. So we want somebody with specs on the illustration and then we added those specs in, the spectacles in. Avoiding use of locally offensive colors, images and signs. So that's another design challenge and the design tool you can employ to sort of solve this. Some of the others, especially when you're onboarding your users to the application, some of the other onboarding challenges that you should think of. Maybe you're not solving for them, but understanding language barriers, exploring devices, screen sizes and resolutions. Understanding user security and privacy concerns and ensuring consistency in content hierarchy. I'm not going to dive deeper into each of these, but you guys are mostly from Drupal development backgrounds. So you know that the first three is something that Drupal does amazingly again. It has multilingual support, supporting a large variety of languages, RTL, LTR, everything. It also, you know, it fits very well to the different devices, screen sizes and resolutions. Also the security and privacy and then ensuring, because it's a CMS, it ensures that the content hierarchy is always, it's consistent. But yeah, I mean, if any of you want to talk, discuss more about this with me, I'm available throughout the day here today. Finally, quick question. How many of you guys have said this statement to one, you know, any of your users at least once in your life? I know I have. I know I have. Why did you make the error? It's written in that user manual. Now you got that in the user manual, didn't you read it? We all make this, I would say it's a mistake. I realized it much later, but as a developer even I have said this statement multiple times, didn't you read the manual? When I started designing, I realized that what we call error is usually bad communication or interaction. When people understand what has happened, what state the system is in and what the most appropriate set of actions is, they can perform their activities more effectively. Right, this is again a quote from Don Norman's book, Design of Everyday Things, amazing book. Anybody wants to get into really how product design is done? But yeah, I mean this sort of sums up the essence of what we look at as a solution design, right? Oftentimes we expect our users to behave, to interact with the system in a certain manner. And 99% of the times they won't do that. And then they'll run into errors. They'll run into obstacles, roadblocks, which they can't solve, right? So this is where, and this has a very serious implication actually is that when you're working with a diverse audience or even, you know, we don't even have to go into the kind of diversity we were speaking of so far. Just think of your application being used by let's say a 60 year old, right? They get stuck with something. What will they do? Oftentimes they will not think this is a system failure. They will not think, okay, why was an alert not given to me? Or why was I not told what to do? Or given a right hint or a tooltip in the app? Most of the times they'll say, oh, I don't know how to use technology, right? It's a common thing. It's perceived as human failure, whereas actually it is system failure. And what is the adverse effect of that? People will stop using it. Especially the vulnerable population, people who are old, people who are young, people who have some kind of challenges, right? Or people who are maybe first time users. They will think that, oh, I don't know technology and that's like a mental block they'd develop. And this will often stop the user from returning to the experience, to the digital experience that they were on. I've spoken a lot and I'm hoping the audience is still awake. So we're gonna do a quick activity. What I want you to do is, and here's where your partner or neighbor, somebody around you comes in. Raise your dominant hands. If you're a right-handed person, your right hand, left hand. Okay, put that in your pocket or behind you. Okay, now take out your phones or if you have a notebook, take out your notebook and any note-taking app on it, pull it up, write your name, type your name on it. Okay, let me know when you guys are done. You can just maybe, you're done. Okay, very fast. Excellent catch. Done, okay. Now, pick up a neighbor, some of you guys are sitting alone but now exchange your name, show your name to your neighbor and maybe exchange phone number or your LinkedIn IDs with them. So open either, let's say the phone app, dialing app or the LinkedIn app. You can just share it via a text. Okay, share your, any identity. You could share your phone number. You could, if you don't want to give out your phone number or your, let's say you could just share your LinkedIn ID. So open LinkedIn, say share, hit the share button, send it to the other person or send a connection request. You're making some connections as well in this session. Yeah, network a bit in this session. Just making sure everybody's awake for the next 15 minutes. Okay, done. Okay. I see some people have completed it. Okay, are we done? Some networking done? Great. How did the experience feel? Any volunteers? From this side this time. I think this section is very interactive. How did the experience feel? Sorry? Inconvenient, okay? Awkward. Yeah. Normal, you're the exception. And again, another persona for our, if somebody was to do a user research, you would be another persona because you could use both hands. That's amazing. So we have any other experiences. How did you guys feel doing this? Slow. Sorry? Yeah. So it's difficult. It's slow. It's awkward, right? It feels unnatural, right? What was this? What is, none of you guys have really, I mean, I'm hoping, but none of you guys really have any kind of disability that way, right? Using your dominant hand. But does that mean you will always use your dominant hand? I think this gentleman, you brought up a very nice point. How many of you registered your non-dominant hand fingerprints? Exclusion. Can, it does not always have to be permanent. When we design for audiences, and earlier in the session, I spoke of a point where I said, you know, it's not always, if you're designing for, if you're building an application for inclusion, it does not always have to target people who are, you know, who have certain disabilities or who are always from, you know, a background that you're not familiar with, right? Exclusion can of course be permanent. Somebody with audiovisual, colorblindness, cognitive or motor limitations. It could be temporary, right? What you just had was a temporary limitation using your dominant hand. It could be a short-term injury. You could have a broken limb. You could have a ear infection. It could be situational, right? All of us who parents probably here in this group or, you know, who've got kids, know, you know, how it feels to have a toddler in one hand and then do all the other work with the other hand, right? So it could be situational, right? You could be driving and have to take a call, right? You're trying to watch a video in a very noisy place, right? So it could be situational. So when we're designing or building something for inclusion, does not mean that you always have to go into researching an audience sitting in some remote place of the world. It is right here in this room, right? So that's where, you know, when you're building your applications, you have to make sure that you're designing for all kinds of exclusion, not just permanent exclusions, but also situational or temporary. So building a digital experience for inclusion benefits everyone. It's not just somebody you've never met. So question of inclusivity versus accessibility. I know there are a couple of more sessions around this today. So I'm gonna go like breeze through this. When we talk of inclusion, including and learning from people with a diverse range of experiences and needs, when you're designing the experience, right? When you're looking at what should my architecture look like? What should my UI UX look like? What kind of error handling do I need? I'm designing it still. I do not have the concept of a typical customer when I'm designing for inclusivity. Accessibility on the other hand is a digital experience that enables people with diverse needs to use it. It has a very clear definition. If you go and look at the WCAG standards, there's a very clear definition of what your typical customer for accessibility will look like, somebody with certain limitations. So in a way, you could say designing for inclusivity is the method. And accessible design is the outcome of that method, right? In a way also, accessibility is like a subset. When you design for inclusion, most of the times, and we saw that in the design challenges, most of the times, accessibility will get covered in it. So accessibility doesn't necessarily take into account different ideas, cultures or perspectives. It focuses more on adapting the content to support different modes of interaction and engagement, hence a part of the outcome. Last part of the session, what we learned while we were implementing inclusive DXP with Drupal. Some of the handles out of Drupal that we leverage and amazingly, because it's so convenient to actually build an inclusive design in Drupal. A virtual personal guide, we've got the onboarding modules available with us. So when users access the site, they were greeted with Ania. Ania is a name that's virtually there in almost all languages. So we could find this name with a very positive meaning in almost 86 different languages, which means graceful in most of them. So Ania was a virtual personal assistant, their guide throughout the site. She would help them on board, provide them recommendations and help the user navigate via prompts. Voice assistants, we did an integration with Google voice assistants as well, but because not all languages and dialects were supported, there was some which was built custom. So instead of a conventional search page or a content listing page, users were first presented with a box where they could like a search box where they could speak questions into the search box and they get directly to the contents instead of having to browse through content or typing in a search. So Ania enabled users to find the relevant content via speech and voice search based on their interests. Offline support, again, users could download content to view offline. We did a PWA, so their activities offline were stored and synced once they went online when they were in a better bandwidth zone. We did localized microsites, so Drupal MultiSite architecture was adopted. We built multiple microsites based on the core main site. The code base was kept the same, but they had different themes and different modules for each microsite based on the geography that it would be shown in. And some parts of the database were also different to deliver the localized versions of the site. Low bandwidths, again, we have the Drupal AMP module that we used, making sure that even people in 2G, 3G connections could access at least the most key pages of the site. They can work on low bandwidths and automatically all the layouts were generated in AMP with literally zero effort. We were using Drupal 9. It was multilingual, supporting almost all languages. And it was mobile-first PWA because none of our audience segment had, almost like it was hardly 10, 12% of our audience segment that really had an access to a laptop and or a desktop. Finally, wrapping up with the question, why should I invest on designing an inclusive digital experience? I know that many of us, this question came up a couple of times yesterday as well. If you guys were on Tavi's keynote as well, do I design, what level of inclusivity do I need to go to? Do I need to pick up all the diversity that I can? Not really. It depends. It's the 80-20 rule, 80% of your users. The 20% is for us when we design, the 20% is always a nice to have. We follow Agile. The 80% is a must have. The 20% is a nice to have. We try and break down that 20%'s requirements into as granular as we can so that we can pull it into our requirement set that we implement. Why should I invest? The next three billion customers, these are your unconnected populations, people who are sitting on either no internet or very low internet. This is your literacy rate by region and gender, right? This is just an input. And what happens when you design for these people? You expand your consumer base in existing markets. Like we just saw, we have a very diverse, very different audience, different identities sitting right here in this room which has hardly 30 people in it, right? But you can expand to every single person sitting in your existing market. You can target new markets and very important from a business perspective, you build trust in your brand. That's key critical element to why you adopt an inclusive digital experience. An inclusive digital experience. And of course, because it's the right thing to do, right? It's unfair that we who are maybe privileged are able to use almost all applications. There are vast majorities who are not able to, right? And if we look at ourselves as developers, we do wanna make sure that what we are building gets out to as many people as possible. So it's just the right thing to do. Some resources that we refer to when we were doing this case study, when we were doing this project was the design kit from IDEO. Amazing design kit. It's got handy tools and everything. Best practice guide from Material and the W3C's accessibility initiative. So with that, I wind up and I don't know if you have time for questions, but I'm right around here. Yes, maybe one question we'll pick. Sorry, this is very simple. What is AMP? You mentioned AMP. Accelerated mobile pages. That's like a very, to put it very simply, it's a very basic version of your page. Strip down of all kinds of, you know, all elements that will consume a lot of bandwidth. Yeah, unfortunately we're five minutes over, so we're gonna have to leave it there. But thank you very much, that was fascinating. Thank you. Thank you so much.