Xargaar Accessibility Scanner

描述

Automated tools find only part of the real problems. This plugin does not certify accessibility or compliance with any law or WCAG level.

One click checks the home page, all published pages, posts and products, and WooCommerce shop, cart, checkout and account URLs, in batches of 10 pages. Continue each batch until the full selection is checked; there is no total page cutoff. Findings are grouped by problem, with WCAG references, affected URLs, markup examples, and limited fix availability. No external services, tracking, accounts, fees or locked features.

Document, image, heading, link, button, form, ARIA, keyboard, landmark, table and media checks are included. Hebrew, Arabic, Persian and Urdu direction and Hebrew/Arabic/Cyrillic language hints help reviewers spot mixed-language markup problems. Script is not a reliable language detector: confirm every hint manually.

Contrast checks only handle explicit hex foreground/background pairs in inline styles and simple tag, class or ID style rules. No external CSS, inherited colours, cascade accuracy, JavaScript rendering, pseudo-states, gradients or background images. Verify contrast in the rendered page. Advisory checks such as multiple H1s and missing skip links are not automatic WCAG failures.

Fixes edit output tokens, not stored content. Defaults: missing document language/direction, pinch zoom, skip links with one clear main area, generic iframe titles, hidden new-tab warnings, placeholder names, existing Media Library alt text, product-aware WooCommerce cart labels and error announcements. Positive tabindex removal, focus-outline forcing and reduced-motion CSS are off until enabled. Test fixes in your theme. Placeholder names are not visible labels. Generic titles need context; no alt text is invented.

Scans bypass this plugin’s fixes using short-lived local tokens. Other plugins, themes, caches and CDNs may still affect output. No authenticated customer, cart or checkout content is scanned. Redirects are not followed; canonical URLs must return HTML directly. Each page is limited to 2 MB and a 15-second fetch. The PHP DOM extension and working loopback requests are required. A scan stays in the current browser tab and does not store a report.

HTML output fixes require WordPress 6.9 or newer, using the core template enhancement filter. On older supported versions, scans and CSS fixes remain available; HTML output fixes are not applied. The plugin never owns an output buffer.