Mission

BaseLayer Digital exists because too many digital systems still remove independence the moment a person reaches the screen.

This is about lived use, not paper comfort

Digital systems now sit between people and ordinary tasks: getting food, checking in for an appointment, paying for something, finding the right desk, reading an account page, or using a public service. When those systems are rigid, the person loses access at the exact point where the service is meant to become easier.

BaseLayer Digital was formed to address that directly by building digital systems that can adapt in front of the user instead of forcing the user to adapt to the system.

What we are arguing against

Self-service screens that replace a member of staff but not the accommodation that staff provided
Websites that technically pass but still force everyone through one visual model
Interfaces that cannot adjust when a person is fatigued, overwhelmed, or simply unable to read the default presentation
Digital handovers that remove human help without providing another workable route

Real-world failure points

The problem shows up in ordinary places people should be able to use without asking for help.

The deli ordering screen

A supermarket can move from a person behind a counter to a self-service display and call it progress. If that screen cannot adapt for low vision, reading difficulty, glare, or fatigue, the customer has not gained convenience. They have lost the independence they had before.

The hospital sign-in terminal

If a patient used to arrive, speak to a person, and make their way through the building independently, but now needs another person to operate the sign-in system and help them find the department, the digital change has made the service worse.

The public self-service handover

The same pattern appears in kiosks, account portals, ticket machines, and check-in points. The issue is not that they are digital. The issue is that they are fixed and built around the assumption that the user will adapt instead.

The legal and standards baseline

The current framework matters, but it does not remove the need for practical accommodation in live use.

Equality Act 2010

In the UK, service providers still have a duty to make reasonable adjustments. That matters because digital systems are now part of the service, not separate from it.

Public Sector Accessibility Regulations 2018

Public bodies have named accessibility duties for websites and mobile applications. That sets a baseline for public digital services, especially where a person has no realistic alternative route.

WCAG 2.2

WCAG remains the technical benchmark most teams work to. It is useful and necessary, but it is still not the same thing as building a system that can respond to the person in front of it.

The short version

The legal floor matters. The problem is that too many teams stop at the floor and call it done.

BaseLayer Digital is built around the next step: keep the baseline, then add the controls, fallback routes, and adaptive behaviour that make systems usable in practice.

See how the engine works See the support page

What works in reality

A workable system has to combine structure, runtime control, and a route back to human support when needed.

Layer 1

Solid baseline build

Semantic HTML, keyboard support, sensible contrast, readable defaults, and clean structure still matter.

Layer 2

Runtime adaptation

Users need live control over text, contrast, spacing, motion, comfort, and visual presentation.

Layer 3

Service continuity

If the digital route still fails, the person needs a visible and workable path to human help without starting from zero.

Layer 4

Longer-term support tools

That is where apps, navigation tools, and support platforms come in. The website is only the starting point.