 I've been told that I forgot to thank the sponsors again, thanks to our sponsors ClearTrip, Web Engage and Music Guru. Sorry, I forgot. And I also wanted to say that it's absolutely coincidental that all the talks feature ClearTrip and Zomato very prominently as examples of good design. We didn't tell speakers to put those in at all. Of course, we would never do that. The next talk is by Shyamala who works at Amazon on user experience and she's going to be talking about mobile accessibility. So yesterday we had Prem who was, who gave us a beginner's introduction or an introduction to accessibility, what it is, how you can look at it and you also had some demos about screen readers, how they work, different assistive technology. So Shyamala is going to go into some depth about how you can solve the same problems but on a much smaller factor, the technical challenges that are introduced as well as the opportunities. Good afternoon, Shyamala this side. How are you doing? Hungry? I'm sure, I'm hungry. So my talk is on mobile accessibility challenges and base practices. Before going to that, the disclaimer is there are a lot of principles and guidelines for mobile accessibility but I won't be covering all of them due to the lack of time. So I'll be covering only couple of them which I felt is important. So if you feel like the ones which I am showcasing are not the important ones, we can take it offline and we can talk about it. And the second thing is yesterday Prem spoke about accessibility already. So there may be some slight repetitions in my talk as well. So I apologize for that in advance because accessibility is the same. The term is same, principles are same. The only thing is device changes and challenges increases. So now do we really need to care about mobile? Yes? No? Yes, why? Because you have one? Great. Sure. Yes, we need to care about it because it has become a integral part of our life. Everyone uses it everywhere, every time. So it is very much important. At the same time, it is important for them as well. Agree? Disagree? Agree? I don't hear any yes or no? Yes. So are we not being biased when we are developing something or some mobile applications? We are, aren't we? Yeah. But the big point here is mobile, by definition is disabling. Confused? How do I say that? Sure. Do you remember this? One of the oldest phone. How many people used to have this phone? Man, so many people. Great. So basically this is an electronic telecommunication device. So mobile, mobile basically was and is supposed to be an electronic telecommunication device. The purpose basically is to make and receive calls and then send and receive messages. That is what a mobile device was basically meant for, right? So that is the reason it have small screen, poor light, small fonts. So these are some of the things which makes it disabling. Agree? Yes. Now at the same time, mobile is by definition enabling. Any idea why this? What is that? Everyone has that. So the thing is mobile have, you know, the definition of mobile has changed from what it used to be to what it is now. So a lot of things have changed. People started expecting more from it. So rather than just being a calling device or messaging device, it has changed. It added so many new features. People want more from the devices. So then a lot of new features have been, you know, introduced like geolocation, camera, calendar. All these things makes it enabling. And then again, I cannot afford a computer but I have a mobile. I am not talking about the smartphones of course, right? Not everyone can afford the smartphones but basic phones they can. And basic phones can also have the same kind of features, functionalities, applications which we develop for smartphones, right? Now the next big question is what are the different types of applications? Can anyone tell this? I cannot hear. Native, okay, okay, that is not application type. They are a category. I mean the different categories of application which we are talking about. Application types basically are, as you mentioned, native applications which basically is device specific, iOS, Android, which you have to download from the respective marketplaces. And then you have mobile applications which is the HTML based application which works on your mobile browser. And then you have something called hybrid application which is a combination of mobile application which is when you, you know, combine these features of mobile and native that is what is called a hybrid application. And then you again have a responsive application. So these are the four different types of applications. Now the next big question is we have so many devices, we have so many different types of, you know, mobile applications to build. How do I make my application accessible? So before even getting into how, I should know what exactly is accessibility. Yesterday Prem spoke about accessibility but what do you understand by accessibility? I am sure you guys was not concentrating on yesterday's talk. No one is ready to give a definition? Making sure that the largest section of the population can access all the content on your screen which will be on a computer or now on a mobile. So basically accessibility to me is making an application accessible and usable for everyone irrespective of age, ability and situations. Right? And how do I call this for a mobile application? For a mobile application, I call it accessible when it is ready for the diverse user model. Like you have side problem, hearing problem, cognition, assistive technologies. When your site is ready for assistive technologies like screen readers, that is when it is accessible. Hidden disabilities. What is this? Depression, chronic and these things. Then you have aging. This is also important. The way I use a computer or a mobile, my parents will not be able to use it. Right? Generation gap. Or maybe when I grow old, I don't know how my son would be using it. And how I would be using it. Right? And then you have something called temporary fractures, accidents. These are also kind of disabilities. That is, that is not, see low bandwidth definitely is a kind of accessibility but that is situational. That is not functional. Right? Then you have cultural. This is also one of the things. And then technology and challenges, that is where your low bandwidth comes. Technology changes. Operating system keeps changing. So many upgrade comes. So many different devices come. So many new things are coming up. How do I make it accessible? This is what, when you are ready for all these things, that is when your mobile application is accessible. Now what are the challenges? Anyone? Sure. You are talking about the different accessibility issues. And as a part of that, you brought out things that were not generally considered or I haven't thought in depression being an issue in terms of accessibility. I know it's very prevalent but I can't correlate what is the accessibility issue that it brings or what is the restrictiveness. Because when you are depressed, your brain stops working to some extent. You are not, you know, completely concentrating on couple of things. Let's say you are depressed, you have some tension in your mind and you have to, you know, do some banking transaction or something. You may get confused, you may make mistakes. So that is again a kind of, you know, a challenge for you, a disability. Right? Sure. Yeah. So now what are the different type of challenges? Anyone? Yeah. What happened? Everyone is talking about bandwidth. Okay. Sure. So first thing is small device. So obviously this covers the screen size. The second thing is your mobile comes in all different shapes and sizes. Right? So that is the biggest challenge. I have the smallest mobile phone. I have the biggest tablet. I have so many things to, you know, cover. So many things to make sure like, okay, my application is accessible for. And then you have touch screens. That is the biggest challenge. And you have lack of standardized UI. Why? You have jQuery mobile. You have Sencha. You have the native applications. You have hybrid applications. So many different kind of applications are there. So many programming languages are there which we have to use. So you know that makes it very much difficult for us to concentrate on the accessibility. And then lack of device expandability. Right? Memory is limited. You can't upgrade it to a huge amount. It can be to some extent. So those kind of challenges. And then obviously you don't know what context you will be using your mobile device on. So context could be something different. Now, with all these challenges, how do I make my mobile application accessible? I would say before even getting into the thought of the standards and guidelines, accessibility should be in your mind. It should be in your decision making process. You should first think like, okay, I have to make things accessible. It's not just because, you know, it's a mandate in some countries. I have to make it. That is the reason only governments are accessible. Not all applications. So it should be in your decision making process. It should be in your mind before even thinking about the standards. Now coming to the ingredients. Am I going fast? Okay. So the ingredients are web standards, HTML, CSS, JavaScript, XML, which is basically used for mobile web applications. And then you have web browsers which again works on mobile web. Then you have platform accessibility APIs. So this is basically, you know, platform specific APIs which is available for device like iOS, Android, BlackBerry and so on. And then you have assistive technologies, screen readers, right? Then you have platform accessibility features. So all the devices have their own inbuilt accessibility features like iOS have something called voiceover. So when someone is touching, it will voiceover for disabled people who can't hear or who can't see, sorry. So, and the biggest is users. Without them, we don't even need the terms like accessibility, usability, user experience or we don't need these standards. Now coming to the principles. First is add descriptive takes to your user interface controls. So this is the same thing which we have been doing for web as well. We need alternate text. But why do we need it? Why? So that, as in, okay. So he's losing that content. So, yeah, that's it. The screen readers can read the content in case the images are not loaded. Right here. Right here. Right. The screen readers. Okay, okay. The screen readers in case the images are not loaded can at least read the content of having the all tags would help for that. Definitely. So the challenge is not all users can read the information if we have it in the form of images, objects and you know, dynamic stuff. So that is the reason all these things should have an alternate and descriptive text. Who does it help? It helps the people who are blind. It covers the functional disabilities. Right. It helps the people who use assistive technology. At the same time, it helps the functional disabilities like, sorry, situational disabilities like some people turn off their images in the mobile because you know, for downloading the images also, your data usage is there. So you may be charged. And then some of the browsers, they don't support the size. So it can shrunk and a lot of problem happens. Now how do we do this? So we basically do alt in the HTML, right? And in Android, we use something called content description. And then we add the string. When we are doing something for HTML, it is like you have to do it in the element specific. You have image, you have to do it. For AHRIF, you are writing title, which is an alternate text and so on. But for Android, it's more like you have to write Android, colon, content description and you have to write it for all the things like image or whatever you want. How do I do it in iOS? In the interface builder itself, I have something called accessibility. When I click and enable this thing, then it gives me label hints and triads where I can write what label, what triad and all. So I will explain you what exactly this is. Label is basically your alternate text. What do you want? And the triad is basically, is it a button? Is it an image? What is it? Right? And hint is basically, hint is optional. It's not mandatory. Hint is basically used to tell like, okay, this is a button. It goes back or something like that. This is an example which I gave. This is a video player, which is a combination of multiple images and so on. So the label here, if you see for the pause and play, the triad is button. And the same thing if you go on the right hand side, I have a label which is show more and the triad is button again. So this is how we define it in iOS. The guideline here is, localize the text, add information which is contextual. So if this is a button, what button it is and what it is trying to do, you have to mention that just because you know, I've seen people doing this, they actually link this thing to search engine optimization and do a lot of keyword stuffing. I've seen that, so don't do that because that is not accessibility. You're trying to use accessibility for search engine optimization. Okay, now second thing is don't rely on colors alone to convey meaning. I'm sure everyone is able to see this image. What do you understand by this green and red? Can you see? What is that? In that four options, you are asking the user to use the last option. Okay, so what do you understand with these colors, the red and green? Red is danger, green is okay. Okay, this looks like a button to you. Exactly, the text is not visible first of all and this looks more like a button. When I first opened this application, I was trying to click and see like okay, what will happen? But that is a static text. So the thing is, why shouldn't we rely on color alone? We saw live example, danger, right? Not everyone perceives the color properly. Everyone have their own way of understanding the colors. This again has some cultural differences also, which is included. So definitely we have to take care of this thing. This helps the blind people and color blind people who can partially or cannot perceive color at all. And then it helps people who, I mean some of the mobile devices, they have limited color palettes and then some of the screen readers, they have limited color palettes and all. So for them also it is useful because they won't be able to completely depend on colors. And then when you go out, like are you able to see your device properly? Because I find a lot of difficulty, you know, when I am trying to access my mobile outside, I have to put my hand like this and then see like okay, I have to give it some shade. So that again is a kind of disability, right? Why is it happening? Because of the poor color combinations which we have. So fortunately, unfortunately, I use Jomato too. Yeah, so the thing is use blocks of color rather than vague outlines and shades. The contrast, the background and foreground contrast should be 4.5 is to 1, 7 is to 1. So we have couple of online checking tools which we can use and see how better our application is contrasting the colors and all. We can do that. But before even getting into like what 4.5 is to 1 or A is, let me tell you the contrast is very important not only for disabled people, but also for people who can see properly. So now, you have this 4.5 is to 1 which compensates for people who have low visual acuity and then lot of contrast sensitivity. These are also kind of, you know, accessibility issues. And you have 7 is to 1 for people with vision loss or 2080 kind of things. Background and background. Yeah, the contrast is basically background and foreground. So background like if it is 4.1, the foreground should be 7 or something. This is the minimum requirement. And how do you measure these numbers? So you have online tools. So basically all these colors are RGB values, right? You have hash, CCC, hash, FFF and so on. So there are online tools, the contrast checker tools available online. So where you can put both the images, both the color RGB values and then you can check. So it will give you like, okay, with this combination. So example, when I checked this image, the black and red and white and red, when I checked in the color tool, it was giving me 21.7 or something which is the highest contrast, which is the best contrast which we have. So you can check like, okay, this is the background color, this is the foreground color. That is how we check it. Yeah. And foreground per se, but also maybe in a button. The button has a background and the text has a border. Yeah. So it's contrast for everything. It's multi-level. Yeah. For all the interface things, it works. Yeah. Excuse me. Yeah. I have a question regarding for different mobiles, the screens quality will be different. So we are measuring this contrast ratio in the sense that it is how it will be perceived by the graphics processor, right? But how you see it is different. For instance, some screens may be having a good contrast ratio, so it may be showing like that. Yeah. So even if you match the 4.5 is to 1 ratio, some screens may not be showing it like that, right? So that is the reason this has been tested and for a mobile device, minimum 4.5 is to 1 is what works for any mobile for the contrast. So that is what the W3C actually suggests. So they have tested it like, okay, what is the contrast which works for a mobile? Yeah. For instance, yellow is normally considered a brighter color than say a red or a blue. But the RGB value is not very different. It's just F on one side or one column versus the other. So does this contrast checking tools also look at human perception of colors? No. It is just about the RGB values. Yeah. That's it. Wouldn't that be a bit of a limitation? Wouldn't that be a bit of a limitation? For instance, blue at the maximum is still very, very low contrast to black compared to say yellow. So basically how contrast works. So there is something called hue. There is something called, you know, values, right? So what is hue? Hue is color of color. So you have red, green, blue. You have all these things. These are hues. You have values which is like basically there can be different shades of red. There can be different shades of blue and all. So when value, one value is combined with another, that is when you get the best combination. So hues may not work always. So there are different things. That is how you can check whether it is working or not. The color checker basically is to check like what is the contrast which you are using and it will give you a person. So it's more like, you know, when you're checking for accessibility. So it will tell you, okay, these are the accessibility problem in your site, right? I have a question here. Here. Back. Okay. We recently built an application so, but we didn't give a serious thought about accessibility. So towards the end, we thought, okay, that's important. So we did this color contrast checking also. So what we found out was we used some contrasting colors before. Visual designer did the design. It was basically very pleasing and all. But finally when we came to the accessibility section or the process in which we made the application accessible, we had to actually compromise on some colors. So that again, we had to consult our visual designer. So the only thing that we should start right from the scratch. I mean, at least when we start building the layouts, when the visual designer does the mock-up, wouldn't that be nice when actually these things is also actually imported into the visual designer so that he can actually think. I know that it's a bit limiting from a creativity point of view, but what are your thoughts on that? Yeah, definitely, definitely. So that is how it is. When you are designing something, accessibility should be taken in consideration right from the beginning. So visual designer should be aware of all these, you know, contrast. Because I've seen, I'm a designer basically. So I know how, you know, we design things, right? So definitely that is important. And then the color guidelines basically are make sure you have a proper contrast. And also make sure like whatever you're trying to show on your mobile application with color is also available without colors. The next is minimize text input in the interface. Do we need it? Yes, no? Text input. Text input. It can be anything. Text also. It adds to text input, text, text. I'm writing something, Facebook. I'm typing my message. That is also a kind of input, right? Agree, disagree. How many people face problem with this typing? Very few people. Wow. I'll give you an example. I mean, recent incident which happened with me two days back. Blast happened in Hyderabad. So I actually wanted to send a message on Facebook and I wrote, I was traveling actually. I was in the car and I was writing like, okay, hope all my Hyderabad friends are safe. It's so disheartening to see such incidents happening in India. Right? And then I posted it. But due to, you know, the jerks, travel, whatever, I don't know what message went because I didn't actually bother to check. The way, you know, we don't see the URLs on the top, the same way I just posted it. After some time, I got the comment on that, like one word can make you sound evil. So I thought, what is my friend trying to say? And then I re-read my message and it read like, hope all my Hyderabad friends are safe. It's happening to see how, you know, these blasts are happening in India. Why this happened? You know, because of these typing mistakes which we do and we don't realize most of the time. So that is the reason, lot of people make mistake, lot of people face problem when they are trying to input something, a form or something. So that is the reason we should have minimum text. Who does it help? It helps people who have motor disabilities, you know, paralysis or fracture or anything. I can't use both my hands. So I am, you know, dependent on only one hand. So these kind of things. It also helps out of the context, outdoor context also. Traveling, your one hand is busy, right? And people will not make mistakes like I did. And how do we achieve this? We can have alternate means to enter text. We can have voice, recording and then, you know, converting it to text for us if it is possible. Because blind, they can't write. They might face problem. So these kind of things we can take care of. You know, pre-selected, drop-downs and values and all. The next is using the semantic markup. So this is very important. Even for accessibility and not for accessibility, also you should have a semantic code. Because it helps other developers also when they are working on your code. They won't find difficulties. But why do we need this? Why? Semantics of the pages is maintained. Like navigation should be in Aside or NavTags. And other links should be in Aside. Header should be in Header. Footer should be in Footer. So basically, it helps the screen readers. Assistive technologies and disabled help them as well. So it's like, you know, if it is invalid, it may not work properly in some of the screen readers or some of the devices. And from the functional disability point of view, assistive technologies cannot handle invalid markups. So like, you know, if your markup is not valid, if you haven't added doc types, not HTML5, but the previous ones. So I may go into quirk mode in some of the cases. The same thing holds true for assistive technologies. So you should have a semantic code. And then, you know, it is easier for them to navigate the blind users or people who are dependent on assistive technologies to navigate from one part to the other when you have a semantic code. Then how do we achieve that? This is an example. We have a form, a well-structured form which is having input, which is also having label for, which is a very important part of accessibility. Android, we basically use something called accessibility node provider. So this is the entire, you know, thing how we write a semantic code in Android. Yeah. And then we have, basically, you know, have a concise page, content and size. So I'll give you an example. When I was working for one of the biggest airlines, I was developing the mobile application. So they were actually, you know, arguing like, they have a huge set of, you know, terms and conditions which they wanted to put in mobile application. Right? They wanted to create a native mobile application and they wanted to put the terms and conditions. So I argued with them. I said, like, what do you want that? No one is going to read it on a mobile device. And they were like, no, this is a policy. We have to do it. We can't do it anyway. So then it became very difficult for me to convince them. And finally I had to put because designers have limited choice. They can just suggest. But at the end, you know, what client tells, that is what we have to do. So later on what happened, people started facing a lot of problems. They were not able to read properly. And, you know, scrolling, scrolling, scrolling. So they saw a lot of drop-off rate for the mobile applications. The reason is because when you have so much of scrolling, it's very difficult for people to read it. It's very, you are almost lost and out of the context. So that is the reason, have limited context or make it look visibly, you know, good. So this also helps for accessibility. For the functional disabilities, people who have, you know, vision problem or screen magnifier, who use a screen magnifier, they can see only small parts at a time. So they don't, you know, you won't, like the way we read something, a book or something. So we are engaged. We can't be so much engaged when we are using that on a mobile. Who does it help? Functional, I have told this, right? Okay, yeah. Now how do we achieve? Avoid scrolling if possible. Have one-way scrolling. Don't have, you know, horizontal and vertical scrolling. And then create large clickable areas if possible, rather than having a lot of scrolling. If you have a lot of content, structure it in a proper way, or they can read it properly. Now do not insert functions that can only be managed via gestures. Always add a button or link. How many of you agree with this? Okay, great. Very few people, but why? If you actually look at the example of Google Maps on Android, they have introduced a single finger gesture for zooming. You know, you double tap and then push your finger up or down the screen to zoom, which does not require two fingers anymore. And that means you can do it with one, your phone in one hand. You don't need the other hand to use it. I think that's a great example of how to solve this problem. Earlier they had the zoom buttons. And what they've done now is figured out how to do it with a single finger. That is one thing. And most of the times, I've realized this thing. Some of the times we don't even know what gestures to use. Like, it's more of a guesswork. When I first started using my note, I wasn't sure, like, okay, if I pinch it will work, or what, tapping is one thing which I knew. But half of the things was more experimental. I started exploring and that is when I got. So they're not intuitive. You don't know what exactly it is. Right? They're not intuitive. And most of the, like, users, they don't recognize the gestures. And plus blind users, they can't see these gestures or use these gestures. They are more dependent on screen readers. Yeah. Now, who does it help? Sorry. Blind users, people with temporary disabilities, like, if I have fracture, I'm not able to use both my hands. Some of the gestures require both your hands, kind of things. And then, for the functional, it is, for the situational, it is like, you know, the context can be anything, indoor or outdoor, where you're not, you're busy and you won't be able to use both your hands or some of the gestures you won't be able to understand. Okay? So, it is having buttons and text as an alternative and don't rely completely on gestures. Now, the last thing is, ensure that it is possible to zoom the interface. How many people agree with this? You should have the possibility of zooming the interface. Okay? Yeah? Very few. Yeah, so that is a mandate, right? You should do it. I may be able to see things properly. What about the third person? Right? So, there should be a possibility of zooming things. So, you know, my grandfather was playing Sudoku on my iPad. He's like, 87 years old. He also read a lot of articles on my iPad. So, that's what I could relate to when you asked this question and I was probably the first person to raise the hand. Yeah, definitely. It has so many people. Not only like people who are aged or someone, but, you know, also people like, right? Who have temporary disabilities or who have side problems. So, now, how can we do that in HTML? We have something called Viewport and then you have to give the initial values minimum maximum. That is how you can do. But some of the browsers, they don't support this. So, that again is a challenge. So, that is the reason you should also have, you know, font size kind of options like we do for HTML and all. We have A plus A plus plus and so on. So, those kind of options is what we have to work on. Now, the only conclusion I want to draw with the entire guidelines principles and my talk is mobile is for everyone. So, think about it when you are designing your next application. So, there are couple of guidelines if you want to see. So, the mobile will like best practices, the accessibility guidelines and all. This is basically for the native mobile web applications and then we have something for the native applications the platform specific guidelines which we have. You can have look and see what exactly it is. So, I am ready for the questions. I have one here. Yeah. When you talk about the contrast ratio can we compromise for the supplementary text? Yeah. Alternate text like supplementary text and all we can exclude. There are couple of exclusions not all. For examples like the gray text on the white. Usually even for the HTML5 components where we have the placeholder text, icons coming up on the white background which has a the gray thing is like gray color is always has a less contrast against the white background. So, I would say if your content is very much important have the greatest contrast, but some of the things the text which feel is not so important and could be you know skipped by the disabled also in that case have a minimal contrast. But just try to follow the 4 is to 4.5 is to 1 contrast minimum. Yeah. Yeah. I have a question here. So, my question is on the accessibility part of your talk. So, see most of the companies at the time of the start or take the case of the start-ups they are already involved in so many issues. It's hard to include this at the decision-making level, but by the time you realize that you should consider this say maybe one or two years down the line, the cost rises tremendously. So, how do you create a fine balance? See the main problem here is when I was talking about the decision-making how do you decide like I have to design this application. So, when you are designing you already you know decided like I have to use HTML or I have to use CSS sorry or I have to use Java or whatever you have already decided that thing. So, what makes it so difficult for you to include accessibility? Accessibility is not something out of the blue which you are doing. Accessibility is basically you are trying to make your code more semantic, trying to add the labels and these kind of stuffs which makes it more accessible, right? So, talking about the colors, obviously you are going to design. So, when you are designing think about the color. Right? Yeah. Oh ma'am, I have a question. Yeah. So, generally on your web websites you have your alt text when the mouse hovers on say an image or something. How does that generally work on touch screen because we do not have that option of hovering over any element. Yeah. So, basically in touch screens you do not have these alt text. I mean this is basically I will tell you what exactly alt text is. Alt is basically alternate text. So, alternate text is not basically like when I hover over the image then I should see a tool tip. That is not what alt text is. Alt text is basically what if you have a low bandwidth and you are not able to load the image. So, till the time your image loads you should see something rather than a blank space or you know something. So, that is the reason you have alternate text which tells you like this is the logo. Right? The same way goes the same thing happens for the screen readers also and for the mobiles also. So, if you do not have alt text it will show you blank space or you know a place holder kind of thing but it will not tell you what exactly this image was which you may be curious for. That is why we use alt text. Yeah. So, this is not a question. This is a follow up comment to what Kiran asked like there is absolute contrast say white and black. Absolute contrasting text but then when you are reading on white background absolute black text would hurt your eyes. Subjective it might hurt people's eyes it does not make for a very pleasant experience. So, what I see on a lot of websites what they do is instead of keeping it absolute black they use a tone of dark gray or something which is still acceptable contrast but not doesn't hurt your eyes. Similarly, if you reverse white text on black contrast is perfect but it does not make for a very pleasant reading experience and I am sure you have heard about a site called Contrast Rebellion. No, I haven't. Okay. You should check that out. They make a case against illegible text just because some trends need to be followed where text is like just a little darker version of the background. So, they make a very big case about it that the text on the internet is supposed to be red. It's not just that. It's not supposed to be looked at. That happens a lot in mockups. It looks nice to have low contrast in your mockup because then it doesn't hurt your eyes with distracting details but the details are the text that you are reading it for. So, this is one more question. I hope you got your name right. So, one of the things I noticed at least older browsers is that if you do not use anything apart from absolute white and absolute black you lose sub-pixel hinting because most rendering engines were not capable of sub-pixel hinting in anything apart from black and white. So, black color text on white background or white text on black background. I think that's been fixed in recent times but I don't know how universal that fixes. Okay. So, if you use say hash 2 to 2 which is a very common in bootstrap does it and so do a bunch of others and if you look at HTML5 boilerplate they use hash 444 as the default text. Now, that thing disables sub-pixel hinting and you get this grayscale hinting in some browsers. So, I don't know if any of you here are aware of what is the status of rendering text in browsers today. Do they do sub-pixel hinting even with color text? Hi. Yeah. Is it possible to make native apps zoomable? Native apps? Zoomable. Zoomable, yeah. See, native application it is very much easy because you are using the devices in built capabilities. So, you don't have to add some extra effort to do it because native applications already have these features. You don't have to do some extra coding or something for that. The only challenge is with the web applications. I have a question here. Yeah. Okay. As a team, we are working on an enterprise web application which caters users of all categories and it is a crucial web application as it comes in the enterprise. And we have a search feature. Since we need to use a minimal amount of components, so we are actually neglecting the search button. Instead, while pressing enter it is by default everybody goes types of text and it has a placeholder text, types of text and press enter it searches. But accessibility says that you need to have a button for that. So, what do you say of both this? How would you enter that in a mobile? Yeah. That is the challenge, right? So, you should have some alternate way of doing it. So, button. So, that is the reason button is required, right? See, design looks good and all these fancy things. But is it accessible? Are people able to use it? Not only, I mean, disabled, talk about any functional or situational kind of, you know, problems which may arise. Then what? So, please send questions offline. Sure. So, let us take a lunch break and then come back by 2.15 shortly.