 I appreciate all of you who have come here when the alternative is you could be queuing up for an early lunch. I thought about doing the same and then I remembered I had to be here. So I am doing this talk, Selfish Accessibility. I would like you to know that the slides are already online. The URL is r-o-s-e-l dot l-i slash w-c-e-u. So this is potentially useful for people all the way in the back who aren't going to see all of the text or the images in my slides. So you can follow along, which means you could conceivably leave, go to lunch now, watch the live stream and follow my slides. I would do the same thing except I'm giving the talk, so that's just a bit awkward. Good news is, after a ton of editing, I managed to get my slides down from 108 slides to 121. That's the wrong reaction, but that's also really, really nice to hear. So I'm going to be flying through a bunch of slides in the middle. There's technical stuff and not technical stuff. If you were in Rian's talk earlier, then I'll just throw away about 60 slides because she covered it. So thank you, Rian. You jerk. Okay. Look, introductions. So I have a slide dedicated to my ego just so you know that I'm not just somebody who makes crap up. I do. But other people seem to think there's value in it. I've written some books and some articles. I have a website at AdrienRoselli.com. You can also avoid me on the Twitters at Ardrian, a-a-r-d-r-i-a-n, just hit the mute, block, unfollow. The Pastiello Group is a consulting firm around accessibility, remediation, and compliance. They're the ones who allowed me to be here today. Yay. They're going to be surprised when I submit some expenses. You guys are laughing at that, but it's not funny. Also this microphone tastes like croissants. Okay. So some of you might have seen this A11Y or A11Y or ALI, and I want to give you a little bit of context for this because it's common in the industry. It is a numer in M, and what we do is we take the A and the Y, and then we take all the letters in between, and there are 11 of them, and we replace it with the number 11. So A11Y means accessibility. There are analogs already, L10N for localization, I18N for internationalization. This is handy, though. If you go out to the Twitters and you do hashtag A11Y, you're going to find a lot of people talking about accessibility for good and or for bad. So for a little bit of context about accessibility, I maintain that accessibility in general gets no respect no matter where you go. This is a photo of when we were first remodeling my office at the company I used to have, which I don't know. It's hilarious. So some of the paint colors, the green post is lime Ricky. The ceiling, that gray is called cyberspace. The blue pillar is called online blue, I don't know why. So they have, sure when Williams went to all this effort to come up with these really compelling names, and oh yeah, we did move out of that office, they came up with these really compelling names and then they came up with accessible beige. For those of you in the way back who can't see this, you're not missing anything. It's the same color as 1980s era PCs, old IBM machines. So my partners at the time thought it'd be hilarious to paint my office accessible beige. This might explain why I no longer have that company. So these are the things we're going to cover. I'm going to run through some statistics. I'm going to go over my thesis of how to be selfish, talk about some experienced models, technical stuff, WordPress, and we'll wrap it all up. So first off, statistics. And I'm going to go through these relatively quickly, but I want you to at least be aware of them. In the U.S., if we talk about anybody who has a disability, in that age range of 21 to 64, we're looking at 10% of the population. In that 65 to 74 year old age bracket, that number jumps to a quarter of that population and continues to climb. And this includes visual, hearing, mobility, cognitive, et cetera, any type of disability. Worldwide, 285 million people have a vision impairment. And as these numbers show, that number tends to climb with age. Hearing impairments, 360 million people worldwide have disabling hearing loss. And that's disabling. There's a far greater number of people who just can't hear what I'm telling them at a party or they're lying to me. Probably the latter. So again, that number tends to increase with age. Cognitive impairments, 5.5% in the U.S. in that 21 to 64 age bracket. The number, that percentage increases with age as well. Cognitive impairments are a lot trickier to try to identify. I've listed some examples, dyslexia, dyscalculia, which is the numbers equivalent essentially of dyslexia, memory issues, ADD, ADHD, et cetera, lots of different things. We're talking about 4.3% of the population. And that's just the ones that are necessarily diagnosed. There's a lot of people out there who struggle with different kinds of impairments, and it's not diagnosed. And some of them are not as easy to define either. I probably shouldn't have put the clicker down as priorities right now. So here's the thing. I have been to lots and lots of accessibility talks over the years where people talk about numbers and they try to motivate you to think about how many people you're going to benefit. And in my experience, that is useless. It doesn't work. People aren't necessarily motivated by that. So my thesis is about how to be selfish. WebAIM is an organization called Web Accessibility in Mind, and they put together this great hierarchy for motivating accessibility change within an organization on a project, et cetera. And it starts off by guilting people, which is kind of a mean way to do it. You punish them when they don't do it right. You make it a requirement, so they have to do it in order to, I don't know, get paid. Then you start to turn the corner. You reward them for making things accessible. You hopefully will enlighten them. And ultimately, you want to inspire them. You want people to feel motivated to take on accessibility themselves and just make it happen. It doesn't always work. So I put a star on top of this tree, and I call it Make It About Me. Very simple thesis. These other things don't work, so maybe I can make it about me. So here's some ways we can look at that. One of them. When we think about getting older, I showed you some stats earlier as numbers of impairments tend to increase as a percentage of the population. Getting older is something that affects nearly everybody. With some exceptions, you might be fortunate if it doesn't affect you. It's probably a pretty dark thing to say. Nobody's laughing, so clearly I have a darker sense of humor than everybody in this room. It does carry risks and side effects. Definitely not for the young, as evidenced by the very few number of young people I see that are old. See, that wasn't even funny. So looking at these two couples sitting here, think about it for a moment. What's different between these two couples? What separates them? Besides about, you know, five, six feet on the curb, the only thing that's separating them is 30 to 40 years. Otherwise they're probably doing the same thing. They're probably trying to figure out where they're going to go to get some food. All the restaurants are closed. They don't open until seven. We have to drink three bottles of wine and just kill some time. Really the same goals here. There's not a lot of difference. It's just age. That's it. These two women separated again by, you know, a foot, two feet, and 30 to 40 years, trying to do the same thing. They're both hanging out in the sun. They're both reading. One of them is smart enough to use a solar powered device. That doesn't require a battery backup. I'm just going to cross off the rest of my jokes. I'll blame it on the translation because I'm speaking English very quickly, I understand. So another thing to consider, accidents, sort of a situational disability where you might be temporarily disabled. And that comes around from things like broken limbs, eye injuries, hearing injuries, head trauma. I am sort of the perfect case of all of these. All of these scenarios have happened to me. I've broken bones, jacked up my eye, been deaf for a while from running concerts, and I have a row of scars on my head. So I've collected everything here. I don't recommend doing that. If you've had a broken wrist, a fractured wrist, a repetitive stress injury, then you might be familiar with having your hand disabled for a while and in a cast. Very difficult to use a mouse or a keyboard when one of your hands is out of commission or the entire arm. Maybe you poked yourself in the eye, just keep clicking close window, close window. And now you've lost some depth perception. Makes it a little bit trickier to make sure you're typing correctly, grabbing the mouse, opening the door, pulling something out of a cabinet. Arguably, some people do it as a fashion choice. I can't explain that. There's also this notion of cognitive impairments that you know are coming. Or maybe you already have. So there's a British guy in the front row who's laughing at this. That's a wheel of cheese. These guys are running down a hill at top speed chasing a wheel of cheese. You could argue that none of them is impaired when this race starts. But they put ambulances at the bottom of this hill because every year when they do this cheese wheel chase, people get injured. They always load a bunch of people into ambulances. This is very much a scenario where they don't start off disabled, but they absolutely finish this run disabled. Permanent or not is a different conversation. You might think that, like me, you are invincible and allergic to nothing. But there are situational modifiers that come into play. You might pretend that you can multitask. You might work in the sun, eat at your desk, not have headphones handy. Or the content's not in your native language, like mine would be English, usually. So this is sort of an analog to how I do my work. I sit at the computer with one hand working and the other hand holding a taco. Or since I'm here for another few days, a croissant with butter dripping all over my laptop, which means I'm limited. I'm down to one hand, essentially. And I've always maintained that everybody is a keyboard user when they're eating lunch with their mouse hand. It's really that simple. We're all keyboard users every day around lunch. I like to work on my patio, this is not my patio, in the sun. And when I'm working in the sun, I have to turn the brightness up all the way on my computer. And think about just when you're outside and you're using your phone and you're trying to tweet or text or look up the schedule or whatever. It's very bright, you have to turn your screen brightness up. The contrast becomes an issue. It's a real thing to consider. These guys are professionals. These guys are multitasking pros. They are so on the ball they brought a tarp. I mean, how awesome is that? But look at them, they are multitasking. One of them has one hand on his phone and the other on the cigarette. The other one's not even using his hand for his phone, he's just that awesome. But arguably they're distracted. They're probably not super focused on the task that they're doing. And there are things that we can do to benefit those users. I know that I fall into that scenario. This guy, however, is my favorite. I would like to point out that's a typewriter. I mean, really, he's got the whole sun thing sorted and contrast, another solar-powered device. Some people I see regularly working in cafes. This is a guy who's probably doing some video editing. Might even be teaching himself based on the number of manuals sitting next to that camera. And this is a case where the headphones are really important because he can't necessarily hear the audio if the cafe is full of people behind him or they just pull one espresso. Then you can't hear anything anymore. Some of us have to consider what we're doing when we have a partner in bed with us. Playing audio and video, not so compelling when you're afraid of waking up the person next to you. Or in this case, maybe you don't watch videos of squirrels while the dog is laying next to you. That's a big dog. Big, big dog. This is sort of analogous to my living situation. I live in a tiny, tiny house. But I live between people with motorcycles. And they like to have these motorcycle duels on the weekends. One of them wheels his motorcycle out and revs it. The other one wheels his out and revs it and his rev, rev. And as a result, I can't have a conversation or listen to anything because all I hear is a motorcycle. This is why my television has closed captions on permanently because I never know when they're gonna start. And I swear they wait until that really important scene in Mighty Morphin Power Rangers where they reveal the bad guy. Oh, some fans. Years ago, I had my passport stolen in Spain and I sat down at a keyboard with letters that were familiar yet different to me and all of my touch typing skills fell apart. And I'm using an operating system that's in Spanish and surfing websites that load by default in Spanish. And I think I can speak some Spanish. You really can't when you're in a panic situation trying to use a full system in a foreign language on a keyboard you don't know. So the language barrier becomes a problem too. And some of the affordances that we think about for accessibility can benefit those situations. I'm from America where we have Thanksgiving every year. We murder a turkey and eat it. And the last thing that I wanna do is spend that visit eating this poor murdered turkey sitting with my parents changing printer toner and putting paper in and cleaning all the viruses off their system and all the custom cursors and icons. So realistically, you don't wanna be tech support for your family if you don't need to be. You don't want to lose all that potential time you could spend hanging out with your family by sitting, you know, crowding around the computer and trying to uninstall, uninstall, uninstall. So I'm gonna talk a little bit about some user experience models. Normally I do a show of hands, but thank God I can't see past the front row. Ariane, hi, hi. Otherwise I'd be panicking, which is awesome. So what I'm gonna do is talk a little bit about user stories in the context of these things that I've puttin' on the screen. The word will come to me later. I'll shout it in the middle of the night. So here's an example of an example, here's an example for some of what I've been talking about. As a user on a sunlit patio, I wanna be able to read the content and see the controls. This is a tangible user story. 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. In order to click links as a user with no elbow room in coach class with a tiny track pad, I want to click areas to be large enough and adequately spaced. I know I'm not the only one who flew here on goat class, so I didn't even bother pulling out the laptop because it's just impossible to use. As a user distracted by the television, I want clear headings and labels so that I don't lose my place. Pretty straightforward. These all feed into some personas. These user stories help inform these personas. You might have a different model and a different approach. I'm not trying to tell you or write a wrong way to do it, just give you some ideas. What's great is that Sarah Horton and Whitney Quessenberry have written a book called A Web for Everyone, and they have these personas for people with disabilities that are available free online. And if you look at the slides, there's a link there and you can follow it. And they've done some of this hard work for you. They've identified some of the disability types and they've created these personas to support them. In my experience, though, personas like these tend to get kicked out pretty early in the process. So you're trying to get that number down to three to five personas in many cases, so you're blind persona, gone. You're a person in a wheelchair, gone. So instead, what I try to do is I take the personas that correspond to stakeholders and I fold in some of those user stories, some of those things that they will have some experience with. I'm appealing to their inherent selfishness. So I have a stakeholder who I know is always traveling. What are some of the things they experience? Coach class, always having a hand tied up, carrying equipment or holding champagne if it's first class. Maybe the sun coming through the window, et cetera, and I fold those into that person's persona. A business manager, a purchasing agent, whatever. I look at the things that that person does on his or her job and I fold those into the persona. And now what you're doing is you're creating personas that stakeholders identify with that have temporary disabilities or situational disabilities built into them. And now they're not getting discarded. Now you're not having a conversation about, well, we have a colorblind user or a low vision user, so we need to make the contrast higher. No, no. Hey, Bob, VP of Guy Who Spends the Money on this project, I know that you're working in the golf course a lot and it must suck in the sun, so let's kick the contrast up so you can actually see the screen. So I'm appealing to the inherent selfishness of my clients in many cases. I'm gonna pivot a bit here and fly through some technical bits because I feel like I'm behind schedule. Am I behind schedule? Whatever. Nobody's going to lunch, right? Ooh, okay. I don't need to see the room to know that that's not gonna go over well. I'm just gonna run through a series of tips. Use alternative text on images, please. In a case where the images disappear, the alternative text is displayed. You'll note that there's no text for the kid happily chasing a soccer ball, which is a photo we took right before he face planted into the grass, by the way. It was so funny. But the logo in that upper corner does have the name of the organization, Buffalo Soccer Club, an inner city soccer program my company helped found a few years ago for, now has year round programs and I know nothing about soccer, so it was hilarious. I also fell on my face. But all of the other images that were in there were decorations and they can go away and that's no big deal, but that logo is really important. So it has important alternative text. I'm gonna blow through some of these slides because you can read them at your leisure. Oh, look, there's a flow chart on how to choose alternative text. You can look at that when you want. It's just a handy reference. Hyperlinks, it's not uncommon to have sites where you cannot identify what on the page is a hyperlink until you hover over it with your mouse. Just be smart about that, avoid those click here links, avoid all caps and emoticons and emojis, warn users before opening new windows and downloading giant files, good pagination links, try to make the links obvious, make the link text consistent. If you're using an image as a link, make sure the alt text also makes sense. Please use link underlines wherever possible. In this image, the color for link text is the same as their highlight color. So if it's orange, I have it in multiple color blindness simulators, but if the color is orange, that doesn't necessarily mean it's a link. So whenever possible, consider you're not Google, you're not some special snowflake where everybody understands what your site is about, just use underlines. It's the quickest and easiest way to make sure the links are understandable, and I have some references to WCAG guidelines as well. Use focus styles. You probably can't tell just by looking at this screen, but this is an animation of me tabbing through the Virgin America homepage. I can't tell where the cursor is at any point as I'm tabbing through the page. Oh, wait, look, the page scrolled. I still don't know where I am. It's an infuriating site that's won a lot of awards for great design, but is incredibly useless to anybody who has any kind of impairment. So this is really easy to fix. Everywhere you have a hover style, add the focus selector onto it as well. If you have any libraries that use focus outline none, kill it, remove it. As Rian had said earlier, just use the tab key. First thing you do when you go to a site, start tabbing. If you can't tell where you are, you've got a problem. I talked about color contrast. No, I didn't. I did. Somebody, whatever. These are screenshots of that soccer club showing it in three different views. This is if you have Tritonopia, Protonopia, or Deuteronopia, those are three forms of color blindness. It's important to make sure that there's sufficient contrast between content and links and navigation items and menus, et cetera. And there are some really great tools online to help walk you through that. And there are some widgets you can add to your browser for color blindness simulators, which you can also add into Adobe Photoshop. Use the label element properly. If I click the label text next to the field, the focus should go to the field. It's just a matter of matching the four attribute of the label with the ID attribute of the field. Really easy to test. Use HTML5. Look, it's a layout. It's one we're probably familiar with. You can probably, without thinking too hard, guess what the HTML5 elements would be, and oh, you were right. Use those elements. They already have nicely built-in support for screen readers. If your site is responsive for all contexts where we're just talking about a narrower screen, same thing, just HTML5 still applies, still very valuable for a ton of users. Try to use only one main element per page. You could use more than one main element, but don't, because the exception for that is too long for me to get in here into with a little time I have left, and I know you all want lunch. I think you want lunch. Use headings wisely. So I have an article with an outline view just based on the heading structure. And even if you can't read the text, you can see it indents a little bit. And that's because my heading structure corresponds to the structure of the content. H1 for the main title, and then a subsection is an H2, and a sub to that section is an H3. And I step back out of it to an H2. Just use good heading structure. If you've ever heard about the document outline algorithm, it's a fiction. It doesn't exist. No browser has ever supported it. So don't think that you can just do H1s all over the place. That can be problematic for some users. Use, know whether you need to use a button and input type submit or an anchor. You can style them all to look the same, but that doesn't necessarily mean they are the same. Don't use a Diverrspan. If the control takes you to another URL, if you can right click and open a new window, use an AHRF. If it changes something on the current page, hide something, toggle something, use a button. If it's going to submit form fields, I recommend input type submit, only because button type submit, I find button usually has some overlap with other styles. Don't use tab index greater than zero. Otherwise you run into this problem where as soon as I start tabbing on the page, it jumps me down to the captcha because they have tab index one, two, three, and four on the captcha. Whether or not you use captcha is a whole different discussion. Also, don't use captcha. Okay, that's a good response. Don't use tab index one or greater. That's the gist of this. It is okay in some cases to use a tab index of zero. This is an example of a grid I had to build for a client where they wanted things to only show on hover or make people scroll to see the content. If you have scrolling content areas on your page, a keyboard user can't get in there to make it scroll. A tab index of zero on that content area now puts focus on it and a keyboard user can use the arrow keys to scroll up and down and get to content that was otherwise hidden. Please set the lang attribute on HTML. Make it appropriate for the language of the content on the page. I have this whole demo here where I show off how Firefox automatically chooses between commas and decimals based on your language settings, but it's like 20 minutes to explain. It's not at all interesting. But do know that it has wonderful benefits for screen readers. You can force screen readers to say things on the wrong accent, which is hilarious if you want to make like a dance techno German version of Nick Cage songs, but that's just me. It's also a separate talk. If you saw Morton's talk this morning about grid where he talked about flex, et cetera, something I want you to keep in mind, source order matters. As people tab through the page, they tab through it in the order of the code in the DOM. That doesn't mean don't screw around with it, but we've learned some lessons from floats and absolute positioning. Flexbox has that order property which can throw things off, so please don't use that, and grid has the same risk. So just be careful, understand what it will do, tab through the page, see the impact. Definitely don't disable zoom. You'll never see Bill Murray telling you that you're awesome, because you're awesome. That's my Bill Murray moment, whatever. If you go into a page, just remove the user scalable no and the maximum scale of one and look, it's fixed. Mobile browsers tend to overwrite it now anyway. It's still good practice to get rid of it. Please avoid infinite scroll. If you have a footer or you have content in the right column, maybe after that scroll area, and you want people to be able to get to it hitting the tab key, they'll never get there. So I can never get to that grid on the right side when I'm on this page. It's infuriating. It destroys the back button as well. You can't share those URLs to a specific place. Please use captions and subtitles. Whenever possible, if you're doing video or audio, transcripts are ace, captions and subtitles are ace as well. If you've ever used YouTube's automatic captioning feature, it creates some terrible things. This one says, while so long to his Viagra, this is in Sweden when a guy was introducing me for a talk. I don't know how he knew. But the nice thing is, there's the site nomorkraptions.com where you can take the auto-generated captions from YouTube and hack them up, fix them, make the text good, and it'll output it into all these different file formats. Really handy. If you find yourself doing talks, for example, grab the YouTube video, auto-caption it, clean it, re-upload it. Everybody uses them, by the way. Oh, look, I have a whole other slide that has some links to resources to help you walk you through some of these things. Really quick, I'm just gonna touch a little bit on ARIA here, Graan had mentioned it earlier. For the most part, you don't need to worry about ARIA unless you're building unique custom elements that aren't already defined in HTML. So don't get too excited about ARIA because it can be very, very risky. There are five rules to keep in mind if you're gonna play with ARIA. If you can use a native HTML5 element that already does what you want, then do it. Use a button instead of a div with a non-click, for example. Don't change native semantics. If you've got a heading and you want that to be a button, don't, it's gonna throw everybody off. All of your interactive controls that you build with ARIA must be usable with the keyboard. They have to be able to perform those same actions. Definitely don't use a role presentation or ARIA hidden true if it's a focusable element because that means that some users can never actually get to focus onto that element. And all interactive elements must have an accessible name. So a button has to have a name, a link has to have a name, a tab has to have a name. And usually it's visible text. And if possible, you wanna convey the current state and what it's doing at the time. And again, Rianne had shown a little bit of that with the ARIA expanded example in her talk. And if you're in the future watching this on YouTube, you can just go to Rianne's talk on YouTube and catch up on that as well. And if you're in the future, I'm sorry. Definitely one thing, I have this one example I wanna show you on how not to do things. This div on click event is a problem because it won't work for a keyboard user so I add a tab index so now a keyboard user can get to it. The problem is now I need to trap the keyboard action as well so I have to listen for an on key press event. And at the same time, I then have to make it not scroll the page because I hit the space bar because I think it's maybe a button. And then I have to throw a roll of button on it so it announces itself as a button in a screen reader. When all along, all I had to do was this. And it really is that simple. You don't need to over engineer this stuff. Most of these things are already built for you. Wow, I'm gonna go over a little bit. Whatever. So I had a whole thing I was gonna say about this but mostly you can go watch the video and see the transcript. But Rion said something back in March of 2016 that I think is really important. All new or updated code released into WordPress core and bundled themes must conform with the WCAG 2.0 guidelines at level AA. This is important because those are the standards. The WCAG 2.0 AA is the standard that is being recognized by governments in lawsuits by third parties who are getting on board with accessibility. This is, if you want stuff to be in core, you need to follow this anyway. So get on board with it and accept this. I think it's a great statement and I think it's awesome that WordPress is doing that. There's some notes related to that. There's the accessibility ready tag which you can get for your theme, including some information on how to make that happen. Note that plugins is the, all plugins, the accessibility on plugins is the responsibility of the plugin author. So as far as I know, there's still no guarantees on that. I would also like to note that Rion Rietveld, a year and a half ago was it, won the heroes of accessibility award in the individual achievement category. She doesn't like it when I say this but I think we all need to acknowledge. Yeah, Rion's contribution because of the status of WordPress has an outsized impact on the web as a whole and I think it's awesome and I'm glad that she did that. And as a result, I'm glad I know you as opposed to me saying who? Who did that? There are currently 134 accessible ready themes that you can just download and work with. You can just go. So grab them, ready to go. There are some plugins that are out there now that have been out there for a while rather that help make things accessible. I think Access Monitor uses Tenon to do checking. Nice thing is I was signaled, I have five minutes and I'm at the wrap up portion of this thing. Here's the general message I want everybody to understand coming out of this, this whole selfish aspect of it. Supporting accessibility now is really working to help future you. That's what we're talking about. You're all probably capable of using your equipment today but 10 years, 20 years, that might not be the case. You might be dependent on somebody else. So getting it in now is gonna help future you. It also helps the injured version of you or the encumbered version of you which could be today or next week or tomorrow morning depending how much you drink at the party tonight. Also get younger developers to help you. Get them to buy into it now. Force them, train them, get them interested because once you've moved out of what you're doing today into a different role, you need other people to support this and to support future you. So you have to teach them well. You have to prepare them for this. They have to be able to do it well. I have a couple examples where I wrap up here. This one is what I call the stair ramp. This is often shown as an example of how things can be accessible and beautiful and what a lot of people who use this in their talks don't understand is that this is a death trap. This is basically a wheelchair murder device. The slope on the ramp, way too steep, way too steep. Each one of them ends in a concrete wall with the exception of this one which I believe I've been told ends in a pit of crocodiles. If you are like me and you take stairs two at a time it's hilarious, it's step, step, stumble, step, step, stumble. This is a death trap. It really is. What's important to note though is this was built based on a checklist. Somebody said we need to get a ramp into those stairs and they followed that checklist. There's a ramp and that's not what accessibility is. It's not just a checklist. There's so much more that needs to happen. There's an aspect of maintenance that's involved here. So a friend of mine who uses a wheelchair was going to his pharmacy and when he got to the ramp to wheel himself into the pharmacy he noticed that they had put a potted tree on the ramp. So they shoveled all the other parts but they put a potted tree on the ramp. He could no longer get into the pharmacy. I mean good for them, they built a ramp checklist but they didn't think about how to maintain it and sometimes maintenance is really nothing more than just not breaking the crap you've already built. Really can be that simple. It's an ongoing process and when you build it right the first time you don't need to stress about it going forward. I have a ton of links in here at the end. Pile of resources that you can read at your leisure. Again, maybe over drinks, I don't know. And if I recall correctly, that's my entire talk. Done. It's 121 slides. We have time for half a question. You're gonna be around. Yeah, I'm gonna be around. You're gonna have lunch. I'm gonna have lunch. You're gonna be that expert by coming to the party. Are you what? Coming to the party. Yeah, tonight. Oh God, yeah. All right. Should we do questions at the party and have lunch now? We could do, you know. Sound good? Or if there are quick questions from the floor. One last call for questions from the floor. Raise hands or go to a microphone. Lunchtime it is. Lunch. Thank you very much, Adrian. Bye. Thank you.