FAQ

What exactly is web accessibility?

It means building and auditing your site so everyone can use it—people navigating with a screen reader, people using a keyboard instead of a mouse, and anyone with a motor, cognitive, or low-vision condition that affects how they interact with a page.

What is WCAG, and why does it matter?

The Web Content Accessibility Guidelines (WCAG) are the internationally recognized benchmark for digital accessibility, maintained by the World Wide Web Consortium (W3C). WCAG 2.1/2.2 Level AA is the specific baseline referenced in accessibility settlements, consent decrees, and state procurement standards.

Is my website required to be accessible?

Most likely, yes. Most federal courts that have addressed the question treat public-facing websites — small-business sites, e-commerce sites, nonprofits, municipal programs — as covered under Title III of the ADA. WCAG 2.1/2.2 Level AA has become the de facto benchmark referenced in DOJ guidance, settlements, and consent decrees, even without a single binding federal standard.

My website is small — do I still need to worry about this?

Site size doesn't change the requirement. A five-page business site can carry just as many accessibility issues as a large e-commerce store. The good news is that issues on smaller sites are usually straightforward to fix, so the cost and effort of an audit scales down right along with the site.

About the Audit

What does an accessibility audit actually look for?

We check your site's source code and interactive elements against the full set of WCAG Level A and AA success criteria — things like keyboard navigation breaks, missing alt text, unlabeled form fields, and hidden elements that trip up assistive technology.

Why isn't a free automated scan or widget enough?

Automated tools are useful, but they only catch a portion of real accessibility issues. They can't test whether your site is actually navigable by keyboard, whether a promotional graphic has hidden text behind it, or what a screen reader experience is actually like for someone using one. A clean automated score means the machine-detectable bugs are gone — it doesn't mean the site is usable.

How many pages do you test? (Our scoping model)

We evaluate your site by unique page templates — homepage, standard content page, contact flow, and so on — rather than by raw page count. This keeps testing efficient without skipping anything that matters. See our audit process page for how that works.

Do you install an overlay toolbar or "widget" to achieve compliance?

No. Overlay tools and quick-fix widgets don't touch your underlying code, don't satisfy legal requirements, and can actually create new barriers for screen reader users. We work exclusively at the code level — diagnosing issues at the source.

How long does a technical review take?

Once we've finalized scope, we complete the technical review within 7 to 10 business days.

About Remediation | What's the difference between an Audit Only and Audit + Remediation?

An audit is the diagnosis: a full roadmap of what's failing and exactly where it lives. To keep our findings objective, we separate auditing from remediation — we handle code remediation directly only for sites built or maintained by 54 Design Group, LLC, the design studio behind webcompliance.co. If your site belongs to another agency, we hand you a clear, plain-English roadmap your developer can act on directly.

Can I fix some of these myself, without a developer?

Yes. Our roadmaps sort findings into "Editor-Fixable" and "Developer Required." A lot of content-level issues — adding missing alt text, rewriting a text-heavy graphic — are things you can handle yourself right in your CMS.

Does a passing audit mean permanent compliance?

No. Accessibility is an ongoing practice, not a one-time achievement. New content, media uploads, or platform updates can introduce new issues over time. Our roadmap validates your site at the time of testing; we recommend a scheduled annual review to catch anything that creeps in as your site grows.

I already have a web designer. Can you still do the audit?

Yes. This is one of our most common engagements. We step in as an independent, objective third party: we conduct technical testing, write your Accessibility Statement, and provide your existing designer or developer with a roadmap they can act on without guesswork.

What do I actually receive at the end of the audit?

Every client gets a clear Technical Audit Report prioritized by severity, a remediation roadmap, and a publication-ready Accessibility Statement built for your site's footer. Developer-Ready tier clients also get a companion spreadsheet with exact CSS selectors and HTML fix snippets.

What if I just have a question about my specific site first?

That's a good place to start. Contact us, and we'll walk through your site's footprint, any platform-specific constraints, and what a right-sized plan would look like for you.