Transparency alternatives to accessiBe
Other Web accessibility vendors we measure, sorted by how much we found at them and not at accessiBe. This is a comparison of disclosure, not of features or fitness.
12 shown of 30 that differ from accessiBe on at least one criterion we measured for both. Public transparency score, not a product or security rating.
accessiBe has 7 gaps in what we could measure: Subprocessor list, Status page with history, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116), Named privacy contact. The column “Found there, not found at accessiBe” is the one that closes them.
| Vendor | Score | Found there, not found at accessiBe | Found at accessiBe, not found there | |
|---|---|---|---|---|
| Silktidesilktide.comSee also Transparency alternatives to Silktide | 57/100 | 4 Subprocessor list, Uptime SLA with a figure, HTTPS enforced with HSTS, +1 | 2 Data location stated, Public pricing | Compare |
| Evincedevinced.comSee also Transparency alternatives to Evinced | 35/100 | 3 Status page with history, HTTPS enforced with HSTS, Named privacy contact | 4 Data processing agreement, Public pricing, Certifications named, +1 | Compare |
| Siteimprovesiteimprove.comSee also Transparency alternatives to Siteimprove | 22/100 | 3 Status page with history, HTTPS enforced with HSTS, Named privacy contact | 5 Data processing agreement, Data location stated, Public pricing, +2 | Compare |
| UserWayuserway.orgSee also Transparency alternatives to UserWay | 43/100 | 2 HTTPS enforced with HSTS, Named privacy contact | 2 Data location stated, Certifications named | Compare |
| A11yWatcha11ywatch.comSee also Transparency alternatives to A11yWatch | 39/100 | 2 HTTPS enforced with HSTS, No third-party tracking before consent | 3 Data processing agreement, Certifications named, Notice before subprocessors change | Compare |
| Eye-Ableeye-able.comSee also Transparency alternatives to Eye-Able | 26/100 | 2 HTTPS enforced with HSTS, Named privacy contact | 4 Data processing agreement, Public pricing, Certifications named, +1 | Compare |
| Dequedeque.comSee also Transparency alternatives to Deque | 22/100 | 2 Status page with history, HTTPS enforced with HSTS | 4 Data processing agreement, Data location stated, Public pricing, +1 | Compare |
| Accessibility Insightsaccessibilityinsights.ioSee also Transparency alternatives to Accessibility Insights | 17/100 | 2 HTTPS enforced with HSTS, No third-party tracking before consent | 5 Data processing agreement, Data location stated, Public pricing, +2 | Compare |
| AccessiWayaccessiway.comSee also Transparency alternatives to AccessiWay | 33/100 | 1 HTTPS enforced with HSTS | 3 Data processing agreement, Certifications named, Notice before subprocessors change | Compare |
| Fablemakeitfable.comSee also Transparency alternatives to Fable | 30/100 | 1 Named privacy contact | 2 Data processing agreement, Notice before subprocessors change | Compare |
| Starkgetstark.coSee also Transparency alternatives to Stark | 22/100 | 1 HTTPS enforced with HSTS | 3 Data processing agreement, Data location stated, Notice before subprocessors change | Compare |
| Level Accesslevelaccess.comSee also Transparency alternatives to Level Access | 17/100 | 1 Named privacy contact | 4 Data location stated, Public pricing, Certifications named, +1 | 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.