PublicInput includes a built-in Accessibility Checker inside the rich text editor — the same editor used to author project pages, email templates, and campaigns. It scans your content, highlights problem elements one at a time, and walks you through each issue with a short explanation and (when possible) a one-click quick fix.
It's available to all customer users in the editor toolbar, with no extra setup.
Where to find it
The Accessibility Scan button appears in supported rich text editing areas, including:
Project pages — in the rich text editor toolbar when editing descriptions, instructions, FAQ answers, and other rich text areas
Email templates and email campaigns — in the email composer controls above the preview pane
Running a scan
Open the supported page, content area, email template, or email campaign you want to review.
For project content, click into the rich text field so the editor toolbar is active.
Select A11y Check.
In project-rich text areas, this appears in the editor toolbar.
In email templates or campaigns, this appears in the email composer controls near the preview pane.
After the scan runs, one of two things will happen:
If no issues are found, you'll see the message: "The document does not contain any accessibility issues."
If issues are found, the editor highlights the first problem element and opens the Accessibility Checker panel anchored to that element.
Working through issues
When the panel is open, it shows:
A short description of the issue (what's wrong and why it matters)
A severity label, notice, warning, or error
An issue counter, such as "Issue 1 of 4 (error)" so you know how far through you are
Navigation and action buttons
From there, you have four ways to resolve or move past an issue:
Quick fix: For issues the checker can auto-correct (for example, certain missing attributes), click Quick fix to apply the suggested change. You may be prompted for a value, such as alt text for an image.
Fix it manually in the editor: Edit the highlighted element directly (change colors, add alt text, rewrite link text, etc.). The panel will show: "Waiting for manual content changes. When done, click Check again below." Click Check again to re-scan.
Ignore: Click Ignore to skip an issue you've reviewed and don't want flagged. You can reverse this later by clicking Stop ignoring on that element.
Next / Previous: Step through the remaining issues without acting on the current one.
When all issues are resolved (or ignored), running the scan again will show the "no accessibility issues" confirmation.
Click Close to dismiss the panel at any time.
What the scanner looks for
The checker flags common WCAG issues in user-authored content, including:
Missing image alt text — Images without a description are invisible to screen readers. Add alt text that conveys the image's purpose. For purely decorative images, mark them as decorative where that option is available.
Missing iframe titles — Embeds like YouTube videos or Google Maps need a descriptive
titleattribute (for example, "Project overview video"). Edit the embed to add one.Empty headings or headings used for spacing — Remove empty heading tags and use headings only for real section titles. Use heading levels for structure, not for making text bigger or adding whitespace.
Low color contrast — Text and background color combinations should meet WCAG AA contrast (generally 4.5:1 for normal text, 3:1 for large text). Adjust colors when the checker flags a contrast issue.
Non-descriptive link text — Replace "click here" or "Read more" with meaningful link text that makes sense out of context (for example, "View the project timeline (PDF)").
Quick accessibility checklist
Use headings for structure, not spacing.
Add alt text to informative images.
Write link text that's understandable on its own.
Don't rely on color alone to convey meaning.
For email, double-check that the text is readable in common email clients.
What the checker does (and doesn't) do
The Accessibility Checker is designed to warn and educate as you write. A few things to keep in mind:
It does not hard-block saving. You can save content with flagged issues; the goal is to surface problems, not prevent publishing.
Passing the scan does not guarantee full WCAG or ADA compliance. A manual review is still recommended, especially for complex layouts, embedded media, and color choices.
The checker focuses on the content you write inside the rich text editor. Platform-level accessibility (keyboard navigation, ARIA roles, focus indicators, page structure) is handled separately as part of PublicInput's standard build.
More about accessibility