Getting Started with WebYes Accessibility

WebYes Accessibility is a website accessibility checker designed to help you meet WCAG compliance standards. It scans your site to identify accessibility issues, provides AI-driven suggestions for fixes, and generates detailed audit reports to demonstrate compliance.

Features

1. Scans and checks for WCAG 2.2 level A, AA, and AAA (only in paid), ADA, and Section 508
2. Identifies the affected pages, prioritises issues based on criticality, and suggests AI-generated solutions
3. Allows you to export reports in .xlsx format
4. Includes a checklist for manual checks
5. Provides the ‘Inspector tool’, a unique feature of WebYes Accessibility that helps you identify elements that need fixing and also allows you to hide elements on your webpage, making changes much more easily.
6. Automatic monitoring of websites.

Getting Started

Go to the WebYes website, click on ‘Products,’ and then select ‘WebYes Accessibility’.

WebYes Accessibility

Paste your website URL and click on the ‘Scan Now’ button to get started.

Scan now button

The scan will begin as shown below.

Scanning URL

Once the scan is done, you will see the WebYes Accessibility dashboard as shown below.

WebYes Accessibility dashboard (before sign-in)

Certain data, like ‘Issues per page’, ‘Accessibility over time’, etc. can be accessed once you sign up.

Sign up to get access

Alternatively, you can also click on the ‘Try for free‘ button to get started.

Try for free button

You will see a page as shown below. Paste the link of your website and click Next to get started.

Paste URL option

You will be redirected to the sign-up page as shown below. After filling out the details, click on the ‘Sign up for free’ button, or you can use a Google account to sign up.

WebYes Accessibility sign-up page

The scanning process will then begin, as shown below.

Scanning Webpage

Once the scan is complete, you will see the whole WebYes Accessibility dashboard along with its data.

WebYes Accessibility dashboard

Once you are in the WebYes Accessibility dashboard on the top navigation bar, you will see four options, including ‘Dashboard’, ‘Pages’, ‘All Issues’, and ‘Checklist’.

Dashboard

In the Dashboard section, you can see the overall accessibility score of the website.

Dashboard overview

On scrolling down, you will see details like the changes detected from the last scan, a pie chart for ‘Most common issues found on your website’, ‘Quick wins’, ‘Issues per page’ and Accessibility over time’ graph.

Quick Wins

The Quick Wins section highlights the accessibility issues that will have the greatest positive impact on your website when fixed. Rather than reviewing every issue individually, Quick Wins helps you prioritise improvements that can significantly increase your overall accessibility score with minimal effort.

Also, you can enable scheduled scans to make sure that the scans are done automatically on the month and date you set.

Scheduled scan option

Click on the ‘Enable’ button to view scheduled scan options. You will see the following page, as shown below.

Scheduled scan edit option

If you need Level AAA checks, you can enable them here. You can also set a credit limit for the scheduled scans and choose whether the scan should run weekly or monthly, as well as select the specific day. After setting your preferences, click the ‘Save changes’ button to schedule the scan.

Pages

In the Pages section, you will see page-by-page issues listed along with respective URLs and the number of issues in each of them. Click on it to get a detailed analysis.

Pages section

Clicking an issue opens its detailed view, where identified issues are grouped into categories such as Development, Design, and Content. Users can filter issues by category and view their details. The page also provides ‘Verify in extension‘, ‘View in Inspector’ and ‘Export’ options, allowing users to inspect individual issues or click ‘View in Inspector’ at the top to review all issues at once.

View all issues together in the Inspector option

Inspector button

The inspector interface will be as shown below. The red dot highlights the element, and you will see a ‘Generate solution’ option to view solutions generated by AI.

Inspector tool

Also, you will see a ‘Hide element’ toggle, which can be turned on to hide elements by clicking them.

Hide option functionality

From the above GIF, you can see that once the toggle is turned on and the ‘submit’ button is clicked, it becomes hidden, making it easier to resolve and highlight other element issues. This feature can also be used when there is a need to hide elements. For example, some websites may have cookie consent pop-ups that can cause inconvenience while resolving issues. To avoid that, you could simply hide that element while in the Inspector mode.

There is also an option to view the focus order of the elements as shown below.

Focus order option

You will then see the focus order listed on the left side of the page, while it is simultaneously illustrated in real time on the webpage to the right, as shown below.

Focus order list and illustration

All Issues

The All Issues section is divided into three sub-sections:

• Confirmed checks – Automated and verified issues that require action
• Needs review – Automated potential issues that require manual validation
• Manual checks – Issues that must be evaluated manually

Confirmed checks section

Here, you also have an option to filter out issues along with categories according to your needs.

Issue filter

Both the Confirmed checks and the Needs review sections can also include Best practices, which are recommendations that improve usability and accessibility, but are not part of any official WCAG success criterion.

Needs review section

These issues (tagged best practices) do not cause direct non-compliance, but fixing them helps create a more structured, predictable, and user-friendly experience, especially for screen reader and keyboard users.

Each best practice:

• Is clearly labelled as Best practice
• Does not have a WCAG conformance level
• Is optional, but strongly recommended
• Helps prevent future accessibility issues

For example, based on the image above, “All page content should be contained by landmarks” is considered a best practice. While WCAG does not strictly require this hierarchy, following it makes content easier to understand and navigate using assistive technologies.

Why Best Practices Matter

Although best practices are not mandatory for WCAG compliance, addressing them:

• Improves overall content structure and readability
• Enhances screen reader navigation
• Reduces the risk of future WCAG violations
• Helps teams build accessibility-first design habits

By clearly separating WCAG issues from Best practices, WebYes Accessibility allows teams to prioritise compliance-critical fixes while also encouraging continuous accessibility improvements.

Also, there is a ‘Manual checks’ option. Click on it to resolve issues that need manual checks. After checking each issue, select the checkbox of either ‘Mark as resolved’ or ‘Not applicable’, and then click on the ‘Save changes’ button.

Manual checks option

Checklist

This section gives you the checklist based on WCAG guidelines and accessibility levels. You can use this report to see how many pages are affected by which guidelines. After accessibility issues are resolved, redo a scan and go through the checklist again to make sure they are resolved.

Checklist page

Final Thoughts

You can now check for accessibility issues using WebYes Accessibility. If you want to know the difference between WebYes and WebYes accessibility, refer to the WebYes and WebYes Accessibility comparison.