Test many pages. Automate processes.

Lakeview is growing. New rooms, new activities, something on the blog every week. On top of that, editors keep publishing new content. A single test only ever checks one page. With lots of pages and constant changes, you can't keep up that way. And a barrier quickly creeps back in: a new image without alt text, a button with too little contrast. That's why the Accessibility Test in EZZE WCAG Pro has Batch Tests and Automation: scheduled runs and tests after publishing.

In the “Batch test” tab, you open “Test for” and choose the content types: posts and pages, custom post types like rooms and activities, taxonomies like categories and tags, other archives, the front page and other special pages. The scope is estimated in advance, and in brackets you see the number of URLs. Then you click “Start batch test” and confirm.

The test runs in the background. A progress bar shows you how many pages have already been checked. You can close the browser, and the run continues on the server. If it's interrupted, it picks up where it left off. Pages already tested stay untouched. So you don't have to sit and watch.

The results appear in a list that you can filter and sort: by content type, score, test age or test source. Active filters appear as chips. Each row shows the desktop and mobile score. That way, you find the pages that need the most work first.

Every run stays traceable. The batch history shows you the status, page count, duration, retries and errors for each run. So you can see at a glance whether everything went through.

Under “Settings”, you turn on “Scheduled Batch Tests”. You choose the content types and the interval: weekly, monthly or custom, every seven to 365 days. You see the next run right in the list. After each run, an email sends you the report.

And when editors publish? Under “Background auto-tests”, you turn on “Test after publishing” and “Test after updating”. Both are off by default. You also decide which user roles trigger the test. An example: an editor publishes a new post about hiking trails. The test starts on its own. Shortly after, the result appears in the “Accessibility” panel of the editor, with score and last check.

Who can do what? Under “Permissions”, you set for each role: allow individual test, allow batch test, test other users' content and delete test results. By default, only the administrator can start the batch test.

Accessibility is not a one-time state. New content, new plugins, new updates: something is always changing. With Batch Tests, scheduled runs and automatic tests, you keep an eye on Lakeview. Here too: automated tests don't find everything. But they keep you on track for the long run. Batch Tests and Automation in EZZE WCAG Pro.