Start
Small and mid-sized stores
99 PLN net / month
- 1 domain, up to 100 pages
- Monthly scan and regression report
- Barrier-report form and 30-day timer
- Reminders on day 7, 14 and 25
Polish Accessibility Act · in force since 28.06.2025
Scanority.Your store’s accessibility. Without guesswork.
Find the barriers between your customer and a purchase. A concrete WCAG report, priorities and remediation guidance — no overlays, no empty promises.
- Specialized accessibility testing engine
- WCAG 2.1 AA criteria
- No overlays altering your site
- requirements apply to e-commerce services
- 28.06.2025
- to respond to a consumer accessibility complaint
- 30 days
- maximum fine imposed by the President of PFRON
- up to ~PLN 89k
Indicative values based on the Act of 26 April 2024. Not legal advice.
§ 1. The problem
Accessibility is no longer a nice-to-have. It is an obligation, with a deadline and a penalty.
The European Accessibility Act (EAA) was transposed in Poland by a statute that covers e-commerce and consumer banking, among others. Only micro-enterprises providing services are exempt.
A customer who cannot add a product to the cart with a screen reader, or cannot read a price because of low contrast, can file a complaint. You have 30 days to respond. The next step can be a request to the President of PFRON.
A traditional audit costs PLN 3,000 to 15,000 and goes stale with the next marketing campaign. Free tools speak to developers, not to business risk.
§ 2. How it works
Three steps, about twenty seconds.
Paste your store URL
We pick the homepage and three high-risk subpages: product, category and cart.
The engine tests rendered pages
A specialized accessibility engine checks contrast, form labels, alt text, heading structure, button names and dozens of other rules.
You get a risk index and fixes
The first 3 critical barriers are shown right away. Unlock the full report with your email and tax ID.
§ 3. Platform
The scanner is just the start. Scanority covers the whole process.
The Act requires more than an accessible site — you must also handle customer complaints within 30 days. We are building one place for all of it, from finding a barrier to answering a complaint.
Available now
Accessibility scanner
Automated WCAG 2.1 AA audit of your homepage and key subpages, with priorities and fix guidance.
In development
Barrier reporting form
A lightweight, accessible widget or link where customers report accessibility problems. Not an overlay — it changes nothing on your site.
In development
Complaint panel with a 30-day counter
All reports in one place, with statuses, response history and a countdown to the statutory deadline for every case.
In development
Notifications and reminders
Alerts about new reports and reminders before deadlines, by email or messenger.
Features marked “In development” are being shaped with our first customers. Leave your details in the report to influence them.
Our direction
Rules today. More context tomorrow.
An automated scan is a starting point, not a finish line. We are developing a process combining repeatable checks, purchase context and human verification.
Available now
Established WCAG rules
A specialized accessibility engine analyses rendered pages. Each finding identifies the element, its impact and a practical direction for fixing it.
Planned · AI
Analysis beyond the rules
We plan to use AI to assess image context, content and purchase journeys — to highlight more areas needing verification.
Always needed
Human verification
Keyboard, screen reader and real user experience. AI should support this stage, not replace an expert’s judgment.
AI is not yet part of this scan. We will not claim a higher coverage percentage without measurement. More findings do not mean a compliance certificate.
§ 4. Our position
We don't sell overlays. Here's why.
Accessibility widgets that add a contrast or font-size button do not fix the page's code. The barrier for a screen reader stays exactly where it was.
Disability organisations and experts have warned for years that overlays can actually get in the way of assistive technology. In the US, companies using overlays are still being sued.
Scanority points to the exact element, the WCAG rule and the fix to ship in code. Accessibility that lives in your product, not in a script.
| — | Overlay widget | Scanority |
|---|---|---|
| Changes the site's code | No | Tells you what to change |
| Helps screen reader users | Usually not | Yes, once fixes ship |
| Separates automated and manual checks | No | Yes, in every report |
| Promises “100% compliance” | Often | Never |
§ 5. A sample report entry
Here is what a single barrier looks like in a report.
Critical · WCAG 2.1 · 4.1.2 Name, Role, Value (A)
“Add to cart” button has no accessible name for screen readers
/product/winter-jacket
A blind user only hears “button”. They cannot tell it adds the product to the cart, so it blocks the purchase.
<button class="btn-cart">
<svg>…</svg>
</button>Fix
<button class="btn-cart"
aria-label="Add to cart">
<svg aria-hidden="true">…</svg>
</button>§ 6. Early-adopter pricing
Two plans. The price depends on the size of your store.
You pay for the number of pages we monitor and how often we scan. A small store never pays for a large catalogue.
Pro
Large catalogues and frequent changes
149 PLN net / month
- 1 domain, up to 1,000 pages
- Weekly scan and regression report
- Everything in Start
- Priority email alerts and accessibility statement generator
Early-customer pricing is guaranteed for 12 months from service launch. Net prices, no commitment during the pilot.
§ 7. Questions
Frequently asked questions
Is my company covered by the Accessibility Act?
If you run an online store or another consumer e-commerce service and you are not a micro-enterprise (fewer than 10 employees and turnover or balance sheet of up to EUR 2 million), most likely yes. See our guide to the Act for details.
Does the scan guarantee compliance?
No, and no automated tool can. Automation typically catches 30–40% of WCAG issues. The rest needs manual testing with a keyboard and a screen reader, so every report includes a manual testing checklist.
Why do you ask for a tax ID (NIP)?
It lets us check whether the company is an exempt micro-enterprise and give a sound recommendation. We don't spam, and you can have your data deleted at any time.
Do I need to install anything?
No. The scan runs from the outside, like a visitor. We add no script or overlay to your store.
Which testing engine do you use?
axe-core by Deque, the same engine used by Google Lighthouse and Microsoft Accessibility Insights. We add plain-language explanations, business priorities and a risk index on top.
From the founder
I'm building Scanority because I've seen too many stores buy an accessibility widget and consider the job done. The Act doesn't work that way. I'd rather tell you honestly what needs fixing than sell you a false sense of security.