Needs Review Section: An Overview

The Needs Review section in WebYes highlights potential accessibility issues detected during automated scanning that require manual verification. These are cases where the tool can identify a possible issue, but human review is needed to confirm whether it is actually an accessibility problem.

After the scan is complete, WebYes lists these items separately so users can review each occurrence and decide whether it should be treated as an issue or marked as “Not an Issue.”

Items in the Needs Review section also affect the accessibility score. If an item is reviewed and marked as “Not an Issue,” the score will increase.

Needs Review in WebYes

The Needs review section can be accessed from:

• The dashboard summary card shows the number of items that require review.
  

• The All Issues page, under the Needs review tab.

• The Pages section, where page-specific review items are listed.

Issues in this section are not automatically included as confirmed accessibility issues until they are manually reviewed.

Reviewing Issues

Selecting a needs review issue opens the detailed review panel.

The review panel displays:

• The affected element
• Element details and selector information
• The affected page URL
• Guidance on why the issue was flagged
• Steps explaining how to manually verify the issue

Users can then choose one of the following options:

It’s an issue

Select this option if the element does not meet accessibility requirements.

Once confirmed:

• The issue is moved to the Confirmed checks section
• Accessibility reports and scores are updated accordingly
• The occurrence is treated as a verified accessibility issue

Not an issue

Select this option if the flagged element is accessible and does not require fixing.

Once marked:

• The occurrence is removed from the active needs review list
• The issue is moved to the Marked as non-issues section
• The occurrence is treated as reviewed

Reviewed Items in Confirmed Checks

If a needs review occurrence is marked as an issue, it will also appear in the Confirmed checks section.

Reviewed occurrences are identified with a user-reviewed indicator/icon beside the issue name. This helps distinguish manually reviewed issues from fully automated findings.

Opening the issue again allows users to:

• View the reviewed status
• Change the decision later if required
• Mark the occurrence as a non-issue

Marked as Non Issues

The Marked as non-issues page stores all reviewed items that were determined not to be accessibility problems.

Users can reopen these items later and change the status back to an issue if required.

Why Manual Review is Important

Some accessibility checks cannot be reliably validated through automation alone. For example:

• Contrast issues caused by overlapping elements
• Content that depends on visual meaning
• Elements requiring contextual understanding
• Interactive components that need human verification

Manual review helps ensure more accurate accessibility reporting and reduces false positives in scan results.

To begin using WebYes Accessibility, refer to the “Getting Started with WebYes Accessibility” guide.