A website can look finished and still shut people out, and that means lost opportunity for you. Someone who doesn't use a mouse, who magnifies the page, who is colour-blind or sees colour a little differently. uses an assistive technology like a screen reader, navigational aide or magnifier, who doesn't hear audio or see video clearly, or experiences any number of ability limitations may not understand, complete a task or otherwise use web content as easily as you might think.

SiteScan gives you one place to see those problems, choose what to fix and when, so everyone can use your website with ease.

When you have worked through SiteScan, you can:

  • See which pages on your list have accessibility problems, and how serious they are.
  • Open the live page, find the affected code, and hand a clear bug to the person who will fix it.
  • Check image descriptions, and captions or transcripts for audio and video, in the same workspace.
  • Scan again after the website changes, so the list shows what is still open.
  • Download a PDF that shows the progress, for a manager or a report.

Automated checks find a lot, and they miss a lot. SiteScan keeps both: the bugs a scan finds, and the bugs your team adds after looking at the page. The rules behind the checks are the W3C Web Content Accessibility Guidelines (WCAG). When a bug names a rule and you want it in plain English, open the AccessUX Vault.

If you only want to try one public page, and you do not need an account, start with PageScan. When you are ready to watch a list of pages, choose a plan on SiteScan Plans and sign in.

Use the guide menu to move through setup, signed-in pages, health scores, bugs, images, multimedia, reports, and the Vault. Each page says which plans include that function.