- [Mike] Good morning. Good evening. Good afternoon, everyone. Thanks for joining us today. We'll begin momentarily as people start to trickle in and sign onto the webinar. All right. Thanks everyone for joining us today, we're really excited about this session, The Marketer's Guide to Accessibility. Just have a couple of housekeeping items I wanna take care of before we get started. First off, this session is being recorded, and we will email everyone the recording after the event. We have live captions available, feel free to use those as needed. And lastly, if time permits, we'll do live Q and A at the end of the assessment session. So if you have any questions, feel free to use the chat box, so the Q and A box that Zoom provides, and we'll handle those at the end of the session. So I'll introduce myself first, and then Marissa will introduce herself. My name's Mike Mooney. I'm the digital marketing manager at TPGi I have six years experience in marketing with a focus in digital marketing, and I've been learning about accessibility and creating inclusive experiences for over a year with TPGi. And I'm excited to share some of those insights with you today and how it pertains to marketing Marissa? - [Marissa] Hi everyone. Thank you for joining. I am a senior product marketing manager here at TPGi I've been at TPGi for almost four years. I have an MBA in marketing, and I have about 15 years of marketing experience. And I'm very excited to talk to everybody about how you can improve your marketing overall with accessibility best practices. - [Mike] Awesome. So we'll over the agenda quickly here today. We'll start with what is digital accessibility and set the stage for the conversation today? We'll go over user experience, website pages, chatbots, email marketing. We'll discuss multimedia PDFs, social media, SEO, and then some accessibility testing tools that everyone can kind of utilize on a day to day basis. So getting into it, what is digital accessibility? And really what digital accessibility is, is providing inclusive experiences for all. So the World Bank estimates that about a billion people worldwide, that's roughly 15% of the population, has some level of disability, whether that's a visual, hearing, a motor, or a cognitive disability. And so when we think about digital accessibility and creating digital experiences, we think about providing inclusive experiences as all, because digital disabilities change the way people consume digital content. So just to kind of get a perspective, blind or low vision users rely on screen readers or screen magnifiers to read the content. And individuals with limited mobility may only be able to use a keyboard to navigate the content. And people with cognitive disorders may only be able to focus on disparate pieces of content rather than the entire page. So, when you go to create a website or an application, or just a new, a blog page for your site, thinking of the collective whole and making sure that your content is accessible to someone that uses a screen reader or needs to navigate your site with a keyboard is very critical to ensuring that they're able to access that content, especially if have an e-commerce website, or someone trying to transact the banking transaction. So making sure that all these different pieces of content is accessible is super important. Now, the beautiful thing about this is, there are guidelines for ensuring digital accessibility. So the web accessibility standards, or known as the Web Content Accessibility Guidelines, WCAG, also referred to as WiCAG, they come from the Worldwide Web Consortium, W3C, and they're currently on version 2.1. And the WCAG provides criteria for content creators that will help ensure an accessible digital experience. So you don't need to be an accessibility expert to conform to many of the WCAG criteria. And this really helps community of digital creators, developers, designers, and marketers like you and I to work cross-functionally and create accessible experiences and content. And that's really what we're gonna talk about next is user experience. And so user experience, we can kind of think about the different user flows that are made up on the different websites and applications that are on our digital content today, and that may even span to multiple sites. And so, when you think about user flows, they're primarily objectives that users may need to complete on your website. And so on the screen here, I have an image of a collection of pages with highlighted areas of these pages where users might flow and navigate to based on their objectives and what they need to accomplish on that site. Now, there are a lot of lawsuits around digital accessibility, which includes achieving objectives on your website. Now this is not in all cases, but it's something to be aware of. And so if you do identify accessibility issues within specific user flows, for example, if someone comes to your site and one of the objectives is to just schedule a conversation to talk to a representative or an expert at your company, if they are unable to complete that form and that critical function of that user flow, then that could trigger a lawsuit. Similarly with any eCommerce platform, adding items to a checkout cart, and someone trying to check out, these are critical functions that people need to complete in order to achieve their objective and complete a successful user experience. So when you're able to identify these issues, you can narrow the focus, prioritize accessibility issues in these user flows, and then I hopefully improve the experience for everyone. And when I say everyone, I do mean that it could be typically what we see is, when we create user experiences that are accessible for everyone with disabilities and without disabilities, it ends up being a better user experience for everyone. And we have some examples of that later on. But identifying these critical user flows on your site, there's a couple ways to get started. On screen, I have a screenshot of a Google Analytics Goal Funnel. Hopefully some of you are familiar with this. If you're not familiar with Google Analytics, I definitely recommend diving into them. But when you use your Google Analytics Goals and Funnels, you can actually identify specific issues impacting the steps in the user flows, looking at different conversion rates at each stage of the funnel. If there's an unusually high abandonment rate or a high bounce, that might be a good area to start. And then using some accessibility testing tools like ARC Toolkit and ARC Monitoring, which we'll talk about in a second, you're able to prioritize and remediate those accessibility issues, and hopefully try to increase and improve upon those conversion rates. So analyzing user flows with ARC. ARC is is a software that TPGi provides. It stands for the Accessibility Resource Center. And on the screen, there's a screenshot of the ARC Platform, and it's displaying a user flow dashboard, and kind of like thinking about Google Analytics and the Goal Funnel we were just talking about, you can actually drill into individual components of those user flows in the ARC Platform and identify and push some issues to your developers to try to remediate that. The other benefit of ARC is leveraging the monitoring. And we'll discuss that more in a little bit, but you can actually track performance and trending over time. And so when you do make initiatives at your organization to fix some of the accessibility issues that you've uncovered, you can actually release the new code updates and see if your fixes are actually trending in the right direction. And if they're not, then you know there's some more work that needs to be done and you can dive back in. And so I'm going to let Marissa take over this next section here, website pages. - [Marissa] Excellent. So as a digital marketer, you know that your website is your digital presence. And this is where people will purchase products from you. They can contact you, they can find out information about your products and services. It's basically a online store. And if you have an inaccessible website, it's basically a store or office where someone with a disability is locked out. And Mike and I are here to help you remove these locks, to make sure that anyone can access your services and your products and talk to you. - [Mike] Marissa, I think you might be on mute. - [Marissa] So one of the things to keep in mind is that, if you have images on your site, I'm using... It's the code. It's not going to interpret an image. It's not a magician. It can't see an image. So if there are images on your site that are necessary to understand the content or are necessary for all of the contents to make sense, always add alternative texts to them. Next. Also make it easy for users to skim your stone. And as Mike mentioned earlier, when you make your site accessible to people with disabilities, it also improves the experience for everyone. So for example, you will wanna make sure that you use proper headers on your site. So always start out with an h1, and then work your way down h2, h3, potentially h4, if you have a decent amount of copy. And make sure you use them appropriately. Don't just style all h ones or h twos so they look different visually, because the screen reader is actually able to skim your site using the keypad. So this means that you will be able to break up your content, which is also great, because if wants to read a giant, dense block of content. And it makes it easier for people with all different types of disabilities, the cognitive, the mobile, someone using a screen reader, and it improves the user experience for everyone. And when in doubt, just break it down, make it simpler. Also choose your colors wisely. So on screen, I have two logos, one is a TPGi, which is a dark blue on a yellow background, and then I also have some delightful Christmas color TPGi logo with a yellow background. So, which color combination is more appealing to, if you can see the screen? So I personally like the former, the yellow background with the blue, and that's great because it actually uses a appropriate color contrast ratio. So as part of the Web Content Accessibility guidelines, Mike mentioned earlier, one of the criteria for accessibility is actually using an appropriate color contrast ratio. And this is critical because people with low vision or colorblindness may not be able to distinguish if colors do not have a high enough contrast ratio. And you may be thinking, "I don't even know what that ratio means." Or how to get that ratio. But, you know what? That's okay. Because TPGi has a free Color Contrast Checker tool that we will put in the chat at the end, and you can go to our website and download it to make it super simple. So most websites have forms. And if your website does have a form, there are some considerations for you to implement, to ensure that it is accessible. So there are non-technical and then there are technical. And non-technical are fairly easy to implement. Keep it short and simple. Provide clear instructions and visible labels, so people know exactly what they need to input. You need to validate the inputs. So if someone has put in something incorrectly, let them know exactly what is wrong with it and what needs to be changed. I mean, there's nothing more frustrating than trying to fill out a form and it keeps giving you an error and you have no idea why. And imagine if you are a screen reader user, and you can't even see the screen and it's not telling you why. So always make sure there's a reason for the error. Make sure that you notify the user if they've been successful, or if there's a failure, as I mentioned before. If your form has to be long, then consider adopting a multi page or a progressive form. And this is actually helpful for anyone using a form. People regardless of their abilities, get bored and annoyed with long forms. So if you can break it down, it makes it a lot more likely they're going to actually finish the form. And also remove time limits or provide options. Someone who is using a screen reader or only a keyboard, or maybe has cognitive disabilities, may not be able to fill out a form in the same amount of time as someone without a disability. And it's stressful to have that timer in the background, and even worse if at times out, and they're ultimately not able to submit. So do yourself a favor and just remove them. I know as marketers, we love that sense of urgency, but in this case, it's not the best use of that. The technical considerations, and these are things that you can pass on to your developer, or if you happen to have developer skills, great, you can implement them yourself. So just make sure that the form is operable by keyboard alone. Use the "label" elements and the "for" attributes. Make sure you have grouping controls like fieldset and legend. You need to associate the related controls with ARIA. Make sure that your font size is appropriate. Usually 14 font is the minimum that you wanna use on a form. And of course the color contrast, like we mentioned earlier. And then run it through a rules engine, just to make sure there are no accessibility failures. So one product that we'll talk about later is ARC Toolkit, which will help you. It uses the ARC Platform rules engine, which is our accessibility platform for all of your accessibility needs. So you can use the ARC Toolkit. Next. Also try not to communicate critical information through hover states and tool tips. Unfortunately, if you are not using a mouse, like a screen reader users or someone who's just using a keyboard because of mobility issues, it is very hard for them to access a tooltip. So if you have to use a hover state or a tooltip that relays information, make sure that they are reachable and operable by a keyboard. And this is what you can tell that they're your developer. They will appear on focus as well as hover. And make sure they are screen reader compatible. So there are multiple ways to acquire the information, but the overall recommendation is that just don't them. If the information is important enough to go on your site, it's really important enough to be in plain view. Breadcrumbs are a great way for people to navigate the site, to understand exactly where they are, where they came from, and they are helpful for everyone, regardless of their ability. You just wanna make sure that users always know where they are on your site and how to get back to the homepage. Meaningful link text. This is one of my favorites actually. So you may not be used to writing meaningful link text. I know that a lot of us are just used to linking click here, or download, or go to, or just linking something that really doesn't have a lot of context. So this is a problem because not only for screen reader users, because they're able to skim an entire page and just see all the links or they will hear all the links rather. And if they hear a link that says, download or click here, they're not going to know what that means at all. So what you wanna do is, make sure that you have informative link text. Sign up for our webinar, contact us today, review your purchase. So anyone, regardless of their ability will know exactly what they're going to get when they click on this link. Chatbots. Chatbots have become very popular in the past few years, and they are honestly a great addition to a site. They can be very helpful in routing more complex queries or even answering mundane questions that your customer service team doesn't have time to do. However, they are usually an out-of-the-box chatbot solution. Most companies do not have the internal resources to actually create a custom chatbot. And just keep in mind that as a third party software, you are responsible for anything that's on your site, regardless if it's third-party or something that you created. And some of the issues like contrast and some layout, they may be able to be addressed by one of your developers with strong CSS skills, but a lot of the issues that a person with a disability may run into are core problems with the chat bot software itself. And scripting it can't fix it all because the underlying code and the chat bot vendor has things that change with each render, making it possible to target. So one way you can safeguard this is first, get a credible accessibility expert to test any chat bot solution before you implement it, just so you understand the level of risk that you're taking on. And also check to see if your vendor has an accessibility statement or some type of guarantee, and then build it into the contract. If it is an inaccessible part of your site, it's not going to fully protect you from any risk, but it will give you a better sense of how much risk you'll be exposed to. Email marketing. We love email, who doesn't? I mean, it has a return on investment of something like 35 times, which is fantastic. We use it a lot here. But when you're doing it, always keep in mind that you need to use alternative text for your images. It's the same thing with websites. A screen reader user is going to be using email as well. And if they can't see the image and there's no alternative texts, they are not going to know what's going on. So just always make sure that you include that, regardless of whether it's a Mailchimp or constant contact. Usually, all email platforms will have that option to add the alt text. Don't be stingy with your tags on email. So again, make sure that you have the H1 for the title, and the H1 is not the subject line. It's going to be the title. Use H2s for sub-headers. And if you find yourself in need of an H3, you may wanna rethink your email content and send your visitors to a landing page copy instead. And this is also a best practice for marketing in general, emails that have too much information are overwhelming, and you're better off just sending someone to your webpage. Remember to include the P tags for your body copy, and you can even use the title tag to provide context. Now, if you have a visual email, so an HTML based email, then you need to be aware of a minor addition to your code. So back in the day, when the web was beginning, it was actually used by scientists to share data. So they use data tables. And as more and more people get interested in this crazy new worldwide web, the developers who were developing websites for the internet started using these tables for their own purposes. So they would fill them with images and content. So that was the old way of building websites. If some of you were around in the early '90s, early 2000s, then you'll remember, this was the way of building websites. Now we don't do that, but a lot of HTML emails still utilize these tables for their content. So, because these tables are actually used for data, what you wanna do is add the role equals presentation code to let screen reader users know that these are presentation tables, not data tables. And it will actually change the way the screen reader reads what is in the tables, so it makes sense for that screen reader user. And remember that people read a lot of email on mobile devices. So aim to keep your texts above 14 points. If people can't read your message on mobile, they're not going to read it at all. As always, keep your color contrast to accepted guidelines. Avoid center aligned paragraphs, which are much harder to read anyway. And make link texts informative and short. So all of these things are applicable across websites, as well as emails, really any type of digital content. And I keep hammering home this point, these are all things that are going to help everybody. It's going to improve the user experience for anyone, regardless of their ability to consume your content. Multimedia. So multimedia is fairly straightforward. Always include your captions on the video. And this is great, not only because everyone will be able to understand what's going in the video, but it's also helpful for people without disabilities, who are in different situations, such as somebody who wants to watch a Instagram video in a public place, but they don't have any headphones. Or, if you're sitting in a doctor's waiting room and you happen to see a video on TV, it's on mute, you don't understand what's going on, but if they have captions, you can. Other considerations. So if you host podcasts or other audio multimedia, make sure you have a transcript on page. If you are deaf, then a podcast is a non-issue. They won't know what the content is at all unless you have a transcript. They're also transcripts are highly recommended, even for videos that have captions. However, if you're hosting videos on a platform like YouTube, the transcript that is part of the YouTube is sufficient for most organizations, but best practices, like if you're hosting something on your site would be to provide a link to the transcript. And then video descriptions are a nice touch. A video description is narration that's used to communicate key visual elements to blind or low vision individuals. So for example, if there is a poignant scene where nobody's talking, there's just a lot of music, the audio description will actually describe what's going on in the scene. So everyone knows what's going on. PDFs. PDFs, like every other digital content need to conform to the same accessibility guidelines as websites. So they need that same logical reading order. They need the headings and sub-headers to facilitate faster and easier comprehension, and alt text for images. Creating an accessible PDF ranges from very easy to very complicated. So if you have a very simple word document, maybe it just has a couple of images, just make sure you add the alt text, and you can create it to an accessible PDF in the Acrobat tab and then create PDF. So before doing that though, just make sure you use the native Accessibility Checker. So that is part of Word and PowerPoint. Adobe Acrobat Pro also has a native accessibility checker function that's very helpful. However, if you have a longer, more complicated document, so if you have a Word Document that has a lot of different components, or if you've created something in Photoshop, or Illustrator or InDesign and you need to convert that to a PDF, you may want to call it an expert because there are a lot of different considerations that need to be done on documents like that. And you can use the Adobe Acrobat Pro native checker. It's a little more complex to do. - [Mike] Awesome. Thanks a lot, Marissa. All right. I think we're gonna talk about social media now. So similar to the website and a lot of what Marissa just covered, creating inclusive experiences doesn't stop at social media. We should continue that, it's an extension of your brand. And so, the first two topics on under this umbrella is image alt-text and video captions, which Marissa touched on earlier. And a lot of the social platforms over the past couple of years have actually been releasing accessibility features to allow marketers and anyone posting content to make it more inclusive and provide accessible experiences. So when you go to post an image, make sure that you're describing what that image is through the alt text. And similarly, when you're providing or releasing some video content, make sure that you're providing video captions so that everyone can experience this and enjoy your content. Next is hashtags, and this is a pretty critical thing that not all people think about, because we've been using hashtags since they became popular and analyzing which ones are gonna connect you with the audience you wanna connect with. And if people aren't able to understand what these hashtags are through the use of screen readers, then they're not really gonna be able to connect with your brand the way you want them or find your content. So using camel case when creating hashtags and capitalizing these words or phrases that you combine into into a hashtag is critical for screen reader users to actually be able to read and understand what you're trying to convey or say. And I have an example of that in just a moment. So for, for the camel case, it's just capitalizing each word. So if camel case was a hashtag, it would be capital C, capital C, CamelCase, versus lowercase Cs. And the same goes for emojis. So on screen now I have a fictitious social posts, and I will read through this as sighted a person would interpret it and then I will read through it as if a screen reader is reading through this content. And so, check out this five star review. Schedule your appointment now. #fivestarreviews. And so easy enough for anyone who is sighted to understand what you're trying to convey here. Now, as a screen reader user, a screen reader will read this as so, check out this yellow medium star, yellow, medium star, yellow, medium star, yellow, medium star, yellow, medium star review, schedule your appointment now. And a screen reader will read this hashtag as nummer fister views. And so this is something that most people don't think about. It wasn't something that I thought about prior to working with TPGi. And I hope this like sinks in for people to kind of make some and changes and adjustments to how you create and think about social media and your content. So drafting this post in a different format, check out this five-star review. Yellow, medium star. Schedule your appointment now. #FiveStarReviews. And so this is just provides a better experience for everyone. It gets the same message across and it minimizes the amount of emojis used. And so for social media, those are just a couple of takeaways. I hope resonate with you and you'll take into and adopt in your practice moving forward. But with social media and emojis, less is more. All right, let's dive into SEO. SEO, organic optimization, I hope everyone is familiar with this. The good thing is what we see is there's a lot of overlap between organic optimization, and what's good for SEO is good for accessibility. And the other good thing is that we've covered some of these today in previous topics, do's for SEO on your website and digital content. Again, make sure you're describing your images and utilizing those all tags with relevant descriptions. You also have the option of using image captions. You don't have to use both. You have some flexibility to do either. Video transcripts, you could actually check out TPGi.com and some of our video content on there and see how we do it. But we have links to video transcripts for anyone that wants to do utilize the transcript versus going through the entire video. It's great for screen reader users. Link anchor texts, making sure that your link anchor texts are descriptive, not just saying, click here. Making sure that they're descriptive and people understand like what they're actually gonna click to or experience next. It's good for SEO as well. Proper, descriptive title tags, making sure that your headers are actually descriptive of what some of the users is gonna consume or read is critical to providing them. And people with screen reader users, they're experiencing what they intend to get into next. Proper and sequential use of header tags. Again, making sure you're not starting off with H4s, start off with H1 and H2, H3, keep it linear and make sure it's logical. And the last one here is time on page and additional related searches. So on-screen, there's a screenshot from a tweet last year to the search advocate of Google, John Mu. And the question is, is it possible that Google will ever factor in the accessibility metric with search results ranking? And John responded? "I won't say never, "but I'm not aware of any immediate plans. "In general, though, "when sites are hard to use, "people stare away from them anyway, "so over time things like recommendations and other signals "tend to drop away, "resulting in the site being less visible in search too." And so I think a good takeaway here is, if your site's not accessible and people are bouncing because they're not able to navigate it with their keyboard or using a screen reader, then it's likely to trickle into your SEO as well. and you might experience some higher bounce rates and a D ranking in the SERPs. So it might be a good best practice to make sure that you're creating accessible content. Now, some SEO don'ts. Don't stuff keywords in any of the attributes used for SEO or accessibility, like alt tags, title tags, captions, and transcripts. Don't use images as texts. It's not generally accepted that images are machine readable. So again, if you do have to use, or you do wanna create a word cloud that is not made up of HTML, but it is a graphic, make sure you're providing an alt tag so that people can understand what that content is. Don't make your alt tags overly complicated, or try to put entire infographic's worth of content. So this is kind of like an art form in describing what an image may be. You don't wanna overburden. A screen reader user would try and understand what an image you just wanna describe and get the general understanding of what that image is conveying. And lastly, don't use image graphics for... Don't use images for infographics when possible. Use HTML and CSS to code it onto your site versus just posting the image. And that actually, it was just beneficial for everyone, so. All right, up next, accessibility testing. So we have some tools that we wanna go over today, but first, like what is what testing actually is? Is the ability to understand how these practices we're talking about are applied when compared to various standards. As we discussed earlier, accessibility standards, Web Content Accessibility guidelines. And there are manual and automated tests that can be done. And there is also some tools that you might not be aware of in the programs and platforms you use every day. So Microsoft and PowerPoint and Microsoft Word actually have native accessibility testing tools built in that are located under the Accessibility Checker. So, if you're not aware of that, you are now, definitely go check them out. It'll help improve the experience for your content if you are sharing it with people that are operating a screen reader or need to navigate with the keyboard. Additionally, Adobe Acrobat has a native accessibility checker tool, as Marissa mentioned earlier. It's pretty robust. It can help you make your content accessible. So definitely check those out if you're not familiar with it. ARC Toolkit, it's excellent tool for single webpage testing. As we've mentioned earlier, ARC Toolkit is a free professional-level accessibility testing tool, and it's a Chrome extension that you or your developer can turn on average, scanning your website and scanning a single page for any accessibility issues related to the WCAG guidelines. And it's great. Just trying to get a quick synopsis of, do I have errors? How many errors do I have in my page? I think you can export the content and share that with the developer. And here's a quick little view of ARC Toolkit. So you can identify again, quickly visible errors, totals, warning signs to look out for, and then you can take immediate actions and next steps. So definitely worth checking that out. And we'll provide links to that after the webinar, as we send out an email with the recording of the webinar as well. So screen reader testing for website accessibility. So one of the things that developers and QA testers will do, is they'll manually test your site for screen reader accessibility and compatibility for screen readers. And they can use a screen reader tool like JAWS screen reader, or they can use a screen reader testing tool to test the accessibility of your digital content. So the advantages of using a screener testing tool, it's usually easier to adopt those tools and actually get a better sense of the accessibility of the content. So, screen readers have a high learning curve, whereas screen reader testing tools like JAWS Inspects. It's a little more intuitive. Anyone can use it. So you as a marketer or someone in your apartment, if want to just to get like a better understanding and not necessarily work with your developer on this, you could use JAWS Inspect, scan your pages for screen reader compatibility and get a report on some areas that you can go make some changes to right away, or you can pass that off to your developer. So there's some flexibility there. JAWS inspect transforms JAWS speech output into a text format for easy bug tracking remediation. So it's a really cool tool, and we actually have a webinar coming up on February 2nd of JAWS Inspect. So if you're not familiar with that screening or testing tool, definitely recommend you registering for that event, passing it onto your developer to register for that event to learn more about it. Alright, ARC Monitoring, we talked about this briefly earlier. On screen, is a screenshot of the ARC Monitoring dashboard. And again, ARC is the Accessibility Resource Center. It's a accessibility platform that allows you to enter your domain, scan it and track against the WCAG guidelines for accessibility errors, failures on your site. And so on screen, there's a WiCAG Density Score. Again, that's been tracked against the WCAG standards. And so you basically have received after entering your domain, a benchmark of your accessibility of your site. And one of the cool things about this is, it's similar to Moz or STM rushes You can track your website's accessibility over time. And so you make adjustments to the violations that are on your site, you can create tests initiatives and you have your developer improve the accessibility of your website by making those code implements and changes. And then track your website history and make sure that you're on track with where you wanna be as you set your goals. And if new new errors arise, as you release new content, you can let your developer know and make sure that you're prioritizing these failures that happen. The other thing is, developers don't have to go scouring the web for the solution to the violations that you've identified on your website. ARC provides the solution to the violation so that you can have the answers right away, and your team can take action to remediating these accessibility issues. Lastly, JAWS Connect. So JAWS Connect is a free user feedback tool that was released in December last year. And it's free for users that are having an ARC account and have ARC Monitoring enabled. And so screen reader users can provide feedback quickly and at the point they're encountering a barrier on your website. So kind of going back to the examples we had talked about earlier, where someone is trying to go through the user flow, and they're trying to submit a form to you to execute on their objective. If they can't fill out that form, that's a barrier. And so, JAWS Connect allows these users to provide feedback to your team so you can go and remediate and make those changes immediately and improve that experience for the next person. Similarly, if you have an e-commerce website and people aren't able to check out, again, if they hit that barrier, they can provide feedback right away and your team can take immediate action on it. So again, it's a free user feedback tool, as long as you have an ARC account and you have monitoring enabled. And we can talk more about that later on. And with that, I think we have some time for some questions. - [Marissa] So in case you are not looking at them in the chat, I have put the links to the webinar that Mike mentioned on Jaws Inspect. I have the link to the JAWS Connect, solution that he talked about, as well as the link to the ARC Toolkit Chrome extension. So does anybody have any questions about the webinar or any of our presentation? Any of our tools? Okay, well, I don't see any questions. If you have a question, or tomorrow, if it comes to you, then you can email Ida, ida@tpgi.com, and she will route any questions about the seminar to me and Mike. So thank you everybody for joining. We really appreciate your time, and we hope that we've been able to provide some valuable information for you. So have a great day. - [Mike] Awesome. Thanks a lot everybody. - [Marissa] Bye.