Link to Definitions copied to clipboard



The highest entity in the axe Monitor taxonomy (Enterprise > Organization > Project). The Enterprise is administered by the axe Monitor System Administrator who manages the axe Monitor server settings and creates Organizations within the Enterprise.


The second level entity in the axe Monitor taxonomy (Enterprise > Organization > Project). An Enterprise can contain one or multiple Organizations. An Organization in axe Monitor can model organizations within your business. Organizations are discrete entities, and Administrators and Members of one Organization do not have access to data from other Organizations. Projects are created within an Organization.


The third level entity in the axe Monitor taxonomy (Enterprise > Organization > Project). In axe Monitor, work gets done in the context of Projects. An Organization can contain one or multiple Projects. Projects are typically created to analyze the accessibility and/or quality of a specific website or web application – or portion thereof – and monitor progress toward improvement.


The Scan is the process in axe Monitor that browses a site in an automated fashion following every link in a page recursively according to the link level set when you create a Project. Scanning in axe Monitor is controlled by the Scan and Scan Settings pages in Project Settings where a user can define how deep to scan and what content to include or exclude.


The Analysis process in axe Monitor parses the content retrieved during scanning and checks it against the selected practices for conformance to the chosen rules. When you analyze a Project in axe Monitor it is acting upon a copy of the code captured during scanning and not on the original website code.


Document Object Model provides a tree representation of the HTML document. Axe Monitor uses a DOM to perform part of its analysis.

Headless Browser

A headless browser provides the same functionality as a browser to get and interpret a web page without the display functionality. axe Monitor uses a headless browser to perform part of its analysis.


Full Name

This is the first and last name of an axe Monitor User which appears in the Welcome message in the upper right portion of the axe Monitor toolbar.


The Username is used to log in to axe Monitor. It is typically an email address.


Axe Monitor's System, Organization and Project Dashboards are high-level executive summaries that provide a visual description of the current level of accessibility of web assets and show trends over time.

Custom Standard

Deque axe Monitor has built-in capability to perform evaluations based on the W3C WCAG 2.0 Levels A and AA standards, as well as US Section 508 guidelines. Axe Monitor's out-of-the-box default analysis standard is based on WCAG 2.0 Level AA. Users can select all of or parts of any of the Section 508 and WCAG 2.0 standards to create a Custom Standard which can be applied at an Organization-level or the Project-level. Custom Standards can also include Custom Rules.

Custom Rules

Custom Rules are specific to an organization's policy or requirements that may not be directly related to accessibility. The custom rules in axe Monitor are written in JavaScript. A custom error message, priority and remediation help can be provided for a custom rule.


Page Group

A group of pages within a Project that allows you to create axe Monitor Reports for a sub-set of pages within a Project.

Template page

A page designated in a Project's Scan properties that axe Monitor uses to evaluate template areas (also called scope definitions) such as header, footer, and navigation areas .

Project Scores

A Project Score is calculated by formula based Page Health. Pages are categorized as Critical, Serious, Fair or Good based on the "worst" issue on the page.


Action Drop Down

When issues are selected from the Issues page the Action Drop Down appears above the Issues list, which provides access to relevant actions related to working with issues.


Axe Monitor marks an issue's Severity as a Violation if it is an error that can be definitively identified by automated means; for example: an image with no alt attribute, or a form with no explicitly attached label, or poor color contrast.

Potential Violation

A Potential Violation must be verified by a person to conclude whether or not it is an actual Violation (such as text that has style markup applied and appears to have been used as a heading but is not tagged as a heading, or a table that may be a data table but has no header cells).


An Issue's Severity describes whether it is a Violation or a Potential Violation.


An Issue Label is an optional piece of information that can be applied to an issue or groups of issues. Labels can be used to group issues by type or source (such as a particular use case script). Labels can be a helpful way of searching for and locating issues.

Description (Issue)

Each Issue type is assigned a short Issue Description which appears in the Project and Issues Reports.


An Issue's Priority describes how serious an issue is to a site's accessibility: Critical, Serious, Moderate, and Minor.


When an Issue is reported, its Status is marked as Open. An Issue's Status can be changed to Fixed or Ignored.


Page Health

Pages are categorized as Critical, Serious, Fair or Good based on the "worst" issue on the page. If a page has one Critical issue, the page is Critical; one Serious issue, the page is Serious; one Moderate issue, the page is Fair; and if a page only contains Minor issues, it is Good.