Built to the standard we sell
We audit other organizations’ websites for accessibility, so ours has to hold up to the same scrutiny. This page says plainly what standard this site is built to, what’s in place, and what to do if something doesn’t work for you.
Last reviewed July 12, 2026
WCAG 2.2 Level AA
We build and maintain cascadiasouth.com to WCAG 2.2 Level AA — the current W3C accessibility standard, and the same one we audit client sites against. There’s no official WCAG certification, from us or anyone else; conformance is a claim you back up with your work and stand behind when someone finds a gap.
This statement covers cascadiasouth.com. The demo sites at demos.cascadiasouth.com are sales examples built on the same practices, but they aren’t reviewed on the same cycle.
How this site stays accessible
The same things we check in a client audit, applied to our own site.
Keyboard first
Every page works without a mouse. A skip-to-content link is the first thing keyboard users reach, and focus indicators stay visible as you move through the site.
Reduced motion respected
The site uses animation, but if your device asks for reduced motion, we turn it off. Content never depends on an animation finishing.
Readable contrast
The colour palette was chosen against WCAG contrast thresholds, including the text-on-colour combinations that usually slip through.
Semantic structure
Proper landmarks, one h1 per page, and headings in order — so a screen reader can skim this site the way a sighted visitor does.
Described images
Meaningful images carry alt text. Decorative flourishes are hidden from assistive technology instead of narrating clutter.
Plain language
Short sentences, no jargon, and no acronym used before it’s explained. Plain language is an accessibility feature, not a style choice.
Light pages
Static HTML, compressed images, no bloat. The site loads on an older phone with a metered data plan, because that’s real life for many of the people nonprofits serve.
Labelled forms
Form fields have visible labels, and submitting tells you plainly whether it worked. No mystery-meat inputs, no silent failures.
Tell us. We’ll fix it.
If any part of this site doesn’t work with your screen reader, keyboard, or anything else, that’s a bug, not a policy. Email us with the page and what happened, and a person — not a ticket queue — will reply. Fixing access barriers is literally what we do for a living.
Let's talk about your challenges
Discovery calls are peer conversations, not sales pitches. No pressure. Just honest advice.