WEBVTT

1
00:00:00.330 --> 00:00:04.740
[Speaker 1] Welcome! In this training, we're going to give a quick overview of an audit report

2
00:00:04.740 --> 00:00:10.320
in AMP. Let's get started. This dashboard
view [of an audit report] provides a compliance summary of

3
00:00:10.320 --> 00:00:13.920
your audit. It displays several widgets
with different information and metrics

4
00:00:13.920 --> 00:00:17.369
and it also includes a number of
additional views that offer greater

5
00:00:17.369 --> 00:00:22.289
detail. Towards the top left, AMP shows
the organization that you're in, the

6
00:00:22.289 --> 00:00:27.359
asset being tested, and then the specific
report that you are viewing. Below that,

7
00:00:27.359 --> 00:00:31.710
we have the 'Review' section, which offers
links to detailed views that explain

8
00:00:31.710 --> 00:00:36.660
what was tested, which use cases were
evaluated, and compliance tables for

9
00:00:36.660 --> 00:00:40.769
different standards. For a quick
refresher on modules: sites and

10
00:00:40.769 --> 00:00:45.019
applications today are based on
templates patterns and reusable pieces.

11
00:00:45.019 --> 00:00:50.039
Modules are distinct components of a
site or application. A module could be a

12
00:00:50.039 --> 00:00:54.600
page, or specific part of a page. It's a
unique collection of design and coding

13
00:00:54.600 --> 00:00:59.460
elements that can be tested from a code,
or Assistive Technology perspective. The

14
00:00:59.460 --> 00:01:03.390
'Fix & Prioritize' section contains
information to help you fix violations

15
00:01:03.390 --> 00:01:08.610
and prioritize that work. This includes a
'Priority' view which takes you to a table

16
00:01:08.610 --> 00:01:13.740
of different violation types ranked by
their weighted priority. There's also the

17
00:01:13.740 --> 00:01:18.120
'Patterns' view which lists violations
that are global in nature or patterned

18
00:01:18.120 --> 00:01:23.229
throughout the system. The 'Violations' view allows your

19
00:01:23.229 --> 00:01:29.340
violation instances to be grouped by
module, violation type, or pattern.

20
00:01:30.480 --> 00:01:35.200
Next, you have the 'Status' and 'Description' sections which show the progress of

21
00:01:35.200 --> 00:01:39.180
different types of testing, as well as
any relevant notes from the testers.

22
00:01:39.180 --> 00:01:44.320
Under the 'Compliance' header you have the number of violation instances as well as

23
00:01:44.320 --> 00:01:48.100
failed best practices, so you can know
how many different types of violations

24
00:01:48.100 --> 00:01:53.440
exist. The Compliance Score is calculated
from the modules, or pages, captured

25
00:01:53.440 --> 00:01:57.490
in this report. To learn more about the
algorithm we use to calculate your score

26
00:01:57.490 --> 00:02:02.020
and what it means, select the 'Support'
link at the top of the page in the

27
00:02:02.020 --> 00:02:07.380
navigation menu. A star next to the score
means that testing is not yet completed.

28
00:02:07.380 --> 00:02:11.770
The 'Report Deliverables' section offers
various downloadable documents that

29
00:02:11.770 --> 00:02:16.660
summarize the testing results. The 'Top
Issues' widget displays your highest

30
00:02:16.660 --> 00:02:20.920
priority violations and gives users the
option to sort the table by a given

31
00:02:20.920 --> 00:02:25.990
violation's Occurrence Rate, Severity
Noticeability, and Tractability, or, how

32
00:02:25.990 --> 00:02:29.980
difficult it is to fix. Then, there's the
'Compliance Health by Ruleset' widget,

33
00:02:29.980 --> 00:02:34.350
which shows your compliance with
specific rule sets.

34
00:02:34.740 --> 00:02:39.780
For a breakdown of violations, select
'Violations Instances' to see the details

35
00:02:39.780 --> 00:02:45.240
and status. By selecting the linked best practice, under the violation column, a

36
00:02:45.240 --> 00:02:50.220
modal window opens showing a description of the best practice violated, along with

37
00:02:50.220 --> 00:02:54.870
the Severity, Noticeability, and
Tractability ratings. The additional tabs

38
00:02:54.870 --> 00:03:00.080
provide compliant and non-compliant code examples, recommendations for fixing, a

39
00:03:00.080 --> 00:03:07.150
view of affected modules,
a list of mapped standards,

40
00:03:07.150 --> 00:03:10.920
and a list of applicable tests.

41
00:03:11.940 --> 00:03:16.110
To get started right away on your
remediation efforts, we always recommend

42
00:03:16.110 --> 00:03:19.770
going off the specific recommendations
our consultants have provided for you.

43
00:03:19.770 --> 00:03:23.820
But, generally speaking, it's a good
approach to focus on fixing all the

44
00:03:23.820 --> 00:03:28.980
issues on your most important modules
first: like your 'Home' or main page. To do

45
00:03:28.980 --> 00:03:33.700
this, you can go to the 'Violations
Instances' view, and sort according to module

46
00:03:34.720 --> 00:03:42.440
[End Screen] Contact Us! Reach out to our team to learn more about the information provided in our AMP reports and the best actionable steps to take following an audit. info@levelaccess.com (800) 889-9659