Values  ·  Set October 2026

Four things every project has to be.

Accessible, clear, beautiful and found. They are the bar every Apex Mono project is judged against: before design starts, before the client sees it, before launch, and a month after. They are not a style. They are what the thing has to do for the person using it.

01

Accessible

Everyone can use it.

What we mean

Anyone who arrives can use the thing, whatever device, connection or ability they bring. Someone on a five-year-old phone on a weak signal. Someone who cannot see the screen and hears it instead. Someone who cannot hold a mouse and moves through it with a keyboard. Someone who gets dizzy when things move.

Accessible means the product was built for all of them from the first screen, not patched for them at the end.

How we do it

We hold every build to WCAG 2.2 AA and write that into the proposal, so it is a promise rather than a hope. Before a client sees a preview, we go through every page with a keyboard alone and with a screen reader. We turn reduced motion on and check that every animation has a gentler version. We measure how fast the first screen appears on a phone, because a slow page is a page some people cannot use.

Automated checkers run too, but they catch under half of what matters, so the manual pass is the real one. On a site that serves the public, we also pay someone who uses assistive technology every day to use it and tell us what broke.

Why it matters

For the person using it, this is the difference between being included and being turned away by a door that looks open. For a practice or a business, it is the difference between a patient who books and one who gives up, and an inaccessible website is a legal risk no practice needs.

A note from Gina

I want to be honest about where this stands. I have built accessibly for years in the ways a checklist can catch: contrast, labels, focus, structure. I have not yet sat beside someone who uses a screen reader and watched them use something I made. That is the next thing I am doing, and I will write up what I learn, including what I got wrong. A value you cannot test is a slogan. This one I intend to test.

02

Clear

Nothing to figure out.

What we mean

A person lands and knows within seconds what this is and what to do next. Every screen has one job and one main action. Words say what will happen. When something goes wrong, the message says what went wrong and how to fix it.

Clear is not minimal for its own sake. It is the absence of anything that makes a person stop and think about the interface instead of their task.

How we do it

We write the copy before the layout, from the user’s side of the screen, in the words they would use. We test the first screen on someone outside the project: if they hesitate before saying what it is, it is not done. We read every button and link on its own, out of context, and change any that do not say what they do.

Structure follows the same rule. One heading names the thing. The first paragraph answers the question the visitor came with.

Why it matters

People do not read interfaces. They look for the way through. Every second someone spends working out what to do is a second they are not booking, buying or reading, and most people will not spend it. Clear is what makes the other three values count.

03

Beautiful

Made with care.

What we mean

Beautiful means the thing looks like someone cared, because someone did. Every space, every size, every colour and every moment of motion is a choice that can be defended. There is nothing on the page without a job.

Motion is feedback, never decoration. It tells you something happened or where something went, and when it has nothing to say, it is not there.

How we do it

One accent colour. A type scale we hold to. Air where the eye needs to rest. We look at every page at phone and desktop widths before anyone else does, and nothing placeholder or clipped survives that pass. Each animation is named with what it tells the user; if we cannot name it, it goes. Screenshots of the work are never cropped. We capture them at the right size instead.

Why it matters

People decide in a moment whether something deserves their trust, and they decide with their eyes. For a founder or a practice, the site is the first thing most people will ever see of them. Care is visible. So is its absence.

04

Found

Shows up when someone asks.

What we mean

The people looking for what you do can find you, whether they type into Google or ask an AI. More people now ask an assistant first and never open a results page, so being the source an answer quotes matters as much as ranking.

Found means the site states plainly what it is, who it is for and where, in words a person or a machine can lift whole.

How we do it

Every page gets its own title and description, written in the visitor’s words. One heading names the thing. The first paragraph answers the question. Structured data tells search engines and assistants what kind of thing the page is, and it validates. Images carry descriptions. Robots and sitemap files let search and AI crawlers in. Speed counts here too.

A month after launch, we ask an assistant the question a customer would ask and note whether the site is the answer. We do not promise rankings. We promise the groundwork is there and checked, and that we will tell you what we find.

Why it matters

A site no one finds does not do its job, however good it is. For a practice, this is a patient in a new town typing a symptom. For a founder, it is the first ten people who will ever hear of them.

Where this is going

Every one of these comes back to the same person: the one on the other side of the screen, who did not choose the device, the connection, the ability or the deadline they arrived with. Human-centred design is the plain name for building for that person first. It is where the studio is heading, and these four words are how we hold ourselves to it.

If a project cannot be built to this bar, we will say so, and point you to someone who can.

Start a project