- [Marissa] Hello, everyone. Welcome to our JAWS Connect webinar today. I will be waiting for another minute or so, so we give enough time for people to join, but thank you everybody for joining. I'll also be going over a few housekeeping tips, so just hang tight. Thanks for joining. 

Hi everyone. Thanks again for joining our JAWS Connect webinar today. It is now 12:01 Eastern so we are going to start. I would like to go through just a few housekeeping items. First, if you have a question for Charlie, please put it in the Q&A, and he will address it at the end. Also, if you are interested in watching a recording of this webinar, you have to leave early or would like to share it with someone, you will get an email with a link to the recording. Also, if you have any questions that were not answered during this webinar, please feel free to email ida@tpgi.com and I will give that information in the chat as well so everybody can see it. And it is almost 12:02. So I'm going to turn it over to Charlie Pike. He is our product manager and he will talk to you all about setting your future JAWS Connect. Thanks.

- [Charlie] Thank you, Marissa. So yeah, I'm Charlie Pike. And as Marisa said, I am the product manager for the ARC platform and our platform for those of you who don't know, it's TPGI's product for all aspects of an accessibility program. And we also have edge products as we call them a part of the whole platform like JAWS Inspect and this new service, which kind of links some of our solutions together, which is called JAWS Connect and JAWS Connect is what I'm going to talk about today. It's a brand new service that we're offering. It's very exciting. It's not just another feature of the platform. It's really a game changer and it's only possible because TPGI became part of the whole Vispero company organization. 

And therefore we're linked with the assistive technology products such as JAWS. This allows for a very, very unique connection between the accessibility consulting business and assistive technology itself and people with disabilities and their tools. So I'll be taking you through that, as Marissa says, we're going to have some questions and answers at the end. This actually won't take so long as a webinar because the service that we're talking about is by its nature and purpose quite simple to demonstrate and to talk about, but its power is remarkable in terms of what it makes possible. 

So yeah, in terms of an agenda, I'm first going to obviously introduce the topic and the tool and what it is and tell you a little bit about the problem that we're trying to fix. The problem statement, essentially, what are we trying to do here? What are we trying to address? And then I'll talk about the Connect service and all its various parts. And I'll give you a demonstration. I'll show you a video in this case of a user, actually a JAWS user using the service. And then I'll also demonstrate on the platform and on ARC, what that looks like and getting the feedback. And then as I said, we'll open it up for questions and answers. So what is JAWS Connect in general? 


So JAWS Connect very simply is a means for JAWS users to provide feedback on websites, could also be web applications, directly to the accessibility team. And what I mean by that is if you're an ARC customer and you're monitoring a domain or a website in ARC for accessibility, then you can have this service turned on. It's free, if you're an ARC customer already, it's not an extra, you just ask the ARC support to turn it on for you. And we will do that as long as you own the domain. You're not asking for feedback on a domain that's not yours, and as soon as you turn it on, JAWS users will be able to provide feedback on that domain as soon as they encounter that domain, they'll be alert to the fact that the feedback is available. And this feedback goes directly to your ARC monitoring dashboard. So it doesn't go to some inbox somewhere. It goes directly from the user into your ARC management dashboard, where you've got all your other data around the accessibility of your site, combines with that data and makes sure that the message is going to the right people. In other words, the people who were in charge of the accessibility on the domain. So that's a very important feature of it. 

We'll be talking about those things more as we go on. So what problem are we trying to solve here? And what are we trying to fix? As I said, I've been in accessibility business for very long time, nearly 20 years now from the inception of TPGI. And in that time, I've worked with a lot of organizations, government organizations, Fortune 500 companies, small organizations, all of them trying to address accessibility in their own ways. And certainly at the start of that period, it was very much a scatter gun approach. It was one product, one thing at a time, that's developed into more mature programs. There are more organizations now who try to build a mature accessibility program, but the reality is even now and with the improvement I guess of intentions in a lot of cases, you still have this scene. And what I've got here is an image essentially of a tug of war over a cliff or two cliffs if you like. And on the one side in the red, you've got people with disabilities. And then on the other side, you've got organizations, companies, government organizations, all of these, and even with the best of intentions with the state of accessibility as it is now, it's usually this kind of tug of war. 


It's usually something of a struggle and you have people with disabilities simply trying to access services, access businesses, get on with their lives, do their work and facing constant frustration in trying to achieve that. And their leverage really has been over time has been obviously legal action, taking legal action against sites, organizations, et cetera. It's been government mandated, putting political pressure in getting mandates like section 508. And there are mandates all over the world, including in the EU now to put pressure on both public services and companies to effectively, they have to do this. It's the law, it's a requirement. And then you also have social pressure and pressure to social media and so on to get companies to change things. People with disabilities of course go directly to companies as well and say, you need to fix this. You need to do something about this, but generally this is the picture that has emerged over time of how this can be achieved or how people with disabilities can move this along if you like. 

On the other side of this cliff, you have as a result of the way that this pressure is being put on them through legal action and government mandates, often you have bare minimum compliance. And what that often means is somebody brings a legal action. It specifies some particular problem or set of problems on a website and the company or organization come back and address those, say, what are the problems? Okay. Now we fixed them. They may fight it, of course, but this is often the case that we fix those things. That might just be addressing the issues for that particular user group. It might be addressing only a small number of issues out of a lot, and it's really not holistic or longterm. So they might be doing an honest job, but it's a very small job. It's really looking at the problem through a keyhole. You've also got short-term fixes out of this. 

So you've got an organization, for instance, selling to the federal government, selling a product, the federal government mandates that that be accessible. The company then puts in an effort over a number of months or years to make the product 508 compliant. But at the end result is maybe there are other products that they don't touch in their own suite. And likewise, how long does that last if the sale isn't made or if the sale is made, but then the product develops over time, do you lose that accessibility? If it's not at a deep level, at a process level, it's all in the organization, it tends not to stick. And that's the result is you will often see these once-off initiatives. Very often we see companies coming in the door to us looking for audits. They want to find out what they can fix and what are the costs to fix, they do these things, but it's not organization wide. And this is the tug of war that's going on between the two sides constantly. 

And they may not want to be on either side. They may not see themselves as two sides, but this is the result of the pressure and the pushback, I guess, against the pressure. And so you get organizations who are in a tug of war they don't necessarily want to be in, they have no relationship with the users. There are accessibility programs out there across large organizations where the user never comes into the picture at all. It's WCAG, it's section 508, it's a set of requirements, a bug list. Essentially, we need to fix all these things. And it really doesn't look at the user at all, as part of this. And as a result, there's often a poor understanding of the actual requirements. It's painting my numbers. Organizations have a list of things, as I said, a list of bugs and they learn how to fix those bugs either by coming to consultants like ourselves, or simply learning from the available material out there, how do we meet these requirements. But if they don't understand the users and the challenges that the users have and the assistive technologies, they can't really adapt those rules. They don't understand it fundamentally. 

And so for instance, they may understand how to get their calendar control accessible to screen reader users by following technical requirements. But if they don't understand screen readers and how they work and what users want to do, then they're not going to adapt that the next time they change that control, or they have some new type of control that hasn't been used before. What do you do then? Unless they understand, there's a limitation on what they're doing. And finally, perhaps most importantly, it tends to be half-hearted. You may have advocates, strong advocates in your organization for accessibility, but for many people, particularly development teams and so on, this is just another requirement that they have to meet, another standard. 

And I've had customers say to that to me in the past, look, we have to deal with compliance with ISO standards. We have to be security compliant. We have to be this, that, and the other compliant. And this is just another one in the list. This is very demotivating, if you want to do things effectively and longterm, you really want to put the user in the picture. So this becomes a matter of empathy. Empathy is what's lacking here. Empathy is something that's talked about more and more in business terms, in terms of the value of empathy in your organization. We as human beings tend to be motivated by other human beings. It's the way we learn. It's the way we think. It's our main focus is others. So building the empathy is the way to unlock if you like the potential around your accessibility program. For a start, it affects motivation. 

We are, as I said, motivated by other people, not by abstract standards. We might be motivated to meet requirements and hit a target, but really principally when we realize we're doing this work for somebody and that they are benefiting from it, it's much, much more effective way to motivate teams. It just changes the picture completely. It builds a constructive relationship, and that goes both ways. So for users with disabilities, who are just trying to do certain things, they're trying to complete tasks on the web, they're trying to do their job and so on. 

And yet they're beating up against a wall all the time, the difference of raising issues and having them addressed and actually connecting directly to an organization and seeing change is just a game changer. The whole attitude and relationship changes as a result and becomes much more constructive rather than simply suing or going to government mandates, trying to put out alternative pressures. You build a conversation. And in that conversation begin to understand one another and expectations change as well. And then the user can become a guide and an advocate. So you're not just in the dark painting by numbers. You're actually talking to users and you're going well, we've done all of this stuff, but now how usable an experience is it for end-users? 

What are the things that are really important to end users, as opposed to the things we might be spending a lot of time on that actually make very little difference at all? It might be there in the standard, but in these cases, do they matter to users as opposed to other things that we might not have thought of? So they could become the guide to how you prioritize and how you think about your accessibility and also ultimately an advocate for what you're doing. Because at the end of the day, you make the changes and you see the result for users, then they become your case studies, if you like, your examples of effective accessibility. So how do you actually reach these users and build this connection if it's so important? And obviously there are lots of ways to do this on the web for users in general. 

So you've got CRM systems like Hubspot, you've got things like Zendesk, SurveyMonkey, there's thousands of them out there. It's quite a mature world now, we have overlay systems and so on for engaging your users, all kinds of live help and so on. There's all these kinds of ways to do it. But there are limitations to these approaches. One is that obviously solutions are not fully accessible. Those things have improved over the years. They've kind of gone up and down. Some are better than others, but the reality is if you're not providing an optimum accessibility experience to get that connection and that feedback to users, then you're already set up for failure. So it's not a great approach. 

There's no identification of assistive technology users. So you don't know they're out there. A lot of people don't necessarily self identify as someone with a disability. You can't see the assistive technology. So you don't know how many people with disabilities, how many JAWS users for instance are coming onto your site and so on, and to address them and their needs directly. They go into a sort of general group in terms of feedback, even if you ask accessibility questions and it's also often obstructive or difficult. These are often tools that are separate that the user would need to get familiarity with. This can be doubly difficult if you're using an assistive technology. So let's say you need to go to another site, or this is built into the website somewhere, but getting focused to that place, being aware of it, and it can obstruct you. 

These systems can get in the way of the assistive technology doing its job, and they can be different from site to site. So just because you've done feedback on one, doesn't mean they're going to have the same system on another site, and this is a huge problem. You've got to learn it, everything is an extra weight, extra time. And remember that the key to getting feedback and getting connection is to smooth the path for the user. It's got to be easy. It's got to be efficient and non-obstructive and it's really got to be going to the right place as well. There's no point in getting this information with general user information about the usability of the site. You need to be able to target this accessibility information. So this is how we came up with JAWS Connect. 

And as I said, it's a unique offering because of the nature of our organization. We have both the assistive technologies, in this case JAWS, which is the leader in the field of screen readers with the most users, by far and away the most users. So we are able to combine these two to make it seamless. And the benefits of the approach are it's built in, there's no install or learning. So JAWS Connect is built into the latest version of JAWS, the 2022 version of JAWS. There's nothing the user needs to do. It's just there, it's quiet inside JAWS, initially you don't need to configure it or set it up. So that that's huge because they know how to use JAWS. So it's not a separate system each time they come across it. It's quick and easy. And I'll show that in the demonstration, it's very, very straightforward for them to use, again, smoothing the path. It's non-obstructive, they're made aware that it's there. It's inside the interface for JAWS, for instance, inside the links list, they don't have to go anywhere to use that. It's just available to them right there. There's clear data handling so we make it very clear. I'm going to show you as we go through the demo, how we make it clear to the user what's happening to the data, and they have the option to send contact details if they want to start a conversation about an issue. 

And it's straight to the right place, and this is the key, it goes to the accessibility team because the data they provide goes directly to the ARC dashboard and who's using the ARC dashboard, it's the people responsible for accessibility in the organization. So it's going to the right people who they know will address things so that all the more reason to provide the feedback. It's clear that it's going to the right place and it can be acted upon. For the ARC customer then, similar benefits. There's no coding. You don't need to set anything up. It's free. Once you're already monitoring your domains with ARC, this is a free service, a free add-on. The data goes to the right place to the people who are actually going to be able to make use of it, as I said to the team, and you can combine it with the dashboard analytics to give you an overall picture of your accessibility. So it's an additional data point. You've got all your data from ARC, from the scans in terms of accessibility tests. Perhaps you've got manual test data there, I'll talk you through that in a minute. You've got all of that. 

And now you've got that extra layer, which is what is the actual user experience. And another thing that I haven't mentioned before is it helps to meet program requirements for user feedback. So a lot of accessibility programs now and in the past have had a component to them, which is not just compliance with certain technical requirements, but also to provide a mechanism for users to provide feedback and others to raise issues. The assumption is in all of these that you're not going to achieve complete compliance or total accessibility. There is no such thing. So there should always be a route for users to say, hey, this didn't work, or to praise you and say, this is great, I love this, but there must be a method to provide that feedback. And this is the ultimate way to do that because as it is, it's built into the assistive technology. So now I'm going to show you a demo. I'm going to show you a video because it's best to see this from the perspective of an actual assistive technology user, in this case, Matt Ager, who's involved in TPGI. And Matt did a demo recently at the launch of this service, just showing you from the user's point of view in JAWS how this all works. Just get this playing. Here we go.

- [Matt] All right, checking out the demo of JAWS Connect. I've opened up a page, we're on tpgi.com. And I'll go ahead and check that with insert+T.

- [Computer] TPGI.

- [Matt] Now that I know I'm on that page, if I was on a page and found something that I wanted to report, I can press insert+F7 to get a list of links.

- [Computer] Links list dialogue, links list view. Provide feedback on the page using JAWS Connect, one of 79.

- [Matt] And you can see at the top of the links list is the provide feedback using JAWS Connect. I'll go ahead and press enter on that.

- [Computer] JAWS user feedback form. Heading level two and user feedback for www.tpgi.com. To improve www.tpgi.com for JAWS users, we would like to collect some feedback. Please answer the following questions.

- [Matt] And I can press the tab key to go ahead and land in the first question.

- [Computer] JAWS user feedback for www.tpgi.com complementary region. Was this your first visit to this page group? Yes radio button, not checked, one of two.

- [Matt] And I can press the enter key to turn on forms mode, and then I can arrow into my choice.

- [Computer] No radio button checked, two of two.

- [Matt] So I'll leave it on no, and I'll hit the tab key.

- [Computer] What task were you trying to do?

- [Matt] And I'll go ahead and type in the task.

- [Computer] Looking for the blog link.

- [Matt] And I'll read back with insert+up arrow.

- [Computer] What task were you trying to do? Looking for the blog link.

- [Matt] and I'll press the tab key.

- [Computer] Please provide details of what happened and what you expected to happen.

- [Matt] I'll go ahead and type in my answer here.

- [Computer] I was able to find the link, use the JAWS list of links period. I was able to find the link using the JAWS list of links.

- [Matt] Completed that, I'll hit the tab key.

- [Computer] Were you able to complete your intended task group? Yes radio button not checked. One of two.

- [Matt] So out of two choices, yes.

- [Computer] No radio button checked. Two of two.

- [Matt] And so I'll go back to yes.

- [Computer] Yes radio button checked, one of two.

- [Matt] And then I'll hit the tab key.

- [Computer] How would you rate the accessibility of this page group? Very accessible radio button not checked. One of four.

- [Matt] Then I have accessible.

- [Computer] Moderately accessible radio button checked, two of four. Moderately accessible radio button checked, three or four. Very unaccessible radio button checked, four of four. Very accessible radio button checked, one of four.

- [Matt] So I'm on very accessible, I'm going to hit the tab key.

- [Computer] Feel free to contact me regarding this feedback checkbox not checked.

- [Matt] And I can check the box if I want somebody to contact me, it doesn't mean anybody will contact you. It just gives them the notification that you're willing to talk about whatever issues you ran into. So I'll go ahead and check the box and hit the tab key.

- [Computer] Email address pop up. Submit button. Enter. Thank you. Heading level one, our accessibility team has received your report. If you selected the contact option, we may be in touch if we have any further questions about the issue. Thank you again, your efforts will help us make a better web for everyone. You can now close this tab using control plus W.

- [Matt] Very good. So I'll press control+W to go ahead and close the tab.

- [Computer] TPGI Paciello Group is now TPGI accessibility solutions provider. Google Chrome.

- [Matt] And now the form was submitted and is sitting inside the ARC platform for somebody to review the feedback.

- [Charlie] So that was Matt Ager using the tool in JAWS. So that's the first iteration of the feature. It will include an alert of some kind, we're working on that at the moment to essentially let the user know that it's there as an option on that domain. So feedback is available. We want to do that as unintrusively as possible, and we're working with users to understand what the best experience is there, but you can see that it's very, very easy for the user, either from the links list or from a couple of other places in JAWS you will get that link available and go straight to the feedback form. And that mechanism will always be the same, so that there's really nothing to learn here. It's very straightforward. And as I said, not obstructive. 

So the user gets the note that they can provide feedback on the domain. They fill out the details and submit it, and it comes to the customer's domain. So essentially we look at it from the customer perspective. I'm in ARC here in an ARC account, and I've got a workspace open. And in that workspace, we're monitoring different properties. So we're scanning them for accessibility on a regular basis. In this case, maybe we've done a lot of work for accessibility over the years, and we're in that sort of monitoring state, we've addressed what we can address. Always some issues out there. 

And we're in a state where we're really watching the accessibility and making sure it stays effective. What we want to know beyond that, what is the user experience and how are users actually getting on with our domain? And here's our monitoring dashboard, where we have our key data indicators, the WCAG density score, the historical data over the lifetime of the scanning. How has the site improved or not improved? How has it improved since the last scan? Our overall trend lines over time, which should hopefully be continuing down or staying down. All of that key data. And in here right into the dashboard, the top performance summary panel is this usability feedback. So here is what Matt provided in that demo. 

And it goes straight into the dashboard, it sends the user fields and then it gets sent directly to ARC. And it appears here and all of the data, including some data that we're tracking, which we tell the yser we're tracking, the JAWS version, the URL in question, in the future that will actually link directly to the ARC dashboard, where you can see data about that URL, if you've been scanning it, and the browser version. So this all helps to diagnose whatever issue the user has encountered and understand the context. And then you have everything that the user filled in, including permission to contact and the contact details if they provided it. And this is all together as part of the monitoring interface. So you can use it together with your other monitoring data. So you can go in, look at your data. And let's say for the sake of argument, a user has complained that they can't use the calendar control to set a date for something. 

You can look at your scan data and see have we found that problem in our accessibility scanning up to now? And if you have, we need to prioritize and address it, if not, why not, do we need to do a further audit? Do we need to examine that more carefully to understand why? Maybe we need to get back to the user and find out what specifically they were trying to do and why they weren't able to complete it. All in all, it starts to create that connection that we talked about with the user, which is the missing piece. 

To give you an idea, if we look at a domain where we've done a lot of different work on here, we have the guardian domain in our demo site and the guardian have been doing various kinds of analysis. So we have the domain scans we'll be doing on a regular basis on the guardian domain, which gives that broad overview. And they've been scanning individual folders to look at specific sections of the guardian site. And that includes obviously looking at templates comparing one template to another. We've got user flows and user flows are essentially key tasks that a user will carry out on the site. For example, on a hotel website, it would probably be the booking process would be a key user flow. And this is another level of analysis, if you like, it's a more detailed level of analysis where you're focusing on a few key things, the template here, a podcast listing, a video listing page, and then you've got the manual audit. 

So you've got the expert engagement, which is not automated, which is the complete WCAG compliance testing of all the various requirements, including those that are covered by the automated scans. And this is the most detailed and forensic view. And they've done a thorough analysis of the key flows in there, and they're getting all the detail they need on the dashboards. And that includes by the way, JAWS speech from JAWS Inspect that they can include in there to see a transcript of what the JAWS user would experience on the page. They've done all these levels of analysis. And because we're using the same rules engine throughout, the ARC rules, they can effectively compare this data, including their engagement data, and see how they're doing, what they need to prioritize, what they need to fix. 

And now we've added this extra layer through the JAWS Connect, which means you can go beyond the compliance to actually find out what the user experience is and make sure that it's optimum for the user and you build that connection. And you see that conversation. The best time to build that is when you've already done some work and you want to see how effective that work is. And just going back to our slides here, the way I see this in terms of getting a complete picture on your accessibility, it's like peeling back the layers of an onion. And at the top level, you've got those domain scans, which are used to see trends, big picture, and particularly what's going on behind the scenes that might be causing those trends, your production cycles, your processes, et cetera, that might be causing issues that will bring you to decisions around how do we address this longterm? What do we change in our production process, our test process to make sure these issues are addressed? Then you've got the user flows as I showed you. 

These are the critical paths that you need to focus on, and they get a more intensely focused analysis. And then you've got your manual expert audits, which are deeper still, deeper to the core, which really are, as I said, forensic, show me everything, everything that's an accessibility issue on this site. So you can do a full analysis and address them in full and that core is now that user feedback and user research. Reaching out to users, we know user research is something that's very, very important, but not often done because of the cost and the time to set up. And it's not ongoing. You'll do this every now and again, doesn't tend to be an ongoing part of development process. So this is where user feedback is so critical because it can be happening all the time at any time. So that conversation is going on all the time. And that is how the ARC platforms through these various methods provide you with that complete picture of your accessibility. It's not just narrowly focused on one thing or compliance with one standard or whatever. It's the whole picture is available to you in whatever way you want to use that. 

So that's the service, that's JAWS Connect. As I said, we were quick enough running through that. I will open it up now to folks who have questions. We already have some questions in here in the Q&A, so we've got first question, how do I become a member of ARC and how much does membership cost? So you can sign up for ARC directly on the tpgarc.com website. We actually have a free tier which provides you with a initial domain analysis as we call it a first report and the accessibility of your domain and the free tier is that you can have one user on the free tier. Beyond that, ARC is charged on a usage basis, which means that you can really control your cost. So we charge per call on our API and per page in terms of our scans. So you can really decide how many pages you want to scan. Once you are monitoring a domain, then you are able to turn this service on for free. 

Another question, how many URLs can a single account be associated to? I assume this means different domains. So you can have it really any number of domains that you want in a specific account. And for each of those domains, if you're monitoring them, you can then turn on the feedback service. And as I said, once that's turned on, you just have to ask us once that's turned on, then the JAWS user will automatically be notified. Question, is the link visible to sighted users or other aided users? At the moment it's JAWS only, of course, we're looking at other ATs down the line, but we're starting off with JAWS. And obviously JAWS is one of the most widely used ATs out there. So it's not necessarily visible to sighted users. It's really through the assistive technology. And that's a good thing because it means that it's right there as you need it, it's not a separate feature, separate from the assistive technology. 

Another question, how will a JAWS user know that the option to submit feedback is available? So it does appear for instance in their links list and where they get a list. If they press insert+F1, they'll get a summary of the page and it will appear there too. But as I said earlier in the presentation, we're working on ways of effectively notifying the users. So there will be a notification, probably an audio notification when the user first encounters the domain to tell them that the feedback is available and that'll be on again each time they come back to the domain if you like. So it just happens once. So it's not intrusive for the user. Would an area alert be a good way to alert the user to availability? I suppose, potentially we certainly follow a similar idea, but since it's built into JAWS, we don't need to go down that line. We don't need to put something in the code again. We can optimize the experience by making it part of the assistive technology itself rather than somewhere else. We're very conscious of a lot of tools that have sprung up over the years that provide assistive technology to users directly on the site. It provides certain tools like it will read the site content to you. Problem is the users are used to their assistive technologies. They don't want to learn a new assisted technology each website they encounter. So we really want to do it in one way, provide the alert in one way inside of JAWS. And that will always be the same for them. So again, fluid, simple and unobtrusive for the user. 

Another question, what happens if I do a linked list in NVDA? Well, at the moment, we're not supporting NVDA, so NVDA will not be able to provide that, the whole feedback process works only with JAWS at the moment. Any more questions?

- [Marissa] There's one question from Chris Smart. Is there any plan to make JAWS Connect available to everyone, or is it just available to the users of your platform? What are the chances that a webmaster I submit a bug report to is involved with your company?

- [Charlie] So first part of that question, is it going to be more widely available outside of the platform? We have no plans to do that because as I said, the key part of this is the connection with the platform that the information goes to the right place. And again, it's consistency and ease of use. The key for any feedback system is going to have to be that it's unobtrusive and easy for the user, and it's a consistent experience. So having it go out of the platform would in a sense break that connection. And so it would simply become another feedback service. It wouldn't be what it is. Marissa could you read to me that last part of that question again?

- [Marissa] What are the chances that a webmaster I submit a bug report to is involved with your company?

- [Charlie] So if the feedback is going directly to the monitoring dashboard in ARC, so it's going to go to an organization. If it's a webmaster, whoever is in charge of the accessibility for that domain, it's going to go to them because they're going to see it on their dashboard. If they're not looking at the right dashboard, they're not really doing what they're supposed to be doing. The key here is we make sure before we turn this on, that you are the owner of the domain. In other words, it's not going to somebody else. In other words, you can't turn this service on for a website you don't own. So you're getting feedback about somebody else's site from JAWS users. You have to be the owner of this website. You have to be the right person.

- [Marissa] We have another question. Is the feedback link only available from the links dialogue? Or can they user tab to the link, but it's visually hidden?

- [Charlie] It's not visually hidden. As I said, it's not just the links dialogue. It's also, if you press insert+F1, it is available in your summary there of the page. And as I said, we will provide an alert that will take the user directly to it when they first encounter the page so that they don't have to dig around or search for it. Obviously the more aware users become of its availability, the easier they'd be able to find it in things like the links dialogue.

- [Marissa] One other question, is there a projection of how many websites you hope will use the ARC software? How will we know if websites are using ARC?

- [Charlie] So obviously we have a lot of sites currently under monitoring. We have thousands of sites currently being monitored by ARC so this is where we'll learn from these sites how many want to turn it on and use that service. We're hoping that just about everybody will, because why not? And to get their feedback that way. So from a user point of view, obviously they'll know when they encounter the sites and JAWS lets them know that it's available. The community in general, I guess, watch this space for updates on how that's progressing.

- [Marissa] What about Moodle? JAWS doesn't work on iOS or Android.

- [Charlie] So again, right now, this is a JAWS only feature for the reasons that I've laid out, but we're looking at all the different ways that the feedback might be connected with the ARC platform in different assistive technologies and platforms.

- [Marissa] What version of JAWS do you need?

- [Charlie] So the very latest, JAWS 2022 will include this. It's basically from the end of this year, start of next year, people will be able to start to use it.

- [Marissa] One last question. Shouldn't the service be opt out, not opt in, IE by default?

- [Charlie] I mean, if we're talking from the end user's perspective, there's nothing need to opt out of. They don't want to provide feedback. They don't provide feedback. It's not obtrusive. It's not going to pester them. There will be an option to turn it off in the JAWS interface, it's not something that's going to get in their way. And from the ARC customer's point of view, it's essentially, you have to opt in, I guess. But the key reason here is that we need to make sure that they are the owners of the domain.

- [Marissa] Chris, I think that answers your question. He had said, no, shouldn't it be on by default for the ARC user, so okay, thanks. If nobody has any... Oh wait, no, we have another one.

- [Charlie] I work for a large company with thousands of URLs and multiple domains, can a single account point to all of the individual page in multiple domains? So yes, you can have multiple domains and all the individual pages in a single account, I showed you there the ARC interface, you've got workspaces inside of the account, and you can put different domains into those workspaces and organize them accordingly. So if your domains are organized by product group or geography or whatever, you can set them up in workspaces as needed, and you can monitor all of those and compare your results and your JAWS Connect data would be with those domains.

- [Marissa] Does anybody else have any other questions? All right. It looks like Charlie, you have answered all the questions. Thank you very much everyone. Thank you for joining. Again, there will be an email sent to everyone with a recording of this webinar, in case you'd like to share it with someone else or would like to review it. And also, if you have any questions that you thought of later, you can email ida@tpgi.com. And that email is in the chat box as well. So thank you very much everyone. And have a wonderful rest of your day.

- [Charlie] Yes. Thank you much. Thank you everybody for your time.

- [Marissa] Okay. Great. Good bye guys.