Your build starts here
Replace bracketed details with your own goal, context, and checks. Keep the first build small enough to inspect.
Investigate whether [large collection] needs virtualization using [representative record count and device]. Establish the current scrolling and interaction baseline. Preserve stable record identities independently of rendered positions. Choose appropriate list, table, or grid semantics for the actual behavior rather than adding a grid role solely because rows are visible.
If virtualization is justified, define how keyboard navigation reaches an item not currently rendered, how focus remains valid during recycling, and how total and positional context are communicated where the chosen semantics require them. Keep selection and edits attached to record IDs. Provide [pagination or another usable fallback] if needed for the supported experience.
Verify scrolling, filtering, reorder, an edited row leaving the viewport, a focused row being removed, and navigation near the end. Compare performance and usability under the same scenario and report remaining screen-reader coverage.Make this prompt yours
ARIA row counts belong to applicable table/grid structures; do not apply them indiscriminately to every visual list.
You might also hear
- virtualized list
- windowing
- recycled rows
- aria rowcount
- keyboard scrolling
The docs behind it
These references explain the underlying concepts and APIs. The prompt templates and project plans are original examples to adapt to your own setup.
Research sources reviewed .
Editorial review · October 28, 2026
Supported: Original virtualization investigation. WAI positional metadata applies to appropriate table/grid structures, as the note says; focus, identity, fallback, and performance cases are proposed implementation tests.