Website accessibility testing
Find Common Website Accessibility Barriers
Some visitors use a keyboard, a screen reader or a magnifier to get around your site. Provelex checks each page it visits against automated accessibility rules, and explains each problem in a plain sentence with the people it affects.
How it works
Provelex runs axe-core, a widely used open-source accessibility rules engine, inside the browser on each page. The rules are tagged against WCAG levels A and AA, and each finding states which level it relates to. axe reports in developer language, so Provelex translates each result into what is wrong and what it means for the people using your site.
Examples of what is reported
| Finding | Who it affects |
|---|---|
| Images with no text alternative | People using a screen reader hear nothing useful, or a file name |
| Low contrast between text and background | People with low vision, and anyone reading in bright light |
| Form fields with no label | People using a screen reader do not know what to type |
| Buttons and links with no accessible name | People using a screen reader hear only “button” or “link” |
| Missing page language or document title | Screen readers may use the wrong pronunciation, and browser tabs have no useful name |
| Controls too small to tap | People with limited dexterity. See mobile testing for this check |
| Zooming disabled on phones | People who need to enlarge the text |
What a result does not mean
Provelex does not certify conformance with WCAG, or with any accessibility law. If you need an accessibility statement or must meet a legal requirement, use these results as a starting list and have the site reviewed by a specialist, ideally with people who use assistive technology.
Where to start
- Fix the problems repeated across every page first, such as those in a shared menu or footer. One change clears many findings.
- Then fix forms, because a person who cannot complete a form cannot become a customer.
- Try your main journey using only the keyboard. It takes a few minutes and often reveals problems no tool can find.
- Run another assessment to confirm what has changed.
Start with what can be checked automatically
The free Basic assessment runs the accessibility rules on up to three public pages, with no account.
Start an assessmentRelated pages
Need help with your account or a report? Email provelex@devsapience.com