Why digital accessibility belongs in the business brief

Digital accessibility belongs in the business brief because it affects who can use a service, how easily they can complete a task and whether a proposed solution is worth pursuing. It is not solely a website concern: the same consideration can apply to web services, mobile applications and other digital technology.

Accessibility is a customer and product question

Accessibility and usability are closely connected. Both ask whether an experience is intuitive for people trying to achieve a goal in different circumstances. Treating accessibility as part of the initial problem definition helps a team look beyond a preferred feature set and consider the range of people, devices, contexts and constraints involved.

This is a strategic judgement rather than a promise of a universal commercial outcome. The relevant priority will differ between organisations. For some, the central concern may be customer access; for others, it may be service quality, brand expectations, internal users or the practicality of supporting a digital service over time.

Why late consideration creates avoidable project risk

A brief that assumes every customer will interact with a service in the same way can narrow the solution before the team has understood the problem. That can leave important user needs undiscovered until a project has already committed budget, scope and expectations.

Discovery is the appropriate point to examine what users are trying to achieve, the context in which they do it and the constraints that may affect a service. It should also establish whether there are particular accessibility requirements in the problem space. This makes accessibility part of deciding what should be built, rather than a late addition to a preselected answer.

What a stronger business brief should make visible

• Which users need to complete which important tasks, and in what circumstances?
• What assumptions are being made about devices, input methods, connectivity, language or confidence with digital services?
• Could the wider user journey include offline steps, other teams or other services that affect the experience?
• What constraints could limit the usefulness of the proposed solution?
• How will the organisation judge whether the service is working for the people it is intended to serve?
• Is building or changing a digital service the most viable response to the problem, or should other options be considered?

A better framing for investment decisions

The value of early accessibility consideration is not that every project follows an identical path. It is that the organisation makes a more informed choice. Understanding users and constraints can reveal whether a proposed service is viable and cost-effective, or whether the problem should be approached differently. Deciding not to proceed can be a sound outcome when the evidence does not support the investment.

For business leaders, the useful shift is from asking whether accessibility can be added later to asking whether the brief represents the people the service is meant to support. That places inclusion alongside customer experience, delivery risk and product strategy—where it can influence the quality of the decision, not just the finish of the product.