Skip to content

feat: new conversation ai component#6170

Open
TarunAdobe wants to merge 23 commits intomainfrom
ttomar/conversation-ai
Open

feat: new conversation ai component#6170
TarunAdobe wants to merge 23 commits intomainfrom
ttomar/conversation-ai

Conversation

@TarunAdobe
Copy link
Copy Markdown
Contributor

Description

Motivation and context

Related issue(s)

  • fixes [Issue Number]

Screenshots (if appropriate)


Author's checklist

  • I have read the CONTRIBUTING and PULL_REQUESTS documents.
  • I have reviewed at the Accessibility Practices for this feature, see: Aria Practices
  • I have added automated tests to cover my changes.
  • I have included a well-written changeset if my change needs to be published.
  • I have included updated documentation if my change required it.

Reviewer's checklist

  • Includes a Github Issue with appropriate flag or Jira ticket number without a link
  • Includes thoughtfully written changeset if changes suggested include patch, minor, or major features
  • Automated tests cover all use cases and follow best practices for writing
  • Validated on all supported browsers
  • All VRTs are approved before the author can update Golden Hash

Manual review test cases

  • Descriptive Test Statement

    1. Go here
    2. Do this action
    3. Expect this result
  • Descriptive Test Statement

    1. Go here
    2. Do this action
    3. Expect this result

Device review

  • Did it pass in Desktop?
  • Did it pass in (emulated) Mobile?
  • Did it pass in (emulated) iPad?

Accessibility testing checklist

Required: Complete each applicable item and document your testing steps (replace the placeholders with your component-specific instructions).

  • Keyboard (required — document steps below) — What to test for: Focus order is logical; Tab reaches the component and all interactive descendants; Enter/Space activate where appropriate; arrow keys work for tabs, menus, sliders, etc.; no focus traps; Escape dismisses when applicable; focus indicator is visible.

    1. Go here
    2. Do this action
    3. Expect this result
  • Screen reader (required — document steps below) — What to test for: Role and name are announced correctly; state changes (e.g. expanded, selected) are announced; labels and relationships are clear; no unnecessary or duplicate announcements.

    1. Go here
    2. Do this action
    3. Expect this result

@changeset-bot
Copy link
Copy Markdown

changeset-bot bot commented Apr 13, 2026

⚠️ No Changeset found

Latest commit: f07bd52

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@TarunAdobe TarunAdobe marked this pull request as ready for review April 13, 2026 11:28
@TarunAdobe TarunAdobe requested a review from a team as a code owner April 13, 2026 11:28
@TarunAdobe TarunAdobe added the Status:WIP PR is a work in progress or draft label Apr 13, 2026
@aramos-adobe aramos-adobe self-assigned this Apr 13, 2026
@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Apr 14, 2026

📚 Branch Preview Links

🔍 First Generation Visual Regression Test Results

When a visual regression test fails (or has previously failed while working on this branch), its results can be found in the following URLs:

Deployed to Azure Blob Storage: pr-6170

If the changes are expected, update the current_golden_images_cache hash in the circleci config to accept the new images. Instructions are included in that file.
If the changes are unexpected, you can investigate the cause of the differences and update the code accordingly.

@TarunAdobe TarunAdobe force-pushed the ttomar/conversation-ai branch from efa98e1 to 38ba0ce Compare April 14, 2026 11:11
Copy link
Copy Markdown
Contributor

@nikkimk nikkimk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's chat about status and conversation turn accessibility.


// ──────────────────────────
// OPTIONS STORIES
// ──────────────────────────
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We need a behaviors section with examples to show how consumers use the event to change the status.

);
}

protected override render(): TemplateResult {
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd recommend using arrow key navigation here view the new focusgroup controller

Comment on lines +80 to +97
private _renderLoadingRow(label: string): TemplateResult {
return html`
<div class="swc-ResponseStatus-row">
<span
class="swc-ResponseStatus-loadingSlot"
role="status"
aria-label=${label}
>
<swc-progress-circle
size="s"
indeterminate
aria-hidden="true"
></swc-progress-circle>
</span>
<span class="swc-ResponseStatus-label">${label}</span>
</div>
`;
}
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The screenreader reads the label twic. I recommend the following

Suggested change
private _renderLoadingRow(label: string): TemplateResult {
return html`
<div class="swc-ResponseStatus-row">
<span
class="swc-ResponseStatus-loadingSlot"
role="status"
aria-label=${label}
>
<swc-progress-circle
size="s"
indeterminate
aria-hidden="true"
></swc-progress-circle>
</span>
<span class="swc-ResponseStatus-label">${label}</span>
</div>
`;
}
private _renderLoadingRow(label: string): TemplateResult {
return html`
<div class="swc-ResponseStatus-row">
<span
class="swc-ResponseStatus-loadingSlot"
role="status"
>
<swc-progress-circle
size="s"
indeterminate
aria-hidden="true"
></swc-progress-circle>
</span>
<span class="swc-ResponseStatus-label">${label}</span>
</div>
`;
}

`;
}

private _renderCompleteRow(label: string): TemplateResult {
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Completed status won't update the screenreader without being inside the status role. Let's talk through how we can implement this. Also see https://www.figma.com/design/42VzvpW262EAUbYsadO4e8/Loading-animation-discover for guidelines on loaders.


protected override render(): TemplateResult {
return html`
<div class="swc-ConversationTurn">
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sighted users can tell which turn is from the user and which one is from the AI. We need a way to communicate this to screenreaders as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Status:WIP PR is a work in progress or draft

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants