PIPELINEGuide
Implementing an Accessible Website: Step by Step
The path from decision to live operation — in the order that has proven effective in small businesses, including the points where projects typically get stuck.
An accessible website is implemented by first identifying the bottleneck, then scoping it small, and only then executing. The implementation itself takes 3 to 6 weeks; a project is almost never delayed by technology, but by missing content, access, and decisions.
01 — Getting started
Where to begin
Name the bottleneck
Not the most interesting thing, but what takes the most time. A week of tracking what repeats delivers a more realistic list than any workshop.
Define a small scope
One process, one measurable goal. What works gets expanded — what doesn't costs little.
Survey the starting situation
Which content, data and access are available. For an accessible website, this is the factor that most strongly influences effort and timeline.
Decide who is responsible
For the implementation and for operations afterward. Without this definition, every system becomes outdated.
Only then request proposals
With a clear scope, proposals become comparable. Without it, you get numbers that have nothing to do with each other.
02 — Process
The steps in detail
Audit
Automated testing finds about a third of the issues. The rest requires manual testing — keyboard, screen reader, magnification.
Prioritize
What blocks use, what is a cosmetic flaw. That's the order in which issues are fixed.
Fix
Implementation, mostly in design and markup, less often in functionality.
Document
Re-audit, report, and accessibility statement for the website.
03 — Participation
What we need from you
- A contact person who can make decisions — not just forward them.
- Access to the affected systems, in time and not on launch day.
- Real examples from daily business — the messier, the more useful for testing.
- Two to four hours for coordination, distributed over the project duration.
- An answer to the question of what success means. Without it, nothing can be assessed afterward.
04 — 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.
05 — Questions
Frequently asked questions
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.
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.
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.
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.
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.
What happens in case of violations?
The Sozialministeriumservice is responsible. Administrative penalties of up to 80,000 euros are provided for. In the initial phase, the focus was mainly on advice rather than penalties, but that's no guarantee for the future — proceedings are already underway.
06 — Next
Related pages
- Accessible Website — Overview
- Accessible Website — Duration
- Accessible Website — Funding
- Accessible Website — Small Businesses
- Accessible Website — Costs
- Accessible Website — Checklist
- Accessible Website — Do It Yourself
- Accessible Website — Risks
- Have a website created
- Web design
- Website relaunch
- All guides
Accessible Website by Region
Next step
Let's talk briefly about whether this makes sense for you.
A twenty-minute conversation is usually enough to clarify whether a project makes sense. If not, we'll say so — that's cheaper for both sides than an offer nobody needs.