CrossBrowserTesting
Sauce Labs
BrowserStack
browserling
TestMu AI (Formerly LambdaTest)
Browsershots
Litmus
MultiBrowser
Scandiary
accessiBe
UserWay
Siteimprove
BrowserStack
ExcellentWebCheck
Scandiary runs an automated WCAG 2.1 AA accessibility scan on the same pages of your website every Monday, then emails you a dated report showing what is new, what increased, what decreased, and what is no longer detected since the previous scan.
It is built for online shops with no in-house developer and no accessibility budget.
Three things it deliberately does not do:
It does not issue a compliance verdict, and no report we send will ever use that word. Automated checks find roughly a third of accessibility problems — ours included. The rest, whether alt text is meaningful, whether a page makes sense through a screen reader, needs a person.
It never writes "fixed", only "no longer detected". A problem can disappear because a page was deleted, or because an element only shows up sometimes. Disappearing is not proof of repair.
If nothing changed, it sends nothing. A week with nothing in it is a real result, not a failure — though it is also not proof that your site is accessible.
No install, no account, no script on your site. The site itself loads no third-party scripts, no analytics and no external fonts. Five pages are scanned free every Monday and the free plan is not a trial. $12 a month (or $120 a year) adds twenty pages and lists where each problem sits — every affected element with its CSS selector and the page it is on, up to 25 per issue, not one example.
CrossBrowserTesting ScandiaryThis service is highly recommended for software development teams, QA engineers, and web developers who need to ensure compatibility and functionality of their web applications across multiple browsers and devices. It is particularly useful for organizations with a focus on maintaining high-quality user experiences across various platforms.
No Scandiary videos yet. You could help us improve this page by suggesting one.
Scandiary's answer:
Memory, not detection. We use axe-core, the same open-source engine most accessibility tools are built on, so a browser extension will show you the same issues on a page you are looking at right now. The difference is that we scan the same pages every Monday, keep the history, and tell you what is new, what increased, what decreased and what is no longer detected since last week. Nobody runs an extension on their own site every week for a year, which is the only reason this exists.
Two things we will not do. We do not issue a verdict: automated checks find roughly a third of accessibility problems, and the rest needs a person. And we never say a problem was repaired, only that it is no longer detected, because a problem can disappear when a page is deleted. If nothing changed, we send nothing.
Scandiary's answer:
Online shops and the people who look after their websites — often a Shopify, WooCommerce or Wix store. The scan is against WCAG 2.1 AA, which is the same standard EN 301 549 points to, so it is not tied to one country. Whether any particular law applies to a given shop depends on its size and where it sells, and that is a question for the shop, not for us.
One thing we learned scanning real shops: most of what we find comes from the theme rather than from anything the owner wrote. That is worth knowing before you pay us, because it changes who has to do the work.
Scandiary's answer:
It started as a scan of ten real EU shops, five pages each, to find out whether the problem was real. Nine of the ten had violations. One was genuinely clean, and that mattered more than the nine: a tool that finds something everywhere is not sensitive, it is useless.
The scanner was wrong at first. A redirect made it treat a site's own links as external, so it scanned a single page and reported nothing. That defect was found by pointing it at real websites, not by the test suite, and it is written up on our research page instead of being quietly removed.
Running a scan once tells you almost nothing. Running the same scan every week and keeping the dates is what turns it into evidence.
Scandiary's answer:
Node.js, Puppeteer and axe-core for the scanner. The visitor-facing site is plain HTML and CSS with no JavaScript at all — our own Content-Security-Policy is script-src 'none'. Reports are generated as static HTML and delivered by email through Resend. Hosting is Vercel, and the scan history is stored in a private Git repository rather than a database.
Scandiary's answer:
If you already have a developer and a test suite, tools like axe DevTools or BrowserStack will serve you better. They are built for that workflow, and we use the same engine underneath anyway.
Scandiary is for the shop owner who has neither. Five pages are free every Monday and the free plan is not a trial. $12 a month adds where every problem sits — each affected element with its CSS selector and the page it is on, up to 25 per issue — and twenty pages instead of five. There is nothing to install, no account, and no script added to your site.
The other difference is what we do not sell. There is no widget added to your pages, and no report we send will tell you that you passed. A scan is evidence of what a machine could see on one date. We write that inside the report itself, not in the small print.
Based on our record, CrossBrowserTesting seems to be more popular. It has been mentiond 6 times since March 2021. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.
Yeah I moved on pretty quick from browserstack, but it seems to be the most popular. I've tried crossbrowsertesting.com but at the moment I really like app.lambdatest.com. Source: almost 4 years ago
Https://geizhals.de/ - this is a german site but the UI is nice and you can find a lot of stuff. Https://www.gsmarena.com/search.php3? - a phone search site. When I was at https://crossbrowsertesting.com we used this site a lot Https://www.howacarworks.com/ - how a car works Https://www.mcmaster.com/ - the UI here is so nice. Those illustrations Https://ciechanow.ski/mechanical-watch/ - how does a mechanical... - Source: dev.to / about 4 years ago
Fortunately we don’t need to install, nor configure, any other tools, unless maybe some fancy reporters, but for now we can get everything we need in terms of end-to-end automated testing out of Nightwatch. Besides Chrome, Nightwatch has built-in support for all major browsers, including Firefox, Edge, and Safari, all thanks to its integration with the W3C Webdriver API and Selenium. It also allows you to use... - Source: dev.to / over 4 years ago
Crossbrowsertesting.com - Manual, Visual, and Selenium Browser Testing in the cloud - free for Open Source. - Source: dev.to / about 5 years ago
Professionally, I do basically the same for dev testing. We also have various devices on different platforms/versions in the office when needed, and our QA team primarily uses Cross Browser Testing Tool. If I need to check something specific, I usually use CBT. Source: over 5 years ago
Sauce Labs - Test mobile or web apps instantly across 700+ browser/OS/device platform combinations - without infrastructure setup.
accessiBe - Making websites accessible to people with disabilities
BrowserStack - BrowserStack is a software testing platform for developers to comprehensively test websites and mobile applications for quality.
UserWay - Accessibility isn’t just “compliance.” - It’s revenue, brand loyalty, and better UX.
browserling - Live interactive cross-browser testing from your browser.
Siteimprove - Consider the Siteimprove Intelligence Platform the newest member of your team.