See whether the site exposes the company to legal and reputational risk, in a few minutes
- Automated page test against WCAG 2.1 / 2.2
- Tool report with the issues found
- Accessibility status of the page
197 EUR gross, 160 EUR net
160 EUR
Take care of accessibility. Take care of yourself.
Check whether your site is available to everyone: today, tomorrow, and when it actually matters.
AUDIT · yoursite.com Live
Perceivable Perceivable — 12 criteria
✓ 12 / 12Operable Operable — 11 criteria
⚠ 9 / 11Understandable Understandable — 8 criteria
✓ 8 / 8Robust Robust — 6 criteria
✕ 2 / 640
avg. WCAG issues / project
99%
conformance after fixes
We work on digital accessibility with our clients. See the work.
We support banks, ecommerce, public bodies, financial services, grant-funded projects.
Accessibility Team in numbers
URLs reviewed
We have reviewed thousands of URLs for WCAG conformance and for whether people can actually use the page.
Average WCAG issues per project
A typical project turns up about 40 material WCAG failures that affect how the site can be used.
Conformance after fixes
After the recommended changes, projects reach a high WCAG 2.2 AA conformance rate, at 99%.
Projects closed with a re-audit
78 projects ended with a re-audit confirming WCAG conformance after the fixes.
Accessibility since 2016
We have been auditing accessibility since 2016, before the mandatory rules took effect.
Companies using the free tool
1806 companies have already used our free digital-accessibility check.
More about the team on the Team page.
A setup that already works
Packages include a report, a WCAG 2.2 audit and an accessibility statement.
Turn audit results into an action plan and the papers leadership needs, in 3–7 days.
- Automated page test against WCAG 2.1 / 2.2
- Expert manual review of key pages
- Issue ranking (critical / major / recommended)
- Reading of the results against your accessibility duties
- Implementation notes for the IT team
- Draft accessibility statement
- The accessibility documents you have to hold
- A report you can take into the organisation
2214 EUR gross, 1800 EUR net
1800 EUR
Full WCAG 2.2 assurance and an IT rollout plan, with a re-audit after the fixes
- Full page review (automated plus manual)
- Review of every key user path
- Issue ranking with legal and business risk
- Detailed technical and UX recommendations
- Draft accessibility statement
- Full accessibility documentation
- 1:1 expert session
- Re-audit after the changes
- Certificate of the audit
- Pack for an inspection
3813 EUR gross, 3100 EUR net
3100 EUR
Questions and answers
Practical notes on digital accessibility and answers to the questions we hear most.
We work toward a web that anyone can use, whatever their limits, tools or way of getting online. We help organisations take digital barriers down and give people equal access to information and services.
Questions:
ask a consultantWhat is digital accessibility?
Digital accessibility means designing and building sites, apps and tools so everyone can use them, including people with disabilities. With WCAG 2.2 in place, content stays readable and usable whether someone has limits of sight, hearing, movement or cognition. Examples: captions on video, usable colour contrast, keyboard access, PDFs that a screen reader can follow. Accessibility widens reach, improves UX and helps SEO.
Why does digital accessibility matter?
Digital accessibility gives people equal access to information and services, lowers legal risk and supports the brand. WCAG 2.2 and Poland’s PAD act are mandatory for many public bodies and regulated firms. Accessibility lifts traffic, conversions and trust. It also reaches the 30–40% of users who rely on accessibility features.
How long does an accessibility review take?
Timing depends on the package and the size of the site. Accessibility Check: a fast pass over the basics (a few minutes). Accessibility PRO: a full review and fix list (3–7 days). Accessibility PREMIUM: a full audit, deeper testing and a recommendations report (14–21 days). A tight review cuts the risk of fines, improves conformance and keeps the work moving.
Meet the Accessibility Team
Accessibility Team is a crew of specialists. Meet them below or on the Team page.
Rafał Kaczmarzyk Team lead / project coordinator
Julia Linek Accessibility auditor
Janusz Pierzchalski Sign-language interpreter
Paulina Gajoch Accessibility tester / researcher
Piotr Nowicki Accessibility tester
Monika Balon Communications and education
Also see the products we build so people can reach information, goods and services.
Read the notes
Need the duties that sit on digital accessibility? Start with the latest pieces, or browse all guidance and obligations.
EN 301 549 V4.1.1 was adopted on 24 August 2026 and published on 2 September 2026. Presumption of conformity will only apply after citation in the Official Journal of the EU, expected around 30 November 2026. Until then, V3.2.1 remains the reference. National standards must adopt the new version by 31 May 2027 and withdraw conflicting standards by 31 May 2028.
EN 301 549EN 301 549 V4.1.1 was published on 2 September 2026. It is the first major revision of the European ICT accessibility standard since March 2021. The standard now references WCAG 2.2, adds user preference requirements (9.7, 10.7, 11.7), rebuilds real-time text requirements, and adds annexes linking it to the European Accessibility Act. Presumption of conformity will only apply after citation in the Official Journal of the EU.
EN 301 549Every EN 301 549 requirement has its own test in normative Annex C. A test has four fields (evaluation type, preconditions, procedure, result) and three possible outcomes: passed, failed, not applicable. The standard states it is not a testing methodology: sample selection, tools and reporting are left to the auditor.
EN 301 549
Legal, financial and brand risk: fines, inspections, people shut out.
Risk
Who has to comply: public administration, the EAA, private bodies.
Who is covered
Putting accessibility in place and keeping it: WCAG 2.1 AA, an accessibility statement, a way to report problems.
Implementation