Using the Dashboard

Link to Using the Dashboard copied to clipboard

The Dashboard screen provides a high-level overview of the assessment results in a graphic format. It is designed to provide valuable data to a broad audience, including executives, project managers, designers, developers and subject matter experts.

You use the Dashboard to view both manual evaluations and automated tests performed to give you complete visibility into your accessibility status across sites, apps and products. The dashboard enables you to review scores, severity, and remediation recommendations.

You can also view the test information, and generate your completed test run report using the Dashboard.

Screen shot example portion of the Dashboard
screen

Global Results

Accessibility Conformance

Accessibility Conformance graph reflects your product's conformance with accessibility standards and guidelines. It displays the number of assessments that are passed or failed based on your selection: Success Criteria or Deque Checkpoints. The default view is Success Criteria.

Note: The number of Deque Checkpoints depends on the standard and conformance level selected for the assessment. Another important point to note is that if the assessment includes 50 WCAG Issues but ALL are associated with 1 Deque Checkpoint, the Overall Accessibility Conformance % appears to indicate a high level of conformance. However, if the 50 Issues are Serious or Critical in nature, and affect multiple pages, the website or application may be unusable for users with disabilities. When determining the overall Accessibility Health and Level of Effort for Compliance, please refer to all data points. It only takes one "High Risk" User Impact Issue to increase your vulnerability to legal action.

[]{#userimpact}User Impact

By default we associate each identified Issue with a user Impact category: Blocker, Critical, Serious, Moderate, and Minor. Blocker, Critical and Serious issues are considered "High Risk" with greater effect on usability and greater vulnerability to legal action. When determining an assessment's overall Accessibility Health this data should hold significant weight.

[Blocker]{.underline}: This issue results in catastrophic roadblocks for people with disabilities. These issues will definitely prevent them from accessing fundamental features or content, with no possible work arounds. This type of issue puts your organization at high risk. Prioritize fixing immediately, and deploy as hotfixes as soon as possible. Should be extremely rare.

[Critical]{.underline}: This issue results in blocked content for people with disabilities, and will definitely prevent them from accessing fundamental features or content. This type of issue puts your organization at risk. Prioritize fixing as soon as possible, within the week if possible. Remediation should be a top priority. Should be infrequent.

[Major]{.underline}: This issue results in serious barriers for people with disabilities, and will partially prevent them from accessing fundamental features or content. People relying on assistive technologies will experience significant frustration as a result. Issues falling under this category are major problems, and remediation should be a priority. Should be very common.

[Moderate]{.underline}: This issue results in some barriers for people with disabilities, but will not prevent them from accessing fundamental features or content. Prioritize fixing in this release, if there are no higher-priority issues. Will get in the way of compliance if not fixed. Should be fairly common.

[Minor]{.underline}: Considered to be a nuisance or an annoyance bug. Prioritize fixing if the fix only takes a few minutes and the developer is working on the same screen/feature at the same time, otherwise the issue should not be prioritized. Will still get in the way of compliance if not fixed. Should be very infrequent.

Top Issues

The Top Issues data is generated to quickly identify the top accessibility issues (with the largest remediation impacts) detected based on either Deque Checkpoints or Success Criteria. This data is typically utilized when prioritizing training and accessibility knowledge gaps.

Viewing/Editing Test Info

Use this button to expand a handy reference section of information below that displays additional details about the test run, such as its Description, Standard, Session, timeout, Product, Release, Environment, Platform, Assistive technology and Units to test.

The summary section at the top of the Test Run Overview screen, with
each major feature
numbered

Note: You can use this button to edit the information when the test run is still In-Progress status.

Generating the Test Run Report

Use the button to view and print an HTML report for completed test runs.

The summary section at the top of the Test Run Overview screen, with
each major feature
numbered