Blog
A practical guide for agencies on scoping accessibility work, defining WCAG deliverables, and avoiding overpromising in proposals.
Accessibility projects don’t fail because agencies don’t care, they fail because the scope is unclear.
As accessibility becomes a standard part of digital delivery, agencies are increasingly expected to define what’s included, what’s excluded, and what “done” actually means. When this isn’t handled carefully, accessibility becomes a source of risk rather than confidence.
This guide explains how agencies can scope accessibility work clearly, define deliverables responsibly, and avoid the most common overcommitments that create delivery and legal exposure.
Accessibility scope tends to break down because:
Without structure, scope becomes implicit — and implicit scope is dangerous.
Confident agencies make accessibility explicit.
Always state:
Avoid vague language like “WCAG compliant” without detail.
Define what accessibility applies to:
Avoid phrases like “the whole site” unless that’s genuinely what you mean.
Explicit exclusions protect everyone.
Common exclusions include:
Clear exclusions reduce friction later.
Through design-stage accessibility guidance, agencies can provide: