This article includes important AMP concepts and key icons to learn as you familiarize yourself with AMP.
On this page:
The table below includes descriptions for key AMP concepts.
Organizations are the top of the AMP structure and contain all your users, assets, AMP tests, reports, and organization-level settings.
Each AMP customer has at least one organization. Some Enterprise customers, like a university with multiple campuses, may need child organizations.
A child organization is a secondary organization within a parent organization, allowing AMP to be scalable when deployed for large companies and organizations. Child organizations operate independently with all the capabilities of a parent organization.
For example, a large university can have a parent organization with each campus as child organizations. This allows individual campuses to operate independently while still being part of an overall university wide accessibility initiative.
An asset represents a property (such as a website or app) and contains reports and AMP tests. For example, an asset created for your website might contain reports and AMP tests for your website's PDF content, videos, or content templates.
Assets can also be used to group subsequent audits or spiders of a site over time, such as keeping track of the 1.0, 1.1, 1.2, and 2.0 reports for a site.
An AMP test is a saved accessibility audit configuration which you can use to set up repeatable audits. You can configure settings like viewport size, max page count, authentication, and more. Each time you run an AMP test it generates a new report.
AMP tests are useful when conducting regression testing, re-testing the same content, performing side by side report comparisons, and report trend analysis.
Reports are the result of an AMP test for a specific media type and for a specific set of modules. Reports offer a number of sortable views and a dashboard full of informational widgets, such as compliance percentage, report deliverables, top issues, and more.
A module is an individual element of a digital or physical property defined for testing. For web sites and applications, a module is generally a single page and maps directly to a specific URL.
Other examples of modules include:
|A violation is non-compliance with a specific best practice. For example, a violation of the best practice “Provide alternative text for images” occurs if an image element doesn't contain alternative text.
A global violation is a violation that occurs on every module within an AMP report. This equates to violations that are site/application wide.
Common global violation examples include issues with the design system, session time-outs, lack of skip navigation, or an issue within the header or footer.
Patterns allow users to group violations on elements, such as forms or data tables, that appear on multiple pages within the asset. Identifying patterns is useful, because remediating the violations on patterns will typically result in the greatest increase in compliance with the least amount of effort.
For example, elements like data tables are usually built the same way across a website, so all data tables on the website likely contain the same violations. Creating a pattern for violations on data tables prevents testers from having to create the same violation on each data table.
The occurrence rate is the rate (%) at which a violation occurs in a given report. The occurrence rate is calculated by taking the total number of modules with a particular best practice violation divided by the total number of modules in a report.
For example, consider a report that contains twenty modules. Among these modules, fourteen contain a violation of a best practice. The occurrence rate for these violations is seventy percent (70%).
The compliance rate is the percentage of modules within a report that comply with a certain standard or guideline. The compliance rate is calculated by taking the total number of modules without a violation divided by the total number of modules in a report.
For example, consider a report that contains twenty modules. Among these modules, six comply with a specific best practice. The compliance rate for that best practice, then, is thirty percent (30%).
In AMP, different technologies are broken down into technology platforms and media types. Media Types are general development platforms such as Web, Adobe Acrobat, and Java Software. Each of these media types has accessibility best practices that have been developed by Level Access. For example, the Web>Images media type is for images within web pages and applications.
Best practices are specific accessibility requirements that are validated by audits. Best practices are specific and must include testable criteria for determining compliance with the best practice.
An example of a best practice for the media type "images" is "provide alternative text for images".
AMP icon directory
The table below includes descriptions of important AMP icons.
|AMP Best Practice Section.
|The Add Widget icon.
|The Edit Action icon for assets and reports.
|The Permissions Action icon for assets and reports.
|The widget level configuration icons (maximize, configure, and delete).
|The edit icon found under the Actions column of many AMP tables.
|The delete icon found under the Actions column of many AMP tables.
|The Bookmark icon found on AMP Reports and Assets.
|The delete Use Cases icon found within the Use Cases section of an AMP Report.
|The run icon is found throughout AMP anywhere there is an action that you can run.
|The View Test icon is found throughout AMP anywhere there is an ability to view testing results, such as accessing the manual testing tree after manual testing is completed.