[yihuiliao]

Closes

✅ Pull Request Checklist:

• Included link to corresponding React Spectrum GitHub Issue.
• Added/updated unit tests and storybook for this change (for new code or code which already has tests).
• Filled out test instructions.
• Updated documentation (if it already exists for this component).
• Looked at the Accessibility Practices for this feature - Aria Practices
• I understand every change in this PR and can explain why it's there.
• If AI-assisted, I followed our AI contribution guidance and pointed my assistant at AGENTS.md.

📝 Test Instructions:

🧢 Your Project:

[rspbot]

Build successful! 🎉

• View the storybook
• View the S2 storybook
• View the S2 docs
• View the React Aria docs

[rspbot]

Build successful! 🎉

• View the storybook
• View the S2 storybook
• View the S2 docs
• View the React Aria docs

[rspbot]

## API Changes

@react-spectrum/ai

/@react-spectrum/ai:AttachmentList

 AttachmentList <T> {
   aria-describedby?: string
   aria-details?: string
   aria-label?: string
   aria-labelledby?: string
   children?: ReactNode | (T) => ReactNode
   dependencies?: ReadonlyArray<any>
   disabledKeys?: Iterable<Key>
   id?: string
   items?: Iterable<T>
+  onAction?: (Key) => void
   onRemove?: (Set<Key>) => void
   slot?: string | null
   styles?: StyleString
 }

/@react-spectrum/ai:PromptFieldAttachmentList

 PromptFieldAttachmentList {
   aria-describedby?: string
   aria-details?: string
   aria-label?: string
   aria-labelledby?: string
   children?: (PromptFieldAttachment) => React.ReactNode
   dependencies?: ReadonlyArray<any>
   disabledKeys?: Iterable<Key>
   id?: string
   items?: Iterable<PromptFieldAttachment>
+  onAction?: (Key) => void
   onRemove?: (Set<Key>) => void
   slot?: string | null
   styles?: StyleString
 }

/@react-spectrum/ai:AttachmentListProps

 AttachmentListProps <T> {
   aria-describedby?: string
   aria-details?: string
   aria-label?: string
   aria-labelledby?: string
   children?: ReactNode | (T) => ReactNode
   dependencies?: ReadonlyArray<any>
   disabledKeys?: Iterable<Key>
   id?: string
   items?: Iterable<T>
+  onAction?: (Key) => void
   onRemove?: (Set<Key>) => void
   slot?: string | null
   styles?: StyleString
 }

/@react-spectrum/ai:PromptFieldAttachmentListProps

 PromptFieldAttachmentListProps {
   aria-describedby?: string
   aria-details?: string
   aria-label?: string
   aria-labelledby?: string
   children?: (PromptFieldAttachment) => React.ReactNode
   dependencies?: ReadonlyArray<any>
   disabledKeys?: Iterable<Key>
   id?: string
   items?: Iterable<PromptFieldAttachment>
+  onAction?: (Key) => void
   onRemove?: (Set<Key>) => void
   slot?: string | null
   styles?: StyleString
 }

---

[rspbot]

Agent Skills Changes

Modified (9)

• react-aria/agent-skills/index.json $\color{green}{+1}$ $\color{red}{-1}$
• react-aria/agent-skills/react-aria.tar.gz
• react-aria/agent-skills/react-aria/references/components/Separator/useSeparator.md $\color{green}{+1}$ $\color{red}{-1}$
• s2/agent-skills/index.json $\color{green}{+3}$ $\color{red}{-3}$
• s2/agent-skills/migrate-react-spectrum-v3-to-s2.tar.gz
• s2/agent-skills/react-spectrum-s2.tar.gz
• s2/agent-skills/react-spectrum-s2/references/guides/ai-components.md $\color{green}{+1}$ $\color{red}{-17}$
• s2/agent-skills/react-spectrum-s2/references/react-aria/components/Separator/useSeparator.md $\color{green}{+1}$ $\color{red}{-1}$
• s2/agent-skills/spectrum-audit.tar.gz

Install

React Spectrum S2:

npx skills add https://d1pzu54gtk2aed.cloudfront.net/pr/4653a298425bb81052c501561899fc08beb59c64/

React Aria:

npx skills add https://d5iwopk28bdhl.cloudfront.net/pr/4653a298425bb81052c501561899fc08beb59c64/

[nwidynski]

I see this is largely based on Devons exploration from the Carousel RFC. Just for your consideration, I may point out that Tab-based Carousels have a rather large accessibility challenge, that also remains unresolved here: how to handle focus(within) on slides if they are scrolled/swiped. Since this is for a Lightbox component, we should consider enforcing phrasing content only. There are similarities in principle to the ongoing work for "readonly" StepList.

[yihuiliao]

Yeah good point on how to handle focus within the slides if they are scrolled/swiped. I'll bring it up with the team and see what we want to do there.

Otherwise, this is supposed to be a pretty simple version of carousel. I don't think we'll have autoplay (at least in this version) so some of the accessibility concerns that were brought up for that use case won't be addressed here. And I don't think there are plans to support Virtualization for this specific component in the AI package. Perhaps that discussion will change if we bring this pattern into RAC.

I will definitely need to play around with the voice over announcements and see how that works with scrolling. It's not something I've tried yet so far.