WEBVTT 00:00:00.000 --> 00:00:05.580 All right, we're gonna do a quick audio check,  um. Hopefully, you guys, if you can see me and   00:00:05.580 --> 00:00:10.380 hear me, please put a one in the chat. You can  just make sure that we have a smooth transition. 00:00:16.560 --> 00:00:17.400 Excellent. 00:00:19.440 --> 00:00:23.460 All right. Hello, Interpreter  K, we see you. How are you? 00:00:25.140 --> 00:00:30.000 All right, excellent, excellent. All right, guys,   00:00:30.840 --> 00:00:36.240 um, hopefully everybody had an enjoyable  10-minute break. That was important,   00:00:36.240 --> 00:00:41.220 but probably more important, I just  really hope everybody enjoyed that video.   00:00:41.820 --> 00:00:48.600 There's something about when we had that 10-minute  break that just, it was just great, right? Kind of   00:00:48.600 --> 00:00:53.580 takes you back to being a child, they're watching  those Saturday morning cartoons. All right,   00:00:55.200 --> 00:01:01.140 all right. We're going to now move into our  next presentation. Our presenter is going   00:01:01.140 --> 00:01:08.700 to be Janae Lockett-Renolds from Human  Systems Integration Branch Chief, S&T. 00:01:12.300 --> 00:01:13.860 Janae Lockett-Renolds, are you available? 00:01:18.480 --> 00:01:22.260 Oh, there you go. Yes, uh, thank you. Make   00:01:22.260 --> 00:01:25.260 sure you hear your audio. All  right. Well, how are you today? 00:01:25.260 --> 00:01:27.540 I'm doing well, how are you? 00:01:27.540 --> 00:01:33.960 I'm doing great. I am doing great. So, very nice  to have you, uh, come today and do a presentation,   00:01:34.560 --> 00:01:41.700 um, today at our DHS Accessibility Day 2023.  Um, so we are looking forward to having a   00:01:41.700 --> 00:01:48.120 lot of information presented to the participants  today, um. So I'm not gonna hold you up too long,   00:01:48.120 --> 00:01:53.460 so we're definitely going to allow you to be  able to speak now. And, uh, afterwards, if there   00:01:53.460 --> 00:01:57.360 are any questions, please make sure you put those  questions in the chat, and we'll try to make sure   00:01:57.360 --> 00:02:02.460 we relay those questions over. Um, again, we're  trying to make this presentation as interactive   00:02:02.460 --> 00:02:07.200 as possible, and we want to make sure that  everybody is able to get those questions across   00:02:07.200 --> 00:02:13.080 and get as much information as possible. So,  on that note, I'm going to hand it over to you. 00:02:13.680 --> 00:02:20.100 Uh, thanks so much, Vince. Uh, it's a  pleasure to be here. And Vince, do you   00:02:20.100 --> 00:02:26.220 have the slides? I think, uh, Aunika mentioned  that you guys could navigate the slides today. 00:02:27.360 --> 00:02:31.800 Let me check with my team, let me  check here. When my team will get up,   00:02:32.340 --> 00:02:38.160 you ask, and it is our opportunity  to present to you. So here you go. 00:02:38.160 --> 00:02:43.920 Okay, perfect. Oh, thanks so much,  Vince. Thank you. Uh, and on behalf   00:02:43.920 --> 00:02:49.920 of the Science & Technology Directorate,  uh, Office of Science and Engineering,   00:02:49.920 --> 00:02:57.360 Systems Engineering and Standards Division, um,  I'd like to thank you all for having us here today   00:02:57.360 --> 00:03:04.740 to talk with you about Human Systems Integration  and its implications for Universal Design. 00:03:06.780 --> 00:03:07.980 Um, uh, next slide, please. 00:03:14.520 --> 00:03:23.580 Okay, okay. So, Human Systems Integration, uh,  really offers a human-centered design approach   00:03:23.580 --> 00:03:30.900 that is applied within the context of systems  engineering. IT addresses Human Performance and   00:03:30.900 --> 00:03:37.680 safety in the design, development, fielding,  and operations of technology and systems. So,   00:03:37.680 --> 00:03:45.000 at its core, it's a discipline that focuses on  being able to strike a balance between what we   00:03:45.000 --> 00:03:51.240 know and understand about human limitations  and capabilities with the affordances   00:03:51.240 --> 00:03:59.280 and constraints of the system, in order to  achieve mission objectives, system objectives,   00:03:59.280 --> 00:04:06.240 and ultimately Human Performance objectives.  So, within the Department of Homeland Security,   00:04:06.240 --> 00:04:14.520 we recognize that HSI has broad applicability  across the Department's Mission areas,   00:04:14.520 --> 00:04:24.840 its systems, and end users. And so, this includes  DHS personnel as well as the General Public. 00:04:25.500 --> 00:04:35.340 In Human Systems Integration consists of seven  domain areas that you see here. Essentially,   00:04:35.340 --> 00:04:43.080 it's concerned with all aspects of systems and  products that pertain to Human Performance,   00:04:43.080 --> 00:04:52.020 accommodations, and safety. What I'd like to  point out is that we have the opportunity to   00:04:52.020 --> 00:04:59.460 collectively look across these factors, or  a subset of these factors depending on the   00:04:59.460 --> 00:05:05.640 type of system and acquisition strategy, and  look at the interdependencies in terms of how   00:05:05.640 --> 00:05:14.820 that influences design decisions. And so, as a  result, HSI as a discipline tends to be scalable.   00:05:14.820 --> 00:05:24.420 It's tailorable with respect to how best to meet  the program's needs. Okay, next slide, please. 00:05:26.820 --> 00:05:35.820 Okay, okay. So, fundamental to the  HSI approach is designing with the   00:05:35.820 --> 00:05:44.940 end user in mind. This helps to ensure that  systems are usable, accessible, inclusive,   00:05:44.940 --> 00:05:50.100 and that they support Universal  Design principles and practices. 00:05:50.820 --> 00:05:54.600 So, there are a number of  things that we need to consider   00:05:54.600 --> 00:06:01.980 when designing systems for humans to use.  We need to understand what the user needs   00:06:01.980 --> 00:06:08.280 to accomplish. You know, what are their goals?  What is the system going to help them to do?   00:06:09.120 --> 00:06:14.940 We need to understand what information they  need to know, and when they need to know it. 00:06:15.660 --> 00:06:22.260 We need to know the physical and cognitive  or mental capabilities and limitations of   00:06:22.260 --> 00:06:31.080 the end user, so that we can design systems to  accommodate them. We also need to know and have an   00:06:31.080 --> 00:06:40.980 understanding of the environmental and operational  context. For example, are they multitasking? Are   00:06:40.980 --> 00:06:48.000 they working in extreme environments? Are  they working under stressful situations? 00:06:48.840 --> 00:06:58.380 We need to understand, um, you know, essentially,  uh, are they working to accomplish their goals,   00:06:58.380 --> 00:07:06.000 uh, alone or are they working in a  team? And finally, are the new job,   00:07:06.000 --> 00:07:13.620 are the things that they're working, are they  pertaining to a new job, or uh, is it a new   00:07:13.620 --> 00:07:20.580 situation for them? Or have they done this work  before, or uh, do they have extensive experience? 00:07:20.580 --> 00:07:27.540 So all of these things are really important and  critical for us to know as we work to design, uh,   00:07:27.540 --> 00:07:35.340 technology and systems for our end users. So as  we begin to think more about how they're going to   00:07:35.340 --> 00:07:43.500 interact with the system, we can work to implement  empirically validated design principles early and   00:07:43.500 --> 00:07:50.340 often. So that we can develop usable systems  with intuitive interfaces that accommodate a   00:07:50.340 --> 00:07:57.660 broad range of characteristics, capabilities,  and limitations for the end user population. 00:07:58.920 --> 00:08:08.880 Also, you'll see here there are a couple of  definitions that, um, we've highlighted from   00:08:08.880 --> 00:08:19.260 some ISO standards for usability. Uh, across these  different definitions, you can see a focus on how   00:08:19.260 --> 00:08:27.300 well the user is able to accomplish their goals,  the effort required to do so, and the overall   00:08:27.300 --> 00:08:34.500 impact that this has on their perceptions and  their responses, essentially their satisfaction. 00:08:34.500 --> 00:08:43.800 So, you know, as you begin to think about  it, it becomes clear that usability is a   00:08:43.800 --> 00:08:49.680 multi-dimensional construct, you know, and it  can be addressed from an integrated perspective.   00:08:50.700 --> 00:08:52.440 Okay, next slide please. 00:08:53.820 --> 00:09:04.080 Okay, so there is a wide range of end users that  interact with our systems here at DHS. And so,   00:09:04.080 --> 00:09:14.040 this includes DHS personnel, both our internal DHS  users, as well as those personnel who are on the   00:09:14.040 --> 00:09:21.180 front line of security. It also includes end users  across the various first responder communities,   00:09:21.180 --> 00:09:27.000 as well as those that consist of the  general public, like travelers who are   00:09:27.000 --> 00:09:33.540 interacting with screening technology at the  airport checkpoint. Okay, next slide please. 00:09:35.220 --> 00:09:44.820 Okay, so in addition to the breadth of end  users that we have described, there is also   00:09:44.820 --> 00:09:52.200 a variety of technology and systems that they  need to accomplish their goals. For example,   00:09:53.400 --> 00:10:01.920 ships and aircraft, surveillance and detection  systems, immigration case management systems,   00:10:01.920 --> 00:10:09.000 wearable technologies, portable handheld  communication devices, protective equipment   00:10:09.000 --> 00:10:16.620 and gear, threat detection systems, public alert  and warning systems, and those are just examples.   00:10:16.620 --> 00:10:23.700 There are many, many more. So all of these systems  align with the seven core functions that you see   00:10:23.700 --> 00:10:31.260 here, which in turn align with the Department's  mission priorities. Okay, next slide please. 00:10:32.580 --> 00:10:41.100 So, uh, how are we implementing Human Systems  Integration in the department? Uh, here, uh,   00:10:41.100 --> 00:10:49.260 you'll see a snapshot of our Strategic Mission,  Vision, and goals where our mission is to enable,   00:10:49.260 --> 00:10:59.640 train, and safeguard end users of DHS systems by  implementing human-centered design approaches. Our   00:10:59.640 --> 00:11:07.800 vision is to influence the future of work for DHS  end users through human-centered design and this   00:11:07.800 --> 00:11:14.820 includes things like policy work, processes  and procedures, technological capabilities,   00:11:15.660 --> 00:11:19.740 how we train, um, just to name a few examples. 00:11:19.740 --> 00:11:28.860 So, as a result, we have the seven goals that you  see here that we are continuing to work towards.   00:11:29.940 --> 00:11:35.460 So, for the purpose of today's  brief, and in the interest of time,   00:11:35.460 --> 00:11:39.180 I'm going to focus on some of  the work that we've been doing   00:11:39.180 --> 00:11:46.500 in support of the first goal which is to  institutionalize HSI within the department. 00:11:46.500 --> 00:11:56.160 So, here, the focus has been on really getting  HSI considerations built into departmental policy   00:11:56.160 --> 00:12:06.420 and guidance, getting HSI methodology embedded  within, uh, the various engineering frameworks,   00:12:06.420 --> 00:12:12.960 uh, in acquisition frameworks as well  as providing support to programs. 00:12:13.500 --> 00:12:18.960 So, within the context of this goal,  we can begin to think about how this   00:12:18.960 --> 00:12:26.220 approach supports the basic principles of  Universal Design. Okay, next slide, please. 00:12:28.440 --> 00:12:35.460 Okay, so, here is a look at the acquisition  and systems engineering life cycle framework,   00:12:36.120 --> 00:12:42.600 uh, and we've had an opportunity to  get, uh, HSI activities, methods,   00:12:42.600 --> 00:12:49.740 and criteria across a broad set of systems  engineering activities as well as systems   00:12:49.740 --> 00:12:56.580 engineering technical reviews across the life  cycle that inform acquisition decision events. 00:12:56.580 --> 00:13:05.280 So, the bullets listed on this slide provide  some examples of the type of support that we   00:13:05.280 --> 00:13:14.040 give to programs. And so, from the earliest  point in the life cycle, you can see that we   00:13:14.040 --> 00:13:21.420 are really thinking about how to improve  upon deficiencies and legacy and existing   00:13:21.420 --> 00:13:27.600 systems that may have human performance,  and usability, or safety implications. 00:13:27.600 --> 00:13:36.060 And, just to give you some examples of the  things that we've seen in the past, we've seen   00:13:36.060 --> 00:13:45.960 deficiencies related to high levels of workload,  sometimes it's due to manual processes, or   00:13:45.960 --> 00:13:54.180 sometimes it's due to poorly designed automation,  uh. We've also seen safety and health hazards due   00:13:54.180 --> 00:14:01.800 to excessive noise levels, uh, lack of shock  mitigating seats, and poorly designed consoles. 00:14:01.800 --> 00:14:09.300 And, we've seen a high rate of human error and  workload due to poorly integrated information   00:14:09.300 --> 00:14:16.860 across the spirit systems. So, just to give you  an idea of some of those things that we're seeing,   00:14:16.860 --> 00:14:24.480 and when we have opportunities to get involved  early on in the life cycle, or really at any   00:14:24.480 --> 00:14:30.960 point in the life cycle, one important thing  that we keep in mind is the need to gain an   00:14:30.960 --> 00:14:38.460 understanding of the end user, also known as  the target audience. Okay, next slide, please. 00:14:41.040 --> 00:14:53.460 So, early on, you know, essentially our goal is  to be able to characterize the target audience.   00:14:53.460 --> 00:15:03.300 And so, in the box that you'll see in the upper  left side of the screen, that provides some key   00:15:03.300 --> 00:15:11.280 questions for considerations in this activity.  And please note that this can include things like   00:15:11.280 --> 00:15:19.260 physical and mental characteristics,  limitations, and capabilities, um. 00:15:19.260 --> 00:15:26.940 So, once we gain this information, in  addition to understanding the deficiencies   00:15:26.940 --> 00:15:34.620 and what capabilities are needed to resolve  those deficiencies, HSI offers an integrated   00:15:34.620 --> 00:15:43.140 approach that forms the basis for influencing  requirements, as well as the underlying   00:15:43.140 --> 00:15:50.100 behavior of the system or system architecture,  Design Concepts, as well as considerations for   00:15:50.100 --> 00:15:58.980 testing. And this includes usability testing  for accessibility. Okay, next slide, please. 00:15:59.880 --> 00:16:09.180 Okay, so ultimately, the goal is to obtain  usability through Universal Design. Okay,   00:16:09.180 --> 00:16:16.920 so the bulleted list that you see here provides  some examples of areas where HSI can have an   00:16:16.920 --> 00:16:27.300 impact. Like, for example, the design of jobs  and job environments, user interface usability,   00:16:28.020 --> 00:16:34.560 also issues pertaining to training  and skill levels, language abilities,   00:16:34.560 --> 00:16:41.760 workload, and user performance  efficiency and effectiveness, um. 00:16:41.760 --> 00:16:48.180 Human systems integration is an integrated  approach that supports implementation of   00:16:48.180 --> 00:16:55.320 Universal Design principles. It is  tailorable, it's scalable, and it   00:16:55.320 --> 00:17:01.020 can be applied across a number of different  contexts to support developmental products,   00:17:01.020 --> 00:17:08.460 technology systems, and environments that  are accessible, usable, and inclusive.   00:17:09.180 --> 00:17:15.120 Thank you. I'm happy to take any  questions that we have in the chat. 00:17:21.960 --> 00:17:27.660 All right, guys, this is your opportunity.  We always want as many questions as possible,   00:17:27.660 --> 00:17:33.840 so if you have any questions, I think this is  a great time. While we're waiting for people   00:17:33.840 --> 00:17:39.240 not to be shy, I do have a question. Well, I  don't know if there's a question as much, but   00:17:39.240 --> 00:17:46.320 can you give a very low level for people who do  not... Well, one person asks, can you get a copy   00:17:46.320 --> 00:17:52.560 of the slides? Yes, from the unknown user, we are  going to provide a copy of the slides. Okay, um. 00:17:52.560 --> 00:17:57.480 Can you just give a basic kind of overview  of what Universal Design is, for those who   00:17:57.480 --> 00:18:05.880 may not know what it is? Yes, um. So, you know,  we did a little bit of research, and we've been   00:18:05.880 --> 00:18:18.900 working with a colleague of ours at DHS that is,  um, focused on, uh, Universal Design. And there   00:18:19.800 --> 00:18:28.260 tends to be... let's see. I'm gonna see if I can  pull this up while I'm talking, uh, and I'm not   00:18:28.260 --> 00:18:36.660 sure if I can, but there are seven principles  associated with Universal Design. Excellent,   00:18:36.660 --> 00:18:43.740 and I'm gonna see if I can get a hold of  those while we're talking because it's,   00:18:43.740 --> 00:18:54.000 it's a little new to us, uh. But we are also  looking at how we can support this area of work. 00:18:54.540 --> 00:19:00.000 Not a problem. And in my team, if you guys can  also look for Universal Design seven principles   00:19:00.000 --> 00:19:05.220 to add into the chat, I think it'll be great  for the team. While you're looking for that,   00:19:05.220 --> 00:19:08.760 I also want... there's one question that  came in. They said, thank you so much for   00:19:08.760 --> 00:19:15.120 sharing. What kind of challenges have you had in  integrating HCD considerations into requirements   00:19:15.120 --> 00:19:22.740 and influencing policy implementation?  No, I think that's an excellent question,   00:19:22.740 --> 00:19:29.220 and I'll pause my search for my  link to you design. No problem. 00:19:29.220 --> 00:19:38.640 So, you know, typically, the way, uh, we are  involved with, uh, requirements... so in our   00:19:38.640 --> 00:19:46.500 office, uh, in our division rather, systems  engineering standards, we have opportunities   00:19:46.500 --> 00:19:55.620 to support, uh, The Joint requirements Council.  So the requirements come in from our operational   00:19:55.620 --> 00:20:04.500 components, and we have opportunities to  review requirements documents like, uh,   00:20:04.500 --> 00:20:11.940 the operational requirements documents and any  subsequent documents related to requirements,   00:20:11.940 --> 00:20:19.020 like the concept of operations,  Mission needs statements. Typically,   00:20:19.020 --> 00:20:28.080 we will review those documents with a focus on  human centered, or on human systems integration. 00:20:28.080 --> 00:20:40.680 We, we typically, uh, we, we see, uh,  programs, uh, working to incorporate those   00:20:40.680 --> 00:20:49.080 types of considerations. You know, in terms  of, uh, the, the end user being able to, uh,   00:20:49.620 --> 00:20:57.180 successfully accomplish Mission tasks using  the system. And so, we have that lens on,   00:20:58.200 --> 00:21:00.240 um, when we're reviewing those documents. 00:21:00.240 --> 00:21:10.740 I think the challenge that we would, uh, say that  we typically see is that we don't see those types   00:21:10.740 --> 00:21:20.160 of requirements being identified consistently, um.  So, you know, we'll, we typically will make a note   00:21:20.160 --> 00:21:28.320 that, you know, those types of requirements, you  know, have not been included in the operational   00:21:28.320 --> 00:21:36.120 requirements document. That has implications  further down the life cycle, for example,   00:21:36.120 --> 00:21:45.600 during operational testing and evaluation. You  know, where they're determining if the, the system   00:21:45.600 --> 00:21:53.760 is meeting those requirements, and if the system  is proven to be effective and suitable for use. 00:21:53.760 --> 00:22:00.540 You know, we want to make sure that human  systems integration requirements are included,   00:22:00.540 --> 00:22:05.460 you know, as a part of those testing  and evaluation activities. So it's   00:22:05.460 --> 00:22:11.640 really important early on that those  requirements are present. So, you know,   00:22:11.640 --> 00:22:17.940 we just try to do our due diligence there  to support programs in that capacity. 00:22:18.720 --> 00:22:22.320 Excellent. Well, it's interesting. There was  another question that came in that kind of   00:22:22.320 --> 00:22:28.140 talked about what you were just mentioning there  a moment ago about the implementation early on in   00:22:28.140 --> 00:22:32.640 the life cycle. They asked a question of, "In  our experience, many development teams are not   00:22:32.640 --> 00:22:39.960 interested in including accessibility at the  planning phase. What is DHS doing to implement   00:22:39.960 --> 00:22:45.240 this within HSI?" And I'm not sure if you're  going to be able to answer that one or not. I   00:22:45.240 --> 00:22:50.700 mean, from an accessibility standpoint, yeah,  no, I, I think that's an excellent question. 00:22:50.700 --> 00:23:00.960 And I, I had an opportunity to, um, hear,  uh, Mr. Floyd speak about a week ago during   00:23:00.960 --> 00:23:10.560 the Customer Experience Community Practice.  And during his presentation, he had shared,   00:23:11.220 --> 00:23:20.820 um, some of the goals, you know, for getting  accessibility included. And, you know, we thought   00:23:20.820 --> 00:23:32.460 that there was a lot of opportunity there to,  um, provide some support. Uh, we, um, you know,   00:23:32.460 --> 00:23:43.020 having, uh, this human-centered approach, um,  exists within the context of systems engineering   00:23:43.020 --> 00:23:52.500 and acquisition. We've had, uh, opportunities  to have visibility to departmental policy and   00:23:52.500 --> 00:24:04.140 guidance, uh, with respect to these types of  activities, you know, that are human-centered,   00:24:04.140 --> 00:24:12.180 uh, related. You know, and I think that there  will be opportunities, you know, going forward   00:24:12.180 --> 00:24:21.720 to think about how we can include this content  in, um, those venues, if, if that makes sense. 00:24:21.720 --> 00:24:30.600 Currently, uh, currently, I, um, I don't  see that content in those documents,   00:24:32.040 --> 00:24:38.340 um, you know. But that's something that I think  we can discuss, you know, to see how we can,   00:24:38.340 --> 00:24:48.600 you know, get that included. Uh, we've got a  colleague with S&T that is our POC for, uh,   00:24:48.600 --> 00:24:58.080 D-- DEIA, and, you know, we've been talking with  her a lot about how to ensure, uh, that these,   00:24:58.080 --> 00:25:04.080 in these considerations are included,  um, within the life cycle. And so, we've   00:25:04.080 --> 00:25:13.980 been thinking through, uh, how we can best, um,  incorporate these considerations, um, you know. 00:25:13.980 --> 00:25:22.140 I think Human Systems Integration offers,  um, you know, a pretty good approach, uh,   00:25:22.680 --> 00:25:27.720 to begin to think through some  of those important issues. So,   00:25:28.860 --> 00:25:36.120 um, you know, definitely looking forward to future  discussions, uh, about that. And I think that,   00:25:36.780 --> 00:25:42.180 um, you know, this discipline provides  a good mechanism for doing so. 00:25:42.840 --> 00:25:47.820 Excellent, excellent. Thank you for that  response. That was great. Are there any   00:25:47.820 --> 00:25:52.440 other questions? Uh, looks like our  chat slowed down there a little bit.   00:25:53.340 --> 00:25:56.880 Um, thank you again so much for this,  uh, presentation. I think it was great.   00:25:56.880 --> 00:26:01.620 We did put in the chat, for those who  did not know about Universal Design,   00:26:01.620 --> 00:26:06.960 so there's a link in there for you to get  more education on what Universal Design is. 00:26:06.960 --> 00:26:13.980 Yeah, and I just, uh, Vince just found the  link, uh. Oh, okay. And I'll also put that   00:26:13.980 --> 00:26:21.300 link in the chat. Um, right, you know, it, it  says, uh, you know, essentially there are seven   00:26:21.300 --> 00:26:30.480 design principles for Universal Design, um, you  know, and it's equitable use, flexibility in use,   00:26:30.480 --> 00:26:40.800 simple and intuitive use, perceptible information,  tolerance for error, low physical effort, and size   00:26:40.800 --> 00:26:49.680 and space for approach and use. We did a little  bit of digging ahead of this presentation. Many   00:26:49.680 --> 00:26:58.920 of these principles map to the, the seven Human  Systems Integration domain areas that, you know,   00:26:58.920 --> 00:27:06.240 we mentioned earlier on. So, I think it will be  interesting as we move forward to look at some of   00:27:06.240 --> 00:27:15.420 those points of synergy and connection to support  our colleagues in accessibility and usability. 00:27:16.620 --> 00:27:21.540 Interesting. Yeah, I would love to be part  of that conversation because that's going to   00:27:21.540 --> 00:27:27.480 be a seven and seven conversation, right? To  talk about what... Were you about to say...?   00:27:28.020 --> 00:27:33.240 No, I, I said, sure, sure. Yeah, yeah. I think  it would be great. I'm sure a lot of people that   00:27:33.240 --> 00:27:38.760 are on, uh, the call today, on the presentation,  would love to be able to see, you know, how they   00:27:38.760 --> 00:27:44.220 kind of merge together between the human systems  and Universal Design, uh, between those seven,   00:27:44.220 --> 00:27:49.680 and then see how that can all work together  with accessibility, ultimately for usability. 00:27:49.680 --> 00:27:54.720 So, this has been great. I mean, these are the  type... I know everybody doesn't like to get   00:27:54.720 --> 00:28:00.120 too in-depth in the technical aspects, but  I think having these cyber conversations is   00:28:00.120 --> 00:28:06.420 very important for people to be able to pull  back those proverbial layers of the onion, to   00:28:06.420 --> 00:28:14.400 understand the importance of what we do in order  to make systems to be humanistic and accessible,   00:28:14.400 --> 00:28:19.380 right, for all people. So, thank you again, so  much for this presentation. This is really good. 00:28:19.380 --> 00:28:25.080 If there are no other questions, we're  actually going to move on. And again,   00:28:25.080 --> 00:28:31.620 thank you so, so much, Ms. Reynolds. Thank  you, Vince. All right. Take care. Bye-bye. 00:28:32.760 --> 00:28:38.640 All right, guys. I hope you have enjoyed the  last presentation. All the presentations up   00:28:38.640 --> 00:28:42.960 to this point. So, we're going to kind of  change things up a little bit. All right.   00:28:42.960 --> 00:28:48.060 We've been kind of heavy on the technical side  and providing a lot of very important information   00:28:48.060 --> 00:28:55.080 about usability and accessibility, and CeX,  and HSI, and all that good stuff. However,   00:28:55.800 --> 00:29:02.280 we are now going to have a little game. And  I would like for everybody to participate   00:29:02.280 --> 00:29:05.940 in this game. So, we're going to  have now, Miss Dominique Wheeler,   00:29:05.940 --> 00:29:13.320 who is also part of our Office of Accessible --  or Accessibility & Usability. Miss Dominique. 00:29:16.320 --> 00:29:18.060 I have here. Pop one up here. 00:29:23.520 --> 00:29:27.480 There she is! All right, almost. We see your,   00:29:27.480 --> 00:29:31.140 your background. We don't see you yet.  Let me make sure I can hear you also. 00:29:37.320 --> 00:29:39.480 Don't worry, we'll be up in a moment. Whoops,   00:29:40.560 --> 00:29:43.687 we're all waiting for, uh,  Dominique to pop up. Any questions?