Suhoolah User Guide

This guide explains how to use Suhoolah for web accessibility scanning, scheduled monitoring, design scans, and report review. Suhoolah is focused on websites and web-based digital services.

Before you start

Log in to Suhoolah using your account. If you do not have an account, create a trial account or contact A11y Oman for access. After logging in, use the dashboard to start scans, view previous jobs, download reports, and manage scheduled scans.

Start a regular web accessibility scan

1. Open Login to Suhoolah and sign in.
2. Go to the dashboard.
3. Choose the option to start a new accessibility audit or scan.
4. Enter the website URL or page URL you want to test.
5. Select the scan options available to your account, such as WCAG level, report type, or scan depth.
6. Submit the scan and wait for Suhoolah to process the results.
7. Open the completed report from the dashboard when the scan is finished.

Scan a single page

To scan one page, enter one complete URL, such as a homepage, service page, form page, or landing page. This is useful when you need a quick review of a specific page or want to confirm whether remediation work fixed a known issue.

Scan multiple URLs

To scan multiple pages, enter each URL separately in the multiple URL field or list, if your account has this option. Use one URL per line. This is useful for reviewing key pages such as the homepage, login page, search page, service pages, contact page, and important forms.

Use single-page scans and full-site crawls

An single-page scan or full-site crawl is a scan you start manually whenever you need it. Use this when a new page is published, after a fix is deployed, before a release, or when a team needs a quick accessibility review.

Set up a monthly scan

1. Go to the scheduled scans area in Suhoolah.
2. Choose monthly scan if it is included in your plan.
3. Add the website or URLs that should be scanned every month.
4. Confirm the scan frequency and reporting options.
5. Save the schedule.

Monthly scans help teams monitor accessibility over time and identify new issues that may be introduced by content updates, design changes, or code releases.

Set up an annual scan

1. Go to the scheduled scans area.
2. Choose annual scan if it is included in your plan.
3. Add the website or list of important URLs for the yearly review.
4. Select the reporting level needed for the annual review.
5. Save the schedule or request support if the annual scan needs a custom scope.

Annual scans are useful for accessibility reviews, management reporting, compliance planning, and measuring progress year over year.

Start a design scan

1. Open the design scan area from Suhoolah.
2. Upload the design file or screenshot supported by the tool.
3. Provide any page name, project name, or notes that help identify the design.
4. Submit the design scan.
5. Review the design scan results and use them to identify visual accessibility concerns before development.

Design scans can help teams review issues such as visual structure, contrast concerns, layout risks, and accessibility problems that can be addressed earlier in the design process.

View your reports

Reports are available from the dashboard after a scan is completed. Open the scan result to view issue details, severity, WCAG mapping, affected pages, and remediation guidance. If exports are available, download the report format that matches your role or meeting need.

Understand report levels

Developer report

The developer report focuses on technical details, affected elements, issue descriptions, WCAG references, and remediation steps. Use it to assign fixes and verify changes.

Management summary

The management summary explains accessibility status, risk, severity, progress, and business impact in a format that is easier for managers and decision makers to understand.

PowerPoint presentation

The PowerPoint report presents WCAG violation issues in a discussion-friendly format. It can be used in meetings, awareness sessions, project reviews, and executive briefings.

How to use remediation guidance

When a report links to remediation guidance, review the issue pattern, affected users, user impact, WCAG success criteria, testing steps, common mistakes, and recommended fixes. Developers and testers should use this guidance to fix and validate issues.

Good scanning practice

• Scan important user journeys, not only the homepage.
• Include forms, login pages, search pages, dashboards, and service completion pages.
• Run single-page scans and full-site crawls after major releases or remediation work.
• Use monthly scans for ongoing monitoring.
• Use annual scans for formal accessibility review and management reporting.
• Review both technical reports and management summaries so the right audience gets the right information.

Need help?

If you need help with scans, reports, remediation, or account access, use the support page or contact A11y Oman.

Get support | Contact us