microsoft / microsoft/BotFramework-WebChat

Indicator on suggested actions to show that the action will open a URL

Open
#3,833 4 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

backlog Bot Services customer-replied-to customer-reported feature-request
Dominant language
HTML
Stars
1.8k
Forks
1.6k
Avg merge
22h 58m
Merged PRs (30d)
2

Description

[Edit by @corinagum]
Although the original comment is using Adaptive Cards as a visual example, this need applies to BotBuilder's suggested actions as well, which would be an update inside of the Web Chat repo. The Adaptive Cards example needs to be requested with Adaptive Cards.

Suggested action example:
image

Related to #3817

Note: Does the role for this button need to be updated to role=link? (a11y requirements)

(original message below):


For the suggested actions for adaptive cards, I would like to indicate what type of action would be taken by clicking the button. For example for "Action.CardType", I would like to indicate on the button that this will take you to an external URL:

image

At the moment this is no possible as every button is rendered with the same CSS so there is no way to differentiate which type of button has been rendered.

Is it possible to include the action type as part of the CSS on the rendered button as shown below?

image

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing how BotBuilder suggested actions are rendered in the Web Chat repo and where their button CSS is defined. Check the related issue #3817 and the accessibility question about whether URL actions should use role=link. Done means URL-opening actions are visibly distinguishable from other suggested actions without changing the separate Adaptive Cards request.

Written by the indexing model from the issue text.

Assessment

Tech stack
css, html
Domain
accessibility, frontend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.