Alternatives to A11yWatch
Other Web accessibility vendors we measure, sorted by how much they publish that A11yWatch does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 25 that differ from A11yWatch on at least one criterion we measured for both. Public transparency score, not a product or security rating.
A11yWatch has 8 gaps in what we could measure: Data processing agreement, Subprocessor list, Status page with history, Certifications named, Uptime SLA with a figure, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “publishes and A11yWatch does not” is the one that closes them.
| Vendor | Score | Publishes, and A11yWatch does not | A11yWatch publishes, and they do not | |
|---|---|---|---|---|
| accessiBeaccessibe.com | 48/100 | 3 Data processing agreement, Certifications named, Notice before subprocessors change | 2 HTTPS enforced with HSTS, No third-party tracking before consent | Compare |
| Evincedevinced.com | 35/100 | 2 Status page with history, Named privacy contact | 2 Public pricing, No third-party tracking before consent | Compare |
| Fablemakeitfable.com | 30/100 | 2 Certifications named, Named privacy contact | 2 HTTPS enforced with HSTS, No third-party tracking before consent | Compare |
| Dequedeque.com | 26/100 | 2 Status page with history, Certifications named | 3 Public pricing, HTTPS enforced with HSTS, No third-party tracking before consent | Compare |
| Siteimprovesiteimprove.com | 22/100 | 2 Status page with history, Named privacy contact | 3 Data location stated, Public pricing, No third-party tracking before consent | Compare |
| Eye-Ableeye-able.com | 26/100 | 1 Named privacy contact | 2 Public pricing, No third-party tracking before consent | Compare |
| Monsidomonsido.com | 13/100 | 1 security.txt (RFC 9116) | 3 Data location stated, Public pricing, No third-party tracking before consent | Compare |
| Level Accesslevelaccess.com | 4/100 | 1 Named privacy contact | 4 Data location stated, Public pricing, HTTPS enforced with HSTS, +1 | Compare |
| Silktidesilktide.com | 4/100 | 1 security.txt (RFC 9116) | 4 Data location stated, Public pricing, HTTPS enforced with HSTS, +1 | Compare |
| AccessiWayaccessiway.com | 30/100 | nothing we found there and not here | 1 No third-party tracking before consent | Compare |
| Accessibility Insightsaccessibilityinsights.io | 17/100 | nothing we found there and not here | 2 Data location stated, Public pricing | Compare |
| Pope Techpope.tech | 17/100 | nothing we found there and not here | 2 Data location stated, No third-party tracking before consent | Compare |
Only criteria we could measure for both are counted. Where we could measure one and not the other, the row is silent: that would be a statement about our measurement, not about either vendor. Every single result with its source is on the two profiles.