Sustainable by design: rethinking digital quality

Sustainability in digital is still often framed around infrastructure choices - hosting, performance and carbon reduction. But this is only part of the picture.

There’s growing recognition that sustainability is also shaped by how digital systems are designed, built and maintained. This can be seen in the W3C Web Sustainability Guidelines (WSGs), as well as the work of the Green Software Foundation, which provides more technical guidance for making sustainability part of digital products.

In other words, sustainability is not just about what the web runs on, but how it’s built.

Sustainability doesn’t stop at launch

Most digital products aren’t finished at launch; they evolve continuously. This isn't just about maintenance to keep things running smoothly, but adding new features, responding to changing requirements and fixing those hidden bugs that can pop up.

This means sustainability is not defined at release, but in the ongoing cost of keeping systems usable, stable and adaptable over time. Complexity rarely appears all at once. It accumulates. Small inconsistencies, assumptions and shortcuts made during delivery compound into long-term overhead.

This creates a hidden cost - ongoing effort spent maintaining and correcting avoidable issues rather than improving or extending the system.

The WSGs address both challenges through guidelines such as Follow a product management and maintenance strategy and Make deliverables understandable and reusable, which encourage long-term product support and maintainable, reusable documentation and code resources.

In each case, complexity creates additional work. And when that complexity is avoidable, so too is some of the time, effort and resource required to maintain it.

Better quality means less rework

Well-built systems don’t just perform better – they require less intervention over time. Higher quality reduces instability, reactive fixes and the costs of change.

In this sense, quality is not about perfection at launch, but about reducing the need for future remediation. This is where digital quality becomes an important part of the sustainability conversation.

Testing, performance, accessibility and other quality practices can help teams identify problems before they become embedded within a product. Finding and addressing issues earlier can mean fewer reactive fixes, less duplicated work and systems that are easier to maintain as they evolve.

It's something we've seen in practice through the partnership between Studio 24 and Zoonou, where bringing independent QA into projects earlier has helped identify issues sooner and reduce time-consuming fixes later in development.

The result isn't simply a better product at launch. It's a product that requires less avoidable effort to sustain over its lifetime.

Where accessibility and sustainability meet

Digital accessibility and sustainability can go hand-in-hand, with a number of sustainable web practices aligning closely with established accessibility principles. When accessibility and sustainability are considered early, it reduces the need for later workarounds, retrofits and duplicated solutions.

There are practical overlaps too. Clear and efficient user journeys can help people complete tasks with fewer unnecessary interactions. Consistent interfaces and reusable components can reduce duplication. Lightweight, well-structured experiences can improve performance while also supporting people using older devices or slower connections.

Accessibility and sustainability have different primary goals, but many of the decisions that create more accessible digital products can also contribute to products that are more efficient to use and maintain.

Building sustainability into everyday delivery

Quality can be difficult to capture through a single measure. In this context, however, a combination of objective and subjective indicators can help teams understand and track it over time.

These could include measures such as test coverage, defect rates, loading times, WCAG conformance and documentation coverage.

Importantly, these aren't necessarily new measures created for sustainability. In many cases, teams are already collecting this information as part of development, quality assurance, accessibility or performance work.

The shift is in looking at some of those familiar delivery metrics as sustainability signals too. Sustainability doesn't need a full framework overhaul on day one. Start small:

• Assign a sustainability advocate. Have a team member with relevant experience and knowledge take the lead.

• Measure first. Track measures such as defect rates, fix times, accessibility audit results and page weights before setting targets.

• Document as you go. Even lightweight documentation reduces the hidden cost of onboarding and maintenance later.

• Include accessibility and sustainability early. Retrofitting can be expensive; designing with both in mind from the start can avoid duplicated work later.

• Review complexity regularly. Small, scheduled reviews of code and user journeys can catch compounding issues before they become structural.

It's less about introducing another process and more about recognising how everyday decisions around design, development and quality contribute to the long-term sustainability of a digital product.

A sustainable web isn't built once. It's sustained through decisions made every day, not just at launch.

Complexity, quality and accessibility are important levers. Treating them as central rather than secondary can help us build digital products that are genuinely made to last - for people and for the planet.