From bf33085e1841f35c29dca396f0b2119bbb2c09eb Mon Sep 17 00:00:00 2001 From: Muhammad Ubaid Raza Date: Tue, 24 Feb 2026 04:21:41 +0500 Subject: [PATCH] docs(agent): prefer accessibility_snapshot for element identification Updated agent guidelines to specify the use of accessibility_snapshot over visual screenshots for element identification. Accessibility snapshots provide structured DOM/ARIA data, which is more reliable for browser automation than pixel-based visual analysis. --- agents/gem-browser-tester.agent.md | 1 + 1 file changed, 1 insertion(+) diff --git a/agents/gem-browser-tester.agent.md b/agents/gem-browser-tester.agent.md index 4a5bb551..945f5f57 100644 --- a/agents/gem-browser-tester.agent.md +++ b/agents/gem-browser-tester.agent.md @@ -30,6 +30,7 @@ Browser automation, UI/UX and Accessibility (WCAG) auditing, Performance profili - Think-Before-Action: Validate logic and simulate expected outcomes via an internal block before any tool execution or final response; verify pathing, dependencies, and constraints to ensure "one-shot" success. - Context-efficient file/ tool output reading: prefer semantic search, file outlines, and targeted line-range reads; limit to 200 lines per read - Follow Observation-First loop (Navigate → Snapshot → Action). +- Prefer accessibility_snapshot over visual screenshots for element identification - accessibility snapshots provide structured DOM/ARIA data that's more reliable for automation than pixel-based visual analysis. - Use reference_cache for WCAG standards when performing accessibility audits. - Evidence storage (in case of failures): directory structure docs/plan/{plan_id}/evidence/{task_id}/ with subfolders screenshots/, logs/, network/. Files named by timestamp and scenario. - Use UIDs from take_snapshot; avoid raw CSS/XPath.