1. Automated testing has limits

AccessiSight tests pages automatically, in a real browser. Automated tools can only check part of what accessibility standards such as WCAG require. Many requirements need a person to judge them, for example whether alternative text describes an image well, whether captions are accurate, or whether a page makes sense with a screen reader.

A clean scan does not mean a site is accessible or conforms to a standard. It means the automated checks found no problems on the pages and states that were tested.
A scan can miss real problems, and it can report something that turns out not to be a problem once a person looks at it. Findings marked "needs review" or given medium or low confidence should always be checked by hand.
Results cover only the pages, screen sizes and interface states that were scanned, at the time they were scanned. Sites change, so results can go out of date.
Scores (including the accessibility score and the WCAG 3 preview score) are our own summary of the automated results. They are not an official rating from W3C or from any regulator.

2. Laws and standards information

The laws, standards, deadlines and WCAG versions shown in the app, on the Standards page and in our guides are a summary for general information. We check them against official sources and review them regularly, but laws change and how they apply depends on your organisation, sector and country. The official text of a law always takes precedence over our summary. Choosing a law in a compliance profile only changes which automated checks are shown; it does not show that a site meets that law.

3. VPAT / ACR and accessibility statements

VPATs (Accessibility Conformance Reports) and accessibility statements generated by AccessiSight are drafts based on automated results. Criteria that cannot be tested automatically are marked "Not Evaluated". Where a criterion shows "Supports" from automated testing alone, it means the automated checks found no known defects, not that a person has fully tested it; a manual audit you record in the app is used instead where you have done one. Before you publish or sign one, or send it to a customer or regulator, a person who has tested the product should review and complete it. You are responsible for what a published report or statement says.

4. Smart Fix and code suggestions

Fix suggestions, whether written from our templates or by an AI model you connect, are a starting point. They are based only on the code the scanner saw and cannot know the rest of your application. Review each change, test it in your own environment and with assistive technology, and re-scan before relying on it.

5. Not legal advice

Nothing AccessiSight produces is legal advice, a legal opinion, a certification or a guarantee that a website, app or document complies with any law, or that it will not face a complaint or lawsuit. For advice about your own legal obligations, talk to a qualified lawyer in your jurisdiction.

6. Terms of Service

This page explains in plain words what our Terms of Service already say, mainly in section 3 (Not Legal Advice), section 11 (Disclaimer of Warranties) and section 12 (Limitation of Liability). If the two ever differ, the Terms of Service apply. Questions: accessisight@gmail.com.