XCompliant – Accessibility Scan & Audit

XCompliant is an accessibility scanning and audit plugin designed to help WordPress site owners identify common accessibility issues and improve usability for a wider range of users. The plugin analyzes selected pages and content elements and highlights potential accessibility concerns based on established accessibility best practices, including WCAG-related guidelines. XCompliant is intended to support accessibility review and improvement efforts. The results provided are informational and do not constitute legal advice, certification, or a guarantee of compliance with any specific law or regulation. Key Features

• Automated accessibility scans for selected pages
• Issue summaries grouped by category
• Accessibility insights related to structure, text alternatives, and navigation
• Ongoing scans for newly added or updated content
• Optional accessibility interface for end users

What XCompliant Does XCompliant analyzes page content and interface elements to help identify potential accessibility-related issues, including:

• Missing or incomplete alternative text
• Interactive elements that may require improved labeling
• Navigation and keyboard interaction patterns
• Common UI and structural accessibility concerns

The plugin may apply session-based adjustments through an optional accessibility interface that allows users to customize their viewing experience. Accessibility Standards XCompliant references established accessibility guidelines, including WCAG 2.x-related principles, to help surface potential issues. Accessibility requirements vary by jurisdiction and context, and manual testing is strongly recommended in addition to automated tools. How It Works

1. Install and activate the XCompliant plugin.
2. Register an account to enable scanning features.
3. Select pages or allow automated scans to review accessibility-related findings.

Scans may take time to complete depending on site size and content.

1.0.12

• Fix: on some hosts the accessibility widget script URL was built without the XCompliant address, so the widget did not load. The plugin now loads its configuration by absolute path and always falls back to the correct address.

1.0.11

• Maintenance release.