 Alright, anyways, so talking about website accessibility and the internet as a whole. This is a quote from Tim Berners-Lee, he's a little bit of an important guy, he created the World Wide Web, and he says, the power of the web is in its universality, access by everyone regardless of disability is an essential aspect. So that's the foundation of the internet and of websites in general. That's why accessibility should be kind of a core aspect of what you're doing when you're creating a website. Keep in mind that there's all different types of people that are going to be viewing your site, not just somebody that is completely 100% able-bodied and uses a mouse and a keyboard and can see the screen. So, also, the UN has even gotten in on this game and has defined web accessibility as an essential human right. So the access that people have to the internet, to the information on the internet is a human right because it's such a major part of what you do on a day-to-day basis. Worldwide, so why should you care? This is a very simple formula, but potential clients plus worldwide users means that there's going to be an equal unprecedented access and equal opportunity to information. This is as basic as I can explain web accessibility and why it should matter. So, a few quick facts. There's 20 million blind adults in the US, approximately. 10% approximately use screen readers and 8% of men and half a percent of women are colorblind. You might say, alright, well that's not actually that many people in the grand scheme of things. We're going to get into that, but that is a very important part of... There are a lot of people that are using websites that aren't 100% able-bodied. So the most common example that comes up in terms of web accessibility is colorblindness. So the most common form of colorblindness is deuteronopoeia. And that's the simplest example that I can provide. So on the left-hand side is the normal color wheel as you would generally see it. And on the right-hand side is what you actually see. So the most common way to describe that is if you're using red, for example, to highlight something. Say you have a sale on your website or for your client's site and you say sale, but there's no other indication of the sale other than the fact that you use red letters and an exclamation point, for example, then it's not going to really stand out, right? It's going to be this sort of awkwardly brown-green-gross color. But if you decide to use other factors to highlight what you're highlighting, so you use like a circle or like a star behind it or something else, anything else that's not just solely dependent on color. So we're going to go through a few examples of websites. This is Apple.com, pretty well-known site. And it's also very highly regarded as a really well-known, they take design into account, right? That they're very well-known of taking design into account. So if you look at it with deuteronopoeia, it's not that bad. You can see what's going on. Sure, it's not as warm and welcoming, I guess, because the pink is gone. But at the same time, you can still, it's completely legible. You can read what everything is saying. This is the first step to things to think about when you're creating your site. The next one, this is a government site, White House.gov. So also a fairly prominent site. And if you look at it with deuteronopoeia, again, it's not as good as the Apple site where there are dark colors, and it does start sort of blending in. But even they've, I mean, it's a government site, so they're kind of responsible for being responsible about this. But they did do a relatively good job of making sure that it's still legible. Now, this site, you guys may see it, have seen it already, might be a little familiar, is where Camelana site for this year. And this year's site does a pretty darn good job. For the most part, it's still legible. The bottom is a little bit harder to read, kind of. But it's just, I want to give these examples so you guys have something in your head to look back on when we're talking about all the other stuff. So colorblindness is not the only kind of disability. There's a very large number of other things. So these are the, this is a basic breakdown, as I've done it. Auditory, cognitive, neurological, physical, and visual. So there's colorblindness, of course, but then there's also hard of hearing. So if you have videos on your site, make sure that you have captions for your videos or something else to describe what's going on if somebody can't hear what's going on. Or you have levels of blindness. It might not be colorblindness, but they might be on the scale of all the way from legally blind to just near sighted or something. You know, they don't have glasses on. You also have ADHD or dyslexia, or if it's a cognitive disability, then making sure that your website is laid out properly. So you want to be sure that the layout of the site map and everything actually makes sense. You know, your about page is where you would think an about page is. Your contact page is where you would think a contact page is. I've had clients that have had very interesting menu setups, and it's not always clear why a certain page is underneath a certain subheading. Does that make sense? Everyone with me so far? Notting heads, cool, good. And then also there's things like physical disabilities. It could be something like you can't use a mouse, so you're using a keyboard. Or it could be a permanent disability, and it could be a completely temporary one. For example, I was in a car accident two weeks ago, and the airbag hit my hand, and so my wrist was, it burned and tingled, and it was not fun. But the annoying part of it was that I work on the computer all day. So my right hand was kind of out of commission for a few days while it got better, and I noticed a lot of how much I used the keyboard and the mouse, and I was like, oh geez, this is not fun. I can't imagine if it was like a permanent thing. I might lose my mind. So it's just things like that to keep in mind. It might not be a permanent disability, but a temporary one, but that might keep someone from staying on your site or taking in your content. And then finally, things like screen readers or eye tracking or things like that. A lot of people will use screen readers as the facts mentioned earlier. So things to keep in mind. When you're creating your site, make sure that the code or the alt tags, for example, make sense. Because when you use a screen reader, it reads everything. So if it doesn't make sense and it's not laid out properly, it'll just sound like a bunch of gobbledygook. I would recommend checking that out on your computer. If you have an Apple, you can use Apple VoiceOver. There's a lot of different programs for Microsoft computers. Try it. You'll see how annoying it is if it's not properly set up. So there's all sorts of different assistive technologies. Screen readers, as I just mentioned. There's also Braille display, Texas speech, voice browsers, voice recognition, keyboard navigation. These are all different kinds of tools that people will use to access your site in however they need to access your site. So screen readers specifically. These are some of the most common screen readers. I would recommend checking out one of them, all of them, any of them, because you will get a much better understanding of what I'm talking about just by experiencing it. So now what makes a website accessible? We've talked about all these things, all the disabilities. So what makes a website accessible and how can you know that yours is accessible? So there's things like types of content, their size, complexity, development tools, the environment, who your audience is, all these different things that you should be thinking about. And I know that it's a lot, especially if you've never thought about accessibility before, but it's a lot more important to do one thing than do nothing at all and start with baby steps and start thinking about it, even if it seems overwhelming right now that there's so many things I'm not doing anything right. I'll just not make it accessible at all. Please don't think that. Please just like do at least one step. It's not as hard as it looks, and if you guys have any questions, you can always ask me now or later. I just like saying that throughout because I can see some eyes glazing and being overwhelmed. So we're going to talk about content. So when you're building your site, if you have intuitive navigation, properly labeled links and images and you have user-friendly design, people are going to stay to read your content, right? If your site is properly set up, then they're going to be willing to stay to look at more of your site. If they come to your site and your homepage is a mess, for whatever reason, they're not going to stay. Still with me? Yeah? Okay. All right. So there's a lot of different strategies that you can think about. So for content, you think about the auditory, the visual, and the tactile content, like how you're doing it. For example, the videos that I mentioned earlier. If you have videos, think about the sound. Think about not everyone is going. Even if it's something as simple as, oh, I don't have my headphones and I'm in a coffee shop, so I can't listen, I can't watch your video. I do that all the time, and it's really helpful whenever a video has captioning on it, because then I can at least, like, basically figure out what the video is about, even if I can't listen to it, right? Also, thinking about your presentation. The first example with Apple's website, it was whether you had color blindness or not, you could still completely read the website and the content of the website, right? So think about that when you're thinking of a background or images or putting text on top of something. Make sure that it is really, really distinguishable. If nothing else, the image can fade away. If the image is not important, but the text is, make sure that the text is distinguishable. If the image is important, then make sure that, no matter what, if you look at it in black and white, print it out on a piece of paper, I actually don't, that's a waste of trees. But look at it with a black and white view. Like, you know, do a printer preview and look at it in black and white. Something, anything, just make sure that it is legible on all accounts. Not just thinking of really crazy situations, like stripes on top of a plaid or something. Definitely don't do that, but even for simpler ideas, like putting red on top of green might be okay, sometimes depending on the kind of red and green that you're using. But if you put, like, from the eyes, from the color wheel from before, if you have all the colors that are all together, then they're all gonna blend together if you have color blindness. Does that make sense? Okay. I like that this row is, like, nodding and going with me. It's very entertaining and very helpful. Thank you guys. Yeah, it's good to sit. All right. So, evaluation tools. So now you've built your site and now you want to figure out, all right, I already built it. Now I have to go back and, like, fix it. What? So, these are some different evaluation tools that I would recommend you guys look into. By the way, I have put these slides up. They're on my website and they're also, I tweeted them out. So right before the talk at about 1045. So if you guys want the slides, all of the information is online and all of those are linked. So you can click on it and go to their respective websites to learn more about them. So, just as a heads up, if you can't write fast enough or whatever. So they exist. And, all right, so implementation. The thing about, yes. It's pretty easy to read online. It's not as great with the projector. But it is actually pretty easy to read online. Yeah. Better? Yeah. Okay. Sorry, you guys. My bad. Can you guys see now better? At least, if nothing else. All right. Yeah. If you follow along on the website or on your computer, it is a lot easier to read. And which is why I put it up. Yeah. So if you look up on Twitter, just at Nancy Tanke, which is my name. Or if you go to NancyTanke.com, it's the latest post. So. T is in Tom. H-A-N-K-I. Thank plus an I. Let me know when you guys are good. Yeah. You guys good? Awesome. Awesome. Yeah. Kind of. It depends on which one you use. Yeah. There's not really like an easy way to break that one down. Yeah. I recommend looking into them because looking at different ones will also give you a better idea of how each one reads it. So, all right. Next. Implementation. So the cool thing about accessibility is that if people start using it or demanding it, more people will start using it and or demanding it, right? So if developers create tools, then people are going to use those tools. If people are using those tools and they'll ask site creators to make sure that those tools can be used on the site. If the site creators get asked to make accessible sites, then they'll be asking for accessible tools to make them accessible, right? So you have the nice little circle of life going on. Yeah. Okay. So a little bit more in-depth is that you have all these different things. So you have browsers, media players and assistive technologies. They all go into users who are going to use them and then they're going to go in and because they're using them, they're going to demand that they be able to be used, right? And so then developers are going to say, oh, well, now I'm being asked to make these things, so I guess I better start making these things because I have people asking me, right? So you have the nice, it's a little bit more in-depth, but a kind of example of why you guys should start using it because even if it seems a little hard to do at first, as more and more people start using it, more people will start using it. Does that make sense? Yeah. Okay. So there are lots and lots of benefits for others when you make an accessible site. There's digital divide issues, mobile access, older users' needs, low literacy, low bandwidth, new or infrequent users. So there's so many reasons why you should think about making an accessible site. People think that, oh, it's just, you know, well, it's for disabled people, so I don't want to think about that. Or it's only for this, and I don't want to think about that, and it's not true. Accessible sites are important for so many reasons. If you have a really, a site with a lot of content and it involves a lot of things that need to load, but people don't have a good internet connection, then they're not going to be able to access the content on your site, right? So you have, as more and more people use phones rather than laptops, then you also need to think about mobile responsiveness so people can use the sites on their phones, et cetera. There's so many different examples. So now we've talked about all the other people and everyone that's going to be using your site. So that's important, but what is it, what is in it for you guys, the ones that are actually building the site? And does it matter how accessible your content is if nobody ever finds it? So I see a lot of shaking heads, which is very true. We're going to go back to that slide from before. The thing about accessible sites is that when you make a site accessible, you're going to make it more intuitive to use because you're going to make the layout better, you're going to make the content more easily accessible. And you're also going to be using better UX and UI, right? Because that is what makes a site more accessible. So when you do that, people are going to use, they're going to access your content more, period, right? So that's a good thing. You want your site to be well-known. If it's a business, you want your business to be well-known. If it's a blog, you want your blog to be more well-read. You know, things like this. The fact that you make your site accessible is good for other people and it's good for you. Okay? Get still with me? All right. So that example from earlier that I talked about, this is what you see on the left, right? It's my hands with Mindy on them. And you can either say, all right, well, this is image, you know, underscore 5789, right? Or you could say that this is the image source, which is Mindy.jpg. And then you have an alt tag, a girl's Mindy covered hands outstretched. That is a lot more helpful than image underscore 56789, right? And this is also helpful, not just because for screen readers, but it's also helpful for search engines. Because search engines don't know what image you are putting on your site. They can't see the image and say, oh, well, this is a girl with Mindy on her hands, obviously. They're going to see a bunch of pixels. That's all they know. If they see the alt tag, then they can say, oh, all right, so this is a picture of Mindy, a girl with Mindy on her hands. And that means that this is, that's what this post is about, or that's what this image is about. And I can categorize this site as this is what it offers, right? So if the more and more image tags, alt tags that you use on your images, the more the search engines are going to know that that's what you do. So this is especially important for things like photographers' portfolio sites, because, or any artist that uses a lot of images on their site and has a portfolio site for any reason, because most of the content is images. You don't have blog posts. You don't have pages to really describe what you're doing other than the fact that, you know, hey, I'm a photographer. Hey, I'm a painter or whatever. But you probably don't have very many words on your site. If you use any sort of SEO plugin on your site, it'll probably tell you, hey, your post is not long enough. Please use more words. But you might say, well, I'm an artist. I don't have any more words. Look at my painting. It's pretty. So in that sense, because you have the alt tags, it tells search engines what you do and what you're about. So this, I know it's very small. It's purposefully done so because I want you guys to look at the slides, the slideshow later, and go through this because there's no way that you can do all of these all at once in one speech, right? But these are examples of things that you can do. As I mentioned before, it may be overwhelming for getting your site accessible. You might already have spent so much time on building your site and now you're being told, hey, make it accessible. And so you might think that it's a lot of stuff to do. Even if you pick just one thing from this list, you will make your site more accessible and it'll be a good thing. And you don't have to do all 17 things that are on this list all at once. You can go one by one and say, all right, well, I know about this. This I can do. Alt tags. That's a pretty simple thing. It'll take a bit of time, maybe an hour a day or something, and go in and change your alt tags or decide that, oh, well, I'm going to make my menu structure better, more navigable, et cetera, all these different things. So I will read through them really quickly. If you guys do want to talk about them more, you can come back at the end if there's enough time. But providing a clear and proper heading structure and avoiding empty headings. Please do this. Please, please, please do this. Providing descriptive link text. So this one's a pretty easy thing to do. Whenever you're making your links, instead of saying, go check out this. Instead of saying this, say go check out Bob's Burgers website. Instead of just saying this or check out here or anything like that, make a descriptive link so then people know that this is where I'm going to be sent, rather than just being like, oh, I'm going to click on a link. If they happen to be computer savvy and can hover over the link and see the little thing in the top bottom left corner, then they might know the URL. But if not, if you're using a screen reader, for example, then it's just nice. And even if you're just reading the page, it's nice to know. Ensuring page titles are descriptive, yet succinct. This is something that a lot of people seem to have trouble with sometimes. And making the title short, it helps if you're just thinking about, well, I want to tweet this title. How can I make it short? That might help. Just making sure that you make the title as short as you can while still obviously describing what the blog post is about or page. Not relying on JavaScript for things that don't need it. That goes back to internet connectivity issues a lot of times. If they can't load it or for whatever reason they can't load all the content, then they can't really access the full awesomeness of your site. Avoiding mouse-dependent interaction. This one might be easier said than done, but just trying to make sure that nothing is solely dependent on scrolling, like a parallax effect or something like that. Using standard web formats when possible, providing transcripts and captions for videos, identifying the language of pages and page content, allowing multiple ways of finding content. So a search bar, a site map, a table of contents, some sort of clear navigation of some kind. Providing useful links to related and relevant resources, ensuring URLs are human-readable and logical. So try and make it a URL that you can read out loud without using a bunch of numbers and letters, for example. Presenting a clear and consistent navigation and page structure. I cannot emphasize this enough. Please make sure that if you're using categories or tags or you're using parent categories and subcategories, make sure that they make sense. Please. Avoiding CSS and other stylistic markup to present content or meaning, defining abbreviations and acronyms, and having unique and relevant titles and meta descriptions. So yeah, those are just some things. There's all sorts of other things you can do. These are some of the simplest and easiest things to go through, especially when you're first starting out and trying to make your site accessible. Which one? So basically, when you're using CSS, right? So if you use CSS, you can basically designate that something is different. It looks different, right? So making sure that you're not just using how it looks to designate it from the rest of the content. Does that make sense? Mm-hmm. That's one of the main things. Yeah. No worries. So what that means is that, for instance, if you designate something in your CSS as, okay, so you said, all right, click the red something. But whatever button that is. Button or element, you know, whatever you're making, ask one to do. So to not designate that by color alone, what that means is, you know, a better way to handle that might be to say, click the product button on the left. Click the, or activate the read more link. I'll repeat it. Oh, sorry. So, stand up. I'm totally taking over your talk. No worries. If you don't know me, I'm Amanda Rush with the Work for Successibility team. And basically what we do is help work for our success. So this is what I do. She's a really important person. Yeah, I like to tell myself that. This is what I do. This is my job. And I do this all day long. I do accessible websites and accessible applications and accessible plugins for my clients. So what she means by not using CSS alone and using color alone essentially to distinguish something on the website is, so for instance, if you have a, you're pointing out products. Now I mean, you're pointing out a particular image or something that you want them to perform. So I'm just saying, just click on the red box or where to bring up the particular product. A better way to deal with that is to go ahead and put by all means use the CSS and style your product links or style your image orders or things like that for this one. But what she also means is provide some kind of text that says click on the, or choose the, whatever product link. So choose the link for red shoes or something and then make sure that when you provide that, use your CSS. But if there's an image involved, make sure you have an alt attribute which is going to be a little alt key made of something and then your description of whatever you're providing and make sure that that same link or button can be activated by a keyboard. So you can totally use your color and your CSS and you can make it look pretty. That's fine. Just make sure that you provide an alternative way for somebody who is using a keyboard or who is using a screen reader or who is color blind to find what it is that you're trying to actually get them to get to because if they can't find it and if all you're doing is depending on color alone and your CSS alone, they're not going to click on that and if you're doing e-commerce or something like that they're not going to buy your product. And there's a lot of us that spend, we don't have to spend on online because we don't drive or we're going to shop online or things like that. We don't have to make it too late to take us to the store. So we will gladly buy your products online but if we cannot find and cannot access what it is that we're looking for on your site then that's a lost sale. Thank you. That was awesome. And very, very important. Go ahead. Okay. I haven't seen that but I'm sure somebody else in this room has because I saw nodding heads about the CSS. Interesting. Yeah, if you want to talk afterwards we can talk about that. I haven't seen that, I'm sorry. All right, so finally, resources to consider. Again, I know it's not a legible slide. It's purposefully there for you guys to, you can't click on all these links right now but go check it out. Check out all the different resources that there are. I am just a lone speaker and I can only point in all the awesome resource directions but all of these places will have information. They'll either have tools or a breakdown of, it'll be something as simple as hey, this is what accessibility is all the way to something as technical as this is how you need to change your code to become more accessible. This talk is specifically supposed to be like an introductory like hey, this is what accessibility is and it's not as crazy or hard as you may think it is but check out these sites because I hope that this at least interested you enough to see more about what you can do and that it's not as hard as you may think it is. And finally, I would like to leave you with this final thought. Look at it this way. So you're not, you're not the only person that cares about your blog about bunny rabbits or you're not the only person that cares about your store that's selling jewelry, for example, right? So make sure that like you're, because you're not the only person that has so many other people that are going to be accessing your site. Whether it is someone that can't drive, for example, they're going to be looking at your e-commerce store and if you can provide a really good experience then they're going to buy from you because you're the one that actually cares about their business because that's what you are. You're a business. You should care about your users and your customers. And so just think about the fact that there's so much more than just you who is accessing the site. So finally, and this is basically, you were basically creating what is this and you're just, you're turning it into this and that is what you're doing to your site when you're not making it accessible. This beautiful image is now covered up and no one is going to enjoy it. So, homework for you guys. I'm going to be checking on all of you. Just a bit of homework. Check out some sites that you go to on a regular basis. Open up a screen reader and look at the, and listen, not look, listen to the screen reader read the site out to you. Is it legible? Do you still like going to that site because odds are you probably won't. So just keep that in mind when you're making your own sites whether it's for yourself or for your clients or just, you know, talking to a random person that says, oh, you make WordPress sites. What do you do? Just tell them about accessible sites because you'll be cool. But just think about that and try screen readers and don't try just one, try different ones because they all have different features about them. So just check it out. If you have any questions, I will be here and I'll also be there. And yeah, that's it. Sure. So the basic idea of digital divide is the basic idea of digital divide is that you have different levels of experience of people with digital technology, right? So you have people that are, you know, you have two-year-old toddlers that can totally set up your iPad and they're totally good to go and then you might have people that have never really used technology as much or they don't, you know, for example, I taught my mom how to use a mouse a few years ago. Like she didn't use computers before because she didn't use a mouse and so like the idea of teaching even a mouse is a very interesting concept. It's very, like, intuitive to us now, but it's weird teaching it. So basically keeping that in mind that there are people that will know, oh, I can right-click and do things with this site and do stuff, or there's people that might not have no idea how to access your site in terms of if there are fancier, quote-unquote fancier things that are on your site and ways to interact. Does that make sense? Mm-hmm. Yeah, exactly. So in terms of accessibility, I should have explained this earlier. When I talk about accessibility, it's not just for keeping disabilities in mind. That is really important, but it's also keeping in mind that it's accessibility for all users, right? It's like the quote at the very beginning. It's to keep in mind the fact that there are people that may only be looking at your site on a mobile phone. They may only have a really slow internet connection. They may not really use technology that much. They may not really know how to read as well. They may not know how to hear. There's so many different ways that people interact with technology. And to keep that in mind when you're creating a site. If you're creating a site for a local florist, for example, you may not be as worried about accessibility. Maybe you still should be, but people will argue about that. But if you're making a site, say you're making a blog, for example, about running, right? You might think, oh, I'm running, so I don't need to make it accessible. Only people that run are going to want to look at my site. That's not necessarily true, first of all. Second of all, even if you're not thinking about disabilities, you should at least be thinking about other things that people are accessing your site on their phone or they don't have a good internet connection, etc., etc. There's so many other things to think about other than just disabilities. That's the one key takeaway I would really like you guys to take away from this is that accessible sites is not just for people with disabilities. It is very much important to make sure that you keep those in mind, but it is also to make sure that it's accessible for all people, period. Yeah. There's kind of a legality. It depends on where you are. For example, the European Union is a lot more strict about making sure that sites are accessible. I've even gotten tickets from users in the EU that have said, hey, I need to make the site more accessible. How can Jetpack do it? Kind of questions. America is not as on top of that game. It's not a legal requirement to make all sites accessible. There is a growing trend of government sites have to be accessible. And because of that, a lot more companies are requiring their sites to be accessible when they're made. So you may be dealing with clients that are requesting accessible sites. Or you may just have clients that are interested in, hey, what else can I do to make my site better? And then at that point, you can introduce the idea of accessibility. But there is no blanket accessibility legalness about it. Yeah. Yeah, there is. There's a lot of conversation happening, but nothing officially signed. Oh, okay. Nice. Did you guys hear that? No. So the DOJ has released the latest draft on the guidelines, but it hasn't been fully passed by courts yet. Because courts are divided. Okay. Thanks. One question I have is about we try to use this tech, you know, like we see a lot of bigger tech, more tech, please magnify the tech one. Uh-huh. There's some plug-ins we use in other sites trying to make it accessible. Sure. But it kind of conflicts with other plug-ins that have made it very hard. Right. Do you have any suggestions? I don't have suggestions on what other plug-ins you could use, because unfortunately there are often plug-in conflicts whenever you use a site, because you do have to balance between how do I make the site, the tech's legible, while also keeping your design intact. Because the bigger the font gets, obviously things start shifting around, especially if you have responsive design. Something to keep in mind is that people do end up magnifying their screens on the browsers. So it's more important that the content is organized properly than it is, like, it should be big enough. It shouldn't be like size 10 font on your browser, right? When you create your site, please don't make it size 10 font. That doesn't mean that it needs to be size 40 font. It just needs to be a legible size that covers the largest population number, right? And then, I know that I'm sounding like I'm contradicting myself. You should make your site accessible. There does come a point where other technologies come into play. For example, I had a classmate in high school that was legally blind. She had much larger... She could see, but she was still legally blind, so she had much larger textbooks, for example. But then, she had her own personal computer that magnified the entire screen, and so she was able... It wasn't just, you know, clicking command plus, plus, plus, plus. It was actually a magnified screen on the whole. So there are things like that that other people are using that you can also keep in mind. But I would definitely defer to the person in the front row who is blind more than me. What can we do to... If we need to provide the text magnifier? Because that is an requirement in certain scenarios that we work with. But we have a hard time doing that in WordPress environment compared to UBLA. There's a plugin called WP Accessibility by Joe Wilson. On the WordPress plugin repository that does provide... It does have the... Does it have the magnification thing in it? No, it actually doesn't, because according to the WCAG 2.0 guidelines, what actually needs to be provided is... So users need to be able... They need to be able to modify it, not that the site itself needs to provide that modification functionality. So as long as you have not blocked, say, Zoom on your mobile responsiveness, then you've covered that guideline. As long as you are allowing for a user to either be able to do Command Plus or Control Plus on Windows or use their magnification software, then you've covered that guideline. And that's included for section 508 as well, which is the government purchasing standard for the United States that has guidelines as well for what websites you're supposed to include. So the website itself doesn't necessarily need to include that functionality, but you just need to not block it. So in other words, don't stop somebody from being able to magnify their site, but you don't necessarily need to include the technology itself on the website to magnify. Does that make sense? Does that make sense? Did you guys hear it? Whoever raised their hand first. I don't know that there's a talk about a class that's in play right now, but I do know that, for example, at WordCampUS that happened in December, there was a very large accessibility meetup to try and make sure that the content that we have, the documentation and everything about making sites more accessible actually exists and is robust enough to help with that side of things. But would you know, Amanda, if there's a class? So there's nothing, like there's not a team effort in the WordPress space for a class just because we've got to figure out, okay, so if we do this, then you know, okay, how do we make it free? Do we make it free and in charge? So there are people in the space in the WordPress space that do accessibility stuff, and we are basically accessibility consultants, but I don't think that idea has actually been floated. You know what, I will, it's nothing else, then I'll float it on my own personal Twitter and go, hey, so whoever's interested in like a WCAG for developers, or WCAG for content managers or whichever, you know, but there's not an official joint WordPress effort to teach WCAG because, or 508, partly because 508 is about to be modified, at least that's what the government's telling us at this point, that there is an actual date for when we're going to release a standard, and partly because there are, the W3C itself, the World Wide Web Consortium does have a lot of documentation on, so here are the WCAG guidelines, and here's about 400 or so pages on how to understand and how to apply those guidelines to actual web content, but there's not a joint WP accessibility effort to say we're going to get together and develop a course just for the WordPress community and say, you know, we're going to teach you guys, but I don't know, like I might actually float that on my own Twitter and see what the interest looks like, and if there is enough interest in it to make it something that would be viable, just because it would take a lot of time to do, to put A together and B to actually run, if there's enough interest, then yeah, I mean, I'd be willing to do it, but at this point there's not like an actual, there's not an accessibility team effort to say we're going to teach you WCAG from the ground up. Cool, yeah. It sounds like, is this correct in saying there's different degrees of accessibility that you don't have to do everything at once, but here's everything you could do. So what does, for example, you don't have accessibility, do you make it like black, white, or accessible, or you're not accessible? I don't see it as black and white. I think that you can make your site more accessible. I say this because there isn't a legal requirement that says you have to do X, Y, Z things to be an accessible site. The EU has those kinds of requirements. You're either accessible or you're not. I guess once you are accessible, you can technically become more accessible, but there are certain points, checkboxes that you have to check off, to become an accessible site. So there isn't that. When I have the checklist of things that you can do, these are things that you can do. If you do one of them, then cool, you're on your way. If you do all 17 of them that are on the list, then great, you're going to be really accessible. It'll be great if everyone in this room went and did all the things that are listed. And those aren't the only things. There are many things. There's a 400 page guideline, or a book of all these things that you need to do. That's also in that list of resources. It's linked. It's a lot of stuff, and it can be very overwhelming. So if you already have your sites ready, I don't recommend sitting down and reading it all at once, because you might want to chuck your computer. So just start off one by one. Try these different things. Some of them are really simple. Some of them are not as simple. I won't just stand up here and say, oh yeah, it's really easy to make your site accessible. It's not necessarily really easy, but that doesn't mean that it's not worth it. Thank you guys. You guys have been an awesome audience.