[FluentAutocomplete]: Delete Country button does not have a descriptive accessible name
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- csharp, html
- Domain
- accessibility
Research direction
This is a FluentAutocomplete component bug in microsoft/fluentui-blazor: the remove-item button lacks a descriptive accessible name. Find the razor/C# component source under the component library (search for FluentAutocomplete and the delete/close button markup) and add an aria-label combining the action with the selected item's name, e.g. Remove India. Verify with the demo page's Autocomplete examples under a screen reader or an accessibility inspector.
Written by the indexing model from the issue text.
Description
Tags:
#A11yMAS; #MAS4.1.2; #TCS-BIC; #FluentUIBlazor_Web; #Win11; #DesktopWeb; #A11ySev2;CT_FluentUIBlazor_Web_Oct2026;
Test Environment:
Application Name: fluentui-blazor
OS: Windows 11 [Version 25H2 (OS Build 26200.8457)]
Edge: Version 148.0.3967.70 (Official build) (64-bit)
Test URL: https://fluentui-blazor.net/Nav
Repro Steps:
- Launch the URL: https://fluentui-blazor.net/Nav
- Search for FluentAutocomplete
- Turn on Narrator
- Verify the issue.
Actual Result:
When focus moves to the button used to delete a country, the screen reader does not announce the associated country name or identify the action as Delete or Remove. As a result, users cannot determine which country will be removed.
Expected Result:
The button should have a clear and descriptive accessible name that includes both the action and the associated country name, for example, “Remove India” or “Delete India.”
User Impact:
Screen reader users may be unable to determine the purpose of the button or which country will be removed. This can cause confusion and may result in users deleting the wrong country.
Attachment:
https://github.com/user-attachments/assets/d0083771-5157-4c6f-9971-9e21c37d5976
- Dominant language
- C#
- Stars
- 4.9k
- Forks
- 493
- Avg merge
- 23h 11m
- Merged PRs (30d)
- 80
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from microsoft/fluentui-blazor
-
a11y
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
microsoft/fluentui-blazor#5546 ·
Maintainers usually reply within 1 day
-
[FluentTabs]: Screen reader does not announce the accessible name and role for the Delete Tab buttonOpena11y
Difficulty 2/5 Half a day Newbie friendliness 72/100
microsoft/fluentui-blazor#5540 ·
Maintainers usually reply within 1 day
-
a11y
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
microsoft/fluentui-blazor#5539 ·
Maintainers usually reply within 1 day
-
a11y
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
microsoft/fluentui-blazor#5538 ·
Maintainers usually reply within 1 day
-
a11y
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
microsoft/fluentui-blazor#5533 ·
Maintainers usually reply within 1 day
All issues in microsoft/fluentui-blazor
Similar issues
-
bug P2
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
microsoft/SimpleL7Proxy#302 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
QuantConnect/Lean#9957 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 1 day