Back to Basics Guides

Introduction

AAArdvark makes it easy to see what’s going wrong across your site. This guide walks you through how issues are grouped and how to read site-level data.

Whether you’re looking for contrast problems, missing alt text, or anything in between, this is where you start to learn the basics on how to understand issues.

You must run a scan on the site you wish to view issues for first, or this menu item will not be accessible.


Basic Concepts

There are a few important concepts to understand before diving into the Issues tab.

Issues

Accessibility issues on your site are mapped to specific WCAG Success Criteria, such as insufficient contrast or missing descriptive text. Think of an issue as a category of problem that may have multiple occurrences.

Instances

An instance is a specific example of an issue on your site. For example, a missing alt text issue may have instances on several images across multiple pages.

We use advanced pattern matching in an attempt to group like issues together. This grouping enables developers to better identify the source template for grouped instances, even if they occur on multiple pages of your site.

Issue instances that appear on several pages.

Issue Categories

Issues in AAArdvark are categorized into three groups to help prioritize remediation:

  1. Errors
    These are confirmed issues detected by our automated scanner or identified through manual testing by an accessibility expert. Errors represent clear accessibility failures and should be prioritized for resolutions.
  2. Warnings
    Potential issues that require human review to confirm if they are actual problems. For example, a warning might flag text that could have insufficient contrast under certain conditions, which needs to be checked manually.
  3. Notices
    Turning on notices is optional, and notices are helpful reminders to review common elements that could cause issues. For instance, the automated scanner can check if an iframe has a title, but cannot determine if the title is accurate and descriptive. Notices prompt you to manually verify such details.

Tip: Start by addressing Errors, as they represent the most critical and actionable accessibility issues, then move on to Warnings and Notices as part of a comprehensive review.


Issue Trends and Data

Site Statistics

The Site Statistics in the dashboard provide a summary of the issues on the site. A graphic will display issues by impact, and from there, the issues can be visited.

Active Issues will be tracked as well, displaying the most common issues found on the site.

Additionally, Average Instances/Page with the most problematic pages will be presented in this view.

Site Statistics displays issues by impact, active issues, and average instances per page.

Count History

The Count History section in the dashboard provides a graph view of issues and issue instances over time, based on the most recent scan. 

A graph for the issues can be seen, showing issues scanned over time.

An issue count history showing the issues recorded over time since August 2024.

Another tab with issue instances can be viewed, showing issue instances scanned over time. 

Issue instances count history is displayed in a graph, from August 2024 to April 2025.



Accessibility Issues for a Site

After a site scan or manual auditing, discovered issues will be listed under the Issues tab on your Site’s Dashboard.

Viewing Issues

For each identified issue, you’ll see the following details:

  • Issue Number: The unique identifier for the issue (e.g., Issue #1).
  • Severity Level: The criticality of the issue, such as Critical, Very High, High, Warning, etc.
  • Detection Status: Was the issue found through automated scans or created manually?
  • Instance: The number of occurrences of this issue across the site during the audit.
  • Date: The scan date when the issue was identified.
  • Description: A short overview of the issue.
  • Assignee: The name of the team member responsible for resolving the issue. If unassigned, it will display “Unassigned.”
  • Comment: The total number of comments added on this issue. 
The image shows the issue list with summary details for each issue identified in the scan.
Issues detailing the issue number, severity level, detection status, instance, date, description, assignee, and number of comments.

Filtering Issues

Use the filters in the Issues tab to search, sort, and prioritize accessibility issues. Filters include severity, status, assignment, and more, helping you focus on what matters most.

Overview of filtering issues.

Search Issues

Search for issues by entering keywords, WCAG criteria, or descriptions. For example, you can search for ‘color contrast’ or a specific success criterion like ‘1.4.3.’

Sort Issues

Sort issues by priority to focus on what needs attention first. Priority is determined by:

  • Severity: How impactful the issue is for users
  • Urgency: How quickly the issue should be resolved
  • Instances: The number of times the issue occurs on your site

You can also sort issues by severity or chronological order.

Severity

Issues can be filtered by Severity, all of which is determined by the impact the issue has on the site users. The choices available are:

  • All
  • Critical
  • Very High
  • High
  • Moderate
  • Low
  • Warning

Type

The Type dropdown can be used to filter issues depending on whether they were caught in an Automatic scan, or added as a manual issue. The choices available are:

  • All
  • Automatic
  • Manual

Status

Issues can be sorted by Status, whether they are active, resolved, or not an issue. This allows users to discern what issues need resolving and are already resolved. The choices available are:

  • All
  • Active
  • Pending
  • Resolved
  • Not an Issue

Assigned To

To find out which issues are assigned to certain assignees, the Assigned To filter will allow users to select which assignee they want to filter by. Issues that have been assigned to other Workspace users will appear under the filter. If they have not been assigned to anyone, they will remain under the Unassigned filter.

The choices available are:

  • Anyone
  • Assigned to me
  • Unassigned

Success Criteria

Issues can be sorted by WCAG Success Criteria. Depending on the Success Criteria of issues captured on the site, either through automatic or manual audits, these criteria will be listed out on the dropdown to use as filters. 

Success Criteria dropdown depicting WCAG criteria for accessibility issues.

Pages

The Pages filter can be utilized to view the list of issues for specific pages or the overall site. You can also search pages by their slug.

This allows users to see what issues have been found on certain pages and address them individually.

The All Pages option under the AAArdvark Accessibility Issues filter.
Filter the issues by looking through pages in the dropdown.

Issue Details

Click an issue in the Issues List to open the detail view. This includes:

  • Description: A clear explanation of the issue.
  • Recommendations: Suggested solutions and examples.
  • Instances: A list of all places this issue occurs on your site.
  • Comments: Notes or discussions from your team.
  • Status: Whether the issue is Active, Resolved, or Not an Issue.

Use the Previous Issue and Next Issue arrow buttons at the top of the page to navigate between the Issue Detail pages.

Image displaying the issue details.
Details of an issue with information on what it means and how to fix it.

Issue Description Feedback

To leave feedback on an Issue Description, click Yes if you found it helpful, or No if you didn’t, under the “Was this helpful?” section.

If you choose No, a comment box will appear so you can share any suggestions for improvement. Our support team will receive and review your feedback. 

The image shows a comment box that opens up when you don't like the issue description.
A pop-up window accepting suggestions for improvement to submit for feedback.

Issue Instances

An issue is a type of accessibility problem (like missing alt text). An instance is each place where the problem shows up on your site. For example, if three images are missing alt text, that’s one issue with three instances. Instances help you see how widespread an issue is and where to fix it.

Issue instances can be filtered in two ways: 

  1. By the state of whether or not they require a review 
  2. The pages they appear on
A dropdown displaying the review status and pages where issue instances can be found and filtered by.

Filtering by Pages

Filtering Issue Instances by pages is especially useful if there are a lot of issue instances active on a site across numerous pages. One page, several pages, or all pages can be selected and displayed.

Filtering by Review Status

When you filter issues by whether they need review or not, only the relevant ones will show up, making it easier to focus on reviewing and verifying fixes.


Collapsible Instances

By default, all the instances are in expanded view. You can either collapse all instances together via the “Collapse All” option or use the collapse option on individual instances to collapse or expand an instance.

The Collapse All button is highlighted above the Issue Instance list on the Issue Detail page within AAArdvark.

Instance URL

Click the URL under ‘Seen On’ to open the linked page in a new tab or switch to Visual Mode for issue viewing.

An image that shows the options that get displayed when clicking the instance URL.

Viewing Instances on Pages

Instances can also be seen in a group of pages, allowing the ability to see where the issue appears with ease. Pagination is included if there are more than ten pages that the issue appears on.

Issue instances that appear on at least 11 pages

Ready to Fix and Manage Issues?

Now that you know how to view and understand issues, it’s time to take action. Head over to the Fix and Manage Issues guide to learn how to assign issues, review instances, update statuses, and track your team’s progress as you resolve accessibility problems across your site.


Still stuck?

File a support ticket with our five-star support team to get more help.

File a ticket

  • Please provide any information that will be helpful in helping you get your issue fixed. What have you tried already? What results did you expect? What did you get instead?
  • This field is for validation purposes and should be left unchanged.

Related Guides