Orvellan Group
GLOBAL ADVISORY ◯
☰
Computer keyboard keys lit in blue and orange

ORVELLAN GROUP
ANALYSIS
Digital Economies

CLEAR STRATEGY.
SOUND DECISIONS.
PRACTICAL SOLUTIONS.

3 OCTOBER 2026 / Digital Economies

Digital Procurement Should Test the Whole User Journey

An attractive demonstration does not establish that people can complete the service. Accessibility belongs in the procurement brief, acceptance evidence and continuing ownership.

Illustrative photograph by Christian Wiediger / Unsplash. Not an Orvellan project or event.

Analysis · 3 October 2026 · 3 min read

A digital service can demonstrate its main screen convincingly while making an essential task difficult for some users. The obstacle may appear later: a form gives an unclear error, a document cannot be read with assistive technology or a confirmation step depends on a particular interaction. Digital procurement accessibility is therefore a question about the complete journey, not only the appearance of the opening page.

The procurement brief shapes the evidence available

W3C’s Web Accessibility Initiative planning guidance includes procurement, acceptance testing, responsibilities and resources in an organisation’s accessibility effort. Its implementation guidance discusses staff skills and evaluation early and regularly during development. These are practical process references. They do not certify a product, determine an organisation’s legal duties or establish that a single test can represent every user’s experience. W3C WAI: Planning Web Accessibility; W3C WAI: Implementing Web Accessibility.

The commercial implication is that a requirement becomes more useful when the buyer and supplier share an understanding of how it will be examined. A broad claim that a product is accessible can leave the applicable scope unclear. Does it cover the public website, administration interface, generated documents and third-party components? Does the evidence relate to the current version? The answer may be more nuanced than a single label suggests.

Follow a realistic task beyond the demonstration

Imagine a hypothetical online application service. A visitor must find eligibility information, enter details, review an error, submit the application and keep a usable receipt. Testing only the successful submission path can miss how the service behaves when a required field is incomplete. Testing only the browser interface can miss a barrier in the downloaded receipt. The service exists across these stages, even if responsibility is divided between suppliers.

A task-based review can examine these interfaces without claiming to replace specialist accessibility evaluation. It can also reveal operational questions: who corrects content, which supplier controls a component and what happens when a user reports a barrier? These details affect whether an issue is actionable after launch. A finding with no responsible owner is evidence of a problem, not evidence of a remedy.

Balance consistent requirements with changing systems

A procurement process needs enough specificity to support acceptance, while recognising that content and software change. A platform can receive updates, a team can publish new documents and an external service can alter its interface. Evidence tied to one version cannot automatically describe later versions. Continuing responsibilities and review points are therefore part of the commercial arrangement, rather than a separate concern postponed until complaints arrive.

There is also a balance between standardised checks and diverse experience. Automated checks can identify some issues efficiently, but they do not establish that all tasks are understandable or usable. Specialist review and appropriately arranged participation by users can add different forms of evidence. The relevant scope, methods and protections need to be defined rather than inferred from the mere presence of a test report.

  • Which complete user tasks and generated outputs are included in acceptance?
  • What evidence supports the accessibility claim for the actual version being purchased?
  • Who owns defects that cross content, software and third-party boundaries?
  • How are reported barriers assessed, prioritised and followed through after launch?

The takeaway is that accessibility becomes easier to govern when it is connected to procurement and continuing service ownership. A complete journey gives the commercial discussion a more concrete object than an attractive demonstration. This article is general digital governance analysis, not a conformance assessment, legal opinion or assurance about any platform.

Sources reviewed on 3 October 2026. This analytical perspective reflects the information available at that date. Explore Digital Economies and all insights.

Explore more perspectives.

BACK TO OPINIONS →
Ask AI about us

Copy the suggested question, then choose an AI service. Opens an external website; sign-in may be required. Check answers against the cited sources.