Skip to main content

AMP data export

  • Updated

This topic describes AMP data export types.  Data exports provide specific data for an AMP instance. If you require such data, be as specific as possible when filing your data request. 

On this page:

Export types

AMP has four data export types. Each subsequent export goes one level deeper into your AMP data, in the following order:  

  1. Asset summary export

  2. Report summary report

  3. Module export

  4. Instance violation report

Depending on the use case, the data export might not have all the files.

To request a data export, you can submit a AMP Custom Reporting form through fresh service.

Asset summary export

 The following table describes the purpose and noteworthy columns of the asset summary export.

Purpose

A high-level report of all Assets in the AMP organization. The data includes overall counts of Reports, Modules, Violations, and Use Cases. The export also summarizes the compliance score across all configured standards for the Asset.

This report provides a solid foundational overview of the accessibility profile for a given Asset.

Noteworthy columns

  • Total reports

  • Total modules

  • Total violations

  • Relevant compliance score columns

Report summary export

The following table describes the purpose and noteworthy columns of the report summary export.

Purpose

A high-level report of all AMP Reports for the respective Assets. The data includes overall counts of Modules, Violations, and Use Cases. The export also summarizes the compliance score across all configured standards for the specific Report.

This report provides a foundational overview of the accessibility profile for a given Report.

Noteworthy columns

  • Asset ID and name

    • Use this to cross reference with the asset summary report.

  • Report name

  • Report type

    • List of components that created the instance violations for the report.

  • Total modules

  • Total violations

  • Relevant compliance score columns

Module export

The following table describes the purpose and noteworthy columns of the module export.

Purpose

An extracted list of modules within a given AMP report, where a row has the information for a Module for a given AMP Report.

To use this report, filter by a specific Report ID to exclude other Report data.
Limitations

  • Doesn’t support images

  • A file is generated for every 200k records
Noteworthy columns

  • Report ID and name

    • Use this to cross reference with the report summary report.

  • Module name

  • Location

  • Viewport size

  • Module assignee

  • Type

  • Path

  • Total violations

Instance violation export

The following table describes the purpose and noteworthy columns of the instance violation export.
Purpose

An extracted list of instance violations within a given AMP report, where a row has the information for an instance violations for a given AMP Report.

To use this report, filter by a specific Report ID to exclude other Report data and use the module ID column to map related modules for a set of instance violations.
Limitations

  • Doesn’t support images

  • A file is generated for every 200k records
Noteworthy columns

  • Report ID and name

    • Use this to cross reference with the report summary report.

  • Module ID and name

    • Use this to cross reference with the module report.

  • Media type

  • Instance ID

  • Violation name

  • Description

  • Severity

  • Noticeability

  • Tractability

  • Note

  • Patter/Global

  • Page number

  • Defect ID

  • Defect status

    • Typically used to track if the issue is open for fixed.

  • Defect comments

    • Relevant if the AMP organization was integrated with Jira.

  • Advisory
 
 

 

Related articles

Comments

0 comments

Article is closed for comments.