 All right. Good afternoon, everybody. I think we're ready to go. Everybody's finished checking the email, Twitter, and so thanks for coming out. We're really excited to be able to talk to you guys about improving your new engagement and some of the tips and tips that we can help you guys. I'm Katherine McNally, and this is Dave Espire from Phase 2. I just kind of want to get out there that we showed up individually this morning, wearing pretty much the exact same thing. And we were deposed to wear Phase 2 t-shirts, but we were like, no, we got to roll with it. So they're just not intentional. So thanks again. We've got a lot to cover. We're really excited. And as I mentioned, I'm Katherine. I lost my hearing to meningitis when I was eight months old. And I was one of the first recipients of the cochlear implant, which is a technological implantable device. So I've been a technology pioneer my whole life. So it's been really cool. So I've grown up and I've lived computers, and I'm really excited to talk about how we can have a technology to bridge communities and equal the playing field for everybody. Hi, I'm David Spire. My background in accessibility started when I was 16 years old, when I volunteered to build a computer lab at a retirement home and teach the people living there how to use them and got an immediate and startling crash course on accessibility. We both work for Phase 2. We're a digital agency. We design, develop, and do a whole bunch of awesome things for various web properties. We're hiring. We have a really interesting booth downstairs, so you should definitely come check it out. Let's dive on in. The elderly are going to outnumber those under the age of five by 2020. This is a thing that hasn't happened before in history. So while they aren't making new ones, the baby boomers are the largest segment and the elderly are the fastest growing segment in America at the moment. And this is happening throughout the Western world. They make up 15% of the population. And this is a group that you cannot afford to ignore. Because 68% of baby boomers, and please, folks, come on in. There's plenty of seating up front, if you want. 68% of baby boomers have multiple devices. These are folks over the age of 55, and they're used to using them. As they start to age, they are not like their parents' generation who generally didn't care about use of technology. These are people who are expecting to use technology until they're gone. So don't treat them like you, you know, from a web design standpoint, like the previous elderly generation who genuinely didn't care. So on top of that, you have this group of one in five Americans who have a disability. Now, this map that you're seeing here doesn't mean much for accessibility, but just to give you a frame of reference, this is each state redrawn according to its population. And if we were to go and take a look at the population of people in America with disabilities, it's seven times the population of the state of New York. So this is a large amount of people. One in five Americans have a disability, and half of them need some kind of assistance navigating a website. So that's 10% of the population, essentially. Do you want to ignore 10% of the population? And then on top of that, you have temporary disabilities. A friend of mine went snowboarding, had a very interesting fall, and left the hospital with both of his hands and casts. These things happen. People have strokes, people encounter all sorts of unexpected elements that change the way that they see and hear and interact with the world. So this is not just for some niche group of people. We're talking, when we talk about accessibility, we're talking about everybody. We're talking about the elderly. We're talking about people who have the disabilities that you commonly associate with accessibility. And we're talking about people who are living functional lives without any impairments who suddenly find themselves in need of accessibility. This is truly for everyone. So let's talk a little bit about colorblindness. And if you've ever attended one of our talks, one of the things that we really focus on is reframing disability and helping people find an empathic connection to these problems. So colorblindness affects half a percent of women. Colorblindness is genetic. But it affects approximately 8% of men. So that's an important thing to note. If you operate a website that is targeting men, you're talking about 8% of your audience is colorblind. The cobblest colorblindness simulator is a thing I'm a really big fan of. Because what it does is it allows you to upload images and then simulate most of the different types of colorblindness that are out there and see what your designs look like through the eyes of someone else, literally. So on the left you're going to see a normal image. On the right you're going to see a different type of colorblindness. It's worth noting there are lots of different types of colorblindness. So red week. This is what red blind looks like. Blue blind. And then black and white, which is the stereotypical but incredibly rare colorblindness that most people, I think, think of when people talk about colorblindness. This isn't actually a very common form of it. Let's see if it's going. Okay. So this is the cobblest colorblindness simulator. So you can just upload an image. This is Humanitarian ID, an app that I worked on for about a year. And this is what it's looking like through different types of colorblindness. You can very quickly, easily, and for absolutely no money, upload screenshots of your designs, of your existing websites, and run them through and see what they look like for different types of colorblindness. And what you're looking for is not this mythic perfect brand experience for the colorblind. You're not going to achieve that. But what you are looking for is making sure that you can actually read and see everything that's relevant on the page. So really the great thing about technology is that it can enable independent living. People who have a wheelchair, or who are blind, or who have hair loss, can use technology to get what they need. If you think about somebody who's blind, they can use Alexa at home to call Uber, where they're having to rely on somebody else to drive them somewhere. So they can lever technology to advance to make their data lives easier. One thing that I just kind of want to talk about a very ironic experience, when you're thinking about your website and who you're serving, and who's your audience, and thinking about that, you would be amazed at what kind of sites I encounter in the customer service that I experience. I just want to talk to you about the experience I had a year ago when my cochlear implants broke. And let me tell you, when they break, I can't hear a thing. I can't come to work, I can't talk to my family, I can't talk to my friends, but I can't hear them. So it's a very distressing experience. So I have a little turning map of what was going on when my process was broken. I was in a really low emotional state, like, shoot. I can't function. I can't be productive. My project is broken. So I'm going to go to their company's website and say, hey, they're to contact us for them, good, but I can't call them. So I'm able to go on the website and say, hey, my project is broken. I need a replacement. I can't submit. You know, the response I got was, hey, call us. Really? You are in the business of providing a hearing device. And the response was, get me a call. You clearly do not know your audience. You do not know who you're serving. And it was kind of a bummer moment because I had to call mom. I had to text my mom and be like, mom, keep this for me. I'm 33 years old and I still need help. And that was kind of a bummer and that really negatively impacted me as a person. And it made me feel like I still needed somebody to help me. I couldn't do this alone. I can't adult by myself. But now let's look at the ideal experience and what the ultimate experience could have been. So as we can see, my project is broken and I'm waiting. I'm anxious. So in the response I get is, hey, sorry, it's broken. Here are several ways that you can contact us. You can text, you can need to chat with it on our website. You can also email us. You will get to a replacement, ASAP. Usually they overnight a device. And in the meanwhile, I still need to go to my clinic to literally get my hearing reprogrammed. They put me up to a computer and then I get a new program for my processors. So I had to go to my audiologist's website. Remember, I can't hear anything. Thankfully, Johns Hopkins, who's just down the road, said, hey, use an online booking calendar to book an appointment with a doctor. And that was great because I could see all the available times. Then my doctor could see me as well as mine. So that created a much more permanent experience. And the great thing was they didn't call me to confirm. They confirmed me in the same way I reached out to them by text means. So they texted me to, hey, an appointment's been confirmed or seen on Thursday. That was good because they didn't call me, which would have gone unanswered. So, and you know, and the great thing is my doctor saw me and then she sent me a follow-up email to say, hey, hope it's working out great. So this is a really important experience for you to think about in the audience who are serving and think about the response and how are you receiving that audience? Are you able to access them? Are you able to give them the means to get in touch with you? And so I really want to talk here about, like, teacher-proofing your digital experience. What are those temporarily disabling conditions? Are they going to be able to do to site if they don't know how to use a screen reader? Or if they don't know the keyboard shortcuts? Are those click targets easy to find? Easy to understand the web experience? Thinking about those experiences because not everybody's going to know how to use a screen reader right off the back. Now, I kind of want to go through some experiences that emulate what it's like for somebody who can't see a screen. And so we're going to go through a quick exercise. I'm going to be playing an audio description of an image, and I want you to try to visualize what that image is. So. Image, man washing hands. Oh, dear. Image, man washing hands. I'll come to mind. What do you think about when you hear man washing hands? It could be a lot of different images, right? Did it look something like this? I doubt it. She thought of a search and washed his hands. Let me see your hands. I didn't think so. Now, let's talk about writing a good alt text description. Now, one thing I love to do is think about alt text like a tweet. Swirl succinct into the point. Now, in that image I just showed you how about something like mere doctor inscribes, surgical cap, and masks looks on as you lather up to elbows with soap to prepare for surgery. That's more descriptive than man washing hands. You mean to say? Good. I'm going to agree. So consider thinking about why was that image chosen? What was the context of that image? Why did someone on the content marketing team say there's just an important image? What does it communicate? What does it convey? And so we're going to be, what is the emotional context of this? Only you are carrying a website. Do you want to show the hospital patients that you care in Hytenic? So we've got mere doctor inscribes, surgical cap, and masks. So surgical cap indicates standard of care. It's not really a baseball cap going to surgery. So it's important to say it's a surgical cap, looks on, meaning he's observant, he's alert. You know, he's ready to prepare for surgery. Lathers up to soap and elbows, meaning that he's Hytenic. Another important thing in preparation for surgery indicates purpose. So these are very important qualities of an image that you want to be able to communicate to a user for screen reader. And it's not just for screen readers. It's great for SEO. So you're going to be getting these to help your website search. Now, let's do an exercise together. Let's write our text together. So now the context of this is the Red Cross Disaster Relief. And there's a disaster going on. So if you would go to Twitter and you go to see McNally, I have a link, then you all can go to and click on from your mobile phone and describe this image together. So let's take a few minutes and describe that image. So if you have a hard time finding the link, please let me know. And it's also under David's Twitter handle. So literally it's going to your URL, type twitter.com, see McNally. There will be a link. It's my first tweet, my most recent tweet that is a sent out. And Andrew will take you to this forum. Let's see if it came in. Don't be shy. I'm going to zoom in, if I can. So we have two now. Anyone need more time? I'm going to start reading out some of the responses that came in. Now we've got, I'm going to refresh this. Okay, great. Two women hike in front of a pile of debris. That's pretty good. But we're missing the context of the America Red Cross. These could be two friends. It's missing the context of an aid worker. We've got American Red Cross, aid worker hiking, devastated woman surrounded by home workers under abuse guy. That's very good. That indicates the disaster already happened and there's a recovery process. There's a rebuilding process. So that's definitely a good description. Women embrace, we leave Brooklyn with a hike as they stay in front of a pile of ruins also good. Volunteer hikes flooding victim. Could be a little bit more descriptive because is the flood still going on? You know, we can't quite tell. And then let's see what else is there. Anybody else want to chime in from the audience if you want to say if you have any other suggestions? But I think it's really about context and the context matters. Thanks for participating there. I think the link is live if you ever want to keep trying it and you can see what people wrote for reference. So again, as you mentioned, these guys, the home is destroyed. There's women embracing a disaster aid relief worker. This shows, hey, we're here for you. This could be on the American Red Cross homepage to show, hey, we care. We're first to respond with their ASAP. So that is the context of our text. Links is another thing that is very challenging. And oftentimes missing context. A lot of times we see links that are more click here, contact us, but doesn't have the context that we need to understand what the link is saying or what it means. So how many of you have ever heard a screen reader before? Oh, that's a good number of you. So I'm going to play a series of videos that emulate what the screen reader is saying. And again, this is not the one-to-one experience of somebody who uses a screen reader. They may have their own shortcuts. So, yeah. Link, link, link, link, link, link, link, link, link. First steps at link, learn more. Link, link, link, learn more. Link, link, link, link, learn more. Communications in the arts, web content. You are currently on web content. To enter the link, learn more. Main 26 items. You are currently on a link. To click link, image, link. All right. Did you know what to click on? Did you know when you clicked on learn more? So there's better ways to do it. You can actually make the links more relevant. You can add hidden elements that a screen reader can pick up on, like the blog title. So this is actually a good compromise. So as you can see on this website, it still says more, but the screen reader is getting given more context. So hopefully I can get this video to play. Did that make a little bit more sense? Yeah. So you could actually have a little bit of no stop. Thanks. So you can have, dang it. Okay. Let's just stay there. So it's really great if you have a website like app identity, which it appears. As you can see, is the header, the main image is national save day and month. Find out how to win $811 in April. That's more descriptive than learn more. So if you can add in that context, it helps everybody, not just screen readers. Having that context is really helpful. So the next one I want to show is navigation from a keyboard user. All right. Now, when you're using a keyboard, in a tab or through a menu, you may add a keyboard user. You may not always know if something is dropping down. So you got to make sure that we do tab to send an element to the menu that the turd and items appear. And then also for the screen reader, where the screen be to know that there's children menus that drop down. We need to add in those elements to educate the user. You can't see the screen. Search, search, edit text, search, search one item, search button and the search and the banner navigation one item. You are currently on a navigation inside of web content list six items. You are visited link home one of six, visited link information and services two of six, link about government three of six, link news and social media four of six, link about Australia five of six, link my governor six of six. You are currently on a link to click this link, press control option space. So we're going to follow one. So one of six is helpful. So I can see like when I go over one of six, two of six, three of six, that helps them understand the context of where they are in that experience. So there's another one. So thankfully, all of this is achievable. If you know what those standards are, and you can actually implement them into a website to make it easier for everybody. It's going to be great for mobile tablets. It's going to be great for down the road when we start to implement the voice automated technologies like Siri and Echo and it's a lot of really exciting stuff. So really, where do you begin? Not here. Don't don't worry about it. It's okay. Just take a deep breath because it is not as overwhelming as it may seem. Really, just take a step back and think about a site. Identify the main purpose of a site. What are you doing for the audience and start there? Don't think about every single thing they need to be fixed right now. It's just say to e-commerce site. If it's an e-commerce site, make sure that the shopping experience for somebody usually a screen read or a keyboard is on track. The forms are accessible. The submit button are accessible. And what are those touch points? What is the user going to be doing in order to purchase those items? They're going to be filling the fields. They're going to be selecting a shopping credit and then consider those accessibility elements. Will the user understand the field in the label relationship? Will they understand how to check out? Will they understand where to put the credit card information and think about those interactions and how can you achieve those accessibility purposes? And then from there, what is it going to look like when you have 10% increase in accessibility of a site? Are we looking at 10% increase revenue? Are we looking at 10% increase memberships? The opportunities are really there for you to be able to make a business case, to talk with the product teams, to talk with somebody who is in charge of the spending for the site to say look, we have the opportunity to increase our revenue by making this accessible. So that is our bottom line right there. And so from there really is categorizing by the interaction. Okay, amenities are not accessible. Okay, what do we need to do about it? And you just kind of go from there and track them. Who is responsible for this? The content editor is responsible for quality or text. The developer is responsible for making sure that the field is there for the content editor to fill in. Now in Drupal 8, the art text field is required by default. So that's taken care of for us in Drupal. But we need to identify who is responsible for work so that we can communicate in the backlog and prioritize what needs to happen. And so from there, you've done audit about prioritizing what other must have elements. Who must? One must be fixed at the top of the backlog in order to improve the experience. And that's what you should focus on first. And then once you've done that, you can take a step back. Okay, now we've done that, we've released it. Now our customers can purchase things. Now stage two is kind of making sure that they're up to compliance. Whether or not they're part of a federal funding site, how many of you are familiar with Section 508? A good handful. How about web content accessibility guidelines? Very cool. About equal number. How many of you know that the web content accessibility guidelines are now the new to be standard for Section 508? That's pretty cool. So it's really exciting. So literally just a few weeks ago, the access board said, hey, Section 508 after 10 years is finally being updated. Section 508 was written in 1988. And they're just way before modern web technologies happened. So the web content accessibility guidelines is made up of thought leaders who are as a, hey, these are the best practices that we should be doing for the websites today. And they kind of cut things up to date. So people kind of starting going to work out for best practices. Section 508 in the meanwhile kind of became outdated. But it's still the federal standard. But now the Section 508 is kind of saying, look, we recognize what our date. So let's look at RCAG 2.0, because I thought it would be the new standard. And that actually went into back March 22nd. And by January 18th, 2018, federal sites must be in conformance with RCAG 2.0 level A and AA. So it's a lot of, a lot of really exciting stuff on the accessibility front, because we are bringing these websites up to relevance and accessibility in the modern technologies, not just the outdated levels. And so it's a great opportunity. And so, yeah. Okay, so I want to talk about some tools that can help you along. The first one is, I don't actually know how they pronounce it, whether it's totally or toe to ally, either way, it's a great tool. What this is, is it was made by the Khan Academy, and it is both a Chrome extension and a Drupal module. And it basically is like accessibility vision. When you use it, when you turn it on, you get this little menu on the left side that gives you a number of different ways to scan the site for accessibility. Now, this is not perfect. This is not, you know, if you need to do a proper accessibility audit, you know, this is not really going to help you. You're going to need to bring someone on who actually knows what they're doing. And that's a thing we can help you out with. But if you are looking for spot checks of content, spot checks of your site, this is great. It will allow you to view the alt text. It will allow you to, you know, check color contrast. It just starts to overlay it. Bear in mind that this has been, they've been iterating on this. It is a little bit quirky at times. Like right now, you'll notice in the middle that it's reading the background, the contrast on that button against the background color, not against the, of the site, that blue area, not against the white button background color. So it can be fooled. But you can take a look at the notes that it brings up and you'll be able to identify that it just doesn't know what it's talking about. But that's just, those are few and far between. You know, it's also useful for spotting when you're not using proper semantic structure. It's useful for reading your site back to you or sections of your site back to you as a screen reader would. This is great because as you heard before, many, many, many websites torture people who use screen readers. So this is a great way for you to do quick spot checks and make sure that a screen reader user won't hate you. Another tool is CK editor, which is baked into Drupal 8. It is currently not enabled because there are some security issues that still need to be ironed out. If anyone is in the room who could have an effect on that, you know, maybe bump that up the backlog. The CK editor is mind bogglingly useful because as a designer for accessibility and someone, and our developers who handle it, we can design and build for accessibility and then it is entirely upon the content manager to actually see this through. So a site that is perfectly designed for accessibility and perfectly built for accessibility will completely collapse if you don't have a content management team that is on top of it every single day with every single word that they drop on the site with every single image that they put on the site. CK editor can really, truly help do this by putting in browser, you know, in WYSIWYG tools to scan this. So you hit a button, it brings up this, and right now the first thing that it has spotted is that this image doesn't have an alt text. You'll notice that it's got a quick fix field right in the middle of, you know, right there. You can type in your alt text, hit quick fix, and it will apply it. You don't have to go back and make any changes. It's literally there for you. The next one, this is, having a hard time seeing on that angle, this one is identifying the paragraphs module is being used to drop headers instead of an H1, H2, H3. So that's going to baffle a screen reader that is trying to skim the site and provide an overview. You can do a quick fix right there. It's giving you a drop-down asking you which H you want. You select the one you want. Quick fix, done. The next one is, has noticed, this is my favorite, it noticed that the editor didn't use proper markup to insert numbers. They typed them in, and it's just flagging it, say, hey, fix this. Delete those numbers, lasso it all, and then just hit numbers and it's fixed. That one, there is no quick fix because it's a little bit more nuanced. The next one, this is noticing that there was not proper semantic structure used. Someone jumped from an H1 to an H3, skipping H2, it's telling you what to do, provides a quick fix, done. And then this last one is noticing, this is my second favorite, that the content editor has copied and pasted the image name into the alt text field, which is awful. It is worse than having no alt text because now a screen reader is getting some, you know, screen reader user is getting some gibberish that provides no context to them. Quick fix again, type in your alt text and you're all good. And then the last one is tables. Oh, yes, tables. This one is noticing that the tables don't have proper headings. It allows you to select whether you want horizontal or vertical. Quick fix, done. And last but not least, we have another, this is adjacent links, this one's really cool. It picked up that there are two links beside one another that are pointing at the same place. So a screen reader user would end up hearing that URL twice. In this case, if you hit quick fix, it will just merge those hyperlinks together so it removes the redundancy, which is great. So again, when you are auditing your site, when you're reviewing your site, as Catherine was saying, what you want to be doing is prioritizing. You have to figure out what makes your software, what makes your website important, why are people going to it and focus your accessibility efforts on that because accessibility, as we said in our talk last year, it's a journey, not a destination. You are not going to achieve some level, some imaginary perfect accessibility that you never have to focus on it again. But you should always keep in mind your core functionality, your core goals, and your user's core goals. Prioritize what you need to make your experience work at stage one. The next is figuring out what you need to achieve from a regulatory standpoint. And if you don't have a regulatory standing that you need to achieve, it's good to know what status you're striving for, single A, double A, triple A. Because if you're really putting the effort into accessibility, you should make sure that your user base is aware of it. If you do all of this and nobody knows it, then you've also kind of failed. And then the last is figuring out where you're going to iterate. And again, you should be looking towards your core functionality to figure out where it makes most sense for you to put the effort in. Um, you know, focus on this and do it, start now, if you haven't already, because it's a long road and it's, but it's a road worth walking. You need to do this, you know, for your users. Make sure that they know that you actually, you really, truly care about their experience, about their ability to access your information. In order to show this, you want to make sure that you're doing things like providing tons of ways, as many ways as you possibly can, and as many ways as makes sense for your user to communicate with you. Don't choose for your user how they have to communicate. Let them choose for themselves how they're going to interact with you. Um, you know, as with Catherine's, you know, setup, you've, you know, don't just provide a phone because there's going to be someone who literally cannot do that. If you have some kind of booking, you know, provide, you know, a text-based interaction that will allow people to book and let them call. Make sure that your core functionality is front and center. There's no reason to bury your core functionality. Make it easy. Use closed captions. Um, and this is, you know, closed captions are great now, not just for people who need it because they can't hear the content. It's great because if you're scrolling down, you know, your social media feed, um, I mean, raise your hand. If you've been sucked into a video, you would have otherwise ignored because you saw some closed caption text. Yeah, me too. Um, it's useful. It's also, again, good for SEO. You don't need to put in a ton of effort to close caption. You don't need to go and sit there typing this up all by yourself. We showed this last year. We have a blog post up on our site that walks you through step by step, but YouTube has a freely available automatic closed captioning system. You upload a video. Even if you upload it privately, YouTube's bots will go and analyze the audio, add the closed captions, and it's crazy accurate. All you have to do is then watch it through once, identify where it messed up, and just change the word. And it's, it's easy to do because it's adding all of the timing. So you don't have to go back and do that. That was the brutal part of closed captioning before this. So anyone can do this. There are zero excuses for having videos without closed caption because you can then export them back out and upload them elsewhere. You don't even need to keep it on YouTube. Um, when you're displaying error text, don't just use color to indicate that something is wrong. You know, because color is not going to be helpful for your colorblind users, and it's not going to be particularly useful for your screen reader users. It's also, even if you are sighted and, you know, and have normal vision, it's kind of a pain to have to go through and find, you know, what silly, you know, tiny symbol someone dropped next to a field to indicate to you that you screwed up. Make it clear. Use text, use imagery. The more, the more that you use, the better. Optimize around touch and keyboard and mouse interactions. If you are, if you think that touch and mouse interactions are the same thing, come find me at the phase two booths. I will happily educate. Um, all text your images and do it properly. Really figure out why you put your, that image on the site in the first place. What was it that you intended to convey? If a blind user can hear your description of the image and move on having understood what a sighted user would, you have achieved your goal. If they cannot, you've fallen short. Um, you know, set up, use, just use proper semantic structures. Don't jump between your H's, um, and don't use, um, don't use your H's specifically for styling. Um, I know that that is, you know, depending upon how you've set up your site, that might require a refactor in either technology or how you are, um, using it. But this is an important thing. Drupal 8 is a really great base to start with, um, if you're looking to build an accessible site, um, the way that handle skip links forms, alt text is now required, error messaging, all, you know, an SEO, all of this is out of the box. You have a much stronger experience. Um, our whole talk last year was on this. So there's a video of that if you are interested in more of the nuance. Um, we also have an accessibility playbook that we put together. Um, this is a lot of the things we've talked about and some more, um, that can be used to help kickstart your team. Um, you can, uh, I think Katherine has tweeted this out. Give it two minutes. She will be tweeting it out. I'll be retweeting it. Um, but you can get that from us and, um, you know, feel free to reach out if you have follow-up questions on it. So to wrap up, when you are designing for accessibility, you are designing for the lowest common denominator. Um, we're talking about in terms of senses and, uh, and, and mobility and use of their, use of their hands. This means that you are trying to build something that is as universal as you can possibly get it. What I'm asking everyone to do here is to fight for accessibility, not just push, suggest, I mean, you should absolutely be fighting for it. You should be fighting for it because it's the right thing to do. You disenfranchising users is, you know, not something that should be happening at this point. Do it because it's the selfish thing to do. Do it because one day you're going to need it. If you live long enough, you are going to reach a point where you are going to say, man, I really wish I fought harder for accessibility because the web sucks. I can't see this. I can't read this. Why is it this way? And the reason that it, that you would be looking back and saying that is because not enough people were fighting for it. Some other quick selfish reasons to do this is that it's good for SEO. That will boost your site. It's also opens you up to new markets. It opens up people who otherwise would not be able to purchase from you or take in your content. If you are doing a new site build, if you are looking out over the horizon, then there is one coming. Make sure that accessibility is a core part of your goals because it is far easier to build fresh accessibility than it is to start from scratch on a, sorry, than it is to bolt it on. It is absolutely doable. It's, you know, you have to focus on incremental iteration. And it is important if you don't have a site redesign coming up to start figuring out how you could make those incremental improvements. But if you have a redesign coming, think about what you're going to do to make sure that you are coming into compliance because you will thank yourself later on if you do it. So, last recap. Do this for yourself. You're going to want this one day. Do it for your users because they are going to want it. Designed accessibility for your lawyer because they are going to love you for it. And you should love your lawyer. They are looking out for you. Do it for usability. A site that is built with good accessibility principles is a usable site. Do it for SEO. A site that is built with good accessibility practices is usually pretty search engine optimized. Do it because it is the right thing to do. One minute. I think we have to give up the room. But please, if anybody has any questions, I think they are to make it in the middle of the room. Don't be shy. Oh, yeah. I'm not shy. So, I just wanted some clarification on alt text. So, are there any guidelines as far as assuming the gender or race or anything like that of the person or people in the picture because I feel like that could potentially be touchy. And also just the length of the alt text. So, some of the examples that you gave are a little bit longer than I've been guided to use in the past. So, in terms of race, ethnicity, and other identifying characteristics, my suggestion would be to think about, again, the context. Is the fact that the person a woman relevant? If you are building a site that is encouraging girls to code, absolutely. It is completely relevant. If your site is pushing a pharmaceutical product that is gender neutral, maybe not. In terms of length, we recommend shooting for the length of a tweet. And use the length that makes the most sense to convey the meaning that you need to convey. If you've got 500 characters, you're too long. If you've hit 100, 110, you're fine. The key is to make sure that you're conveying the meaning. Yeah, can you speak to some of the newer technologies like AngularJS and accessibility or basically things where you're using JavaScript to draw the screen and how screen readers handle that? That is a technical area that I'm not super familiar with. But we've got some great experts in the room. We've got somebody right next to you. Right there. Yeah, so there's a lot of accessibility in JavaScript that is improving. It's definitely being watched upon. And I've seen some JavaScripts implement in Angular. Even go ahead. Just to say that the screen readers work on the DOM. So you can build a nice framework with JavaScript that is accessible. But it comes down to if the community has enough people and if there's enough motivation to go up and see that the central library is being maintained and tested for accessibility. And I've heard some mixed results. And so it really depends on the library and checking to see how viable that is. Thank you. Thank you, Chris. Oh, this is a suggestion. If you're going to tell people to use YouTube automated capturing, tell them to make sure that they go through and correct the captions. Because the automated captioning doesn't work in most conditions. Yeah, definitely. That's definitely something that we do. We do the automatic transcription that we go through doing manually. I did this talk last year. YouTube understand David perfectly. Didn't understand me. I hurt my feelings. But that's so I had to go and we changed my talk. So I definitely agree. Go ahead. Well, to continue the conversation off of what you just said, if you work in the public sector, you're actually required to have broadcast quality captioning. So just for any other public sector folks in the room, I thought I would share that. And then for color contrast, I actually really like the Possello groups color contrast analyzer, because not only does it check for different forms of color blindness or cataracts, but also lets you select it give you color options for your palette. So it's actually a really strong tool. That's great. Yeah, thank you. I've seen a contrast analyzer is by the Possello group who works with WC three. I'll treat that. I've seen that tool. So I'll definitely treat that out after this for you guys. It's definitely great. Thank you. Thanks. Thanks, everybody. We'll be around. We'll be in the booth. Come find us at booth 404. I promise it's there.