Accessibility Scope & Deliverables: What Agencies Should Commit To (and What to Avoid)

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.

Why accessibility scope is so often unclear

Accessibility scope tends to break down because:

  • WCAG is broad and technical
  • clients ask for reassurance, not details
  • agencies want to be helpful
  • accessibility touches design, dev, content, and QA

Without structure, scope becomes implicit — and implicit scope is dangerous.

Confident agencies make accessibility explicit.

What agencies should always define in scope

1. WCAG version and level

Always state:

  • WCAG 2.2
  • Level AA

Avoid vague language like “WCAG compliant” without detail.

2. What’s being assessed

Define what accessibility applies to:

  • page templates
  • components
  • journeys (e.g. checkout, onboarding)
  • documents (if included)

Avoid phrases like “the whole site” unless that’s genuinely what you mean.

3. What’s not included

Explicit exclusions protect everyone.

Common exclusions include:

  • third-party tools
  • user-generated content
  • legacy documents
  • future content updates

Clear exclusions reduce friction later.

Accessibility deliverables agencies can stand behind

Design-stage deliverables

Through design-stage accessibility guidance, agencies can provide:

  • design accessibility reviews
  • component guidance
  • documented decisions
  • accessibility considerations for handover

These deliverables shape outcomes early and reduce rework.

Audit and verification deliverables

With WCAG conformance audits, agencies should deliver:

  • structured issue reports
  • WCAG references
  • prioritisation by impact
  • remediation guidance
  • scope statements

Avoid framing audits as pass/fail certificates.

Evidence and reporting deliverables

Clients expect evidence, not absolutes.

Good deliverables include:

  • issue tracking reports
  • remediation status
  • accessibility statements aligned to the scope
  • verification summaries

This supports defensible delivery.

Post-launch deliverables

With ongoing WCAG monitoring, agencies can offer:

  • regression detection
  • trend reporting
  • maintenance insights
  • continuous improvement support

This reframes accessibility as an ongoing responsibility, not a one-off.

If you’re helping your agency partner articulate accessibility to clients, our how agencies sell accessibility post offers useful framing.

What agencies should avoid committing to

Certain promises create risk immediately.

Avoid committing to:

  • “100% accessibility”
  • permanent conformance
  • legal compliance guarantees
  • responsibility for future content

Instead, commit to process, scope, and evidence.

How confident agencies present the accessibility scope

Strong agencies:

  • include accessibility as a defined workstream
  • explain deliverables in plain language
  • separate advisory, verification, and monitoring
  • document assumptions clearly

This builds trust and speeds approvals.

For guidance on pricing accessibility work once the scope is defined, see our pricing accessibility for agencies guide.

Where IncluD fits

IncluD helps agencies scope and deliver accessibility responsibly.

From design-stage accessibility guidance that informs early decisions, through WCAG conformance audits that provide clear, defensible evidence, to ongoing WCAG monitoring that maintains accessibility as sites evolve.

All delivered through a purpose-built agency accessibility platform designed for real delivery workflows.

Key takeaways for agencies

Accessibility scope works best when agencies:

  • define it explicitly
  • separate stages clearly
  • document exclusions
  • avoid absolutes
  • support accessibility over time

Clear scope isn’t defensive, it’s professional.

To see how accessibility fits into overall delivery workflows, see how WCAG fits into agency delivery.

Delivery teams can also benefit from our accessibility for delivery teams insights.


Platform

Blog

About

Pricing

Contact

Privacy Policy

Security Policy

Accessibility Statement

© 2025 IncluD