Find barriers before they cost you users

Lakeview, a small guesthouse. The website looks good. But not for everyone. If you can't see images, you only hear silence. If you read on your phone in bright sunlight, you can barely make out pale text. The “Rooms” page hides exactly three such barriers: an image without alt text, weak contrast and a link that only says “Learn more”. You don't see them at first glance. Searching every page by hand takes hours. The Accessibility Test in EZZE WCAG Pro finds problems like these right in the WordPress backend.

At the top of the Accessibility Test page, there are three tabs: Individual test, Batch test and Settings. We'll start with the individual test.

You decide what gets tested. Either you use “Select content” to pick a page from the list, with the built-in search. We'll take “Rooms”. Or, under “Enter URL”, you type in the path yourself. If the mobile view should be tested as well, you turn that on in Settings. One click on “Start test”, and you see what happens: check page URL, test desktop view, test mobile view, save result.

The result appears at the very top of “Latest test results”, with the score achieved for desktop and for mobile. When you expand the row, the score circle shows a number from zero to a hundred, plus a traffic light: green from 90, yellow from 50, red below that. Rooms: 78, yellow. Next to it, you see a screenshot of the page. If mobile testing is on, you switch between desktop and mobile at the top. Score, screenshot and findings then apply to the selected view. Below are four check groups: failed, manual, passed and not applicable.

Open the failed checks. Each finding is a card with a title, a severity from Critical to Low and a reference to the WCAG criterion. With “Show affected elements”, you see the code. “Explanation & Solution” tells you what to do, for free. And for a single element, the AI Element Fix gives you a concrete correction – in the test result or in the Inspector. With “Open Inspector”, you see the element right on the page.

Now you fix the problems. You let the AI suggest the alt text, right in the Media Library: “Generate suggestion”, a quick check, “Apply suggestion”. Then you darken the color and make the link text more precise. Finally, in the row, you choose “Retest”. The score improves significantly. Yellow turns green.

The check stays within reach in the block editor, too. In the sidebar, you find the “Accessibility” section: the score for desktop and mobile, “Last check” with date and time, and the link “Check accessibility again”. On the front end, an entry in the admin bar takes you straight to the test of the current page and starts it right away.

Test many pages at once, on a schedule or automatically after publishing? That's what our video on Batch Tests and Automation shows you. The Accessibility Test in EZZE WCAG Pro: find barriers before they exclude anyone.