There you go. All right. Good morning and welcome to this week's edition of Encompass Live. I am your host, Krista Porter, here at the Nebraska Library Commission. Encompass Live is the Commission's weekly webinar series where we cover a variety of topics that may be of interest to libraries. We broadcast the show live every Wednesday morning at 10 a.m. Central Time. But if you're unable to join us Wednesdays, that's fine. We do record the show and then post it on our website and our archives for you to watch later at your convenience. And I'll show you at the end of today's show where you can access all of our recordings. Both the live show and the recordings are free and open to anyone to watch. So please do share with your friends, family, neighbors, colleagues, anyone you think might be interested in anything we have on Encompass Live. For those of you not from Nebraska, the Nebraska Library Commission is the state agency for libraries, so similar to your state library possibly. So we provide services and training and resources to all types of libraries in the state. So you will find shows on Encompass Live for all types of libraries. Public, academic, K-12, corrections, museums, archives, historical societies, really our only criteria is that it's something to do with libraries. We do book reviews, interviews, mini training sessions, demos of services and products, all sorts of things. We have Nebraska Library Commission staff that sometimes come on the show and do presentations about programings and things we're doing through the commission, but we also bring in guest speakers and that's what we have this morning. Today we're going, well Emily's going to talk about accessibility, not just for patrons, but also for us working in our library. So I will hand over to you Emily to introduce yourself and take it away. Awesome. So yeah, my name is Emily Gaywicky. I'm with the University of Nebraska Libraries. I do tech services and we're going to talk about accessibility. A lot of us have probably done posters or flyers or podcasts about books for our patrons. And so we're familiar with those public service ADA requirements, but when we're sending an email or a workflow or just a memo between colleagues, we might not put in all of that effort. So we're going to talk a little bit about why that's important, how it's different from doing it for the public, and then a couple of those major things. I have a lot about alt text, captioning and subtitles, navigation, and then some more advanced things towards the end. So we'll take a start about defining disability. There's two major models. We have the medical model and we have the social model. Medical is a physical or mental condition causes disability. And the social model is that inaccessibility causes disability. And as we're going through today, I'm taking a social model, look at things, that if we make things accessible, people won't have a non-ability to do things. They won't have a disability to access our ability to products. The World Health Organization, they estimate about 15% of the population has some variation of a disability. U.S. Census puts that rate at almost 30%. So it's kind of low to me. It's a lot, but we also had a recent major pandemic that is going to have disability effects. So that 30%, I think is about a five or six year old statistic because it's the census and it takes a little bit. But that number is probably going to go up at least a little bit within the coming years as disability from the pandemic goes. Disabilities involve lots of things. We have those physical ones that we could see, but there's also cognitive ones like brain injuries or brain fog and hearing disabilities that we need to accommodate for in our co-workers. Accessibility and universal design. We hear that all the time in libraries. People need to be able to access things no matter who they are, their age, sizeability, disability, all sorts of things. Accommodation is an adjustment to a work or job compared to how things are usually done. And accommodation is a legal requirement and they're covered by ADA. If someone has that paperwork, you have to do it. We're going to talk a bit more about voluntary accessibility and why we should be doing it, even if there is no accommodation paperwork. Why do we do this? You're either disabled or you might be in the future.  And people also frequently will develop a disability as they age. Glasses is a major one that you'll see as is hearing loss. And if we aim for it now, our co-workers won't have to tell us when they have a migraine or when their vision is getting a little blurry. It's already there, already taken care of. These accessible items, they can also stand without you there. If you're out for the week on vacation or just aren't in the office one day, someone can still take that work form, that internal document and make pretty decent sense of it without having to ask you a question because you made it as clear and accessible as possible. How it's different from the public, outside of accommodations, there's almost no legal requirement to do it, it's voluntary. For many people, it's a hidden need. They're not going to ask a co-worker, they're just going to struggle through or make the changes on their own. And we're doing this more for interpersonal and work community developer than for the benefit of all of society. Showing our co-worker, hey, I did this not because I have to, but because I care about making more life easier, even if you don't need to ask me. So the first thing is alt text. We've heard about this a little bit. You see it in videos or major ADA things. And it's going to be the major thing that you're going to work with internal documentation. We're going to write memos or emails, things that might have images and graphics. So this is going to be a big part. Alt text as just a general definition is a hidden description of a visual element. You can't just look at the page and see it. It's usable by a screen reader. It can be used by those with a limited vision capabilities, including blind. And in certain ways, it can be used if you have weak internet. It can be put up instead of an image to lower download necessity. And just the bare bone rules of how to make it. Don't put something like image of in your alt text. When a screen reader is going through a text and it hits an image with alt text, it will say image, and then it begins reading the alt text. So if it says image, image of, image picture of, or however, it's duplicative and not necessary. Next thing, keep it very brief. You get one, two sentences. A lot of alt text is also a maximum of 100 characters. So we're not putting in three, four paragraphs here. Ah, be mindful of the context. The alt text for your boss might be a bit different than the alt text for your coworkers. It might not be. It could be. But kind of keep that in mind as you're making it. And then say you've got just a pretty clip art or like a filigree somewhere on your page that doesn't add anything to the text or the document. There are ways you can just mark it as decorative so that the screen reader skips right over it and you don't have to put like a smiley face as a description. So here are some examples of that alt text I found. I have come across using screen readers before. On the screen here, we have some pretty roses and I have seen the alt text for those roses to be random numbers. And if you're using text-to-speech, you can't fast forward very easily. So all of a sudden you come across image and then it's slowly reading out all of these numbers or trying to turn them into like billion million. That's really annoying and doesn't do anything and can be jarring to processing the documents. Same with the word plant or the date. And I've even seen an alt text that was automatic that was just the copyright information. And when you're talking about how to catalog a book in a document for a coworker, a copyright statement in the middle of the text is not useful or helpful. So we'll go into some like better examples. I chose some non-library examples just to kind of give an extreme way to show context. So Grand Flora Rosa Blooms is what kind of flowers these are. A botanist, that would make sense to them. If you're just talking to hobby gardeners, a different context, collection of pink Queen Elizabeth roses would be great. And kids, pink roses in a bush. It gets the point across, it's accurate, and it takes into account who we're speaking to and what they want to know from the picture. Now, in internal documentation, we're never working, well rarely going to be working, with a pretty picture of flowers. We're going to be working with slow charts, hierarchies, pie charts, all sorts of really complicated pictures or images that need a lot of description, things that won't fit into one or two sentences, that won't fit in 100 characters. So how do we handle that part? Complex images. So the first step is going to be that same traditional alt text, just aim for something basic. If you have a picture in your workflow of some buttons on a website and they're labeled A, B, C, etc., a good alt text for that would just be an array of buttons with labels. And then beyond the alt text, we add an alternative description. Text and description can be synonyms, here they mean different things, extra very short descriptions, very long. There are three major options of how to do alternative descriptions. The first is to do a caption underneath your image that has maybe the statistics you're looking at or more information because you can do several sentences as part of a caption. Another option in my personal favorite, what I tend to do, is I discuss the image and the body of the text. So if I'm referencing button A, instead of just saying button A in the text, I will say button A, a blue or a small blue button towards the top of the page labeled submit and then go on with my description so that they can tell where it would be in the image, but I'm discussing as part of the text. And the third option is for remarkably complex images, hierarchies that are made like massive flow charts that have tons of subsets, is to just link to a completely different page, a different Word document or a different website. After your image, you can put something that says link to alternative description as a hyperlink. Go to a new page and describe it in as deep of detail as you would like. The three pages as long as it gets the information across and correctly. When we're building that alt text, the major thing we're looking for is the idea or the conclusion makes sense and is discernible. We also want to look for alternative ways to communicate data. If we're doing a pie chart, we could pair it with like a data table that might be easier for a screen reader to handle and we're looking to communicate the information of the image over what it looks like. So if we're doing a bar chart, we don't need to say category A is a red hash marked tower halfway up the image. It can be category A is 50% or however you're doing that data. I have a resource for the guides. It's called complex images for all learners by Supanda Amornja. They are from Western Illinois University and they wrote a handbook on so many different types of complex images and they have a little section for each one. How can we turn this into a text description? How can we do a list, a data table, and even how to turn our complex images into tactile or braille images so that they're still usable even without technology? So I have a link to that at the end that will help get to that real quick. So we're just going to go on to how to do alt text physically. When trying to add or edit alt text, Microsoft Word and Suite are pretty easy. You can do a right click or a secondary click, whatever your mouse is set up to do and then click view alt text. It'll pop up on the side of your screen and you can change it. Microsoft Word does auto-generate alt text for good or bad, but you really want to make sure you go in and edit it just because their AI is not great. Google Docs is the same concept right or secondary click and then choose the option alt text. But if you just use a keyboard, if the image is selected, you can just hit control alt and y and it will open it as well. As I just mentioned though, a lot of programs are starting to use artificial intelligence and AI to auto-generate alt text for images. And this is a great first start to making things automatically accessible. But AI isn't that smart sometimes. So it's just going to say the most basic thing or it's going to guess completely wrong on what it images. With those pictures of flowers that I had earlier, it said flower as the alt text instead of anything more interesting or more descriptive. So while it is a great start, I would advocate that you try to avoid it.  You add yourself. But if you do use it, just make sure you proofread it. Microsoft adds a phrase at the end of their alt text that they generate saying it was generated with x amount of confidence, which is unnecessary information for the user or your coworker or whomever to read. I've seen that coming up in my Facebook posts. I've been doing a lot of posting images of things for conferences and events and for promoting Encompass Live and whatnot. I noticed that I already have alt text. I didn't do it yet. Oh, it did it for me. And it does do that image of or might be a picture of. Delete, delete, delete. Yeah, it tries really hard. But it's just a start. AI is developing. We've seen it and then do so much recently. But when it comes to alt text, it's got a little bit to learn. Yes, we're getting there. But for alt text, that's a big basics for it. Next thing we can talk about is the auditory support. Not everyone can hear. Not everyone can understand. But videos and your voice recordings are not your only problem when we're talking about how to support audio. If you are telling someone or writing a document on how a machine like a printer might work. And it makes a little ding when it's done doing whatever process. If you're deaf, you can hear the ding. So you want to look when you're writing these workflows of what else you can tell someone to indicate that something has happened. Maybe with the ding, a little light turns on or a screen flashes or something that you can also add to support. And when you're choosing how you want to make this support, you have to look at what you're communicating. What technology your coworkers might have access to. And just decide overall what's important. Do they need to know that it dinged or is that just kind of fancy? So as I talked about a little bit with the ding and the light, that's a coexisting queue. So one thing happens and something else will happen until the exact same information. It's a great option if we're talking about processes, machines, things of that nature. For typical audio support with voice, we have captioning. There are two major types that's open and closed. On the screen right now, my captioning is called open captioning because you can't turn it off. Closed captioning is what you would normally see on TV, Netflix, YouTube, where the user would have to say, yes, I would like to see captioning, please. Major thing with both of them, they need to be an exact match of what is said. That includes saying, um, and that includes profanity. You're not going to censor the point of the caption is to let someone know exactly what was said, not do sentence and grammar repair after the fact. Transcripts are another thing that you can use for presentations if someone had to miss a meeting or something. They are a form added and edited transcript of what was said. And when I say edited, I mean adding things like punctuation, capitals and fixing spelling, not taking out the um, they're very labor intensive, but they are very useful for people who need some tools we have. I just said don't use AI. I'm going to flip on this one. AI is very useful for automatic transcription. My text at the bottom of the screen is automatic transcription using Microsoft AI. I believe Microsoft AI. It's not 100% accurate, but it is better than not having anything. It is great for major vocabulary, normal conversation. If you have a fun name, like gay wiki, it's not going to say the correct words, but it gets the idea crossed at the sound. For live presentation, that's what you can see here. Powerpoint does it, Google Slides does it. A couple others probably do it. And if your software doesn't normally, web captioner is a free software online you can use to caption things in real time using AI. But if you're just sending a video to your coworkers of how to do something, you can use that web captioner and it'll do the same thing. As was stated at the beginning, YouTube adds captions automatically. They're not perfect, but once again, better than nothing. And if you have all the time in the world, have a little extra budget, or are really good at computers, you can make something called an SRT file. I believe it's sub, rip, transcript, and they are the file that you paired to a video that adds the subtitles into it. Ooh, they are complex to write, but there are ways you can find online to at least make the framework for you. Or if you've got tons of time, you can hand write them in things like Notepad. And then you can upload them into YouTube or with your video and it will show on the bottom as correct and properly timed subtitles. That's a very over the top option, but it's good to know that those exist and how that works. Next thing is navigation is a quick thing to do for your coworkers. Not everyone can use the TrapPad or not everyone can use a mouse. So we want to aim to make sure that they can still get around our workflows, get around our documents. It also aids just in quick skimming of our documents because it is a heading based system. And when we're setting it up, we can think of it kind of like bullet points made with text styles. Sounds very weird. But we start off with a heading one, heading one only used one. Then two, three, I kind of see a diagram on the screen right now of what that could look like. We don't skip from two to four, but it can help. And then how to turn it on. It varies by the program you're using. Microsoft, it's a home tab, ribbon style function. And you highlight whatever heading you want to change. And then you apply that style. And then it will change how your words look. You can go back and change how it looks and it'll keep that heading. Style hidden. So it's still navigation. Google Docs is under the format tab. It's a paragraph style. They have a lot of heading options. I think they have up to heading number seven. So they're a great tool to make sure you have lots of options for navigation. And then I don't know how much internal documentation you might be making with HTML. Maybe you like HTML editors for writing things. But, you know, heading start, break heading, basic coding to get that to work. So before we go on, that was the basics. Does anyone have a question about these three major topics before I go on some other things? If anybody has any questions, type into the question section of your go-to webinar interface. I'm monitoring that here and I can read it off for you. Nothing came in while you were talking, Emily. So I can't see if you're typing. So just give a minute or so here for me to see if anything pops up. That was partially so I could get a drink of water. I don't see anything right now. I'll just keep an eye on it. If anybody does, I need to type in your questions or comments. Oh, wait, of course. As soon as I say something. Thanks, Amy. Amy wants to know, okay. And you could repeat this, Emily, then. So it gets into the closed captioning for you too. How difficult is Microsoft AI to set up for closed captioning? Microsoft AI to set up for closed captioning is very, very easy. Nice. Okay.  Yes, we can see that on your screen. Yes. Awesome. So there's this one that's right here and it will do subtitling. And you just hit that. It'll say we're turning this on. You hit okay. And now you have captioning on your PowerPoint. It is very easy. Google slides is about just as easy to turn on. You start presenting and then there will be an option somewhere on your screen to just hit start transcribing. So very easy to start the AI Microsoft captioning. And as you can see, when we're using PowerPoint within GoToWebinar, it adjusts and shows not just a slide, but everything kind of shrinks up. So you can see that below. It's not cut off or anything. Yep. It makes it proportional, I guess. Yes. So very easy, very, very useful. Awesome. Awesome. Right. But I see anything else right now. Go ahead, Emily. And if anybody does have any questions, anything pops into your mind, just go ahead and type it in and I'll keep an eye on it. We do a thank you for that answer. Yeah. Cool. So these next couple of things we're going to talk about are not ADA things. These are nice things we can do to make our documents accessible to as many people as possible. That first thing is going to be clarity of language.  So we want to try to avoid as much confusion as possible and use as much clear language as we can. This can benefit English second language speakers, people from different background, England, Australia, and the US all have very different ways of speaking. And it can also benefit people who have processing and cognitive disorders that can lead to issues, understanding spoken language, as well as issues, understanding written text. So when we're making our workflows, we have a couple of things that we want to avoid to make things as clear as possible for as many people. First is undefined technical jargon or abbreviations. Next would be slang or idioms, because they don't translate well. Vagueness, saying exactly what we mean. And then we want to avoid double speak. Double speak is saying one thing and meaning a different thing. A good example you will see is if someone says, hey, go put away these books, and they actually mean put away the books and shelf read and clean and all these things. Just say exactly what you're trying to say. So I have some examples. There it goes. So for jargon or abbreviations, the 245 needs to follow this format. If none of you catalog or have to work with mark files very often, 245 is no logical thing. So we would rephrase it. We can still use that 245, but we can say the 245, the title field, needs to follow this format. Because most everyone is going to understand what a title is. Everyone in a library is going to understand what the title is. In terms of slang and idioms, the new project is a cake walk. Making a cake is very difficult and cakes don't have legs. So why does it mean something is easy? I have no idea. I'm an adult, so I've memorized it. But when we're saying something is easy or difficult, using those adjectives that are part of the normal language, it's a lot easier than using an idiom that might not translate well. Vagueness. Put the item with the others. If they knew where the other things were, you wouldn't need to tell them, nor would they ask you. So we can say specifically, put the item on the shelf with the blue tag. We've told them exactly what we need. They don't have to ask a follow-up question and it's clear. And then an example of the double-speak that I've encountered. How did you find the material? And what they were actually asking is how did you learn about this material? These two questions will list different answers depending on how thoroughly you take questions. So making sure that whatever sentence you put, question you ask, things of that nature are going to elicit the correct type of information. If you want to know where they put something, ask them where they put it, not where did it go. Things like that. That is probably going to be one of the hardest concepts for a lot of people to learn because English, once again, is a ridiculous language. And we can ask the same question in so many different ways, slightly different from each other. So it could take a lot of work to figure out that specifically. The next thing we can do, did it change? There it goes, is doing multiple formats for our workflows, our internal documents. If you make a video, you could put a Word document with it. If you do a Word document, maybe make a checklist. This allows people to choose however they want to get their information, whatever works best for their brain, their body, or their situation. If you have a co-worker who is going to be doing some work out in the public with individuals, a video training them on how to do it is a great option until they're out in the field and need a refresher on something. Then they can't put the video or they can't see the checklist. So a checklist will be better. Or they're in a really loud environment and they want to just read it. Having all of them together makes things just a little bit easier. And not everything has to be the same type of offerings, but try to keep it consistent. Some examples of how that would look. How to catalog a book as a training document. I have one that I wrote. It's about 20 pages. It's great if you've never done it before. If you're looking for just one piece of information, it is the most infuriating thing to go through. So to make it more accessible, I have quick checklists that it's a couple pages and then a little short list that's like a sticky note long. That allows me to just hand it off to somebody who already knows kind of what's going on to be able to take over something for a day. Me to refresh or a full training document for someone brand new. Maybe we're teaching a co-worker how to use a new piece of tech that we've got. Video, great first option. But as I was just mentioning with doing fieldwork, a video might not be loadable. So a Word document expressing very similar information would be a good option. But for people who can't necessarily read large blocks of text video is the better option, giving them that choice between the two. And the Word document also very similar to that transcript with the stills from videos. And then presentations. We teach our co-workers in person all the time. In person? Step number one, that's one format. We can also just distribute the slides. I'll have these posted after this so you guys can just go look at them. And then transcripts, same thing. So people can read it instead of listening to it. Give people as many options as you can do that makes sense. And then try to keep your offerings and your formats consistent. So don't make this document like one font in this big way in this one unique formatting way. And then this other one is super basic. Try to keep them all looking similarly formatted. So people aren't having to change how they're reading every single time they switch. Keep in mind the common tech. People aren't usually using overhead projectors nowadays, so you don't have to do that. But people use a lot of cell phones nowadays. So if you're expecting someone to be able to access something on the small screen, make sure you keep that in mind when you're formatting. And then a big thing that you see a lot in accessibility is fonts. You'll hear talk about a share of font and a sans share of fonts, which ones are better for dyslexia and better for paper and better for screens. There are so many options for fonts. There are no truly wrong answers because every font says something a little different. But when you're looking for good accessible fonts, you've got three big principles in postures, making sure that things don't look like each other. Dissernability, meaning that if something gets blurry, it still looks unique. And mirroring, so if something rotates or flips, it still looks like it's on letter. I have more examples. First one is not a font you probably want to use in an internal document. It's Broadway. That first section is a capital I in the lower case L and the number one. And they look very similar to each other. So lots of imposters, hard to tell the difference. C and O are discernibility. If the C gets blurry, it's going to look like the O or if it gets too close to a different letter. And D, P, D, B, Q into P, those are all the same letters just turned around. I tested it. You can take a screenshot of those four letters and turn it all over the place and it's still going to look like those letters, just in different spots now. So we want to avoid things like that where mirroring is really common. Bernana, Verdana is my favorite font. It's what I have this presentation in. Imposter is really good. Dissernability is pretty decent. Mirroring's good. Times New Roman. A really popular font, especially in academics. It's a serif font, so it's got the little feet and the little decorations on the ends of letters. It's a pretty decent font, but there's a lot of talk about how a serif font might not be a good choice for dyslexia or for readability. There's lots of research still going into this, so make your best educated guess on a day to day basis. There might be more research and more fonts coming out in the future. But Calibri is what's replacing Times New Roman in a lot of places. All postures or the imposters, discernability, mirroring, all good. But for example, the State Department, the US State Department just changed their website from Times New Roman to Calibri for accessibility reasons. I think within the last month, so sometime January 2023, and then I have my favorite chaos example. This is what I write my personal documentation in when I'm just writing it and haven't shared it yet. I do it in Comic Sans because it's the easiest for me to read. As you can see, there's no imposters. Dissernability is excellent, and there's no mirroring. I wouldn't say send an important memo to your boss in Comic Sans, but also it's a really good font for readability and accessibility. But it's a good example of what you're looking for to apply the concepts to others, but I am advocating for chaos. It has a bad reputation. It really does. It's a good font. Completely inappropriate settings, yeah. Yeah, but if you have issues reading big blocks of text, try flipping the font to Comic Sans, and it might be very useful to read a PDF in Comic Sans, or not a PDF, a Word document. It's interesting as the State Department switched to Calibri because looking at your comparisons here, those first two letters, like the second one, it looks like one of those bar lines to me, not like a letter. And I would prefer the Verdana, like you said, over Calibri, but yeah. Yeah, that was an interesting choice, but I know Calibri, I think, is more widely accessible on more computers. I think Verdana might be limited to windows or something like that. But it's a little bit better than Times New Roman, because L and one look identical in Times New Roman, to me. Yes, definitely that, yeah. So when it comes to font, there's never going to be a perfect choice because every individual is a little bit different, hence the word individual. But Calibri is a little bit better than Times New Roman, so we're moving forward, maybe just not very far. But I've got some closing up things, just things to remember. The first thing is you're not perfect, this is new for you, or could be new for you. So be willing to try something that you've not done before. If you've never used captioning on a PowerPoint, make that your very first step next time you do something for a coworker. Try new things, try new processes in this. Next is be open about learning. You're here, so great first step. But accessibility progress goes really fast sometimes. People change fonts, new fonts come out. AI progresses really fast, so try to keep an eye on what's going on in the world. Except the feedback you get, every person is going to have a little bit of thought on what you do.  Keep that in mind next time you go to do something and realize, hey, the technology or the environment or the preferences of my coworkers are these things. Let's do that when I make my internal documentation. And be comfortable remaking things. You probably have internal documentation that's been sitting around for maybe a couple of weeks, maybe several dozen years. You might have to update it. Maybe rewrite it, re-record it, add alt text to things. Going back and changing and updating is a good thing. This isn't something you can just start now and be better about. You can always go back and improve. And then remember the things are going to change. AI wasn't a huge thing in the public spotlight a couple of years ago. AI transcription on Microsoft slides came within the last year or so. New ADA standards come about every couple of years. Web standards change. So don't get set in the mindset of what I've done here is perfect because in 10 years you might need to change how you did it. Just keep that in mind. Be flexible. But that is too, there it goes, the bulk of my information. But I have here a little URL and a QR code board as well that has a little site that has the slides for this, as well as a link for a bunch of different resources, including that handbook that I gave you, the ADA standards and the federal standards, a book recommendation, and some other things like that that can help answer specific situational questions that I just can't address as many in a presentation. So now is a new time for questions if anyone has them. Great. Yes, thank you, Emily. Yes, anybody does have any questions that you want to ask? Definitely get them in. We still have about 10 minutes left in our time for today's show. But we'll go as long as you all have questions. We do have a question about the auto captioning. When auto captioning is turned on and recordings underway, do the systems have much difficulty with heavily accented speech? I would think that might make a difference. So if the system has issues with heavily accented or heavy accents, I have a Midwestern accent. So I've never tried it. And I haven't seen really anyone use it with a heavy accent. So it would very much depend maybe on what the accent is, if it is like an English or an Australian accent that's very heavy, it might have an easier time than like a French accent or a Japanese accent. The best option is to maybe go through and try a couple practice with the micro, but like see what Microsoft captions look like and try Google Slides and try web caption and see what works best for the heavy accent you've thought. Yeah, practice it. I know I've attended some sessions where they have various types of auto captioning on it. I'm not sure what program they're using sometimes. But I think something, if we're going to start using this, is like you've been talking today. And for some people, it's difficult slowing down your speech just in general. Because if you talk very fast, it's not going to catch what you're saying. It might skip some words. I've seen that happen in presentations, or it will just have to guess and put in something that's completely, oh, that is not at all what the person just said, because they've been so, so fast. It just doesn't, it can't catch it all. So you kind of have to practice. And I think that would help possibly with just anything an accent. Practice slower, more clearly, more deliberately, so that the system can recognize whatever you're saying. And like I said, practice ahead of time. See what it does do when you say things. Yeah. And then also, if you're talking about really complicated niche topics, that could also be a big issue, because it's working off of the vocabulary and matching what you say to that. If you are saying like a dinosaur name or something, it might not match. So keep that in mind as well. And practice your actual topic with each captioning software to figure out what's going to work best for you. Yeah. Absolutely. All right. Anybody have any other questions? I didn't see anything else come in. But please do get your questions in. Use the go to webinar, interface the questions section. You can type in your question there. Excuse me. I actually, while you were talking, I was paying attention, honestly. But I did go and check out that web captioner just to see what it was doing, how it worked. It's working pretty well. It was catching what you were saying. I was comparing it to what was coming up on your PowerPoint. PowerPoint is way more accurate. I'll tell you that. But it's not bad. It does only work in Chrome though. That is something to be where I found out I default to Firefox as my browser and it said, nope. If you want us to do another, because it uses Chrome, Google's AI is its basis for doing it. So I had to pop over to Chrome. So not bad. I'm going to start experimenting with it. Yeah. Getting, I think web captioner also is a feature where it will make a transcript for you. So that can also be useful. Yeah. There was something about that. I'm going to see what that looks like afterwards. Yeah. All right. I don't see any other questions, desperate questions coming in right now. Just more thank yous. You're welcome. I think if nobody, nobody has any desperate questions they need to ask right now or they want, they're thinking of right now, that's okay. We can wrap things up. No problem. We're almost at our hour. There is Emily's contact information. You can always reach out to her. If you do have any questions, comments, thoughts, you want to discuss with her. Her link is there. As she said, the slides will be available along with the recording when we get that put up. And I'm going to show you where that will be. So you'll have access to all of this afterwards as well. Okay. Okay. Question just came out. I'm not sure I understand it. It just says what is purpose of navigation? Okay. So the purpose of navigation, it allows someone to go through a document without the scroll wheel on a mouse or without their track pad. They can use a keyboard shortcut to go from section to section to section. It helps with that. It also makes a sort an outline of the document on the side of your window. So you can go over there and just quick get to something instead of scrolling that will create a lot of flashing. So it can be good for physical mobility as well as for very sensitive light or people who are very sensitive to light and flashing. So. Okay. Thank you. That explains. Nice. Thank you. They said yes. Awesome. All right. Just waiting to see if anything else pops up. Anyone other questions? All right. I am going to pull presenter control back to my screen. So thank you, everybody, for being here today. Thank you, Emily, for sharing with us your presentation. This is great. Lots of awesome information. Like I said, I'm already trying out one option for captioning just to see how it works. As I said, we have unfortunately with GoToWebinar, they do not have any built-in live captions. We have to use what you have, something else. And having other options are always good too because you never know what someone is going to use. All right. So this is our session page for today's show. If you go to our main Encompass Live page and if you just Google, use your search engine of choice. Encompass Live is the only thing called this. Our show is the only thing called that on the internet. So you'll find it right up at the top of your search results. No one else is allowed to use our name. These are upcoming shows, but to get our archives, there's a link right here at the bottom. Most recent show is at the top of the page. There's last weeks. Today's will be here by the end of the day tomorrow. Everything should be processed and ready. There'll be a link to the recording in our YouTube channel and a link to Emily Slides. Everyone who attended today's show and registered for today's show will get an email from me letting you know when the recording is available. We also push that information out to our Nebraska Library Commission mailing lists. And Encompass Live, we have a Facebook page that if you like to use Facebook, you can go over there, pop over there and see. Here's a reminder to log into today's show, meet the speakers, but then there we go. Here's a recording from last week's. We post over there and onto Twitter and Instagram using our hashtag and comp live a little abbreviation of our name. So if you like to use any of those places resources, you can go over there and you'll see when the recording is ready. Or you can just pop back here and look for it. While we're here, I'll show you. We do have a search feature. If you want to search our archives to see if we've done any show and any topic you're interested in, you can do so. You can search the full show archives or just the most recent 12 months. That is because this is our full archives going back to when Encompass Live premiered, and I'll show you here.  I'm going to scroll real fast. January 2009 was our first show. So we are in the 15th year of Encompass Live, and all of our shows are here. I'm going to go back up to the top now. So just pay attention to original broadcast dates of anything. Many shows will spend standard test of time, still be good, valid, good resources, but some things, information will come old, outdated, links may no longer work anymore, resources may have disappeared, people may work at different libraries from when they presented with us five, 10, 15 years ago. So just pay attention to that original broadcast date whenever you do watch a recording of one of our shows. Something else I want to highlight here before we wrap up is, in addition to this weekly show that we host at the Nebraska Library Commission, we also host and run the Big Talk from Small Libraries online conference. This is coming up at the end of the month. It's always the last Friday in February, and it is, we do this with the Association for Rural and Small Libraries. All of our speakers are from libraries with an FTE or population served of 10,000 or less. So please do register for it. Our registration is open. The schedule is up so you can see what all of our sessions will be for the day. Our speaker information is all up there as well so you can see who all of our speakers are. So please do register. It's free and open to anybody across the country, across the world, anyone who wants to watch. And so we invite you to please do that and spread the word about the conference. Anyone who's interested in what's going on in our small libraries, please do join us for Big Talk at the end of February. And our next topic for Encompass Live next week will be Digital Libraries as Digital Third Place Virtual Library Programming. Staff from other University of Nebraska locations. Emily is from UNL in Lincoln, but we're having staff from our Carney and Omaha locations come on and talk about virtual library programming. So if you're interested in that, sign up for that or any of our other upcoming shows that we have coming up in the next few months. Other than that, I didn't see any of the new questions coming in while I was doing my wrap up so I think we are good for today's show. Thank you everybody for being here. Thank you Emily. Good to see you. Thank you. And hopefully we'll see you all on a future episode of Encompass Live. Bye-bye.


Hi, my name's Darren Smith. I'm the officer in charge of the Logan District Road Policing Unit for the Queensland Police Service. Here's some helpful hints and tips that will help you have a safe and enjoyable time riding your motorcycle on the roadway.  So make sure that you practice regularly, practice tight turns, practice your figure rates, help improve your safety and skills on the roadway. As police we want you to be out there to have fun on the road.


Hey everyone back here live in Austin for Linux Foundation open source summit You know, we haven't really spoken about it, but there's a large Expo floor up on floor four. We're on floor two some great companies Exhibiting up there talking to people joining in the conversation. I want to introduce you to a company. We haven't covered Before on tech strong on any of our brands and that is layer five and I'm here with Lee Calico from layer five We get that right. Oh, that's that's correct layer five. Lee Calico. You're speaking of great companies. Okay, let's talk about layer five All right, man. Let's jump in. Well before we go. What's your position with layer five? Yeah founder and CEO so Excellent, you're the right person to talk to that. Yeah, I think so. All right. So tell talk to me What what's layer five about? Yeah? Well, I've been been around for a couple of years now been focused on Open source community first some of we built a couple of open source projects from scratch. They're cloud native centric. They're actually Service mesh centric in nature There's about three of them two of them have recently landed into the CNCF Actually, now that I think of it, there's an annual review of one of them coming up To step back for a moment and say like a layer five is sort of mission and vision in general is Well is a recognition that like the Infrastructure is quite capable these days and we aim to Enable service teams to expect more from their infrastructure To help them extract more value than maybe they recognize that's there Okay, we really think that we've had an initial focus and start toward Service mesh as an intelligent layer that you can program and tell it to do various things we think that there's a lot of untapped power in the Network and that's really important to microservices and lots of requests transiting the network and so we're here to Will help people wield that power in a self-service way? excellent, so Look when we look at Service mesh right so I've been going to cube cons and everything well before COVID and all and you know before COVID it really seemed like service mesh was where The action was right people were using kubernetes, but now as we layered on Security and network and all these services. We needed a way for them to communicate talk to each other Interact and and that service mesh became the sort of the API hub if you will lack of a better word Where all that action was taken place and then we saw several different kind of service mesh right Istio, which only recently became part of CNCF right it was Google Is it link or D is another yeah, right and you mentioned a couple that your company have yeah There's well actually it's kind of interesting just within the CNCF as actually one of the roles that I play is the Chair for the technical advisory group for network for the CNCF and so with Istio's recent donation or It being donated as a recent project rather is Well, if I get the count right, I think that that's Depends on how you count, but it's either five or six service mesh is just in the CNCF Right and that excludes service mesh implementations that are outside of the CNCF and so Yeah, it's a crowd now one may look at that and say well obviously that is just or not justification But proof that the service mesh area is a really big area that's very Important to people and and you know It's gonna need a good solution The flip side is the fact that there's so many of them means none of them are doing great right now They're all kind of works in progress and we'll have to see what What comes out of this yeah, how they're how the adoption how the adoption how they mature, right? It's it's still relatively immature networking is a deep deep kind of a deep and wide area that you know I don't know that that I guess I'll commonly say that if you were to Like reflect on this this position that service meshes are in with the number of them that there are if you look at Something relevant like container orchestrators and so Kubernetes having Is enjoying the most popularity but by by far But previously with a litany of others that I won't I won't prattle off But there's a whole bunch of them right that you know the road to perdition is littered with the best of intentions Yeah, right and from Docker on on down and I think we'll eventually eventually we might see something similar happen with service match and it It's I Guess I would put it this yeah I think that that's totally true that you could we could step ourselves outside of the tech industry and just Look at soft drinks, you know and use some other relevant examples, right? There are winners and losers in every one, but but here's the other thing. I think You know taking a uniquely open source view of this whole thing is when you have So you're gonna have some open source solution or maybe there'll be two or three solutions that are really popular and they'll be the de facto Winners standards that people use but then you'll have commercial companies that are Harnessing those leveraging those but but that's the way of open source, right? So we all start here and then commercial companies build on top of it And is that sort of where layer five wants to be yeah, that's about yeah, it captures it pretty well that Well, we were kind of said these things are kind of deep and complex They're more capable than some people choose to use or really comprehend can be a big scary old thing to Be running well Kubernetes any of this infrastructure at at scale or or or even not at scale to I know that if I were in the operator's seat Gosh, I might have to just change my shorts if I as I go to like make a change in Absolutely, this traffic supposed to go there and it's crazy what goes on the amount I mean the kinds of traffic that we see now and it is just crazy So you mentioned another role that you have though besides being CEO of layer five and that is chairman of the of the attack of Technical advisory committee for network for CNCF. So that includes service mesh is a big part of it What else is a part of that there are other kind of well the term network gets expanded from there, but kind of well things like Core DNS g rpc It's gonna stretch my the Other network centric projects that I'm drawing a blank on at the moment Well, don't don't knock yourself down. Let's talk DNS. It was just so funny. I actually had a I Call me young guy. They're all young young researcher here who is the Dan Kaminsky Fellowship Winner and of course Dan is the guy who discovered the huge DNS Vulnerability that kind of broke the internet, right and as a result of that we DNS as a As a thing became real right people started. Hey, we better make sure our DNS is Tight right lockdown secure Scalable what what what's going on in the world of CNCF around DNS Yeah, there's well core DNS as a project specifically has become in the earlier days of Kubernetes there was a different DNS implementation and core DNS has Been sort of a cloud native implementation from from scratch and become the de facto DNS offering within your group at least your vanilla distributions of There's been it's to your point that gets DNS is a is a wonderful Like makes for a wonderful attack vector for getting into organizations being able to slip in the middle and kind of redirect some of that traffic with without people knowing and You know, it's one of the older Like like TCP early like a lot of what the internet is comprised of it DNS is one of your older inherited and Well like a lot of the infrastructure that we keep around it Needs to needs to continue to evolve to with a real security centric perspective Absolutely, we end up within the CNCF tag network. There are a couple of working groups Within it the one that's the most active is the service match working group So back to your point about the buzzeness of that the topic And tends to be the one that I focused the most on yeah No, I think it's it's one getting the most oxygen. That's for sure. You know, we didn't tell people Layer five. Where can they go on the web to find out layer five dot IO? Well, la y er Number five number five dot IO