Marissa: All right, I'm going to start the webinar.

00:00:00.000 --> 00:00:04.000
Right now, so. Okay.

00:00:04.000 --> 00:00:17.000
Hello, everyone. Thank you for joining us today for our presentation on the ARP enterprise tier and Zapier, hosted by Charlie Pike, Product Manager at TPGI.

00:00:17.000 --> 00:00:47.000
We are going to wait just another minute, to make sure that we have. Most of the people who will be attending. So please hang tight and we will get started shortly.

00:00:55.000 --> 00:01:25.000
Welcome everybody who was just joined, we'll be getting started in just a minute to make sure that everybody has enough time to join.

00:01:33.000 --> 00:01:35.000
Okay. It is now 1201.

00:01:35.000 --> 00:01:45.000
And I just have a few housekeeping things to go over first. There are captions available. If you'd like to toggle them on.

00:01:45.000 --> 00:02:00.000
Also there is a Q&A box. If you have questions please add them to the Q&A box and Charlie will address them at the end. If your question has not been answered if we don't have enough time to get to it, or you have further follow up questions,

00:02:00.000 --> 00:02:02.000
feel free to email.

00:02:02.000 --> 00:02:09.000
ida@tpgi.com and I will also put this link in the chat box.

00:02:09.000 --> 00:02:25.000
Also, if you have to leave early, the webinar is being recorded, you will get a follow up email after the webinar with a link to the recording, feel free to watch it at your leisure share with any colleagues or acquaintances, or email either you have

00:02:25.000 --> 00:02:27.000
any questions.

00:02:27.000 --> 00:02:38.000
So without further ado, I would like to turn the presentation over to Charlie. Again, this is the TPGI ARC enterprise tier and Zapier presentation.

00:02:38.000 --> 00:02:57.000
Charlie: Thanks very much versa. So, yeah, my name is Charlie pike. I'm product manager for the arc platform, and the our platform is not just the ark portal but includes a bunch of our edge products as we call them such as jaws Inspect.

00:02:57.000 --> 00:03:06.000
And our tool kit and a few others so essentially the whole, the whole product line that we have a TPGi.

00:03:06.000 --> 00:03:23.000
And I've been in the accessibility business for close to 20 years now since the start of TPG, And today on going to be taking you through some of the exciting new features of our enterprise tier so we have a new tier.

00:03:23.000 --> 00:03:35.000
We have obviously got a lot of enterprise customers in our could have been using our app for a number of years now since, since the beginning since we acquired and built on the product.

00:03:35.000 --> 00:03:46.000
And, but we've launched this new tier, to really tailor things to their needs, and we've added a few features that we haven't had before in arc.

00:03:46.000 --> 00:03:48.000
In order to address.

00:03:48.000 --> 00:03:55.000
Excuse me. In order to address a lot of the needs that we've seen those enterprise users have.

00:03:55.000 --> 00:04:08.000
So, as Marissa says, I'll go through things, I will show you some practical examples of all this various features, particularly the Zapier integration and our API.

00:04:08.000 --> 00:04:21.000
But I will leave time hopefully at the end to answer some of your questions so do pop them in the q amp a if you if you want to do that and we'll try to address more at the end.

00:04:21.000 --> 00:04:38.000
So, today fairly, fairly brief agenda so I'm just going to introduce the topic and the concepts are going to talk a bit about the enterprise arc enterprise tier and what's involved in it and the ARCA platform in general or all the bits are.

00:04:38.000 --> 00:04:50.000
But the bulk of what I'm going to go through today is essentially a case study a made up case study but one that's that's amalgamated from a lot of different cases that we have seen over the years.

00:04:50.000 --> 00:04:59.000
In TPGI, to show these new features in the context of a full scale accessibility program for an enterprise.

00:04:59.000 --> 00:05:05.000
And then as I said, we'll go into q amp a, and we'll answer some of your questions.

00:05:05.000 --> 00:05:09.000
So what is this enterprise tear that we've just launched.

00:05:09.000 --> 00:05:26.000
So, the enterprise tear. And one important thing to remember about it is that it moves to moves our enterprise customers to this new usage model that we've had, which we started out with this year, and the aim of that is really to change the game of it

00:05:26.000 --> 00:05:45.000
in terms of accessibility products and provide much more flexibility in the hands of users to control their costs and spread their costs. So now we have a $59 per seat per month so essentially per user, and each user to add to that gets access to all

00:05:45.000 --> 00:05:50.000
of the content in the portal so the knowledge base.

00:05:50.000 --> 00:06:00.000
With all our articles and best practice shooter with all our training modules, and of course the analytics, and so on. That's all available to each seat.

00:06:00.000 --> 00:06:03.000
So there's a lot of flexibility there.

00:06:03.000 --> 00:06:19.000
We provide along with that at that price we provide some additional features, only for the enterprise. One is configurable rule sets, I'll talk about that in a little bit and show you what that means but essentially, It's an ability to to remove or hide

00:06:19.000 --> 00:06:30.000
certain rules from our rule sets from your dashboards if needs be the Zapier integrations that I'll be showing you today.

00:06:30.000 --> 00:06:45.000
And they provide a huge range of options for exporting and sharing your arc data. If you're aware of Zapier to middleware application. And it's got thousands of apps.

00:06:45.000 --> 00:06:52.000
So, we're talking about the whole Microsoft Office Suite, and pretty much everything from Microsoft.

00:06:52.000 --> 00:06:53.000
Yeah, leading content management systems, such as Drupal, etc WordPress.

00:06:53.000 --> 00:07:10.000
Leading content management systems, such as Drupal, etc WordPress. It's all in there really there's thousands of apps, so you can easily with no programming, no real complexity, if you like, you can quickly create integrations workflows that you need

00:07:10.000 --> 00:07:13.000
so I'll be showing you some examples of that.

00:07:13.000 --> 00:07:25.000
And it includes account, linking so that you can bring several accounts together, and the enterprise. So you're more flexible in the way that you can compose your enterprise and set it up, but it's still pretty simple.

00:07:25.000 --> 00:07:43.000
So you've got a lot of flexibility in terms of access and who's got access to what but the structure itself does not take a major User Guide to understand and enterprise reporting, which allows for accounts to report, up to it to a senior account and

00:07:43.000 --> 00:08:00.000
I'll show you an example of that, flexible payment options for enterprises and free API calls. So, normally the API is charged on the usage basis basis when you make calls to the API you pay for those calls.

00:08:00.000 --> 00:08:15.000
However, for enterprise customers, you get free use of those API. And again, I'll talk about those things. So, I'll be talking about these as it goes through the and demonstrating the various features but those are the are the distinct features for the

00:08:15.000 --> 00:08:21.000
enterprise tier above and beyond the other tiers in arc.

00:08:21.000 --> 00:08:36.000
So, looking at what the art platform is now a lot of people just think of it because maybe the monitoring or analytics part of the portal that you see but actually there's a lot of parts to arc, and even more in fact than that are in this diagram so it's

00:08:36.000 --> 00:08:52.000
a it's a platform, and it contains monitoring it contains tutor our training modules knowledge base which is basically a compendium of TPGI, knowledge, best practice can all aspects of accessibility.

00:08:52.000 --> 00:09:09.000
Help Desk, or we can connect directly to TJ consultants to get help.

00:09:09.000 --> 00:09:18.000
But then on the flip side of that the other side is the arc Analytics API. And that's where you get all of that same data.

00:09:18.000 --> 00:09:23.000
But in integrated into your own tools.

00:09:23.000 --> 00:09:40.000
So you get all your analytics, etc available inside your content management system available inside your development environment, wherever you need it in context where your developers are testing and fixing the issue.

00:09:40.000 --> 00:09:59.000
So it's kind of another way of working with arc, and I'll be showing you some examples today. We also have the art tool kit, which is a free Chrome plugin, which allows you to do the same testing same rules, and we have jobs inspect, which is a desktop

00:09:59.000 --> 00:10:12.000
windows product and its really jaws for testing simplifies jobs and provides transcripts of jaws speech for testers, in the form of reports that they can easily distributed, and review.

00:10:12.000 --> 00:10:16.000
So that's the our platform.

00:10:16.000 --> 00:10:33.000
In a nutshell, and I want to talk now about accessibility phases and accessibility program, just to put some of these features into context for you so obviously we've, as I said I've been in accessibility for a long time and TPI have been accessibility

00:10:33.000 --> 00:10:44.000
for a long time. And we've worked with a lot of customers, and, and, and, and we've seen the maturity model, develop at the start, when when they started out with accessibility.

00:10:44.000 --> 00:11:03.000
A lot of organizations even larger organizations dependent on a very very small team of accessibility consultants, sometimes just, you know, 234 people, and they would do all the testing for the organization they would bring in third parties to help.

00:11:03.000 --> 00:11:18.000
And the emphasis it tended to be a product was in trouble with a legal case, or they were selling to the federal government, they heard about accessibility, they needed this team to test the product for them and find out how compliant they were the word,

00:11:18.000 --> 00:11:31.000
and, and, and this, this was a very much a I guess a baby approach a first discovery phase where, you know, a lot of the time the work that was done wasn't sustained.

00:11:31.000 --> 00:11:38.000
So, a product was improved accessibility was fixed, and then a little later on.

00:11:38.000 --> 00:11:51.000
That went backwards the new version, and a lot of that accessibility work was lost. And so a lot of organizations that are trying to move towards a more mature model where accessibility is really embedded.

00:11:51.000 --> 00:11:57.000
And because retrofitting accessibility, does not work, it's too expensive it's often ineffective.

00:11:57.000 --> 00:12:02.000
and they want to spread the effort throughout the organization.

00:12:02.000 --> 00:12:13.000
So what we see are different phases I've split it up into three phases. Obviously, these programs are unique to the organization, but there's a lot of common threads.

00:12:13.000 --> 00:12:23.000
So, the first phase is that kind of discovery phase, said, where you're trying to find out where you are, if you're looking at it from a risk analysis point of view where the big areas of risk.

00:12:23.000 --> 00:12:39.000
If you just want to address things for your users, what are the best ways that you can do that. And so you're doing accessibility scans, using automated testing, you might be doing some manual testing, particularly on things that are critical.

00:12:39.000 --> 00:12:55.000
And you might be looking at existing user flows. And what I mean by that is the key tasks so a hotel website that might be the booking flow, for instance, and you want to start based on the data that you get started setting baselines so that you can track

00:12:55.000 --> 00:12:57.000
progress.

00:12:57.000 --> 00:13:02.000
And you can build out a roadmap of where you want to be.

00:13:02.000 --> 00:13:14.000
And then the next phase the rollout is essentially to spread responsibilities. So you want to get quickly beyond the small team won't scale into a program that will scan.

00:13:14.000 --> 00:13:23.000
So you want to start identifying who needs to test where and walk. And where do they need to focus their efforts.

00:13:23.000 --> 00:13:30.000
Who needs access to what setting them up with their own projects if you like their own accessibility projects.

00:13:30.000 --> 00:13:46.000
You want to embed processes as upstream as possible, so that you reduce the effort downstream in terms of texting and fixing, and then integrate testing all levels so you everybody should be doing some manner of testing even content authors, and you want

00:13:46.000 --> 00:14:00.000
to train people and you want to build knowledge inside the organization, then hopefully you get towards a more mature state where it's a steady state, right you've got aspect accessible in all aspects of the business, you're testing in all parts of your

00:14:00.000 --> 00:14:14.000
development pipeline, you're monitoring the stage state so hopefully you've addressed most of the issues, you're producing accessible content you just have to make sure there are no changes, or we're not moving backwards, at any stage and you can react

00:14:14.000 --> 00:14:26.000
quickly to that. And you're also doing usability testing so you're moving beyond simple compliance to actually looking what's the optimum experience for the end user.

00:14:26.000 --> 00:14:34.000
So I'm going to what I'm going to do today is really show you the ways in which you can use an arc enterprise tier account.

00:14:34.000 --> 00:14:54.000
To be able to address those things and it's all here. So we talked about discovery in the first phase being discovery.

00:14:54.000 --> 00:15:07.000
until you get down to the core, and you can look at everything through these different layers depending on what your needs are. So we've got the high level, our domain scans and domain monitoring and that's usually going to be a scan of something large,

00:15:07.000 --> 00:15:18.000
okay, an entire website, or a selection of 200 300 pages from your website, whatever you're going to do, and that's going to give you the macro view. Okay, you're going to see trends over time.

00:15:18.000 --> 00:15:27.000
And you're going to see what's in the production process might be contributing to accessibility issues, then you've got that critical focus, which is the user flows.

00:15:27.000 --> 00:15:39.000
I mentioned, you know of booking booking process and the hotel website that will be a key user flow. These are the things you want to make sure work at the minimum.

00:15:39.000 --> 00:15:49.000
Right. These are the tasks you want your users to be able to complete as a baseline. So you might look at those in more detail than you would add the domain scans.

00:15:49.000 --> 00:16:07.000
And then finally the most forensic view is the manual expert testing where you might get the likes of TPGI, or you do it internally with your own teams, you carry out a full, for instance way gag orders, go through everything eyeball every issue, essentially,

00:16:07.000 --> 00:16:10.000
and report those in detail.

00:16:10.000 --> 00:16:16.000
And the good news is art has a new rules engine the ARPU five.

00:16:16.000 --> 00:16:27.000
And that aren't rule five is it is a unified engine. In other words, all of the tests and criteria in there are the same threat all these levels of analysis.

00:16:27.000 --> 00:16:44.000
So there we've got rules that are tested automatically. And we've got rules in there that are tested manually, and all these user flows domain scans and engagements as we call you call them our audits and use the same rules engine, what does this mean

00:16:44.000 --> 00:17:00.000
it means the data is comparable where you do a deep analysis. You can also compare it to. If you like that broader analysis you do with the, with the domain scans, and you can use one with the other and I'll talk a little bit when I show you my demo,

00:17:00.000 --> 00:17:02.000
about how that works.

00:17:02.000 --> 00:17:11.000
But it's all one rules engine, so you get that normalization of the data, which really helps you to compare compare and contrast.

00:17:11.000 --> 00:17:21.000
So we do the accessibility scanning of what websites and web applications are also supports interactive flows so you can record.

00:17:21.000 --> 00:17:32.000
Using flows using for instance a Selenium recording to and upload that to art build a user flow, an arc and then test that interaction.

00:17:32.000 --> 00:17:50.000
We can test authenticated content we have special recorded flows for authentication. And we can do that in a very secure way. And we could also test and analyze things that are, you know, not necessarily open to the public are open to the cloud.

00:17:50.000 --> 00:18:09.000
These include a safe listing of the ark IPS to allow the ark servers in but we also include VPN, and deployed containers and the VPN and deploying containers that are available only to this enterprise tier customers.

00:18:09.000 --> 00:18:21.000
And just to show you how that works. So, obviously the standard way to use arc is the website that you're testing is public, and then you can just use the ark analytics hyper scale with no configuration needed.

00:18:21.000 --> 00:18:23.000
If it's not, public.

00:18:23.000 --> 00:18:36.000
The easiest option is to whitelist the our IPS. We have fixed IPS whitelists those are safe list those. And, and then our can operate and scan your content.

00:18:36.000 --> 00:18:49.000
If that's not feasible. We also support VPN access we can make a VP set up a VPN tunnel. There is an extra cost involved, but it's just a setup costs.

00:18:49.000 --> 00:18:52.000
And then finally we have.

00:18:52.000 --> 00:19:12.000
We have managed AWS mi we also have a container that I'll tell you about, which allows you to essentially deploy the arc analytics service inside your firewall to dm z, so that you can run the analytics in there.

00:19:12.000 --> 00:19:22.000
Obviously that's the most difficult option to maintain a separate server and image essentially on your on your network.

00:19:22.000 --> 00:19:27.000
So you would want to go through the look at the other steps before you go down that point.

00:19:27.000 --> 00:19:44.000
And those the container image, I was talking about so that the generally the service, they analytic service runs here just in a standard way through our Secure Gateway IP addresses, we run our analytics on a, on a visible public website that's the simplest

00:19:44.000 --> 00:19:56.000
scenario is just a diagram of our VPN tunnel, which is the same scenario but obviously run through a tunnel directly to the secure content.

00:19:56.000 --> 00:20:08.000
And then finally, we've got these container images, which will be available to you on Docker Hub, and you can essentially use your arc of indication to go get that image, but set it up on your network.

00:20:08.000 --> 00:20:13.000
It's quite simple. I mean it's just a matter of opening up the correct ports.

00:20:13.000 --> 00:20:25.000
And it should be able to see that secure site and also see out to arc on the cloud so that you can send the data, send the test results, etc.

00:20:25.000 --> 00:20:43.000
and access your dashboards is normal. So that's the analytics, you can do as part of the discovery and obviously continuously beyond that. But we also then move on to a rollout phase where you've begun to understand set your baselines understand where

00:20:43.000 --> 00:20:46.000
you are and take action.

00:20:46.000 --> 00:20:55.000
But at that point you want to be able to spread the effort throughout your organization that not everybody in the enterprise is going to be coming into the art portal.

00:20:55.000 --> 00:21:08.000
They want accessibility in context with the work that they're doing. So for them. We've got the Zapier integration, and you can use Zapier really to send that art data out anywhere you need to.

00:21:08.000 --> 00:21:12.000
Okay, and into multiple places at once if needs be.

00:21:12.000 --> 00:21:22.000
and the API, which really give you full flexibility to integrate the art data into your for instance here development environment your test processes.

00:21:22.000 --> 00:21:28.000
So nobody has to go anywhere their tests appear right in front of them, as they're doing their work.

00:21:28.000 --> 00:21:36.000
So you want to roll out that testing, you can use the API. We also have the art tool kit, I'll show you how that works too.

00:21:36.000 --> 00:21:53.000
That's a desktop installation it's a browser extension, so it can be used really in deep environments where there's for instance no connection to the cloud at all, even to other parts of the network and developers working on their local system contest

00:21:53.000 --> 00:22:07.000
their templates directly in the art toolkit if they need be. So it's a very flexible option. We also have for those deeper environments we have a note package, which allows you to integrate the testing into your note, being with your other note tests

00:22:07.000 --> 00:22:22.000
for instance, again the thing to remember is, they're all using that arc. Five rule set. So, they're all you're comparing the same data you're all running off the same set of tests.

00:22:22.000 --> 00:22:31.000
And so you've got the same data, and you can share it across the organization that's so crucial and effort like this because it's not normalized if you're not looking at the same thing.

00:22:31.000 --> 00:22:39.000
The same scores that mean the same thing. and you can no longer rely on that data.

00:22:39.000 --> 00:22:49.000
So I'll just go over switch over now. If you are live from the slides, and will start to look at an actual enterprise tear account.

00:22:49.000 --> 00:23:04.000
So here just to set the scene. We have a imaginary media organization that has a bunch of media assets that they've acquired over time so it's in the UK.

00:23:04.000 --> 00:23:22.000
They have a bunch of UK newspapers. They have a broadcast TV and so on. And they also have interactive interactive so they have games companies and so on so they have a bunch of of different logos, underneath the main logo.

00:23:22.000 --> 00:23:33.000
And they have to dress accessibility enterprise wide and their, their history has been that some of these organizations are more mature with accessibility than others.

00:23:33.000 --> 00:23:42.000
Some have done testing. They've all use different variety of tools depending on the knowledge and preferences of various accessibility teams.

00:23:42.000 --> 00:23:52.000
So they've got a lot of knowledge around accessibility, they have it embedded in the organization but it's patchy, and the information, really can't be compared.

00:23:52.000 --> 00:24:04.000
Okay, there's none of this normalization they're not using the same set of tests or rules are the same style of testing, and they have even tried out our separately and have separate accounts and the dairies divisions.

00:24:04.000 --> 00:24:16.000
But what they've done now is they formed it all up into one enterprise tier account. So here we've got the main account this demo account. We will also got an account for broadcast.

00:24:16.000 --> 00:24:31.000
We've also got an account for interactive. So as we do the discovery, all of these are now linked together inside an enterprise account, and I'll show you how they can report up with essentially each one has their own administrator runs that account sets

00:24:31.000 --> 00:24:46.000
of users workspaces, and all the rest and has their own report, and then they have one overarching account, which is like the controlling account for the others, and already that's simplifying the things for them in terms of their.

00:24:46.000 --> 00:24:53.000
Obviously the variety of tools they're using but also how they do their billing, etc.

00:24:53.000 --> 00:25:11.000
So in this example, we're looking at one particular asset and they've put this asset The Guardian newspaper in here into their workspace, so that the team that owns the Guardian if you like old people who work on it and share their guardian data, and

00:25:11.000 --> 00:25:25.000
and they've done this discovery so they've combined various elements of the Guardian, and started to analyze them for instance we have this Guardian site so this is the domain The Guardian.

00:25:25.000 --> 00:25:30.000
And they're scanning it's just in this example it's just 15 URLs, but it could be anything.

00:25:30.000 --> 00:25:38.000
They're using the arc engine. We also support other engines we support acts, for instance for capturing all the data.

00:25:38.000 --> 00:25:49.000
And they're using this to get the broad view. So they use that obviously the week identity score which is our way in our scoring on the, the number of issues per page.

00:25:49.000 --> 00:25:59.000
But more importantly, they're using these trend lines so they're looking at this and they're going, that a significant amount of effort was done and in fact accessibility was excellent.

00:25:59.000 --> 00:26:14.000
But over time since 2019 that has crept up, and then on a particular date here is going up further. Okay, so this is one of the ways that we can use this data in the world sweep of the domain monitoring, to see what's happening behind the scenes what

00:26:14.000 --> 00:26:20.000
was what happened here was their release. Was there a change that they put in you.

00:26:20.000 --> 00:26:35.000
Did they start using a different widget library, what has happened, you can go back to those, those dates, figure out what's happening in your process and understand how that's contributing to the accessibility and also obviously we've identified with

00:26:35.000 --> 00:26:46.000
pie charts, the largest wake egg failures and engine assertions, which are essentially the technical issues that are leading to those week out failures.

00:26:46.000 --> 00:26:49.000
And the worst of landing pages.

00:26:49.000 --> 00:26:53.000
Down going on down to the least at least problematic.

00:26:53.000 --> 00:27:10.000
And then we also identify the priorities. Okay so arc immediately starts to pull out the items that are contributing most in terms of the number of failures and divides them up into priority one priority three so straight away can start to.

00:27:10.000 --> 00:27:23.000
It can start to onion skin This problem can start to do to address it in the past with accessibility programs the approach tend to been pure compliance so give me a list of accessibility issues and you'll start to go through them.

00:27:23.000 --> 00:27:30.000
The problem with that is a there's probably too many sure an enterprise there are too many there are thousands of issues.

00:27:30.000 --> 00:27:39.000
And, and there's what I call compliant whack a mole, you know, just do with your fixing issues that are popping up you're creating them faster than you can fix them.

00:27:39.000 --> 00:27:50.000
So the process has to be dealt with. And you can use this data such as the trend lines, and the priorities to start looking at where you need to focus your efforts.

00:27:50.000 --> 00:28:04.000
Now I'm not going to go in detail into these dashboards in our, because obviously, if you're familiar with arc, we have covered these and other other presentations and I want to focus on particular things today.

00:28:04.000 --> 00:28:15.000
But basically you're going through the dashboards. And the important thing to remember is the dashboards are following the same patterns, no matter what kind of analysis your new.

00:28:15.000 --> 00:28:24.000
So once you become familiar with them with their trend lines pie charts and so on. Then, it works the same throughout.

00:28:24.000 --> 00:28:36.000
And you get to the lower lowest level, really, where you can actually see the instances, the code instances of issues and page and you get details about the issue.

00:28:36.000 --> 00:28:47.000
You also get this direct connection to RTPJI authored knowledge base, which explains in detail.

00:28:47.000 --> 00:29:02.000
All of these issues, how to fix them with code examples. And these are maintained on a monthly basis so this is it being a dedicated content team, maintaining and updating these and adding to these articles constantly so there's plenty of content to support

00:29:02.000 --> 00:29:10.000
your remediation efforts. You can also include your own commentary on these issues.

00:29:10.000 --> 00:29:29.000
So that's one level of analysis, and then the other level of analysis being done is I said the user flows, and the user flows are are, as I said they're there, they're the key flows in your, in your software or your applications.

00:29:29.000 --> 00:29:41.000
And they can be interacting so you can record with the Selenium script and build a user flow out of that script called your screen, various steps. And they also.

00:29:41.000 --> 00:29:58.000
They also allow you to to scan a particular part of a page not just a whole page and when you scan domains you scan the whole page for you the flows, you can actually scan, and you can actually scan a component on a page which is the dialog box, a data

00:29:58.000 --> 00:30:14.000
table, whenever you want you can define that component and scan that. So it's a lower level more detailed analysis. But again, here in The Guardian case they're focused on particular templates that they want to capture that users are always hitting, and

00:30:14.000 --> 00:30:20.000
they, they scan those so it's a smaller set that they scan.

00:30:20.000 --> 00:30:23.000
They're looking at it and close it detailed.

00:30:23.000 --> 00:30:33.000
They're looking at individual components. And this analysis and they're making sure that they fix those issues and address them urgently.

00:30:33.000 --> 00:30:44.000
And, but in this case, they've looked at these they've discovered significant issues, and they've decided to dive even deeper, and this case they've actually decided to do a full audit.

00:30:44.000 --> 00:30:58.000
So they brought in TPGI to do an audit. And again, the audit report done by expert testers is then uploaded to the dashboard here.

00:30:58.000 --> 00:31:05.000
And it's again the same type of dashboard in fact it's the same user flow we're looking at the same components.

00:31:05.000 --> 00:31:16.000
And you can dig into those, and each item has its own dashboard again.

00:31:16.000 --> 00:31:33.000
These components, and I can go in and I can get the level of detail. Now obviously this being a audit, there's a little more detail in here because the auditor has added notes, and there are certain things you can find such as the severity and complexity,

00:31:33.000 --> 00:31:38.000
can be defined, because somebody an expert is actually looking at the issues.

00:31:38.000 --> 00:31:57.000
But otherwise, this is the same rule set. And, and, if for instance, you're using your, your automated testing, and you might identify things that you might test in the user flow, but you might also identify problems and say we need to do deeper analysis

00:31:57.000 --> 00:32:07.000
on that. Let's do some manual testing. So the automated tool can help you find those things that you need to test in more detail because you can audit everything.

00:32:07.000 --> 00:32:12.000
And then you do your audit, and then as you fix things.

00:32:12.000 --> 00:32:22.000
In that audit, you can use the automated testing to make sure your teams are going in the right direction that the remediation is actually working.

00:32:22.000 --> 00:32:36.000
And then if it's not, maybe they need to look at the report again maybe they need to be trained, so you can hold the effort and fix it. So these are the ways that you can interplay between your levels of analysis, because you're using the same set of

00:32:36.000 --> 00:32:38.000
rules.

00:32:38.000 --> 00:32:48.000
And actually, in this example so we've got all this different data in this workspace, but we can compare it all because we're running off the same rule set the same scoring.

00:32:48.000 --> 00:33:03.000
We've got user flows we've got individual folders inside that domain that we're scanning, and what the Guardian have learned is that they have a problem with I frames because they're iframe like a lot of media websites are content contained advertising,

00:33:03.000 --> 00:33:18.000
they're being supplied by the by a source outside them that they have no control over. So they were getting a lot of this iframe data issues with their iframe, and what they wanted to do is actually hide that from the dashboard, they want to see on the

00:33:18.000 --> 00:33:21.000
dashboard as the things that they can actually fix.

00:33:21.000 --> 00:33:27.000
And this is an enterprise only feature where essentially in their analytics.

00:33:27.000 --> 00:33:32.000
They can go into the rules and configure the rules.

00:33:32.000 --> 00:33:44.000
As a brand new feature in arc, and they can have a look for the iframe issues, you see them here. So we've actually hidden the iframe issues. And we see this in action.

00:33:44.000 --> 00:33:48.000
Here, and open the guardian.

00:33:48.000 --> 00:33:53.000
Again,

00:33:53.000 --> 00:34:00.000
if we go down to our list of all the issues that have been identified and have a look for iframe.

00:34:00.000 --> 00:34:02.000
Let's see, there's nothing here.

00:34:02.000 --> 00:34:06.000
Okay. However,

00:34:06.000 --> 00:34:09.000
if we go back in history, which you can do an arc.

00:34:09.000 --> 00:34:24.000
I didn't realize we have this feature, we can actually jump back to a previous dashboard let's go back here to see what that dashboard was like back then.

00:34:24.000 --> 00:34:28.000
And then if we have a look at issues on that date.

00:34:28.000 --> 00:34:36.000
You'll see that we had 49 cases of this iframe know title, down to that ad.

00:34:36.000 --> 00:34:52.000
So we've taken that out with hidden it it's it's a it's a powerful thing, and a rather dangerous thing to use because obviously a lot of people use that to hide things that maybe are false positives from the otter automated scans, but the reality is that

00:34:52.000 --> 00:35:10.000
that these false positives that same rule might actually give you accurate results on the same site even on the same page, where it gives false positives in some cases you have to be careful about the use of this, but it's a good way of if you like hiding

00:35:10.000 --> 00:35:16.000
away things that you can't control or maybe you're waiting for another version before you control it.

00:35:16.000 --> 00:35:20.000
And so, the Guardian have done all this.

00:35:20.000 --> 00:35:27.000
They can report for the administrator, that can be a report, all the way up.

00:35:27.000 --> 00:35:37.000
For all of the various things that have been scanned in all the various workspaces, and you get that overview, but also because this is the main controlling account.

00:35:37.000 --> 00:35:54.000
We have a roll up report, which covers all of the analytics, from all the link to count.

00:35:54.000 --> 00:36:11.000
And because it gives them this few immediately on all their various accounts, rolling up and this is an enterprise only feature, so I can see immediately we've got a problem down there and BT Sport has been a major problem there that we need to address.

00:36:11.000 --> 00:36:21.000
So don't need to know about week I don't need to know the details on executive level here, but I need to know where we're particularly exposed or where things are particularly problematic.

00:36:21.000 --> 00:36:26.000
And are they heading in the right direction. That's key.

00:36:26.000 --> 00:36:28.000
And that's available there.

00:36:28.000 --> 00:36:44.000
And the other thing to note about about this account is we've everything organized in workspaces, as I said, so the workspace is allow you easily to organize your access rights, because all you have to do is put your stuff in a workspace that you want

00:36:44.000 --> 00:36:52.000
a team to share, organize it around teams and just add members to it. So rather than having a complex access model.

00:36:52.000 --> 00:37:03.000
We actually have a very simple one with a very flexible one, if you don't want somebody to see something you can move what's what's available in that workspace into another workspace, you can switch them around very easily.

00:37:03.000 --> 00:37:12.000
You don't have to get into complex roles and who's got access to what, and all of this, but it's still flexible enough for an enterprise.

00:37:12.000 --> 00:37:26.000
And that brings up the next important point which is obviously as you begin to roll out this information, you're going to have to go beyond the portal to the various other tools, not everybody is going to come and that not everybody has accessibility

00:37:26.000 --> 00:37:30.000
is their job, so they're not going to necessarily come into the portal.

00:37:30.000 --> 00:37:34.000
And in the case of a guardian.

00:37:34.000 --> 00:37:49.000
They actually have different teams working on the site so they actually have a third party company who are providing their templates and where they have accessibility issues this company has asked them to report them has bugs in JIRA instance so they

00:37:49.000 --> 00:38:07.000
they can track them. And they also want a separate report on anything that's alerts, so if it's an error to narrow identified by the automated to. They want that to go in as a bug in JIRA, but if it's maybe something that needs to be manual check might

00:38:07.000 --> 00:38:21.000
not might not be an issue or might be an issue, and they've got a special report they've set up to keep a track of those. So this is where our Zapier capability comes in.

00:38:21.000 --> 00:38:28.000
Sorry I got so many windows here

00:38:28.000 --> 00:38:38.000
last night Zapier and second.

00:38:38.000 --> 00:38:52.000
So Zapier makes it very easy, without any programming to set up, simple workflows for your art, data, and do integration, as I said, you don't need any scripting knowledge.

00:38:52.000 --> 00:38:59.000
We've got a basic example to do what we want to do here it's got some couple of conditions, they're very simple.

00:38:59.000 --> 00:39:01.000
If there are errors.

00:39:01.000 --> 00:39:21.000
We want them to do a specific thing if we've got alerts, we wanted to do another thing we've just connected it up to their JIRA instance here. Very simply, and then we mapping the data from arc, to go into that JIRA instance, and the data we're talking

00:39:21.000 --> 00:39:32.000
about here is essentially our issues. Okay, so if we dig down. Let's go into the culture section here, because we're talking about templates

00:39:32.000 --> 00:39:35.000
and pick a page.

00:39:35.000 --> 00:39:44.000
And here we've got a list of issues here in the assertion summary. And I can either send one at a time.

00:39:44.000 --> 00:40:03.000
Or I can send all the assertions to Zapier, and we'll go. The reason we do this this manual push basis is essentially, because we don't want to overwhelm, for instance cheer with if there's thousands of issues suddenly you've got thousands of tickets.

00:40:03.000 --> 00:40:15.000
And also because generally somebody needs to triage this. Okay, they need to look at what issues need to go in as bugs, they're always the case with accessibility issues.

00:40:15.000 --> 00:40:37.000
And so you manually push it to JIRA. We also have a spreadsheet report here set up in Gmail or in Google Docs, excuse me, to receive the alerts. And all we have to do once we fed up that that is go in here and essentially that I'm going to zap all the

00:40:37.000 --> 00:40:42.000
assertions in this case I capture everything.

00:40:42.000 --> 00:40:51.000
And then we go over to their JIRA project, and we should start to see those issues start to populate.

00:40:51.000 --> 00:40:55.000
So here we go, here is no image role.

00:40:55.000 --> 00:41:11.000
An issue. We've got a link back to the dashboard to see the detail and the knowledge base content. and we've got some specific fields that we set up in JIRA to keep track some of the accessibility information such as the weekend criteria.

00:41:11.000 --> 00:41:24.000
And that book is created automatically, we just refresh here we see more of them, and they've all been added automatically to JIRA as books. So once you've created the zap, I can just forget it.

00:41:24.000 --> 00:41:35.000
At this stage, it just runs every time I need to send those issues out. And then if we go over to our Google Doc, you can see that it's sending just the alerts, over here.

00:41:35.000 --> 00:41:51.000
But again, you've got your link back to the dashboard, you've got all the elements you need from the report Zapier, really, is there I mean there's an awful lot more that you could do here, you could send out emails for instance as integration with the

00:41:51.000 --> 00:42:06.000
email, including Microsoft Exchange, you could send out alerts, of different kinds depending on you know if the wake identity score goes over a certain level, and and and you can run all these integrations at the same time, so you can just hit this button

00:42:06.000 --> 00:42:19.000
once to send your zaps, and then have to go in multiple different directions depending on the different tasks you are. That's how you spread it out throughout the organization.

00:42:19.000 --> 00:42:38.000
But we also have of course, the API. And the API, give you the ability, obviously, it requires some scripting, and requires some integration, but it gives you full flexibility to integrate everything so here we have, for instance are sort of API playground

00:42:38.000 --> 00:42:53.000
where you can see the data that's available. And we cover really every aspect of arc so we're not limited at all to just accessibility issues here, you can get all aspects of your account, new configuration.

00:42:53.000 --> 00:42:58.000
For instance, here we've got to get account summaries.

00:42:58.000 --> 00:43:11.000
And if we just run that on a test basis so we've got the Guardian account, and the arc moves engine, in this case, if we just run that.

00:43:11.000 --> 00:43:22.000
So it's going off to arc, to make that query, basically to get summaries of all the of the account.

00:43:22.000 --> 00:43:33.000
You can see here, it's coming back with things like the domain is the Guardian scanned monthly, but the last candidate. What was the week identity score.

00:43:33.000 --> 00:43:46.000
So, that can be run in your test environment you can run that on a regular basis and get the results back enterprise tier customers can avail of that for free.

00:43:46.000 --> 00:44:01.000
The only thing they don't get for free, here is if they actually run the test you can also use the API to run a test and come back with results. What if all you're doing is getting existing test data you're running the test on arc, the portal.

00:44:01.000 --> 00:44:13.000
And then you're getting the results down into your system, then you can do it this way, just to demonstrate the power of API's here very quickly, I'm going to show this in Windows.

00:44:13.000 --> 00:44:17.000
We have a spreadsheet here an Excel spreadsheet.

00:44:17.000 --> 00:44:41.000
And I've created without any programming or scripting. I've created a connection between this spreadsheet and the ark API. Very simply, I come in here and just go to the data view will see the connection.

00:44:41.000 --> 00:44:42.000
It is.

00:44:42.000 --> 00:44:54.000
And if I just run that connection is going to do the same thing it's going to call the API. It's going to do the same thing, give me an account summary.

00:44:54.000 --> 00:44:59.000
And it's going to pull it into this spreadsheet.

00:44:59.000 --> 00:45:17.000
And there it is. So the same data, I've actually taken some of the internal ID fields out here, because of course I can customize it in Excel. And also what I've done is I've added this heat map in Excel for telling me the, the different levels of accessibility

00:45:17.000 --> 00:45:22.000
based on the week identity score red or green.

00:45:22.000 --> 00:45:29.000
I just set up that formatting in Excel very easily. I also reformatted this content as percentages.

00:45:29.000 --> 00:45:45.000
You can imagine if you've got custom reports that you need to do. Let's say you're reporting up to executive level one customers reporting up to GRC system on a regular basis, and they need to put in their own data they need to change or transform some

00:45:45.000 --> 00:45:54.000
of this data that can all be done in Excel. and there's a tool actually in Excel here for transforming your data.

00:45:54.000 --> 00:46:08.000
And it's all based in the API so you can call any of those things. I showed you there. I'm here on the dashboard, your engagement data, your workspace data, all of that is available to the API to pull down.

00:46:08.000 --> 00:46:13.000
So this is another way you can spread the work.

00:46:13.000 --> 00:46:21.000
But you haven't, obviously, in that case, it's for, particularly for development teams and for different levels of your development pipeline.

00:46:21.000 --> 00:46:29.000
But the Guardian also have content authors and content authors won't necessarily be using an API.

00:46:29.000 --> 00:46:42.000
And we've also got this Chrome extension that I told you about the our toolkit. The our toolkit is a browser based plugin, it's free to use. Again, we're using the ark rules.

00:46:42.000 --> 00:46:58.000
The rule set version five. And so, we're able to run the same tests, and your content authors, for instance, get a very easy to use to that will test your page and show you visually, the results.

00:46:58.000 --> 00:47:06.000
It's beautiful about this is it doesn't clutter up the page with all of the issues of once in fact you can toggle between them.

00:47:06.000 --> 00:47:16.000
And you get these nice visualizations of issues such as the tab order, Intel here. They don't necessarily need to understand where character or all of accessibility either.

00:47:16.000 --> 00:47:23.000
Things are very simple, they're organized around content topics, if you like structure media, etc.

00:47:23.000 --> 00:47:33.000
and it can also be used by developers, as I mentioned before, in their local environment to run tests as they need to.

00:47:33.000 --> 00:47:49.000
And. And so that, for instance, you find issues on your accessibility dashboard. You then tell your developers look on these pages are in these templates we've got issues.

00:47:49.000 --> 00:48:05.000
The thing is, this is not monitoring you you test on demand you can test fix the issues retest run it as much as you want, keep testing, and we actually have a give you a quick view, we actually have a new version of the tool kit, which were just building

00:48:05.000 --> 00:48:17.000
at the moment, which actually, it supports multiple brands is built on a new platform, and it's going to be installed on Firefox, Safari, etc, that's available there as I said a free to.

00:48:17.000 --> 00:48:37.000
So, these are the different ways that the Guardian, and this all enterprises media enterprise can spread the effort out their organization. So they get to a mature state where everybody is testing the right roles are testing the right things.

00:48:37.000 --> 00:48:42.000
And if we go back to our presentation very quickly.

00:48:42.000 --> 00:48:55.000
This is an example of a mature assembly line it's just a very simple example. We see a lot of tools I showed you there. but you have the art tool kit for instance testing the code as it's being developed.

00:48:55.000 --> 00:48:58.000
And then you might have the ark Analytics API.

00:48:58.000 --> 00:49:02.000
Testing commits before the code, makes it to production.

00:49:02.000 --> 00:49:08.000
And maybe pushing back accepting and rejecting based on accessibility policies.

00:49:08.000 --> 00:49:16.000
And then our monitoring is seeing the end result, what's coming out. And if this process is working well they should find no issues.

00:49:16.000 --> 00:49:27.000
What were they you find issues they can then push them back set new policies, etc. Obviously there are different ways I showed you a bunch of tools to do Zapier etc There are different ways to do all these things.

00:49:27.000 --> 00:49:37.000
But that's one simple example of where you get a good effective mature accessibility assembly line.

00:49:37.000 --> 00:49:53.000
I just before quickly before I move to the, the questions and answers I just wanted to show you one last thing on our desktop PC here and this is a brand new feature that we've just launched and going to open up doors and run the risk of doing a jaws

00:49:53.000 --> 00:50:07.000
demo. So, go there at all are,

00:50:07.000 --> 00:50:19.000
We are the being monitored with arc. So, to our identity now because in our customer, it's being monitored on a regular basis.

00:50:19.000 --> 00:50:25.000
And we've turned on our new jobs Connect features you may have seen this on our release.

00:50:25.000 --> 00:50:36.000
Last week, but essentially by majority that I bought my thing that you would fight back.

00:50:36.000 --> 00:50:45.000
If I hit that before.

00:50:45.000 --> 00:50:55.000
To look at what happens over here we go to our biz bro sites

00:50:55.000 --> 00:51:09.000
is the feedback that I give goes directly on to the domain dashboard for the site. So whatever I filled in in that form comes here. The point is, it's very easy for the user to do.

00:51:09.000 --> 00:51:13.000
You saw it there it's very non disruptive for the user, very quick and easy.

00:51:13.000 --> 00:51:20.000
It goes to the right people who goes to the accessibility people whose job it is to look after the accessibility of the site doesn't go to so inbox.

00:51:20.000 --> 00:51:28.000
And it's there with your domain monitoring data. So you can look if a user has raised an issue.

00:51:28.000 --> 00:51:42.000
You can look directly at the data in your testing and say has this been raised before waiting we see this isn't a priority, etc where we're adding it right in the right context.

00:51:42.000 --> 00:51:51.000
And this, this is really I talked about maturity. This is really moving beyond compliance to creating a relationship with your end users, a positive relationship.

00:51:51.000 --> 00:52:02.000
A lot of programs accessibility programs require some means of getting feedback from your users allowing them to report issues, etc. And this is a great way of doing that.

00:52:02.000 --> 00:52:04.000
so I just wanted to show you that as well.

00:52:04.000 --> 00:52:20.000
And so that's it that's all the enterprise tier items that I wanted to show you will now open it up to some questions.

00:52:20.000 --> 00:52:29.000
Let's see. Got You got one of the pie chart and other graphics based results, accessible.

00:52:29.000 --> 00:52:31.000
Yes, all of them are accessible.

00:52:31.000 --> 00:52:51.000
We obviously being a CPG we put an absolute premium person first to make sure that all of these elements in the arc interface are fully accessible. We do have assistive technology users who use the platform all the time supporting the platform, selling

00:52:51.000 --> 00:52:58.000
the platform and so on. They use it on a daily basis, and they find it very accessible,

00:52:58.000 --> 00:53:10.000
how to connect There's another question about connecting the JIRA Service. So, yeah, I mean, you do those connections in Zapier itself. I lost my Zapier again.

00:53:10.000 --> 00:53:13.000
There's too many windows here.

00:53:13.000 --> 00:53:14.000
Oh, here we go.

00:53:14.000 --> 00:53:25.000
And creating connections is very easy so you set up connection, I might show you a different one here.

00:53:25.000 --> 00:53:29.000
That might be a little bit simpler.

00:53:29.000 --> 00:53:36.000
So there is one I've created for Slack channel, and you create a connection to arc.

00:53:36.000 --> 00:53:52.000
Right here, and you use details from your account to to authenticate and then where you've got your action send the message to slack. You connect up to your slack account, your walk through it event, essentially step by step things up here, okay, you

00:53:52.000 --> 00:53:57.000
choose your slack account set up your action.

00:53:57.000 --> 00:54:08.000
It will expose the data from arc for instance from the issues the assertion title assertion description, and then what's really nice is you can add your own text around that.

00:54:08.000 --> 00:54:23.000
Here, you can write around that data, which is just a variable here and choose your parameters, and then it comes out in your Slack channel here.

00:54:23.000 --> 00:54:32.000
Another question, what rules does your pro bowler use to check a website for accessibility violations. So that's where I was talking about the rule set.

00:54:32.000 --> 00:54:35.000
We obviously support.

00:54:35.000 --> 00:54:49.000
x, and our own art move but we have our article five, and that covers all aspects of accessibility. So includes things that are manually checked, as well as things that are automatically checked.

00:54:49.000 --> 00:54:57.000
And as I said for

00:54:57.000 --> 00:55:03.000
your.

00:55:03.000 --> 00:55:09.000
That's the complete rule set all the various tests that we run.

00:55:09.000 --> 00:55:22.000
And as I said at that covers really all use cases, lower building on it all the time.

00:55:22.000 --> 00:55:36.000
So, that we are with this new rule set so the question is, are they based on act or wakening well a bit of both. They were originally obviously built on on waco requirements, but we've moved them increasingly.

00:55:36.000 --> 00:55:47.000
So with this latest release. We've moved it very close to the AC T or act use cases.

00:55:47.000 --> 00:55:53.000
Obviously that is still an evolving project so there's not absolute one to one.

00:55:53.000 --> 00:56:14.000
But we are developing that with a goal to having, you know, a very standard rule set that tests the same as everything else tests.

00:56:14.000 --> 00:56:26.000
Marissa:  Does anybody else have any other questions for Charlie.

00:56:26.000 --> 00:56:33.000
Okay, well. Oh wait, hold on, we have one other question. Oh no, nevermind. You all know.

00:56:33.000 --> 00:56:44.000
Thank you everybody for joining in the chat. We do have the opportunity for you to schedule an appointment with Peter.

00:56:44.000 --> 00:56:52.000
If you have any questions about arc he can connect you to salesperson, get you a demo, or you can email it after the call.

00:56:52.000 --> 00:57:13.000
you will be getting a copy of the on demand webinar through your email.