The code examples exist to provide a glimpse into the nature of the issue (and how to fix it), but the rest of the Best Practice entry - such as the description and recommended changes - is equally important in understanding what the problem is and how to resolve it. In most instances, the code examples provided in AMP will be relevant to the Best Practice and violations generated in the reports. In cases where the code example does not seem directly relevant, it is likely that it should be viewed in context with the rest of the Best Practice information to understand the violation more fully.
- < Back to Home
-
AMP FAQs (Frequently Asked Questions)
- Why do the compliance graphics on the Overview page of my report show less than 100% compliance, even though when I go to the Modules page, I don't see any violations?
- How do I familiarize myself with the terminology used in AMP?
- How do I create a Child Organization?
- How do I edit a Child Organization's properties?
- How many pages should be included in a representative sample for testing?
- Why are my AMP reports showing Compliance Rates Charts for Industry Standards I don't want?
- I see line numbers in the report results. What do they mean?
- What is meant by Report State?
- I can't find a violation in the source page, what gives?
- The compliant (or non-compliant) code example seems irrelevant, why is that?
- Why do the compliance graphics on the Overview page of my report show less than 100% compliance, even though when I go to the Modules page, I don't see any violations?