Testing content with AMP

On this page:

• How do I test content in a secure environment or content that requires user interaction?
• How do I perform manual testing?
• How do I test a public website?

How do I test content in a secure environment or content that requires user interaction?

Access Assistant is a browser extension for Chrome, Firefox, and Microsoft Edge that allows users to do automatic and manual accessible testing in context, directly in the browser. This testing toolbar is fully integrated with AMP. All assets, reports and modules created within the toolbar, and all testing results, are saved to AMP for tracking and management.

The Access Assistant 2.0 release introduced a new user experience that is identical across all supported browsers. This version of the toolbar also makes use of the new and improved Access Engine accessibility testing library. This library includes a comprehensive set of Javascript-based, automated accessibility tests that will be used in AMP and all other integrated products.

• Get Started with Access Assistant

How do I perform manual testing?

Please visit the Performing Manual Testing page to learn about manual testing in AMP.

AMP provides the ability to perform formal and informal compliance testing across a variety of accessibility standards and technologies. Several testing workflows are provided by AMP which drives a key concept of AMP Anywhere. Based on Level Access’ proven Unified Audit Methodology, AMP’s testing support extends from the ability to perform in-browser, quick page tests to scanning complete, enterprise-level websites. AMP supports a wide degree of formality in testing, from quick, page specific tests to full, formal compliance audits of systems.

How do I test a public website?

Set up a repeatable AMP crawler

Create an AMP crawler - For testing scenarios that need to be repeatable, users can create an AMP Test. This is the testing workflow that allows users to configure the testing specifications that can be saved and run repeatedly in the future. For example, users can create an AMP Test to test their website and schedule the test to run automatically every month. At the end of the year, the user will have 12 reports for comparison of compliance over time.

Learn more about AMP Crawlers.

Create a new AMP report

Users can create a new report by navigating to an Asset Dashboard when working within an existing AMP Project, or by choosing the Create New Report link located within the Quick Links widget on the Dashboard.

Be sure to select the correct media Type when creating your report. This can't be changed once the report is created.

When testing non-web content (e.g., PDF documents, Flash/Flex content, hardware, etc.), users can begin the auditing and testing process by manually creating a report, accessing the Asset Reports widget, and selecting the Create Report link. This approach is sometimes necessary when testing will be completed with AMP Toolbars. In this case, users can create an AMP Report ahead of time so that they can choose to send the testing results from the AMP Toolbars directly into the report(s) that they have previously created.

When users manually create a new report, they create the initial container for the storage and analysis of testing results. Once a new report is created, users can navigate to the Modules section of the report to add a single or multiple modules to begin the testing process.

Users can add modules by three main options:

1. Test and add Module via URL'- Add modules to the report via one URL at a time.
2. Test and add module via Source Code - Add modules by uploading local files (.html) for testing.
3. Add Module Manually - Add modules by manually defining their Name and Location. This is the option chosen when working with non-web content.