microsoft / microsoft/BotFramework-WebChat
Suggested actions to become a composite component with a single TAB to go in/out
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 1.8k
- Forks
- 1.6k
- Avg merge
- 22h 58m
- Merged PRs (30d)
- 2
Description
Feature Request
While we are working on navigable transcript, aria-activedescendant really shines.
We should also move suggested actions to use the aria-activedescendant or roving tab index to make things easier to select thru TAB keys.
The whole suggested actions container should be a single TAB. And for buttons inside, they should not need to be tabbable, but interactable using arrow keys. Similar to how auto-completion box is done.
[feature-request]
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the suggested actions container and comparing its keyboard behavior with the autocomplete box. Review the existing navigable transcript work involving aria-activedescendant or roving tabindex. Done means the container is entered and exited with one TAB stop, while its buttons are selectable with arrow keys without individual TAB stops.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- accessibility, frontend, web-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100