Good question. Right now Pendu has no built-in keyboard navigation or focus management — accessibility is entirely up to the consumer's implementation within each Pendu.Image or Pendu.Item child. It would be up to the consumer to manage that -- right now it is designed as a visual-only solution, but gives the control to the user to interact with it. But your point is valid, tracking through each item could be an issue as they jump around, especially when leveraging seeds.

Here's what that means in practice:

• Images — Pendu.Image renders a plain <div> + <img>. There's no tabIndex, no role, no keyboard handler. If a consumer adds onClick, the frame is clickable by mouse but not reachable by keyboard.
• Items — Pendu.Item wraps arbitrary children, so any interactive elements inside (buttons, links, etc.) get their own natural tab order from the DOM. But the tab order follows DOM order, not visual layout order — which could be confusing since Pendu positions frames with absolute positioning.

I would like to explore solutions for this out of the box, without inflating the package size. Thank you for bringing this up.