AMP Report Navigation (Advanced View)

  • Updated

Enterprise-level accessibility initiatives demand comprehensive reports that are tailored to specific roles within an organization. AMP supports this requirement by providing detailed reports across a number of parameters, including views of standards-based compliance levels, best practices for identified violations, affected modules, and violation prioritization. These reports allow organizations to document current accessibility status and compliance rates and create a prioritized project plan for addressing issues. Along with high-level report data and compliance scores, AMP reports include:

Compliance Level Reporting, which provides compliance officers, product managers, webmasters, and other project stakeholders with the high-level standards conformance information. Information at this level can be used to easily identify key areas which lack conformance to the relevant public standards. This information can then be used to help drive educational efforts within an organization.

Page Level Diagnostic Reporting, which provides support for detailed page-by-page reporting of violations that have been detected during the testing process. Descriptions and notes pertaining to a violation can be edited and customized based on tester’s discretion to clearly define the issues that must be addressed for compliance. AMP also provides guidance on how to fix violations in-line with the diagnostic information. This guidance significantly decreases the time, budget, and resources allocated towards remediation efforts.

Intelligent Violation Modeling, which provides different views of the overall list of accessibility infractions identified within a report. Users can view overall violation summary information, violations by standard, and violations by priority. This information is extremely valuable when estimating and evaluating required remediation efforts.

AMP allows an organization to rapidly increase their compliance levels with limited budget and resources.

AMP Report Action Icons

AMP Reports now contain Action Icons on the upper right side of the screen. These icons provide actions to a number of different options and report modifiers including Report Permissions which is available from any section of an AMP Report. The following Action Icons are universal while the section dependent modifiers, which will be covered in their relative report sections below, are not.

Advanced report view with the Action Icons highlighted

Report Permissions

The Report Permissions Action Icon is a Universal Action Icon, meaning it appears on every section of an AMP Report. This icon opens the Edit Report Permissions Modal, allowing you to modify the user permissions on the report. AMP controls user access to AMP Reports through a user permissions system. This system is comprised of three possible permission levels:

  • No Access - Users given this permission will have no access to the report; if this is applied at a project level the user will not have access to either the project or the reports the project is comprised of.
  • Viewer - Users given “Viewer” permissions are allowed to look at the report but are unable to make any changes to the report.
  • Editor - Users given “Editor” permissions have complete access to the report and can view as well as make any changes they would like to the report.

Learn More about AMP Permissions

Selecting the Edit link in the title bar of Report Permissions launches the Edit Report Permissions module. This module allows users to add, edit, and remove Report permission.

  • Report Owner - Allows you to designate any organization member as the report owner
  • Other Report Permissions:
    • User Name - Any users with permissions to the report will appear here with a drop-down menu to the right of their name; this drop-down allows you to choose which of the three possible permission levels to give the specified user
    • Add People From Current Organization - Activating this list results in all the current organization users appearing with the aforementioned drop-down to the right of their names
    • Add Someone By Email - This form field allows you to batch add multiple users. You can even add non-AMP users; however, they can only receive “Viewer” permissions

Editing Report Permissions is also how you can distribute an AMP Report. This distribution is done by giving “Viewer” or “Editor” permissions to additional individuals through the “Edit Report Permissions” Module. By using the “Add Someone By Email (Comma separated list)” form field you can distribute the report to multiple people at once, You can even distribute the report to non-AMP users.

  • Non AMP users who are given access to a report will be able to view the specific report and nothing else, they will not be able to make changes to the report, and cannot be given Editor permissions

Advanced Report Permissions View


Switching Technology Platforms Within a Report

Users have the ability to navigate between the two technology platforms within the AMP report by selecting the desired technology choice within the navigation structure of the report. When the technology is toggled the user is brought to the most relevant location within the report for the newly chosen technology.

Amp Report View with technology platfor toggle highlighted

Report Contents

AMP Reports contain six separate sections that are navigable utilizing the secondary navigation bar

  • Overview - Provide a report level compliance summary and general information about the report. There are also several report level widgets which provide visual information and metrics for the results contained within the report.
  • Document Inventory - The document inventory section of a report depicts all non-web file types that were detected during the automated spidering/scanning of a website or application. You will also be able to perform PDF Testing from within the document inventory.
  • Compliance - Provides an overview of the current compliance levels for all of the accessibility standards that were used during the testing process on the report.
  • Modules - Provides a list of all of the modules that have currently been added to the report. The module summary provides a high level violation count for each module. Additionally, there is an 'Actions' column provided for each module which allows users with write permissions the permission to the report to delete the module or edit the module. Users can also perform manual testing by choosing the test icon within the Manual Testing column.
  • Use Cases - Provide a repository for functional testing results. Use Cases are created and assigned to an assistive technology tester. The tester is able to perform the testing and enters all of the functional testing results into the proper use case. Creating use cases is not required in order to generate a report.
  • Patterns - Provides a list of issues that were detected that occur on more than one module within the report (pattern) or across the entire report (global).
  • Violations - Provides a cumulative list of all of the best practices that have been violated across the entire report. The list of violations can be viewed in several different formats.

Report Overview

The Report Overview is the default screen that will be loaded when a report is viewed in AMP; it is comprised of a title, a bookmark option, breadcrumb navigational aid, Action Icons, and widgets.

Report Overview Screen

Default Overview Widgets

By Default the following widgets are loaded on the AMP Report Overview page.

  • Report Info - The Report Info widget provides basic information about the report, such as:
    • Report Name - The name provided by the user who manually created the report, or the name for the report derived from the AMP Test which created it.
    • Created - The date on which the report was created.
    • Technology Platform - The type of technology that was tested. AMP reports are based on a single technology platform.
    • Report State - This is the state that the report is currently in. Created means the report has been created, and is currently in the testing process. Published indicates that the report is completed and finalized.
  • Overall Report Compliance - This widget shows the total compliance score for the report, based on a roll-up of all the standards in the report. 
  • Compliance Health By Ruleset - This widget shows how compliant (as a percentage) the tested material is in context to each individual standard ruleset.
  • Top Issues - A value-weighted list of the top active issues identified for this report, sorted by priority. This prioritization model, derived using AMP’s SNT ratings, provides a list of best practices that provide the most benefit if fixed first.


Add Widgets

The Add Widgets Action Icon provides you with a drop down list of available widgets that can be placed on the Report Overview Dashboard. The list of available widgets can be found on the AMP Widgets page.

'Edit Report' Action Icon

Advanced View of Edit Report Dropdown options

  • Copy Report - Allows anyone with viewer or editor access to the report to create an exact copy or clone of the report. This is especially helpful during regression testing, or when users want to alter a report while retaining the original copy. When a report is copied, a user is given the following options:
    • Keep use case results: If checked off, this option migrates all of the results of Use Case Testing to the new report. If unchecked, the results of Use Cases will not be kept, but the Use Cases themselves will remain.
    • Keep State: This will allow your report to remain published once it is migrated over. If you leave this unchecked, the new report will not be published.
    • Keep Module Completion Status: This will keep any manual testing that has been completed. If this is unchecked, the new report will need to be manually tested again.
    • Keep Module Assignments: This will keep the user who was assigned to each module as the module tested. If this is unchecked, all module assignments will be cleared.
  • Edit Report Properties - Anyone with editor access to the report will be able to edit the report basics information.
  • Delete Report - Anyone with editor access to the report can delete the report. This removes it permanently from the Organization, and it is not recoverable by the user.

Report Overview Navigation List

Report Advanced view with Overview Options highlighted

The “Report Views” section of the navigation pane contains five links:

  • Test Reports - Brings you to the Test Dashboard
  • Documents and Permissions - Launches the “Documents and Permissions” modal which shows you any documents attached to the report, as well as all the users with permissions to the report and what their permissions are.
  • Report PDF Overview - Gives the details of all PDFs that are part of the document inventory.
  • Mapped standards and best practices - Launches the “Mapped standards and best practices” modal which lists every standard and the connected best practices that are active for the report.

Document Inventory

The document inventory report depicts all non-web file types that were detected during the automated spidering/scanning of a website or application. The document inventory section of an AMP Report contains sortable summary information about the documents found on the site. This information includes:

  • Document - The file location of the document
  • PDF Module (PDF Only) -
  • Linking Page - The name of the module (page) that linked to the given document
  • # Linked Pages - The number of pages that link to the given document
  • Technology Platform - The Technology Platform of the given document
  • Tested(PDF Only) - Tells you whether or not the page had undergone automated testing
  • Tagged(PDF Only) - Tells whether or not the PDF is tagged.
  • Violations(PDF Only) - Number of accessibility violations found in the document
  • Actions (PDF Only) - Action Icon to initiate automatic testing

It shows how many PDF files were detected, how many were tested, and how many that were tested were tagged. From the document inventory AMP users have the ability to initiate the automated testing of one or many PDFs found within the report. Additionally, users can filter the document inventory report to show all or specific file types for review.


The document inventory table has a built-in filter that allows users to filter specific document technology platforms. This allows users to see one specific document technology platform at a time. This feature is available at the top right of the table with a drop down menu labelled Technology Platform. From the drop down menu, select the desired technology platform you would like to filter and then select the filter button, symbolized with the funnel iconography. This will result in the table only displaying the desired technology platform.


Compliance Section

  • The “Compliance” section of an AMP Report provides a detailed look at compliance results, broken down by the various individual standards.
  • Navigating to the “Compliance” section of the website will result in additional navigation options in the “Report Contents” modal of the navigation pane.
    • These additional navigation options are in the form of individual links to each standard that is active in your instance of AMP, as well as links to Best Practices that will bring you to the Best Practices section.
  • The compliance section of an AMP report also includes a new set of options titled "Compliance Actions" which provides a link to download the compliance tables as a spreadsheet.

Compliance Widgets

  • Compliance Health by Ruleset.
    • The “Compliance Health by Ruleset” widget is comprised entirely of a horizontal bar graph
    • The Y-axis lists the selected individual ruleset.
    • The X-axis is a scale for compliance health, ranging from 0% to 100%
    • Compliance Health is determined from the combined average compliance rate of each individual standard requirement.
  • Detailed Compliance Results

The Detailed Compliance Results table displays detailed compliance for an individual standard selected via the additional navigation options on the left side of the compliance section.

    • Name - Gives the name of each individual standard requirement (Also known as a paragraph or success criteria)
    • Modules - This column shows the number of compliant modules over the total number of modules.
    • Total points - The Total Points column converts the compliance rate for each individual standard requirement to a point value. Each individual total point value is then combined for an overall point value for the report.
    • Compliance Rate - Compliance rate is calculated by taking the number of modules that do not contain any accessibility violations for the associated individual standard requirement divided by the total number of modules within the report.

Compliance Section List

Report Advanced view with Compliance Options highlighted

The Compliance Views Action Icon provides links to select standards for the Detailed Compliance Results Table, as well as options to export the compliance tables as Excel spreadsheets

Report Modules Section

Report Modules page

The “Report Modules” section of an AMP Report is comprised of a single table containing every individual module in the report, as well as an additional navigation modal labelled “Module Actions.” This is the location where specific violations can be reviewed on a per module basis. Each instance of a violation will be mapped to a Best Practice which provide inline actionable guidance on the violation.  You can use the 'change columns' modal to add and remove columns. 

The "Modules" section of an AMP report, comprised of an editable column table, can have the following columns:

  • Check Box Selection Column - This column lets you select one or more modules at a time.
  • Name The name of the individual module, which is also a link to the “View Module” page which provides additional details about the module.
  • Location - Displays the actual location of the module, for a webpage the location would be the URL for the specific webpage.
  • Thumbnail - This shows any uploaded thumbnails or captured thumbnails for a module. 
  • Path - This shows the path of the module if a user has added it when creating a module or editing it. 
  • Violation Count - Displays the Number of violations found in the module
  • Tester - Displays the name of the user assigned to perform module testing, defaults to the report owner.
  • Manual Testing - Provides a link to the "Manual Testing Tree". (for more information on the "Manual Testing Tree" as well as performing manual testing please visit Perform Manual Testing with AMP
  • Actions - Contains links for editing or deleting a module

Edit Module Actions Icon:

  • Add Module - Launches the “Add Module” modal, which allows you to add new modules to the report
  • Add Module(s) - Launches the “Add Module(s)” modal, which allows you to add multiple modules to the report at once
  • Scrub Violations - Launches the scrub violations modal, which allows you to search for and delete a set of violation occurrences from a report.

Module Views List

Report Advanced view with Module Options highlighted

The Module Views List provides links to the following actions.

  • Report Modules - Brings you to the 'Report Modules' Page described above. 
  • Module Details - Loads the detailed view from the “View Module” page but for every module in the report on one page.
  • Module Testing Status - Launches the “Module Testing Status” modal which displays any modules you have been assigned to test and the status of said tests.

In the 'Report Deliverables' Section, you can also find: 

  • Modules Details Excel Report - Link to download the Module Details tables as an Excel spreadsheet
  • Generate Module List - Link to download the list of Modules as a PDF document
  • Modules by Total Violation - Link to download the Modules table sorted by number of violations as a PDF document
  • Modules Detail - Link to download the Module Details tables as a PDF document

Use Cases Section

The “Use Cases” section of an AMP Report is a table that lists all the use cases attached to the report as rows. This table is comprised of the following columns:

  • Name - Name given to the Use case.
  • Goal - This is the purpose of the use case.
  • Operator - User assigned to complete use case testing.
  • Assistive Technology Type - displays which assistive technology (JAWS, ZoomText, etc) was used to perform the use test.
  • Tester - Name of user who is assigned or performed the testing.
  • Rating - Provides a 1-5 rating to determine the level of accessibility based on actual use testing.
  • Description - Description documenting the success or failure of the use case
  • Actions - Icon-based links to perform, edit, delete, or clear a use case.

Use Case Edit Icon

Accessing the Use Cases section of an AMP Report prompts the “Use Case Actions” icon to appear with the other Action Icons.

  • Add Use Case - Opens the Add Use Case Modal

Use Cases View List/Report Deliverables

  • My Use Cases - Displays all use cases assigned to you
  • Show All Use Cases - Prompts the View All Use Cases modal to open, displaying a more detailed look at each use case.
  • Use Case Results - Prompts the View All Use Cases Result modal to open, displaying the same detailed look as the View All Use Cases modal, but also containing a section documenting all the results of all the use cases separately.
  • Use Cases Excel Report' - Downloads the use case table as an excel file
  • Appendix D - Use Case Results' - Downloads a use case results table as an excel file
  • Show All Use Cases PDF - Prompts you to download the detailed use case results in a PDF document

Patterns Section

Report Patterns Page

The “Patterns” section of an AMP Report provides a list of issues that were detected that occur on more than one module within the report (pattern) or across the entire report (global). Patterns and Globals are broken into two separate tables, however the tables have almost identical structures:

  • Check Box Selection Column - This column lets you select one or more modules at a time.
  • Name - The name given to the pattern or global, which is also a link to either the “View Global” or “View Pattern” pages. Both of these pages share the structure as well and provide additional details about patterns such as which modules they appear on.
  • Best Practice Count - Lists the number of best practices that are applicable to the violations in the pattern/global
  • Module Count (Patterns only) - gives the number of modules the violation occurs in
  • Actions - Contains links for editing or deleting a pattern/global

Patterns Edit Action Icon

  • Add Global - Launches the “Add Global” Modal which allows you to add global violation issues. You are able to add multiple violations to one global pattern.
  • Add Pattern - Launches the “Add Patterns” Modal which allows you to add patterns of violation issues. You are able to add multiple violations to one pattern, as well as select which modules the pattern applies to.

Patterns Views List/Pattern Deliverables

  • Globals Excel Report - Downloads the “Globals” table as an Excel spreadsheet
  • Patterns Excel Report - Downloads the “Patterns” table as an Excel spreadsheet
  • Globals and Patterns Detail - Launches the “Globals and Patterns Detail” modal which is a table listing each global and pattern violation, the description of the violation, and the number of modules the violation occurs in.
  • Globals and Patterns Detail – Excel Report - Downloads the “Globals and Patterns Detail” table as an Excel spreadsheet.

Violations Section

View all instances Report View

The Violations section of an AMP Report provides a list of all of the best practices that have been violated across the entire report. The Violations Action Icon provides a means to view the list of violations in several different formats through the violations drop down.

Violations View List/Violations Deliverables

Report Advanced view with Violation Options highlighted

  • Report Violations - This is a web view summary of all best practices violated in the report. 
  • Violations Summary - A simple table that gives the best practice in violation, which links to the relevant best practice page in the Best Practices section, the technology platform of the best practice, , and the occurrence rate for the best practice violation, both as a percentage of and number of modules the violation occurs on
  • Violations Detail - This format displays the full best practice content for every violation, all on one page
  • Violations by Priority - Provides a table that ranks the best practice violations by weighing the SNT ratings for each violation, as well as the violation frequency, and creating a priority variable based on those metrics. Like the “Violation Summary”, it contains columns for Best Practice and Technology platform.
  • Violations by Standard - Provides a table that documents the accessibility violation, the technology platform, and which accessibility standards are compromised by the violation
  • Violations Instances - Provides a table that lists in detail every single violation instance in the report.

Where do I look if I am a compliance officer or Web Master?

Overview and Compliance Section

  • Compliance officers and Web Masters would most likely spend a lot of time reviewing the Overview and Compliance sections of the report. This will provide a high-level indication of level of compliance with the overall standards and requirements (paragraphs / success criteria).
  • This compliance information can then drive educational efforts to address requirements that regularly receive lower percentage scores.

I am a Developer / QA person and need to see the specific violations

Modules Section

  • Developers and Q/A folks would benefit most from the Modules section of the report.
  • This is the location when specific violations can be reviewed on a per module basis
  • Selecting a module name under the modules tab will provide all of the specific details of violations detected
  • Each instance of a violation will be mapped to a Best Practice which provide inline, actionable guidance on the violation

Patterns Section

  • The location where violations that are repeated across multiple modules will appear
  • Violations that are site/application-wide are also listed here. These issues are typically addressed first since fixing a single issue can drastically improve the overall compliance rates for the entire report

Where do I get started with planning remediation?

Violations Section

  • The violations section will provide a view of all of the Best Practices that were violated by the report.
  • Violations by Priority will prioritize issues that are typically fixed quickly with little effort or education required. Violations can be viewed by priority for a suggested order in which to fix issues. This will help to develop an intelligent plan for remediation efforts.
  • Correcting the high priority violations will produce the quickest and largest overall positive impact on compliance levels.
  • Educational efforts can also be driven through the Violations section of the report which will call out the most commonly occurring violations.

Can I view Assistive Technology (AT) Test Results?

Use Cases Section

  • Note, the creation of Use Cases is not required in order to generate an AMP Report.
  • Testing performed with AT devices, also known as functional testing, can be reviewed under the use cases tab.
  • AT tests enter their testing results and comments into each use case.
  • Functional testing results reflect a users experience when accessing the content with industry-standard AT devices.

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request