WCAG Watchdog

Accessibility checks for every release

Can everyone read your site?

WCAG Watchdog gives your site an eye test after every release. You see what got worse for people with low vision or a screen reader, and the exact element to fix.

Check a color pair
  • No widget on your site
  • Your team fixes the real code
  • Honest about what machines miss
Eye test for shop.northwind.exampleRelease 2.15

    Free tool

    Check a color pair.

    Pick a text color and a background. You get the contrast ratio, what it passes, and the closest color that would pass. Your pair also shows on the eye chart above.

    Text color
    Background color

    Large text looks like this

    Body text at 16 pixels, the size most of your page uses.

    Add to cart
    4.54:1contrast ratio

      Screen readers

      Hear what a blind visitor hears.

      The same page, read out by a screen reader, before and after release 2.15. One button lost its name, a heading jumped, and one field got its label back.

      Release 2.14

      Pricing page, read top to bottom

        Release 2.15

        Same page, one release later

          Contrast problems are not heard, they are seen. The eye chart shows those.

          Every release

          Each release, compared with the last one.

          You do not get a list of 400 old warnings. You get what this release broke and what it fixed.

          Known problemsNew in this release

          Release 2.15, deployed 14 Nov

          • NewCart button has no name. Screen readers say only "button".
          • NewPrice note is too faint: 2.41:1, needs 3:1.
          • NewHeading jumps from level 1 to level 4.
          • FixedEmail field has a label again.

          Accessibility breaks one release at a time. WCAG Watchdog tells you the same day.

          Honest scope

          Machines find about a third. We say so.

          No tool makes a site compliant on its own. We check what a machine can check, and list what still needs a person.

          Our automated checks
          Your keyboard and screen reader tests

          Automated checks cover about 30 to 40 percent of WCAG 2.2 AA. Every report says which part is which.

          What our checks catch

          • Text and buttons with too little contrast
          • Buttons, links and images without a name
          • Form fields without a label
          • Heading order and page language
          • Focus outlines that were removed

          What still needs a person

          • Does the page make sense when read aloud?
          • Can you finish checkout with only a keyboard?
          • Do videos have captions that match?
          • Are error messages clear enough to fix?

          How it works

          Connect once. Every release gets its eye test.

          1. 1

            Add your site

            List the pages that matter, including staging pages behind a login.

          2. 2

            We test every release

            After each deploy, a real browser opens your pages and runs the checks.

          3. 3

            You see what got worse

            Only new problems, each with the element and the fix. Sent to GitHub, Slack or email.

          Pricing

          Pay for the sites you test.

          Start free with one page.

          Free

          Try it on one page.

          $0/ month

          • 1 page test
          • Shareable report
          • List of what needs a person

          Starter

          For one product site.

          $39/ month

          • 1 site
          • 100 pages a week
          • Alerts on new problems

          Pro Popular

          For teams that ship every week.

          $119/ month

          • 5 sites, 1,000 pages a test
          • Staging pages behind a login
          • VPAT report history

          Agency

          For agencies and their clients.

          $299/ month

          • 25 sites, 5,000 pages a month
          • A workspace per client
          • PDF reports for clients

          Every report says what automated checks cannot cover. No overlay widgets, no compliance badges.

          Questions

          What teams ask first.

          Will this make our site compliant?

          No tool can do that alone. Automated checks find about a third of WCAG problems. We show which parts still need keyboard and screen reader testing.

          Do you add a widget to our site?

          No. Overlay widgets do not fix your code. We find the problems so your team can fix them where they are.

          Can it test pages behind a login?

          Yes, on Pro and Agency. You give us a test account or headers for your staging site.

          What if a site blocks bots?

          We mark the page as blocked and never try to get around it. You can allow our tester on your staging site instead.

          When can we start?

          WCAG Watchdog is not open yet. Join the list and we email you when it opens. The free plan stays free.

          Book your site's first eye test.

          Join the early access list. We email you when it opens.

          Get early access

          WCAG Watchdog is not open yet. We email you when it opens. Joining costs nothing.

          We use your email only to contact you about WCAG Watchdog. Privacy notice