Alternatives to TPGi
Other Web accessibility vendors we measure, sorted by how much they publish that TPGi does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 22 that differ from TPGi on at least one criterion we measured for both. Public transparency score, not a product or security rating.
TPGi has 12 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, Public pricing, Certifications named, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “publishes and TPGi does not” is the one that closes them.
| Vendor | Score | Publishes, and TPGi does not | TPGi publishes, and they do not | |
|---|---|---|---|---|
| accessiBeaccessibe.com | 48/100 | 5 Data processing agreement, Data location stated, Public pricing, +2 | nothing | Compare |
| A11yWatcha11ywatch.com | 39/100 | 4 Data location stated, Public pricing, HTTPS enforced with HSTS, +1 | nothing | Compare |
| Evincedevinced.com | 35/100 | 4 Data location stated, Status page with history, HTTPS enforced with HSTS, +1 | nothing | Compare |
| Fablemakeitfable.com | 30/100 | 4 Data location stated, Public pricing, Certifications named, +1 | nothing | Compare |
| AccessiWayaccessiway.com | 30/100 | 3 Data location stated, Public pricing, HTTPS enforced with HSTS | nothing | Compare |
| Dequedeque.com | 26/100 | 3 Data location stated, Status page with history, Certifications named | nothing | Compare |
| Eye-Ableeye-able.com | 26/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | nothing | Compare |
| Siteimprovesiteimprove.com | 22/100 | 3 Status page with history, HTTPS enforced with HSTS, Named privacy contact | nothing | Compare |
| Accessibility Insightsaccessibilityinsights.io | 17/100 | 2 HTTPS enforced with HSTS, No third-party tracking before consent | nothing | Compare |
| Pope Techpope.tech | 17/100 | 2 Public pricing, HTTPS enforced with HSTS | nothing | Compare |
| Monsidomonsido.com | 13/100 | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | nothing | Compare |
| Adallyadally.com | 13/100 | 1 Data location stated | nothing | 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.