Creating an Accessible Web Together in 5 Simple Steps

Hello, everyone. Thank you for coming to my talk and staying here, actually. So we all actually care a lot about building performant web applications and creating an amazing user experience. We put a lot of effort in making fast websites. But what use is a fast website if people can't use it? Accessibility is often left as an afterthought in a software development cycle. When it is time to ship, we actually do a quick accessibility test and find out that our app is not accessible and put some hacky code in and make sure that it's accessible enough and then ship it. And sometimes it kind of ends up looking like this. We make sure that it's visually pleasing and aesthetic, but the experience itself looks pretty hacky. In my talk, I will talk about five simple things that you can keep in mind while you're doing development so that you can avoid a situation like this. My name is Shruti Kapoor. I am a lead member of technical staff at Slack. And over the last few months, I've been working on building accessible user experiences in huddles at Slack. I would be lying if I said I was an expert in accessibility. Don't ask me any hard questions. When I built my personal site, I made it look visually pleasing. It looked beautiful. I used Tailwind. Everything looked great. And when I did an accessibility test, I found out that most of my site wasn't accessible and people weren't able to do the things that they wanted to do. Like, for example, read the blogs. And so through the means of this talk, I want to share some tips and tricks I learned and some things I now keep in mind that you can do while developing your web applications so that you don't end up in a situation where it's almost time to ship and your app is not accessible. This is a long journey, actually. Building accessible web apps is a lot to take and it's a big undertaking. My journey here is not done. Through this talk, I want to share some things. But this journey continues afterwards as well. I'll continue to share my learnings on accessibility through blog posts, and if you're interested in following, then you can find it on anywhere on Twitter here. Or on my not accessible website for now. And if you've been following me on Twitter, you already know that I'm a big DevJoke fan. So you know what's coming up. I'm going to ask you a DevJoke question, and you can just yell the answer out loud. So what did the process say after working in an infinite loop all day? I need a break. You're right. Yes. Okay. Because we're short on time, I'll only do one DevJoke, but if you want more DevJokes, you can find them on Twitter. So here's what we're going to talk about today. We'll look at the basic principle of accessibility and the guidelines of accessibility. We'll look at how to test if your current app is accessible, and we'll have a checklist of things. We'll debug a web app and find out what the problems are and where you can look for solutions. And then we'll look at some tools that can automate this work for you so you don't have to do it all manually. Finally, we'll look at a web app that has taken accessibility seriously and goes above and beyond. So first, let's talk about accessibility. By the way, all the slides are available already online, and if you're interested, here's a QR code. I've also tweeted the link out right now, and you can find it on Twitter if you're interested. Everybody has the QR code, and moving on. So what is accessibility? Now I want you to take a minute to think about the last website you built or one of your favorite websites. Are you confident that anyone in the world can use that website? Are you confident that people who have limitations or are using assistive technologies can use that website the same way an able-bodied person can? Are you confident that all parts of your website are easily accessible? Accessibility is enabling everyone to use your site and to perform the critical actions easily. And accessibility benefits everybody. You may have seen examples of accessibility in your life. For example, when you're coding and your trackpad dies and you need to connect or you need to log in. So you just use keyboard to access the login screen. We've also seen accessibility features benefiting us in real life as well. For example, when you have a lot of suitcases in hand and you need to go up a flight of stairs and there's no ramp. Or when you need to open the door and you have your both your hands are full. Or in the night when you need to watch YouTube and your partner is sleeping so you turn on closed captions. So accessibility benefits everybody. Not just those with limitations. But building accessible experiences provides a great experience for everybody who's using them. What does accessibility look like in digital or in web? In the web, when a person is using the web, they may use different assistive technologies to browse through your website. For example, somebody may be using a screen reader to read out the text on your site. And they may be using screen magnifiers to zoom your screen to even 20 times to see the screen itself. People who have motor disabilities may be using different technologies. For example, keyboard or selection switches. Or maybe using a head tracker to find out where the cursor or to point to cursor on the page itself. So in order to make sure we are building for everybody in mind, we need to consider the different assistive technologies people are using. You can actually access most of these technologies on your Mac itself by browsing to the accessibility shortcuts menu in Mac. There are more people using these accessibility tools than you think. According to World Health Organization, 15% of the population has some sort of disability and may need to use an assistive technology. In the U.S., one in four U.S. citizens has a disability. And it's not just a feature. It's also a legal requirement for a web app to be accessible. In the U.K., according to Equality Act 2010, your website needs to be WCAG 2.1 AA accessible. So let's look at what that means. This actually specifies guidelines that your website needs to be perceivable, operable, understandable, and robust. What does perceivable mean? It means that the content presented on the screen should be understood by people who are using assistive technologies. An example of this could be you have images on the page and you need to provide all text for it. Or if you have video on the page or audio on the page, you need to provide closed captioning so people can read them. This is also the principle that specifies that color should not be the only way of displaying information. The next is operable, which basically means that websites should be able to be operated by not just mouse, but by other assistive technologies as well. For example, a screen reader. For example, a keyboard. It specifies that keyboard focus should not get trapped and the user should always have understanding of where the keyboard focus is on the web app. The next one is understandable, which basically means that the text presented on the screen should be understandable by screen readers. And it ensures that people who are using assistive technologies can use the learnings that they have from one website to navigate to your website. For example, you may have seen skip to main content present on most websites. People who are using assistive technologies have muscle memory built in because they've been using their technologies for a while. And if you move the skip to main content from that part to some other part, it becomes very hard for people to understand where that is and access it. So this principle basically guidelines that things like this should be on the same part of the website. And finally, robust, which basically means that assistive technologies should be able to parse your code. And this is why using semantic HTML is very important. And your code should work in every browser. There are different types of accessibility needs we have to keep in mind. A few of them are motor disability, which is when a person has problem� which is when a person has limitation of muscular control and inability to use maybe a mouse or a trackpad and they may have slow response time. Cognitive is when a person has learning disability or may have ADHD. And it may be hard for them to remember large amounts of information on the screen. Visual includes things like blindness or low vision or color blindness. And auditory includes things like deafness or hard of hearing. So that's accessibility 101. And now how can we make sure that our app is accessible? So while learning how to make things accessible, I came up with, like, five main things that we can keep in mind. And they are as follows. Semantic HTML. Tab index. ARIA tags. Roll. Finally, keyboard navigation and screen reader. And to make that easier for us to remember, just think of Stark. Or this guy. Or if you're a Game of Thrones fan still, these guys. So again, Stark is semantic HTML, tab index, ARIA tags, roll, keyboard navigation, and screen reader. So let's talk about the first one, which is semantic HTML. I think we all know what semantic HTML is, so I'm going to jump to the tips. Which is a big tip that everybody says is use buttons for actions instead of adding it to div. So basically instead of adding, like, an on click handler to a div, you should be using the semantic HTML version of it, which is button. And whenever you have an anchor tag, make sure it has an href. Whenever you use images, make sure it has all tags. And don't use CSS or font formatting only to use headings. And as much as possible, use the native semantic HTML elements to show content on your screen. But let's take a minute to think about what is the problem if you use div instead of a button. The problem is that when a screen reader encounters div and it has an on click handler, the screen reader doesn't understand that it should operate like a button. So if it encounters a div with an on click handler or just a div, it will announce it as roll or it will announce it as group. So the person using the screen reader has no idea that I need to be clicking on it. So it could happen that they would completely overlook your button and go past that page. So that's why you need to have button instead of div on clicks. Now what's the problem with not using correct heading tags and just adding formatting? The problem is that when a screen reader encounters a heading, it actually announces heading in the text. So if you just use font formatting, the user has no idea that this is a heading and needs to be paid attention to. Another great thing about using semantic HTML is that you get free accessibility out of the box. For example, things like let's say you're using select, you can use space bar to select an item. Or if you have a button, you can use the enter key to select or to click on the button. So you don't have to actually build these things. You don't have to make accessible. You don't have to make them accessible. These are already given to you out of the box. Another great example is using a slider. You can use the space keys to move the slider around. So in summary, use semantic HTML. All right. The next is tab index. So if you're not familiar with tab index, tab index is actually used to set focus on certain elements on the page. So you can tell keyboard navigation, you can basically specify where keyboard should be navigating to or where it should be setting focus to. There's a really cool tool in Firefox that can help to find out or debug tab index. And I'll show that in a minute. It looks kind of like this. So you see the little black icons zoomed in here? It tells you what the tab order of each element is, if it's interactive and focusable. A quick tip about tab index is to either use zero, which is for elements that you want to be focused by default, like divs, if they need to be focused, or minus one, if you want to programmatically focus an element and target it with JavaScript. So minus one gets skipped when you are using it by default, but you can use it with JavaScript to focus on it programmatically. An important thing to remember in mind is to not use a tab index greater than zero because it confuses screen readers. The next one is ARIA, and these are ARIA attributes. There's a bunch of them, and I only listed a few of them, which I've been using very commonly. ARIA attributes actually give extra information to assistive technologies to make them understand what's going on on the page. For example, when you click on a toggle button and you have the ARIA check set to on, it can help announce things. So let's say you have a mic and you set the ARIA check to true, it can announce the state of that mic. So you can say mic on or mic off. And it helps screen readers. R stands for role. There's lots of roles out there, but be careful, though. If you can use a native HTML element, use that instead of using a role. The problem of role is also that you have to actually build accessibility on top of it. So if you're using a div and adding a role, you're actually not using button. Button gives you free accessibility. So use native elements as much as possible instead of slapping a role on top of it. And finally, keyboard navigation and screen reader. So test your site with keyboard navigation. Keyboard navigation basically means using your keyboard only to navigate your site instead of using the trackpad or the mouse. So a quick tip is to unplug your mouse or trackpad and see if you can access every part of your app through keyboard navigation. And check if your focus outline also stays visible and you know where you are on your web page. So if you want to remember those acronyms, again, remember STARK. And here's a quick checklist of things you can do before you release your app. So remember STARK, semantic HTML, tab index, attributes, role, and keyboard navigation. Make sure that there are no keyboard traps and your focus always stays visible on your site. For anything that is an interactive element, provide an audio attribute, an audio role, and provide explicit labels on what that element is. So, for example, a video. All relevant images should be using alt attribute. If you have an image that you do not want to be pronounced, for example, it's a tick icon or it's just a presentation element, you can use the role equals presentation to skip that. And make sure that all your multimedia is tagged. You have closed captioning available for anything that is auditory. Text has sufficient color contrast. And make sure you run automation tests so you can catch anything that you may have skipped. All right. So now let's look at a few tools that are available. There's a bunch of tools that are available out there that can do most of this manual stuff for you and provide a list of errors that your app may be having. There's browser extension. Axe and Wave are some very popular ones. There's a lot of accessibility tools built into the browsers itself. Firefox and Chrome have pretty good accessibility tools. We'll demo that in a bit. There's also build tools that you can use within your code itself. And then finally there's CI tools that can help you show errors when you have published your code. So, before you release your feature or before you finish� before you create your PR, make sure you test accessibility. Use keyboard navigation to make sure that your content is accessible. Remember Stark. And check your app. Make sure it's keyboard navigable. Use screen reader and use the automation tools to find out errors that you may have skipped. And finally, make sure that you're testing your app with real users. Code cannot catch as many errors. Code may even tell you that your app is 100% okay. But if a user cannot understand your app still, it's no point. So make sure you do user testing with real users. All right. So now we're going to look at a quick demo of a site that is not so accessible and find out the problems that it has and see if we can debug it. Going to mirror my screen. Perfect. Okay. So I'll put myself on the spot. I built the site. And if you look at it right now, it looks visually okay. My design skills are okay. If you hover on an item, you can see that you can kind of tell what item should be hovered. When you click on it, it will open as well. And there are some links and there are some videos at the bottom. Now let's see what a person using an assistive technology would be seeing. So I'm going to turn voiceover on. And I apologize for the noise. Okay. So watch for what things the screen reader focuses on and what things it's skipping. So it's focusing on read blogs. And you can kind of see the outline as well. It's at the top of my blog post. That's cool. And the next thing it focuses is browse more talks. So it actually totally skipped that section. So let's see what's going on. And this is a really bad experience for somebody using screen reader because they did not see any blog post I wrote. So I'm going to close voiceover and see what's going on. Okay. So I've got Chrome open here. And I also have Firefox open here because I want to show you both the tools. So what I'm going to do is open accessibility properties in Firefox and open accessibility properties in Chrome. So you can find them here. Make sure it's zoomed in. Okay. The first thing we'll look at is the accessibility tree. And this is the tree that a screen reader would be using to understand what's going on in the page. And you can find that right here. Enable full page accessibility tree in Chrome. So when you click that, it gives you a popup to reload DevTools. We'll do that. Okay. I reloaded. And you see a little man here. And that's how you can access the accessibility tree. This looks a little different than the DOM tree. But basically the idea here is like it will tell you all the things that a screen reader would be seeing. So you may be able to see things like focusable true. So that means I can see this and I can focus on it. And then things over here that are next being focused. We'll get back to this in a bit. So in Firefox, this is actually even better. In Firefox, it has these issues. It has this testing thing already built in. So what I can do is I can click on check for issues. And I found out that I was having keyboard issues. So I'm going to click on keyboard. And now I see that it is giving me a few errors here. Let me see if I can zoom that in. Put that down. So you see all of these are problems that are that is that my content is currently having. I'm trying to debug this one. So I'm going to open this one and see what's going on. So I see that there's a keyboard issue here. Let's see what's the problem. It says interactive elements must be focusable. And to understand what that means, I'm going to open this link. But basically, it says that you need to have a tab index on your content. Part of start. Okay. So to do that, let's see what my content even looks like. So I'm going to inspect this. So if you see here, this is my box. I see that there is a div here. Now our suggestion was to add a tab index. So you may be tempted to add tab index to this box itself. But remember, tab index should only be added to interactive elements. The problem with adding a tab index to div is that div is actually not an interactive element. An interactive element is either a button or a link. So instead of adding a tab index to div, go down the tree and see what is our next interactive element. So if I look at the tree, it's an anchor tag here. Now, let's see what the problem is. So I've got a class here. But I don't have any href. And so that's the problem. So with the help of this accessibility tree and a quick test, I can find out what the problem is. If I add href here, it will be able to tab onto it, no problem. All right. There is another really cool thing here which I want to show you. And that is a tabbing order, if I can find it. There. So it has a tabbing order here. And it takes a while to actually load up. But basically what it does is it will show me which element is being tabbed onto in what sequence. So it puts like a 1, 2, and like 4, 5 here based on what the tabbing order of each element is. And so that's super handy in debugging whenever you want to do whenever you want to debug, suppose your element is not being tabbed onto correctly. So that's tabbing order. Let me make sure I've taken all of these. Cool. Okay. So that's how you can find problems with your web apps and use the browser accessibility tools to debug them. Now I'm going to switch back. This place. Stop. And then this. Shoot. The other one. Okay. Going back to the presentation. And play. Sweet. Okay. So some things that we looked at was fixing broken anchor tags. One thing that I don't know if you noticed was that when we were focusing, our outlines were visible because of the screen reader. So that's something that we need to make sure when we are using keyboard navigation that our outlines are always visible. Now there are apps that have gone to making their web app accessible by just adding tab index everywhere. But you can do a little bit better than that. There are a few apps that provide skip to main content and that's a great first step. But you can do more than that. You can provide keyboard shortcuts for things that are commonly used by a user. And now I'm going to show you an application that has gone above and beyond in ensuring an accessible user experience. Okay. So let me play this video. Oh. Doesn't work very well. Okay. I am going to go back to main screen. And mirror them. Okay. So if you look at this video, I am going to use keyboard navigation to actually tap through all of these items. And you'll notice that it detects that I am using keyboard and it shows me a popup saying if you're using keyboard, then these are some shortcuts available. And that was really cool. I was very amazed to see this. But basically what it's telling me is that you can use this command key or command shortcut to actually focus in a certain section. We're going to look at how that works. So basically what it does is when I use command control left arrow or right arrow to move focus between sections, it will stick the focus in that section itself. So right now I'm going to use command control focus. And you see now it's in the left section. And now if I keep tabbing, it won't go to the messages section. It will just keep the focus in that section. And that helps people who have problems focusing on a certain section, especially if there's a lot of content on the page. And you can think of Slack as an app where there's tons of messages. So when you keep tabbing onto a message, it may be very hard to navigate to that message. So things like these shortcuts actually help people a lot in ensuring that the focus stays in a certain area instead of having to tab over every single interactive element on the page. And so now I can use my keyboard arrow keys to just stay in that one focus section. I can also use more than just tab index and I can also more than just tab keys and I can use arrow keys to go between other sections of the app. So for example, you may like in Slack, one of the biggest things is writing a message. You write a message. And now let's say that I made a mistake and I want to edit it. So now you can use your shortcut key, which is the E key in Slack, to go up in a message and edit it. So that's how an app has been thinking about accessibility seriously and not just using tab keys to actually make everything tabable, but also thinking about the most common things a user may be doing and making that experience better for a user. All right. So because this is getting harder, I'm just going to present from here. Cool. Okay. So in the talk today, we looked at the guidelines of accessibility, principles of accessibility, the different types of disabilities people may have. We talked about Stark, semantic HTML, tab index, attributes, roles, and K for? Keyboard navigation. These are some simple things you can keep in mind to build your next web applications while you're building the web applications so that once you're done, you don't have to go back and refactor and spend a lot of time undoing the work you did and redoing all of that work. So I hope this gave you a good indication of things that you can keep in mind. And if you're interested in following the journey forward, I'll be sending a blog post of everything I talked about today and everything in the future. And if you want, you can sign it up here. We can't leave before one final dev joke. Who won the debate for the best variable? Say that again. I won. Thank you so much, everybody. You've been great. Thank you so much, Rudi. Would you like to take a seat? I promise not to hold you too long or ask too difficult questions, mainly because we're a little bit over time and people want their coffee. But let's do the top rated question here, which I think is a really good question and I don't know the answer to this. With alt attributes or ARIA labels, is there such a thing as too much information? How do you decide what to actually put in? Oh, that's a great question. So I think one of the things and one of the most common mistakes people may make is especially if you're using semantic HTML, like buttons, you may add a role to it. You could do that. Technically, it's not breaking anything, but it's just useless work to do. You don't need to do that if you're using semantic HTML. So, yeah. Great. That was so quick. Let's do another one. There are many accessibility testing tools available. In your opinion, what's the best phase to test your code? Is it on the component level or is it on the end-to-end when it comes to accessibility? Oh, great question. I think both of them are really important. But at the end of the day, I think once your code lands in the hands of the users, it's very important to do accessibility testing there. You can make sure you have semantic HTML, your code looks great, but if it's not usable for the user and they can't access the information, I think it's worth for nothing. That's very true. And in my personal practice, I only do end-to-end testing for accessibility because I usually use accessible component libraries that do their own testing on the primitive level. Awesome. Protip, use Radix. All right. And then final question. How would we pitch accessible implementation to stakeholders? Is there some sort of argumentation that tends to work well? Oh, great question again. One thing that you can tell them that it's a legal requirement, so if they don't take care of it, they're going to have to pay for it heavily. Another thing to remember is that I don't know if you have a use case experience from your own experience. If you have a use case from your own experience. But in my experience, I've noticed that we build web applications and then finally we realize that it's not accessible. We go back and refactor the entire component. And that happened to me as well and it wasted like a month of my time. So it's better to start accessibility from the get-go and design level itself instead of coming back to it and refactoring it. Wise words. And that's all we have time for. Thank you so much, Rudi, for your talk and the jokes. Thank you so much. I hope to hear some more later.