- [Dave] Hello I'm Dave Musser, VP of Customer Success at Deque Systems, Inc. What I'm gonna be showing you in this video is how to get started with your WorldSpace Comply server. I'm going to show you from the very beginning, as if you first installed the system. When you first install WorldSpace Comply you will need to log in with our default user firstname.lastname@example.org. The password for this is admin. Once you've logged in to the system then what I recommend doing is going to Settings and System, Testing Standard. We're going to set our testing standard to be our axe-core ruleset 3.0.3. That's what's available in WorldSpace Comply 6.2.1. You can actually view the release notes for each of these to determine the changes in those different versions of the rulesets. I set this for the entire system and then now what I'm going to do, is I'm going to create my first organization. Organizations are holding objects if you will, for the different projects that you're going to have on your system. You can divide organizations up by agency, lines of business etc.. I then say Create an Organization and I can give this organization a name. Maybe I want to scan just my public-facing websites. So I'm going to do www for the name. In the description I'll say public, public facing websites. I'll select Add. You'll notice that right now the only users that are here are the ones that are our, out of the box users, if you will. I'm going to select this email@example.com. In a later video I'll show you how to add users to the system as well as how to configure it to talk to LDAP or Active Directory. I'll select Add. There are other options here. Primary e-mail domain, which means the domain of users that'll show up when you select Add. As well as the, display the share link on the report pages. I'm gonna go ahead and select Yes for this and I'll leave the other options blank. If you have questions on this or other options, simply select the help available on the page and that help will actually open up in Deque University for the user's guide for WorldSpace Comply. I'll select Create now. So this creates the organization. Once I've created the organization I will go to Settings and Organization. And now what I want to do is I want to enable that testing standard on this Organization and not our default out of the box. So I'm going to select the stock rules. I'll leave it at 3.0.3, and I'll select WCAG 2.0 Level AA. You could select Section 508. You could also enable the Best Practices if you'd like or you could have a custom standard. Custom standards are something that Dev Services at Deque can work with you on creation of. I will select Add Standard. And then I'm going to go ahead and make that Standard as a default by selecting the ruleset here, and then selecting Save as Default. I'm gonna go ahead and delete the other standard because I don't need to have that running on this Organization at all. Typically after you've set this part up when you're creating a new WorldSpace Comply server, you'll then go to Home and you'll say, I want to create an organization project. When you create an organization project the first thing you need to do is give it a name. I'm gonna call this Wings. I have a test site that I use called Wings Airline. I always recommend copying the URL for the site that you want to scan, versus typing the URL, because you could introduce spelling mistakes if you will and sometimes when you go to these websites they'll have a redirect that'll send you to a different URL. So you really want to make sure you're getting a true URL and not a redirect. After I put the URL I simply hit tab. By default it shortens the domain so it would only get things under wordpress.deque.cloud.com if I decided to not have this be a shorter domain. So I can specify the scan domain. If I wanted to allow this to go across and pick other domains underneath of the dequecloud, I can simply leave it as it is by default. I select the link level that I want to scan with. Typically on your initial scans I recommend starting with the, scan start page only. So that way you can verify the content. Also verify if there's any issues if you're on an internal server, as far as for proxies and things like that. So I say Create Scan. This is going to go ahead and start that scan and you'll notice in this UI it shows me the time it started. It shows me the percentage completed, the tasks that are pending. If any tasks are running it'll show me that and then the average time per task. Down below it shows for the entire server. The, since I've just created this server, there are of course no other scans running. But if this was an active server you would see other scans running potentially, as well as the priority of those scans. When the scan is complete you can then go to the Dashboard and Project and inside of this you'll have access to all of the information about this project. The accessibility score, similar to a grading scale. The number of issues per page, number of pages scanned, as well as the types of issues, the standard they fail against and the descriptions. We'll go more into projects during a later video. For now I just want to go ahead and go back to my scans, and I'm going to edit the scan and have it go just a little bit deeper inside of the website. Maybe a level three scan. I can also set the user agent and other settings here, if they're required for your website. I can then update this scan, and go ahead and start the scan. Typically this would be an administrator-type task when you're first doing your install of WorldSpace Comply. This is not really a subject matter expert-type task if you will. This is just simply making sure that WorldSpace Comply can get out to the websites and web applications that you want to scan, as well as setting the standard based on what your subject matter experts have told you that the standard should be or what you've worked out with Deque as far as if you're using a custom standard. Once this project completes you can then take and go back to the project dashboard, and you can view from the project dashboard how you're doing across multiple pages. One of the things that I will be showing in another video is for these projects, how can we determine what may be our common issues. So issues that are on every single page, so that we can reduce the issues and also focus in on the parts of your website, your templates if you will or your common pages. As well as I'll be showing how to log in to a website using a recorded script. If you have any questions on this or any issues as you're working with WorldSpace Comply, please email firstname.lastname@example.org. Thank you very much.