Use Visual Accessors for Web Testing

Last reviewed: October 2, 2026

Use this article when web tests need visual matching because a stable DOM locator, accessibility locator, or text locator is not available.

What changed in this article

• Clarified visual accessors as a targeted fallback for web testing rather than the default locator strategy.
• Updated guidance around image boundaries, visual matching, UI drift, and maintenance review in current AIQ terminology.
• Added checks for viewport size, browser scaling, theme changes, crop quality, waits, and false-positive matches.

Validation workflow

1. Try stable DOM, accessibility, text, or attribute-based locators before adding a visual accessor.
2. Capture a tightly scoped image of the element or region and avoid broad screenshots that can match unrelated UI.
3. Replay on the target browser and viewport and review results after UI or theme changes.

Review note: This page now aligns web visual accessor guidance with the mobile visual accessor cleanup already completed.

Last updated: October 2, 2026

If you have feedback on this topic, contact documentation@appvance.ai.