Prefer accessible all-photos views for property photo review

This commit is contained in:
2026-03-27 13:15:06 -05:00
parent 90635bf8f2
commit c2ae79ccf0
2 changed files with 22 additions and 18 deletions

View File

@@ -127,20 +127,21 @@ Example:
npx tsx flow.ts --instruction 'go to https://search.fiorinis.com then type "pippo" then press enter then wait 2s'
```
### Gallery/lightbox workflows
### Gallery/lightbox and all-photos workflows
For real-estate listings and other image-heavy pages, prefer opening the gallery/lightbox explicitly and verifying that each navigation step produces a distinct image.
For real-estate listings and other image-heavy pages, prefer the most accessible all-photos view first.
Practical rules:
- Do not treat a listing page hero image, gallery collage, or modal landing view as full photo review.
- After opening the gallery, capture the first image, then use the actual in-gallery next control.
- Confirm the image changed before counting the next screenshot as reviewed.
- A scrollable all-photos page, expanded photo grid, or photo list is an acceptable source for condition review if it clearly exposes the listing images.
- Do not treat a listing page hero image, gallery collage preview, or modal landing view alone as full photo review.
- Only rely on next-arrow / slideshow traversal when the site does not provide an accessible all-photos view.
- If using a gallery, confirm the image changed before counting the next screenshot as reviewed.
- If a generic `Next` control exits the gallery or returns to the listing shell, stop and adjust the selector/interaction; do not claim the photos were reviewed.
- Blind `ArrowRight` presses are not reliable enough unless you have already verified that they advance the gallery on that site.
- For smaller listings, review all photos when practical; otherwise review enough distinct photos to cover kitchen, baths, living areas, bedrooms, exterior, and any waterfront/balcony/deck elements.
- If automation cannot reliably advance the gallery, say so explicitly in the final answer.
- If automation cannot reliably access enough photos, say so explicitly in the final answer.
Where possible, prefer specific controls over vague ones, for example a gallery-specific next-arrow button rather than a page-level `Next` button.
Where possible, prefer a sites explicit `See all photos` / `Show all photos` path over fragile modal navigation.
## Compatibility Aliases