An organization is the root level within AMP which contains all Users, Projects, AMP Tests and Reports for a group of users, e.g., Acme Corp. This is the location which also houses the Organization Testing Control settings, which centrally deploys a uniform testing setting for all users. This ensures that all testing for an organization is congruent across multiple users. An Organization Administrator is assigned to each organization to control these settings and other organization level configurations. Standard Users do not have access to this area within AMP.
A child organization is an organization that is created within an organization. This allows AMP to be completely scaleable when deployed in large companies and organizations. Each child organization can operate interdependently with all of the capabilities of a parent organization. For example, a large university can have its root organization and each campus can be created as a child organization. This allows individual campuses to operate independently while still being part of an overall university wide accessibility initiative.
A Project is simply a group of reports and AMP Tests. Projects can be used to model diverse IT applications or keep track of multiple versions of a single system. For example, a website project might contain a variety of different reports relating to the PDF content on the site, a Flash movie on the site and the general content templates on the site. Projects can also be used to group subsequent audits or spiders of a site over time. For example, a single project can keep 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. Users create AMP Tests in order to set up repeatable audits. This allows users to enter the desired Test settings once, allowing them to conduct the same audit multiple times. Each time an AMP Test is run, a new Report is generated. This is especially useful when conducting regression testing, or re-testing the same content. Additionally, this allows users to perform meaningful side by side report comparisons, and provides for accurate trend analysis.
A report is a snapshot of compliance at a given point in time. Reports are the result of a compliance test for a specific media type and for a specific set of modules.
A module is an individual component of an IT system. The module forms the basic atomic unit of an IT system that is defined for testing. For web sites and applications, a module is generally a single page and maps directly to a specific URL. In addition, a module can be a component of a webpage such as the header, footer, navigation structure, etc. For software systems, this component is most often an individual dialog or UI class. For hardware systems, this set of components is the combination of individual controls, standard control groups and displays on the device.
A violation is a violation of a specific best practice. For example, a violation of the best practice “Provide alternative text for images” occurs whenever an image element that does not contain alternative text is found on a web page.
A Global violation is an issue that occurs on every module within an AMP report. This equates to violations that are site / application wide which would occur on each page. Rather than have testers repeatedly enter the same violation on each page/module that it occurs on, they can simply enter it once and it is applied to each module in the report. Common Global violation examples include issues with the color pallet for the site, session time-outs, lack of skip navigation, an issue within the header or footer, etc.
A Pattern is a violation of a best practice across multiple modules. AMP reports provide the ability to enter patterns consisting of multiple violations because, in practice, pattern violations occur in sets. This is because developers typically create things using the same development style so that, for example, their data tables, forms, etc. are usually constructed in a similar manner. Every time they create such content, they often commit the same violations on each table. For this reason, AMP reports provide the ability to enter multiple violations ("Pattern members") for each pattern.
The occurrence rate is the rate at which a violation occurs in a given report. The occurrence rate is based on the percentage of modules within a report that contain a violation of a specific best practice. The occurrence rate is defined as the total number of modules that exhibit a particular 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 the best practice “Provide alternative text for images.” The occurrence rate for these violations is seventy percent (70%), or fourteen modules which exhibit the requirement violation divided by the total number of twenty modules.
The compliance rate is the percentage of modules within a report that comply with a certain standard or guideline. The compliance rate is defined as total number of modules that do not exhibit a violation of a standard or guideline divided by the total number of modules in a report.
For example, consider a report that contains twenty modules that is being evaluated for compliance with the requirements of Section 508 - Section 1194.22 Paragraph A. Amongst these modules, fourteen modules contain a violation of a best practice that relates to Paragraph A. The compliance rate for Paragraph A, then, is thirty percent (30%), or six modules which comply with the requirement divided by the total number of twenty modules.
In AMP different technologies are broken down into technology platforms and media types. Media Types have to do with general development platforms such as Web, Adobe Acrobat, Adobe Flash and Java Software. Each of these media types has a number of accessibility best practices that have been developed by SSB BART Group; these best practices are grouped into media types. This grouping makes it easier to understand which aspect of accessibility each best practice applies to, for example, the Web > Images media type has to do with the use of images within web pages and applications. The Flash > Forms media type has to do with the use of forms in Flash movies.
Best practices are the specific accessibility requirements that are validated as part of the audit process. In contrast to the media types, which are general in nature, best practices are specific and must include testable criteria for determining compliance with the best practice.
AMP Icon Directory
|AMP Best Practice Section|
|The Add Widget Icon|
|The Edit Action icon for projects and reports|
|The Permissions Action icon for projects 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 Projects|
|The clear 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.|