How To Do Manual Checks Using WebYes

Last updated on 02 March 2026

Manual Checks help you evaluate aspects of your website that require human judgment and real interaction. While automated tools can detect many technical issues, some accessibility, usability, and user-experience factors can only be verified through manual review.

These checks focus on how content behaves in real scenarios, including keyboard navigation, reading order, clarity of instructions, and overall usability, ensuring that your website works effectively for all users beyond automated validation.

Steps To Do Manual Checks

1. On the WebYes Accessibility dashboard, you can see the Manual checks area, which also shows the percentage of manual checks completed. Click on the ‘View checks’ option as shown below.

    View checks option

    View checks option

    2. Then you will see the issues listed out that come under categories like ‘Time-based Media’, ‘Adaptable’, ‘Distinguishable’, ‘Keyboard Accessible’, etc.
    Here, you can select the page you wish to do manual checks on, and once these checks are completed, you can either mark it as completed or mark it as ‘Not applicable’, as shown below.

      Manual checks option

      Manual checks view

      3. As you click the ‘Save changes’ button, you can see that the score has changed in the dashboard.

        Manual checks score

        Manual checks score

        Once all the checks are done in a category and changes are saved, then you can see that the status is changed from ‘Not resolved’ to ‘Resolved’. Once you get that status for all categories, you can see that Manual checks have a score of 100% in the dashboard.

        Category status updated


        Category status updated

        Manual checks score updated

        When to Mark an Issue as “Not Applicable” or “Mark as Resolved”

        Let’s take the example below. When we click on the issue named ‘Audio-only and Video-only’, it shows a short description and steps to do manual checks for that issue. If there is no need for a transcription or audio description on that page or if the audio or video element is absent, you can mark it as ‘Not applicable’.

        Example for not applicable

        Similarly, if we take another issue like ‘No Keyboard Trap’, this applies to every page and must be tested. Follow the steps shown below to test it, and if any one of the interactable elements has a keyboard trap, rectify it and make sure that the issue is not there before you mark it as ‘Resolved’.

        Conclusion

        Manual checks play an essential role in understanding the real user experience of your website. Automated testing can identify many technical issues, but only manual evaluation can confirm whether content is usable, understandable, and accessible in practical situations. By combining automated results with manual checks, you gain a more complete view of your website’s quality and can make informed improvements that support all users.

        To know more about automated testing, check “Getting Started with WebYes Accessibility”.

        Was article helpful?