[Android] Fix for IndicatorView Provides Correct TalkBack Accessibility Description #31775
Conversation
praveenkumarkarunanithi changed the title 
| Hey there @@praveenkumarkarunanithi! Thank you so much for your PR! Someone from the team will get assigned to your PR shortly and we'll get it reviewed. |
dotnet-policy-service bot added the partner/syncfusion 
| /azp run |
| Azure Pipelines successfully started running 3 pipeline(s). |
There was a problem hiding this comment.
Pull Request Overview
This PR fixes TalkBack accessibility support for IndicatorView on Android by providing meaningful accessibility descriptions for indicator items. Previously, TalkBack would either skip indicators or announce them generically as "button" without context.
- Adds proper accessibility configuration for indicator ImageViews with meaningful TalkBack announcements
- Implements custom accessibility delegate to prevent generic "button" announcements
- Includes device test to verify correct accessibility descriptions are provided
Reviewed Changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| src/Core/src/Platform/Android/MauiPageControl.cs | Adds accessibility support with custom delegate and dynamic content descriptions for indicator items |
| src/Controls/tests/DeviceTests/Elements/CarouselView/CarouselViewTests.Android.cs | Adds device test to verify TalkBack accessibility descriptions are correctly set |
| var contentDescription = isSelected | ||
| ? $"Item {itemNumber} of {totalItems}, selected" | ||
| : $"Item {itemNumber} of {totalItems}"; |
There was a problem hiding this comment.
The hardcoded strings 'Item', 'of', and 'selected' should be localized or made configurable to support internationalization and different accessibility preferences.
Copilot uses AI. Check for mistakes.
| | ||
| var firstIndicator = mauiPageControl.GetChildAt(0) as ImageView; | ||
| Assert.NotNull(firstIndicator); | ||
| Assert.Equal("Item 1 of 3, selected", firstIndicator.ContentDescription); |
There was a problem hiding this comment.
The test only verifies the first indicator's accessibility description. Consider adding assertions for non-selected indicators and testing accessibility state changes when the position changes to ensure complete coverage of the accessibility functionality.
Copilot uses AI. Check for mistakes.
Root Cause
On Android, the
MauiPageControldid not provide proper accessibility support for its indicator items. EachImageViewlacked meaningful accessibility configuration, causingTalkBackto either skipindicatorsentirely or announce them generically as “button” without context.Description of Change
Accessibility support for indicator items in
MauiPageControlwas improved to provide meaningful TalkBack announcements. Each indicatorImageViewis now configured withImportantForAccessibility=Yesand a customIndicatorAccessibilityDelegateto avoid being read as a generic “button.” Dynamic descriptions are added throughUpdateIndicatorAccessibility, announcing the current page (e.g., “Page 2 of 5, selected”), and are updated whenever indicators are created or refreshed.Issues Fixed
Fixes #31446
Tested the behaviour in the following platforms
Note:
The device test case was added only for Android, since this issue fix was specific to the Android platform.
Output Video
Beforefix.mov
Afterfix.mov