 Okay, so I'm going to dive right in. Thank you for coming to my talk. I know you have a wonderful selection of accessibility talks in this time slot, so clearly this is the one that's still in the scalable. I have, if you follow me on Twitter at all, I'm sorry, but I noted that I had 108 slides in 40 minutes, and after a lot of work I've gotten it down to 120 slides. So we're going to see how many of those I get through. To manage your expectations, all of my slides will be available online later. And I'm saying this now partly because as I manage my own, as I manage my own time, I have a whole chunk of slides that I'm just going to fly through because they're mostly technical stuff. And the nice thing about technical stuff is it's so boring that you guys can't read it at your own time, and what we call sleep, I won't be personally heard or watched in film at times. I really thought you'd come to film me off this day. Such an auspicious start. Quick question, how many people here use WordPress for CMS or a blog platform? That's good, okay, most of you. How many of you use, in addition to WordPress, some other platform besides WordPress than they blog or CMS platform? Okay, usually I see a much higher ratio. Part of the reason I always ask that question is because I'm going to be talking to you about things that apply regardless of the platform. There's a chunk in here about WordPress that I'm talking a little bit broader than that. So really quick, this slide is dedicated to my ego. I have a website, I only put it here because I write on accessibility pretty regularly, so adrenvillay.com. And then you can avoid me on Twitter at our brand, that's a-a-r-e-r-i-a, and I recommend you make me do it. I'm here because the other group was able to take me to come here, otherwise I couldn't afford to fly across the ocean to tell you all these lovely, wonderful things. So, right off the bat, some people have probably seen the a-1-1-y hashtag or seen it, who's maybe not on Twitter or elsewhere, and it's not uncommon for people to say, what is that? What is L? Who is L? What does L mean? So real quick, accessibility, a-1-1-y needs accessibility. It's just a new word in there. It's a pretty common technique in some communities where you just remove all the no letters and you're replaced it with a common character that will come. So localization is L10N, internationalization is I-18N. When you see a-1-1-y or a-11-y or alley, it means accessibility in almost all these cases. The thing about accessibility, though, as I've discovered over the years, it typically gets no respects. It's sort of an afterthought of things that people aren't really too interested in. When I had my own company, we were painting the offices, we were going through colors to paint everything, and that nice blue is called online blue. I don't know why they call it that. The ceiling was cyberspace gray in a real high-tech sounding terms. Oh, yeah, we moved out. But accessible beige. So the color of computers for, you know, old IBM computers from the 1980s. That was the color that my partners wanted to paint my office because I did the accessibility stuff and they thought accessible beige. A bunch of jerks. So these are the things we're going to run through. Some statistics just to give a little bit of grounding. I'm going to fly through those, though. I'm going to talk about this whole concept of being selfish. The technical bits is probably the part I'm going to post just so you know. So statistics right off. These are U.S. This particular slide is U.S. focused because if you haven't figured out by my accent, yes, I'm from the United States. I don't know if that was obvious. I'll just keep talking. So in the U.S., any disability, when we look at the numbers for who has any type of disability, which includes visual hearing, mobility, cognitive, we're looking at in that age range of 21 to 64, 10% of the population. You'll note that at this 75 and up age, it's 50%. Sort of a theme that happens. Worldwide, 285 million people have some sort of vision impairment and 82% of those people living with blindness are 50 and above. There's a bit of an age factor there as well as we see from some of these other stats. Hearing impairments affect 360 million people worldwide. That's disabling hearing loss. That means that they really do need help to get by and say an event like this where you're socializing with a room full of other people who are also socializing, all of whom have more interesting things to say. So 36 million American adults report some degree of hearing loss. Mobility impairments relatively low as you're younger, but they tend to increase. So 5.5% in the 21 to 64 year old age bracket in the U.S. goes up to a third of the population that are 75 and older. Cognitive impairments are always a little bit trickier for people to sort of get their arms around. It includes, this is just some of them, dyslexia, dyscalculia, which is the numbers version of dyslexia to simplify it. Memory issues, distractions, the list goes on and on and on. In the U.S. that number is about 4.3% of the population in my age bracket and then again continues to climb. But one thing I've learned is that showing the stats doesn't really make the case. I show the stats because I want people to understand first and foremost this is a real population of people. If you're more like me, you don't care. Screw them, I really don't care. My whole treatise is about being selfish. So that's what I'm here to talk to you about. If you were in Heather Burns's talk earlier today, you might have seen this pyramid and if you weren't, cool, now you get to see it for the first time I guess. So WebAIM is an organization called Web Accessibility in Mind and they have this hierarchy that they see as motivating accessibility change. And when you start off by guilting people, you're not going to be as effective. Punishment means that they've already done something and that just creates a bad relationship afterward. You make it a requirement, they'll do it, but they're not necessarily so interested. If you start to reward people, then they start to pick it up a little bit more. You want to work to get them enlightened and ultimately you want them to be inspired. You want them to just know that it's the right thing to do and feel that something that sets them apart in the product. I again am wired very selfishly so I modified it. I put a star on top of this tree. And it's all about making it about me. So you might have been in some talks already, you've heard people talking about the users, not this guy. So to run through some of these things, getting older affects nearly everybody except those who are fortunate enough to not have to get older, I should really rethink that. So it does carry risks and side effects as I note and it's definitely not for the young as evidenced by how few young people are old. The only thing separating these two couples besides about four feet is probably 30, 40 years. But really they're doing the same thing. They're living the same life. They're both arguing about probably where they're going to go get some food next. I don't know for sure. The only thing separating these two women besides the fact that one of them is using a solar powered piece of technology is probably about 40 years again. They're doing the same thing. They're hanging out, they're reading. Well, she might be tweeting, I don't know. But conceptually they're doing the same thing. The only difference for them is age. Really not that different. Accidents happen to people a lot. I am evidence of that. I could show you the row of scars across my head and all the other things I've broken over the years kind of weird and I might be in violation of the code of conduct. Accidents come in the form of everything like broken limbs, eye injuries, hearing injuries, head trauma, et cetera. If you've ever broken a wrist and tried to use a computer, you realize how quickly, whether you quickly realize how difficult it is to do things like operate the mouse, use the keyboard, close the lid, actually click save instead of reply at the wrong time. Sometimes just having a temporary vision problem means that you lose your depth perception and instead of grabbing the mouse, you end up pushing it off the table. Hilarious. And now that they're all wireless, now you have to go hunting for it, you can't just reel it in. Some people do it as a fashion choice. Some people arguably might start an activity with a cognitive issue, but they definitely end with more issues. That wheel of cheese that they're chasing down a hill, by the way, is a tradition somewhere in this country. You all should know better than I, I hope, because I forgot. Anyway, what's interesting about this is at the bottom of the hill they have a team of ambulances waiting. It's not a function of if somebody gets hurt. After every one of these, somebody walks away temporarily disabled, maybe permanently depending on whether or not they got the cheese. If, like me, you believe that you are invincible and allergic to nothing, then there are other things you have to bear in mind. Multitasking, sunlight can be a great weakness, eating at your desk, not having headphones handy, just not even working in your native language. And I thought my native language was English until I came here, so that's awkward. But this is how I spend a lot of my days. I try not to get a taco filling bits into my keyboard because it's a laptop and you can't just shake it. It's very bad. I like to sit on my patio or on my porch and if you've ever used a phone in the sun or tried to work in the sun, it's really difficult. You're turning the brightness all the way up and then how long does your battery last? Oh, it already ran out. These guys, I think, are professionals. I would like to point out, though, that neither of them has a free hand to actually use the computer. But they brought the tarp. I mean, these guys are on top of it. But this is a function of they're not just in the sun, they're distracted, they're doing other things. And if by chance they had to use email or fill out an online application or sign up for a bank account, you'll know nine times out of ten they're doing it wrong, every keystroke. This guy's my favorite, though. I would like to point out, part of the reason he's my favorite is because his laptop is a typewriter. Solar-powered, baby. Sometimes you find that you're working in a public space because it's the only option you have. I can tell you the Airbnb flat that I have right now is a little too small. So I will probably be working in cafes for the next few days. This is a case where the headphones become really important. He's doing video work. It's very hard to do video work when there's a lot of background noise because, well, you can't hear anything. And maybe you don't want everybody to hear what you're up to anyway. Also, the consideration of having a significant other in bed with you. I work in bed. I don't know that I would want to wake up a dog that big because I'm watching a video or dictating something or just shouting at my computer because the error messages are so arcane. This photo is kind of analogous to how I live. I don't live in apartments, but I do live somewhere where I am flanked by motorcycles. And on the weekends, these guys like to have motorcycle duels. They want to show whose motorcycle is louder and throatier. And if I am trying to do any work, that's very much a problem. It also explains why I have closed captions on my television permanently. I never know when they're going to start it up and it's usually during the critical scene of Mighty Morphin Power Rangers. I have been this person in a foreign country trying to look up information about the flight that might have been canceled on a keyboard that has characters I don't recognize, looking at a website that is localized for the region I'm in as opposed to the language I speak. And all of a sudden, I feel like I have a cognitive disability because I don't know what I'm looking at. It makes no sense to me. This happens more often than I think people are really willing to admit. And from my experience just bouncing around Europe and Southeast Asia, when I go into any place that has these public terminals, there are a lot of really confused people sitting at them. They're not locals. They're just confused. Another thing to consider though is that if you're in this room, you probably have some comfort level with technology, which means that when it comes to family events, the holidays, you might be tech support. That sucks. I don't like going to my parents' house and changing printer paper and printer cartridges and updating all the software on their machine and doing all the windows checks and reboots galore. I just want to eat the turkey. It's a simple goal. So if you're in a situation where you're always helping other people, you might start to recognize that if the interfaces were a little bit easier, maybe you wouldn't have to spend so much of that time. You could eat turkey. If turkey is a thing here, not so much. Yeah, that's why we left. Anyway, so I'm still going to stick to sort of high level here. I'm going to talk a little bit about user experience models. I've given you sort of the context for Selfish and I'm going to pull it into user stories. I'm not going to spend too much time on this, but is anybody here not familiar with user stories? This is awesome. I don't have to spend 14 minutes on this slide. So I have these really simple user stories that are based on this Selfish model. Let me give you a little bit of context as you're reading that anyway. I have found that when I put together personas and user stories for clients, they often don't understand who that accessible persona is. They're not necessarily invested in it or interested in it. All it does is represent extra work they're going to have to do. And in many organizations, when they are looking at how many personas they have, they're saying, we need to get down to three or four, maybe five on the high end. Who do you think is the first persona to get cut? Jerry, the guy in the wheelchair. Lucy, the one who can't see. Those gone every time. So I have started to fold these selfish concepts into personas, and I'm showing you the user stories first because it's a little bit more digestible. So as a user on a Sunlit patio, I want to be able to read the content and see the controls of a web page. This affects a lot of people. As a user in bed with a sleeping spouse, I want to watch a training video in silence so I can get caught up at work. This is a real use case. This is a real thing that happens. In order to click links, as a user with no elbow room in coach class with a tiny track pad, so you were all on my flight too. I want click areas to be large enough and adequately spaced. As a user distracted by the TV, I want clear headings and labels so that I don't lose my place. This really speaks to my inability to have a good work ethic because I just sit on the couch and watch. For what is worth, there are some personas from the book, A Web for Everyone. There's a free chapter online and these personas are free for you to grab. Sarah Horton and Whitney Cuesenberry wrote this, and the personas are great and they are personas for people with disabilities. I encourage you to go steal them and use them wherever you can. I also encourage you to look at creating a persona. Yeah, that is me. Maybe this isn't as good an example as I was hoping it to be. Am I doing that? Is that better? I'll stand here for a minute. It is not uncommon to be in a situation where the personas, once they're discarded, you're not going to get them back, but what you can do is you can take the persona that might speak to a particular stakeholder, the president, the client relations person, whatever, take that persona where they've already identified with it, and fold in a trait. And maybe the trait is that person travels. It's always on the train. And now you can fold in the fact that there's a mobility impairment. And for another persona, say this one always works in a cafe in the sun and can't always hear because of the noise. And now you've folded in hearing and mobility and maybe visual impairments. So don't necessarily try to build these separate, discrete personas and user stories. Instead, appeal to the inherent selfishness of your clients and build them into the personas and the things that they do into those personas. I've had some reasonably good luck with that. Mostly because they see themselves and they say, yeah, I understand that. Boy, that is a pain in the ass using a trackpad on a train. This is the part where I look at my watch because I'm terrible at managing time. And I told the timekeeper not to bother because I'm not going to pay attention anyway. Right? She knows me already. So I'm going to go through some technical bits. Much of the rest of this is about code stuff. I may dwell on a few bits of it, but the nice thing is all of these samples will be out there for you to look at. Use alt text on images. Please, for the love of God. So this is Buffalo Soccer Club. I'm very proud of this. It's an inner city youth soccer program that I co-founded back in Buffalo, New York, where I'm from, by the way. We think it's pretty awesome. I'm not going to bore you too much with it other than the pictures. So this is the page showing, hey, here it is and here's a happy kid playing soccer. If I turn off the images though, the kid playing soccer, there's no text behind it at all. It's strictly decorative. The logo up there does have text behind it because that's important. That's the name of the organization. The other places where there were images that were strictly decorative, there's no alt text behind them. So the notion here is to use alt text, be smart about where you use the alt text so you're not creating two verbose of a page for a screen reader. Can you still make sense of the page without the images? Is any of the content missing, which is a sign that maybe you have some text set in a graphic? That's a problem. Can you still use the site? And is your alt text useful? There's this wonderful chart. Yeah, don't worry. You don't have to. But there's this chart that later on you can look at and it's just a way to get you familiar with those steps on how to decide what alt text to use and what is appropriate. Hyperlinks. This is an example of a page that I can never tell what is a link on here. I never know which element on this page is a link. Some simple tips for hyperlinks and this is really basic stuff but incredibly useful. Avoid the click here, the more, the link tos, the key reading, et cetera. Avoid all caps. Maybe don't make a URL a link because a screen reader is going to announce the entire thing. emoticons are probably worth avoiding, not just because they have cultural cues embedded in them, but a lot of screen readers can't announce them anyway. Maybe one people before you open a new window. Maybe inform them that they're going to download something and that it's a 200 meg PDF because I don't know why people do that but they do. Make sure the links are underlined and obvious. Make sure that if your image is a link that there's alt text behind it that's still valuable and useful. Make sure the link text is consistent. If you're going to keep linking to the same resource like that 200 megabyte PDF that you're all suddenly fascinated with, at least every time you link to it and mention, oh yeah, this is that 200 megabyte PDF, you should stop clicking. Use link underlines. Color alone is inadequate. I have it showing in the, through some different types of color blindness here, but what's most important is that orange is the color for links. Orange is also their call out color. Hey, look at this thing. So I never know what is a link on the Verge site because the same color is used to highlight stuff. You're not Google. I don't care how awesome your site is. I don't care who you think you are. You're not Google. Google can get away with it because everybody understands the layout of the search results and we all know what we're getting. They know the layout. They're used to it. There's all this lovely stuff in the web content accessibility guidelines that coaches you and what really you need to know is just make sure you leave the link underlines in place for everybody's benefit. Use focus styles. I am tabbing through the Virgin America page right now. All you can see is that this is updating. I have no idea where I am. This is for anybody who uses a keyboard primarily instead of a mouse. Oh, I must have hit something. I still don't know where I am. Use focus styles whenever possible. If you remove link underlines, you really need them. Anytime you see focus outline none in the CSS, just delete it. Just deleting that alone makes your website probably a lot more accessible. And it's very simple to test. Just use the tab key. Wherever you have a hover style, make sure you have a focus style. Color contrast is important. Same page we saw before, but this is looking at it through three different types of color blindness. Tritonopia, Protonopia, Deuteronopia. It's important that there's enough contrast because those colors aren't always going to be discernible on their own. And I have links to all these tools so you can grab those after I've finished talking and you've taken an app and then you've downloaded my slides. Use the label element. Here's an example really easy to test. If I click that field, the focus should go into that input. I'm sorry, if I click that label, the focus should go into that text input field. It's really simple to do. All you have to do is match the four attribute on the label with the ID on the element that you're pairing it to. That's it. Simple to test. Make sure you do it with radio buttons and checkboxes because if you don't, holy crap, is that going to be difficult? Use HTML5. Great way to be accessible. Just use HTML5. Really straightforward. Here's a layout that probably looks familiar to you. Really simple and really basic, but you probably already know what those elements are on the page. And there are HTML elements that speak to those design elements. We've got the header, which has a roll of banner already built in. The navigation, which maybe lives up top for you over on the other side, might live within the header. The main content, the footer, there's a search form, an aside, et cetera. Those are already built in. Here is the responsive version of it. For all values of responsive, that mean narrow viewport. Because we know that, yeah. So same thing. Familiar layout, header, nav, form, the roll search, the main, aside, footer. Just use the HTML5. You'll be in a much better place. Bear in mind that the main, you should only use one of those per page. Because screen reader users can jump right to the main content of your area. And if you have more than one main content area, then you don't have a main content area. Use your headings wisely. So this incredibly boring blog post on my site, if you just navigate by headings, those headings show the entire structure of the article. And there are users who navigate by headings and who listen to just the headings of a page to understand the structure. So don't skip levels. Start with H1. Should probably match the title of the page. Just use one H1. Make sure you're nesting them appropriately. If you've seen anybody who says that the document outline algorithm says you can use all H1s, I'm sorry, that's wrong. It's documented in the HTML specification. It's been written about many times. Don't use an all H1 approach. Every time you use a new section or article, it should get a heading, but it should not be an H1. And if you think it's going to affect your search engine optimization, don't worry about that. Google refuses to give direct answers, but Google has made it very clear that there is no outline algorithm. Using a button versus an anchor versus an input element, you can style them all to look exactly the same way. Really easy to do, right? Yeah, well, don't. Consider using the right element for the task at hand. Right off the bat, don't use a div or a span. If you find yourself putting an on click on a div or a span, stop. Think about what you're doing. Cry a little. We'll get through it. If it takes me to another web page address, including an anchor further down the page, use the ahref. If it's taking me, if it's only doing something on the page, it's not moving me off the page, it's expanding, collapsing, hiding, showing, use a button element. If you're submitting a form, input type submit, I prefer over the button type submit, only because I find that there are fewer style conflicts if people are using the input type submit. I have an article about this that also talks about the key handlers, and what the effects of those are. Don't use a tab index of greater than zero. If you have a captcha on your page, this is just a silly example. As soon as you start tabbing, it jumps right to the captcha because Google's old captcha had a tab index. One, two, three, four. I couldn't even get to the skip navigation link because it jumped me right to the bottom of the page. And what's funny is that I filed a bug with a digital Gov team and they insisted I was wrong and they could not reproduce the issue of keyboard. It's funny how you learn that stuff. A tab index of negative one is great if you don't want it to have keyboard focus, but you want to use script to put focus on it at some point, like a close button on a modal, for example. A tab index of zero at least puts it into the focus order. So if you have a div with a non-click and a tab index zero, stop. Go back to slides. But tab indexes of zero is useful for things that do become interactive for whatever reason. Just don't ever do tab index of one or greater. It is worth noting there are places where tab index zero is very useful. I have seen the grid, literally just a data table that has either scrolling content or has content that only appears on hover. You may have content on your web page that is in a little scrolly box, for example. The keyboard user can't get into that and make it scroll. So putting a tab index of zero on that means that it'll get focus. You can give it a roll as well if you want. You can give it an aria label if you want. But more importantly, giving it that tab index of zero means that a user with just a keyboard can tab into it and then can use the arrow keys to scroll up and down and experience the content that was otherwise missing. Please do set the lang attribute on your HTML element. I have a whole talk on this, and I talk about all the wonderful benefits for a number of fields and everything else, but probably the thing that's most valuable to know is that screen readers in particular really, really benefit from this because they will say things the appropriate way. In my other talk, I have the lyrics of Nick Cave songs that I have read out in German and French, and they're funnier that way, but we're not going to do that here. Source order matters. It's very easy today to blow up the way that we tab through content just by using floats and absolute positioning. Be aware that Flexbox and Now Grid can also screw with things. It doesn't mean you've done anything wrong, but just know by tabbing through the page what's going to happen when you start to reorder the content. Definitely don't disable Zoom. Definitely don't do that. Otherwise you'd never know that Bill Murray thinks you're awesome. Enhance. So it's not just for mobile users, but for all users. Just make sure that you don't ever have a user scalable know. Get rid of that. If you're interested in supporting Windows mobile phones, the MS Viewport will help you address that as well. The nice thing is most mobile devices now override the Zoom settings, so you can still Zoom no matter what happens. Avoid infinite scroll wherever possible, he says, thinking about the WordPress themes page. But I use this as an example. Avoid infinite scroll. It makes it impossible to access some of the content on a page, such as the footer or maybe even sidebar links. It ruins the back button. Sharing a URL to a specific place in those results is impossible. You can't just jump into a link and go back and get to where you were. And less powerful computers and devices and assistive technology will just choke. And that's not fun for anybody. Use captions and subtitles wherever possible. Nomorkraptions.com is a great resource for pulling in captions that are auto-generated. Yes, that says well so long to his Viagra. Don't let Google auto-caption because they will be terrible. But if you let Google auto-caption, you can use Nomorkraptions, pull in all that stuff that's already time-stamped and fix it, which might involve using the word Viagra a lot more. Remember, though, everybody uses captions and subtitles. Regardless of the circumstances, try to include the audio description as well, like he dropped the microphone, everybody laughed, and the speaker identification whenever possible. Yeah, more there. Some of you might have heard of ARIA, accessible, rich internet applications. You've probably seen people ask questions about ARIA all the time. Don't stress, unless you're building some really complex, really novel user interface elements, you probably don't need ARIA. ARIA has some simple rules. Basically, don't override. HTML already does a lot of great stuff. Don't override it. Maybe don't change the stuff that's there, so don't make a heading into a button. Make sure that they're still usable by the keyboard. Pretty straightforward. You wouldn't want to use ARIA to make something more accessible and then break it for keyboard users. Don't use role presentation or ARIA hidden true on something that needs to get focused because now it just disappears for some users. And remember that all interactive elements must have an accessible name. They must have some piece of text associated with them that says what the control is, ideally what it is and what it does, and in many cases what its current state is, toggled, on, off, blue, angry. So I'd mentioned the div with the on click. If you want to make that accessible, you'd have to add the tab index of zero, and then you need to throw on the key press because it has to respond to a keyboard, and then you want to make sure you give it a role of button so that it's announced properly. So what you're doing is you're creating... This doesn't even include all the code. There's a lot of JavaScript that has to support all the keyboard commands as well. Just to turn a div into a button when I could just do that. I mean, it really is that simple. It really is not that hard to do. Conveniently, WordPress has decided to go all in on WCAG. I still don't know if that's the way you're supposed to say it, but that's the way I see it. There's this lovely announcement from the state of Word 2015. She's just going to kill me after this. Anyway, what's hilarious about this is there are no transcripts for this video, but you can get in there and see him talk about how they are moving forward with this, and we are fortunate enough to have Rihanna and our audience today. I think this is really, really important. All new or updated code released into WordPress core and bundled themes must conform with WCAG 2.0, level AA. That's important because level AA is what people are using when it comes to government, when it comes to lawsuits, when it comes to a lot of business's best practices. It has just become the de facto standard. All these great notes on that. I'm going to leave these things with you guys. The accessibility ready tag is a great way to go grab some pre-built themes and not have to stress about the accessibility because it's already there. I think there are 123 as of a few days ago. The nice thing is it keeps growing. Yet more notes. Oh, by the way, Rihanna won the Heroes of Accessibility Award. I thought that was awesome. Good for you. Absolutely. She should be doing this more than me. Oh, look, infinite scroll again. There are some plugins already made. Joe Doulson wrote these three. I have links to them. I'm going to wrap this up, which will leave me about 12 seconds for questions in a moment. But it's going to take me three minutes just to explain to you I need 12 seconds. So here's the general message. They're trying to convey to you in addition to just being a selfish git like I am. Supporting accessibility now is going to serve future you. I showed you those stats before about how people accrue disabilities as they age or do dumb things, which they do over time. So supporting accessibility now also helps the injured version of you or the encumbered version of you. By getting younger developers to buy into it now is going to help future you if you are teaching them well because you're not always going to be the one who is able to do this, whether it be code it, drive it, create a requirement, write it into contracts. Start doing it now because in a few years you're not going to be able to get people to build this stuff that's going to benefit you. So this is sort of future-proofing your life. This is often held up as a wonderful example of how integrating accessibility into design can be great and look good and be useful for everybody. This is a death trap. This is a death trap for people who like to run upstairs like me and this is a death trap for anybody in a wheelchair because the gradient is too high, the turns end in concrete walls. I imagine there's a pit of alligators off the shot here. This is terrible. So you have to be careful when you're trying to integrate these things. Don't just try to make it look good but actually spend a little bit of time putting somebody in a wheelchair on that ramp and if they don't die, listen to what feedback they give you. Accessibility is not a checklist. You can't just say we built a ramp and walk away from it. Further, it's something you have to maintain. So this is a wonderful example of a ramp that goes into a drug store that a friend of mine couldn't get into because they put the trees on the ramp. They lifted the trees because it snowed and put them on the ramp and he wheeled up there and that's much more polite than what he said in real life. It's not just a checklist. It's also not something that you can do once and walk away from. It's an ongoing process. It's something you have to maintain and usually the easiest way to maintain it is to not stress about it. Don't overwrite it. Don't build new things into it without understanding their impact. If you've got good headings everywhere, good. You're in good shape. You probably don't need to stress. So it's not a checklist. It's an ongoing process. Be prepared to internalize that and get on your own. My slides will be available, provided I can get good Wi-Fi and I have how long for questions? Two minutes. I won't probably need it. So do we have any questions? No? Really? Do you have a view on access keys at all? I don't know. Access keys? So the general... That's a really big question. So I'm going to try and really simple. Access keys are awesome in the right context. The problem is the people who benefit from them are often using tools that intercept those keys and they become very problematic. There is a group of people who feel very strongly that access keys have value. The trick is figuring out how to make sure those access keys are presented in a way that people who use assistive technology can still benefit without breaking the technology they're using. I don't think they have value to them. I don't think that they are workable with the current technologies that we have today. Hope that was quick enough. Other questions? There's no way I answered everything. Is everybody asleep? Alright. Old caps, don't do old caps. That's obviously true for larger blocks of text. Because it's difficult for anyone to read large blocks of old caps text. For example, Google Material Designs recommends old caps for buttons. All caps for buttons? No. And here's the thing about all caps. A screen reader will typically announce every letter. Depending on the user's verbosity settings you might put something in all caps and the screen reader is going to say S U B M I because it thinks it's an acronym or an abbreviation. I always encourage people to avoid all caps. In headings you can get away with it stylistically if you're using just CSS, but I still always caution people to avoid all caps whenever possible, particularly on user interface controls because that's where the problem manifests because it can prevent people from actually completing a task. Related to that, screen readers, do they interpret text transform uppercase too? The screen reader bases text transform off of how the browser passes it. So the short answer is it depends. It depends on the screen reader, the version, the browser, the version of the browser, how the CSS was put in there. So it's not a really simple answer, it's variable. And that's where testing is important. And I've been signaled that I have to shut up. But you were very polite about it. Very polite. Okay, that's it. Thank you.