---
title: "Taking over a web app: what we check before we change a line"
updated: "2026-11-17"
url: "https://www.etheon.com/company/news/taking-over-a-web-app"
authors: "Etheon"
published: "2026-11-17"
type: "news"
---

# Taking over a web app: what we check before we change a line

Five checks before we change a line: the repository and its dependencies, accessibility against WCAG 2.2 AA, performance, the deploy pipeline and consent.

Yes, we take over existing web apps, and we start with five checks before we change a line: the repository and its dependencies, accessibility, performance, the deploy pipeline, and analytics and consent. Each check ends in something you keep.

## What do you check before changing a line?

1. Repository and dependencies audit. You receive a report.
2. Accessibility audit, WCAG 2.2 AA. You receive an issue list.
3. Performance baseline. You receive a budget.
4. Deploy pipeline. You receive a runbook.
5. Analytics and consent. You receive a consent map.

## Why check accessibility and consent at takeover?

Because speed and accessibility decide whether people can use a site at all, and because the web apps we build render on the server for speed, meet WCAG 2.2 AA and load analytics only after a visitor consents.

## What happens after the checks?

Every release is held to its budgets and checked for accessibility. Each kind of page gets a performance budget agreed with you, every release is tested against WCAG 2.2 AA with screen readers and keyboards, and a release over its budget waits until it is fixed.

## What if the code needs more than fixes?

Then it is replaced in steps. Legacy modernization replaces an old system while the business keeps running on it, one module at a time with a rollback at each step: see [Software](https://www.etheon.com/services/software#modernization).

The takeover plan is on our [Web page](https://www.etheon.com/services/web#takeover). Tell us your use case and timeline. We reply within one business day.