Find More Bugs
See more, find more.
Evinced algorithms can see important accessibility problems that are invisible to other automated solutions. That’s because those solutions are syntax-checkers: they read code, and look for problems in the code based on a set of rules. This works for some accessibility problems, but usually for small ones—like, say, a missing alt attribute in an <img> tag. But finding critical problems that prevent a user from using your site or app requires true understanding of how the code would be viewed by many different kinds of users. In the past, that sort of sleuthing required a manual audit. But not anymore. Consider these examples of Evinced in action:
- Undeclared controls
- Inaccessible controls
- Poor contrast
- Poor focus indication
The Problem
The button below, which isn’t declared as a button, won’t work with screen reader software.
The Evinced Difference
Evinced reports 2 problems, because we understand the intent of the element even if it isn’t properly declared.
19 times more
In every head to head comparison we’ve done for customers, we find way more critical accessibility bugs than traditional solutions like Axe, Lighthouse, and the rest. In fact, in a recent study of thirty major company websites, we found 19X more critical issues on average. That’s not a typo!
Critical issues keep some people from using your site or app. Why not find those bugs sooner rather than later?
"We’ve seen Evinced discover as much as 10x more critical accessibility issues than we were previously finding through automated testing alone."
More ways we find more bugs
DOM Mutations
Most accessibility tools analyze a single page in its initial state.
But things happen on web pages as users make their way through them. Buttons get clicked, tabs get indicated, divs get dropped, and slider elements get selected. Each of these interactions changes what a user would experience on the page or screen, and, on web pages, they are changes in the page’s DOM -- its Document Object Model.
Typical accessibility tools can’t scan all these different permutations of each web page. But Evinced can.
User Flows
Not only do web pages and apps change based on what the user does on THIS screen, they can also be different based on what the user did on the screen BEFORE. Ordinary accessibility solutions have no way to handle this, because they have a static view of each screen.
But because Evinced has already built special machine learning and computer vision algorithms that can see UI elements in much the way a sighted person would, we can use those same algorithms to model all the possible paths a user might take through a site or app. And then find the accessibility roadblocks in their way. So you (or your users) don’t have to.
Single Page Apps
What goes for User Flows counts double for
Single Page Apps. These standalone web applications, often built with Javascript, are entirely dynamic and don’t work like traditional web pages, which can only update when you reload the page. Instead, they handle that themselves, along with navigation between pages, focus and scroll position.
Sound familiar? That’s because many of your favorite websites are SPAs -- from Facebook to Gmail.
Traditional accessibility tools simply can’t cope with SPAs and all their permutations. But Evinced can.