How many pages are tested?

A representative selection of all page types, usually ten to 20 pages plus key user journeys.

How long does the audit take?

Two to four weeks until the report, depending on scope.

Do you also help with implementation?

Yes, from design corrections to development.

Testing & evidence

Accessibility audit to WCAG 2.2 and EN 301 549

We test your website for accessibility, document every issue and show the path to conformance.

Free initial call

Reply within 24 hours · no obligation

Our audit combines automated checks with manual testing: keyboard operation, screen readers, contrast, forms, error messages, video and documents. Every finding includes location, affected success criterion, severity and an actionable fix. On request we support remediation and produce the accessibility statement required by the European Accessibility Act.

Scope of services

What this service includes

Automated and manual testing of representative pages
Screen reader and keyboard testing
Findings report with severity and suggested fix
Assessment against WCAG 2.2 level AA
Support during remediation
Accessibility statement and re-test

Expertise & perspective

What matters for your project.

An accessibility audit examines a defined selection of pages and journeys for barriers to use. Zensations in Vienna combines automated checks with manual testing and maps findings to relevant WCAG requirements.

Define the assessment scope transparently

An audit needs a justified selection of typical pages, navigation and core processes. Dynamic states such as errors or open dialogs belong in scope too. The report should identify the tested version, coverage and criteria. An assessment of selected pages should not automatically be presented as an assessment of the entire digital offering.

Combine automated and manual methods

Tools identify certain technical problems, such as missing markup. Whether a screen reader makes a form understandable or keyboard focus is managed sensibly requires additional manual assessment. WCAG 2.2 includes requirements concerning obscured focus and accessible authentication. Applicability is checked against the actual journey.

Make findings actionable

A useful finding describes its location, affected usage and a possible correction. Priorities help developers address serious barriers first. After changes, testing verifies that the problem is resolved without introducing another barrier. The report is a working foundation; conformity statements need to match the documented scope.

Useful for the initial conversation

Website, test access and core journeys
Intended scope and earlier reports
Technical implementation contact

Reference: W3C: Web Content Accessibility Guidelines (WCAG) 2.2

Who it is for

A good fit if

Public bodies with legal obligations
Companies within the scope of the European Accessibility Act
Shops and portals with a broad audience

Frequently asked questions

Clarity before you start

How many pages are tested?: A representative selection of all page types, usually ten to 20 pages plus key user journeys.
How long does the audit take?: Two to four weeks until the report, depending on scope.
Do you also help with implementation?: Yes, from design corrections to development.

Part of Accessibility

Let’s make it happen

Let's talk about your project.

Whether it's a new website, AI in marketing, or a full relaunch, we listen and deliver a clear path forward.

Reply within 24 hours
Free and non-binding
A concrete proposal instead of a sales pitch

office@zensations.at