If you have spent any time in web design or development, you have met the shadowy, whipping demon of the digital world: poor colour contrast. Even as a visitor, text that is hard to read is a sometimes subtle, sometimes bloody obvious barrier to understanding.
You find light grey text on a white background. You squint. You shuffle closer. You give up and leave.
To help non-technical people understand this I built a dead-simple tool: Hue Shall Not Pass.
Aside from being a spectacular pun and a dad joke of the highest order, this micro-tool points at a bigger shift in how software gets made. Here is why colour contrast is the web's gatekeeper, how the app came together in minutes with AI agents, and why your business should think about replacing paid micro-tools with in-house ones.
The "you shall not pass" rule of web design
In The Lord of the Rings, Gandalf slams his staff down on the bridge of Khazad-dûm and yells, "You shall not pass!" at the Balrog.
In the digital world, low-contrast text does the same thing to your users.
[ bad contrast ] -> "you shall not pass!" (users bounce)
[ good contrast ] -> "welcome, friend." (users convert)
Whether someone is visually impaired, colour-blind, reading a phone in direct sunlight, or just tired at four in the afternoon, poor contrast shuts the door on their experience. The Web Content Accessibility Guidelines require body text to reach a contrast ratio of at least 4.5:1 against its background.
Hue Shall Not Pass was built to be the gatekeeper. Put in your colours; if they fail the standard, the tool stands firm. If they pass, you get the green light.
The era of agentic development
A couple of years ago, building, styling, testing and deploying a utility like this would have taken a developer a weekend of fiddling with component state, luminance formulas and custom CSS.
For Hue Shall Not Pass, the heavy lifting took minutes, using agentic development. Choosing the name and buying the domain took longer than the tool did.
Rather than writing code line by line, I worked alongside an autonomous AI agent that:
- understood the WCAG contrast formula
- generated a clean, accessible interface
- tested the edge cases, like invalid hex codes
- packaged the code to deploy instantly
- scored 100 in every Lighthouse category, including, of course, accessibility
In 2026, making software is less about manual syntax and more about curation and intent. You provide the vision, the brand and the logic; the agent handles the execution. Most of it, anyway, and it gets better by the month.
Stop paying for micro-SaaS
Which brings me to the takeaway for your business.
How many small, specific tools does your team pay a monthly subscription for? A PDF utility, a palette generator, a markdown formatter, an internal calculator. Each one costs a little every month; together they quietly bleed the bottom line. I woodwork as a hobby, and I built myself a cut-list optimiser to plan how to use sheets of plywood. It took half an hour and has already paid for itself, against both the software it replaced and the plywood.
Because agentic AI has made utility apps fast and cheap to build, these tools can now be built in-house. If your team relies on a generic public tool that charges a monthly fee, consider a bespoke version: customised exactly to your workflow, hosted for pennies, and owned outright.
Try it
Whether you want your next landing page to be WCAG-compliant or you just want to see what a modern AI-built micro-app looks like, head to hueshallnotpass.com and test your colour combinations.
Keep your contrast high, keep your users happy, and remember: don't let bad design pass.