WorldSpace Project Dashboard

There are two means of reaching the project dashboard: either by clicking the Project from the 'Home' tab, or going into the Project Dashboard.

example of project dashboard with scan results

This page is one of the most important in seeing the breakdown of your scan results. By default it shows a snapshot of the last month of data, which can be changed by manipulating the date range.

Snapshot Results

more detailed example of snapshot results in project dashboard

The Snapshot Results are the shorthand means of seeing progress, and generally the overall score that is seen by the Web Accessibility Team.

  • Score: This is a percentage score that is based on the issues and page health.
  • Issues Per Page: This shows an average of how many issues are on each page. The higher this number, the more numerous your issues are across the website.
  • Pages:
    • Total: This is not a total of issues, but a total of pages last scanned.
    • Critical / Serious / Moderate / Good: How many pages (not issues) have issues of either rank. Remember that a 'Good' Page may not be a fully accessibility page.

    Automated Issues

    More detailed example of automated issues in project dashboard

    This section is one of the greatest assets provided by the Project Dashboard as it gives the shorthand version of issues found during the last scan.

    • Grouping: Each section is grouped by the type of issue it is related to WCAG, 508 Compliance, or ARIA. These may be vastly different based on what type of scan has been generated or how many issues are within the pages.
    • Standard: Simply defines what part of web accessibility each of these items relate to.
    • Priority: How damaging these issues may be considered. The table can be sorted from Critical to Minor, or vise versa.
    • Description: A shorthand version of what the issue is in simple programming terms. The More information button button brings forth a popup on the page that lists the issue's specific guideline in WCAG, remediation, and an example on how the issue can appear and how to fix it.
    • Issues: These numbers identify how many times the issue was found during the scan. A redundant issue that may be built into the website's framework and repeats across the website will be counted for every single page. The link attached to each number connects to the Issues section and shows a filter based on that specific rule. More on how to utilize the resulting information will be under Finding and Understanding Project Issues. This table can be sorted by via this column.
    • Pages: These numbers represent how many pages within the scan were pinged with these specific issues. This information is incredibly important for finding repetitive issues that may be built into the website framework and found on every page. The links attached to each number connects to the same information as it does the Issues' link.
    • % of Pages: Gives a percentage visual to how many pages within the scan were affected by specific issues.