 This is one on one D right I don't have the internet so I don't have the schedule make sure I'm in the right room I'm up here first Someone else the schedule said there is but so this room's double booked to look like No, I trust I'm hearing about it Yeah, the only thing is it seems like there's on the schedule there's two sessions listed for this room at this time So I don't have the printed one on me, but in people's phones Play something I don't know what's the app say? I Am going to give the first dual session at Rubicon. It's gonna be to come first. Yeah, that's true. I'm here So, all right, thank you Yeah, they're hanging out by the door there. It's not a very inclusive use of the space The session is short enough where I don't have too many bad jokes. So All right, I'm gonna get started So if you're using the app To view the schedule it seems on the app this room is double booked So if you're not here for inclusive mindsets, you should totally stay because you're only gonna benefit from it So if it's not the talk you're looking for, you know Be open to new ideas Have it come on have a seat. I'd appreciate it But thank you everyone for coming to my session I really appreciate having the chance to talk to you about this subject. It's something that I really care about And before we get started, I just want to tell you a little bit about myself. My name is Mike Miles I am from Boston, Massachusetts. I help run the Boston Drupal group there. I've been working with Drupal for about 10 years I do everything under the sun when it comes to Drupal During the day I work as the senior technical solutions manager. It's a long title for a digital Interactive agency digital marketing agency called genuine. I've been there for about nine years my Drupal tenure career Genuine we're a full-service digital agency and what we do is we make we build agile brands that stay culturally relevant We make them easier to love for for their users and we do this by leveraging our full Service capabilities that we have in-house from digital strategy to design to UX to video production And development across number of technologies not just Drupal Drupal is just a small part of what we do But it's like 99% of what I do and we have offices in Boston, Chicago, San Francisco, New York At night I run the developing up podcast which is a podcast focused on the non-technal side of being a developer So if you're a developer out there anything about your development career That's not about code is what we cover on our subjects on the podcast We just released an episode yesterday on leadership skills So check it out if you're a developer or if you're not you know share it with friend If you want to know any more about me you can find me anywhere in the internet Mike Miles 86 Since the short session I'm not going to give you the full spiel, but you can find me on Twitter on Drupal.org on YouTube Google plus I probably still have if you want to go there So I believe that everyone in this room we have one thing in common. No, it's not our love for Drupal That's just a given so I won't even count that It's that no matter what we do every day, you know We work in the digital world and If you're a developer if you're a designer if you're a UX experience designer if you're a product manager a project manager Every day we want to make a positive impact on as many people as possible How many people here would raise their hand and agree this is ultimately what they try to do? Yeah, everybody in the room. That's excellent like a hundred percent I don't think anyone seeks out on their day-to-day to say alright How am I gonna make someone's day worse by building something? Right, whether you're building something for your company whether you're building something for a client You're trying to see how can I build something that's gonna make a better impact on the users How am I gonna make it so users want to come back to this product website come back to our mission statement? How am I gonna make that positive impact? And this is great. This is something we all want to strive for and One of the things we do for this especially for reaching a positive impact of users is we think about Accessibility needs right we I would hope a lot of us think about accessibility needs by that I mean paying attention to vision and herring and pyramids cognitive ability mobility use amounts or a keyboard When we build our digital products, we think about these these topics and we make sure our products work for these users with these differences The issue is though humans differ on Way more subjects than this this They differ on location on gender on language on their education levels on their age a whole number of metrics that are way beyond accessibility and All these differences which are covered under the idea of inclusive design They change how we interact with the digital world. They impact how we experience the web and the products on there So they change how our users reach our content and how we can make an impact on our users So the idea of a time inclusive design is building something to make the biggest impact on the greatest number of people as possible it came from Actually building in the physical world and it's been carried into the digital world and There's a lot of ways to do inclusive design and with this short talk What I want to share with you is what I consider my four pillars for an inclusive mindset Four ideas that you can apply to any one of your projects no matter what your role is to make sure you're making a positive impact As many people as possible So I created commons 4.0 this for you. So feel free to steal it and share it out My four pillars in inclusive design or inclusive mindsets that I applied to my projects is one that no user is average That every user deserves equal access To provide understandable content for every user and that every user deserves our trust and respect Four important pillars that if we apply to our projects, it's gonna make a world of difference. Hopefully I'll prove that to you So no user is average If we were to assume that every user is average it it seems like It seems like the thing to do right you you figure out who your users are by doing user studies or tests or just making assumptions You find the middle ground you say I'm gonna build for these people that way I'm gonna reach the most number of people possible. I'm accounting for the bell curve in the middle There's this great talk though by Todd Rose Titled the myth of average. It's a TED talk and in his talk. He explains that if you design for the average You are literally designing for nobody I have a Bentley link to his talk here And if you think about the statement for a second it makes sense if you are planning for what's the average user like? How can I build for the average user? There's no one of your users in reality Who is that average person who hits all the those average marks? Everyone falls on a spectrum of the degrees you're trying to target so if we Want to build for our users we have to throw out the idea of the average user and recognize All our users have actual differences. We need to capture those from the onset of our project How do we do this? There's number of ways to do it one way that I think is very easy and simple to implement Is creating personas with limitations how many people here have heard of personas or use personas in their work? All right, great number of the room 85 90% so personas put it basically putting a story a face a name to Type of user and giving that to everyone on your project from your client to your designers to your developers and saying build for this person So to our personas we could list simple limitations that everyone has to build against for example this persona has red green color blindness such as I do and That's going to impact from your design what colors are used to emphasize things It's going to change how you approach your project It's a simple line that makes a big impact so you're building something that works for a person with something They can't control his limitation to people who don't have that Or what about has broken risk due to a skiing accident? This is like a temporary disability You want your CEO who's visiting your site to be able to make it to the donation page without using a mouse Because of this if you throw this in there you have to consider that situation Someone doesn't have a mouse doesn't have the ability to touch to navigate or Does most of their work while traveling this puts our persona in a scenario where they're very distracted They're cramped. They're uncomfortable. They have a small screen. They can only pay attention to a little bit of information that's going to drastically change how you approach your content design and How you approach your UX and what's important to the user? Three simple sentences to add that have a big impact that suddenly if you build for these differences is Going to change how you approach your project and you're going to throw an assumption that it's somebody can see the full spectrum of Color has full mobility and is in a nice lazy easy-going situation So if we use personas with limitations, it's going to help us get past that idea of average The second pillar every user deserves equal access if we believe that every user deserves equals access We have to throw out the idea that we can assume where our users are located We can assume what devices they're using and we can assume the speed they have to access our products There's this interesting statistic from it's from 2016 But in 2016 45% of internet browsing was from a desktop. That means 55% came from mobile devices or other devices This means for majority of our users. We don't know how they're accessing our Applications our websites. We don't know where they are when they're doing it or what their speed is So we can't assume they have a lot of data that they have a big screen We have to take into account how they're accessing and the differences therein So how can we change our workflow to adjust for this? Well, we can structure our markup our content our UX in a way that makes sense If we can't know the device that the person's using we can know the rules that all devices use to read data from The web and build for that one great way is using semantic markup semantic markup is the rule set around html tags and Reasons when you should use each tag. There's a small company. You might have heard of called the BBC. They run some TV stations They have open source their semantic markup Which they state from everything from an msis tag to an h1 header Everything in between when to use it and why and all their digital products follow it It's open source. You can follow it, too Using semantic markup guarantees that no matter what device is reading your content. It's gonna read it in the proper order It's gonna know that an h1 tag means a title and it is a title We can use progressive design to deliver our experiences and get back to the idea to remember that Designs on our websites are not there to make things look pretty. They're there to highlight what is important to the user So start with a very bare minimum I know the develop the designers out there are gonna hate me for saying this But do the bare minimum you can for design for highlighting what's important to the user and then as you learn about where your users are Coming from you collect real-world data as you start to analyze using tools What connections they have you can add on top of that experience add flashy design elements bigger images You know a JavaScript and you can progressively make the experience better But you start with the bare minimum that looks great for everybody And then we can prioritize what needs to be loaded Does your website need to load that third-party JavaScript library to work? Can it work without it doesn't need to have retina images? What about people who don't even load images who are using your screen readers? Is that imperative for delivering your message if it's not figure out a way to prioritize it how it's being loaded on the page So the most important things load first third pillar to provide understandable content to every user if We agree to provide understandable content to every user we have to all Admit to a fundamental truth of the internet to us our projects. We love the code. We love the algorithms We do we love the design the UX We want to show them off to our friends. We come to conferences to tell everybody look at the clever thing I did but to our users they only care about one thing and that's information They only come to our products our websites for content content is king as it always has been So if we want to make a positive impact on as many people as possible It it stands for reason that we want to write our content that is understandable by as many people as possible Some ways we can do this is make sure all the content we write is clear and direct When we can we want to avoid Jargon and use simple phrasing don't use 300 words when you can use two words What's the simplest way to say something that gets your message across? We should pay attention to our font our spacing and our line length for font If you're using a serif font for people who have dyslexic issues or on small screens Those serifs are going to run together where it's going to be hard to read if your letter spacing is really tiny Where it's going to run together. It's going to be hard for them to understand what you're trying to Say to them. So you stand serif fonts with some basic line spacing That makes it easy to read from far away from a small device for someone who Has a hard time reading words That was really a bad way to say that sentence And then line length it's interesting people on the internet. Do you does everyone here know how people on the internet read content? It's in an F pattern. What this means is Someone comes to your website. They read the first line of texts. They read the second line of texts They read half of the third line quarter the fourth line quarter the fifth line. They start to scan So we're cramming as much content as we can on a page There's a great deal of there's a great chance that people are going to start to miss what's important Again, this goes back to simple phrasing in line length. What's the minimum we can say to get our point across? And finally we can be meaningful with our content. We can use tools to check the readability score So readability, it's not the education level someone has but it's about the amount of mental effort It takes to understand what is being presented There are algorithms that will check readability scores for you and the ideal one nowadays is What's considered a sixth grade reading level that provides content that is? Complex enough that experienced users or native speakers will not get bored with the content But simple enough so that those who are not native speakers are not used to material will not get discouraged and we'll be able to understand it It's almost like the less they have to think about it the more they're going to absorb the less We're going to give them mental fatigue one of the tools I like to use for readability and I do it from everything from my tweets to my emails to client communications to the Content if I have to write it for websites is hemmingwayapp.com There's many other tools that you can use but hemming way up is great online resource put your content in there It's going to highlight complex sentences hard to read sentences It's going to highlight phrases that could be done simply or more simply And it's going to not catch everything for you, but it's going to give you an idea how complicated How much energy does my content take to understand can I simplify it? And then pillar number four to provide every user with trust and respect just as with the last pillar we had to Acknowledge that content is the most important to the users What's most important to us is our users information, but we also have to understand that it's their information They own it they control it. We're just usually asking for that data to view it So if we want that Information we have to give the users a reason why they can trust us with the data because trust is really hard to get on the Internet nowadays and we have to respect who they are So one of the ways I got interested in inclusive design was actually from this talk called inclusive design Excluding no gender by Sarah Lahren who's a UX developer out of Sweden. I want to I want to say And what Sarah Lahren talks in her talk One of the statements is the easiest way to do inclusive design is stop asking about gender and The great idea behind this if you abstract it is thinking about what information do you need to collect and why? So what Sarah does and when she has a client and she sees a form on their website that's asking gender question She stops them and says why are you collecting this data? What do you do with it? Most of the time they say well, we've always collected it Well, then it's doing nothing for you and it's potentially putting up a barrier to users whose information you want to collect and use On top of that if you're asking for gender You're probably just going to do a binary. Are you male or female people identified differently? Why would you? Assume what they are when you can have them tell you by using an open text field or additional options So going beyond this it's about being responsible with the data that we want to collect and having reasons Why we want to do it so every time your client wants to collect information every time your company wants to put up a form and Gather data about a user ask yourself. Do we have a reason for collecting it? Whether we're getting it actively from the user or passively through cookies or other metrics if you don't have a reason don't collect it Wait until you have a reason then collect it because again Especially with forms if there's a lot of form fields where you're gonna tell me about yourself I want to ask only information I need so I don't throw up a bunch of barriers to stop you from giving me that information We have to explain how we're gonna protect the data. There's a lot of reasons to do this Again trust is hard to earn on the internet. So if you want users to provide you accurate information Tell them how you're gonna protect their information actually protect it It's important to do make sure you're doing it in a responsible way and Then finally remember users data it belongs to them You're just asking to peek at it. So you have to make sure you're giving users access to control their information This is great for you because the more you can give users access to control their data The more accurate they're gonna make it you can take that all the way back to pillar one and learn more and more about your user base And build for their needs and make a positive impact on top of that, you know, it's going to become Standard that you give users complete control their data. How many people here have heard of GDPR there's been talks about Yeah, about 75% of the room. Look it up May 25th. I want to say late May It has a big impact especially for Europe but in America too if you have European visitors and you're collecting information You have to know about GDPR and give them control about of their data It only helps you Get accurate information. So this is a this was a short session. So this is a Real quick overview of these four pillars that no user is average. So don't treat them as average Treat them for their differences. Every user deserves equal access Don't make assumptions about how users are accessing your products But try to plan for the differences and how they access that data Provide understandable content to every user. How can you say things that's simply as possible? And then every user deserves our trust and respect How can you prove to users that you need their information and that you trust them to give you accurate information and they can control it? How many people here feel like they could agree to doing one of these pillars on their next or their current project? Raise your hand Good everybody in the room. That was a trick question if you didn't raise your hand Because you raised your hand you've been such a great audience. I'm gonna make this as simple as possible I'm gonna remove all the words. I don't need to have in there. No average equal access Understandable content trust and respect That what it boils down to If we can do these four things, what are we gonna do? But the thing we agreed to at the very beginning of this talk We're gonna make a positive impact on as many people as possible. We're gonna make the web better We're gonna make Drupal better. We're gonna make the world better Now I save some time because I have a bunch of resources for everybody here This presentation I've bitly links For for all these links. I have this presentation. It's annotated because I know you're not gonna hear me speak with my lovely speaking voice So every slide is annotated so that you can read the ideas behind it I have a bitly link to the left of that for IDX full This presentation is actually a 60 minute presentation that I cut in half for for a Drupal con So you can view the full presentation there. It has a lot more details and examples The myth of average I mentioned by Todd Rose. It's a TED talk. Check it out. It is a real eye-opener He he explains how assuming average helps the US Air Force back in the 50s or not assuming average Inclusive design excluding no gender by Sarah Leran. That was that talk on The simple way to do inclusive design is not asked about gender really eye-opening talk The BBC semantic guidelines for your use Check it out. Make sure you're using your HTML the way it's meant to be used And then if you haven't read this book in your UX developer Inclusive design patterns at IDX patterns a really great book to read It tells you how to do carousels in an inclusive way which one I hate carousels But if you have to do them do them excessively do them inclusively So with that I want to thank you for taking time for this short session If you have questions, we have some time you can come up to the mic or I can repeat for you But if you want to take afterwards you can find me on Twitter and Mike miles 86 I'll be around the conference for the rest of the conference and again my podcast if you want to check it out It's developing up comm so a round of applause and then five minutes for questions And I'll keep the resources link up there for for anybody who wants to copy them now Any questions Yeah, hi there. So first of all great talk. Thank you I was wondering what sort of strategies you use if you ever run into clients who are a little bit resistant to Accessibility or especially paying for it any ways you kind of get them on board with the overall concept Yeah, so in terms of accessibility the question was, you know, how do you get clients to who are hesitant to pay for it? great line to tell your clients is Developers are cheaper than lawyers so A good a great example of this there's been a couple over the years, but I think it was in 2009 target they were getting sued by the Association for the Blind American Association for the Blind and Because they didn't have captions on their images and they're like hey, this is acceptable. We can't understand what's on this page You got fix it targets like nah, I'm not gonna do that They got taken to court it cost them millions of dollars They had to pay the court they lost the court case they had to pay the court fees and they had to pay to have their website updated So that's a big example, but if you're having users who are going to be accessible Or you want to reach accessible users, you know It's cheaper to pay the extra developers to do it now then to pay lawyers later to fix it for you That could be hard for your clients to swallow But you can also say you know if you're building something to promote a product Wouldn't you want the maximum number of people to see this product to increase your revenue stream? It only helps you so my go-to line is developers are cheaper than lawyers We can also sit in awkward silence Four minutes if you want You're also free to leave you don't have to sit here But thank you if you any more questions, please please come on. Thank you