Accessibility: WCAG 2.1 AA and the European Accessibility Act
The European Accessibility Act has applied since June 2025, and its national implementations — Germany's BFSG among them — turn accessibility from a nice-to-have into a requirement for consumer-facing digital services. We bring existing websites, shops and apps up to WCAG 2.1 AA, the level EN 301 549 references. The sequence is always the same: measure, prioritise, fix — starting where accessibility and revenue are the same thing, which is the form, the cart and the checkout. What an automated scan finds gets cleared in days; the criteria only a person can judge — keyboard operation, focus order, screen reader output — we test by hand and write down. What you end up with is not a badge but a defensible position: what conforms, what doesn't, and what is scheduled. That documentation is the part that matters when someone asks.
What's included
Audit against WCAG 2.1 AA / EN 301 549: automated scan plus manual testing of keyboard operation, focus order and screen reader output
Prioritised remediation plan with effort estimates — ordered by impact, not by criterion number
Implementation in code: semantic structure, form labelling, contrast fixed in the design system, focus management, ARIA only where it is actually needed
Accessibility statement in the expected structure, plus a feedback route for users to report barriers
Regression protection: accessibility checks in CI, so the next feature doesn't undo the work
Why runIT
We don't sell overlay widgets. Those scripts sit on top of the page, leave the underlying markup untouched, and are explicitly criticised by disability organisations — the barrier stays, it just becomes harder to see.
We are explicit about what automation cannot check. Automated testing catches roughly a third of real failures; anyone certifying “100% compliant” on that basis is selling a confidence that doesn't exist.
We fix in the design system rather than page by page. A contrast error corrected in the component doesn't come back with the next release; one patched across twelve pages does.
As smooth as a software deploy.
Sprint-focused, transparent, measurable. You see what we do at every step.
Brief & Strategy
We clarify goals, users and technical constraints. Work begins on day one.
Design & Architecture
UX flows, system architecture and data models run in parallel.
Build & QA
CI/CD pipeline live in the first week. Automated tests, code review, observability — by default.
Ship & Grow
Post-launch SEO, performance and analytics keep growth compounding.
This same system, shipped before.
Pilates Rehberi and Pilates Studios UK are live examples of the programmatic-SEO local-directory system you're looking at right now — built, launched and ranking.
Frequently asked questions
Is an accessibility overlay enough to comply?
No. Overlay scripts promise conformance in one line of JavaScript but change nothing underneath — missing form labels, broken heading structure and unreachable keyboard paths all remain. Disability organisations and screen reader users have criticised these tools for years, partly because they can make navigation worse. Conformance is created in the source: semantic HTML, labelled controls, sufficient contrast, complete keyboard operability. That is more work than adding a script, and it is the part that survives scrutiny.