Accessibility Audit

Comprehensive WCAG 2.2 AA+ compliance checking with server-side and client-side testing, auto-fix capabilities for common issues, and detailed reporting to ensure your website is accessible to all users.

Overview

ProRank SEO's Accessibility Audit provides enterprise-grade accessibility testing that goes beyond basic checks. With both server-side HTML parsing and client-side JavaScript testing via axe-core, it offers the most comprehensive accessibility analysis available in a WordPress plugin.

Getting Started

Prerequisites

• Core+ License: Required for full accessibility features
• WordPress Admin Access: Needed to run scans and apply fixes
• Modern Browser: For axe-core client-side testing

Running Your First Accessibility Scan

1. Navigate to ProRank SEO → Site Audit & Tools → Accessibility
2. Click the "Scan Site" button to start a comprehensive scan
3. Monitor real-time progress as pages are analyzed
4. Review detected issues organized by severity
5. Select issues and use "Auto-Fix" for supported problems
6. Export reports in CSV or JSON format for documentation

WCAG 2.2 Compliance Checks

The module performs comprehensive checks across all WCAG 2.2 levels (A, AA, AAA):

Core Accessibility Checks

Client-Side Testing with Axe-Core

When enabled, axe-core provides additional JavaScript-based testing for:

• Dynamic content accessibility
• JavaScript-rendered elements
• Interactive component behavior
• Real-time DOM validation
• CSS-based accessibility issues

Dashboard Features

Overview Tab

The main dashboard provides comprehensive accessibility metrics:

Issues Tab

Detailed issue management interface featuring:

• Filterable Table: Sort by severity, page, or issue type
• Bulk Selection: Select multiple issues for batch operations
• Issue Details: Click any issue for expanded information
• WCAG References: Direct links to guideline documentation
• Fix Instructions: Step-by-step remediation guidance
• Auto-Fix Button: One-click fixes for supported issues

Auto-Fix Capabilities

The module can automatically fix certain accessibility issues without manual intervention:

Supported Auto-Fixes

// Example: Auto-generated alt text
// Before: <img src="sunset-beach-california.jpg">
// After: <img src="sunset-beach-california.jpg" alt="Sunset Beach California">

// Example: Added landmarks
// Before: <header>...</header>
// After: <header role="banner">...</header>

Manual Review Required

Some issues require human judgment and cannot be automatically fixed:

• Heading hierarchy problems (content structure decisions)
• Link text quality (context-dependent)
• Form label associations (complex forms)
• Color contrast issues (design changes needed)
• Video/audio captions (content creation required)

Export & Reporting

Export Formats

Generate comprehensive accessibility reports in multiple formats:

Report Contents

Each report includes:

• Executive summary with compliance score
• Complete issue list with severity levels
• WCAG guideline references
• Affected URLs and elements
• Remediation recommendations
• Historical trend data (if available)

Settings & Configuration

Scan Settings

Auto Scan: Weekly/Daily/Monthly
Email Reports: Enabled/Disabled
Email Recipients: admin@example.com
WCAG Level: A/AA/AAA
Check Types: [Select individual checks]
Auto-Fix Enabled: Yes/No
Auto-Fix Types: [Select fixable issues]

Advanced Settings

• Axe-Core Integration: Enable client-side JavaScript testing
• Real-Time Checking: Test accessibility while editing content
• Exclude Post Types: Skip certain content types from scanning
• Exclude Post IDs: Ignore specific pages/posts
• Max Pages to Scan: Limit for large sites (100-1000)

Automation Options

• Scheduled Scans: Automatic weekly/monthly audits
• Email Notifications: Send reports to stakeholders
• Auto-Fix on Scan: Automatically apply safe fixes
• Webhook Integration: Send results to external systems

Axe-Core Integration

The module includes seamless integration with axe-core, the industry-standard accessibility testing engine used by Google, Microsoft, and others.

How It Works

1. Axe-core library loads from CDN (4.8.2+)
2. Scans rendered DOM in real browser context
3. Detects JavaScript-based accessibility issues
4. Results merge with server-side findings
5. Provides fix suggestions and code examples

Axe-Core Specific Features

• Violation Highlighting: Visual indicators on problematic elements
• Impact Levels: Critical, Serious, Moderate, Minor
• Help URLs: Direct links to Deque documentation
• Fix Examples: Code snippets for remediation
• Rule Configuration: Enable/disable specific rules

// Axe-core configuration example
window.axe.configure({
 rules: [
 { id: 'color-contrast', enabled: true },
 { id: 'image-alt', enabled: true },
 { id: 'button-name', enabled: true },
 { id: 'heading-order', enabled: true }
 ],
 reporter: 'v2',
 resultTypes: ['violations', 'incomplete']
});

REST API Integration

Access accessibility data and controls via REST API:

Scan Endpoints

# Start a new scan
POST /wp-json/prorank-seo/v1/accessibility/scan
{
"post_id": null, // null for site-wide, or specific post ID
"url":"https://example.com/specific-page" // optional
}

# Get scan status
GET /wp-json/prorank-seo/v1/accessibility/status

# Get scan results
GET /wp-json/prorank-seo/v1/accessibility/issues?page=1&per_page=50

Auto-Fix Endpoint

POST /wp-json/prorank-seo/v1/accessibility/auto-fix
{
"issue_ids": [123, 124, 125]
}

Response:
{
"success": true,
"data": {
"fixed": 2,
"failed": 1
 },
"message":"2 issues fixed, 1 failed"
}

Export Endpoint

GET /wp-json/prorank-seo/v1/accessibility/export?format=csv

Response:
{
"success": true,
"data":"base64_encoded_csv_data",
"filename":"accessibility-report-2024-01-15.csv",
"mime_type":"text/csv"
}

Settings Endpoints

# Get current settings
GET /wp-json/prorank-seo/v1/accessibility/settings

# Update settings
POST /wp-json/prorank-seo/v1/accessibility/settings
{
"auto_scan": true,
"scan_frequency":"weekly",
"wcag_level":"AA",
"auto_fix_enabled": true
}

Best Practices

Scanning Strategy

• Run initial site-wide scan to establish baseline
• Schedule weekly scans for ongoing monitoring
• Scan individual pages after major updates
• Enable axe-core for comprehensive coverage
• Test with actual assistive technologies periodically

Remediation Workflow

1. Prioritize: Focus on Level A errors first
2. Auto-Fix: Apply automatic fixes where available
3. Manual Review: Address remaining issues by severity
4. Test: Verify fixes with screen readers
5. Document: Export reports for compliance records
6. Monitor: Track improvements over time

Compliance Tips

• Aim for WCAG 2.2 Level AA as minimum standard
• Test with multiple screen readers (NVDA, JAWS, VoiceOver)
• Include users with disabilities in testing
• Document accessibility statement on your site
• Train content creators on accessibility basics

Troubleshooting

Scan Not Starting

• Verify Core+ license is active
• Check WordPress user permissions
• Ensure database tables are created
• Review PHP error logs for issues

Auto-Fix Not Working

• Confirm issue type supports auto-fix
• Check file/database write permissions
• Verify post is not locked for editing
• Review auto-fix settings configuration

Axe-Core Not Loading

• Check browser console for errors
• Verify CDN is accessible (not blocked)
• Ensure JavaScript is enabled
• Try clearing browser cache

Missing Issues

• Enable all check types in settings
• Verify pages are publicly accessible
• Check exclude patterns in configuration
• Run both server-side and client-side scans

WCAG Guidelines Reference

Understanding WCAG Levels

• Level A: Essential accessibility features (minimum)
• Level AA: Recommended standard for most websites
• Level AAA: Enhanced accessibility (not always achievable)

Four Principles of Accessibility

Legal & Compliance

Many jurisdictions require website accessibility by law:

• USA: ADA Title III, Section 508
• EU: EN 301 549, Web Accessibility Directive
• UK: Equality Act 2010
• Canada: AODA (Ontario)
• Australia: Disability Discrimination Act

Related Features

Enhance accessibility with these complementary ProRank SEO features:

• Schema Markup: Add structured data for better screen reader context
• SEO Audit: Technical SEO often improves accessibility too
• Content Analysis: Ensure content readability for all users
• Performance Optimization: Faster sites are more accessible

Additional Resources

• WCAG 2.2 Quick Reference
• Axe Accessibility Testing Tools
• WebAIM Resources
• The A11Y Project