 Okay, so I know you'll all have one question on your mind right now. How did I get this black eye? So I was at a bar the other night with the buddy of mine We had a few drinks and we were talking about work and we started talking about alt text and Things got really heated because when you talk about accessibility things get heated and maybe a few punches were exchanged because Think you should put alt text on all images and he said no don't put alt text on them And yeah, it was a fight. So if I get anything wrong in here see me out back and we'll discuss it Okay, so my name is Kevin Lamping I Go by K. Lamping on Twitter I'm a front-end web developer. I'm a native Texan as well. I think that's more important as My slides disappear in me. That's always good. There we go. I Was born in Bernie, Texas anybody know where Bernie Texas is. Yeah, beautiful location. I've Spent my entire life in Texas. I spent a few years. I went to school up in Dallas and Then I moved to Austin spend a few years in Austin as a developer and then I spent a few years Not a few years. I spent about six months as a high school teacher teaching web development And that was a really interesting time in my life I'm currently living in San Antonio with my wife and this is my son He's gonna be three in March and you'll see him later and in the talk Six years ago when I my first job in my first job out of college I started getting involved in in web. Sorry in accessibility Was working with two other web developers really great web developers We were tasked with making an eye care website Accessible you can imagine why an eye care website would need to be accessible and this really introduced me to accessibility From a best practice standpoint and ever since then I've always been interested in accessibility. How can we make sites accessible? Before I get into that I need to ask all of y'all a favor There's only a few y'all out there who have laptops open But if you do have laptop open or a tablet open or a phone open if you can bring up your Site that you are currently working on or you've just worked on or Your favorite site that you've worked on your least favorite site that you worked on Just something to get in your mind and then for those of you who don't have something open If you could just think of a site that you've worked on can be recent old it can be good or bad We're gonna be using this website and kind of thinking about it using it as as an example for What we can do to improve accessibility So these are the WCAG 2.0 or WCAG or WCAG 2.0, whatever you want to call them guidelines They're hard to see but I assume all of y'all have all these memorized, right? Maybe maybe not. No, okay. Well, it doesn't matter Thinking of that site or you're looking at that site that I talked about Go and raise your hands if you know that that site meets all of these guidelines Yeah, I don't think I have a site that meets all those guidelines either How about 90% 75% Okay, good. If you could do me a favor if you have any feedback, I'd appreciate to hear it You know 75% is pretty good. So if there's something That you think I should know I'd really appreciate to have any feedback because I'm always learning We'll get to those again later your job today is I'm going to present some techniques to you to improve HTML5 accessibility That site that I mentioned I want you to think of okay. How can I apply this to that site? now That site I'm going to mention that site again How many of y'all were paid to make sure that that site was accessible raise your hands if that was one of your deliverables This website will be accessible Okay, less than half of you two or three What that means to me is that? Web accessibility is something that we developers have to care about We're the ones who have to put the effort in we're the ones who have to ensure that our sites are accessible nobody's going to be Cracking a whip on us saying hey make sure this is accessible. So That's what that means to me Now I've got good news and I've got bad news. Let's go ahead and start with the good news good news accessibility is easy For the most part HTML is accessible you're building a simple site It's pretty easy to make it accessible because HTML is accessible to begin with you get your alt text in here in there on on your images You get your labels on your forms you use proper semantics like headings that sort of thing and chances are if you've got a If you've got a basic site, it's going to be accessible So I'm going to skip that stuff because that stuff's been covered before there's plenty of good resources out there I want to talk about HTML 5 accessibility today and the good news is that for the most part what I'm presenting today It's pretty easy to implement Onto the bad news accessibility is hard When you get past the simple stuff when you start getting into javascript and you get into dynamic pages it gets really hairy and Not even really tricky stuff even trivial or sorry even simple non trivial stuff like having a drop-down or a pop-up window or even a modal Having to manage focus make sure that it's keyboard accessible Make sure that when it pops up a screen reader read it reads it that can get pretty tricky Trying to meet all of these guidelines It's tough accessibility is a hard thing to do and So as a web developer you not only have to support all the browsers out there and make sure they're all Compatible and all the different devices You also have to include screen reader support and you also have to include Assistive technology support other other than screen readers, you know, you have screen magnifiers. You have different input devices It's really complex and so the truth is accessibility is frustrating It's difficult and it takes time Don't let anybody ever tell you that accessibility is the simplest thing in the world Because unless you're building a one-page site that says my name is so-and-so It's gonna be tricky. You're gonna have to work on it. You're gonna have to test it because of this We have difficulty with it. We forget to follow the guidelines, you know I there's times when I build a site and I go, oh my gosh I never checked whether it's accessible or not and then we also let ourselves off the hook We say we're gonna check we'll check it later. We'll we'll test it later. We'll add an accessibility later I know the basics of accessibility, so I don't need to test for it. We do all that sort of stuff So I want to begin before we get started. I want to clear our conscious Conscient conscience And so what I'm gonna do is I'm gonna bring up my Catholic heritage And we're gonna have a quick little confessional so that we start with a clean slate So if you could repeat after me out loud or in your head, I don't care whichever one Bless me father for I have sinned It has been so many days since I've last used a screen reader I'm I'm sorry for this and the sins of my past life Especially for that one website that I should have checked accessibility on and I just didn't do it Amen, okay. We're all forgiven. We're all clean forget about all your sins of your past Let's look at accessibility Now I mentioned accessibility is hard and it's difficult for anything non-trivial. So why do we do it? I like to think it about think about web accessibility like this when we're developing We have a choice whether to make our application accessible or not The user with a disability, they don't have that choice They don't have the choice of saying I'm gonna turn off my disability so that I can access this website I'm gonna turn off my Disabilities so that I can get past this capture form and then once I'm past it. I'm I can turn it back on So basically we are the gatekeepers We are the ones who decide whether users have access to our side or not Just a side note. I was presenting this to my wife You know as a kind of go going through it and she's great for listening for me to me for 40 minutes about something That she really doesn't know much about and probably isn't ever gonna have to use and She was like, what is that? Who is that? And I was like, it's Ghostbusters. She's I've never seen Ghostbusters at that point. I knew that I failed as a husband to my wife Well, the good news is that accessibility is good for you Accessibility when you improve the accessibility of your website, you're gonna improve the usability of your website What I mean by that is This is a photo that my son took you saw my son. He's about two and a half years old when he took that photo Two and a half years old. He knows how to use a camera phone That's that's usability He knows how to use YouTube or he knows how to use my phone to get to YouTube to watch the video that he wants Anybody ever work out there any parents out there of toddlers ever working on your screen? And they go up to it and they try and scroll up and down and they get frustrated when they can't scroll. Yeah, it happens How about when you see somebody a little kid with a magazine try and use it like an iPad it's pretty cute to watch so I mentioned all of this because After Steve Jobs passed away Stevie Wonder had some unusual praise for him that you don't normally that he didn't always get praised for he got praised a lot for the accessibility side or sorry the usability side of The iPad and the iPhone But not so much the accessibility side and I've got to find the actual quotes here that I'm gonna go through Sorry, you think you prepare but you don't Okay, so this is from that interview quotes that Stevie Wonder had to say The one thing people aren't talking about is how he has made his technology accessible to the blind and the deaf and People who are quadriplegics and paraplegics He is affected not just my world But the worlds of millions of people who without that technology would not be able to discover the world anybody here think that iPhone or iPad could be accessible to somebody who can't see the screen That kind of surprised me when I first learned that it could be and I was like how they wouldn't know where to press How are they gonna figure that out? Well, they took the time to think of a completely different Interaction method and so instead of using instead of precise Touches on the screen they use gestures and so that's opening that up and be I'll talk about Give another quote He developed garage band so now a 15 year old kid can be in his bedroom with his iPad playing around and come up with Unbelievable ideas which can be taken to the next level He has leveled the playing field So I mentioned my son again. I'll bring him up even more When we first got the iPad he was around one I went ahead and gave it to him and I turned on garage band and he started playing with it He started making music and that was amazing for me because the simple act of removing the mouse from that Interaction opened up this technology to him. It gave him the ability to create and so even though that's not necessarily a Accessibility thing for the iPad It opened up the world to somebody who couldn't use a mouse my son at one years old He couldn't use a mouse, but he could press the screen and so that's how I kind of think of accessibility and usability combined Quote another one from the from the article I thought I printed this one out and I didn't so that's bad His company made it accessible without screaming. This is for the blind. This is for the deaf It was just part of the OS. It was just part of the product So that's what we have to think about is we just make it part of the experience. He left us with the final Steven wonder left us with a challenge I'm just hoping that his life will encourage and challenge those who are living still to do what he has done You just make it one of your applications It's in your technology that will then create a world that will be accessible to anyone with a physical disability So it turns out that when you make your site accessible Stevie Wonder might just call you up and say thanks. So you've got that going for you but Steve Jobs, you know, I mentioned that he he did it and and Stevie Wonder mentions that did it for the love of the love of the technology Steve Steve Jobs, he didn't do it to meet government regulations. He didn't do it to meet guidelines He did it because he wanted to make this technology accessible to anyone regardless of the disability And so that's what makes accessibility worth it to me. That's what makes fighting accessibility worth it to me All that said let's get to it. What does HTML 5 mean for web accessibility? We'll start off by looking at the section and the new sectioning elements How many of y'all have used the new sectioning the new section elements? Great. Okay So let's look at some browser support from an accessibility side. We'll start off with header on header in IE Safari and opera header gets reported as a div now This doesn't mean that it's not supported in the browser from an HTML 5 perspective It means that the browser doesn't expose that that element as a header to anything besides the browser And I'll get to what that means in a minute Chrome Reports it as a section. So it's a little bit better than than a div, but Firefox is the one that gets it right It reports it as an actual header I need to mention at this point. This is only for Windows on Mac. It's different on Mac opera Chrome and Firefox mispronounce it as a div and Then Safari is the one that gets it right This support information comes from HTML 5 accessibility calm They've got support for all the different HTML 5 elements out there It comes from September of 2012 the web is moving past So some of this may have changed. It's always best to test your stuff to make sure that it's got the latest So that's header. Let's look at footer Picture is pretty much the same IE Safari opera on Windows. Don't support it. Chrome and Firefox do and Then on Mac opera and Chrome don't support it and then Safari and Firefox do Now two elements down not that great a support maybe 50% at best The problem is it's bleaker than this when we talk about Support it's it's a broader term the browser is not the only one who's responsible for having support The assistive technology must also work must also be upgraded to make sure that it understands what the browser is telling it So what I mean by that I have to get into the relationship between the browser the OS and the assistive technology When you load a website in a browser that browser will expose its Exposed the structure to what's called an accessibility API the accessibility API is part of the operating system It's kind of a middleman between the software being run and the assistive technology that's Trying to access that software. So here Safari will talk about the web page to the accessibility API And then voiceover will listen for listen to the accessibility API for that kind of information this might be a simplification of what's going on, but I just wanted to get it in in an easy to understand format What this means is that support needs to happen in two places Not only does the browser need to support and talk and speak the right language the HTML5 language to the accessibility API The assistive technology voiceover in this instance needs to listen for that and needs to understand what the browser is saying So if you have a browser that exposes accessibility and exposes these elements Exposes accessibility is not the proper term sorry exposes these elements But the assistive technology like a screen reader it doesn't listen then there's essentially no support and then it works the other way if the Screen reader is listening, but the browser never says it then it's equally as useless To make matters worse We all know as web developers that users don't upgrade how many y'all are still supporting IE 6 or IE 7 Yeah, because users don't upgrade and That's a problem because support may increase in the newer in the newer Browsers and the newer technology, but we're gonna have to have backwards compatibility So while we may have HTML5 accessibility support in 2013 2014 We're still gonna have to have to be coding for 2010 Brings me to my question. Is there any hope for us to make HTML5 accessible? Because it it's useless until browsers assistive technology and users upgrade their stuff Well, when you're wearing a belt and the belt doesn't work It's time to put on some some suspenders and I'll talk about what those suspenders are We get back to our sectioning elements while browser support is low is still It's still maturing on the HTML5 side There's a backup and that backup is called aria raise your hands for those of you who know what aria is And I'm not talking about the opera singing. No, okay good aria it stands for accessible rich internet applications and The good news is that it's got pretty good support out there There's a lot aria has actually been around since before HTML5 and so browsers and assistive technology has had time to To upgrade their stuff and users have had time to upgrade their stuff So aria works by adding semantics to your HTML What I mean by that is if you create a tab view on your page You're gonna do it with a div around your around the whole thing UL for your tabs and then divs for your content Well with aria we can add these role attributes and we can add other aria specific attributes to our elements to add semantics for For browsers and assistive technology that's listening for those semantics So we've got HTML5 Support in some browsers, but we've got aria support in a lot of browsers Well, the good news is that we can use both we can combine them and by combining them we can Drastically improve HTML5 accessibility support. Yes. Yes. So the question is is the role attribute part of the w3 spec I Believe with HTML5 it is so I think if you're using an older validator that it will throw a warning But I'm pretty sure with the latest HTML5 Validation it doesn't throw a warning Throw a shoe of me shoe at me if I'm wrong Yeah, yeah, but if it fails validation it fails validation. I'd much rather have accessibility support Okay, so Let's look at this header tag. How do we improve accessibility support for header? Well, it's pretty easy We're gonna add a role attribute. So header role equals banner We get to use the same HTML5, which is really great. We have a background sorry a backwards compatible attribute so that assistive Assistive technology that doesn't understand HTML5 can still understand what you mean. So it's basically a win-win situation Footer footer role equals content info the names don't always match up header banner content info footer They don't match up. That's unfortunate, but it is what it is I'm gonna go through these pretty quickly because you can find all this stuff online searching Aria roles you can get a full list of it and there are some good diagrams out there as well Nav nav role equals navigation almost one-to-one there a side Sure Yeah, so I would say that these were up there before HTML5 came out and then Yeah, yeah, and so with our goal I graded out here because I didn't I didn't have support information You can find support information for how well these roles are supported Some of them are newer than others I couldn't find anything go ahead and use nothing. Nothing's gonna hurt if you do use it Section section does have a role of abstract, but abstract is sorry section has a role called section Or a complimentary role called section, but it's an abstract role There's another an abstract rolling because it's an abstract role. That's kind of programming thing So the W3C doesn't recommend that you use a section role Just that's just the way it is as an alternative. You can use a role called region region isn't as simple as Having a section one would be it's a little complicated. I'm not gonna get into the details, but I want you to know that it's there Here's an instance where Aria kind of helped shape HTML5 in the original HTML5 spec they didn't have a main element Aria did and Because of the efforts of the accessibility community, they were able to push and push and say we need a main element and so Here we have an instance main just got added to the HTML5 spec and We have an instance where Aria shaped HTML5 There's a little bit of repetition here, and that's just the way it's gonna be That's the price you pay for backwards accessibility or backwards compatibility, but it's accessible and that's what matters Okay, so I talked about that website that you don't have in your mind And if you don't think it right now that you can use a quick update to your website You can add a couple Aria attributes I'm gonna tell you this is a great quick win to improve the scannability of your website screen readers support Aria and What they can do is get a quick outline of your page. They don't want to they don't want to get to the navigation They just want to get to the content they can skip to it. They're done with the content They want to get back to the navigation. They can easily skip to it because you have those Semanto Center Okay, so those are the section roles. Let's talk audio and video. Anybody using audio and video up there? Yeah, a little bit. Two or three people. I haven't had a chance to use audio or video yet I do want to use audio because of the way that you can stop and play and skip the certain sections I'm hoping to get a chance to so Let's look at what What we can do from an accessibility standpoint there now I spent a lot of time talking about screen readers But just because your site is accessible to screen readers and that is reusable in a screen here It doesn't mean that it's fully accessible to all the different disabilities out there So you need to consider others in all your accessibility testing people with limited mobility or people who are hearing in here Parkinson's disease is one of the most common Nervous system disorders for the elderly. It causes shaky hands, shaky arms, and that makes it difficult to use a mouse Just as my one-year-old son has trouble using a mouse Somebody with Parkinson's would have trouble using a mouse and it's easier for them to use a keyboard Anybody entering a form want to have through it to get frustrated when they get to the last form field They press tab and they don't know where that focus went Yeah, I get that and I'm like am I on the submit button? Am I not on them? Am I on the cancel button? So I actually think that here's another case where you improve the accessibility by making sure that your keyboard is accessible You improve the usability as well So HTML5 really helps with this really helps improve key work support and support for those who are hearing impaired or Don't have a pair of headphones and don't want to play music across the entire auditorium or where they work So they're trying to watch a video, but they don't want to they don't want to have the sound on Because HTML5 helps because it provides a standard to follow for the browsers So the browsers can implement one single consistent control mechanism That has built-in keyboard functionality And so it doesn't each developer doesn't have to reinvent the wheel the browser doesn't once the user Understands what those controls are and understands how to operate them. It's just that standard that helps improve accessibility across the board and They have keyboard support is for these controls is added in a lot of browsers already So by using audio and video for browsers that support it you've already got accessibility both in that's one of the One of the great ways that HTML5 helps accessibility If you want to roll your own controls, you can make them accessible use the button I highly recommend using the button to Build your controls because if you use a div then you can't tap that div There's tricky hacks that you can use to get to it But use a button It's a simple thing to do and then you have custom controls for your audio or your video But it's still accessible. I Mentioned here you can pair of users or folks without headphones in a busy place There's a track attribute for audio and video and so with track you simply point to the caption track they have and that's a VTT format called Web VTT almost all the Modern browser support Web VTT now Web VTT now Then it provides us a common captioning track format so that we know how to write our tracks and they use They're available across all the browsers So to add that track you do you add your track tag with the proper attributes and You add inside your video tag and you can do this with multiple tracks for multiple languages. It's really great so That's that I do want to make a point that support is out there, but users will slow to upgrade and so you need to provide back and Flash can be that backup as long as you code it in an accessible way. Yes flash can be accessible You've got to try out you've got to try for it. You really got to put in the effort to make flash accessible There's things to watch out for things to be careful with it. You do go that route, but it is an alternative There's you can use a library that's already built It's got that that backwards compatibility built in and that way you can More easily get your stuff out there without having to do too much work. This is a video.js If you do use the library make sure you test not you can't be guaranteed on anything Okay, moving on we've got about 10 minutes left. Let's talk about figure and pick caption. These are two elements that tie Captions with images, so we've always been able to do this. We just happen to do it Screen readers when when they're going through the page when the user is using a screen reader going through the page They kind of have to guess that this image goes with this caption And pretty good pretty easy to do that But if you try to get tricky with it and what your image to be in some other element in that it's harder to do So we've got figure and pick caption at semantics. It doesn't replace the image tag It just adds structure to it. It creates this this This relationship between the image and the pick after kind of combines it together And you can even use multiple images or you can use a code tab or you can use any other thing that you want to say This is my example. This is my Feature and then this is my description about it Now there's limited support out there for figure pick caption, especially from an accessibility side It's pretty much the same as you saw for header and footer Less than 50% So what we're going to do to fix that is use aria aria has a role of group already defined It's not exactly the same thing as figure, but we can use it for the same end So we have a role of group to our figure Element and then we add aria label by C So C is the ID of the caption that we want and those two things tie those elements together Again HMO five is our belt pretty belt and then aria is kind of our ugly suspenders, but they hold us up That being said you do want to have a fallback That fallback is for people for people who they don't have support for HMO five They don't have support for aria, so this is one example of a way to do it It's probably not a perfect example across the board, but it is one So you add an awful photo one and then in your caption you mentioned photo one So you create that textual tie there It's not a strong tie, but it gives users a hint of what's going on I mentioned this isn't ideal, I also mentioned that accessibility is hard and it's hard to get right You know, we've had to cover a lot of bases here, three different ways to code pretty much the same thing Accessibility is hard, that's the truth So you work at it and you do the rest of the thing Talk about Canvas real quick, it wouldn't be an HMO five talk without talking about Canvas Canvas, it's got limited accessibility So I personally wouldn't recommend it for any critical flows you have But if we do need to use it, we can provide follow-ups Here's our Canvas tag, how many of you all knew that we could add subdominal elements to our Canvas tag Just like we could with the did tag I didn't know this before, but you can create a structure that matches what you're defining in Canvas inside And that structure in some browsers gets exposed to a screen reader So that a screen reader, instead of having to figure out what's going on with Canvas Can just read the plain age to know that it's familiar with it Now this isn't visible, but it is spoken, the support is there for screen readers And it's also keyword accessible So to provide an example of this, of what keyword accessibility looks like I'm going to open up this page Y'all want to open this up? Give me a second This is our Canvas element, it's very simple, three shapes In our HTML, we have our Canvas tag that already is and it has links on it And then we have this subdom inside of it That's H2, it's got a paragraph, and then it's got links Now these links, if your browser supports it, you can tap to those links So if I come up here, I press tab You can see I'm cabing to certain parts of the Canvas That's not native browser behavior That's actually part of the link itself You can see there's this on focus draw circle And then on blur, we draw our picture So we draw the circle when we focus on it And then we get rid of it, we draw that base picture when we blur And then on square, we draw square What's really neat about this is that I don't have Wi-Fi on But I can tap, if I hit enter, it would take me to Wikipedia Which is the link, so it would follow that link So that's a way that you can provide backwards compatibility for Canvas tags Pretty cool stuff Support, I mentioned support is hit and miss there And then Chrome and Firefox support that ability on Mac It's Chrome, and it turns out that the support was updated Because it's also Firefox, because I just used Firefox for it So okay, the support is updated Now in some of these browsers, support isn't there for exposing that DOM to the accessibility API And in some browsers it is So just be aware of that and always test your stuff One more thing to mention about Canvas is When a user is using a screen magnifier They can have trouble with 3D Canvas elements So you want to provide a 2D callback Because what happens is that from what I gather is they You try to zoom in on the Canvas It doesn't know exactly where you're trying to zoom in on the 3D plane And it just has trouble with that So you want to make sure that you have a callback for that as well Again, you can fall back to Flash for browsers that don't support Canvas It's not fun, but it's a necessary step that you want to take To make sure that your website is accessible at all I mentioned two things real quick about mobile accessibility It doesn't really have to do with HTML5, but it's mobile So the first thing is that you've got a test port Just because you're working on mobile doesn't mean you don't need to do accessibility testing IOS is actually a very cheap, assistive technology Relatively cheap There's lots of people who, with disabilities, they use mobile Because it's a simpler experience Mobile websites are, by their nature, for the most part, simpler than desktop websites They're easier to access And so you need to test your website If it's a mobile website If it's a mobile website inside a web view inside a native app You've got to test for it and don't make excuses for yourself The other thing is that you should use HTML5 for five minutes They've gotten you the support IOS is really good about this Using something like a date picker versus rolling your own It makes it more accessible The browser already has support for it And it's much easier for someone to figure out once how to use that native browser control That you have to figure out your custom implementation That being said, make sure you provide all of this Test your stuff You know, if there's one thing I've iterated over and over again Test your stuff, put the effort into it You would never release an HTML5 app into the wild without testing it Across all the browsers You wouldn't do the same for accessibility testing Any map computer out there, you've already got a screen reader It's called the Waste Open In senior preferences, you can try it out You don't have to pay any money, you've got a screen reader ready to go Windows, you don't have to pay any money You've got NVDA available That being said, not all the screen readers are the same You've got to test across the whole thing The whole range of assistive technology Just because it works in Firefox It can break an IE The same goes, it can work in NVDA and break new jobs If your company has the budget Pushed for assistive technology Jobs can be pretty pricey But if you can afford a $600 phone If your company can afford a $600 phone for testing Your company can afford the latest screen reader for testing as well I had three questions that I posed in my description I want to cover those Does HTML5 improve accessibility or make it worse? Well, I've kind of shown that it's both Canvas, things like Canvas Tag It complicates things It introduces new paradigms That browsers have to deal with That assistive technology has to deal with But on the other side of things You've got input, new input types New tags that improve the semantics I'm personally on the optimistic side and say Yes, HTML5 does improve accessibility Because we're adding this new layer of semantics We are evolving the language to make it better How have screen readers adapted? They have gotten better They are paying attention Maybe it's not as fast as we want it to be But they are adding support in there And then hopefully you know the answer to that This question that you've got to test your stuff Just because you're using HTML5 Just because it has these semantics in there You still have to test your stuff for accessibility The last quote I've got today Is from Isaac Gasmoff And that is It is change, continuing change, inevitable change That is a dominant factor in society today No sensible decision can be made any longer Without taking into account Not only the world as it is But the world as it will be You've got to test your stuff There's two books I recommend For HTML5 accessibility This covers everything From just basic accessibility It talks about the accessibility API out there And then it talks about using HTML5 And accessibility, using ARIA All that stuff It talks about fit capture And it talks about audio, video All that stuff And then you've got web accessibility Which is a little bit older But it's a real good It covers all your bases on accessibility It talks about implementing engine and enterprise All that good stuff A couple of credits And then this is the repository My slides are on there A Somewhat transcript that I kind of Planned off of is on there If you want to read through there I've also gotten a lot of resources Every resource, pretty much every resource That I use for this talk About compatibility And articles that I've read That were really interesting were on there So if you go here And that's two ones A11Y If you go there Go to the resources.mp It's got a bunch of links on there And then if you have any questions or comments On this talk I'd appreciate anything to add to Kate and Anthony If you have any questions now You can have the answer Thanks Great, I appreciate you all being around This is the last talk Which is about to get started In I think 15 minutes Or 10 minutes