GOMAX ULTIMATE 5.41.0 adds a built-in accessibility auditor that reads your own rendered WordPress pages, checks them against WCAG 2.1, and returns a 0-100 score with each issue mapped to a specific success criterion and a fix — no external scanning service, no data leaving your site. It also generates a ready-to-publish accessibility statement, which laws like the European Accessibility Act increasingly expect.
Accessibility has moved from "nice to have" to "legally required" for a lot of businesses. But most WordPress owners either paste in a third-party overlay widget (which experts widely criticize) or send their URLs to an external scanner. GOMAX takes the opposite approach: the audit runs inside the plugin you already own, on your own server.
Key takeaways
- Scan any page or the whole site. Audit one URL, post or path, or sample your key pages for a site-wide score and the issues that recur most.
- Every issue is WCAG-mapped. Sixteen machine-detectable checks, each tied to a success criterion, with a count, sample offenders and a concrete fix.
- A score you can track. Each scan returns a 0-100 score and grade, with history so you can watch it improve.
- A statement you can publish. Generate an accessibility statement targeting WCAG 2.1 A/AA/AAA, prefilled with your contact and latest results.
- Honest about limits. Automated checks catch roughly 40% of WCAG issues; contrast and reading order are flagged for manual review rather than faked.
What it checks
The auditor parses your page's HTML and flags the issues that can be detected reliably from markup, including:
- Images without alt text (WCAG 1.1.1)
- Form controls with no accessible name — inputs, selects and textareas lacking a label or aria-label (1.3.1, 4.1.2)
- Empty links and buttons — icon-only controls with no text or aria-label (2.4.4, 4.1.2)
-
A zoom-blocking viewport —
user-scalable=noor a cappedmaximum-scale(1.4.4) - Heading problems — missing or multiple ``, or skipped levels (1.3.1, 2.4.6)
- Missing landmarks, page language or title, and no skip link (1.3.1, 2.4.1, 3.1.1, 2.4.2)
- Untitled iframes, header-less data tables, duplicate ids, positive tabindex, generic link text and autoplaying media
Each finding comes with a plain-language fix — for example, "give every field a label or aria-label," or "remove positive tabindex and rely on natural DOM order."
Why in-plugin and self-hosted matters
Sending every page to an external accessibility API means your content — including unpublished or members-only pages — leaves your server. Overlay widgets, meanwhile, don't fix the underlying markup and can even introduce new barriers. A first-party auditor avoids both problems: it reads the same HTML a browser would, reports real issues against the actual standard, and keeps everything on your own site. That fits a pay-once, privacy-first product with no per-scan metering.
From audit to statement
Once you've scanned, you can generate an accessibility statement in one step. It states your commitment, your target conformance level (A, AA or AAA), a feedback contact, and a note that the site is assessed with automated and manual review — reflecting your latest score. Publish it at a page like /accessibility and link it in your footer. It's a starting point to adapt to your exact legal obligations, not legal advice.
Frequently asked questions
Does this replace a full manual accessibility audit?
No, and it doesn't pretend to. Automated tools reliably catch roughly 40% of WCAG issues — things like missing alt text and unlabeled fields. Colour contrast and reading order still need a human, so the auditor reports those as manual checks rather than guessing.
Is it better than an accessibility overlay widget?
Overlays sit on top of your site and don't fix the underlying HTML; accessibility experts broadly recommend against relying on them. This auditor instead shows you the real markup issues so you (or the AI assistant) can fix them at the source.
Will scanning send my pages to a third party?
No. The auditor fetches and analyzes your own pages on your own server. No external accessibility service is used and nothing leaves your site.
Does it help with the European Accessibility Act?
It helps you find and track WCAG issues and generate an accessibility statement, both of which support EAA-style requirements. It is a tool, not legal advice — confirm your specific obligations for your business.
Can I scan the whole site or just one page?
Both. Scan a single URL, post or path, or run a site scan that samples your home page, shop and recent content to produce an overall score and the top recurring issues to fix first.
