Fetches one page from our server and runs a quick automated check of its HTML for a few common accessibility problems: images without alt text, form fields without labels, skipped heading levels, a missing page language and low color contrast in inline styles. It is a quick check, not an accessibility audit, and it does not say a page is accessible or meets WCAG.
How to use it
Enter the address of the page you want a first look at. You can leave out https://.
- Type or paste the address of the page and press Run check.
- Read the note at the top of the result about what the check can and cannot tell you.
- Work through the findings, starting with the critical ones. Each one says what to change.
- Change the page, then run the check again. When the findings are gone, test by keyboard and with a screen reader.
How Reavlo tests this
A quick check, not an accessibility audit. This tool reads the HTML of one page and looks for a few common problems. It does not run the page, use a screen reader, or test by keyboard, and it covers only part of what WCAG 2.2 asks for. Finding no issue does not mean the page is accessible or meets WCAG. It is not a certification and not a legal assessment, and there is no score. For that, use a manual audit with real assistive technology.
This tool runs on our server, because a browser cannot read another site's page. Nothing about the request is stored or logged: not the address, not the page.
Fetching. One request to the page, with up to 3 redirects, a size cap and a time limit. Addresses that point to private or internal networks are refused before any connection is made. The HTML is read as the server sent it; JavaScript is not run.
Language. The lang attribute on the html element must be present and not empty.
Images. Every img must have an alt attribute (W3C WAI images tutorial). An empty alt="" is accepted, because it marks a decorative image. The tool cannot tell whether the text of an alt attribute is a good description.
Form fields. Every field a person fills in (not hidden fields or buttons) must have a label linked by for and id or wrapped around it, or an aria-label, aria-labelledby or title (W3C WAI labeling controls). The tool does not check that the label is clear.
Headings. The page should have one h1, and a heading should not be more than one level deeper than the one before it (W3C WAI headings).
Contrast. Only text whose color and background color are both written as hex values in the same inline style attribute is measured, using the WCAG contrast ratio: at least 4.5:1, or 3:1 for large text (24px, or 18.66px and bold). Colors set in style sheets, named colors, gradients, images and inherited backgrounds are not measured, so most contrast problems on a typical page are not seen. The number of pairs measured is shown.
Limits. The tool cannot judge keyboard use, focus order, link text, error messages, captions, motion, zoom or anything that depends on how the page looks or behaves. A page with no findings here can still be hard or impossible to use for some people.
Questions
Does a result with no findings mean my page is accessible?
No. The check covers a few things that can be read from the HTML and none of what needs a person using the page. Treat it as a first pass.
Can I use this to show that my site meets WCAG or the law?
No. It is not a certification and not a legal assessment. Conformance needs a manual audit against the standard that applies to you.
Why were so few color pairs measured?
Only inline styles with both colors as hex values are read. Most sites set colors in style sheets, which this tool does not read, so a low count is normal. Check contrast for your main colors with the brand color contrast matrix.
Is the address I enter stored?
No. The address goes to our server only to fetch the page, and neither it nor the page is stored or written to a log. Analytics records only that the tool ran, never the address.
What should I test next?
Use the page with only a keyboard, then with a screen reader such as NVDA or VoiceOver, and zoom to 200%. The W3C Web Accessibility Initiative has tutorials for each.