Automated tools
Supporting only — to catch some code errors quickly.
Services / WCAG audits
A WCAG audit that leads to fixes.
An expert accessibility audit against WCAG 2.2 level AA. We combine manual testing, assistive technologies and automated tools, and describe the results in language your team can act on straight away.
Accessibility goal
Who it is for
Who is an accessibility audit for?
An audit pays off wherever a website or app is an important way of reaching people — whether that comes from a legal obligation or from your organisation's own decision.
Public institutions
Offices, universities and agencies that must make websites and documents accessible and describe it honestly in an accessibility statement.
E-commerce and services
Shops and transactional services where a barrier in the basket, a form or the payment step means a lost customer.
Apps and SaaS
Products with sign-in, dashboards and multiple roles that need their processes tested, not just individual pages.
Organisations and NGOs
Foundations, associations and companies that want to plan their website's growth deliberately and reach every audience.
Scan vs audit
An automated scan is not a full review.
Automated tools quickly find some problems, but they cannot judge whether a person can actually complete a task. That is why in an audit we use them only as support. No error count returned by a tool is an automatic conformance assessment — the result depends on expert interpretation and evidence.
Who assesses
An algorithm checking selected rules in the code → An auditor experienced in WCAG and assistive technologies
What it finds
Some measurable errors, e.g. missing alternative text or low contrast → Barriers in real use: logic, order, states, messages and clarity
Keyboard and focus
Does not check completing a process without a mouse → Key journeys completed using the keyboard only
Screen reader
Cannot tell what a user will actually hear → Tests with screen readers in agreed configurations
Content and forms
Cannot judge whether texts, instructions or error messages are clear → Review of forms, validation, content and documents as scoped
Output
A list of alerts to verify, often with false positives → A report with evidence, user impact, severity and a recommendation
Conformance assessment
Is not a WCAG conformance assessment → An expert assessment within the agreed scope and sample
Scope and criteria
WCAG 2.2 AA as the benchmark.
The standard and level are written into the offer and the report. We define the scope with a representative sample of templates, components and key journeys — not an arbitrary number of pages.
Representative templates and view types
Key journeys: sign-in, search, forms, basket
Interface components: menus, modal dialogs, tables
Mobile versions and behaviour when zoomed
PDF documents and media — if part of the service
Error states, messages and validation
Methodology
We combine methods, we don't cut corners.
We match test types to the scope of the offer and back them with evidence. “Not tested” never means “passed”.
HTML and ARIA
Manual review of semantics, names, roles and component states.
Keyboard navigation
Focus order and visibility, no keyboard traps.
Screen readers
Structure, labels and messages in agreed configurations.
Zoom and reflow
Behaviour at up to 400% zoom and in narrow viewports.
Contrast
Text, icons, interactive states and graphics.
Text resizing
Readability after enlarging text only and changing spacing.
Forms and validation
Labels, instructions and error messages tied to fields.
Mobile scenarios
Gestures, screen orientation and touch target size.
Media
Captions, transcripts, audio description and player controls.
Electronic documents
Structure, tags, reading order and metadata of PDF files.
Cognitive requirements
Clarity, predictability and interface personalisation.
Timeline
Audit stages from kick-off to report.
How long each stage takes depends on scope and on access to materials. You will find the exact timeline in the offer.
Kick-off and materials
We agree goals, contacts and access to the test environment. You share test accounts through a secure channel.
Test plan
We choose the sample: templates, components, journeys, devices, browsers and assistive technologies.
Testing and documentation
We test according to the methodology and record every barrier together with evidence.
Report and review
The report goes through an internal expert review before it reaches the client portal.
Results walkthrough
We present the results to your team and help you order the remediation work.
Retest — optional
Once fixes are deployed, we check the selected barriers and describe the outcome of re-verification.
Deliverable
What does the audit report include?
The report is a working document for the team and decision material for management. Every version has a number, a date and a change history.
Goal, scope, standard and test environments
Methodology, sample and scope exclusions
Executive summary with the main risks
WCAG criteria matrix with statuses
Each barrier described with evidence and a recommendation
Priority recommendations and a remediation backlog
Test limitations and a glossary
Appendices and the report's version history
How to order
How do I order an audit?
From the first description of your service to the start of testing — no hidden steps. If the brief turns out wider than the ordered scope, we prepare an explicit change proposal for price or timing. We never cut the scope without your consent.
Describe your service
In the configurator or the form you give the address, service type, key processes and expected deadline.
Scope and quote
We analyse the brief, match a package and prepare a scope with a price or a custom quote.
Offer approval
Before paying you see the scope, the reference standard, deadlines, the price with tax and the change rules.
Testing starts
Once the order is confirmed and materials are shared, the auditor accepts the scope and starts work.
After the audit
The report is the start, not the end of the work.
Implementation support
We help UX, front-end and editorial teams implement fixes — or we implement them ourselves.
Retest
After changes, we check the selected barriers and describe the outcome of every fix.
Periodic monitoring
We come back to your service at an agreed rhythm to catch regressions after updates.
FAQ / WCAG audits
Questions before ordering an audit.
An evaluation of a selected sample of views and processes against WCAG 2.2 level AA criteria: automated tests, expert manual testing, keyboard navigation, screen reader testing, contrast and reflow. The result is a report listing the barriers, their priorities and recommendations.
Let's check your service.
Describe your product and we will propose an audit scope and next steps.