Mant Design

Mant Accessibility Pro

Documentation

Mant Accessibility is a professional WordPress accessibility scanner and issue management tool. It helps website owners, agencies, developers, and accessibility teams find accessibility problems, review them visually, track fixes, and create reports for clients or internal documentation.

The plugin is built around a practical workflow:

  1. Scan the website or a single page.
  2. Review the accessibility score and issue groups.
  3. Inspect problems directly on the page.
  4. Fix issues in WordPress, the theme, or plugins.
  5. Mark issues as fixed or verified.
  6. Generate reports that show progress clearly.

Mant Accessibility is not just a scanner. It is designed to act as a control board for accessibility work, showing what needs attention, what was already improved, and what still needs manual review.

Automated accessibility testing is useful, but it cannot guarantee full WCAG compliance. Manual testing is still required for a complete accessibility audit.

The dashboard gives a clear overview of the current accessibility status of the website.

It shows:

  • Accessibility score
  • Open issues
  • Critical issues
  • Warnings and manual review items
  • Passed checks
  • Failed checks
  • Repeated issue groups
  • Pages with the most issues
  • Recent scan history
  • Progress after fixes

The dashboard is designed to help users quickly understand the health of the website without reading a large technical table first.

The accessibility score is a weighted risk score based on the issues found during scans.

More serious problems reduce the score more strongly than minor issues. This makes the score more useful than a simple issue count.

For example:

  • Critical issues have a high impact.
  • Serious issues have a strong impact.
  • Moderate and minor issues have a smaller impact.
  • Manual review items are separated because they may require human judgment.

The score helps users understand whether the site is improving over time.

Mant Accessibility uses a browser-based scanning approach for rendered pages. This means the scanner can inspect the page closer to how visitors and assistive technologies experience it.

The scanner can detect issues in:

  • WordPress page content
  • Blocks
  • Theme output
  • Plugin-generated elements
  • Rendered navigation
  • Buttons
  • Links
  • Forms
  • Iframes
  • ARIA attributes
  • Visual contrast
  • Page structure

This makes the scanner stronger than a basic content-only checker.

Mant Accessibility can detect many common accessibility problems, including:

  • Missing image alt text
  • Empty image alt text that may need review
  • Empty links
  • Placeholder links
  • Missing button text
  • Missing form labels
  • Bad heading hierarchy
  • Multiple H1 headings
  • Missing H1 heading
  • Low color contrast
  • Missing iframe titles
  • Empty paragraph tags
  • Duplicate IDs
  • Missing page language attribute
  • Missing landmarks
  • Incorrect landmark structure
  • ARIA role problems
  • Invalid ARIA attributes
  • Hidden focusable content
  • Keyboard focus issues
  • Elements needing manual review

Each issue includes a clear explanation and a suggested fix where possible.

Mant Accessibility separates issues into two important categories.

Automated Fail

These are problems that the scanner can detect with a high level of confidence.

Examples:

  • Missing iframe title
  • Empty button
  • Missing form label
  • Duplicate ID
  • Invalid ARIA attribute

These issues should usually be fixed directly.

Needs Manual Review

Some accessibility checks require human judgment. The scanner can flag them, but a person needs to confirm whether they are truly a problem.

Examples:

  • Empty alt text on an image that may be decorative
  • Placeholder links
  • Some contrast or visual context issues
  • Frame or embedded content that needs manual testing

This separation helps avoid confusion and prevents automated tools from pretending they can make every accessibility decision.

The Issue Workspace is where detailed accessibility findings are reviewed and managed.

It includes:

  • Issue type
  • Severity
  • Priority
  • Source
  • Page URL
  • WCAG reference
  • Selector
  • HTML snippet
  • Why the issue matters
  • Suggested fix
  • Current status
  • Owner and due date in Pro
  • Internal notes in Pro
  • Action history in Pro

Users can filter issues by:

  • Page URL
  • Issue type
  • Severity
  • Priority
  • Source
  • Status
  • WCAG principle
  • False positives

This helps teams focus on the most important work first.

Repeated issues are grouped by type so users do not have to read hundreds of repeated rows.

For example, instead of showing every missing iframe title as a separate main item, the plugin can show:

  • Iframe missing title
  • Number of findings
  • Number of affected pages
  • Severity
  • WCAG reference

This is useful for identifying patterns, such as a theme component or plugin output causing the same issue across multiple pages..

The visual page overlay allows admins to inspect issues directly on the front end of the website.

With the overlay, users can:

  • Scan the current page
  • See issue markers on the page
  • Click an issue marker
  • Read the problem explanation
  • View the suggested fix
  • Navigate to the affected element
  • Open the WordPress editor
  • Mark the issue as fixed
  • Open the full issue list

This is especially helpful for content editors and clients because the problem can be seen in context instead of only as a technical selector.

Mant Accessibility uses a browser-based scanning approach for rendered pages. This means the scanner can inspect the page closer to how visitors and assistive tMant Accessibility also adds page-level tools inside the WordPress editor area.

The editor tools allow users to:

  • Scan the rendered page
  • View the page score
  • See open issues for that page
  • Review grouped issue types
  • Open the visual overlay
  • Open the full issue list

This keeps accessibility work close to the editing workflow.

Mant Accessibility can detect mMant Accessibility includes reporting tools to document scan results and remediation progress.

Reports help answer:

  • How did the accessibility score change?
  • Where did we start?
  • What was scanned?
  • How many issues were found?
  • What was fixed?
  • Which pages were affected?
  • What remains open?
  • What still needs manual review?

The Client View is designed for non-technical users.

It focuses on:

  • Accessibility score
  • Progress summary
  • Fixed issues
  • Remaining important problems
  • Pages affected
  • Clear explanations
  • Client-friendly wording

This view avoids overwhelming clients with selectors and raw HTML.

The Technical View is designed for developers and accessibility specialists.

It includes:

  • Issue type
  • Severity
  • Status
  • WCAG reference
  • Selector
  • HTML snippet
  • Why it matters
  • Suggested fix
  • Source
  • Page URL
  • Scan history
  • Developer notes

This helps developers understand where the issue is and how to fix it.

RIn Pro, Mant Accessibility can create saved client report snapshots.

A client report can include:

  • Report cover
  • Client name
  • Website URL
  • Scan overview
  • Current accessibility score
  • Initial score
  • Initial issue count
  • Remaining issues
  • Critical issues
  • Warnings and review items
  • Fixed or verified work
  • Key findings
  • Suggested fixes
  • Affected pages
  • Scan history

The goal is to create a report that feels professional and useful for client communication.

Mant Accessibility uses a browser-based scanning approach for rendered pages. This means the scanner can inspect the page closer to how visitors and assistive tMant AMant Accessibility includes an Accessibility Statement Builder.

This helps site owners create a public accessibility statement page based on the site’s information and current accessibility process.

Users can:

  • Generate statement text
  • Edit the statement
  • Save it as a draft
  • Create a WordPress page
  • Publish the page
  • Update the statement later

The statement should always be reviewed and customized before publishing.

In Pro, Mant Accessibility can export and restore plugin data.

The backup can include:

  • Scans
  • Issues
  • Issue events
  • False positives
  • Logs
  • Plugin settings

This is useful before resetting data, moving work between environments, or keeping a record of accessibility work.

Deleting stored plugin data remains available in Free, but backup and restore are Pro features.

A recommended accessibility workflow is:

  1. Run a scan.
  2. Review the dashboard.
  3. Start with critical and serious issues.
  4. Open the visual overlay for each affected page.
  5. Fix content issues in WordPress.
  6. Fix theme or plugin output in code where needed.
  7. Mark issues as fixed.
  8. Rescan the page.
  9. Verify resolved issues.
  10. Create a report for the client or team.

TMant Accessibility is powerful, but no automated scanner can detect every accessibility problem.

Automated scanners may not fully understand:

  • Whether link text makes sense in context
  • Whether alt text is meaningful
  • Whether reading order is logical
  • Whether keyboard interaction feels usable
  • Whether custom components behave correctly
  • Whether content is understandable
  • Whether a design works well for real users with disabilities

For full compliance work, automated scanning should be combined with manual testing.

Use Mant Accessibility as part of a wider accessibility process:

  • Scan regularly.
  • Fix high-impact issues first.
  • Review manual review items carefully.
  • Test keyboard navigation manually.
  • Check screen reader behavior where possible.
  • Keep reports after major fixes.
  • Rescan after theme, plugin, or content changes.
  • Do not rely only on the score.
  • Use the score as a progress indicator, not a legal guarantee.

TMant Accessibility is powerful, but no automated scanner can detect every accessibility problem.

Automated scanners may not fully understand:

  • Whether link text makes sense in context
  • Whether alt text is meaningful
  • Whether reading order is logical
  • Whether keyboard interaction feels usable
  • Whether custom components behave correctly
  • Whether content is understandable
  • Whether a design works well for real users with disabilities

For full compliance work, automated scanning should be combined with manual testing.

Mant Accessibility is useful for:

  • WordPress site owners
  • Agencies
  • Freelancers
  • Developers
  • Content editors
  • Accessibility consultants
  • WooCommerce store owners
  • Organizations that need scan history and reporting
  • Teams managing client accessibility work

Mant Accessibility helps detect, organize, and document accessibility issues. It supports accessibility work but does not guarantee that a website fully complies with WCAG, ADA, EAA, EN 301 549, or any other legal accessibility requirement.

A complete accessibility review should include automated testing, manual expert testing, keyboard testing, assistive technology testing, and content review.