01 Our commitment
Accessibility isn't a checkbox we tick once. Roughly one in six people lives with a disability, and many more rely on assistive technology situationally — a broken mouse, bright sun on a phone screen, a noisy room. If our site doesn't work for them, it doesn't work.
So we treat accessibility as part of shipping, not a pass we do at the end. New pages and components are built against the same bar described below, and we gate every change in CI so regressions get caught before they reach you.
02 The standard we target
We build loudcrowd.com to meet the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA. That's the standard most accessibility law points at — including the Americans with Disabilities Act in the US and EN 301 549 in the EU.
In practice that means text you can read at AA contrast, every interactive element reachable and operable from the keyboard, a visible focus indicator wherever you land, a skip-to-content link past the navigation, content structured with real headings and landmarks, images that carry alternative text, and form fields that announce their labels.
03 Conformance status
loudcrowd.com partially conforms to WCAG 2.1 Level AA. "Partially conforms" means most of the site meets the standard, but some content does not yet fully meet every success criterion — see the known limitations below.
This status reflects our own automated and manual testing, not a formal third-party audit. We run automated checks on every code change and do manual keyboard and screen-reader passes on key templates. We'll commission an independent audit and update this claim when it's complete.
04 Known limitations
We'd rather be honest about the gaps than pretend they don't exist. Here's what we know isn't perfect yet, and what we're doing about it:
- Motion and animation. A few hero and product sections use motion to demo the product. We honor your operating system's "reduce motion" setting, but a small number of decorative animations may still play. We're auditing each one.
- Third-party embeds. Some pages embed content we don't control — scheduling widgets, video players, and the like. Their accessibility depends on the vendor. We pick accessible vendors where we can and report issues upstream where we can't.
- Older content. A handful of long-lived pages predate our current component library. We're migrating them to the accessible templates, but a few may temporarily fall short of AA.
05 What we do to keep it accessible
Accessibility decays if nobody guards it. So we wired the guardrails into the build:
- Every pull request runs an automated color-contrast check and a broader accessibility scan (alt text, form labels, ARIA validity, landmark and heading structure, link names). A new violation fails the build.
- We design components against WCAG 2.1 AA from the start — keyboard operability, visible focus, and semantic structure are part of the spec, not a retrofit.
- We do manual keyboard and screen-reader passes on key templates before they ship.
06 Tell us about a barrier
If something on loudcrowd.com blocks you, we want to hear it — that's how we find the gaps our testing missed. Email accessibility@loudcrowd.com and tell us:
- the page or feature where you hit the problem (a URL helps);
- what you were trying to do and what blocked you;
- the browser, operating system, and any assistive technology you were using, if you know it.
We aim to acknowledge accessibility reports within 5 business days and will work with you on a fix or a usable alternative while we resolve the underlying issue.
07 If we don't fix it
If you contact us about an accessibility barrier and aren't satisfied with our response, you have the right to escalate. In the United States you can file a complaint with the U.S. Department of Justice under the ADA. Readers in other jurisdictions may have equivalent national enforcement bodies.