Automated scanning
We scan pages and screens against the WCAG criteria set and surface every non-conformance that can be detected automatically.
Managed Services
Accessibility Testing Service
We measure and document your conformance under the European Accessibility Act.
Request a conformance assessmentAccessibility Testing Service
Accessibility testing assesses how usable digital products are for people with disabilities, measured against the WCAG criteria. We combine automated scanning, expert evaluation and assistive technology testing, and report findings by conformance level and remediation priority.
The legal position
Accessibility has been an enforceable obligation since 28 June 2025.
The European Accessibility Act has applied through member state law since 28 June 2025. The directive brings ten categories of product and service into scope. Six of those categories map directly onto the industries Virgosol works in: banking services, e-commerce, electronic communications services, transport information services, self-service terminals such as ATMs and payment kiosks, and audiovisual media services.
Which standard actually binds you: WCAG 2.1 or 2.2? This is the most frequently confused point in the market. Three layers need to be kept apart.
The European Accessibility Act is an EU directive, in force since 28 June 2025 and binding through member state law. EN 301 549 v3.2.1 is the harmonised technical standard the EAA points to, and it incorporates WCAG 2.1 AA in full. WCAG 2.2 is the current W3C recommendation and a superset of 2.1; it is expected to become binding with EN 301 549 v4.1.1.
The level that binds you today is WCAG 2.1 AA. WCAG 2.2 adds nine further success criteria on top of 2.1 and contains it. That is why we run the assessment against 2.2: conformance to 2.2 satisfies the present 2.1 AA obligation and prepares you for the next version of the standard. The report separates the two levels, so your current obligation and your forward target never get confused.
Our scope
Expert evaluation
We manually assess the criteria automated scanning cannot reach. Anything involving meaning, order or context requires expert judgement, and a substantial share of the criteria fall into that group.
Assistive technology and keyboard testing
We test the interface with the JAWS, NVDA, VoiceOver and TalkBack screen readers. Keyboard navigation, focus order and focus visibility are run as a separate check.
Visual and interaction checks
We measure colour contrast ratios and examine form fields for labelling, error messaging and validation behaviour. Critical journeys such as payment and sign-in are verified for accessibility end to end.
Multimedia and responsive accessibility
We assess video and audio content against captioning, transcript and audio description requirements. We verify that the interface remains accessible across screen sizes and zoom levels.
Testing with real users
We test critical journeys with participants who use assistive technology. Automated scanning and expert evaluation measure conformance to the criteria; testing with real users shows whether the journey can actually be completed.
Conformance level reporting
We classify findings against levels A, AA and AAA. WCAG 2.1 AA conformance and WCAG 2.2 conformance are reported separately, together with the distance to your target level.
Remediation prioritisation
We rank findings by user impact and remediation cost, and give the development team an applicable fix with the reasoning behind it.
Continuous monitoring and CI/CD integration
We connect the accessibility checks into Jenkins, GitLab CI and GitHub Actions pipelines. New non-conformances are then caught automatically on every release, and the conformance level won at audit does not erode over time.
How do we work?
We plan around your release rhythm, manage the operation and improve it in every cycle.
Planning
We define scope, test levels and success criteria against your release calendar. Environment and test data requirements are resolved before the work begins.
Management
We take on team, tool and environment management. Progress is reported regularly against defined KPIs.
Execution
We run the tests and prioritise the findings. We track closure together with your development teams.
Improvement
At the end of every cycle we review scope, automation rate and escaped defect rate. The priorities for the next cycle are set from that review.
Virgosol
How technology supports the service
We run the accessibility checks through the Accessibility module in RabbitQA. Scanning follows the WCAG criteria set and findings are collected in the same reporting structure as every other test result, so accessibility stops being a separate audit exercise and becomes part of the quality report. Automated scanning on its own is not sufficient. Screen reader testing is carried out on JAWS, NVDA, VoiceOver and TalkBack, and keyboard and focus checks are run manually. For continuous monitoring we connect the checks into your existing CI/CD pipeline. Self-service terminals are within EAA scope. Physical accessibility scenarios on ATMs, payment kiosks and POS devices can be run robotically with Roboclick.
What you receive
Deliverables
- Separate conformance reports for WCAG 2.1 AA and WCAG 2.2
- Findings from automated scanning, expert evaluation and assistive technology testing
- An observation report from testing with real users
- Level-based conformance indicators and a measured distance to target
- A remediation list prioritised by user impact
- Continuous monitoring wired into your CI/CD pipeline
What changes for the business
- Your conformance position under the EAA becomes documented
- Evidence is ready for audit and vendor assessment requests
- Accessibility findings enter the release pipeline instead of arriving after it
- The conformance level you reach does not regress in later releases
- Users of assistive technology come within the reach of your service
Frequently Asked Questions
Should we target WCAG 2.1 or 2.2?
The level that binds you today is WCAG 2.1 AA, because EN 301 549 v3.2.1, the standard the EAA points to, incorporates it. We run the assessment against WCAG 2.2 because 2.2 is a superset: it satisfies the current obligation and prepares you for the next version of the standard. The report shows both levels separately.
Is our organisation in scope for the EAA?
The directive covers ten categories of product and service. Banking services, e-commerce, electronic communications services, transport information services, self-service terminals and audiovisual media are among them. Microenterprises with fewer than ten employees and turnover below two million euros are exempt from the service obligations; there is no exemption for products.
Is automated scanning enough?
It is not. Automated tools detect a portion of the criteria; anything requiring meaning, context or journey integrity needs expert evaluation. A page can pass an automated scan cleanly and still be unusable with a screen reader.
How long does an audit take?
Duration is set by the number of pages and screens in scope, the complexity of the journeys and whether testing with real users is included. We confirm the timeline once the inventory is established.
Are mobile applications in scope?
Yes. We assess mobile applications against the platform accessibility guidelines and the WCAG criteria, running the tests on VoiceOver and TalkBack.
Do you carry out the fixes?
Fixes are applied by your development team; we provide the applicable fix and the reasoning behind it. We run the post-remediation validation and measure the change in conformance level.
Do you guarantee compliance?
No. Compliance is determined by the regulator and by the courts, and no testing provider can undertake it. What we deliver is your conformance position measured criterion by criterion and documented in a form that can be presented to an auditor.
Let us measure your conformance position under the EAA
Fill in the form and we will look at your digital channels, the services that fall within EAA scope and your target conformance level.