1 00:00:05,960 --> 00:00:08,503 - Hi, everyone. Good morning, good afternoon. 2 00:00:09,650 --> 00:00:10,880 We'll be starting the webinar 3 00:00:10,880 --> 00:00:12,570 in probably just about one minute. 4 00:00:12,570 --> 00:00:15,532 We'll give a few more moments for everyone to join in. 5 00:00:15,532 --> 00:00:18,290 So sit tight and hang out. 6 00:00:18,290 --> 00:00:19,890 We'll kick off in just a minute. 7 00:00:50,160 --> 00:00:51,870 All right, very good. 8 00:00:51,870 --> 00:00:53,030 Again, good morning. 9 00:00:53,030 --> 00:00:54,210 Good afternoon, everyone. 10 00:00:54,210 --> 00:00:56,620 Thank you for for joining TPGi 11 00:00:56,620 --> 00:00:58,660 and our webinar session today 12 00:00:58,660 --> 00:01:00,780 around Transitioning to ARC 13 00:01:00,780 --> 00:01:04,993 as Compliance Sheriff Sunsets come the end of this year. 14 00:01:06,070 --> 00:01:08,190 So I always like to start off these sessions 15 00:01:08,190 --> 00:01:10,420 with just a really high level overview 16 00:01:10,420 --> 00:01:12,350 of what we'll be covering for today. 17 00:01:12,350 --> 00:01:14,320 So here's the agenda. 18 00:01:14,320 --> 00:01:18,240 In just a moment, I'll provide a handful of introductions. 19 00:01:18,240 --> 00:01:21,940 We'll do a general overview of why we're all here today, 20 00:01:21,940 --> 00:01:25,250 which we all should be a bit aware of. 21 00:01:25,250 --> 00:01:28,450 Then we'll be able to transition into a demonstration 22 00:01:28,450 --> 00:01:30,680 of the ARC platform. 23 00:01:30,680 --> 00:01:33,280 We'll do a bit of a comparison conversation 24 00:01:33,280 --> 00:01:35,890 between Compliance Sheriff and ARC. 25 00:01:35,890 --> 00:01:38,150 We'll talk through deployment options, 26 00:01:38,150 --> 00:01:41,060 next steps, and certainly with all remaining time, 27 00:01:41,060 --> 00:01:42,430 I'll open it up to Q&A. 28 00:01:42,430 --> 00:01:45,560 So do make sure that you use the Q&A panel 29 00:01:45,560 --> 00:01:48,470 to ask any questions as we go through today's session 30 00:01:48,470 --> 00:01:51,080 so we can address them at the tail end. 31 00:01:51,080 --> 00:01:55,290 Also, there is live captioning on for this session. 32 00:01:55,290 --> 00:02:00,010 So do feel free to leverage that as you may see fit. 33 00:02:00,010 --> 00:02:01,700 And the session is being recorded, 34 00:02:01,700 --> 00:02:05,210 should there be a need to view the session on demand 35 00:02:05,210 --> 00:02:07,150 after the fact. 36 00:02:07,150 --> 00:02:09,490 So with that, let's jump into introductions. 37 00:02:09,490 --> 00:02:10,650 My name is Brenton West. 38 00:02:10,650 --> 00:02:13,210 I'm the Vice President of Compliance Sheriff 39 00:02:13,210 --> 00:02:14,760 over at Appgate. 40 00:02:14,760 --> 00:02:18,640 Today, tou'll also be hearing from two individuals 41 00:02:18,640 --> 00:02:20,000 from the TPGi team. 42 00:02:20,000 --> 00:02:23,010 That includes Travis Brown, the VP of sales and marketing. 43 00:02:23,010 --> 00:02:25,830 And Kurt Mattes, customer success consultant 44 00:02:25,830 --> 00:02:29,110 and senior accessibility engineer. 45 00:02:29,110 --> 00:02:31,530 So with that, let's do that overview, 46 00:02:31,530 --> 00:02:33,700 kind of why we're all here today. 47 00:02:33,700 --> 00:02:36,020 And it was really all driven at the beginning of the year 48 00:02:36,020 --> 00:02:39,690 when Appgate had to make the very difficult decision 49 00:02:39,690 --> 00:02:42,010 that Compliance Sheriff was gonna kinda enter 50 00:02:42,010 --> 00:02:44,750 a end of life timeline this year. 51 00:02:44,750 --> 00:02:49,100 And, we certainly fought hard not to go down this path, 52 00:02:49,100 --> 00:02:52,103 but unfortunately it was where we were left with. 53 00:02:53,440 --> 00:02:56,710 So we wanted to help our customers as much as possible 54 00:02:56,710 --> 00:02:59,280 by making the announcement early in the year 55 00:02:59,280 --> 00:03:01,630 and providing as much runway for everybody 56 00:03:01,630 --> 00:03:03,700 so that you would be able to decide 57 00:03:03,700 --> 00:03:06,510 what you wanna do as you continue with your needs 58 00:03:06,510 --> 00:03:09,980 for automated compliance and accessibility testing. 59 00:03:09,980 --> 00:03:14,580 So we made that announcement in February in Q2. 60 00:03:14,580 --> 00:03:17,950 We had been reviewing all of the solutions 61 00:03:17,950 --> 00:03:19,830 out in the marketplace. 62 00:03:19,830 --> 00:03:23,110 We identified the ARC platform as being really 63 00:03:23,110 --> 00:03:25,540 one of the most capable in the marketplace. 64 00:03:25,540 --> 00:03:30,310 And so we made a preferred technical recommendation 65 00:03:30,310 --> 00:03:33,060 to our customers saying that if you're looking 66 00:03:33,060 --> 00:03:34,483 for an alternative solution, 67 00:03:34,483 --> 00:03:36,660 ARC's a really strong contender. 68 00:03:36,660 --> 00:03:39,970 So we kinda gave our nod to go look there. 69 00:03:39,970 --> 00:03:42,910 So today we're here to do a joint webinar 70 00:03:42,910 --> 00:03:45,150 so we can show you ARC's capabilities, 71 00:03:45,150 --> 00:03:47,830 talk a little bit about migration options. 72 00:03:47,830 --> 00:03:49,750 And just to look ahead. 73 00:03:49,750 --> 00:03:52,740 We are gifting all Compliance Sheriff customers 74 00:03:52,740 --> 00:03:55,430 the ability to have a perpetual license 75 00:03:55,430 --> 00:03:58,300 of Compliance Sheriff running in their environment. 76 00:03:58,300 --> 00:04:00,600 And especially for those who leverage 77 00:04:00,600 --> 00:04:03,590 a hosted license today, that migration, 78 00:04:03,590 --> 00:04:07,120 we're targeting to complete any customer migrations 79 00:04:07,120 --> 00:04:09,120 in the August timeline. 80 00:04:09,120 --> 00:04:11,320 This will allow for the end of the year 81 00:04:11,320 --> 00:04:15,120 to just be a standard period of support for all customers, 82 00:04:15,120 --> 00:04:17,000 as we do wind down all of our systems 83 00:04:17,000 --> 00:04:19,950 and all Compliance Sheriff sales services, 84 00:04:19,950 --> 00:04:23,390 everything concludes come the end of the year. 85 00:04:23,390 --> 00:04:25,010 So a couple of really quick highlights. 86 00:04:25,010 --> 00:04:26,930 We can go to the next slide. 87 00:04:26,930 --> 00:04:30,140 Again, as we reviewed, all the solutions in the marketplace. 88 00:04:30,140 --> 00:04:32,280 We really saw the ARC platform 89 00:04:32,280 --> 00:04:35,540 as one of the most comparable solutions 90 00:04:35,540 --> 00:04:37,930 to Compliance Sheriff and its ability 91 00:04:37,930 --> 00:04:40,590 to scale features and functions. 92 00:04:40,590 --> 00:04:42,830 And another kicker to everything 93 00:04:42,830 --> 00:04:47,480 is that there's the ability to offer migration services, 94 00:04:47,480 --> 00:04:49,650 taking all that hard work you and your teams 95 00:04:49,650 --> 00:04:51,560 have kind of put into Compliance Sheriff 96 00:04:51,560 --> 00:04:54,950 over the years to find what web properties you wanna scan. 97 00:04:54,950 --> 00:04:57,570 Even more complex scenarios 98 00:04:57,570 --> 00:04:59,260 that leverage transaction scripts 99 00:04:59,260 --> 00:05:01,730 to provide keyboard-mouse type capabilities 100 00:05:01,730 --> 00:05:03,290 to the automated solution. 101 00:05:03,290 --> 00:05:06,410 There's gonna be the ability to take all of that setup 102 00:05:06,410 --> 00:05:09,390 and put it into ARC so that you don't have to necessarily 103 00:05:09,390 --> 00:05:11,470 reinvent the wheel, but we'll certainly cover that 104 00:05:11,470 --> 00:05:13,763 as we go through today's session. 105 00:05:14,630 --> 00:05:16,470 So without any further ado, 106 00:05:16,470 --> 00:05:19,410 I really wanna open up the floor to the TPGi team. 107 00:05:19,410 --> 00:05:21,390 I'll pass the baton over to Travis 108 00:05:21,390 --> 00:05:23,690 so he can introduce his organization 109 00:05:23,690 --> 00:05:25,580 and then we'll be able to take a look at ARC. 110 00:05:25,580 --> 00:05:26,630 So with that, Travis. 111 00:05:27,670 --> 00:05:29,050 - Thanks, Brenton. 112 00:05:29,050 --> 00:05:31,250 And welcome to all of you who are on the call today. 113 00:05:31,250 --> 00:05:35,550 Appreciate you all taking the time to connect with us. 114 00:05:35,550 --> 00:05:37,650 Thanks, Brenton for the nice introduction. 115 00:05:40,132 --> 00:05:43,500 So as mentioned, we've been in some dialogue 116 00:05:43,500 --> 00:05:46,468 with Compliance Sheriff for awhile 117 00:05:46,468 --> 00:05:49,920 over ways that we might be able to help 118 00:05:49,920 --> 00:05:53,020 with the transition for Compliance Sheriff customers 119 00:05:53,020 --> 00:05:54,280 to something different. 120 00:05:54,280 --> 00:05:59,280 And so today's session is just part of that process for us, 121 00:06:00,040 --> 00:06:03,910 is to try to continue to educate current customers 122 00:06:03,910 --> 00:06:05,710 in what possibilities exist 123 00:06:05,710 --> 00:06:06,960 and as it relates to ARC. 124 00:06:07,980 --> 00:06:10,510 For those of you that are not familiar with TPGi, 125 00:06:10,510 --> 00:06:13,783 I wanted to kinda do a quick recap on who we are. 126 00:06:14,810 --> 00:06:18,990 So we've been around for nearly 20 years. 127 00:06:18,990 --> 00:06:22,710 The company was founded in 2002 as The Paciello Group. 128 00:06:22,710 --> 00:06:25,720 We actually happened to rebrand 129 00:06:25,720 --> 00:06:30,720 to TPG Interactive or TPGi for short earlier this year. 130 00:06:32,260 --> 00:06:35,230 We are an accessibility solutions provider. 131 00:06:35,230 --> 00:06:38,710 We support all phases of your accessibility journey. 132 00:06:38,710 --> 00:06:42,853 So we do that predominantly through our platform, 133 00:06:42,853 --> 00:06:47,853 but we have a very robust service capability. 134 00:06:47,880 --> 00:06:52,430 So for those of you that are potentially interested 135 00:06:52,430 --> 00:06:56,840 in a more comprehensive approach to accessibility, 136 00:06:56,840 --> 00:07:00,517 we do provide the services that would be complimentary 137 00:07:00,517 --> 00:07:01,780 to a platform. 138 00:07:01,780 --> 00:07:04,590 So we offer audit services, 139 00:07:04,590 --> 00:07:07,453 we offer accessible UX design type services, 140 00:07:08,930 --> 00:07:12,740 accessibility training and strategic consultation 141 00:07:12,740 --> 00:07:15,010 are among the things that we provide. 142 00:07:15,010 --> 00:07:16,120 We also happen to be part 143 00:07:16,120 --> 00:07:19,770 of the larger organization called Vispero. 144 00:07:19,770 --> 00:07:23,240 Vispero is the world's largest provider 145 00:07:23,240 --> 00:07:26,230 of assistive technology for blind individuals. 146 00:07:26,230 --> 00:07:28,640 So we have a very unique perspective, 147 00:07:28,640 --> 00:07:30,880 I would say, from that regard 148 00:07:30,880 --> 00:07:35,300 in that we have great familiarity with JAWS, for example, 149 00:07:35,300 --> 00:07:37,310 JAWS is one of the core products 150 00:07:37,310 --> 00:07:41,340 that Vispero family companies owns. 151 00:07:41,340 --> 00:07:46,307 And so, we have all of that great background as well, 152 00:07:46,307 --> 00:07:47,860 but that comes to organization 153 00:07:47,860 --> 00:07:49,390 and provides other opportunities 154 00:07:49,390 --> 00:07:52,750 for us to help do JavaScript and other capital services 155 00:07:52,750 --> 00:07:54,930 that might be valuable to companies 156 00:07:54,930 --> 00:07:57,480 that are going through their accessibility journey. 157 00:08:01,420 --> 00:08:03,130 One of the things we'd like to promote is, 158 00:08:03,130 --> 00:08:07,190 is that we are able to scale with your organization 159 00:08:07,190 --> 00:08:12,190 and be the tactical immediate urgent provider of support 160 00:08:13,720 --> 00:08:15,680 for those of you that have a hair on fire problems. 161 00:08:15,680 --> 00:08:17,900 But we're also about building 162 00:08:17,900 --> 00:08:19,950 sustainable accessibility practices 163 00:08:19,950 --> 00:08:23,380 and a long-term longitudinal approach to accessibility. 164 00:08:23,380 --> 00:08:26,120 So you'll see some of that manifested 165 00:08:26,120 --> 00:08:29,630 in how our platform is set up and how we operate, 166 00:08:29,630 --> 00:08:32,537 but it also can be supported 167 00:08:32,537 --> 00:08:35,500 by the various other services that we provide. 168 00:08:35,500 --> 00:08:40,480 So as Brenton mentioned, I think there's good parity 169 00:08:40,480 --> 00:08:42,220 between the Compliance Sheriff platform 170 00:08:42,220 --> 00:08:43,210 and the ARC platform. 171 00:08:43,210 --> 00:08:45,710 And we're here to try to give you largely today 172 00:08:45,710 --> 00:08:47,160 a functional overview of that. 173 00:08:47,160 --> 00:08:50,260 So we won't spend a ton of time talking 174 00:08:50,260 --> 00:08:53,820 about pricing in detail or technical specs in detail. 175 00:08:53,820 --> 00:08:54,653 We'll really kinda leave it 176 00:08:54,653 --> 00:08:58,190 at the macro functional level today, 177 00:08:58,190 --> 00:08:59,613 but at the end of the session, 178 00:08:59,613 --> 00:09:00,730 there will be an opportunity for you guys 179 00:09:00,730 --> 00:09:02,640 to get linked up with TPG 180 00:09:02,640 --> 00:09:05,880 if you wanna have a more involved conversation, 181 00:09:05,880 --> 00:09:06,960 and we actually encourage you guys 182 00:09:06,960 --> 00:09:09,210 to reach out to us to do that. 183 00:09:09,210 --> 00:09:12,460 So we'll provide some links to get connected with us 184 00:09:12,460 --> 00:09:16,180 and do a more personalized experience 185 00:09:16,180 --> 00:09:17,940 about how we might migrate you guys 186 00:09:17,940 --> 00:09:19,170 to ARC if you're interested. 187 00:09:19,170 --> 00:09:21,520 So with that said, I'm gonna turn it over 188 00:09:21,520 --> 00:09:25,610 to the actual expert now and let Kurt Mattes jump in. 189 00:09:25,610 --> 00:09:28,530 And Kurt's gonna do a walkthrough of ARC for you guys 190 00:09:28,530 --> 00:09:30,770 and do some compare and contrast with Compliance Sheriff 191 00:09:30,770 --> 00:09:31,840 and then we'll go from there. 192 00:09:31,840 --> 00:09:33,263 So Kurt, over to you. 193 00:09:34,840 --> 00:09:35,920 - Thank you, Travis. 194 00:09:35,920 --> 00:09:38,620 Welcome to ARC, the Accessibility Resource Center, 195 00:09:38,620 --> 00:09:40,000 as soon as I get it up here for you. 196 00:09:40,000 --> 00:09:41,630 Here we go. 197 00:09:41,630 --> 00:09:43,210 This is the ARC on page. 198 00:09:43,210 --> 00:09:44,300 Let me log into ARC. 199 00:09:44,300 --> 00:09:46,080 ARC supports five core pillars 200 00:09:46,080 --> 00:09:48,540 of any successful accessibility program. 201 00:09:48,540 --> 00:09:50,910 It supports monitoring the automated testing 202 00:09:50,910 --> 00:09:54,280 in lower production regions that you're familiar with. 203 00:09:54,280 --> 00:09:56,210 It has help desk, which provides support 204 00:09:56,210 --> 00:09:58,973 from TPGi's experts in a very rapid fashion. 205 00:09:59,810 --> 00:10:01,590 It offers self-paced learning modules 206 00:10:01,590 --> 00:10:02,870 through our Tutor section, 207 00:10:02,870 --> 00:10:04,500 covering every aspect of information 208 00:10:04,500 --> 00:10:07,150 and communication technology accessibility. 209 00:10:07,150 --> 00:10:09,820 Provides a KnowledgeBase, a detailed problem descriptions 210 00:10:09,820 --> 00:10:12,030 and best in class solutions. 211 00:10:12,030 --> 00:10:14,530 And of course we house our TPGi engagements, 212 00:10:14,530 --> 00:10:16,570 the expert analysis work that's done to uncover 213 00:10:16,570 --> 00:10:18,193 what automated testing cannot. 214 00:10:19,310 --> 00:10:21,860 We use a feature called ARC Capture 215 00:10:21,860 --> 00:10:24,010 that allows us to bring results from manual testing 216 00:10:24,010 --> 00:10:27,380 into the same workspace, as I'll show you here in ARC, 217 00:10:27,380 --> 00:10:29,260 as the automated testing results. 218 00:10:29,260 --> 00:10:31,090 And so you get in one view, 219 00:10:31,090 --> 00:10:33,210 everything related to your site with respect 220 00:10:33,210 --> 00:10:34,840 to what can be found in an automated way 221 00:10:34,840 --> 00:10:36,890 as well as what we found in a manual way. 222 00:10:38,310 --> 00:10:42,503 Work spaces are the home for ARC's monitoring activities. 223 00:10:44,930 --> 00:10:48,332 In this particular account, we have several workspaces 224 00:10:48,332 --> 00:10:49,165 that have been built out. 225 00:10:49,165 --> 00:10:51,250 You can build as many workspaces as you wish. 226 00:10:51,250 --> 00:10:54,150 Workspaces allow you to organize 227 00:10:54,150 --> 00:10:58,290 your organization's assets accordingly 228 00:10:58,290 --> 00:11:02,490 with how your organization builds out those assets. 229 00:11:02,490 --> 00:11:04,670 So for example, the gentleman teams 230 00:11:04,670 --> 00:11:06,310 may build on more than one site, 231 00:11:06,310 --> 00:11:07,590 but only on certain parts. 232 00:11:07,590 --> 00:11:09,860 You can use workspaces to accommodate that 233 00:11:09,860 --> 00:11:13,770 so that they're only seeing what they are involved with. 234 00:11:13,770 --> 00:11:16,310 Workspaces can have multiple domains. 235 00:11:16,310 --> 00:11:18,600 In this workspace, we have one. 236 00:11:18,600 --> 00:11:21,570 It can have user flows, there's a user flow here, 237 00:11:21,570 --> 00:11:23,290 and it can have folders 238 00:11:23,290 --> 00:11:26,090 which are a way to contain findings 239 00:11:26,090 --> 00:11:28,540 from a defined part of the site. 240 00:11:28,540 --> 00:11:29,810 Again, that typically aligns 241 00:11:29,810 --> 00:11:31,540 with a particular stakeholder group. 242 00:11:31,540 --> 00:11:35,970 So for example, we can put all of the sports pages 243 00:11:35,970 --> 00:11:38,080 from The Guardian newspaper into one folder 244 00:11:38,080 --> 00:11:39,880 for those who are involved with maintaining 245 00:11:39,880 --> 00:11:42,620 that particular part of the online presence 246 00:11:42,620 --> 00:11:43,453 of The Guardian. 247 00:11:46,230 --> 00:11:49,320 A dashboard presents the details for each domain, 248 00:11:49,320 --> 00:11:51,210 user flow and folder. 249 00:11:51,210 --> 00:11:53,860 So ARC is built around a series of dashboards, 250 00:11:53,860 --> 00:11:57,440 and we take a look at the dashboard for the domain. 251 00:11:57,440 --> 00:11:59,483 We'll see that it contains high level details 252 00:11:59,483 --> 00:12:01,247 such as the total number of failures that were found 253 00:12:01,247 --> 00:12:03,097 and how many pages that were scanned. 254 00:12:04,670 --> 00:12:06,840 It gives you overall density score as well. 255 00:12:06,840 --> 00:12:09,240 And this is a key number. 256 00:12:09,240 --> 00:12:11,190 This number is calculated by somebody picking 257 00:12:11,190 --> 00:12:12,710 the number of failures divided by the number of pages 258 00:12:12,710 --> 00:12:13,543 that were scanned. 259 00:12:13,543 --> 00:12:16,060 We get an average number of failure per page. 260 00:12:16,060 --> 00:12:19,390 This number can be compared over time to itself, 261 00:12:19,390 --> 00:12:22,890 as long as it's calculated using the same rules engine. 262 00:12:22,890 --> 00:12:25,000 Likewise, it can be compared to other domains 263 00:12:25,000 --> 00:12:26,460 as long as the other domain was scanned 264 00:12:26,460 --> 00:12:28,270 using the same rules engine. 265 00:12:28,270 --> 00:12:30,520 And so this is a very helpful number 266 00:12:30,520 --> 00:12:33,240 to give you insight as to where your domain is at 267 00:12:33,240 --> 00:12:36,530 with respect to other domains that you may have 268 00:12:36,530 --> 00:12:38,530 or other domains throughout in the wild. 269 00:12:41,690 --> 00:12:44,720 In addition to having scheduled domains 270 00:12:44,720 --> 00:12:45,740 that you can see here in ARC, 271 00:12:45,740 --> 00:12:47,510 we can schedule our domains. 272 00:12:47,510 --> 00:12:49,940 There are settings that can be opened up to do that. 273 00:12:49,940 --> 00:12:51,670 We also have a scan now button, 274 00:12:51,670 --> 00:12:54,853 and this allows you to initiate a scan wherever you desire. 275 00:12:55,790 --> 00:12:57,280 What right now, we're looking at 276 00:12:57,280 --> 00:12:59,120 are the results from our most recent scan, 277 00:12:59,120 --> 00:13:01,870 which occurred back on the 21st of this month. 278 00:13:01,870 --> 00:13:04,980 In ARC, we can easily see results from the prior scan 279 00:13:04,980 --> 00:13:07,290 by using our selective scan feature. 280 00:13:07,290 --> 00:13:08,280 Where we can go in and pick 281 00:13:08,280 --> 00:13:09,840 any of the prior month scans that occurred, 282 00:13:09,840 --> 00:13:12,440 or if we're wearing weekly per week scans, 283 00:13:12,440 --> 00:13:14,520 and answer these and see the details 284 00:13:14,520 --> 00:13:16,320 for that particular scan right here. 285 00:13:19,110 --> 00:13:21,120 Our performance visualization graph, 286 00:13:21,120 --> 00:13:22,910 which was one of the demand dashboards 287 00:13:22,910 --> 00:13:26,250 and shows what kind of density score over time. 288 00:13:26,250 --> 00:13:28,920 Obviously something happened in the December release 289 00:13:28,920 --> 00:13:31,910 that significantly impacted the level of accessibility 290 00:13:31,910 --> 00:13:33,740 in a negative kind of way. 291 00:13:33,740 --> 00:13:36,240 And so this graph is very handy 292 00:13:36,240 --> 00:13:39,163 for quickly identifying where those things can occur. 293 00:13:42,170 --> 00:13:46,270 We also have the specific WCAG failures 294 00:13:46,270 --> 00:13:47,690 shown here in a pie chart, 295 00:13:47,690 --> 00:13:49,780 as well as the engine assertions 296 00:13:49,780 --> 00:13:51,433 that were found during the scan. 297 00:13:52,290 --> 00:13:55,580 All of the charts and graphs in ARC 298 00:13:55,580 --> 00:13:58,373 have related table views for accessibility. 299 00:14:00,710 --> 00:14:03,070 So that we are very focused on making sure 300 00:14:03,070 --> 00:14:04,323 that ARC is accessible. 301 00:14:06,270 --> 00:14:09,981 Each assertion, likewise, with these WCAG failures 302 00:14:09,981 --> 00:14:12,400 is a link that takes you out to a dashboard 303 00:14:12,400 --> 00:14:13,983 for that particular assertion. 304 00:14:14,920 --> 00:14:15,930 Successful periods, like I said, 305 00:14:15,930 --> 00:14:18,010 also have their own dashboard trains. 306 00:14:18,010 --> 00:14:19,337 And so we'll go out and look at 307 00:14:19,337 --> 00:14:21,930 a certain dashboard here in a moment. 308 00:14:21,930 --> 00:14:24,200 We also hear the performance by component section. 309 00:14:24,200 --> 00:14:26,170 Now, in this case component represents page 310 00:14:26,170 --> 00:14:28,110 if you're ever scanning of domain. 311 00:14:28,110 --> 00:14:30,950 If this was a user flow dashboard, 312 00:14:30,950 --> 00:14:33,140 component may be just a part of a page. 313 00:14:33,140 --> 00:14:35,200 And so we refer to them as components. 314 00:14:35,200 --> 00:14:37,600 And in this case component means full page. 315 00:14:37,600 --> 00:14:40,528 We're showing the top 15 here using pagination. 316 00:14:40,528 --> 00:14:43,530 This is a tough FTE, unless you don't wanna be on. 317 00:14:43,530 --> 00:14:45,240 This is the list of the pages 318 00:14:45,240 --> 00:14:47,040 that have the most failures on them. 319 00:14:48,190 --> 00:14:50,620 I find this to be incredibly handy 320 00:14:50,620 --> 00:14:52,400 for making sure that none of those pages 321 00:14:52,400 --> 00:14:54,560 that contain your most valuable content, 322 00:14:54,560 --> 00:14:57,180 the content that people want to get at the most, 323 00:14:57,180 --> 00:14:59,760 which is one of the three highest risk exposure factors 324 00:14:59,760 --> 00:15:03,240 you have is not listed here in the top 15. 325 00:15:03,240 --> 00:15:06,020 If it is, that's sort of a the house is on fire, 326 00:15:06,020 --> 00:15:07,920 go fix it problem. 327 00:15:07,920 --> 00:15:09,750 So this is a quick view to get that kind of information, 328 00:15:09,750 --> 00:15:11,100 and you can also go see all of them, 329 00:15:11,100 --> 00:15:13,050 but usually in the view all components. 330 00:15:15,852 --> 00:15:17,360 To assist in your decision making process 331 00:15:17,360 --> 00:15:19,580 in yet another way, ARC provides 332 00:15:19,580 --> 00:15:21,493 recommended remediation priorities. 333 00:15:22,890 --> 00:15:25,930 These providers are based upon the three success criteria 334 00:15:25,930 --> 00:15:27,580 with the most number of failures. 335 00:15:28,420 --> 00:15:31,520 Here's the second one of those factors. 336 00:15:31,520 --> 00:15:32,540 Is really important to consider 337 00:15:32,540 --> 00:15:35,720 for your risk exposure, and that is frequency of occurrence. 338 00:15:35,720 --> 00:15:39,970 And this part of the dataset addresses exactly that. 339 00:15:39,970 --> 00:15:42,330 So, by choosing the success criteria 340 00:15:42,330 --> 00:15:43,480 with the most violations 341 00:15:43,480 --> 00:15:45,630 and associating the related success criteria, 342 00:15:45,630 --> 00:15:48,660 oh sorry, related assertions with them, 343 00:15:48,660 --> 00:15:50,220 we help you focus it on the assertions 344 00:15:50,220 --> 00:15:52,203 that you should probably tend to first. 345 00:15:53,410 --> 00:15:55,220 Go on top of that with your third 346 00:15:55,220 --> 00:15:58,030 most important risk factor that you should consider. 347 00:15:58,030 --> 00:16:00,560 And that is, end user impact. 348 00:16:00,560 --> 00:16:03,130 There may be an assertion that has a higher end user impact 349 00:16:03,130 --> 00:16:05,980 such as a showstopper or a particular type 350 00:16:05,980 --> 00:16:07,120 of disability group. 351 00:16:07,120 --> 00:16:10,350 And that may be something that you would wanna attend to 352 00:16:10,350 --> 00:16:12,660 more so ahead of these. 353 00:16:12,660 --> 00:16:17,403 So all information that is aimed to provide you 354 00:16:18,270 --> 00:16:20,240 the ability to make the most informed decision, 355 00:16:20,240 --> 00:16:21,490 you can make with respect to how 356 00:16:21,490 --> 00:16:24,303 you're gonna go about remediating your existing problems. 357 00:16:25,950 --> 00:16:26,783 Excuse me. 358 00:16:30,190 --> 00:16:33,110 So lastly, on the main page, 359 00:16:33,110 --> 00:16:35,770 each assertion that ARC found is listed. 360 00:16:35,770 --> 00:16:37,870 We're also seeing all of the alerts that ARC found. 361 00:16:37,870 --> 00:16:39,890 So these are assertions as well, 362 00:16:39,890 --> 00:16:43,010 but we're not positive as is the case 363 00:16:43,010 --> 00:16:44,508 with any automated testing tool 364 00:16:44,508 --> 00:16:45,640 that this was really a problem. 365 00:16:45,640 --> 00:16:46,890 A human has to go out and test it. 366 00:16:46,890 --> 00:16:49,090 So we list those here in this table as well. 367 00:16:50,290 --> 00:16:52,900 And so you can also see that we provide 368 00:16:52,900 --> 00:16:54,530 the particular success per criteria 369 00:16:54,530 --> 00:16:56,100 that's related to the assertion, 370 00:16:56,100 --> 00:16:58,390 as well as what checkpoint level 371 00:16:58,390 --> 00:16:59,790 the assertion is related to. 372 00:17:00,970 --> 00:17:03,813 This data is all exportable in CSV format as well. 373 00:17:09,510 --> 00:17:11,850 Nice, let's take a look at our insertion expert now. 374 00:17:11,850 --> 00:17:13,177 This is where we get our this first assertion here 375 00:17:13,177 --> 00:17:15,900 our SVG without area labeled by. 376 00:17:15,900 --> 00:17:17,590 So here on the assertion dashboard, 377 00:17:17,590 --> 00:17:19,160 we get a density trend as well 378 00:17:19,160 --> 00:17:20,290 for this particular assertion. 379 00:17:20,290 --> 00:17:21,520 It's pretty much been flat lines 380 00:17:21,520 --> 00:17:23,080 since the beginning of the year. 381 00:17:23,080 --> 00:17:24,890 Hasn't improved, hasn't gotten worse. 382 00:17:24,890 --> 00:17:25,993 So we're steady state. 383 00:17:29,170 --> 00:17:31,210 So we also give you hear more detail 384 00:17:31,210 --> 00:17:33,340 about the particular assertion, 385 00:17:33,340 --> 00:17:35,363 brief explanation of what it's about, 386 00:17:36,410 --> 00:17:37,970 what success criteria is related to, 387 00:17:37,970 --> 00:17:40,890 link out to the WCAG success criteria 388 00:17:40,890 --> 00:17:42,733 in the WCAG standard, 389 00:17:43,760 --> 00:17:48,440 what engine was used to find this assertion, 390 00:17:48,440 --> 00:17:49,850 as well as our key. 391 00:17:49,850 --> 00:17:52,380 But we also provide KnowledgeBase resources here. 392 00:17:52,380 --> 00:17:57,000 And so KnowledgeBase resources are any articles 393 00:17:57,000 --> 00:17:58,290 that's in the KnowledgeBase that are related 394 00:17:58,290 --> 00:18:00,190 to this particular assertion. 395 00:18:00,190 --> 00:18:01,080 They'll be listed here, 396 00:18:01,080 --> 00:18:02,760 and this is a right to you format. 397 00:18:02,760 --> 00:18:05,200 Whereas we bring that data right from our KnowledgeBase 398 00:18:05,200 --> 00:18:06,140 right here to you, 399 00:18:06,140 --> 00:18:08,320 and it provides that detailed explanation 400 00:18:08,320 --> 00:18:09,230 about what the problem is 401 00:18:09,230 --> 00:18:12,041 as well as what our recommended solutions are. 402 00:18:12,041 --> 00:18:12,900 This is a really handy feature 403 00:18:12,900 --> 00:18:15,740 that a lot of people make use of 404 00:18:15,740 --> 00:18:18,540 while they're here working on this particular assertion. 405 00:18:21,940 --> 00:18:25,530 So each, here on our page listing, 406 00:18:25,530 --> 00:18:27,480 this is the listing of all pages, by the way, 407 00:18:27,480 --> 00:18:30,370 that have this particular assertion that was found on it. 408 00:18:30,370 --> 00:18:32,020 And each of these are our link 409 00:18:32,020 --> 00:18:34,144 that goes out to the page dashboard. 410 00:18:34,144 --> 00:18:36,500 I would say around a series of dashboards. 411 00:18:36,500 --> 00:18:37,840 Page dashboard looks an awful lot 412 00:18:37,840 --> 00:18:39,520 like the main dashboard. 413 00:18:39,520 --> 00:18:41,210 Has a high level of details 414 00:18:41,210 --> 00:18:44,340 and has your favorite density graph over time, 415 00:18:44,340 --> 00:18:45,840 highlighting a different problem 416 00:18:45,840 --> 00:18:47,580 that occurred in September of last year 417 00:18:47,580 --> 00:18:49,870 for this particular assertion. 418 00:18:49,870 --> 00:18:53,203 Again, your failures and your assertions are here as well. 419 00:18:55,250 --> 00:18:57,210 And then priorities with respect 420 00:18:57,210 --> 00:18:58,810 to this particular assertion 421 00:18:58,810 --> 00:19:01,990 and then a listing of all of the assertions 422 00:19:01,990 --> 00:19:03,960 on this particular page. 423 00:19:03,960 --> 00:19:06,010 If we select the one that we were looking at, 424 00:19:06,010 --> 00:19:09,410 this particular assertion, we'll see that ARC will show you 425 00:19:09,410 --> 00:19:11,710 the lines of code on this page 426 00:19:11,710 --> 00:19:13,850 where this assertion was found. 427 00:19:13,850 --> 00:19:16,070 This helps you put in context 428 00:19:16,070 --> 00:19:18,493 where the issue has been located by ARC. 429 00:19:22,030 --> 00:19:23,543 We went back to our workspace. 430 00:19:24,530 --> 00:19:26,790 Let's take a look at ARC user flow capabilities 431 00:19:26,790 --> 00:19:27,623 for a moment. 432 00:19:31,783 --> 00:19:35,380 Once I get domain, user flows up in dashboard too. 433 00:19:35,380 --> 00:19:36,670 And so this is the user flow called 434 00:19:36,670 --> 00:19:39,100 guardian.com accessibility review. 435 00:19:39,100 --> 00:19:41,350 So this is the dashboard for it. 436 00:19:41,350 --> 00:19:42,570 You'll notice here that we're talking 437 00:19:42,570 --> 00:19:43,900 about eight components scan, 438 00:19:43,900 --> 00:19:47,100 as opposed to the number of pages that were scanned. 439 00:19:47,100 --> 00:19:49,860 So really the key difference here lies 440 00:19:49,860 --> 00:19:52,710 in how ARC goes about gathering the data. 441 00:19:52,710 --> 00:19:55,660 When we're running a mock monitoring run, 442 00:19:55,660 --> 00:20:00,230 it is defined by includes, excludes, domains 443 00:20:00,230 --> 00:20:03,760 variety of different key attributes 444 00:20:03,760 --> 00:20:08,070 that sort of contain the automated crawler 445 00:20:08,070 --> 00:20:11,340 so that it doesn't just run amuck and go anywhere. 446 00:20:11,340 --> 00:20:13,370 And so, but it does run on its own. 447 00:20:13,370 --> 00:20:14,870 I mean, it's sort of a timeless. 448 00:20:14,870 --> 00:20:17,440 End user flow, there's autonomy. 449 00:20:17,440 --> 00:20:19,720 This is strictly scripted. 450 00:20:19,720 --> 00:20:22,000 So the ARC will do exactly what it's told to do 451 00:20:22,000 --> 00:20:24,150 as we go through the script. 452 00:20:24,150 --> 00:20:25,930 You have very similar sets of scripts available 453 00:20:25,930 --> 00:20:27,483 in Compliance Sheriff now. 454 00:20:31,470 --> 00:20:34,040 If I show you how you go about doing this in ARC, 455 00:20:34,040 --> 00:20:35,810 your configuration screen, 456 00:20:35,810 --> 00:20:39,240 high-level details about this particular user flow. 457 00:20:39,240 --> 00:20:42,090 But in here you can see the user flow skip steps. 458 00:20:42,090 --> 00:20:45,340 That this is done by using an XML format, 459 00:20:45,340 --> 00:20:49,070 it's Selenium Script, and then inserting instructions 460 00:20:49,070 --> 00:20:51,893 for ARC where to go about analyzing the asset. 461 00:20:53,050 --> 00:20:54,710 And so with these steps, 462 00:20:54,710 --> 00:20:58,250 ARC can be instructed to go through a part of a site 463 00:20:58,250 --> 00:21:00,290 just the same way usually we go through 464 00:21:00,290 --> 00:21:02,450 entering values where values need to be entered, 465 00:21:02,450 --> 00:21:04,023 clicking on buttons and links, 466 00:21:05,040 --> 00:21:07,710 every aspect of what a user would do 467 00:21:07,710 --> 00:21:11,450 and being instructed to give up points 468 00:21:11,450 --> 00:21:13,280 actually analyze what's there on a page 469 00:21:13,280 --> 00:21:15,220 so we can change things on the page as well, 470 00:21:15,220 --> 00:21:16,303 and analyze those. 471 00:21:19,040 --> 00:21:21,960 So each one of these analyzed asset commands 472 00:21:21,960 --> 00:21:24,800 produces one of the components. 473 00:21:24,800 --> 00:21:26,120 And so here's the list of components 474 00:21:26,120 --> 00:21:28,870 that are created as a result of running this user flow. 475 00:21:30,100 --> 00:21:31,260 The first few components here 476 00:21:31,260 --> 00:21:34,060 are instructed to analyze the full page. 477 00:21:34,060 --> 00:21:36,760 So they're pretty much just like a normal monitoring flow, 478 00:21:36,760 --> 00:21:38,310 but then we're gonna come down to this one. 479 00:21:38,310 --> 00:21:39,580 It's the same form. 480 00:21:39,580 --> 00:21:41,200 And you'll notice that the locator is not, 481 00:21:41,200 --> 00:21:42,660 just the HTML page. 482 00:21:42,660 --> 00:21:45,413 In fact, it is a within the ID main section, 483 00:21:46,270 --> 00:21:49,380 content section of the page that this is located. 484 00:21:49,380 --> 00:21:52,713 We saw ARC just to scan this particular part of this page. 485 00:21:53,769 --> 00:21:54,602 And if we click on that, 486 00:21:54,602 --> 00:21:56,360 we'll see that here's our screenshot 487 00:21:56,360 --> 00:21:57,600 of what was analyzed. 488 00:21:57,600 --> 00:21:59,900 And I have the details here about how we got there 489 00:21:59,900 --> 00:22:03,100 and the code, the actual HTML code that was used 490 00:22:03,100 --> 00:22:05,300 for ARC to perform this particular analysis. 491 00:22:06,210 --> 00:22:08,090 Very handy for people who are trying to debug 492 00:22:08,090 --> 00:22:10,460 and figure out how to go about solving problems. 493 00:22:10,460 --> 00:22:13,210 So this level of detail is available right here in ARC. 494 00:22:14,540 --> 00:22:16,520 There are far more features available in ARC 495 00:22:16,520 --> 00:22:18,670 that I'm not gonna be able to present 496 00:22:18,670 --> 00:22:19,530 during the amount of time allotted 497 00:22:19,530 --> 00:22:21,540 for this particular part of our webinar. 498 00:22:21,540 --> 00:22:22,840 But I do wanna call your attention 499 00:22:22,840 --> 00:22:25,280 that we do have the KnowledgeBase. 500 00:22:25,280 --> 00:22:27,740 I showed you before how the articles can come to you 501 00:22:27,740 --> 00:22:30,727 while you're working through details on domain dashboards 502 00:22:30,727 --> 00:22:32,430 and other dashboards. 503 00:22:32,430 --> 00:22:34,640 But we haven't been seven modules as well. 504 00:22:34,640 --> 00:22:37,240 So you can go in and simply explore and learn on your own 505 00:22:37,240 --> 00:22:39,890 using the KnowledgeBased modules. 506 00:22:39,890 --> 00:22:41,690 We also have an ARC user guide here. 507 00:22:42,690 --> 00:22:44,740 Very handy, very helpful. 508 00:22:44,740 --> 00:22:47,840 You'll find that this is extremely detailed. 509 00:22:47,840 --> 00:22:50,410 I'm a developer by trade. 510 00:22:50,410 --> 00:22:52,580 You have to go over field manuals. 511 00:22:52,580 --> 00:22:55,750 If you don't, I'll tell you, we don't like 'em. 512 00:22:55,750 --> 00:22:56,750 This is a good one. 513 00:22:56,750 --> 00:22:58,350 This is really worth your time. 514 00:22:58,350 --> 00:22:59,183 There's a lot of effort that was put into this, 515 00:22:59,183 --> 00:23:02,310 and it is maintained, updated regularly. 516 00:23:02,310 --> 00:23:03,790 And it will really help you understand 517 00:23:03,790 --> 00:23:04,840 how to use many of the features 518 00:23:04,840 --> 00:23:06,340 that are available within ARC. 519 00:23:08,821 --> 00:23:09,810 Some of the other key features 520 00:23:09,810 --> 00:23:11,290 that we just can't get into today 521 00:23:11,290 --> 00:23:13,490 are how actions can be controlled within ARC 522 00:23:15,212 --> 00:23:17,640 and other dashboards, such as the engagement dashboards 523 00:23:17,640 --> 00:23:19,300 for our manual assessments 524 00:23:19,300 --> 00:23:21,450 and dashboards related to success criteria. 525 00:23:23,790 --> 00:23:26,640 Firstly, as I said, all that's gonna be available 526 00:23:26,640 --> 00:23:28,440 to you right here in the user guide. 527 00:23:29,910 --> 00:23:34,203 So returning to our regular presentation, 528 00:23:36,140 --> 00:23:38,720 as we've seen, there's a certain amount of information 529 00:23:38,720 --> 00:23:41,120 that is necessary for every website crawler 530 00:23:41,120 --> 00:23:43,410 to effectively scan a site. 531 00:23:43,410 --> 00:23:47,410 You have those details available in Compliance Sheriff. 532 00:23:47,410 --> 00:23:48,790 That's where you've added them. 533 00:23:48,790 --> 00:23:50,160 We're gonna take a look at those details now, 534 00:23:50,160 --> 00:23:52,420 some of 'em, to show you how they transition 535 00:23:52,420 --> 00:23:54,363 over into ARC for you. 536 00:23:56,959 --> 00:23:57,820 And you're going to hear a new voice. 537 00:23:57,820 --> 00:23:59,530 Brenton, your turn. 538 00:23:59,530 --> 00:24:02,402 - Yeah, Brenton West jumping back in here. 539 00:24:02,402 --> 00:24:05,677 And so over the past weeks, months, 540 00:24:05,677 --> 00:24:10,677 Kurt and I did some exercises and we ran scans 541 00:24:10,770 --> 00:24:13,880 or audits against common web properties 542 00:24:13,880 --> 00:24:17,680 so that we could really kind of create this comparison 543 00:24:17,680 --> 00:24:20,260 of features, functions between the two solutions. 544 00:24:20,260 --> 00:24:22,170 So that's what we'll see coming up here 545 00:24:22,170 --> 00:24:23,620 in the next set of slides. 546 00:24:23,620 --> 00:24:27,460 And just setting the table, here is the view 547 00:24:27,460 --> 00:24:32,030 that most of our Compliance Sheriff users are familiar with. 548 00:24:32,030 --> 00:24:35,660 This is the area where you would define scans, 549 00:24:35,660 --> 00:24:39,150 basically tell our solution what you want to test, 550 00:24:39,150 --> 00:24:40,862 how you want it to be tested through 551 00:24:40,862 --> 00:24:44,070 the selection of checkpoints or filters 552 00:24:44,070 --> 00:24:46,360 to control where the scan goes, 553 00:24:46,360 --> 00:24:49,203 even the clarification of transactions. 554 00:24:50,070 --> 00:24:54,550 So we'll be referring to this full screen a few times here, 555 00:24:54,550 --> 00:24:57,500 as we compare where these features and functions 556 00:24:57,500 --> 00:25:00,200 are found in ARC, now that you've seen 557 00:25:00,200 --> 00:25:02,903 a high level overview that care providers. 558 00:25:04,166 --> 00:25:04,999 Sorry, Kurt. 559 00:25:06,156 --> 00:25:09,390 - And so in our information for domain scanners provided 560 00:25:09,390 --> 00:25:12,340 on the domain configuration screen, what you're seeing here. 561 00:25:12,340 --> 00:25:14,930 And likewise, we're gonna slice and dice this 562 00:25:14,930 --> 00:25:16,650 as we go through the rest of this section 563 00:25:16,650 --> 00:25:18,810 of our presentation to help you understand 564 00:25:18,810 --> 00:25:20,407 how the information that you're very familiar with 565 00:25:20,407 --> 00:25:22,900 and how you see it in Compliance Sheriff 566 00:25:22,900 --> 00:25:25,193 translates directly over into ARC. 567 00:25:28,750 --> 00:25:29,700 Brenton. 568 00:25:29,700 --> 00:25:31,214 - Yeah, the first area here 569 00:25:31,214 --> 00:25:35,850 is what we're calling Compliance Sheriff Base URL. 570 00:25:35,850 --> 00:25:38,940 This is where you define the URL 571 00:25:38,940 --> 00:25:41,930 and domain of the website you're targeting 572 00:25:41,930 --> 00:25:43,630 your assessments against. 573 00:25:43,630 --> 00:25:46,350 Obviously by default in Compliance Sheriff, 574 00:25:46,350 --> 00:25:49,160 our scan engine kinda stays inside this domain 575 00:25:49,160 --> 00:25:52,500 and doesn't transition outside of it 576 00:25:52,500 --> 00:25:55,800 unless you performs more advanced scan criteria, 577 00:25:55,800 --> 00:25:58,073 which is very comparable in ARC. 578 00:26:00,100 --> 00:26:01,986 - The link through relation streamline resolved 579 00:26:01,986 --> 00:26:02,819 before the very top. 580 00:26:02,819 --> 00:26:04,590 We have a design detail section 581 00:26:04,590 --> 00:26:08,243 and that's where your URL for the domain will be located. 582 00:26:09,560 --> 00:26:12,040 Once a URL is established for domain, it can't be changed. 583 00:26:12,040 --> 00:26:13,440 It defines where the domain is, 584 00:26:13,440 --> 00:26:15,140 but the name of the domain can be. 585 00:26:21,860 --> 00:26:22,693 Here we go. 586 00:26:23,784 --> 00:26:26,730 - So then, in a Compliance Sheriff scan definition, 587 00:26:26,730 --> 00:26:30,730 we have the concept of exclusion and filters. 588 00:26:30,730 --> 00:26:33,380 So that as Compliance Sheriff is crawling 589 00:26:33,380 --> 00:26:36,320 through the web property in the URL string, 590 00:26:36,320 --> 00:26:41,120 if these terms or phrases are found telling the engine, 591 00:26:41,120 --> 00:26:44,290 no worries, we don't want to be assessing these pages. 592 00:26:44,290 --> 00:26:47,040 And there's comparable capabilities, of course, in ARC. 593 00:26:50,160 --> 00:26:52,900 - Same concept, slightly different execution. 594 00:26:52,900 --> 00:26:55,480 ARC uses exclusion patterns 595 00:26:55,480 --> 00:26:56,710 that essentially do the same thing. 596 00:26:56,710 --> 00:26:59,840 They instruct ARC to stay away from any URL string 597 00:27:00,710 --> 00:27:02,487 that matches this pattern. 598 00:27:06,210 --> 00:27:09,970 - And then the inverse, if you want to maybe stay focused 599 00:27:09,970 --> 00:27:13,040 on a certain area of your web asset 600 00:27:13,040 --> 00:27:17,260 or define exactly what section of the site 601 00:27:17,260 --> 00:27:19,440 you want to stay in. 602 00:27:19,440 --> 00:27:21,900 In Compliance Sheriff, we use filters 603 00:27:21,900 --> 00:27:23,970 that include URL matching filters. 604 00:27:23,970 --> 00:27:26,933 And then in ARC, again, comparable capability. 605 00:27:28,580 --> 00:27:30,300 - We use seed URLs. 606 00:27:30,300 --> 00:27:33,600 Seed URLs, the root seed URL is the root for the domain. 607 00:27:33,600 --> 00:27:35,220 It typically is one of the starting places 608 00:27:35,220 --> 00:27:37,380 that you wanna scan to start, 609 00:27:37,380 --> 00:27:40,070 although we can avoid that if necessary. 610 00:27:40,070 --> 00:27:41,830 And then we can add in other seed URLs 611 00:27:41,830 --> 00:27:44,550 to have ARC scan other parts of the site 612 00:27:44,550 --> 00:27:46,900 that you really wanna make sure ARC can get to. 613 00:27:48,620 --> 00:27:51,950 ARC also uses a concept called folders. 614 00:27:51,950 --> 00:27:56,010 And so folders are a way to represent 615 00:27:56,010 --> 00:27:57,260 just a piece of the site. 616 00:27:58,490 --> 00:28:01,210 Folders also have their own seed URLs. 617 00:28:01,210 --> 00:28:04,850 And so you can, within a folder establish 618 00:28:04,850 --> 00:28:06,712 a previous a seed URLs, 619 00:28:06,712 --> 00:28:07,940 that will make sure that like using 620 00:28:07,940 --> 00:28:09,860 our Guardian sports section before, 621 00:28:09,860 --> 00:28:12,360 all of the information that ARC gathers 622 00:28:12,360 --> 00:28:15,020 about that particular session is organized 623 00:28:15,020 --> 00:28:18,580 into a single folder and that folder has a dashboard 624 00:28:18,580 --> 00:28:20,200 just like the main dashboard, 625 00:28:20,200 --> 00:28:23,500 and the list of issues and top priorities 626 00:28:23,500 --> 00:28:25,330 so that particular stakeholder group 627 00:28:25,330 --> 00:28:27,400 that's interested in just that area 628 00:28:27,400 --> 00:28:29,270 can see exactly what they're interested in 629 00:28:29,270 --> 00:28:31,950 and not encounter any white noise 630 00:28:31,950 --> 00:28:34,500 from all the other information that ARC can gather. 631 00:28:37,550 --> 00:28:38,383 - Yep, exactly. 632 00:28:39,352 --> 00:28:41,940 Then also of course, in a Compliance Sheriff skin, 633 00:28:41,940 --> 00:28:46,080 you define, what do you want to be testing your sites again? 634 00:28:46,080 --> 00:28:49,370 And so selecting checkpoint groups 635 00:28:49,370 --> 00:28:53,237 would be where you actually identify, for example, 636 00:28:53,237 --> 00:28:55,610 the WCAG success criteria is a standard 637 00:28:55,610 --> 00:28:56,700 you want to test against? 638 00:28:56,700 --> 00:28:59,380 And of course, that common functionality 639 00:28:59,380 --> 00:29:00,880 is also available over in ARC. 640 00:29:02,700 --> 00:29:05,391 - Yeah, in ARC we set accessibility standards. 641 00:29:05,391 --> 00:29:07,410 We set these accessibility standards 642 00:29:07,410 --> 00:29:09,500 at the account level, that's the default. 643 00:29:09,500 --> 00:29:11,840 However, at the domain level, 644 00:29:11,840 --> 00:29:14,030 the standards can be changed. 645 00:29:14,030 --> 00:29:15,550 So we can say that an account 646 00:29:15,550 --> 00:29:17,610 why we wanna test against WCAG 2.1, 647 00:29:17,610 --> 00:29:19,010 but however, for this particular domain, 648 00:29:19,010 --> 00:29:20,673 we're still testing WCAG 2.0. 649 00:29:21,740 --> 00:29:24,840 And so that flexibility just within ARC. 650 00:29:24,840 --> 00:29:26,928 You can also change it in real time 651 00:29:26,928 --> 00:29:30,420 on one of ARC's dashboards between these two standards. 652 00:29:30,420 --> 00:29:33,900 ARC actually does to the analysis against both standards, 653 00:29:33,900 --> 00:29:35,763 whenever it does any kind of scanning. 654 00:29:38,617 --> 00:29:39,450 - Sorry. 655 00:29:39,450 --> 00:29:43,210 And then the last in this series 656 00:29:43,210 --> 00:29:45,220 is around page limits and levels. 657 00:29:45,220 --> 00:29:47,900 So this is controlling as Compliance Sheriff crawls 658 00:29:47,900 --> 00:29:52,220 from the site, how deep into the site do you want to crawl? 659 00:29:52,220 --> 00:29:55,350 And if there's a cap on the page totals 660 00:29:55,350 --> 00:29:57,060 that you want to stop after, 661 00:29:57,060 --> 00:29:58,290 maybe you just need a sampling 662 00:29:58,290 --> 00:30:01,350 versus scanning the entire web asset. 663 00:30:01,350 --> 00:30:02,640 And done slightly differently, 664 00:30:02,640 --> 00:30:05,653 but certainly capable over in ARC as well. 665 00:30:07,420 --> 00:30:10,090 - Here's the core crawl depth and max URLs, 666 00:30:10,090 --> 00:30:12,480 because of course limits really do matter. 667 00:30:12,480 --> 00:30:13,560 One of these tools needs to be told 668 00:30:13,560 --> 00:30:15,170 where to stop at some point. 669 00:30:15,170 --> 00:30:17,690 And so we use crawl depth and max URL settings 670 00:30:17,690 --> 00:30:19,240 to accomplish that here in ARC. 671 00:30:20,737 --> 00:30:23,530 And so those are some of the basic domain configurations 672 00:30:23,530 --> 00:30:25,700 that are identical across both tools 673 00:30:25,700 --> 00:30:28,020 and how we go about implementing them. 674 00:30:28,020 --> 00:30:30,270 But now let's turn to some of the more valuable features 675 00:30:30,270 --> 00:30:32,873 and functionality offered on both platforms. 676 00:30:34,060 --> 00:30:35,840 So when logging in is required, 677 00:30:35,840 --> 00:30:38,660 both platforms can actually execute an authentication script 678 00:30:38,660 --> 00:30:40,800 on the domain prior to scanning it. 679 00:30:40,800 --> 00:30:42,950 So both have that same capability. 680 00:30:42,950 --> 00:30:45,470 In ARC, it's easily exposed. 681 00:30:45,470 --> 00:30:47,180 It looks much like the user flow scripts 682 00:30:47,180 --> 00:30:48,880 I was showing you before. 683 00:30:48,880 --> 00:30:52,120 And as we know, oftentimes the credentials change, 684 00:30:52,120 --> 00:30:54,270 especially if we're working in lower regions. 685 00:30:54,270 --> 00:30:56,160 It's very easy to enter ARC instantly, 686 00:30:56,160 --> 00:30:58,050 add in the different value, the new value, 687 00:30:58,050 --> 00:30:59,520 take out the old value 688 00:30:59,520 --> 00:31:02,263 and continue scanning without interruption. 689 00:31:05,420 --> 00:31:07,840 Because actually the scripts representing the journey 690 00:31:07,840 --> 00:31:09,200 and actions the user might take 691 00:31:09,200 --> 00:31:10,990 can also be consumed by both applications. 692 00:31:10,990 --> 00:31:13,300 Again, these are user flows within ARC. 693 00:31:13,300 --> 00:31:15,300 The assets are analyzed along the journey 694 00:31:15,300 --> 00:31:16,450 to produce a single view 695 00:31:16,450 --> 00:31:18,450 of the journey's level of accessibility. 696 00:31:19,590 --> 00:31:21,310 The essence you get bumps in ARC 697 00:31:21,310 --> 00:31:23,290 is instructed to analyze can be as specific 698 00:31:23,290 --> 00:31:25,160 as a single select list on a page 699 00:31:25,160 --> 00:31:27,240 as I demonstrated earlier, 700 00:31:27,240 --> 00:31:32,180 or as this defined section of the page header, for example, 701 00:31:32,180 --> 00:31:34,080 or could of course be the entire page. 702 00:31:37,780 --> 00:31:40,280 And both tools have scheduled and on demand scans. 703 00:31:41,310 --> 00:31:43,210 This is really important to understand 704 00:31:43,210 --> 00:31:46,220 how you're gonna control when the tool 705 00:31:46,220 --> 00:31:48,420 is gonna actually perform its analysis work. 706 00:31:50,465 --> 00:31:51,620 And so that's the way it looks for you 707 00:31:51,620 --> 00:31:52,800 that you're familiar within Compliance Sheriff. 708 00:31:52,800 --> 00:31:56,530 And this is what we see when we go to this in ARC. 709 00:31:56,530 --> 00:31:58,900 Where we schedule our scans and under our action settings, 710 00:31:58,900 --> 00:32:01,128 we can change what this is gonna be. 711 00:32:01,128 --> 00:32:03,860 Our schedule scans, you can run anything 712 00:32:03,860 --> 00:32:07,470 from daily to weekly, to every other week 713 00:32:07,470 --> 00:32:10,093 for nightly to monthly in ARC, 714 00:32:11,055 --> 00:32:13,350 and you can set the next scan and time. 715 00:32:13,350 --> 00:32:15,110 Time, because important factor 716 00:32:15,110 --> 00:32:16,694 when you're in lower regions, when you know 717 00:32:16,694 --> 00:32:18,370 a certain release is gonna take place 718 00:32:18,370 --> 00:32:19,203 and you actually wanna avoid 'em. 719 00:32:19,203 --> 00:32:21,110 So you time you scan out to make sure 720 00:32:21,110 --> 00:32:23,290 that it's not gonna occur when a lease is occurring. 721 00:32:23,290 --> 00:32:25,353 And then of course, there's a scan down button. 722 00:32:30,160 --> 00:32:33,583 Both those later export results. 723 00:32:35,040 --> 00:32:37,560 When desired, ARC dashboards and folders 724 00:32:37,560 --> 00:32:40,224 provide means to export a subset 725 00:32:40,224 --> 00:32:43,320 of the full set of data collected during a scan. 726 00:32:43,320 --> 00:32:45,440 And so you're not necessarily seeing all of it 727 00:32:46,550 --> 00:32:48,310 when you do your download. 728 00:32:48,310 --> 00:32:49,830 For example, just a page. 729 00:32:49,830 --> 00:32:52,030 All users for a single page can be exported. 730 00:32:53,120 --> 00:32:56,520 Likewise, section on the site as viewed on a dashboard, 731 00:32:56,520 --> 00:32:58,870 a page, or it can be exported. 732 00:32:58,870 --> 00:33:01,893 So again, new folders, that content can be exported. 733 00:33:03,530 --> 00:33:05,770 Both tools provide a way to data filter. 734 00:33:05,770 --> 00:33:08,870 On Compliance Sheriff, that's performed mostly 735 00:33:08,870 --> 00:33:10,280 on your custom views screen 736 00:33:11,140 --> 00:33:14,950 by selecting within this particular area 737 00:33:14,950 --> 00:33:18,320 what you wanna scan and how you want to present here, 738 00:33:18,320 --> 00:33:20,000 what types of tables you want 739 00:33:20,000 --> 00:33:22,343 what data points you want on your tables and so on. 740 00:33:23,477 --> 00:33:25,660 Again, ARC uses a variety of dashboards 741 00:33:25,660 --> 00:33:28,350 to represent the data for each WCAG success right here, 742 00:33:28,350 --> 00:33:29,500 and use assertion ARC finds 743 00:33:29,500 --> 00:33:31,970 as well as for pages and user flows. 744 00:33:31,970 --> 00:33:34,610 So all that is handled simply by visiting 745 00:33:34,610 --> 00:33:36,360 a series of different dashboards. 746 00:33:36,360 --> 00:33:38,090 A dashboard is also provided for the folders 747 00:33:38,090 --> 00:33:39,043 as I pointed out. 748 00:33:40,080 --> 00:33:42,340 And so that one becomes really important again, 749 00:33:42,340 --> 00:33:44,940 to, especially if you're working on a large site 750 00:33:44,940 --> 00:33:46,590 to keep just that portion of the site 751 00:33:46,590 --> 00:33:48,030 isolated away from the rest 752 00:33:48,030 --> 00:33:50,233 to make it easier for those folks to work on. 753 00:33:53,430 --> 00:33:57,650 ARC provides contextual issue identification in real time 754 00:33:57,650 --> 00:34:00,460 on a page using the ARC toolkit, 755 00:34:00,460 --> 00:34:04,150 committing your product to the ARC platform itself. 756 00:34:04,150 --> 00:34:07,060 And as you can see, it helps to identify 757 00:34:07,060 --> 00:34:09,810 lots of aspects about what's going on on a page. 758 00:34:09,810 --> 00:34:11,550 Where you can see things are in black, 759 00:34:11,550 --> 00:34:13,090 this is actually pretty good. 760 00:34:13,090 --> 00:34:15,490 Where you see things in red, well, that's a problem. 761 00:34:15,490 --> 00:34:16,837 We're missing area labels here, 762 00:34:16,837 --> 00:34:18,523 and we have no label at all here. 763 00:34:19,480 --> 00:34:21,400 And so it's easy to see contextually 764 00:34:21,400 --> 00:34:22,823 using the ARC toolkit. 765 00:34:24,560 --> 00:34:26,580 And API access. 766 00:34:26,580 --> 00:34:28,710 And I've talked to Brenton and Compliance Sheriff 767 00:34:28,710 --> 00:34:31,350 has offered API access to you. 768 00:34:31,350 --> 00:34:32,183 I don't know if any of you 769 00:34:32,183 --> 00:34:33,870 are taking advantage of it or not. 770 00:34:33,870 --> 00:34:35,400 We also offer it via ARC, 771 00:34:35,400 --> 00:34:38,830 and we're expanding this capability all the time. 772 00:34:38,830 --> 00:34:41,010 It's pretty robust as it is. 773 00:34:41,010 --> 00:34:43,320 And for anybody who's familiar with how APIs work, 774 00:34:43,320 --> 00:34:45,810 this will give you the ability to integrate 775 00:34:45,810 --> 00:34:49,190 the power of ARC directly into your continuous integration, 776 00:34:49,190 --> 00:34:51,070 continuous development pipelines, 777 00:34:51,070 --> 00:34:53,940 or directly to developer desktops, 778 00:34:53,940 --> 00:34:56,330 or you can create your own dashboards 779 00:34:56,330 --> 00:34:58,633 and pull the data in just like we do. 780 00:34:59,600 --> 00:35:01,800 ARC is using ARC CPIs, obviously, 781 00:35:01,800 --> 00:35:04,670 to represent what I showed you in that demo. 782 00:35:04,670 --> 00:35:06,730 You can use them likewise, to build your own dashboards 783 00:35:06,730 --> 00:35:09,403 to represent data however you best see fit. 784 00:35:10,510 --> 00:35:13,000 So to recap, basic feature set 785 00:35:14,390 --> 00:35:16,970 and strong features of both tools. 786 00:35:16,970 --> 00:35:18,540 You have authentication flow capabilities, 787 00:35:18,540 --> 00:35:21,960 transaction strips for basically behaving 788 00:35:21,960 --> 00:35:23,710 just like a user would. 789 00:35:23,710 --> 00:35:25,400 Scheduled on demand scans. 790 00:35:25,400 --> 00:35:27,170 We can export the results. 791 00:35:27,170 --> 00:35:28,870 We can filter the data. 792 00:35:28,870 --> 00:35:31,180 We can identify the issues contextually 793 00:35:31,180 --> 00:35:32,593 and we provide API access. 794 00:35:35,050 --> 00:35:38,213 There are several ways that ARC can be deployed. 795 00:35:39,490 --> 00:35:41,340 We believe the best deployment option 796 00:35:41,340 --> 00:35:43,193 is our cloud hyper scale. 797 00:35:44,070 --> 00:35:45,580 But if you have ARC security requirements 798 00:35:45,580 --> 00:35:50,320 that prohibit this, we offer several other secure options. 799 00:35:50,320 --> 00:35:55,130 VPN tunnel, and AWS Amazon Machine Image, 800 00:35:55,130 --> 00:35:57,823 route solution and a container image, 801 00:35:58,750 --> 00:36:00,653 fully on prem supported. 802 00:36:02,950 --> 00:36:06,040 Now we decide maybe which is the best solution for you. 803 00:36:06,040 --> 00:36:09,620 We have a sort of a simple little flow work through. 804 00:36:09,620 --> 00:36:11,290 If your website is basically public, 805 00:36:11,290 --> 00:36:14,643 out there publicly available, google.com, 806 00:36:14,643 --> 00:36:17,770 the shared part, Analytics Hyperscale is the best way to go. 807 00:36:17,770 --> 00:36:20,510 Easiest for you to maintain. 808 00:36:20,510 --> 00:36:23,223 And you have no maintenance. We do it all. 809 00:36:24,410 --> 00:36:27,130 If it's not directly available to the public, 810 00:36:27,130 --> 00:36:29,034 or if the domain is being protected 811 00:36:29,034 --> 00:36:32,650 by bot detection software, 812 00:36:32,650 --> 00:36:33,930 or if it's in a lower region 813 00:36:33,930 --> 00:36:35,460 that you simply can't discreetly access, 814 00:36:35,460 --> 00:36:38,480 then maybe safe-listing ARC's IPs will work. 815 00:36:38,480 --> 00:36:40,410 And then we're just, we're basically still using 816 00:36:40,410 --> 00:36:41,930 the analytics Hyperscale solution, 817 00:36:41,930 --> 00:36:43,280 but we're safe-listing IPs. 818 00:36:44,470 --> 00:36:45,990 That's not gonna do it for you. 819 00:36:45,990 --> 00:36:48,910 Can you get provided VPN access to it? 820 00:36:48,910 --> 00:36:50,027 We can provide VPN access 821 00:36:50,027 --> 00:36:52,780 and we can still use the analytics Hyperscale solution 822 00:36:52,780 --> 00:36:53,743 via the VPN tunnel. 823 00:36:56,140 --> 00:36:57,150 Can't do that. 824 00:36:57,150 --> 00:37:00,840 Well, is the resource accessible via your private AWS cloud? 825 00:37:00,840 --> 00:37:02,620 And this is where you can bring in 826 00:37:02,620 --> 00:37:06,833 an Amazon Machine Image into your cloud, manage it yourself, 827 00:37:07,800 --> 00:37:10,830 and therefore not have any dependency on us. 828 00:37:10,830 --> 00:37:13,550 And if you don't have a private cloud with AWS, 829 00:37:13,550 --> 00:37:15,230 then for sure the resource is accessible, 830 00:37:15,230 --> 00:37:16,763 we at your infrastructure. 831 00:37:17,920 --> 00:37:20,520 And so that would be the customer managed container image. 832 00:37:20,520 --> 00:37:23,810 That's basically the entire image pulled out 833 00:37:23,810 --> 00:37:26,490 and balled up and given to you, 834 00:37:26,490 --> 00:37:31,490 and you basically install it on one of your servers 835 00:37:33,370 --> 00:37:34,470 and run it from there. 836 00:37:37,120 --> 00:37:39,640 But traditional ARC, we hope to be able to provide you 837 00:37:39,640 --> 00:37:43,633 a more rapid start and provide you more capabilities 838 00:37:43,633 --> 00:37:45,330 than what you're accustomed to having 839 00:37:45,330 --> 00:37:47,200 with Compliance Sheriff. 840 00:37:47,200 --> 00:37:49,350 By the way, not to say any at all negative 841 00:37:49,350 --> 00:37:52,683 about Compliance Sheriff in full transparency. 842 00:37:53,900 --> 00:37:56,210 A decade or so ago when I was building out 843 00:37:56,210 --> 00:37:59,320 JPMorgan Chase & Co.'s accessibility program, 844 00:37:59,320 --> 00:38:02,340 Brenton was my representative for Compliance Sheriff. 845 00:38:02,340 --> 00:38:05,240 I had Compliance Sheriff as one of my tools. 846 00:38:05,240 --> 00:38:07,380 So I'm very familiar with that tool 847 00:38:07,380 --> 00:38:09,700 and can only say good things about it. 848 00:38:09,700 --> 00:38:12,200 But ARC has gone beyond where Compliance Sheriff 849 00:38:12,200 --> 00:38:13,290 was able to go. 850 00:38:13,290 --> 00:38:15,210 And so we're able to offer you even more 851 00:38:15,210 --> 00:38:17,230 than what you currently have. 852 00:38:17,230 --> 00:38:18,850 In terms of what we can migrate 853 00:38:18,850 --> 00:38:20,940 from where you're currently at, 854 00:38:20,940 --> 00:38:22,510 your domain scan configuration. 855 00:38:22,510 --> 00:38:24,160 So as we pointed out the display name 856 00:38:24,160 --> 00:38:25,610 will become the title in ARC. 857 00:38:25,610 --> 00:38:29,440 Your base URL and starting URLs become root seed URLs. 858 00:38:29,440 --> 00:38:31,810 Page limit and levels becomes max and depth. 859 00:38:31,810 --> 00:38:33,610 Settings includes, excludes, 860 00:38:33,610 --> 00:38:35,350 complete URLs and exclusions. 861 00:38:35,350 --> 00:38:38,103 Your scan groups will become workspaces within ARC, 862 00:38:39,010 --> 00:38:42,923 and your section scans will be housed inside of folders. 863 00:38:44,070 --> 00:38:46,270 So that's how ARC manages that type of data. 864 00:38:47,400 --> 00:38:50,240 What won't migrate is your historical data. 865 00:38:50,240 --> 00:38:52,420 We are not able to bring that over. 866 00:38:52,420 --> 00:38:54,940 And the whole migration is optional 867 00:38:54,940 --> 00:38:57,080 in terms of how you reconfigure domains. 868 00:38:57,080 --> 00:38:58,420 This may be a great opportunity, 869 00:38:58,420 --> 00:39:01,780 sort of like moving to reset some things. 870 00:39:01,780 --> 00:39:04,575 And so if you wish to reconfigure the domains, 871 00:39:04,575 --> 00:39:06,610 we're happy to help you out doing that as well 872 00:39:06,610 --> 00:39:08,560 as we bring them into the ARC platform. 873 00:39:12,210 --> 00:39:13,730 And as I pointed out during the demonstration, 874 00:39:13,730 --> 00:39:15,250 ARC also provides Tutor. 875 00:39:15,250 --> 00:39:17,460 These are 18 expert authored, 876 00:39:17,460 --> 00:39:20,343 self-paced learning modules created by our experts. 877 00:39:21,301 --> 00:39:22,970 The KnowledgeBase, again, 878 00:39:22,970 --> 00:39:25,520 perpetually maintained by our experts 879 00:39:25,520 --> 00:39:28,540 as things change within the W3C, 880 00:39:28,540 --> 00:39:30,600 as things change within the technology stack, 881 00:39:30,600 --> 00:39:32,270 we're updating our KnowledgeBase to make sure 882 00:39:32,270 --> 00:39:33,430 that we're providing solutions 883 00:39:33,430 --> 00:39:35,130 for today's types of technologies. 884 00:39:39,190 --> 00:39:42,800 We have scanning with the ARC's open sourced rule set 885 00:39:42,800 --> 00:39:46,320 available in ARC, and it's turned on by default. 886 00:39:46,320 --> 00:39:47,500 You can turn it off. 887 00:39:47,500 --> 00:39:48,800 You consider it as your default setting 888 00:39:48,800 --> 00:39:50,480 if you're really familiar with those rules 889 00:39:50,480 --> 00:39:53,200 and wanna continue using them. 890 00:39:53,200 --> 00:39:56,083 So we have that option available to you as well within ARC. 891 00:39:57,620 --> 00:39:59,880 Integration with TPGi's expert manual assessments. 892 00:39:59,880 --> 00:40:03,160 As I pointed out through our capture capabilities, 893 00:40:03,160 --> 00:40:05,000 we bring automated and manual findings together 894 00:40:05,000 --> 00:40:06,600 into a single workspace for you. 895 00:40:08,200 --> 00:40:10,280 And we have help desk subscriptions. 896 00:40:10,280 --> 00:40:12,570 Rapid access to our experts. 897 00:40:12,570 --> 00:40:16,000 When you need that answer, you need that answer soon. 898 00:40:16,000 --> 00:40:17,250 The more it waits, 899 00:40:17,250 --> 00:40:20,120 the less likely it's gonna be tended to. 900 00:40:20,120 --> 00:40:22,240 Again, I come from rural development 901 00:40:22,240 --> 00:40:23,493 and I know how they think. 902 00:40:24,430 --> 00:40:26,470 I know how I think, and so, yeah, 903 00:40:26,470 --> 00:40:28,730 having rapid access to get the answer when I need it now, 904 00:40:28,730 --> 00:40:32,610 it was not available in any of ARC's resources directly 905 00:40:32,610 --> 00:40:34,093 like Tutor or KnowledgeBase. 906 00:40:34,093 --> 00:40:35,713 It's a very handy thing to have. 907 00:40:38,410 --> 00:40:41,923 And with that, once we're gonna make it an accessible. 908 00:40:44,650 --> 00:40:45,710 Travis. 909 00:40:45,710 --> 00:40:47,210 - Okay, thanks guys for going through that. 910 00:40:47,210 --> 00:40:49,720 I think that was great coverage 911 00:40:49,720 --> 00:40:51,790 and hopefully folks got a good feel 912 00:40:51,790 --> 00:40:54,180 for the art of the possible here. 913 00:40:54,180 --> 00:40:56,340 If you guys are interested in migrating over to ARC, 914 00:40:56,340 --> 00:40:58,590 just in case it was not abundantly clear, 915 00:40:58,590 --> 00:41:01,120 we are not automatically migrating anybody. 916 00:41:01,120 --> 00:41:05,230 So this would in essence, be somebody 917 00:41:05,230 --> 00:41:06,800 raising your hand saying you're interested 918 00:41:06,800 --> 00:41:09,100 in the ARC platform and us scheduling time with you 919 00:41:09,100 --> 00:41:10,850 to talk through what your need is, 920 00:41:10,850 --> 00:41:15,580 and then assembling a subscription for you guys. 921 00:41:15,580 --> 00:41:19,103 And we do work on it, a subscription model here. 922 00:41:20,240 --> 00:41:25,090 So we're happy to walk through your particular case 923 00:41:25,090 --> 00:41:27,510 with folks that understand what your needs are 924 00:41:27,510 --> 00:41:29,953 and build something that's gonna make sense for you. 925 00:41:31,610 --> 00:41:35,350 If you're interested in that, there was a link 926 00:41:35,350 --> 00:41:38,320 on this slide here that you can go to, 927 00:41:38,320 --> 00:41:43,320 to go get some of this information in greater detail. 928 00:41:44,390 --> 00:41:46,330 There's also a link. 929 00:41:46,330 --> 00:41:49,700 It's in the chat, that if you guys wanna click on, 930 00:41:49,700 --> 00:41:53,510 you can directly go to that and you can go sign up 931 00:41:53,510 --> 00:41:55,250 for an appointment with us. 932 00:41:55,250 --> 00:41:57,080 So we have a scheduler out there 933 00:41:57,080 --> 00:41:59,943 that you can go get directly connected with a rep here. 934 00:42:01,150 --> 00:42:04,260 In most cases, we've already assigned your accounts to reps. 935 00:42:04,260 --> 00:42:05,860 So you might have already started hearing 936 00:42:05,860 --> 00:42:10,510 from our reps or can, if you've not heard from them, 937 00:42:10,510 --> 00:42:12,170 you can ask for a meeting. 938 00:42:12,170 --> 00:42:16,663 So I think Brad put the schedule and meeting link in there. 939 00:42:17,532 --> 00:42:22,190 So please, hit on that link 940 00:42:22,190 --> 00:42:24,193 if you'd like to schedule time with us. 941 00:42:25,937 --> 00:42:28,070 And as mentioned, there's some of the information 942 00:42:28,070 --> 00:42:29,820 from the presentation will be available 943 00:42:29,820 --> 00:42:31,340 through this other link as well. 944 00:42:31,340 --> 00:42:34,070 So I know there were a few questions 945 00:42:34,070 --> 00:42:35,500 that went by through the chat 946 00:42:35,500 --> 00:42:37,920 that I don't think we've gotten to answer 947 00:42:37,920 --> 00:42:38,753 all of these yet. 948 00:42:38,753 --> 00:42:43,640 So I'm gonna roll up here and I will read the questions out 949 00:42:43,640 --> 00:42:45,950 and we will try to answer them. 950 00:42:45,950 --> 00:42:48,330 So let's see. 951 00:42:48,330 --> 00:42:50,090 Last one I saw was from Corinne. 952 00:42:50,090 --> 00:42:52,590 It asks, does ARC allow for scanning of websites 953 00:42:52,590 --> 00:42:55,480 and web apps that require a special authentication 954 00:42:55,480 --> 00:42:57,590 from your local machine? 955 00:42:57,590 --> 00:42:59,730 For example, internet sites. 956 00:42:59,730 --> 00:43:02,763 Would it depend on which deployment option you have? 957 00:43:05,160 --> 00:43:07,950 Kurt, I mean, what do you... 958 00:43:07,950 --> 00:43:11,740 I guess the answer is it depends on that one. 959 00:43:11,740 --> 00:43:14,250 - Well, yeah, if we can access the lower region 960 00:43:14,250 --> 00:43:15,920 from the outside, either through 961 00:43:15,920 --> 00:43:17,910 one of the other solutions, VPN tunnel 962 00:43:17,910 --> 00:43:19,570 or just something wait-listing or safe-listing, 963 00:43:19,570 --> 00:43:21,820 I'm sorry, our IP addresses, 964 00:43:21,820 --> 00:43:24,070 then we don't need to go to any of the other 965 00:43:24,070 --> 00:43:26,710 machine image type solutions, 966 00:43:26,710 --> 00:43:28,103 even though it is intranet. 967 00:43:28,940 --> 00:43:31,860 I have a case now where, yeah, 968 00:43:31,860 --> 00:43:36,150 it requires actually a dual login in order to get to it. 969 00:43:36,150 --> 00:43:38,340 First, we have to authenticate into the region 970 00:43:38,340 --> 00:43:39,270 and then we have to authenticate 971 00:43:39,270 --> 00:43:41,640 into the intranet site itself. 972 00:43:41,640 --> 00:43:44,357 And ARC is capable of executing both those authentications 973 00:43:44,357 --> 00:43:46,240 and extracting the skin. 974 00:43:46,240 --> 00:43:51,240 So we have a wide variety of versatility available 975 00:43:51,550 --> 00:43:54,163 in terms of how we go about implementing the engine 976 00:43:54,163 --> 00:43:56,117 that ARC can run. 977 00:43:56,117 --> 00:43:58,120 - Got it, okay. Great. 978 00:43:58,120 --> 00:43:59,220 Natalie had asked, 979 00:43:59,220 --> 00:44:01,090 will the presentation slides be made available? 980 00:44:01,090 --> 00:44:03,640 Yes, we will make the slides available to you guys. 981 00:44:04,530 --> 00:44:07,490 Tony had asked, it's that our reports are required to show 982 00:44:07,490 --> 00:44:10,870 passing percentage as well as list of failures. 983 00:44:10,870 --> 00:44:14,210 Can the system provide both a passing and failing percentage 984 00:44:14,210 --> 00:44:16,410 as separate reports? 985 00:44:16,410 --> 00:44:19,090 Passing scores are just provided reporting 986 00:44:19,090 --> 00:44:21,103 to general stack and reporting centers. 987 00:44:26,700 --> 00:44:28,880 - I think caution should be used 988 00:44:28,880 --> 00:44:30,930 with respect to the level of detail 989 00:44:30,930 --> 00:44:33,383 we expect from any automated scanning tool. 990 00:44:34,510 --> 00:44:36,410 First and foremost, it needs to be understood that, 991 00:44:36,410 --> 00:44:39,150 and it's debatable within this profession 992 00:44:39,150 --> 00:44:41,420 as to exactly how much automated tools can find, 993 00:44:41,420 --> 00:44:43,710 I hear anywhere from 20 to 50%. 994 00:44:43,710 --> 00:44:45,400 My 27 years of experience tells me 995 00:44:45,400 --> 00:44:48,030 it's somewhere around 30 to 35%. 996 00:44:48,030 --> 00:44:50,670 So we're really only looking at this subset anyhow. 997 00:44:50,670 --> 00:44:53,030 And so trying to become real specific 998 00:44:53,030 --> 00:44:54,530 and exacting with the numbers 999 00:44:54,530 --> 00:44:55,530 by only looking at a subset 1000 00:44:55,530 --> 00:44:59,153 of what the entire site has, may not have much value. 1001 00:45:00,430 --> 00:45:04,210 So just caution. 1002 00:45:04,210 --> 00:45:06,963 When looking at what any automated tool can tell you, 1003 00:45:07,930 --> 00:45:09,730 the general idea is to give you assessments 1004 00:45:09,730 --> 00:45:13,310 of what's out there, that is a problem that you have. 1005 00:45:13,310 --> 00:45:16,960 Yeah, we can get very specific with defining those problems, 1006 00:45:16,960 --> 00:45:18,420 but we're not gonna be able to tell you 1007 00:45:18,420 --> 00:45:20,920 every single problem on every single page. 1008 00:45:20,920 --> 00:45:22,420 That's just not doable. 1009 00:45:22,420 --> 00:45:25,850 And so, yeah, you can look at the numbers 1010 00:45:25,850 --> 00:45:28,030 from the positive or from the negative. 1011 00:45:28,030 --> 00:45:30,340 We tend to approach it by showing you 1012 00:45:30,340 --> 00:45:34,023 your WCAG capacity score, other neutral score, 1013 00:45:35,010 --> 00:45:38,540 as opposed to getting into exact pass and fail percentages. 1014 00:45:38,540 --> 00:45:39,490 Hopefully it helps. 1015 00:45:41,092 --> 00:45:43,280 I do caution very much to be careful 1016 00:45:43,280 --> 00:45:45,253 about how you interpret the data 1017 00:45:45,253 --> 00:45:47,003 that automated testing can provide. 1018 00:45:50,240 --> 00:45:54,180 It's valuable. - Yeah, definitely. 1019 00:45:54,180 --> 00:45:55,360 Tony had also asked, 1020 00:45:55,360 --> 00:45:57,480 can we see you the charge slide again? 1021 00:45:57,480 --> 00:46:00,853 I think Tony, if you're asking about what the fees are, 1022 00:46:02,930 --> 00:46:04,860 I think that's what you're asking. 1023 00:46:04,860 --> 00:46:06,570 Let's actually, I would prefer to do that 1024 00:46:06,570 --> 00:46:09,310 through a one-on-one session with you guys, 1025 00:46:09,310 --> 00:46:12,090 'cause we don't have all the fees in a slide here. 1026 00:46:12,090 --> 00:46:15,030 So we just had brief references 1027 00:46:15,030 --> 00:46:18,750 to the non-cloud hosted deployment fee structure. 1028 00:46:18,750 --> 00:46:23,292 So, I think like let's get time scheduled with you 1029 00:46:23,292 --> 00:46:24,125 if you're interested in that 1030 00:46:24,125 --> 00:46:26,290 and we can talk about your particular situation 1031 00:46:26,290 --> 00:46:28,450 and talk you through what the fees are. 1032 00:46:28,450 --> 00:46:30,660 As a general statement, I'll just say this 1033 00:46:30,660 --> 00:46:33,060 because we're transparent about this. 1034 00:46:33,060 --> 00:46:38,060 Our model is predicated on a seat-tier plus usage structure. 1035 00:46:38,470 --> 00:46:42,930 So think of that as you have X number of users 1036 00:46:42,930 --> 00:46:44,660 that you wanna have access to the platform 1037 00:46:44,660 --> 00:46:48,670 and you have Y number of test calls, we'll call it 1038 00:46:48,670 --> 00:46:50,913 that you're trying to monitor test score. 1039 00:46:52,456 --> 00:46:56,450 And we can build that up in a variety of ways for you, 1040 00:46:56,450 --> 00:46:59,290 but it's a very straightforward model. 1041 00:46:59,290 --> 00:47:02,410 So if you have seat access or based here, 1042 00:47:02,410 --> 00:47:07,410 what we call essentials is a $29 per seat per month fee. 1043 00:47:07,770 --> 00:47:08,860 So you can do the math. 1044 00:47:08,860 --> 00:47:11,770 For a 12-month access, it's $348 1045 00:47:11,770 --> 00:47:14,370 times however many users you might have. 1046 00:47:14,370 --> 00:47:16,480 And then the usage fees are five cents 1047 00:47:16,480 --> 00:47:19,210 per API call or test call. 1048 00:47:19,210 --> 00:47:21,820 And so, every time you touch the page, 1049 00:47:21,820 --> 00:47:24,889 that would be a test call, will be five cents. 1050 00:47:24,889 --> 00:47:29,889 And you can build up your pricing on a monthly basis. 1051 00:47:30,180 --> 00:47:32,380 If you wanna sort of have a cap 1052 00:47:32,380 --> 00:47:34,243 to what you wanna spend. 1053 00:47:35,400 --> 00:47:37,240 Alternatively, we do have an option 1054 00:47:37,240 --> 00:47:39,250 for you to simply put a credit card in 1055 00:47:39,250 --> 00:47:42,850 on our platform and just run on a monthly basis. 1056 00:47:42,850 --> 00:47:45,010 It's a straight usage model. 1057 00:47:45,010 --> 00:47:48,350 So it's very flexible and we're happy to walk through 1058 00:47:48,350 --> 00:47:53,250 the specifics of that if there's known quantities 1059 00:47:53,250 --> 00:47:55,953 that you guys are looking to cover. 1060 00:47:57,270 --> 00:47:58,860 And there are some other fees, 1061 00:47:58,860 --> 00:48:00,469 if you're doing more exotic things. 1062 00:48:00,469 --> 00:48:03,660 Like if you need SSO maintenance and things like that, 1063 00:48:03,660 --> 00:48:06,230 that we're happy to go through 1064 00:48:06,230 --> 00:48:08,103 based on your individual scenario. 1065 00:48:10,950 --> 00:48:12,910 James put in a question in there about- 1066 00:48:12,910 --> 00:48:14,681 - Can I get in on one little piece? 1067 00:48:14,681 --> 00:48:16,120 - Yeah, go ahead. 1068 00:48:16,120 --> 00:48:17,020 - Perfectly clear. 1069 00:48:18,500 --> 00:48:20,470 With any of those plans, 1070 00:48:20,470 --> 00:48:22,590 you are getting access to the KnowledgeBase 1071 00:48:22,590 --> 00:48:24,820 and Tutor as well. 1072 00:48:24,820 --> 00:48:25,740 That comes with them. 1073 00:48:25,740 --> 00:48:27,260 There's no separate fees for those. 1074 00:48:27,260 --> 00:48:28,093 - That's right. Yeah. 1075 00:48:28,093 --> 00:48:31,810 So if you have a seat, you get access to the platform, 1076 00:48:31,810 --> 00:48:35,240 all of the content, all the Tutor training courses, 1077 00:48:35,240 --> 00:48:38,803 all of our KnowledgeBase content through your seat. 1078 00:48:40,640 --> 00:48:42,100 James had asked a question about, 1079 00:48:42,100 --> 00:48:44,070 do you have the ability to do transaction scripts? 1080 00:48:44,070 --> 00:48:44,903 Yes. 1081 00:48:46,860 --> 00:48:51,860 And then he added, if a site has front case 1082 00:48:51,910 --> 00:48:53,463 and duo front end. 1083 00:48:55,090 --> 00:48:59,600 So my guess is, is that the answer is still yes, James, 1084 00:48:59,600 --> 00:49:01,100 but like if there's something unique 1085 00:49:01,100 --> 00:49:04,698 that we need to look at, we can look at it with you 1086 00:49:04,698 --> 00:49:06,393 and figure out how to support it. 1087 00:49:07,500 --> 00:49:10,740 James had also asked, is your solution cloud only? 1088 00:49:10,740 --> 00:49:13,700 I'm not gonna say it's cloud only, but it's predominantly 1089 00:49:13,700 --> 00:49:16,123 a cloud oriented solution, James, yes. 1090 00:49:18,517 --> 00:49:20,060 And you could ask, what if we want 1091 00:49:20,060 --> 00:49:22,563 a test in production on site? 1092 00:49:23,454 --> 00:49:26,900 So as Kurt mentioned, we have what's called 1093 00:49:26,900 --> 00:49:29,400 a container solution that would allow you 1094 00:49:29,400 --> 00:49:31,363 to deploy something locally. 1095 00:49:33,520 --> 00:49:36,000 The fees for that would depend on how many, 1096 00:49:36,000 --> 00:49:38,913 basically how many containers you need. 1097 00:49:41,137 --> 00:49:43,487 And we can talk through those options with you. 1098 00:49:44,410 --> 00:49:47,780 We would ideally like to route everybody 1099 00:49:47,780 --> 00:49:51,710 through the cloud model, which is a highly secure model. 1100 00:49:51,710 --> 00:49:54,570 But if you have some very, very particular need 1101 00:49:54,570 --> 00:49:57,760 to meet a security requirement, 1102 00:49:57,760 --> 00:50:00,130 that for some reason we don't need for our own model, 1103 00:50:00,130 --> 00:50:03,970 we're happy to try to get you to something 1104 00:50:03,970 --> 00:50:05,520 that's gonna satisfy your need. 1105 00:50:08,990 --> 00:50:10,920 I don't see any other questions. 1106 00:50:10,920 --> 00:50:13,927 So unless there's anything else... 1107 00:50:15,240 --> 00:50:16,550 - Yeah, circle back. 1108 00:50:16,550 --> 00:50:18,330 One that was asked early in the session 1109 00:50:18,330 --> 00:50:22,200 was around exporting of results in ARC, 1110 00:50:22,200 --> 00:50:23,910 which I can highlight. 1111 00:50:23,910 --> 00:50:27,280 We saw a quick screenshot that you can export 1112 00:50:27,280 --> 00:50:29,020 CSV or Excel files, 1113 00:50:29,020 --> 00:50:33,450 but you can also do prints of the reports inside of ARC, 1114 00:50:33,450 --> 00:50:36,530 and certainly highlight if there are more capabilities. 1115 00:50:36,530 --> 00:50:38,650 But then there's an additional question 1116 00:50:38,650 --> 00:50:41,700 of the accessibility of the interface itself. 1117 00:50:41,700 --> 00:50:45,430 For example, screen reader capabilities looking at reports, 1118 00:50:45,430 --> 00:50:48,860 I think it could be good to have. 1119 00:50:48,860 --> 00:50:50,700 - So the good news is, 1120 00:50:50,700 --> 00:50:53,571 we have an awful lot of screen reader users. 1121 00:50:53,571 --> 00:50:56,030 With our Vispero parent and the whole JAWS 1122 00:50:56,030 --> 00:50:58,630 freedom scientific branch, I would tell you, 1123 00:50:58,630 --> 00:51:02,980 it's probably 90% people with vision impairments. 1124 00:51:02,980 --> 00:51:05,820 We also have them here within TPGi. 1125 00:51:05,820 --> 00:51:09,210 And so yeah, our own employees try to keep us 1126 00:51:09,210 --> 00:51:10,770 as honest as possible. 1127 00:51:10,770 --> 00:51:12,740 And we do our best. 1128 00:51:12,740 --> 00:51:14,970 We do put our tool through accessibility testing. 1129 00:51:14,970 --> 00:51:17,470 In fact, we use ARC to test ARC 1130 00:51:18,610 --> 00:51:20,600 because ARC is cloud-based. 1131 00:51:20,600 --> 00:51:21,890 We can do that. 1132 00:51:21,890 --> 00:51:24,730 And so we do our best just like everybody else. 1133 00:51:24,730 --> 00:51:26,930 I will tell you that we are highly accessible 1134 00:51:26,930 --> 00:51:29,960 and I will tell you like any other website out there, 1135 00:51:29,960 --> 00:51:31,200 we'll never be perfect. 1136 00:51:31,200 --> 00:51:33,230 We'll never have full accessibility. 1137 00:51:33,230 --> 00:51:36,780 We'll never be without a bug of any type, 1138 00:51:36,780 --> 00:51:40,230 but we are about as close as we can get at this point 1139 00:51:40,230 --> 00:51:43,370 and working diligently to maintain it. 1140 00:51:43,370 --> 00:51:45,850 And we have people inside, 1141 00:51:45,850 --> 00:51:47,220 there's employees that work here 1142 00:51:47,220 --> 00:51:48,793 all over the site all the time. 1143 00:51:49,700 --> 00:51:51,890 I have a pretty good person on my team. 1144 00:51:51,890 --> 00:51:54,823 He sure tells me instantly when he runs into a problem. 1145 00:51:55,690 --> 00:51:57,740 And so yes, we were very mindful of that. 1146 00:51:59,536 --> 00:52:02,230 - I think James had one more question in here. 1147 00:52:02,230 --> 00:52:03,710 - If you wanted the platform we would like to know 1148 00:52:03,710 --> 00:52:05,070 if you encounter any issues like that. 1149 00:52:05,070 --> 00:52:07,940 Please, there's link at the bottom of the page. 1150 00:52:07,940 --> 00:52:09,990 Use it, tell us, we'll fix it. 1151 00:52:09,990 --> 00:52:12,190 - Yeah, that's a great point. 1152 00:52:12,190 --> 00:52:14,490 James had added one other question in here 1153 00:52:14,490 --> 00:52:17,517 about being able to migrate artifacts out of CS to ARC. 1154 00:52:17,517 --> 00:52:20,770 The answer is no, we're not migrating artifacts. 1155 00:52:20,770 --> 00:52:25,570 So we'll migrate configuration basically, right? 1156 00:52:25,570 --> 00:52:28,587 So we can help you guys migrate an existing config, 1157 00:52:29,620 --> 00:52:31,920 but the actual historic results, 1158 00:52:31,920 --> 00:52:34,090 you'll have to somehow snapshot on your side 1159 00:52:34,090 --> 00:52:38,133 to keep historic trends separate. 1160 00:52:41,580 --> 00:52:42,500 And there was a question in here 1161 00:52:42,500 --> 00:52:44,350 about also from James about, can you opt 1162 00:52:44,350 --> 00:52:46,293 for a site license unlimited? 1163 00:52:51,668 --> 00:52:53,640 Again, let's take that offline 1164 00:52:53,640 --> 00:52:56,020 in a separate conversation directly. 1165 00:52:56,020 --> 00:52:59,550 The container option gives you some ability 1166 00:52:59,550 --> 00:53:03,557 to scan at volume, 1167 00:53:05,600 --> 00:53:08,150 but we wanna understand 1168 00:53:08,150 --> 00:53:09,600 what your particular scenario is 1169 00:53:09,600 --> 00:53:12,143 to understand how to price it for you. 1170 00:53:16,690 --> 00:53:18,640 Okay, so again, if you guys are interested, 1171 00:53:18,640 --> 00:53:19,880 we'd love for you to click on the link 1172 00:53:19,880 --> 00:53:21,210 to schedule a meeting with us. 1173 00:53:21,210 --> 00:53:24,000 We'd love to connect with you directly 1174 00:53:24,000 --> 00:53:27,540 and we will be following up with you proactively 1175 00:53:27,540 --> 00:53:28,410 one way or the other. 1176 00:53:28,410 --> 00:53:30,010 But if you are highly interested, 1177 00:53:30,010 --> 00:53:31,320 please go ahead and reach out. 1178 00:53:31,320 --> 00:53:32,430 We'll get time scheduled with you 1179 00:53:32,430 --> 00:53:34,930 to go through ARC in greater detail. 1180 00:53:34,930 --> 00:53:38,050 And we look forward to hearing from everybody, 1181 00:53:38,050 --> 00:53:40,960 even if you just wanna get a deeper understanding 1182 00:53:40,960 --> 00:53:42,880 of what the art of the possible is here, 1183 00:53:42,880 --> 00:53:45,160 but we'd love to be working with all of you guys 1184 00:53:45,160 --> 00:53:47,180 and hope to hear from you. 1185 00:53:47,180 --> 00:53:50,017 And I wanna thank everybody for attending today. 1186 00:53:51,410 --> 00:53:52,720 All right. Thanks, guys. 1187 00:53:52,720 --> 00:53:53,720 Everyone have a great day. 1188 00:53:53,720 --> 00:53:55,123 - Great. Thanks, everyone.