AMP Anywhere is an approach for AMP integration that allows AMP functionality to be integrated into virtual any enterprise development, testing or authoring workflow. The AMP Anywhere approach provides for direct access to AMP services via web services or directly through code level integration with AMP’s Java API.
The AMP Anywhere approach allows for AMP testing to be provided in any testing, development and authoring environment with minimal integration costs. For instance, consider a web developer with an account on AMP who wants to provide full accessibility testing for standards such as WCAG 2.0 or Section 508 on a currently deployed system. The web developer already has a set of test scripts recorded in a leading functional test system such as Selenium, HP Quality Control or IBM Rational Tester. To add accessibility testing, the web developer can add a single evaluation call at any point in their functional testing script to evaluate the page currently under test for accessibility. This call will allow AMP to test the page and return to the functional testing system the overall number of accessibility violations found within the page. From the accessibility test results the developer will be directed to a URL within AMP which allows them to view a report on the individual violations, review the accessibility Best Practices, and utilize SSB’s Recommended Changes to quickly remediate inaccessible pages using industry standards for accessibility.
This integration of AMP into accessibility testing allows developers to quickly evaluate a site’s level of compliance, pinpoint and evaluate the severity of any non-compliant pages and quickly remediate any issues that are reported by AMP. All this can be done without the need to create a new, redundant set of testing scripts specifically for accessibility – leveraging the current functional testing investment in place at the organization.
The AMP Anywhere approach can also be used to include AMP testing services into virtually any extensible development or browser environment including Internet Explorer, FireFox, Safari, Eclipse, Rational Application Developer, SharePoint Designer, TeamSite Content Management System, Visual Studio, Adobe Dream Weaver, Adobe Flash, Microsoft Word, Microsoft Excel and Microsoft PowerPoint. These integration points allow for content to be made accessible as part of the standard document publication workflow at any organization.
For organizations with custom development or build environments SSB also provides AMP users the ability to access AMP via direct Java API. This includes access to a preconfigured AMP client and the InFocus accessibility testing engine. The InFocus engine is written in pure Java allowing accessibility testing to be integrated directly into any workflow across any operating system platform. Integration directly via Java API allows accessibility tests to be carried out at exceptionally high speed and allows for greater flexibility and better runtime access to the accessibility test record for the specific item being tested. This ensures AMP can be accessed through a standardized, object-oriented, API built on an open architecture.
Centralized Configuration and Data Escrow
The AMP Anywhere approach ensures that all end points of the organization test with the same set of centrally defined and updated accessibility requirements. This ensures that all stakeholders are testing and reporting against a single, unified set of requirements whether testing is occurring in a plug-in, toolbar, InFocus Desktop directly via AMP or when accessing AMP via a web service.
The AMP Anywhere approach also ensures that all compliance data is escrowed directly in AMP. This provides a method for readily sharing issues with other developers or exporting them into a QA database where users can track the status of issues – for example Open, Fixed and Ignored on a per user basis. Integration with QA systems allows for issues to be assigned to individual project members for remediation and investigation, commented and collaborated on or otherwise analyzed. For example, developers may wish to filter issues by page, label, status, assignee or tag to facilitate easy management of large issue lists. From a project management perspective this also allows for tracking of all compliance data and collaboration with site or application owners on scope definitions for remediation.