At Kooba, we often hear people equate accessibility with limitations; it can sound like a restriction on design. Clients are misled into thinking universal design is a design setback, that they’ll need to use specific colours, make something bigger, add another label.

It creates a false opposition between creativity and freedom on one side, and accessibility and rules on the other.

But the world of design is already built on structured systems that designers naturally work within, from grid layouts and typographic hierarchies to strict brand guidelines and technical viewport constraints. These kinds of creative boundaries are familiar ground. Far from limiting design, accessibility simply introduces a new set of thoughtful constraints that push us toward richer, more interesting places.

Not just a checklist

There’s always room for creativity, which is essentially just problem-solving. And accessibility gives designers worthwhile problems to solve. With AccessPoint, we’re trying to move the question from“What do we need to do?” towards“How can we make this interesting?”

Going beyond colour

WCAG’s guidance on the use of colour states that colour can't be the only visual means used to communicate information. An error message, for example, can't rely purely on something turning red. W3C recommends using additional cues such as text or shape to convey the same meaning.

At first, that sounds like a pain point, one more thing to worry about when designing a website. But it actually encourages us to play with the other attributes on a page: iconography, shape, copy, typography or movement.

Instead of removing a design tool, accessibility encourages us to find another one.

Adobe’s Spectrum 2 is a good example. Adobe rebuilt parts of its colour approach around accessible palettes, contrast and clearer visual hierarchy, while also making the system more expressive and adaptable.

Bringing character to keyboard navigation

Accessibility also creates interactions that UI designers get to make their own. Consider keyboard accessibility. People who navigate without a mouse need to be able to use interactive functionality from a keyboard and clearly see where their focus currently sits.

WCAG requires that keyboard focus is visible, but it does not dictate one universal way that focus has to look.WCAG’s Focus Visible guidance explicitly notes that focus indicators can take different forms.

And so, another micro-experience emerges.

We get to think about the border, its pattern, its colour and the details of how it appears and changes as someone moves through a page. A functional requirement suddenly becomes another small expression of the brand.

GOV.UK has turned this into a distinctive part of its interface. When a user moves through the site using a keyboard, focused links use a yellow background with a thick black underline, while other elements use similarly strong focus treatments. The design is built to remain visible across different backgrounds, but it also gives keyboard navigation its own consistent visual character.

The same thinking can apply to skip links, navigation controls or ways of moving between sections. They exist for a practical reason, but they don't have to feel separate from the rest of the experience.

Designing around reduced motion

If a digital experience includes movement, designers have to consider people who may need that movement reduced or removed. WCAG includes guidance around allowing users to disable non-essential motion triggered by interaction.

The obvious answer might be a generic accessibility switch added at the last minute to the corner of a finished website. Instead, we can see the switch as a new asset.

For AccessPoint, we didn't just think about how somebody turns motion off. We thought about what that control could look like, how it could behave and how the interaction itself could become part of the experience.

Reducing motion also doesn’t necessarily mean removing every bit of personality. Apple’s accessibility guidance recommends considering animations individually, because removing useful motion entirely can sometimes make an experience harder to understand.

The accessibility requirement creates another feature, and another opportunity to decide what that should feel like.

Even the language on a button or switch takes us to unique, contextual places to insert more personality. Especially with so many generic or repeated CTAs like "Submit" or "Click here", this allows for action-specific microcopy that directly reflects the interaction.

Building accessibility in

That's one of the central ideas behind AccessPoint: accessibility is considered at every stage of building the website, rather than checked once everything else is finished.

Because that's when accessibility really can feel restrictive. A finished colour palette suddenly fails contrast requirements or an interaction needs to be rebuilt. Motion has to be stripped back rather than thoughtfully adapted.

Build those requirements in from the start to make them part of the creative brief.

Accessibility doesn’t only change the things we were already going to design. Sometimes, it gives us something new to design altogether. Instead of asking what needs to be taken away, you can ask what they give you an opportunity to add.