 Hi good morning everyone. So as you see on the screen right now, so I'm here to present empathy driven design how Drupal prioritize accessibility for end users. So I'll be covering the two sections. The first one would be for UX UI designers, which has to focus on empathy driven design. And second part, yes, as part of DrupalCon, I have to fit into something related to Drupal. That's a reason the second one is all about. So I'm Srinivasan from Accelerant. So we create accessible digital culture. We are your team. So we have an internal framework, which is completely depends upon the accessibility, which starts from audit and we go for the recommendations and implement it. So that's where from I am. Yeah, the agenda is first I'll be covering the significance of empathy driven design and accessibility and the practical tips for empathy driven designs. So hopefully we might be using few tools for color contrast and for size, fonts and everything. So I'll be giving few suggestions on that, which we have experience. And apart from that legal and ethical implications of not prioritizing accessibility in Drupal web development. So that is the one important part which I would like to highlight throughout the session. And next is Drupal and accessibility. It's empathy driven approach. I have few demo on the modules, which we have used on the sites, which is easily accessible through the Drupal.org. So those I'll be showing you doubt Q&A, which I'm really worried about it. Let's see. So empathy driven designs. This is a very common picture, which we always see that right. So we haven't sympathy towards all the people over here. As a person, I have sympathy, but I'm not sure whether I have the empathy when I'm going for something. So when a project manager gets a new project, you always used to say that put yourself into the customer shoes and try to get the requirements. We are ready for that, but only on the functional parts. And now as part of accessibility, we need to ensure that inclusivity should be there. So I'm going to start with a failure case study and probably some successful ones later. So Nokia phones that was a successful in the year of 2000 to 2005. And later it completely got diminished. So what was the reason for that is Android approach those people for employing the Android features regarding the inclusivity, but they denied it and later Android comes into the picture. And I hope now we are into most of the Android phones and iPhones. So hardly we can see the Nokia and but recently I had a very good experience. I would say I have given my iPhone for service and I ended up in using the Nokia normal phones, which is like a keypad only for three days. I was very much having a difficulty, which is away from the social networking. First thing, second thing, I don't have the liquid cash always with me when I wanted to pay something. I got a practice of using the GPS Google paste and I went to a store, I ended up and okay, I have a GP. I don't have the liquid cash. Then I realized that I have a mobile of Nokia, which I couldn't. Then the person told me there is an option to pay GP from the Nokia. They started utilizing that option and I paid in the same way. So they realized that change according to the people needs is most important when we work on this era. So this is the one of the best experience which I had. So let's ensure that whatever we develop, whatever we go for any project, any kind of things, whether it's a real time examples, whether it's an online or is it a physical mission, which you are developing, ensure that inclusion is on our mind as an empathy, not as an sympathy. That's what I wanted to highlight here. And apart from that, so that's all about the empathy part. Now when it comes to the accessibility, so when we go to the parks, right, any kind of refreshment parks, when we see that they have an accessibility into the picture, very crucial roles. They have the ramps for the wheelchairs. They have the kids play area. They have the walking path pathways has been brought for the older ones. They consider the gateways to hold it if someone cannot walk. So those people are considering accessibility to the core, whereas we have an option to reach out in a wider area through the web and we are not utilizing it. So let's ensure that we have to go for empathy driven design, but starts from initial phase of the project and it's not a responsibility of only the QA or the development team. That's what I want to highlight. Now getting to the next part, I just would like to know how many UX UI designers are there. So probably it'll be more helpful or how many are looking to the color part color contrasting ratios when we go for a Figma designs. We don't prefer that. So that's the one thing which we have to focus on. So there are three levels of conformance level as part of WCAG rules. So when we have to consider the designs, there are three parts, three conformance levels. So one is oney level A and the second one is level double A. Third one is level triple A. So I can give you a few scenarios like that. So level A would be like I'm a person from India and I like Indian food a lot. So if I'm looking for the restaurants and inside India where I live in, I look for the awesome one where I have to have the real taste one that comes into level triple A. And if I'm stepping out of my state, some other state, I just wanted to have something which at least I need to survive with a good taste. Then I'll go for level double A when it comes to the one where I can, I just wanted to survive. For example, Pascal Flauft is I'm going through the same thing. I need something I need to eat, which I need to survive until I go back to India that comes to the level A. So when you go for the color contrast ratios, we have to consider these scenarios. How much we can fit into the WCAG levels, that is one we have to focus on. And it comes with the branding guidelines with the website which we are preferring. So normally what happens is when we work with the brand colors, so as a UX designer or when, when we start with a project, we will get the requirement where we review the designs, we will get the wireframes and we will review the designs. The initial part you would be getting is the branding guidelines from the project. So the branding guidelines which I say is like it comes with the color for the logo or it might be the entire background color throughout the website. So those are the things which will be client will be saying, see, I need a blue color and I need to ensure that my hyperlinks are in the red. This is the requirement from the client you might be receiving it. So as a project team, what we have to ensure is we have to check the branding colors, whether it is suiting to the WCAG rules, work client is not aware about it. And second thing is like cost. So when we say something like accessibility, right, and we are telling them like for the accessibility audit, you might be paying this much amount client is like, no, no, I'm not ready to do that. What should I have to pay for it? You have to implement it. We have to let them know that it's a one time investment. So you're going to revamp the entire project and it's the initial part you will go and design it. And later it is just the reinforcement part. But whereas if you are going with the fines and settlements with the government, it's not related to nowhere related to that particular amount which you're paying for the audit purpose if it's required. So these are the things which you have to focus on. And as a first step in building accessible color palette, so these are the few tools which I'll take you right now how you can check it out the colors and everything and post that you can tell the client like, see, this is how we have to design with the colors you have provided. I'll show a few of the tools over here right now. You have to bear with me. It's on the second screen. So it's slow. So if you see that there is a color coding over here and you will be able to see what is the background color contrast you have to keep and also the text size, which is leaving the triple A level. So when I say that triple A, that is something like the maximum of conformance level. And if you start moving that palette, so this is the foreground and this is the background. And you can try with different color options over here. And if you see, you can see that the text fails, headline fails. So whatever the text and headlines, if you give it to the foreground and background of this one, it will fail the WCAG limits. And it is not visible for the most of the people. So this is how we can play with this particular tool. So this is the one of that. So this is the other one. These are easily available. So you have an option to choose the background color here, which is white. So if I go with it, so it says one, this code is really light. So whatever comes as four, more than eight, it can be conformed for WCAG levels and we are satisfying those things. So this is the one of the tool. And this is one of the tools. So most of the team is aware about this. We are using the big one for the design purpose. So you have a trial and error option. You can embed it with a big one you are using and you can try the color on that's right there. So when the client says that, so I'm not sure how many of you regarding this issue. Probably the differently able person regarding CEO of Facebook, Ma, he has a red, green, blind issue. So that's a reason he ended up and he will be able to see the blue color in a very, very good manner. So he wants to create a logo of Facebook in a blue and every white. So that's one of the reasons. So we have to consider that way. So the next one is a shapes contract. This is really a good one. I would say you can visualize one for the screen. So you have the options over here. So you can go for the colors and show triple A, AAAT and DNP. So AAAT is something like you can have the colors and you can have the contrasting colors in a mild way, but the text should be in a larger size. So that's come to the picture of the sub. I would say it's a subset for double A. So that is AAAD. And then you have something for DNP. So if I'm experiencing DNP, if that comes into the picture, so you have a light blue and the text, this will not go. It is a white color. So this will not go. It will have the DNP. So this is the metrics which is prepared in that particular way, which you can wrap up for the logos or maybe the entire website colors, the background which you want to keep. You can wrap up to this particular metrics. You can play around with this and get the right one for that. And we can go and recommend that to the customer. So this is one more, which is accessible. So you can try here. I'm just trying to upload image. So you can consider this as a company you are trying to upload. It has the palette results. So when you're customer gives the brand guidelines, it's our responsibility to let them know that, see, hey, this goes with this color. Shall we try something else? So this is something we can try it out and go with recommendations in the Asia phase where we are not playing around once this development starts or once it's gone for the accessibility or something like that. So this is the one of the best room which I really like it. As an example, so how it was implemented. So in the live screen, you will be able to see the icon which is in the white. Whereas the white background, I'm not able to see that. We didn't even consider about the accessibility over here. So we have to be very, very much conscious of this icon when we are going with end icons on the top one-stop lane. We should keep the focus on those things as well as part of the accessibility. So these are a few more tools which I have experienced and one is really another one. So far we were discussing about the ons and the text. So this is something for links. So if you have a link on the site, you can go for this. So you can use this tool and you can provide the link color, body text color, background color. So now I have said it in such a way like if you have the blue, gray and black, which says it has passed and the link to background is free. So this is the one and this is in black. I mean, it's an ash color, so it doesn't go with that. So it's free and the text and the body text has been disabled. So this is something which you can try for the links, link contrast checker. And the next one is web end contrast checker. So this is the another one which you have to check for the contrast colors, which is completely for the backgrounds and everything. So you can provide the normal text and large text. It will tell you the components levels for the scene, whether it's past or not and the contrast ratio. And you can play with the colors over here as well. So this is one of the other tools which has been useful. Yep. So the one which is with the tools and I would say, so it's to remember for empathy designs. So when we start with the development, we have to have a checklist kind of thing. So I'll show another checklist there. So probably I can show that. So these are the points which you have to remember. So establish a color heading structure at the outset. So when I say that they establish a clear heading, I would say like H1, H2, H3. So when the person used the keyboard tax, so they should be taken care of like this is the heading, this is the subheading. And this is something like heading only for this particular paragraph. And this is only for this particular section on the top right or the bottom right. So you should have a semantic head section, heading sections. So that's all about the establish a clear heading structure at the outset. Then only the menu links will be properly can be navigated by a person who's using the keyboard or screen reader. So we have to consider that. After the menu, we will have the jump links on the top left and we will have another site block or maybe any other menu block, which is we call is a related tax maybe on the right hand side. So which will take them to identify that, but whoever is using the screen readers or the keyboard navigation will not be able to find out. So that's the second thing you have to focus, maintain an appropriate reading sequence, that's a one thing. And ensure educate color contrast, which we have discussed in our vast, we can use those color tools, whatever it is, and there should be a color contrast given in the proper way throughout the design. That's the one thing which we have to focus. The next one is offer actual text instead of text embedded in images. You might have a very colorful, I would say glittering image on the site and you want to give information to the customer for a glittering image. It doesn't work out. So you have to ensure that there is an alt text or there should be a text image which is kept separately as an image. It shouldn't be an informative text. So that's the one thing we have to focus on that. And apart from that, next one is utilize and educate font size. So when you are using the phones, I guess the phones and so you should be able to respond to text size. And this is very common. I think we have to do that. But one thing we have to consider is when we replace the components inside another component, we are considering the accordions. And if you are placing a paragraph inside the accordions, we may miss in this text size. So that also should be focused when you place it in that particular way. It should be more responsive. That's the one thing. As part of normal common site, I think now the sites are very much responsive when you're using any kind of devices. But when you place it inside another component, we need to ensure that it fits into the exact size. That's the one thing which we have to focus. And apart from that, the next one is take line length into the account. So when you have the mobile one, we have 20 pixels of margin which is being applied and also for the desktop it's normally 40 pixels. So when you consider the line length, I would prefer like there is a word which is around 25 characters. We do not want end up and breaking that in the last half, 15 is on the top first line and another 10 is on the second line. Let's not do that. So we should be writing in such a way like we have to consider the line length when we are designing it. That's one thing we have to give to the developers. The question from the developers would be like, okay, tell me how many characters fit in that particular line. That's one. So it is something that we have to focus from the initial phase. And the next one is avoid both extremely long and extremely short lines of text. So when I see the short lines of text, I have a hyperlink which is really up to you to some other side. And we are not keeping it very much combat. And I wanted to ensure that client knows that you will be landing on this particular page. So there should be a naming given for that particular hyperlinks. When we are giving the hyperlink names we have to consider this accessibility as well. So those are one sections completely we need to focus. The next one is ensure recognizable length. So when a client wants to go to a particular form or when they want to submit it. So we have a different kind of like, I want my side to be very much unique so that I don't want to use a submit button. I don't want to use a sign up button. Let's do something else if it doesn't work out. We need to ensure that certain things has to be informative, communicative so that the people can understand. So a person, we have an experience on the same thing as like client wants to say that for example if you are telling that there is a form which I need to fill it out. And I just wanted to ensure when you click here it'll give you the terms and conditions. That's what it was explaining. And it was telling that I accept and they were asking for example, I accept should be a hyperlink. And when they click on it it should show the terms and conditions. Most of us would have been gone through that. We may think, where is the terms and conditions? I'm able to see that I accept and I keep on searching for that I accept options. So that is not that much accessible I would say which we have a pretty much stuff by. So that's one thing. Next is design keyboard focus indicators. So design keyboard focus indicators like when you hover on that particular links there is an option to show that you have the keyboard navigation which will show the close whatever it is. So we should be having the keyboard navigations in that particular format so that it will be easily accessible for the absolute people. Next is include a skip to main content link. So this is something like I ended up in the site and I ended up in the navigation. I would say it might be helpful for the couple of people who doesn't know that but I am right now in my team. They might be forgetting within 10 minutes. I have started searching something on the site. There is a door bell ring and I just ran over there and I come back. I forgot completely. This is for the cognitive people and I'm not sure what I'm right now and I have to start from the beginning. So in that case if we have a skip to main content link it would be very helpful. So another thing is if you're thinking about the buildings definitely we will be having an emergency exit because on panic mode we might be knowing where is the exact door so we might be searching for that. So and it'll be difficult for us to reach on that particular one. So we'll go to the emergency door normally. So that is something we have to relate with the skip to main content. And the next one is craft meaningful link text like click here, repo but it doesn't mean that you have to use the click here throughout the site. It should be used whenever it is required. Wherever it is required to repo you have to go there. So that's something like craft meaningful link text. So the next one is create user-friendly widgets and controls. So you have something called a collection of content blocks which are maybe a slide shows. So the slide shows will work in the desktop. When it comes to the mobile it is we have to prefer like whether I have to see the slide show one another each in the below or it would be good if we are keeping it as a carousel. So that is how it has to be designed. So we have to ensure that the user-friendly widgets are there. So which can easily accessible something like within a single widget. For example, the torch and emergency numbers on the mobiles. It's something like it can be easily accessible on the panic mode. So that is something we have to continue. The next one is exercise caution with animation video and audio. Of course, everyone likes the video part when something is there in the site. I go like, okay, there's a lot of videos. The graphics are there. It's a graphical representation. More informative and more attractive. But how much it is being, it can be accessed by another people who I'm talking like maybe the visually impaired people or maybe who is having an issue with. It is a nice music, nice background music. But the person who cannot hear it doesn't go well with that. So we have to ensure we are considering them as well. So that video and audio we should remove more and more cautious on that particular one when we are targeting only the people without any different video once I was here. Caution, this is happening. If you go to the NGO site, you will be having an alert bar which is going on. So that is something that we have to focus on that. That color of convict, that is what we are talking about here. So what are the information which has been very alert? And if you wanted to give some information, for example, an alert message in the Slack, we used to go with the alert symbols. I tried to alert them that way so that it would be more easily cache sheet. That's the reason. So we have to be more focused on that. The final one is design-accessible form controls. So when I say the design-accessible form controls, if you are using the Drupal, so when we design it, when you go for the form valuations, if you are not submitting any kind of field and if you submit, say, the node, it will go to the top. It will not tell you exactly if you are not being customized, like which field is not working as expected. So that is what we have to customize. So design-accessible form is like soft morning messages, blogger messages, error messages, when I'm talking about, when you don't submit it, you will not be able to move further. So that kind of message should be more informative so that they can read it out. It's not like a simple one. This field is blank. Why is it blank? That's more important. So we have to consider that. So that is the one thing, design-accessible form controls. So these are the few tips as part of the empathy designs, which we have to consider so that probably we can put it into the WCAG guidelines to a maximum level of that. So under AAA, I would say, the implications of not prioritizing accessibility into the development. So I'm reading this with disabilities acts. So they have provided the discrimination against the individuals, I would say. So that has been interrupted by some codes to apply website and digital platforms. So section 508 of the RehabLation Act required the federal agencies to make electronic and information technology accessible to people with disabilities, I would say. Failure to comply with this 1508 results in the legal actions and laws of government contracts. So if you deducted the other one, WAD, the European Union's Web Accessibility, they required public sector websites, mobile apps to be very much accessible. So non-compliance with this particular one can lead to legal consequences including final and legal actions. And the next one is national laws. So many European countries have it on regulations and related to the Web Accessibility. So for example, if you take the UK, Equality Act 2010 is there, so which includes provision of digital accessibility. So national cases, so I guess on 2021, there was a legal action has been taken on the dominoes for the same in the Europe as well as in the UK and there have been so much of time for not being accessible. That's what the reason. So the UK, Equality, 2010, which I guess that's right now, they have the WCG to 0.1 and level AA components that are to be there. So if you satisfy that the website is good to go, that's how it is. And apart from that, there are regulations which came into the picture on UK on 2018 as well. So the next one is the European Accessibility Act. So as of 2018, June 2025, customers will be able to file complaints before national courts or authorities if service of products do not press type in new rules. So we have another 1.5 years to go where we start already having outside right now, probably we can end up in getting a good access within 20, 25 years to go. So we don't have much time to do that as well. That's something we have to focus on. Which is like a medical disability act as I have echoed earlier. And apart from all these, these are, we are really worried about the regulations and everything. But let's ensure that we are giving the psychological safety of our own people who works with us. That's most important when it comes to accessibility. So apart from all these, so when we get a demand like, so when the team is not ready for an accessible and when we get a demand like this settlement would be like around, it's being mentioned in the Google, so I'm not sure I don't have any data part from that. But I guess it's fine up to $55,000 and violation is around like 10,000 more in subsequent violations. So let's ensure that we are sticking to that. We are educating our clients that accessibility is most important we have to consider from the initial phase of the project. This is something like if you are not doing the priority in accessibility lawsuits which I have explained much right now. So individual with disabilities they can file a lawsuit against organizations with websites lacking accessibility, claiming discriminations. The next one is financial priorities as I told you right, $55,000 which is really a huge amount. So that's the one thing which we have to focus on. Reputation damage, which cannot be purchased by a money agency. This might give you a reputation created for a site and if you end up giving the penalties, penalties would be like a one-time shot and we can go for a revamp. But getting that reputation again for the same site would take much time. So ensure that we are not having any reputation damage. The last one is lost opportunities. You might be using the opportunities with the, I would say government contracts and might be a higher clients thinking that okay these people have not considered accessibility. So we may end up in penalties. So we don't want to do that. So we might lose opportunities in the market as well. So let's ensure that we are sticking to the accessibility and not getting into these stuff. So how you can do that? So right now we have this because what is the challenges we are facing? If we are not going into what trouble we will be in, now this is something like let's ensure that we are working towards a solution to conduct an accessibility audit. So I was talking about this in the initial phase. So whatever site you are working, you can refer to this. There is a digital accessibility audit block which has been written properly or any other part which is related to the accessibility audit. You can refer to that and start auditing the current site and check what is the accessibility level, the score which you have for your current site right now. And the regular testing. So continuously test your site. So when I say the regular testing, one thing you have to ensure is let's ensure that we are just checking with NGOs or let's ensure that we are recruiting a person who is having a different ability, a skill and then let's get it tested so that we will get more results and it will be more productive. So as a person which we do not have any kind of visible activities, it will be pretty tough for us to include that. So like ensure that we are having any one as part of the NGO for that and regular testing can be done so that it will be more productive for the site. The last one is training. Educate your team on web activity in best practices. So for the front-end developer, they should be knowing how to clean the headings. As a UX UI designer, you should be getting a custom client that these are the things. And when you get to brand guidelines, so the client might not need this blue color. That is what my client got. So let's first check it out whether it goes with the specific guidelines. At the first point you have to consider a point considering the brand guidelines colors. That doesn't work so well. And you are not able to match the guidelines. Let's propose a new color to the client which is related to that particular color. So it should not be a different color, I would say, maybe something like a blue. So something related to that particular blue we can go and recommend to the client so that it's not going with the color options which you have told. Let's go with this new color, go with the data so it will work out. So these are the things which you have to consider. So that's the training part as stability. Now we have a couple of modules which is being labeled in Google which is easily accessible. We can download it as a conflict module and you can use it. So there are certain things as like, search engine format presentation, that's the one there. And the next one is brand and rock functionality. So that's there. Color contrast and intensity, there is a module for that as well. So image handling, form labeling, removal of duplicate or null test. So there are a few things which is on the Google modules is already available. So I'm going to take some models which we have tested later to that but not exactly later in this one. So these are the things which is already there right now which we can, on handy we can use it right now. So to each one of us, let's ensure that our website harmony is every user is part of the tune which we prepare, which we make, let's consider that. Prioritize web accessibility and improve your business. So these are the few tools. So Drupal Machica would say modules that makes accessibility a reality. So if you check the first one, accessibility audit. So when we say the accessibility audit, there is a site which is already there and you want to check the score for that and go for the recommendations. So that comes into the picture for the accessibility audit. So there are two modules which can be used for this, Editorial 11y Accessibility Checkup and A111. I'll show that. I think it might be not accessible for the people who are here because I'm standing here. So there is a tool at the very bottom. I played the block over here. I'm sorry, I was not expecting this. So there is a tool. This is called Editorial 11y. I enable it through the contributed modules. So this you can tell your developers to enable it through the contributed modules and it can be used by the end users. No coding knowledge required, I would say. So once you create the content, once you create the content and once you save it and once you come to the front end, you will have this option. There is a tick mark over here. When you click on that, it will tell there's an issues, outlines and all text. So the all text is something like for the images is there in your text as being given or not. Those things of issues will be applied over here and if there is anything to be taken care of, it will be reported over here. And apart from that is Editorial 11y. If you go to the report, I want to see the report over here. So content accessibility results from that particular module will be shown here. So you can run that and you can get the report as well. 11y, so I place it on the bottom. So this is the other one. So you have an option to check text degrees, text rest, reset, increase, disable animations, contracts. So when you move the contract, you will see the colors changing. And this is for the text, the fonts and the things that get changed. And if you have an option to check, you can work on it. So this is the other tool that you can use for accessibility audit on the current site. The next one is Site Widows. So the accessibility audit can be used by I would say like product manage, managers, QA developers. Anyone can use it once it's been placed as a content report. So the next one is Site Widows. So the Site Widows is something like block, area, landmark, rules. So when I say that, if we consider this search, search bar is being placed with a block, right? So if I go to the search bar on the site, which I have taken care of, let me show that. She's not at the search bar. We have just invited you to do it. You can see it. That's the first one. Yeah, search bar here, right? So which I develop when they are developing, they have to keep the area levels for each particular block which they are preparing. So if it's not being done, and if they are forgetting it, they can enable this using the block module which has been given in the program. So there is a block which can be enabled in a particular way. So this is something like I would say it's only for the developers, but you can mark down the names and you can pass it to the developers, I would say. There is something called, if I, for example, if I'm trying to place a block, I'm trying to create a case block, I have an option to choose it from here and it may be available. So once it is done, they can enable it and they can give the key at area, for example, search, enter the keyword that would be block area before that for the program. So that is the one thing which you can consider as part of this. But it's like, apart from that, no-link reports, that is for the site, and as I would say, so this no-link reports will help you to find out is there any broken links on the site? You can find them in the notes. You can see you have the no-link over here. If that one is being enabled, you will be able to see there are two links on this particular page, hyperlink and it's working as a factor. So that's why it's mentioned like two working. If it's something is broken, it's mentioned like two broken links. So this is something which you can implement as part of the site, the link itself. So this is the other tool which can be used for the group. The end users is something like civic activity tool bar, web activity and non-zero. So this is something like, later to which I told you right now, you can see the color contrast by yourself once it's been enabled. So if you go to the site, it was showing change in the colors. So this is called civic activity tool bar. You can keep trying changing the colors over this particular one. So this is the one which you can try for that. So you can give the different colors. So this is something like a core module, I would say the core module is there. But the guy in the color, maybe that person can go with the grand colors and try it out. So that is something like which we need to customize it. So this is easier by the right now. So these are the few things which we can cover as part of this accessibility model type of thing. The idea I would like to conclude by saying that so far we have given the ideas of what's happening with accessibility, how to implement it and everything. Let's ensure that we're putting it up for the actions. So empathy in actions. Let's ensure that our commitment to accessible design is there. So positive brand image, that's the one thing that you get when you're implementing this. The second one is user satisfaction, which is most important for us. And the third one is legal complaints. We are not getting into any troubles by doing this. The last is inclusivity as a steep technology compatibility. So that's all about session, empathy, and design with Rupert Private Accessibility 4 end users. Thank you very much. You mentioned legislation from a lot of countries, but you didn't mention India. Does India have any legislation that on accessibility? I would say like, I have to consider the accessibility for the audience over here. I guess we are only the Indians. Probably we might be knowing what's happening. So I need to ensure that, what is the information I'm conveying? It should be reachable. So I focused on that part. Hi, thank you for that presentation. At some point, I missed the name of the tool you were using to do the accessibility check. It was in about the first third of your presentation. Is the one you're talking about? All right, so it is an internal check. It is a blog tool actually, accessibility audit. So in that front, we have the internal framework, which is being designed for audit purpose for the current sites. So there is a blog written on the same on a site. I'll just show that probably you can. So if you go to that, so this is the one you were asking like this. So you have the blog content. If it's just well written, I would say like in a hierarchy model, what should be part of the accessibility audit once you start with that? Thank you very much. Great presentation. I just wanted to ask, I've been using Axe DevTools in Chrome as a plugin very successfully. Do you have any other recommendations maybe for other plugins that we can use in Chrome that can work well? For auditing, for accessibility testing, just in browser. I think it's already there. Right now, up to the Axe DevTools, they have established that entire thing. Probably what we can do is like, they are getting a paid contract, I would say, with Axe DevTools once after utilizing it. So instead of that, we know that people will be getting more clients. So probably we have to try something with the internal tools with that what we are experiencing so that we are not end up and using monthly plans with Axe DevTools. So for an immediate response, we can go for an Axe DevTools, but if you are planning for a multiple longer project, I would say it's better for us to create an internal tool. Okay, I see. Also, I'll just take the next question. Have you worked ever on projects where you have automated accessibility testing on deployments? Yes. Yeah, you do, right? So we have a random particular script. It will give you the reports with the home page and with the unique links which has been covered as part of the sampling. You will get an entire report like what is accessibility right currently with that particular pages. And also it will have a graph paper presentation. So there is a separate framework for that automation. Right, okay, great. Thanks. Thanks a lot. Hopefully. Okay, if you have any more questions, I'm glad to catch up outside the auditorium. I have to give a session. Time for the next questions. See you soon, everyone. Thank you.