PIPELINEGuide
Connect an accessible website with existing systems
Does everything need to be replaced for this? Usually not. What can be connected to an existing system landscape, where the limits are, and which part typically takes the longest.
For an accessible website, in most cases nothing existing needs to be replaced: inventory management, CRM, calendar, accounting, or phone systems are connected via interfaces. What matters is whether the respective system has a documented interface — and the time-critical part is almost never the technology but obtaining the access credentials.
01 — Integration
Connection with existing systems
The most common misconception is that everything must be new. In most cases, the existing system landscape remains in place, and the accessible website builds on top of it — through interfaces, not replacement.
What gets connected in practice: ERP, CRM, calendar, accounting, phone system, newsletter system, website. What matters is whether the respective system has a documented interface. Where none exists, there's usually a workaround — but that costs effort and needs to be clarified up front, not discovered later.
The time-critical part is almost never the technical integration, but obtaining access credentials. Starting early here noticeably shortens the project timeline.
02 — Requirements
What you need for an accessible website
- A clearly defined trigger. Not “we should do something with AI,” but a process that demonstrably costs time or orders today.
- Existing content or data. An accessible website works with what is already there. The more complete the starting point, the shorter the setup.
- Access to the systems involved. Whoever manages the credentials needs to be involved from the start — this is, in our experience, the most common cause of delays.
- One decision-making contact person. One, not three.
- Willingness to refine after launch. The first weeks in real operation show what was missing in the concept. That's normal and accounted for.
03 — Bottlenecks
What typically causes delays
- Content and deliveries. By far the most common cause of delay. Text, images, price lists, access credentials — what's missing blocks progress.
- Decisions. When it's unclear who approves, the project waits. A named contact person with decision-making authority noticeably shortens the timeline.
- Access to third-party systems. Getting access to inventory management, phone systems, or CRM regularly takes longer than the integration itself.
- Endless review rounds. Two correction rounds are normal, five are a sign that the goal wasn't clear at the start.
04 — Questions
Frequently asked questions
Is an accessibility overlay sufficient?
No. These overlays do not fix the underlying problems and are largely rejected by disability advocacy groups. They can even create additional barriers. Accessibility is created in the markup, not in a layer on top.
Does this also apply to PDF documents on the website?
Yes, if they contain essential information — such as price lists or downloadable forms. PDFs must also be structured with alternative texts.
What is the most common error?
Forms without linked labels and controls that cannot be reached with the keyboard. Both go unnoticed by anyone working with a mouse — and make the site unusable for others.
How long does a complete audit take?
For a medium-sized website, one to two weeks, depending on the number of different page types and interactive elements such as forms or filters.
Are we affected by the Barrierefreiheitsgesetz?
The Austrian Accessibility Act has been in force since June 28, 2025, and primarily applies to online services in the consumer sector: online shops, bookings, e-ticketing, banking services. Microenterprises with fewer than ten employees and less than two million euros in revenue are exempt for services — but not for the sale of products. A purely informational site without sales is generally not covered.
Can we implement this step by step?
Yes, by priority: first the defects that completely block usage, then those that make it difficult. This can be spread across several stages without taking the site offline in the meantime.
How much work is involved for an existing site?
It varies widely. A well-built site often only needs contrast corrections, alternative texts, and focus indicators. A site with custom-built controls without keyboard support can be more work than building from scratch.
05 — Next
Related pages
- Accessible Website — Overview
- Accessible Website — Privacy
- Accessible Website — Contract and Ownership
- Accessible Website — Where to Start
- Accessible Website — Do It Yourself
- Accessible Website — Common Errors
- Accessible Website — Funding
- Accessible Website — Checklist
- Have a website created
- Web design
- Website relaunch
- All guides
Accessible Website by Region
Next step
We'll look at your starting position.
Tell us what's eating up time today. That becomes an assessment with effort and benefit — and only then an offer.