- When strong public validation is a procurement requirement prior to vendor engagement
- Public third-party review depth for this vendor is relatively limited in the sources reviewed; procurement teams that require broad, independent public reviews may prefer vendors with larger public review footprints.
- For simple, low-cost scanning of a small site
- Free or low-cost tools (axe-core, WAVE, Lighthouse, Pa11y) can provide sufficient coverage for many smaller sites and quick checks; these may be preferable if budget and scope are limited.
- When the primary need is manual audits and remediation services
- Organizations lacking engineering capacity or requiring human expert audits and assistive-technology testing may prefer vendors and consultancies that package auditing services alongside tooling.
- When procurement requires publicly available security certifications and data residency documentation
- The vendor did not publicly list SOC 2 / ISO certifications or explicit data residency options in the sources reviewed; procurement teams that require such documentation before vendor engagement should request it during vendor evaluation and consider alternatives if documentation is not provided.
- When the organization intends to publish benchmark comparisons broadly
- The vendor’s EULA includes restrictions on benchmarking and comparative analysis; buyers should review contractual terms if their procurement process requires publishing comparisons externally.
- Current limitations acknowledged by the vendor
- The vendor acknowledges limits of automation and the continued need for manual audits in certain contexts.
- Features on the roadmap (not yet available)
- A consolidated public roadmap document was not found in the sources reviewed; specific roadmap items are referenced across vendor posts and updates.
- Scale limitations
- The vendor positions the product for large-scale scanning and frequent change, but buyers should validate performance at scale in a proof-of-concept (PoC) for very large sites or high-frequency scanning requirements.
- Security or compliance gaps
- Public security certifications were not found; buyers should treat certification status as unknown until the vendor provides evidence under procurement processes.
- Technical debt or architectural limitations mentioned in reviews
- Community reports contain isolated bug reports (for example, issues handling certain attribute classes); buyers should validate behavior against their applications during a PoC.
- API limitations or integration constraints
- Public documentation does not fully describe all API or integration edge cases. Buyers should perform hands-on testing for authentication flows, single-page application behaviors, shadow DOM/iFrame handling, and mobile platform coverage.