← Back to ResourcesFree Tool · No Signup Required

Accessibility Readiness Check

This is a planning tool, not an automated scanner — it won't tell you whether your site technically conforms to WCAG. It tells you whether your organization has the practices, ownership, and vendor accountability in place to make accessibility real.

Start the check ↓

Personalized recommendations

What to work on first, based on your answers.

These recommendations describe organizational practice — not a substitute for professional accessibility testing on your specific site.

01
Documents & media
Inventory PDFs and videos published in the last two years and prioritize remediating the highest-traffic ones first — captioning and PDF tagging are addressable in phases, not all at once.
Website accessibility →
02
Forms & interaction
Test your highest-traffic forms (donation, contact, application) with a keyboard only, no mouse. This single test surfaces most of the interaction problems that automated scanners miss.
Website accessibility →
03
CMS & editorial practices
Build alt text, heading structure, and descriptive link text into your CMS publishing checklist — accessibility built by editors day to day matters more than a one-time audit.
Accessible WordPress development →
04
Third-party tools & vendors
List every third-party widget, donation platform, and event tool embedded on your site, and ask each vendor directly about their accessibility conformance and remediation timeline in writing.
Website accessibility →
05
Procurement & policy
Add accessibility conformance questions to your vendor procurement checklist before your next tool purchase or website RFP — retrofitting is always more expensive than requiring it upfront.
Website RFP template →
06
Ownership & training
Name one internal accessibility owner — even part-time — and give content editors a short training on the handful of habits (alt text, headings, link text) that cover most day-to-day risk.
Website accessibility →
07
Testing & ongoing governance
Schedule a recurring accessibility check-in — quarterly is reasonable for most nonprofits — rather than treating a single pre-launch audit as the finish line.
WCAG remediation →

Need an actual technical audit?

We'll pair this with real testing on your site.

This self-assessment tells you where your organization stands. A technical audit tells you what's actually broken on your pages.

Talk to CauseHouse →

What this tool is — and isn't

We'd rather be useful and honest than pretend a quiz can validate compliance.

Plenty of tools claim to "check" accessibility with an automated scan. Automated scans catch a fraction of real issues and miss almost everything about how your organization actually operates. This tool does something different, on purpose.

Illustration of a magnifying glass reviewing a document with contact and directory information

Not a WCAG conformance test

Only manual testing with assistive technology, and often a professional audit, can tell you whether a specific page conforms to WCAG 2.1 or 2.2 AA. This tool doesn't touch your site's code.

Not a legal compliance opinion

We are not attorneys, and this isn't legal advice about ADA or Section 508 exposure. Talk to counsel for that.

It is a practice inventory

It tells you which organizational habits — ownership, procurement, editorial practice, vendor accountability — are and aren't in place yet.

When to use it

Three moments this check earns its keep.

Before a redesign or procurement: Use this to know what accessibility requirements to build into your RFP or vendor conversations.
During development: Use it to check whether your team's day-to-day habits (alt text, headings, keyboard testing) are keeping pace with the build.
As ongoing governance: Use it quarterly or annually as a check-in — accessibility is a practice, not a one-time project.