Loading…
Why scanners are not enough
Automated scanners are a useful baseline, and the platform keeps one. They are also structurally unable to evaluate the barriers that most affect disabled users.
Verassa evidence protocol
Evidence
01Screenshot, DOM, replay, and axe baseline captured before decisions.
Judgment
02Reviewer route, rationale, and owner stay attached to lower-confidence work.
Verification
03Re-scan records and disclaimers travel with reportable outputs.
Presence versus quality
A scanner can confirm that an image carries an alt attribute, that a control is a button, that a heading exists. These are presence checks — is the attribute there. They are real and worth doing, which is why the platform keeps an automated baseline layer.
But presence is not quality. Alt text can be present and meaningless. A button can exist and be unreachable by keyboard. A heading can be there and be the wrong level. The barriers that stop a disabled person from finishing a task usually live in that gap.
The gap
A scanner can see that elements are focusable. It cannot tell you whether a real keyboard path exists through a multi-step task, or whether focus ever gets trapped.
A scanner sees that an alt attribute is present. Whether the text conveys what the image conveys, in context, is a judgment a scanner cannot make.
An ARIA role can be present and wrong. Whether a custom widget behaves the way its role promises takes interaction to find out.
Dialogs, live regions, and content that updates after load are only accessible if the change is announced. A static scan does not exercise them.
The barriers that matter most — checkout, account settings, dashboards — sit behind a sign-in a scanner usually never reaches.
Whether an error is identified in text, tied programmatically to its field, and explained well enough to act on is a quality question, not a presence one.
What closes the gap
The platform runs diagnostic agents that interact with a page the way a person would — moving keyboard focus, opening dialogs, submitting forms — and captures the evidence of what happened. A qualified reviewer then confirms or dismisses each finding.
That is the difference between a list of attributes and an audit: an evaluation of quality, backed by evidence you can inspect, checked by a human before anyone relies on it.
A demo runs the agents on a site you choose and walks through what they captured.