One accessible codebase for the phone, the desktop, and the on-site terminal
Three devices, three contexts, one application. Building adaptively rather than separately is what keeps accessibility a guarantee instead of a per-platform afterthought.
Engineering Practice
A person might use a service on their phone on the move, on a laptop at home, or at a terminal in a branch or an office. The instinct is to build three products. The discipline is to build one adaptive application that meets each context well, because three codebases means three places for accessibility and security to drift apart.
Adaptive, not separate
The same application runs in a phone browser, on the desktop, on a shared on-site terminal, and, where needed, inside a native mobile shell. What changes is the surface, not the logic: a shared terminal hides what a shared device should not keep, the native shell unlocks hardware the browser cannot reach, and the workflow underneath is the same validated workflow everywhere.
Accessibility is a gate, not a nicety
When there is one codebase, accessibility is something you can actually guarantee. WCAG 2.2 AA is treated as a release gate rather than a goal, and the harder AAA criteria are met wherever they are feasible. A shared terminal in a busy hall, used by someone tired, stressed, and in their second language, is the real test, and it is the one the single codebase is built to pass.
- Keyboard and screen-reader paths that are tested, not assumed.
- Reflow and small-screen handling so the action a person needs never scrolls off the screen.
- Language support built into the framework, with the same flow translated rather than re-implemented.
- Reduced-motion and contrast honored globally, not bolted onto individual screens.
If accessibility depends on which device you picked up, it is not accessibility. It is luck.
The dividend
One codebase is cheaper to secure, cheaper to audit, and cheaper to change. A fix lands once and reaches every surface. A new requirement is implemented once and is correct everywhere. People get a consistent experience, and the institution gets a system it can actually keep up to standard.