01Our Commitment
Watch Safe runs a public registry. Someone checking whether a watch was reported stolen before they buy it should be able to do that with whatever hardware and software they already use. We build toward the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA. When we find an accessibility barrier we file it as a bug, which means it competes for priority with everything else that is broken rather than waiting on a roadmap.
02Where We Actually Stand
2.1 We have not completed a third-party conformance audit, so we do not claim that Watch Safe fully conforms to WCAG 2.1 Level AA. Telling you where we actually are is worth more to you than a conformance badge we have not earned.
2.2 What we do build for: semantic HTML structure, labelled form fields, text alternatives for meaningful images, a declared page language, and interface states that are announced to screen readers rather than conveyed by color alone.
2.3 As of 30 July 2026, every public page passes automated WCAG 2.1 Level A and AA testing with no reported violations. Automated tools reach only about a third of the criteria, so treat that as a floor rather than a conformance claim. The manual review, which covers keyboard operation, focus order, and page zoom, is still outstanding, and we will update this statement when it is done.
03Known Limitations
3.1 Interactive map. The authenticator locator draws on a third-party mapping component whose pan and zoom controls may not be operable by keyboard or adequately described to screen readers. If you cannot use the map, contact us and we will identify the nearest authenticator for you directly.
3.2 Upload steps. Some steps ask you to upload a file, such as a police report. If an upload interface does not work for you, send the file to us by email instead and we will complete the step on your behalf.
3.3 Third-party components. Payment, sign-in, and mapping interfaces are supplied by outside vendors, and we do not control their markup. We do choose vendors partly on accessibility, and we raise defects with them when we find them.
04Telling Us About a Barrier
4.1 Email support@watchsafe.io with the subject line "Accessibility". Tell us the page, what you were trying to do, and the browser and assistive technology you were using if you know them. Any detail helps, and a report with none of that is still worth sending.
4.2 We aim to acknowledge accessibility reports within five business days. If a fix will take longer than that, we will tell you what we are doing and give you a way to finish what you came to do in the meantime.
05Getting It Done Another Way
If any part of Watch Safe blocks you, we will do it with you. That covers looking up a serial number, filing a stolen report, reaching an authenticator, and anything in an account you own. Ask at support@watchsafe.io. There is no separate process to apply for and nothing to prove first.
06Keeping This Current
We review this statement when the site changes materially and at least once a year. The version and effective date at the top tell you which review you are reading.