Last month I had the pleasure of speaking at the Digital Ethics Forum in Turin. The event was organised by Sloweb, an organisation founded in Italy to promote a more ethical and environmentally friendly approach to digital technology, inspired by the Slowfood movement that started in Italy in the 1980’s as a response to the emergence of fast food. Slowfood promotes a food system with three core principles, of being good (in terms of quality, flavour, and seasonality), clean (sustainable and kind to the environment), and fair (accessible pricing and dignified conditions for producers). Sloweb takes a similar approach to the digital information that we consume, promoting an Internet that is lean, clean and fair.
Every two years, Slowfood organises a big international food festival in Turin to celebrate and educate people about the Slowfood movement, called Terre Madre del Gusto, and this year’s Digital Ethics Forum was co-located in Turin as part of the bigger festival. When I was invited to speak by Sloweb co-founders Nicola Bonotto and Pietro Jarre, the opportunity to travel to such an amazing city and meet up with like minded friends promoting ethical approaches to digital was unmissable.
I took part in a session with Gerry McGovern, author of the landmark book World Wide Waste and more recently 99th Day, and Thorsten Jonas, founder of the Sustainable UX Network (SUX) and it was an honour to present alongside two people who I have so much admiration for.
Myself, Gerry McGovern and Thorsten Jonas after dinner at a vegan restaurant in Turin on the day of our talks
Gerry talked about the physical nature of our virtual world and the incredible toll it takes upon not just our Earth’s natural systems but also indigenous and marginalised communities around the world. It was a powerful call to pause and question our incessant greed and hunger for ever more digital consumption.
I then gave a talk titled ‘Salt, Fat, Sugar, Data’ that picked up on the thread of this of never ending digital hunger and explored the parallels between the human food system, which has gradually shifted from a sustainable natural system that deeply nourishes us to an industrialised system designed to cultivate addiction to empty, high profit foods. I highlighted how the same pattern has played out in our information systems, leading us to today’s world where we are addicted to constant snacking on low quality information that drives corporate profits. I hope to write another article in the near future to share this story in more detail.
And then Thorsten picked up the AI thread talking about the true price of AI, a theme that had been explored at the previous day’s SUX session. He talked about how we have the power to shape our own interactions and usage of AI and not simply be passengers. A key part of this is to recognise the innate wisdom that we have as human beings, including our ability to tune in to “weak signals” that are sometimes more important than the hard data that is accessible to an AI, and that when we outsource our own roles to an AI we actively de-skill ourselves and make ourselves more dependent on AI in the future. Perhaps the most powerful message of the session was these four words — “Brain first, AI second.” And yeah, I added that emdash myself!
More broadly the Digital Ethics Forum had an incredible range of sessions in both English and Italian, covering topics from ‘Human Rights in the Age of AI’ to ‘The Right to Repair’ as well as case studies of digital projects pursuing ethical practices and uses of digital technology. And to top it off, unlike the food festival that mostly happened outside in the forum of street markets, the Digital Ethics Forum took place in an arthouse cinema where a range of films relating to the ethical use of digital technology were screened in the evenings. Speaking of which, there is a Sloweb documentary currently in production, so watch this space!
Following in the footsteps of Slowfood, the Sloweb movement is growing in momentum and spreading beyond Italy, so if you want to get involved then do check out their website and get in touch with them to see how you could collaborate.
It can feel overwhelming in these times of rapid AI acceleration, but coming together as a community to develop and promote more ethical approaches to digital has never been more important.
I don’t know about other people but I often feel like AI is something that’s imposed upon me, rather than something I’ve chosen to engage with. AI features are added to software products whether you want them or not. AI search has changed the way I find information and track site metrics. Discourse in the tech world, sustainability focussed or otherwise is overwhelmed by AI and big data centers.
It makes it hard to feel in control when it comes to AI. Which is what makes the announcements Cloudflare made this week so intriguing and maybe even hopeful. Have site managers been granted a modicum of control when it comes to how AI interacts with their websites?
Let’s find out.
Cloudflare offers security and content delivery services and is used by just over 20% of sites on the internet. As a service provider they’ve been dealing with some of the infrastructural issues that AI presents since the beginning. AI platforms use crawlers to gather information to provide search and chatbot users as well as hoover up content for model training. For Cloudflare and the sites using it, that can cause issues.
Huge numbers of crawlers hitting multiple site pages at the same time can act in the same way as a DDOS attack. This can overwhelm hosting servers, rendering sites temporarily unavailable or slow and unresponsive. Not only that but bots can also quietly chew through bandwidth quotas, leaving organisations with increased site hosting bills for little to no increase in site visitors or engagement.
How to deal with AI crawlers, scrapers and bots has been a fundamental question for Cloudflare. After much discussion and behind the scenes negotiations, it appears they are coming up with some interesting answers.
Content Independence
Recent announcements have their origins in 2025’s declaration that July 1st is “Content Independence Day”. Since the early days of the internet there has been a co-dependency between search engines and content owners. Search engines need content creators to bring users to their platforms. Content creators need search engines to make their content discoverable for a wider audience. Cloudflare and others contend that chatbots and Google’s AI summaries and search results constitute a breaking of this agreement.
“Content is the fuel that powers AI engines, and so it’s only fair that content creators are compensated directly for it.” This year, their second Content Independence Day was marked with two significant announcements: A “pay to crawl” framework and more options for content independence. They detailed new options to allow a more granular and nuanced approach to bot and AI traffic. The new features came into effect on September 15th and are worth exploring, not only for the options they provide to organisations but also the reasoning behind them.
Maintain discoverability AND choice
Cloudflare’s new features reflect an issue that web managers have been grappling with for a few years. If you want your website to be discoverable, the price is that your content will be used to train AI models. This happened because the major players in the field, Google and the like, use what they call “mixed-use” crawlers. These crawlers performed a dual role for training AI models and search indexing. The choice was binary, refuse both or allow both, with no middle ground.
This “either/or” choice didn’t reflect the nuance involved. There are myriad reasons why an organisation might want to opt out of training AI:
Reputational Grounds — A topic like the holocaust is an emotive matter of historical fact that is called into question by bad actors. Telling the truth about it unflinchingly, definitively and authoritatively is a moral imperative. How do you approach discoverability on LLMs for this topic?
Ethical Grounds – Organisations working to protect Data Workers’ rights in Africa and Asia might legitimately want to ban AI access while remaining discoverable in search
Solutions for this dilemma have been tricky to find. In the past robots.txt has represented a “gentlemen’s agreement” as to who and what can access areas of your website. Recent times have seen this agreement ignored by crawlers and scrapers. Cloudflare has been working directly with AI operators to help people take back control. They’ve gained their that their bots will meet the following requirements:
A mechanism for site owners to opt out of AI training, through robots.txt or a similar standard.
A mechanism for site owners to opt out of AI summaries set with the operator directly
URL-level visibility into which pages were made available for training, along with metrics showing how content appeared in search.
Assurance that opting out of AI training will not affect traditional search results.
These requirements along with Cloudflare classifying bots by behaviour and intention help users of the platform have more control. They classify three behaviours:
Search – crawling to build a search index.
Training – crawling to train or fine-tune a model.
Agent – user-directed agents visiting a page on behalf of a human, such as chat fetch bots and browser-use agents.
By classifying these behaviours, you can allow a mixed use crawler to carry out search indexing while blocking content from training. Cloudflare claims that taking actions to disallow training bots will not affect search performance or rankings.
These new controls are already in place. You don’t need to make changes unless you want to. If you are using Cloudflare we would encourage you to check your settings and confirm that they reflect your requirements.
An opportunity to discuss your AI access
Moreover, this change represents an opportunity to think about your sites’ relationship with LLMs and search summaries. If you’ve been uncomfortable with compromises you’ve had to make, now might be the time to see if you still need to make those compromises. Much has been written about the threat AI search and chatbots pose to discoverability and open web principles. Cloudflare taking this option shows big AI companies that they’ve had it their own way for a little too long.
Could this be the start of some rebalancing? I certainly hope so.
If you’re a Wholegrain client and would like to explore what this new functionality could mean for your site, please get in touch with your project or account manager.
If you’re a prospective client affected by some of the issues outlined in the article and want to speak to someone about them, contact Chris to see how we can help.
Today’s post is a collaboration between myself, Tom Greenwood, and Michael Andersen, a fellow digital sustainability advocate and author of the book Sustainable Web Design in 20 Lessons.
Michael got in touch with me recently with a rather interesting question — if people are increasingly getting their information directly from AI services like ChatGPT, Claude and Grok, should we still be designing websites for humans? Put another way, is the primary audience for a website in the future going to be non-human intelligence?
This is a rather provocative question, and as Michael and I both care deeply about the environmental and social impact of the web, it is one that we should not ignore.
Of course, the idea that we might have to consider robots when designing a website is not entirely new. There has long been a tension between the need (and desire) to provide the best experience to human users while also needing to optimise websites for higher search rankings. The robots have been exerting power over us for a long time already. However, until recently the robots were simply the gatekeepers controlling who actually finds their way into our websites. With the rise of AI services, the robots are stealing our content and locking the gates behind them.
This poses some interesting challenges for any person or organisation that has a website, and in the process forces us to ask some deeper questions about what we actually want the Internet to be moving forward. It’s easy to jump to the conclusion that this is an inherently bad thing, and it’s certainly not all good, but Michael and I want to hold space to consider the challenges alongside the possibilities with open minds, to imagine how we might evolve the web positively for this new era.
The AI traffic paradox
In recent times we’ve seen a number of clients at Wholegrain Digital experience significant spikes in their web hosting traffic as a result of AI bots constantly crawling their pages for information. This can come at a real financial cost to the client, not to mention the environmental impact, and it raises the question over whether we should block AI bots from our websites.
At the same time though, Michael highlights that some organisations have seen significant drops in web traffic coinciding with the rising popularity of AI services such as ChatGPT. At Wholegrain we have seen ChatGPT appear as a new traffic source for some websites, but at this stage it’s mostly a small one, as fewer people tend to click back to websites from their AI answers compared to traditional search engine results. Not to mention the fact that Google now provides AI answers at the top of its search results these days, reducing the need for the website “visitor” to um… visit.
Even Google search now prioritises AI answers above links to actual websites
So we have AI companies causing a significant increase in artificial traffic to websites, while also reducing the human traffic to those same websites. And yet the place where these AI tools get their information from are these very same websites. Websites that people have invested a lot of time and money into designing, building, and maintaining, as well as creating content for.
This article isn’t about arguing the injustice of this situation, but to sit with it and acknowledge that we are in something of a paradox. AI services need a thriving Internet full of rich information in order to do what they do, yet they simultaneously erode the incentive for people and organisations to invest in creating a thriving web. The snake is eating its own tail.
Visiting the source
In our discussions, Michael highlighted a key feature of this changing dynamic being that websites are increasingly treated as sources of information, rather than destinations to visit. If AI companies have their way, much like social media, people will spend most of their time on these new platforms and not leave. In this sense they really don’t care about your website other than it being a source of data to mine.
But it’s likely that if you have a website, then you do care that people visit. You likely have reasons, whether commercial or not, to want real human beings to visit your website. You could, as some are doing, block AI crawlers from your website to discourage them from mining your website and attempt to ensure that the information on your website is really only available by visiting your website. This may work for some, but as people increasingly use AI tools as search engines, blocking AI crawlers entirely is not dissimilar to blocking Google from your website. It’s a bold and admirable ethical stance, but it might not be very practical in many cases. So what can we do instead?
My personal view is that we may need to design hybrid websites, facing the tension head on by separating the needs of humans from the “needs” of robots, but neglecting neither. We can compartmentalise, at least partially, the destination for humans, and the source of data for machines. In doing so, we might actually create a win-win and unleash a new wave of human creativity in web design, reversing the long term trend of websites “all looking the same.” Let me explain.
The human experience
One of the things that this new dynamic highlights is that some people go online in search of answers to questions, and LLMs are increasingly taking this role. However, the user experience of LLMs tends to come in the form of long text based responses, or a digital voice speaking these same answers. What they don’t provide is the rich, immersive experience that has for a long time been a significant part of what people enjoy about going online. It could be argued that in the past decade or so, as User Experience “best practices” have become more firmly established and websites have been optimised for search rankings, the web has become increasingly bland compared to its earlier days when website design was a truly creative practice.
We now have an opportunity to reverse that trend by prioritising the human visitor not just in terms of ease of use, but in terms of the richness of experience that we offer people. Websites that are truly beautiful, immersive, joyful and thought provoking in their design, and which people want to visit because they are places that people actually want to be rather than just sources of dry information.
This also includes the tone of voice of the content, which is generally very bland in LLM tools but can be much more expressive on your own website, especially if there is now less need to awkwardly jam our content full of SEO keywords. This will allow us to enrich people’s experiences and convey the spirit of our brands in ways that an LLM likely won’t, making our own websites a more authentic expression of what we really have to say.
The website for Tom’s book Overton’s Garden includes visual and audio features designed specifically to give humans a richer experience
We could compare this to the shift we are seeing in high streets, whereby generic, uninspiring shops have struggled to compete with online retailers, but it has left an unmet need for unique, enjoyable experiences that people cannot get from shopping on Amazon. When high street retailers shift their perspective to see themselves as destinations to be experienced rather than just places to buy things, people do make the effort to leave their homes and go into town. Similarly, when we view websites this way and design experiences that people genuinely enjoy visiting and even want to share with their friends, we create something that the LLMs cannot replicate, even if they steal some of our content.
Of course, my comparison with high streets runs out here as some of the organisations that have the greatest opportunity to do this are likely those with some element of e-commerce. There is an inherent opportunity to inspire potential customers with rich visual information about the products, and interactive tools to help them understand products better and choose what is right for them. Of course we want to do this in a way that is accessible and environmentally efficient, but there are huge opportunities here for creativity. To quote my colleague Chânelle Sharp, a designer at Wholegrain, “the design of websites will shift to work even harder for the user now”. I think that is a good thing, with web design in the near future becoming much more about digital storytelling.
People are time poor and so instead of wasting their time with large reams of text intended mostly for Google, user experiences could actually cut back significantly on written text in many cases and just give people exactly the information they need, in a beautiful and engaging format. And despite the downsides of these AI tools, it may just be that AI coding tools in the long term will make it easier for organisations to create rich functionality and design features such as visualisations, personalisations, dashboard, calculators, and interactive journeys, that were previously beyond their budgets. It may well be therefore that AI coding will gradually reduce one of the key limiting factors in doing really exciting things online.
Then come the robots
If we design websites primarily for humans once more and relegate the AI and search crawlers to second class citizens of the web, then you may be wondering, how do you get your website featured in search results and AI responses? I think the answer might be to have a secondary layer of a website that is purely informational, with large repositories of high quality written information and raw data relating to your organisation and area of expertise. These repositories can include high quality original data, white papers, academic research and the like, making them a rich source of quotable information for the LLMs. These pages can be crawled by crawlers without getting in the way of human visitors, and to quote Chânelle again, “if the information is purely informational, then maybe it doesn’t even need to be designed”. This second layer of a website could be super efficient by virtue of not being mixed in with the presentation elements such as imagery and custom fonts that are there only to improve the experience of humans.
The UK Green Building Council integrated HOLP to help human visitors find key information directly on their own website
But what if your visitors do want to access some of this information from your data repository while they are on your website? This is where a more efficient LLM tool tailored just to your website may provide the answer. Tools such as HOLP, which we used for the UK Green Building Council, can provide answers to the questions of the people who have arrived at your website, without them having to leave your website and unlike mass market AI tools, they can provide trusted answers as they are trained to provide information from your own websites information repository (as well as its user facing web content). This is a win for the human visitor who is seeking specific information that may not be easy to find in the standard user facing content, and for the organisation who is able to meet the unique needs of such visitors without complicating the user experience for other people.
I’ll hand over to Michael now to discuss how some of this might be achieved on a practical level.
Down at street level
I want to begin by saying how excited I have been to write this alongside Tom. Ever since I first read his book Sustainable Web Design, he has been a constant source of inspiration to me. The hybrid idea he lands on, a light and human surface sitting on top of a denser layer meant for machines, is the thread I want to follow, though I would not want to give either of us too much credit for it, since the web has been built in roughly this shape for a long time and most of us have simply taken it for granted. What feels worth examining now is not the layers themselves, but the question of who that hidden layer is increasingly being built for, and that is where my own corner of the work comes in.
That corner is the code itself, where I tend to sit rather than up above it looking at the strategy. Tom has been describing the shape of all this from above, the way you might look down at a city and see how the roads connect to one another, and I want to stay down at street level for the rest of this, because it is down there that the same question we kept circling stops being philosophical and turns into something you can put your hands on. It becomes a question about which file you create, and what you put in it, and who you imagine reading it. So where Tom has been holding the why of all this, I want to spend my half on the how, on what the hybrid he describes actually looks like when you are the one who has to build it.
The plumbing underneath the page
If you have ever sat and built a website properly, not just made it look nice but actually built it so that it holds together, then you already know that a page is never only the thing the visitor sees. Underneath the colours and the images and the words arranged on the screen, there is a second version of the same page that almost no human ever really looks at. There is structured data, little labelled notes in the markup that say this is the price, this is the author, this is the date, this is the review, and here is how many stars it got. There is JSON sitting in the background, describing the page in a way that is clean and predictable and easy for software to read. And none of this is particularly new to anyone who builds for the web, because we have been doing it for years, mostly so that search engines could understand our pages well enough to rank them, and most visitors have never had any idea it was there.
To make that a little less abstract, it helps to picture what one of those hidden notes actually looks like in practice. If I have written an article, I might tuck a small block of structured data into the page, written in a format called JSON-LD, which is really just a tidy way of listing plain facts so that a machine can read them without having to guess. In ordinary words, the block says something like, this thing is an article, its headline is this, the person who wrote it is this, it was published on this date, and it belongs to this larger publication. None of that changes a single pixel of what you see on the screen, and you could read the article perfectly well without ever knowing the block was there. But a machine that lands on the page no longer has to work out who the author is by hunting around the layout and hoping it has guessed correctly, because you have simply told it, in a vocabulary that thousands of other sites use in exactly the same way. That shared vocabulary is what people mean when they talk about schema, and the whole point of it is that meaning stops being something a machine has to reconstruct and becomes something you have stated plainly.
What is changing now is the kind of reader that layer is starting to serve. There is a proposed convention that appeared back in 2024, suggested by Jeremy Howard, who is one of the people behind Answer.AI, and it is called llms.txt. The idea is almost touchingly simple. You place a plain markdown file at the root of your website, the same way we have placed a robots.txt file there for decades, and in it you lay out, in clean and readable text, the parts of your site you actually want a language model to read. No clutter, no menus, no scripts, no advertising, just the meaning, served plainly.
The Overton’s Garden website includes an llms.txt file just for AI bits, but will this concept catch on?
And because it is only markdown, building one is genuinely something you could finish in an afternoon, which is part of why it interests me so much. You open a plain text file, you name it llms.txt, and you place it at the very root of your site so that it sits at a predictable address the way robots.txt always has. At the top you write the name of the site and a sentence or two describing what it is and who it is for. Then you write a short list of links to the pages that actually matter, your best writing, your core explanations, your reference material, and after each link you add a handful of words saying what a reader will find there. That is more or less the whole thing. If you want to go a step further there is a fuller version, often kept as a second file, where instead of only pointing at your important pages you include the full cleaned up text of them, so that a model has the real content in front of it rather than just a map showing where the content lives. Either way, what you are really doing is curating. You are deciding, on purpose and in advance, what you would want a machine to understand about your work if it only ever saw the tidy version and never visited the site at all.
I want to be honest about what it is and what it is not, because it would be easy to oversell it. It is not an official standard, and Howard himself has said as much. The big AI systems do not reliably read it yet, and by now more than one fairly large study has looked at the question and found that adding the file does not measurably change how often a model mentions you, with one analysis of around three hundred thousand sites finding essentially no difference at all. Google has even said, fairly plainly, that it has no plans to support it. And yet hundreds of thousands of sites have already added one, including a few names you would recognise, and people who have watched the web for a long time keep comparing it to the early days of schema markup, back when that too looked like a niche curiosity that later turned out to matter a great deal.
And this is where I want to put the practical heart of it, because it would be easy to read everything above and imagine that building Tom’s hybrid means building two entire websites, one warm and human and one stripped bare for the machines, two of everything and twice the work. You can do that, and for certain things you genuinely should, but for most of a site the truth turned out to be stranger and a good deal kinder than that. If you have already built the human layer properly, with markup that is clean and honest about what each thing is, with real headings and real buttons and images that are actually described, then you have already built most of the machine layer without ever thinking of it that way. What you add on top of that is thin. A little structured data to state plainly what the important things on the page are, and an llms.txt file at the root to hand a model the tidy version of what you most want it to read. That is the bulk of the work, and almost none of it is a second website. It is mostly just the first website.
Where the two layers do genuinely come apart is in the place Tom pointed to, the large stores of pure information, the white papers and the raw data and the long reference material that exist mainly to be read rather than to be experienced. For that kind of thing it really does make sense to build a separate and lighter layer, plain pages or plain markdown with almost no presentation wrapped around them, so that a crawler can read them cheaply and a person who actually wants the underlying detail can still reach it without having to wade through it on the main site. So when I try to picture the hybrid in concrete terms, it is not two parallel websites standing side by side at all. It is one human site built well enough that it serves the machines almost for free, sitting next to a small and efficient archive for the heavy reference material that nobody really wanted dressed up in the first place.
And this is the moment I really wanted to reach, because when you sit with all of this at once, you start to notice something a little strange, and a little hard to name. The future Tom was describing, the website that is one thing for people and another thing for machines, is in some sense already half built. We just never called it that. We built the human layer because we cared about people, and we built the machine layer because we wanted to be found, and now that machine layer is slowly turning into the thing that reads our work on the reader’s behalf. It is a bit like discovering that a path you have been clearing and maintaining for years leads somewhere you never expected it to go.
When accessibility starts serving the machine
There is one corner of all this that I have not been able to stop thinking about since my call with Tom, and it has to do with accessibility. For most of my career, the work of making a website accessible has been understood as work we do for people. The Web Content Accessibility Guidelines, which most of us just call WCAG and which are looked after by the people at the W3C, exist so that someone who cannot see the screen, or cannot use a mouse, or who processes information differently, can still move through a website and understand it. In practice, when we talk about meeting those guidelines, we usually mean building to a level they call AA, which most teams treat as the realistic target, and the work of getting there is made up of a hundred small and very ordinary decisions. You write alternative text that genuinely describes what an image shows rather than leaving it empty. You use headings in a real order instead of choosing them for how big they happen to look on the screen.
You label the fields in a form so that it is clear what each one is asking for. You make sure every part of the page can be reached and operated with a keyboard alone, and that the text has enough contrast against its background to be read by someone whose eyes are tired or beginning to fail. None of it is glamorous, and almost none of it ever shows up in a screenshot, but it is the difference between a site a person can actually use and one that closes its door to them. Here in Europe that work has recently stopped being optional in a lot of cases, because the European Accessibility Act came into force in the summer of 2025 and now expects a great many digital products and services to meet exactly these guidelines. So accessibility has been on a lot of minds lately, and rightly so.
But here is the part that feels strange to me. The whole craft of accessibility has always been, underneath everything else, the craft of making meaning explicit. You write your markup so that a screen reader, which is itself a machine, can correctly understand what is a heading and what is a button and what an image is actually showing. You describe things in plain words so that software can relay them faithfully to a person who needs them in some other form. In other words, we have spent years and years learning to make our websites legible to a machine, because a machine was the thing standing between our content and the human who needed it. We just thought of that machine as an assistant working on behalf of a person, which it was.
And once you see it laid out like that, the overlap with everything I was describing earlier stops feeling like a coincidence and starts to look almost like the same task wearing two different faces. The alternative text you wrote for a blind visitor is meaning made explicit, and a language model wants that exact thing. The heading you marked up honestly so that a screen reader could announce it is structure made explicit, and a model trying to make sense of your page wants that too. The form field you labelled, the button you named properly, the landmark you added so that someone could skip straight to the main content, every one of those is intent stated plainly rather than left to be guessed, and plainly stated intent is precisely what this new reader is hungry for. Which means that in very practical terms, if you build a site to that AA level for the people who actually need it, you have quietly built a large part of your machine layer at the very same time, and the two reasons for doing the work, the human one and the technical one, turn out to be pointing in the same direction.
Now another kind of machine is arriving, the language model, and it turns out that much of the work we did to make the web kinder to people has also, almost by accident, made it more readable to this new reader. The structure, the explicit labels, the meaning made plain, all of the things we built for the person using assistive technology turn out to be more or less exactly the things a language model also wants. I find that both hopeful and slightly unsettling, and I do not think I am supposed to resolve which one it is. It is hopeful because it might mean that good, accessible, carefully made websites are simply ready for this new era without anyone having to compromise anything. And it is unsettling because there is something odd about realising that work you did for the most human of reasons also serves something that is not human at all.
And then it opens a question I genuinely do not know the answer to. If a language model can read the raw, structured meaning of a page and then reshape it into whatever form a particular person needs, spoken aloud, simplified, translated, slowed down, made calmer, then it is at least possible that AI becomes a better companion for people with accessibility needs than many of the tools we have today. The same shift could even help companies that have never been able to afford a genuinely good, accessible experience, because the model sitting in front of their content could, in principle, give their visitors a kinder journey than their own budget ever allowed. I want to hold that possibility gently rather than promise it, because we have all heard a great many promises about what AI is supposedly going to fix. But I would be lying if I said the thought did not move me a little, that the very thing reshaping the web might also, if we are careful and a bit lucky, make it gentler toward the people it has so often left behind.
AI as a search tool
I want to slow down here, because there is a worry underneath all of this that I have been turning over for a long while, and I am wary of how I say it, because it would be very easy to make it sound like I am complaining about the way people read now, and that is not what I mean at all.
At my job we have spent time talking with young people about how they find things out, and one of those conversations has stayed with me. A teenager said, more or less, that AI made the person lazy, that when something can simply be handed to the person, the person loses the urge to go and chase the answer. I want to be careful and call this what it honestly is, which is one young person being candid in one conversation, not a study and not a verdict. But it landed on something I had been feeling for a while without quite having the words for it. Because if the answer can be had instantly, without arriving anywhere at all, then a certain kind of journey simply stops happening. Not the journey through a checkout or a menu, but the one where you go looking for something, and you end up somewhere you did not plan to be, and you leave a little changed by having been there.
For a long time I think we treated that journey as part of the value of the web, even though we never wrote it down anywhere or put it in a proposal to a client. You arrived at a site, you read more than you came for, you understood the people behind it, you caught their tone of voice, you felt that there was a person or a team or a belief on the other side of the screen. That was never really about the information. The information was almost the excuse for the visit. And my worry is not that people have become lazy, but that we are building a version of the web where that kind of arrival is no longer necessary, at least for everything that can be reduced to a quick answer. I do not think that is the whole web, and I do not think it has to be a tragedy. But I think it is worth noticing what we might be letting go of while we are busy admiring everything we are gaining.
And I notice, sitting here at the practical end of all this, that my worry is really the shadow of Tom’s hope. He is hopeful that we will build places worth coming to, websites so rich and so genuinely worth the visit that people choose to arrive even when a machine could have spared them the trip. I share that hope, more than I probably let on. But the thing I keep turning over, down here where the pages actually get made, is whether the arriving itself is quietly being designed out of the web, and whether all the craft in the world can pull someone back to a place they no longer have any reason to go.
The questions I cannot put down
So I find myself ending more or less where Tom began, holding a handful of questions rather than answers, which I have come to think is the honest place to stand.
Are we still designing for people, or are we slowly becoming translators, standing in between humans and machines, trying to serve both at once without fully belonging to either? When a language model has already read everything on the page before the person ever arrives, what is the visit itself actually for, and what is left inside it that still matters? And if the model becomes the thing that shapes how our work is understood, I find myself wondering whether it might end up building better journeys through that work than we do, and whether, a little further down the same road, we will still need the style guides and the UX designers and the graphic content, or whether those become a luxury rather than a default.
I wonder too about the places that exist almost entirely to be read; the Wikipedias and the reference sites and the great open stores of knowledge, and whether they will one day be built in a wholly different way, written first as plain markdown for the machines rather than dressed up in markup for us.
I am not sure either, when it really comes to it, whether companies will simply hand the whole customer journey over to the AI sitting in front of their content, having decided that a more accessible and more helpful experience, delivered by a machine, is worth more to them than the elaborate one they once paid so much to design. And if plain text is becoming the shared layer that the machines hand out for free to anyone who asks, then what becomes the thing worth keeping precious, the thing we still make slowly and by hand precisely because it cannot simply be read out by something else and passed along? I do not have clean answers to any of these, and I am not sure I trust anyone who says they do.
What I do know is that the question Tom opened with, whether we are still designing for humans, is not really a question with a yes or a no waiting at the end of it. It is more like a question we are going to be living inside of for the next several years, whether we choose to or not.
He audits and consults on websites with a focus on efficiency, security, inclusivity and accessibility (WCAG), and works full time as a web developer in Odense, Denmark.
Tom Greenwood
Tom is co-founder of Wholegrain and author of the book, Sustainable Web Design. He’s been featured in media including the BBC, CNN and the documentary film Responsible, and writes Oxymoron on Substack to inspire expanded thinking on how to create more sustainable and harmonious businesses, societies and lives.
Check out Tom’s new book, Overton’s Garden, and embark on an unexpected journey outside the window of acceptable thought to reignite your creative hope and empower you to help create a better world.
We are obviously a WordPress agency but that decision wasn’t made lightly or without considering all of the options. If you’re reading this it probably means that you’re interested in WordPress, worried about its security levels (don’t believe the press, its secure!) or we’ve linked you here.
Either way, welcome! Lets get started…
01. Trusted & Secure
It’s incredibly easy to make WordPress secure, mainly because the core is so well maintained and patched so the addition of hosting and domain encryption or SSL certification adds to the security. You may have heard the not so pleasant hype that WordPress isn’t secure but powering over 43% of the web, there is a reason WordPress is so well established and such a trusted platform. Based on its share of the internet, WordPress hacks are actually a lower proportionality. As with most CMS platforms, the security does also depend on maintenance and the actions of the developers / owners and so with Wholegrain’s Maintenance, that security is optimised for you.
02. Simplicity
It’s easy to build user friendly interface, making it easy for you and your team to on-board, update and edit your site. This level of control means your site won’t need a developer or expert to update it – saving time and budget! WordPress enables consistent, iterative and long-term growth, not a new site every few years – its that simple.
03. Scaleable growth
The WordPress framework makes it easy to create multiple websites under one umbrella, maintaining consistency of your brand whilst also enabling some great opportunities to grown your wider digital estate in a easy, logical way. Not only that, it can also handle everything from simple forms to e-commerce thanks to the use of a combination of out of the box and custom functionality. For Wholegrain, we have our own WrodPress theme that pushes this adaptability even further!
04. SEO friendly
WordPress not only comes with its own core SEO functions, but it’s also enables easy SEO best practice. At its foundation, WordPress is built using clean, structured code – which SEO loves! You can easily add custom permalinks and manage meta data to further feed your WordPress site to the search engines, which also help with your accessibility too. WordPress also enables fast loading and image compression with ease, making the site more sustainable and as we always say at Wholegrain – a sustainable site, is an SEO friendly site.
05. Open source
Meaning you own your own site, and have a community of expert knowledge to lean on and collaborate with. For us, this is a huge benefit and our team learn and grow form the community all of the time (and vice versa). There is a side effect of this too, which we don’t like to talk about, but should you ever decide to move away from Wholegrain, finding a developer to work on your site is also easy because of this open source nature.
06. Cost effective
This may be last on the list, but it has a big impact. Firstly, lets start with the lack of licensing fee for the core software and because it’s open source, its free to install – none of those nasty Drupal updates that cost a fortune every year. You will have read further up that WordPress has a large community behind it and this manifests plugins, themes and a professional network of developers meaning not everything needs to be from scratch and support is easy to find.
So WordPress is safe, cost effect, great for sustainability and SEO whilst also enabling some strong growth of your site. It’s easy to see why WordPress is Wholegrain’s platform of choice.
We work to accelerate the shift to an Internet that’s good for people and planet.
This mission runs through our organisation like a stick of rock. Sometimes it’s a balancing act. At times we are focussed more on one element than another.
Website Carbon as an Internet for Good accelerant
Website Carbon is one of the ways we aim to shift towards a better internet. Since its launch in August 2018 the tool has been used to test over 1 million individual webpages, for free. For many, using the tool has been a stepping stone into larger actions within digital sustainability. It certainly was for me and many of my colleagues at Wholegrain.
How websitecarbon.com looked when it launched in 2018
We take the stewardship of Website Carbon very seriously as a result. It means that making any changes to the site takes time and care. The last major update came in November 2023 when we added a rating system to the tool. The ratings give more context to the results and allow for better benchmarking.
Since then the calculator has remained stable but relatively untouched, until today.
A major update to Website Carbon Calculator
On the 14th July 2025 we updated the calculator to the V4 of the Sustainable Web Design Methodology (SWDM). V4 is the latest version of the model. The process of updating the calculator has been delicate and one we were keen to get right the first time. Any issues that erode trust in the estimates the tool provides need to be avoided.
After extensive testing Website Carbon is now updated. If you have a keen eye you might see some changes to the results it provides.
How are things different now?
V4 is a major update to the SWDM and things are quite different under it.
For one thing you might notice that the estimate your website receives in V4 is lower than in V3. Sites tested using the V4 model tend to have lower carbon estimates per page view than V3. Estimates for your webpages may be up to two thirds lower than in V4.
Why are the estimates lower?
SWDM uses data transfer as the main proxy for estimating webpage energy use. The core calculation is the total energy used by the internet divided by the total data transfer on the internet. The updated sources used for V4 of the model saw that data transfer has increased two fold. However, total energy use has fallen.
Essentially the internet appears to be operating more efficiently than previously thought.
If the internet is more efficient do my webpage results matter less?
Not at all!
Efficiencies in the network will only go so far. The total data transfer on the internet is increasing hugely. Growth in AI and data collection continues at an increasing pace. Efficient, lightweight websites are more important than ever.
Your website’s footprint might represent a tiny fraction of the internet’s overall emissions. But a more efficient website has huge benefits outside of carbon reduction. Lower carbon sites tend to be quicker to load and have better structure. Humans like this, search engines like this, they can lead to higher conversion rates and it’s better for the planet.
API access and API endpoint
When Website Carbon launched 7 years ago it was a pioneering tool. As part of our “improve the internet” remit we offered access to the Website Carbon API endpoint to a handful of users. From today that is no longer the case.
The main tool isn’t affected in any way, but it’s important to be transparent when we make changes like this. Any people or organisations materially affected by the change have already been contacted.
The digital sustainability landscape has changed significantly since 2018. Building a similar tool to Website Carbon is accessible. For instance The Green Web Foundation has an open-source JavaScript library CO2.js. with extensive documentation and support.
The change to API endpoint access isn’t one we have made lightly. Changing the way it can be accessed allows us to put our time and energy into other areas.
Watch this space for more details about where our energy is being redirected.
Wrapping up
We’re pioneers in the digital sustainability space and have a duty to the community to continually refine our offerings as knowledge and technology evolves. We’re on a mission, and we make our tools and resources publicly available so others can learn and help mobilise this mission.
If you have questions relating to Website Carbon you can reach out to our eat@wholegraindigital.com.
If you want to dig deeper into your website’s carbon footprint speak to bailey@wholegraindigital.com about our Digital Sustainability Consulting.
If you want further reading or to take more action you can subscribe to our Curiously Green Newsletter, visit the Sustainable Wed Design site or download the Digital Declutter toolkit.
At Wholegrain we spend a lot of time thinking about the environmental impact of our websites. Our designers create engaging, accessible layouts and craft planet and user friendly experiences. Our developers are continuously working to improve our efficient code bases. They push the envelope on what a low data website can deliver. Our project and account managers are on a mission to ensure that our clients (and their clients) get what they need in a way that is good for people and planet. The whole site from the back end to the front end is carefully considered and iterated on.
All our sites are tested on multiple browsers. They have high levels of backwards compatibility with older versions of Chrome, Safari and Firefox. At an agency level that’s normally where our consideration of browsers stops.
Recently though, I’ve been questioning my choices of tech platforms and software.
Out of all the programmes I use on a daily basis, a browser is what I spend the most time on. I’d never really thought about what browser I use or why. I hadn’t engaged with my choice from a sustainability point of view. This is strange because most of my working and personal life is spent doing just that. Curiosity got the better of me (which shouldn’t be a surprise given my job title) and I started investigating the question.
Pulling on the thread marked Chrome without unravelling my Google sweater
Much of this article is going to focus on Chrome and its alternatives. It is difficult to discuss Chrome without talking about Google as well. Google dominates browser market share in the same way that it dominates other online services:
Many of these products and services are widely used because they are free and default on devices. They are also used because they are good at what they do.
Google is a tech company but makes the majority of its income from advertising. Their dominance across multiple areas of the internet grants Google a monopolistic reach and influence over it. This access allows them to hoover up vast amounts of user data and intelligence through Chrome and other products.
Myself and others see it as problematic.
Some of the others that share my opinion include the US Judiciary. Following an Antitrust ruling in August 2024, the US Department of Justice submitted a proposal stating that Google should be forced to sell off Chrome to reduce its monopolistic powers.
In this article I will try to back up that proposal from a sustainability point of view. The intent is not to persuade you to cut Google out of your personal or professional life. Rather it is to help you make an informed decision about the environmental costs of your online activities.
Browsing the main browsers
With those caveats in place I’ll dig in.
Statistically speaking you are probably reading this article on Chrome or Safari. Google and Apple have huge dominance in the browser market. Worldwide Chrome takes 66% of browser market share, with Safari coming in second at 17.6%. Microsoft’s Edge browser trails way behind in third taking just over 5% of the market.
That means three giant tech firms are responsible for 90% of the browsers used globally. Does it matter that three companies hold the keys to how we interact with and consume content online? On an individual basis possibly not. Collectively though, especially in the case of Chrome, this dominance poses a problem for users and the environment.
“If you’re not paying for the product, then you are the product”
There are some obvious reasons why Chrome dominates the market. For a start, Android phones dominate the mobile market and Chrome comes as standard on them. More importantly, it works well. From a usability point of view it’s pretty solid. It’s got great developer tools and most sites are optimised for Chrome because of its dominance. It’s a rare, free, product that we use on a daily basis that works pretty much flawlessly.
It’s not just working flawlessly for its users. Google is benefitting hugely too. As the saying goes – “if you’re not paying for the product, then you are the product”. Chrome plays a vital part in Google making billions in profits from advertising. Essentially the browser is doing two things. Allowing users to access the internet and allowing Google to gather data for advertisers to use.
So what is this free product, used by approximately 3.67 billion people, actually costing us? In my opinion it costs us two interconnected things. As individuals it costs us a measure of privacy and agency in our browsing and consumption habits.
In the context of digital sustainability, it extracts a cost that is paid by the planet.
The big data hoover
Much of what we do at Wholegrain aims to reduce the data transfer associated with browsing our clients web pages. We try to help others to do the same with tools like Website Carbon and through our writing.
In many ways Chrome is trying to do the opposite.
By some estimates, Google stores an additional 15 petabytes of data every day. If 15 petabyte doesn’t sound like much, understand that 1 petabyte is equivalent to:
500 billion pages of standard printed text
or 200 million 5mb photos
or 13.3 years worth of HD video content
They won’t run out of storage any time soon though. Google has an estimated 30 zettabytes (30 trillion gigabytes) of capacity in their (power, water and resource hungry) data centres.
The data they collect from Chrome takes the form of a “digital fingerprint”. This is user data that can identify and target the individual habits of a Chrome user. They use seemingly benign data points like IP addresses, screen resolution, device settings etc to build up a picture of your habits and interests. This, along with data from a wealth of other sources is used to help make their advertising solutions so effective.
In effect we and our data is the product that Google extracts from Chrome.
Why is this bad?
Using the internet is an essential part of daily life. Even an aspiring neo-luddite like myself can’t deny that. Nor can I ignore the positive benefits that digital solutions bring to us all. But browsing doesn’t have to mean vast amounts of data being collected. It doesn’t have to be stored and analysed. The additional, hidden energy and environmental costs of this data collection are not essential to our daily lives.
This data gathering by Chrome plays a part in the data centre growth that has exploded in recent years. These huge data centres need power, water, space, minerals and resources. A browser which helps create a digital doppelganger has impacts in the real world.
The 2024 UN Digital Economy report states, “low-carbon and digital technologies largely compete for the same critical minerals”. Additional and extractive data collection plays a part in this. At a time when we need to decarbonise our grid as quickly as possible, big data centres are increasing energy demands from companies like Google, Microsoft and others. Renewable energy growth is struggling to keep up and we can’t afford the competition for resources.
Less tangibly these digital fingerprints are helping the global economy maintain a level of consumption that our planet cannot sustain. Humanity consumes vastly more resources than the earth has the bio-capacity to regenerate. To combat the climate crisis, the developed world needs to consume less. Being exposed to fewer and less targeted adverts would likely help reduce consumption.
It would be healthier on our bank balances, our psyches and the earth’s eco-systems.
If Chrome isn’t so shiny, what are the alternatives?
If you would prefer a browsing experience without this hidden environmental cost, there are simple steps you can take. Making Chrome more privacy focussed is possible but is less effective than using an alternative privacy focussed browser. There are a number of options to do this including Brave and Vivaldi. Personally I’ve made the switch to Firefox as my main browser for a number of reasons.
Firstly it’s owned and maintained by a not for profit who are committed to building a fairer, safer internet. They want an internet “where our privacy is protected, AI is trustworthy and irresponsible tech companies are held accountable.” That sounds quite nice doesn’t it? Here’s their full Manifesto.
It’s a privacy first browser. It blocks trackers from the first time you install it by default. It also allows you to further enhance your online privacy if you wish. By contrast, Chrome tracks your browsing even in incognito windows.
Using Firefox means less data is collected and stored as I browse. This means less demand for data centres and less energy is required for my online actions.
Not only does using Firefox save energy use at a data centre level, there is evidence it does so at a device level too. Tests show that Firefox uses less electricity than Chrome, meaning lower browsing emissions.
Firefox is an open source project. This means that its source code can be scrutinised and improved by its users. A transparent and collaborative web is better and fairer for all its users.
Making the change
If you are persuaded by the arguments above, Mozilla has a handy guide for making the switch to Firefox. While I’ve been happy with the experience of using the new browser it isn’t perfect. There are some additional privacy tweaks you might want to make. More pertinently I have occasionally found that some website features, such as payment portals, haven’t worked when using Firefox. This can be temporarily frustrating, but firing up the page on Safari or Chrome fixes the issue.
This serves as a good reminder that you don’t have to jump to an alternative browser full time. You could keep using Chrome for work and switch to another browser, such as Firefox, for personal browsing. Any time spent browsing on something other than Chrome means less data collected and stored.
For the sake of the planet, we should all be striving for that.
Article update
If this article peaked your interest you can find out more on the topic in the interview I gave to Reset – Digital for Good. We discussed about the DOJ’s antitrust case against Google, browser choices, digital consumerism and much more.
One of the primary reasons that the people behind Wholegrain work here is a want to do better – that means build more sustainable websites, consider the needs of people more centrally to our decisions and play a leading role in moving forward our understanding of what sustainable web design really means.
I can imagine this to be true for anyone working in any sector where they consider and challenge how to do it more sustainably. It can be frustrating, constantly looking for the definitive end line that says ‘this is how we do it perfectly’, but we all know that we are not there yet and to be truthful, may never be there. Not that this should stop us trying.
At Wholegrain (and in all other businesses and communities we stand beside in this space) we are continuously reading, writing, listening and sharing the latest ideas and frameworks that can push us all collectively closer to that golden state of understanding. Learning from each other and communicating new ideas is what has built the understanding we have today and it often leads to the need to pivot or unlearn what was thought to be true but now is proven incorrect. Again, not that this should stop us trying.
“The digital sustainability community stands for transparency and collaboration. At no point should we or have we gate kept information or said measurement was 100% accurate. It’s about making the intangible visible so everyone can see and access it.”
Bailey Bryan, Wholegrain’s New Business Manager
This past week the overall approach to Digital Sustainability was challenged, sadly not through conversation.
The following is the thoughts of Andy, who manages our Curiously Green newsletter and spends his time in and around the wider thinking on Digital Sustainability with input from Bailey, our new business Manager and Dan, our Technical Team lead – who both speak internally and externally about what Digital Sustainability looks like on a tangible level, as people on the front line of actually designing and building sites to be more sustainable.
Andy: The latest lightning rod
The ever evolving nature of digital sustainability means that we’re constantly reading and consuming articles, reports and ideas on the topic. We keep a careful eye on developments in coding, file formats, data gathering, storage optimisation, changes to calculation models and philosophical ideas about digital usage Our website carbon calculator, Website Carbon often features in these articles in these topics, sometimes acting as a lightning rod for thoughts and findings about low carbon web design.
The effect of dark mode on device electricity usage and user behaviour
Correlation between performance metrics and data transfer and energy usage
The good bits:
The dark mode research is interesting and goes against some of the sustainable web design advice and methodologies. In their research a small sample size of participants turned up monitor brightness levels up when using dark modes, regardless of overhead lighting conditions.
This rebound effect is potentially a useful finding. If it can be replicated across a larger sample size it would certainly change some conventional wisdom and design methodologies. We would add that any dark modes implementation should be in line with accessibility guidelines and based on user preference rather than prescriptive.
As the researchers note, further research would be required using devices with OLED screens, which is something that is noted in the Web Sustainability Guidelines.
The frustrating bits:
The rest of the report has frustrated us at Wholegrain and others in the community. The sections on performance and data transfer feel to have taken an over simplified view on areas that the digital sustainability community treat as nuanced and complex.
The report states that “performance and energy efficiency aren’t always linked, so optimising for performance may not yield the desired energy results”. This is something that we would agree with. Indeed we wrote about how strong performance metrics don’t always correlate with low site emissions in November 2023.
Without knowing what sites were tested, it’s hard to comment further. What we can say is that we and other reputable agencies know that “Developers cannot therefore simply optimise for performance and hope that energy savings occur as a happy by-product”. Suggesting otherwise feels harmful to the industry and undermines trust and engagement at a time when digital emissions continue to rise.
This feeling of being unduly undermined continues when the researchers discuss data transfer. The researchers question whether a link can be made between data transfer and device energy use. The report raises issues where “data is used as a direct proxy for energy” going further to state that it presents a “completely fictitious narrative of how emissions are generated on the internet”, citing Website Carbon as one place this narrative is shared.
Them’s fightin’ words.
Our polite but firm response
It’s widely known and acknowledged within the sustainable web industry that data transfer is a flawed proxy for carbon emissions. I think Fershad Irani’s piece on this issue is the most eloquent and persuasive on the topic. Put simply, we know there are issues and that in certain cases it might cause some paradoxes. Where those paradoxes are proved we take note and adjust best practices.
The report discusses testing “top sites” but not what they were, how they are built and what platforms or frameworks they use. Picking holes in the sustainable web design practices without testing sites built using them doesn’t feel fair or representative. Indeed they tested the COP28 site which did an infamously bad job of implementing the “low carbon mode” mentioned in the report. The site (which was not built by a sustainable web specialist) was criticised heavily at the time and revisited when updates were put in place. Citing this website as a good example of best practice is incredibly frustrating.
In the conclusion of the BBC piece the researchers write –
“Web sustainability guidelines therefore need to be careful about the interventions they recommend and caution developers to think critically about the suitability of those interventions for their individual use cases.”
Next Steps from everyone at Wholegrain collectively
We’ll end this response in the same way as the report does, with some suggested next steps. The researchers express a desire to collaborate with the industry to develop “tools that allow them to accurately estimate energy”. A good place to start might be to collaborate with an organisation like GreenSpector who share similar aims.
“We cannot positively move the needle on tackling digital carbon emissions if the aim is to tear down its very foundations. Digital Sustainability has never been about ‘I’m right, you’re wrong’ but sharing information to mitigate the climate crisis happening at our finger tips.”
Bailey Bryan
They could also ask to collaborate with any of the organisations and individuals mentioned above. We’re an open bunch who desperately want to do the best thing for people and planet in every way. We’re open about what we do and why we do it. We showcase our sites and think they hold up to scrutiny. We’re open to making changes if our methods turn out to be flawed. We want to iterate and improve where we can. We want accurate measures just as much as anyone else. Maybe even more so.
Our mission to “accelerate the shift to an Internet that’s good for people and planet” needs collaborators so we can continue to do the work we do for the companies we work with – one being BBC Good Food, just for reference.
Most countries’ government websites already prioritise accessibility, however the European Union is ensuring its usability doesn’t just stop at government websites, many product and service websites will be affected too.
As of 28th June 2025, the European Accessibility Act 2025 comes into effect requiring any business that is trading, or plans to trade, in the EU needs to provide accessible digital services. This also affects UK businesses that provide services to EU consumers and to public or private bodies that are in the scope.
Why does web accessibility matter?
Our founder, Tom Greenwood, described this clearly when writing about the public sector accessibility regulations for the UK in 2019. Succinctly, it comes down to the fact “a huge part of our world is now online, if we don’t take accessibility seriously then people with disabilities will be excluded, creating a two-tiered society.”
What do the European Accessibility Act 2025 regulations require?
The Design for All (DfA) approach is a design philosophy for products, services and systems to have maximum usability by as many people as possible without the need for adaptation. This philosophy was responsible for the development of the European Standard on Design for All, published in 2019. In the same year the European Accessibility Act (EAA) was officially published by the European Union.
The regulations are not new as such, but the deadline for implementing them, June 28 2025 is now fast approaching.
So what are the key requirements for websites?
Depending on which EU country is involved, websites must at least meet WCAG 2.1 compliance at level AA. Ensuring that websites are WCAG 2.2 compliant at level AA is a more prudent, robust and future proof approach.
Non-text content such as images, videos and products must have associated alternative text providing clear, simple descriptions for screen reading technology .
All parts of the website should be usable with just keyboard navigation.
Audio and video, must be accompanied by captions or transcriptions and offer alternative formats. Auto play of videos should be avoided.
Adaptable website design so it can be adjusted to suit different needs, such as changing text size or colours for better readability.
Accessibility is not a feature, it is a universal human right
Universal design isn’t new or novel. The result of designing for additional needs, benefits everyone, sometimes in ways we couldn’t have predicted.
The dropped curb? Originally created to assist wheelchair users, also benefits people pushing a pram, shopping trolley, or suitcase.
The electric toothbrush? Designed for those who lacked the movement or dexterity to brush thoroughly, and now many people own one as it can clean your teeth more effectively.
The world wide web? Yup! Even in its inception, the inventor of the world wide web, Tim Burner’s Lee created it with universal design in mind. He stated: “The power of the Web is in its universality. Access by everyone regardless of disability is an essential aspect”.
The above are three examples of things we all benefit from frequently, if not daily.
When the web was launched, it prioritised universal accessibility. However, when you release things into the public domain, you lose control of how people adapt it. Legislation and laws are often required to maintain our universal human rights, especially as we continually iterate and improve our digital platforms.
Happily there are many people and organisations who took it upon themselves to make sure this knowledge is shared and accessible to drive change sooner. Here are a handful of those improving accessibility through education, community alliances and free tools:
WCAG 1.0 was published in 1999 and 26 years on WCAG 3 is fast approaching;
You can evaluate WCAG standards for webpages with WAVE.
Reminder! For the EAA 2025, as a minimum, websites must meet WCAG 2.1 compliance at level AA.
The A11y Project is a community-driven effort to make digital accessibility easier as well as providing a list of resources.
Web Sustainability Guidelines which was created by the W3C Sustainable Web Design community group. Designing for not only audience needs, but data & WiFi bandwidth means that no one is hindered from information or interactions online based on data inequality.
Accessibility Insights is a free browser extension to test accessibility of webpages and web applications.
Wholegrain supports all moves that increase inclusion online
We’re encouraged that accessibility protections are written into law and continually iterated. However for us, accessibility online has always been and continues to be non-negotiable, meaning anything we create is done through the lens of universally accessible digital design.
We’ll keep doing what we’re already doing, putting the human behind the screen, first.
When we design with accessibility in mind, we’re creating experiences that are not only compliant but also intuitive and enjoyable for everyone.
This is exactly why we prioritise user testing because without representation, we can never truly understand how to create a fully inclusive digital experience.
From a UX standpoint, accessibility is intertwined with usability. When we design with accessibility in mind, we’re creating experiences that are not only compliant but also intuitive and enjoyable for everyone. Accessibility means removing barriers for people with disabilities, but it also enhances the experience for all.
For example, clear navigation and logical content hierarchy improve usability for those using screen readers, while also benefiting people in noisy environments or those unfamiliar with a website. Captioning videos helps people with hearing impairments but also supports those watching content in quiet spaces. Keyboard navigation is essential for people with mobility challenges and it also improves efficiency for those who prefer shortcuts.
Designing for accessibility encourages empathy, helping us focus on the diverse ways people interact with the web. It ensures that we’re building websites that are not just functional but delightful and impactful, reinforcing trust and inclusivity. For Wholegrain, accessibility isn’t a box to tick, it’s an integral part of creating human-centered, sustainable digital experiences that serve everyone.
It’s important to restate our mission to frame our position on accessibility:
“Our mission is to create the best websites in the world, use our business as a force for good, and help to accelerate the shift to an Internet that’s good for people and planet.”
Sustainable web design is accessible design.
In a world that is increasingly prioritising algorithms and non-human users, we stand strong in putting the people using a website front and centre. Through collaboration, we can uncover usability we’d never discover on our own, that discovery may even benefit you one day!
The team of volunteers have been working to embed sustainable practices into the WordPress community and its processes since 2023. In that time, they’ve worked openly and honestly to ensure WordPress’s social, economic, and environmental longevity.
We should take time to acknowledge the hard work and dedication of the now defunct team. Nora Ferreirós, Csaba Varszegi, Nahuai Badiola and Thijs Buijs worked to highlight the opportunities to improve sustainability at WordPress to a sometimes disengaged leadership. They are on the right side of history and we thank them.
Wholegrain’s stance
This decision feels regressive and extremely jarring in today’s world, where devastating wild fires ravaged California, home of the WordPress headquarters. Climate change and events should focus us all on making the world a more sustainable place.
In this case, reducing the environmental impact of the core code behind the circa 500 million websites (roughly 43% of the internet) that use WordPress would set an example for the rest of the internet to follow. Sadly, this will now not be the case – which is not good enough.
What does not change with this news, is the skills and vision of the community that has fuelled WordPress as an open source platform. The response to this decision has confirmed that this community cares about sustainability and at Wholegrain, we pride ourselves on pushing the envelope when it comes to sustainably designed and built WordPress websites. This will not change either.
The proof is in the performance of our sites, the experience of our clients and the satisfaction of their users. Excellent performance metrics should absolutely be a goal to aim for (as per the Slack conversations that have surfaced), but to focus only on those metrics is to ignore the wider picture. As an ethical, B Corp certified agency, it’s the wider picture that Wholegrain focuses on every day.
We hold our agency to a higher standard than the platform we work with. Our sites demonstrate that 43% of the internet can be more sustainable as standard. If the WordPress leadership can’t see the importance of that, then we, as a community, will continue to demonstrate how wrong they are.
Our mission continues
Create the best websites in the world. Use our business as a force for good. Help to accelerate the shift to an Internet that’s good for people and planet.
Our carbon calculator, Website Carbon, is the original online carbon estimator with its API being used in projects across the web, including a carbon footprint tool that the WordPress Sustainability team have been working to develop.
All of the sites we build use WordPress’s core code and they all have high performance metrics and low carbon scores. They are built with care and attention for all users by an engaged and dedicated team who focus on their work being accessible, both on a technical and user level.
We will continue to take the best elements of WordPress, what the open source community around it offers, and use our talent and experience to elevate our sites to a higher level.
We will continue to show how user focussed, beautiful and sustainable a WordPress website can be.
On a personal note to those we work with
Whilst this is a really disheartening and careless move by one person within the WordPress leadership, this does not affect your website and you do not have to do anything. Nor does it affect our ability to deliver low carbon solutions for the websites that we design and build.
A high quality, low-carbon approach has always been one of our primary focuses when building sites; combining our own knowledge and expertise with WordPress as a rock solid foundation. This was the case for many years before the formation of the WordPress sustainability team [in 2023] and remains our focus into the future.
Tommy Ferry. Technical Delivery Lead at Wholegrain
One person is not WordPress. We are actively choosing to stay within a community of developers and technical specialists that have made WordPress the successful platform that it is – providing open source contributions that enable us to provide the best sustainable websites to you.
If you have any worries or concerns around this news and how it might impact your site, you can reach out to Georgie and myself, our Senior Leadership Team.
In February 2021, I published the book Sustainable Web Design with the publisher A Book Apart. At that time, awareness of how environmental issues relate to the web design and wider digital sector was minimal and I hoped that a practical, easy to read book would help educate, inspire and encourage positive action. I also hoped that it would help put sustainability on the agenda alongside ethical factors in the digital space, such as privacy and accessibility as part of a more holistic conversation.
I’ve been pleased by the reaction to the book and the impact it seems to have had over the past three and a half years, working as one part of a wider tapestry of initiatives that have rapidly accelerated interest in web sustainability not just in the UK but internationally.
I have to give a big chunk of the credit for the success of the book to all of my colleagues and friends who made it possible by contributing knowledge and support, but I also must give much credit to the team at A Book Apart. Their fantastic house style that combines real life examples and stories with practical guidance, delivered in a format that is both concise and fun, not to mention having lots of pictures to bring it to life, is a big part of the appeal of every book they publish.
I received a huge amount of support from their team during the writing and editing process too. Yes, the editing process was painfully rigorous, but it made the book far more compelling and robust, as well as helping me to become a better writer. The fantastic print quality of the original paperback also made it a product that people treasured and passed on, and the publisher’s cult following definitely helped it to find a critical mass of readers who could then become advocates for sustainable practices within the digital sector.
The end of an era
After such a positive start, it was with great sadness that I received an email earlier this year from the team at A Book Apart informing me that they are ceasing publishing operations, and that I would need to republish the book if I wanted it to remain available for sale. From what I understood behind the scenes, the company had been having some financial challenges for a little while and over the past year they had therefore been making a series of tough decisions in an attempt to steady the ship. While I wasn’t over the moon about all of the changes, I felt that they were probably the necessary decisions to take in the context of the bigger picture.
However, many authors weren’t happy with these changes and wrote collectively to the publisher with their demands. While I understood the concerns being raised, I personally didn’t feel comfortable with the specifics of the demands or more importantly, the tone of the approach, so I quietly opted out of being involved. A majority of authors did sign the letter though, and as A Book Apart were unable to meet the demands, they instead decided to cease operations and return all book rights to their respective authors. Perhaps it just accelerated the inevitable, but to me it felt like the final nail in the coffin of a good company going through hard times.
Re-releasing the book
Anyway, the upshot of all this is that along with all other A Book Apart books, Sustainable Web Design would soon cease to be available unless I either found a new publisher or re-released it as a self published title. The A Book Apart team were extremely helpful in trying to make the process as easy as possible and after some deliberation, I decided that the path of least resistance would be to self publish it as a print on demand title using IngramSpark. In theory this would require relatively little work to set up and would then make the book available internationally via most booksellers, not just on Amazon.
It turned out that the process of reformatting the book and getting it distributed via IngramSpark was a huge amount of work and took far longer than anticipated. This was mainly due to the idiosyncrasies of the IngramSpark system and the slow response times of their support, but it’s done now and the book is once again available to buy.
So what’s the difference?
The re-released book is now available as both paperback and eBook, with a few key differences from the original as follows:
New cover design
The first difference is the cover design, which had to be changed to remove the A Book Apart branding. I designed an updated cover that echoes the original but has a bit more character, incorporating a graphic from my favourite classic Wholegrain Digital t-shirt of a laptop plugged into a cable running through a series of wind turbines as shown in the photo above.
A little additional content
After much deliberation, I decided not to rewrite the book as a true second edition because it would have been a significant project in it’s own right that I wasn’t in a position to undertake. However, I did want to acknowledge how much has changed in the world of sustainable web design since the book was first published just three and a half years ago. The updated book therefore now includes an Afterword with my reflections on how the field has changed and giving some pointers as to what the reader may want to explore beyond the content of the book.
Lower pricing
The main criticism of the book until now has been its high price. This was due to it being a low volume book from an independent publisher, but I had always wished that the pricing was more affordable. When republishing the book, I therefore reduced the price significantly. The price of the paperback has been reduced from approximately £27 to £18 in the UK and equivalent internationally, and I have also reduced the eBook price to £9.60. Furthermore, the global distribution system of Ingram’s print on demand service will also reduce shipping costs for people in many parts of the world.
Different print quality
I always loved the print quality of the original book and it was something of a hallmark of A Book Part. One of the changes that A Book Apart had made before ceasing operations was to move to IngramSpark’s print on demand service and I have to admit that I was disappointed with the quality.
When republishing it myself, I therefore upgraded to Ingram’s premium print quality option. It’s still not as good as the original paperback quality, but it is at least decent. The downside is that the high print cost combined with the reduced pricing of the book basically now wipes out any royalties that I would have got, so all the money from each copy goes to Ingram and to the bookseller such as Amazon (eek!). However, I’m lucky that I can afford to forgo royalties and I think that the lower price and higher quality print will help to maximize the reach and impact of the book.
What about the environmental impact?
The original book was printed in Germany by a company that clearly cared about it’s environmental impact and used 100% FSC Certified paper. The downside was that the books were then shipped to the publishers warehouse in the USA for distribution and posted from there to customers around the world.
Since the printing was moved over to the IngramSpark system, the environmental footprint has clearly changed. The clear upsides are that only the exact number of books needed are printed and that they are printed as close to the customer as possible, reducing the impact of shipping. IngramSpark also state that they use “paper that is high quality from sound suppliers primarily from SFI, FSC or PEFC certified mills for the books we manufacture”. It’s better than nothing though their overall environmental policy is pretty meaningless and I can’t help but wonder exactly what they mean by ‘primarily’. How much of their paper is not SFI, FSC or PEFC Certified?
As always, the most environmentally friendly way to buy my Sustainable Web Design book is to buy the eBook, but of course there are many good reasons to have a hard copy and the paperback is there for those who want it.
Where can you buy it?
You can buy the updated book from your preferred bookseller using the following ISBN numbers.
Paperback: ISBN 9781068759406
eBook: ISBN 9781068759413
Due to the efficiency of the distribution systems it has showed up on Amazon first (paperback and eBook) but it is also available from others such as Waterstones and my favourite, Hive.co.uk. You could also keep your eye out for second hand copies.
And it’s still free for non-profits
If you work for a non-profit in the UK, we’re still offering free copies of the original book to help your team learn about and integrate sustainable web design practices in your organisation. Simply fill in the form on our website to request your copy.
Last week I wrote about how the estimated total carbon emissions of the internet have fallen according to the latest Sustainable Web Design Model. This week I’d like to shift the focus from emissions to the mineral resources required to keep the internet running. It’s important not to focus only on carbon emissions. Readers may note that the irony of this being written by the creators of Website Carbon is not lost on the author.
Today I’d like to discuss the concept of carrying capacity and its relationship with our digital lives.
Decarbonisation doesn’t solve everything
The inspiration for this article comes from this report – The environmental sustainability of digital content consumption. It’s a chunky investigation into, well, exactly what its title suggests. According to the report 60% of the world’s population has internet access. Of that 60% the average user spends 40% of their waking life online. If we are spending around 7 hours a day online (2 hours of which are on social media), this is going to have an environmental impact. It is also worth noting that global data traffic levels have risen 440% since 2019. This trend looks set to increase as AI continues to be pushed by all major players online.
The impact of our online activities is most often discussed in terms of carbon output. It’s the simplest way of measuring the impact of an hour’s streaming or loading a webpage. The report looks at the impact of our digital habits on a per capita carrying capacity basis.
Carrying capacity is how many full shopping bags you can carry from the car to the front door:
The carrying capacity of anenvironment is the maximum population size of a biologicalspecies that can be sustained by that specific environment, given the food,habitat,water, and otherresources available.
In carbon terms our current online habits account for 40% of our per capita carbon budget consistent with limiting global warming to 1.5 °C. Great news! If we decarbonise the grid, we solve the issue.
As always, it’s not as simple as all that. Focussing on the carbon outputs ignores the pressure on the mineral resources required to keep us online.
Resources and carrying capacity
While our current browsing habits account for less than half of our per capita carbon allowance, that’s not the case for metal and mineral resources. The resources required for the hosting infrastructure, delivery network and devices account for a big chunk of our personal allowance.
Internet usage currently accounts for around 55% of the per capita carrying capacity for mineral and metal resources use. Put simply, rapid decarbonisation of the net can’t mitigate the environmental impacts associated with the minerals required for electronic devices.
The extraction and processing of raw materials have huge impacts. For this article I’ll put the challenges facing the mining and processing industries to one side. It’s a thorny issue but things can be done to improve standards in the industry. One thing that is worth noting is that the impacts associated are regional. Land use, ecotoxicity and working standard issues often occur in locations far from where digital content consumption is taking place.
The % of the connected population will only continue to grow. Increased living standards (and associated improved levels of online access) should be something we strive for. But we can’t ignore the fact that the increase in internet users will also require more devices. You can’t have more devices without more mineral resources. Circular models and recycling won’t solve this issue.
Ideas and solutions
There are technical and practical solutions available to us here. Ultimately though this report leaves us with a more philosophical question around how and why consume digital content.
From a practical point of view, lengthening the lifespan of devices is the first step to take. Using devices and infrastructure for longer has to be key. Choosing refurbished or second hand tech, supporting brands that promote repairability and extending device lifetimes are all practical steps anyone can take. A brand such as Fairphone is a shining example of this ethos. Second hand platforms are widely available but I would advocate for searching for a more local solution if appropriate.
Designing sites and applications that are widely supported and have backwards compatibility for older devices and browsers could help reduce devices obsolescence. Performant and lightweight digital products will work better on older devices too.
As an industry there has to be more scrutiny over the resources used in the AI gold rush. Processing chips are often used once for training large language models and then discarded. Individuals and organisations should carefully question whether the use and support of AI products is worth the tacit approval of the platform’s current working practices.
More than this I think the figures revealed in the report should prompt a rethink of how and why we use digital services. We are back into the digital degrowth territory that we’ve touched on previously.
For organisations and website owners, we should be working towards more optimised user journeys. Less pages and more efficiency equates to less time online and data stored.
We can perform content audits both on sites and social media to identify low performing posts and content. Deleting this information and being more mindful around how much and how often we create and post aids degrowth too.
As individuals, I think it comes down to just how much time we spend online! As a starting point I would ask:
Ultimately all the insights into material usage are more proof that we have a long road to walk when it comes to digital sustainability.
I’d love to hear your thoughts on this article – curiouslygreen@wholegraindigital.com
How can we reduce our digital carbon and resource footprints even as more connected users come online?
How do you feel about your digital consumption habits taking up so much of your mineral resource “quota”?
Andy
Article citation:
Istrate, R., Tulus, V., Grass, R.N. et al. The environmental sustainability of digital content consumption. Nat Commun15, 3724 (2024). https://doi.org/10.1038/s41467-024-47621-w
There’s no secret sauce I’m afraid. It’s all down to clear, well defined acceptance criteria .
I know it might sound a little dry, and something that you’d expect to hear from a Project Manager, but clear acceptance criteria is vital within any task or project. The definition of set criteria can be easily be something that’s overlooked but, done well, can be the key to ensuring that your project is delivered on budget and on time and, most importantly, to the specification you require.
As we begin moving towards our new project management tool, Jira, it is pertinent that we take this opportunity to highlight some benefits of the tool as well as best practice that we will be following to ensure that this transition will have a positive effect on project efficiency and client satisfaction.
One of the most important benefits is that this tool encourages a clear and concise acceptance criteria for all tasks, stories or bugs raised in a project backlog. Acceptance criteria can be defined as the conditions a software product must meet to be accepted by a user, a customer, or other styles. They are unique for each task and should be added in the description of a task as it’s created in the backlog, in order to define the feature behaviour from the end-user’s perspective.
Certainly, as a PM, acceptance criteria is essential to ensure we are delivering in line with the client’s needs completely – and therefore this is an opportunity to explain why we should be using good acceptance criteria for all projects, what this looks like, and that it is essential our client’s are onboard with this too.
Firstly, what are the benefits?
It removes ambiguity and provides a clear framework to deliver against for the project team.
It reduces the risk of misunderstanding the task – which can ensure we are investing time efficiently.
By setting acceptance criteria for each task it ensures scope creep is easier to manage.
Greater client satisfaction as tasks are delivered in line with their full requirements.
Ultimately – having clarity on tasks saves time, budget, and frustration for both parties!
So, what is a good acceptance criteria and what does this look like?
Acceptance criteria should be testable. Tests should reveal straightforward yes/no or pass/fail results.
Criteria should be clear and concise.
Everyone must understand your acceptance criteria.
Acceptance criteria should provide user perspective. Acceptance criteria is a means of looking at the problem at hand from a customer’s standpoint. It should be written in the context of a real user’s experience.
A good way to meet the above criteria is to follow the template below.
“As a type of user, I want some goal, so that some reason”
So maybe if you’re a membership organisation you would raise an acceptance criteria like,
“As a registered member of the website , I want to easily search for events, so that I can see those that are geographically close to me and are free to members.”
or…
“As an admin of the website, I want to easily tag events, so that I can show our global membership those events near to them, and those available to members and non-members. ”
Clear and concise acceptance criteria will ensure more efficient outputs across our collaborative projects, and therefore we really encourage all of our client’s to raise tasks to include a clear vision for their intended goal.