Skip to contentSkip to content

WCAG 1.4.3 · WCAG Module

Contrast scanner with auto-audit

Ongoing contrast checking in the backend — regression is reported before the editorial team notices anything.

What is that?

What does "contrast scanner with auto-audit" mean?

A scanner running in the WordPress backend automatically checks all brand tokens and all actively used text/background pairs against WCAG contrast thresholds. If someone accidentally sets text that is too light on a background that is too light in a Divi module, the scanner reports this in the audit log and optionally blocks the publication.

Why is it important?

Obligation and Benefit — WCAG 1.4.3.

WCAG 1.4.3 (Contrast Minimum) AA is mandatory — 4.5:1 normal text, 3:1 large. Any content change can introduce a contrast violation: new hover state, new brand color, new background image area. Manual re-audits are not scalable — automation is the only way to maintain BFSG compliance permanently.

Our implementation

How we will solve it specifically.

  • A cron job runs daily on all published pages, sampling text/background image pairs.
  • Pre-Publish Hook: The WordPress "Publish" button validates the brand tokens and custom styles beforehand.
  • Reports in the admin dashboard: red marker per page, clickable to access the relevant section.
  • Slack/email notification for critical regressions (optional).
  • Audit trail: every change is logged with a contrast value — evidence for market surveillance.

Do you need this exact module?

15-minute initial consultation — we'll clarify whether it's relevant for your site.

Book an initial consultation

Further information:
BFSG overview ·
Performance overview ·
BAFA funding ·
FAQs

Easy language