Marissa: Hello everyone. Thank you for joining our webinar today. I'm just going to give people a few minutes to join. So I will put myself on mute and just hang tight. We'll be started very soon. (silence) Hi, everyone. Welcome to our webinar. Undertaking JAWS Screen Reader Compatibility Testing in Real Life. Before we get to the presentation, I just want to run through a few housekeeping issues. First, this webinar will be recorded. You will be sent a link to the recording in a few days. So if you have to leave early or you would like to share it with colleagues, friends, acquaintances, you will have that opportunity. If you would like you can enable the closed captioning. There's a option for you to do that. And if you have questions, please put them in the Q&A, we will address all the questions at the end. And if you find that you have a question that was not answered during the presentation, or you have something that comes to your mind afterwards, please e-mail ida@tpgi.com and I will send in your question to the correct party. And I will put that in a chat as well. So you have my e-mail. That is our introduction, so without further ado, I would like to hand it over to Al Puzzuoli and Mike DeSorda. Mike DeSorda: Thank you, Marisa. This is Mike DeSorda speaking, and hello everyone. First, I want to thank everyone for attending today's JAWS Inspect webinar. I think you'll find this very valuable, especially if you're sort of new to the concepts. I want to start out today by introducing myself and my webinar partner Al here. We both work at TPGi's Customer Success Team, and I'm going to start by letting Al introduce himself, and then I'll do the same. And then we'll kind of get started here. So Al if you wouldn't mind introducing himself. Al Puzzuoli: Okay. Hi, everyone. My name is Al Puzzuoli. I have been with TPGi for about five years now. I worked in the IT field prior to working at TPGi at Michigan State University. I am also a JAWS user. My role at TPGi is a lot of ARC administration and assisting customers and fulfillment. I also provide support for the JAWS Inspect product, and I do UX testing from the perspective of a JAWS user as well. Mike DeSorda: Thank you Al. My name is Mike DeSorda. As I mentioned earlier, I'm on the Customer Success Team. I'm the manager of customer success here at TPGi. I've been here two years. My role is basically supporting clients in every which way that we can with the various platforms we can. So I'm very happy to be here today to be part of this webinar and explain JAWS and JAWS' spec to you guys. So first I want to say, what is our objective today? So our hope is that today we're going to be able to model for you what you might think of as a real-world relationship between a JAWS user like Al who is a real JAWS user, and that's going to be his role, and an accessibility tester, and that's going to be my role today. So I'm going to be using JAWS Inspect to try to uncover what the difficulties that Al will be expressing to you here in a little bit as a screen reader. For those that may not be familiar with JAWS Inspect, JAWS Inspect provides text output in report format of all the JAWS screen reader audio that does enable accessibility testers to efficiently and effectively test for JAWS Speech output. So you don't have to have JAWS on your system yourself and try to transcribe it yourself. So in short, if you have anything at all to do with making the lives of your JAWS users easier and less frustrating with poorly accessible webpages, then JAWS Inspect really is a potential value to you. And this webinar should be pretty enlightening for you. So as Marissa already mentioned, we would like to ask that you reserve questions at the end today, because Al and I will be going and through kind of a back and forth flow that is better seen end to end, kind of in one chunk instead of kind of broken up. So with that, thank you very much again, and I think I'm going to turn over to Al and Al will start sharing his screen and explain the experience he's having with a test website we use for these purposes, and I'll stop sharing my screen Al, at this point. Al Puzzuoli: Okay. Thanks, Mike. I'm going to share, let me know if ... Automated: I've started screen ... Mater Money Fin- con ... leaving menu. Al Puzzuoli: Okay. Are we there? Mike DeSorda: We are Al. Al Puzzuoli: Okay, perfect. All right. So we are looking at our sample [crosstalk 00:05:51] website here called Mater Money Financial. And this is just a little test site that we use to run through some typical issues that JAWS Inspect users might see, or JAWS users might experience. So, one thing to understand that as a JAWS user, I have several ways of navigating content. One thing I might do as someone who is new to the page is just want to understand the entire page. And I can do that by telling JAWS to read the whole page. So I'm going to do that now. And this, by the way is going to be reflected in one of the JAWS Inspect reports called the say all report, but I'm going to do a say all command in JAWS right now that will just basically run JAWS through the entirety of this webpage. Automated: Mater Money Financial ... heading, level two link. Mater Money Financial Services. Heading level one, Mater Money Financial Services. Heading level three serving clients since 1952. Link main office calling 2012-55-1212. Heading level two about us. Heading level three, servicing clients since 1952. Mater Money Financial Services is exactly the type of team you want handling your hard-earned money. We have a combined 250 years experience in the financial services industry, and it flows through our veins. We eat, breathe, and sleep money, rest assured your funds will be in exceptionally competent hands. Heading level two, practice areas. Heading level three, why choose us? We are well versed in all manner of wealth management, and financial growth. Our senior level positions are all held by family members of the founders and their commitment to client retention is unparalleled. When you join Mater Money, you join a family, not just a service provider. Heading level two, We love our clients. Nothing says love like a box of chocolates on your birthday or a phone call just to check in. This is the kind of legendary service we provide. Heading level two, finances life. If you've spent your life accumulating wealth, then you've come to the right place to increase it, live out your retire dreams, or buy that yacht you've always wanted. We'll help bring your dreams to life. Heading level two, explore your options. If you've worked hard all your life and want to give back to the society that helped you to succeed, we can help you manage your charitable foundation or even secure your funds in a trust to ensure your family will be well cared for in perpetuity. Heading level two, we are your spirit guides. You make the choices in your life, but we help advise with expert guidance. We could all use a little advice to get to where we want to be in life. Heading level two, drop USA line, heading level three. Feel free to contact us with questions or comments. Edit, edit, edit, link sent greater, heading level three, Mater Money Financial Services is hands dash down the best financial services firm I've ever had the pleasure of working with. They increased my funds five dash fold, heading level three in just over six months. Casey Johnson. Heading level two, meet the team. Heading level three, partners and associates. Our team is located all over the world and has a variety of experiences in the financial industry. You'll partner with someone who fits your exact needs for your financial journey with us. Heading level two, Alex Riley. Heading level three, founding partner, send mail, link contact. Heading level two, Rachel Bloom, heading level three, partner. Send mail link contact. Heading level two, Lara Edwards, heading level three, senior manager. Send mail link contact. Heading level two, we're here to serve you. Link phone number, calling 2012-555-1212. Heading level, 36 Doyers Street, New York, NY 10013. Heading level two, Mater Money Financial Services. Unlabeled graphic, graphic social media slash six Facebook. Unlabeled graphic, graphic social media slash six Twitter. Unlabeled graphic graphic social media slash six Google+. Let us build and manage your beautiful SEO dash friendly website. Link get started. Started. Al Puzzuoli: Okay. So we've got a lot of content there. Typically, a new user might do a sale, but a more advanced user, or someone more familiar with the page would not do a sale because as you saw, this is a small webpage and that was not an efficient way to deal with the page. So typically what I would do in the situation like this is try to break the page down and navigate it via its elements. And one [crosstalk 00:10:23] very popular element that we use for navigational purposes is the heading level. So I'm going to use JAWS to kind of scroll through the heading levels of this page. Now I can hit the letter H to cycle through the heading levels. If I hit H ... Automated: Mater Money Financial Services, heading level two link. Al Puzzuoli: There's heading level two link of Mater Money Financial. Automated: Mater Money Financial Services, heading level one. Al Puzzuoli: Now we've got heading level two and heading level one, which seemed to have the same titles. Automated: Serving clients since 1952 heading level three. About us, heading level two, serving clients since 1952, heading level three. Al Puzzuoli: I'm scrolling down these headings, and there are several repeated headings. The same heading is at a couple different levels. Automated: Practice areas, heading level two. Why choose us heading level three? We love our con- Al Puzzuoli: So essentially the heading structure of this document has some logic issues. It doesn't quite make sense. So I'm going to go back to the top of the document. Another way to navigate the document is by just pressing the tab key instead of reading all the text. Now, the advantage of pressing tab key is that that will just jump from element to element on the page. For example links, forum fields, buttons. The disadvantage to using that method as opposed to arrowing around and reading the text is you sometimes don't get the full context of the page, and you need to rely on the element labels to give you the proper context. So let's tab through this page and see what we get. Automated: Mater Money Financial Services, heading level two link. Main office call 212-555-1212 link. Edit. Al Puzzuoli: Okay, so edit. Automated: Edit. Al Puzzuoli: Edit. Automated: Edit. Al Puzzuoli: Edit. We've got three edits, and I have no idea what those are as I'm tabbing through them. Automated: Contacts, send mail link. Al Puzzuoli: And we have a contact send mail link. And again, I know that I'm contacting someone, but I have no idea who I'm contacting. I'm going to tab again. Automated: Contact, send mail link. Al Puzzuoli: Another contact, send mail link. Automated: Contact, send mail link. Al Puzzuoli: And another contact, send mail link. And tab again. Automated: Phone number calling 212-555-1212 link. Al Puzzuoli: Now, that was an example of a good link. It said, phone number, and then it had the phone number. So that link gave me the context I needed. Automated: Social media slash six Facebook link graphic. Al Puzzuoli: Now we're getting to the graphics of the different online services here, and these are not labeled properly, but we're picking up the descriptions of the graphics of social media, Facebook ... Automated: Social media slash six Twitter link graphic. Social media slash six Google+ link graphic. Al Puzzuoli: Google+. Automated: Get started link. Al Puzzuoli: And now we have another link, and this is interesting because this is not part of Mater Money Financial, this is just part of this Yahoo site. And again, it's a bad link. It just says get started. And there's no context in the link. It's the link to have them help us with our SEO website or whatever at that. Automated: Let us build and manage your beautiful SEO dash friendly. Al Puzzuoli: Let us build and manage your beautiful SEO-friendly website. But there's not context, I had to up arrow and read the text of that sentence to get that context. So that link could use some work. Essentially those are the issues that I see here as a JAWS user, and now I will turn it back over to Mike, who can illustrate those from a JAWS Inspect point of view. Automated: Meeting control- Mike DeSorda: All right. Thank you Al, appreciate that. I'm going to be firing up my JAWS Inspect right now, and then I'll share my screen. All right. Okay. Ready to go. All right, you see the same website that Al just took you through. So my job here now at this point is to do my best, to use JAWS Inspect, to mimic and affect the experience that Al as a screen reader actually had, and try to detect some of those elements that he mentioned that were problematic for him, but in report format so that I can take some action potentially to remediate some of these areas that are less than desirable so that the next time that Al or whomever would be using the website as a screen reader would have a more pleasant experience. I'm not going to show everything about JAWS Inspect today. That's not the purpose of today's webinar. I'm going to kind of go over a couple of the primary reports that one would use if one had a license for JAWS Inspect. But this will give you the idea. It'll clearly give the idea you know, the power and the value of JAWS Inspect as I take you through some of these reports. So, if you had a license with JAWS Inspect, to invoke any and all of the types of reports that you can run, there's a variety of them, then you always hold down your control key on your keyboard and you right click your mouse. And as you can see, we have a little floating menu pop-up show up here, and these are showing you all the various types of reports and features of functions that we have with JAWS Inspect. As I mentioned, we're going to show you maybe three of these today. Just bear in mind some of these other choices you have here year are really just offshoots of pretty much the same thing where you can kind of focus in on more specific areas on a webpage. But I'm going to show you the bigger reports here today. Keep in mind that just as Al was going through a single webpage when he was using his JAWS system, so he could understand what was on that webpage, JAWS Inspect does the same thing. So it doesn't crawl through an entire website, it's page by page. So you need to keep that in mind. The other thing to keep in mind is that JAWS Inspect is not a platform that ties back to any particular accessibility standard. Say for example, WCAG standard. We have other products that do that. And many people probably do, but this is a product that its sole purpose is to provide you as the tester a report about what JAWS provides in an audio form so that you can take action. So there's not going to be any kind of red blinking lights at you that this is an issue or a problem. You have to look through the reports yourself and put your site-impaired hat on, and try to determine whether something makes sense or doesn't make sense, something's logical or illogical. And I'm going to show you what I mean by that in just a moment, but I wanted to kind of get that groundwork out here first. So I'm going to go through the full page report. This is a report that is going to provide the JAWS output, but it's going to be categorized by HTML element. So that's a way to categorize in a sort of a technical way what JAWS expressed. I'm going to go through the say all report. Al already mentioned that especially with new webpages that a screen reader might be accessing for the first time, they may want to run the say all report to get a feel for the webpage in general and I'll be doing that. And then finally, I want to make sure everybody's speech viewer report, and as Al mentioned earlier just a moment ago as an experienced screen reader, and especially once he has an understanding of a webpage, he would navigate through using his arrow keys and his tab keys to efficiently get to where he wants to go and do what he wants to do. So this is going to be a way to kind of mimic that user journey. So I'm going to show you these three. So let's start with the full page report. And when you click this report, you'll see that it's going to crawl through the website or webpage, and that's going to be a good sign. And the report itself will show up on just another tab in the active webpage or active up browser here. So here we go. And here we are. So this is the full page report. The headers are always going to be very similar or the same for most of these reports. We're just going to give you the website URL you were on, the date and time you ran it, what browser you happened to be in, and the various versions of JAWS and JAWS Inspect that are part of this application. Down here in the body that's really where all the action is. You can see that it found four HTML elements here, lengths, controls, headings and graphics. I'm not going to go through all these today, I'm just goon go through some lengths because the main takeaway from here is not the specific issues really, but it's really how you think through the issues, how you analyze the information in these report. So it'd be pretty much the same mindset you would have regardless of the elements you're talking about. So I'm going to open up links first. And first thing I want to do is walk through the attributes here at the header of the report so we can understand what all of these mean. So first select, select would be pretty much like any software has these days. If you want to pick and choose any particular rows that you might want to take outside of JAWS Inspect at some point to track issues or remediations in a spreadsheet, or if you want to upload it in some kind of a problem management system, you can pick and choose the areas you think are problems. And down here, you can see, you can export of those into CSV files. And every single report we have in JAWS Inspect, you can export into CSV files. The JAWS Speech output is kind of obvious. It means exactly what it says. Everything in black here is the actual content on the page, and everything in dark green, bold green here is the extra context that JAWS provides the screen readers to provide them a little extra help about what they're actually encountering here. The [inaudible 00:21:38] is just nothing more than ... since these are basically links, it's just nothing more than the anchor tag with the [inaudible 00:21:45] attribute associated with that if you want to see that. The screenshot is, as you might imagine, it's just going to show you where back on the webpage that particular part of the real state was. And you can certainly use this as a way to go back to your webpage if you wanted to kind of find the area that any particular row is showing. Code can be quite important. If you're a tester and you detect that something might need remediation so JAWS expresses it better, and you need to feed that over to say a developer or an engineer that's going to do the remediation itself, they may say, Hey, that's great, but can you give me a hint about where in my massive amount of code this might be? And if you click this little icon, then you can see that you can highlight, and you can copy this information. You can send it over to your developer, your engineer, and they can use this as sort of a search string to quickly find the area that they might need to start fixing up a little bit. Locate is an area we're working on. This would be useful in the future where you would see an icon here that if you click it, it would highlight back on the webpage itself the particular component that we're looking at here. An ID is a way to give you a unique ID again, in case you want to export it and put it into some kind of a problem management system where you can uniquely track the issue. If we cannot find an ID in the code itself, we find you our own unique ID. They always start with FFFF, if we can find the ID and the code itself, we'll give you that ID. So that's what the header's all about. Now, again, the takeaway here is how do you look through this, and what do you do? Again, nothing is showing you any particular problem. You have to tease that out yourself as you go through each row. So if I start looking down here, I'm going to say, here's an example, and Al confirmed this, right, when he saw the main office phone number, and that phone number was given, and it was noted that it was a link, he felt that okay, that was plenty of context, I understand what that is. It's a phone number. I click a link to it and get some more information. So that was not a problem for Al. But if you might remember that there was a send button there. And he said, okay, well, send what? I don't know what that's about. So if we go back to the website I can show you what he saw, and what he mentioned is we have a little send button here, which is actually a link, and oh, there's a form associated with it. So if you're a visual person, you can see there's a form and once I fill out the form and then I can send that information somewhere, right? But Al did not know that. So I might want to tag that as an issue. The other thing Al mention was all these mail links, there's send mail links, all these contacts. And when he was tapping through that, all he saw, all he heard was contact, contact, contact, and you guys might remember when he did that, it was these three contacts here. These three people that you can contact if you wanted to. You can pick which one you wanted it to do that. So that was confusing to Al and rightly so. And so we might want to track those as well. Right? And finally, Al noted that there was a get started link at the bottom of that page. And we can see that down here and we can say, okay, somebody's going to help us build and manage an SEO-friendly website. We happen to know it's a Yahoo thing. But he just heard this get started button, or this get started link really, and didn't really know what he's going to get started with. And so again, we might want to tag that as an issue. So once I've tagged those as an issue again, if I want to track that outside of JAWS Inspect, I would just click export the selected, and it would create a CSV file, and then I can work with it out there. So that way you think through this, and you determine whether there could be a problem or not is kind of the mindset you take to this report, really all these reports as I go through that. So that's the full page report and kind of how you navigate through it and understand it. Next. I want to run the say all report, and Al demonstrated that when he initially was going through that page. So I'm going to mimic that now in a report format what he ran in the JAWS application itself. So here I go, and the same thing's going to happen, it's going to crawl through. Now, it's sequentially going from top to bottom of this page through all the content and all the elements, and it's going to show me a report again, in a tab here, but this time it's just going to show me in sequential order everything top to bottom how Al heard it when he ran this same function via JAWS. So we're in the text flow view at the moment. And so everything highlighted in yellow is the extra verbiage that JAWS provides screen readers like Al, and everything in black is the content on the page. You might remember Al hearing Money Mater Financial Services two or three times, and with heading levels kind of cookie, and you might remember if you were paying attention that Al, he hesitated there for a moment, and kind of wondered, and he said, "Huh, what's going on here?" So it's not a big deal, and maybe it's not the best way it should have been designed, but you can see here what's going on, right? Heading level two, Mater Money Financial Services, heading level one. Seems out of order, and it seems it's repeated, and so this seems a little illogical to somebody that's a screen reader. And this might be something you want to reconsider how that's designed, right? But otherwise your point is that you want to go through here, make sure everything seems to be in logical order. Make sure there's context around everything so it's not confusing to screen readers, and just make sure there's nothing illogical about what you're seeing here. So this is a great way to see from top to bottom what it's going to express. Now, if you want additional attributes associated with all this information, just like you saw in the previous report, all you have to do is click table. You saw this same sort of thing in the previous report, and this way you would be able to select, pick and choose areas that might be problematic in your opinion, and then export it out to a CSV file as well. Same as we could before. Over here, you can see this time we did find in the code some of the IDs, and so we provided that here in this case. So still have the code snippets you can find and you can send to your programmers if you need to do that. So that's the value of this particular report mimicking the same function that is in the JAWS screen area itself. Finally, what I want to show you is the speech viewer report. Al mentioned that once a screen reader like Al is familiar with a webpage, they're likely going to be tapping through and arrowing through the website to get to where they want quickly, to get the information they want quickly, and to do whatever features or functions they want to do quickly on the webpage. I call that the user journey or a JAWS user journey. I'm going to try to mimic that using the speech viewer, and that's what it's all about. So this is great, especially if you understand exactly how a JAWS user might navigate through its web webpage exactly, or close to exactly to capture and make sure that JAWS is correctly expressing what's on the page as you navigate through using your keyboard. So this time when I click on it, it's going to show up in a floating report instead of a tab. So here it is. And all you have to do is put the focus back on the webpage. You see it picks things up right away. And now I'm just going to tab and arrow through a bit. As I tab through, I'm going to go through element to element as Al mentioned. Remember Al heard, edit, edit, edit three times? Well, there you go. Right? So you might tag this as an issue or a problem because that certainly is out of context and kind of confusing. If I arrow down through I'll just kind of go row by row through the context of the page. And so there's some combination likely Al or any screen reader is going to do. And the takeaway from this is looking under the text column here, you can look at the journey that you're mimicking for a JAWS screen reader and determine whether JAWS seems to be picking up the information correctly. Again, if you want to export any of this information out to a CSV file, for example all these edits, I might click at it and hold my control key down and highlight those three rows, and then I'm going to save selected, and that would just shoot that out to CSV file as well. So those are the ones I wanted to share. I will just mention, just in case there are people out there with already live designs on their websites ... let me get rid of this, I'm not going to show it, I just will mention that we do have an ARIA Live report that you can determine whether if you're using ARIA Live to push changing content to a website, this can pick that up and determine whether JAWS is actually finding it or has seen it and expressing it or not. And the last thing I'll mention about ARIA Live is that ... excuse me, let me go back to speech view report, is that ... I'm not going to show it to you here today, but if you have desktop documents say like a PDF or a work file, there is a different way to invoke the speech viewer report that can crawl through a PDF or word file or any sort of really desktop application whatsoever frankly, I haven't seen it not working in anything. If you have that as a use case, say for example, a PDF and Adobe Acrobat not expressed on a browser tab, then there is a way to use a speech view report also to mimic how a JAWS user would hear a PDF as an example, right? So there is that capability as well. Okay. I think I have gone through what I wanted to convey to everybody. At this point turn it back over to Marissa, and we'll go from there. Hello Marissa? Okay, so I don't know where Marissa is. Why don't we just start and see if there are any questions. It looks like there's a bunch of chats here. So I assume there's going to be some questions in there, and I'm just going to start at the top and see what we can find, and then we'll let everybody ... if they have some verbal questions, they can now provide it. Okay, the images for contacts was not recognizable by JAWS. So user may not be aware there are images two for the context. Just sharing my feeling on the ... yeah, that's very good [Maya 00:33:45], that's exactly right. Also, Maya, reporting exporting CS file, the report will lose the textiles. Is there a way to export into an Excel sheet? Just wondering if we could retain the style which really affects ... Yeah, I'm afraid not Maya, it just exports into a CSV file only at this point. It's maybe not a bad idea to retain the formatting. Certainly something we can take back to our engineering staff. And finally, [Leslie 00:34:19], does JAWS Inspect work for software as well in addition think web and Microsoft? Yes, it can. I've used it in various sort of desktop softwares, Leslie, and I haven't found anything that it doesn't seem to work in. It even works on your Explorer file systems. So I've done it in there, and it captures all that information just as well. Al Puzzuoli: Can I jump in on that one real quick, Mike? Mike DeSorda: Yeah, please go ahead. Al Puzzuoli: Okay. It works to the extent that the speech viewer works. It's going to be manual testing. You're going to be running through the speech viewer, and you're going to see data from the speech viewer in JAWs Inspect if you're using non web apps. But you're not going to be able to get reports other than the speech viewer. Mike DeSorda: Yeah. Thanks for clarifying that Al. And the other thing I want to say, it kind of makes me remember is, sometimes in JAWS Inspect, you're running a report, and you're wondering why JAWS Inspect did not pick up some kind of component or element or context that you thought that JAWS should be expressing. Well, that's actually a clue to you because if you don't see it in JAWS Inspect, there's a high likelihood that JAWS did not pick it up either and there's something wrong with the design of the webpage that it didn't pick it up. So you shouldn't jump at the conclusion there's something wrong with JAWS Inspect, in fact you should jump at the conclusion there's something wrong with the webpage that JAWS is not picking up correctly. And you might want to check that out and see if there's a redesign necessary there. Let's see ... oh we have some Q&A [inaudible 00:35:56] okay. All right. [Laurie 00:35:58] asked, is there any preferred browser for using JAWS Inspect, and are there any limitations of what JAWS Inspect will capture on the browser such as PDFs or word doc? Well, so we already address PDFs and word. So I think we answered that question. JAWS spec is browser agnostic at this point. It is worth interesting though that JAWS Inspect is a Windows application. And so if you have a Mac, then you will have to have a Windows virtual machine that you run JAWS Inspect inside so that you can do your testing. Al Puzzuoli: And one more thing to add to that too. We work with PDFs inside browsers, but for best performance of PDFs, you want to use Acrobat. But we will work from within a browser, it's just that we will pull more elements from Acrobat. Mike DeSorda: Right. Thank you Al. Yeah, PDFs in particular, obviously you can render those in a browser tab and all these reports that you saw me use, they would work in that case, but as Al said, maybe in a bit more limited way than what an Acrobat reader would be using. [Ginger 00:37:08], just to reiterate, Inspect doesn't confirm the site you are testing, you're testing is compliant? Correct. There's no compliance information there against any sort of standards, it's strictly again, a way to see the JAWS experience so you can determine whether a JAWS user is having a good experience or a poor experience. [Steven 00:37:32] says, are there any plans to make JAWS free for web developer [inaudible 00:37:36]? Have no idea, Steven, we're not in sales. I'm not aware of that, but that's certainly something that if you want to get in touch with [Ida 00:37:47] later as Marissa expressed at that e-mail address she provided, then they can get back to you on that. Ginger asked, would you continue to use ARC tool and manual testing JAWS? So you don't have to. That's a great question. If you are a sighted tester, and your job is to determine whether there are JAWS issues going on and you're testing that using JAWS Inspect, you do not have to have JAWS itself loaded on your system or licensed. JAWS Inspect works independently of that so you don't have to have both at the same time. Is the speech for a floating report, is that a context column? What is the context call I'm referencing? Oh, I didn't notice that. So let's take a look at that. Oh yeah. So Al, this is where they say normal and line, do you know what that is all about under the context there? Al Puzzuoli: Where does it say normal and what? Mike DeSorda: Yeah, under context column in the speech view report, there's a column context, and some of the values are like line and normal. Al Puzzuoli: I believe it's what JAWS is seeing. Like if it's reading a line, or if it's reading text as normal text. If you're doing like maybe a control left and right arrow, it might say word, but I would need to get back to you on that. I'm not a hundred percent sure what that column is. Mike DeSorda: Yeah. There's also a tutor. One of the value [inaudible 00:39:27]- Al Puzzuoli: Tutor is ... JAWS has what's called Tutor messages. So like if you're on a button it might say, press space bar to activate. It'll tell you how to use that control. And tutor is basically going to tell you what the tutor messages spoken by JAWS are. Mike DeSorda: Okay. Thanks Al. Would Al be able to share the true speech speed? Oh yeah. That would be good. Yeah. Why don't we do that? Al, could you demonstrate the true speech speed you would use yourself and as an experienced JAWS user? Al Puzzuoli: Sure. Okay. Let me share my screen. Mike DeSorda: Be prepared to be amazed. Al Puzzuoli: Okay, I need to wait for you to stop sharing and then I can share. Mike DeSorda: Oh okay. Al Puzzuoli: Do we want to do this now or come back to this when you're [crosstalk 00:40:16], I guess you're sharing, okay. Mike DeSorda: Let's just do it now. Al Puzzuoli: All right. Automated: ... have started screen share. Al Puzzuoli: Okay, so this is still the speed [crosstalk 00:40:28] that I was reading the page at originally. Let me- Automated: Zoom. Al Puzzuoli: ... go back to Mater Money. Automated: Mater Money Fin- Virtual, Mater- Al Puzzuoli: And now, I will switch- Automated: Participants- select of- eloquence. Al Puzzuoli: ... and now, we'll do a sale. Automated: [Inaudible 00:40:48] Al Puzzuoli: And that's probably enough, you get the gist. There are JAWS users who listen to this even faster than that. That's a comfortable speed for me. If I want to really blast through something, I might kick it up a notch or two. There are some people who just live with the speed up a little bit faster than that, or even significantly faster than that sometimes. Automated: [inaudible 00:41:22]. Mike DeSorda: All right. Thanks Al. For those of you who've never heard JAWS before, I hope that was enlightening. Al Puzzuoli: And one thing that I will say is that there are trade offs between more human sounding voices and quick, fast, I want to get my work done now type of voices. And that's why ... you know if I'm reading an e-book for pleasure or something, I probably wouldn't use that rate or that voice. Mike DeSorda: Thank you. Susan's asking, can the CSV file be open in Google sheets? Well, not natively from JAWS Inspect, it's going to produce just a regular desktop CSV file. But of course, if you want it uploaded into Google sheets, after that and use it there, then nothing would prevent you from doing that. And somebody anonymous said, do you know of any project management things that work with JAWS? Like Asana, things like that. I'm not really sure what that question's trying to imply unless you are? Al Puzzuoli: I'm guessing it's whether there are some project management apps that are accessible, and I don't know the answer to that offhand. Mike DeSorda: Okay. And Laurie asked, will speech view report pick up items in drop downs as you navigate through it? How does JAWS respond to that when you use- Al Puzzuoli: Yeah, so JAWS Inspect reports are static. So they're going to pick up what's on the page at the time that you tell it to do a full page report. Now, if you're in the speech viewer, and you navigate a dropdown in the speech view report, it will pick that up, but it's not going to pick up any element that needs to change state. Mike DeSorda: Okay. Thank you Al. Al Puzzuoli: Oh, [Benilda 00:43:12] is enlightening us to the context column. Thanks Benilda. Okay. Mike DeSorda: Do you have that Al? Can you express it, or are you looking [crosstalk 00:43:27]- Al Puzzuoli: He put it in the chat window. Mike DeSorda: In the question window or the chat window. Okay, let me get to the last question here. Does JAWS Inspect work on a Mac? We just answered that a few moments ago. It does not directly or natively. You have to have a windows virtual machine loaded on your Mac and where JAWS Inspect can run. Al Puzzuoli: Yeah, and it also will not work on arm-based Mac as of yet. Mike DeSorda: Yeah. All right. Let's see. Let me go to the chat and see what Benilda said. So Benilda says the context column has to do with the internals of JAWS Speech. Some components of JAWS Speech can be disabled in the settings. To support this feature every string spoken by JAWS is tagged with a context. Speaking of some of these contexts can be disabled through the settings manager. The context column identifies which context the string is tagged with. All right. Thank you Benilda. Okay. Is there any other questions? Maybe we can open up to verbal questions if anybody wants to unmute themselves and ask a question? Marissa: Have you guys gone through all the questions to the panelists? Mike DeSorda: Yeah, I think so. Let me look if there's anything new. No, we've gone through everything. Everything was on the question answer area. Marissa: To answer questions again, this webinar is recorded, and you will receive a recording of this webinar in an e-mail in a few days. Mike DeSorda: I think that is the questions Marissa, as far as I can tell. Marissa: Okay. Great. Well, thank you everybody for joining. If you have questions that you think about later, you can always e-mail ida@TPGi, otherwise have a great day. Thank you. Mike DeSorda: Thank you everyone.