SfImageEditor toolbar controls are not programmatically accessible for assistive technology such as screen readers

[Guy]

Using the Accessibility Insights for Windows tool, the programmatic interface of the SfImageEditor's controls can be examined. It is this interface that is accessed on Windows by assistive technologies such as screen readers. The attached image shows that the UI associated with the colors shown on the color picker toolbar are not programmatically exposed as Button controls, rather they are groups all called "Color" which contain two custom controls, one of which contains a text element names "Button". So any user who uses a screen reader, cannot learn what color is shown visually, such as "red" or "blue".

Also note that because these a groups and custom elements rather than semantic Buttons, is seems that no focus changed events are raised as users tab through the colors. So a screen reader will not follow the focus feedback shown visually as the use tabs through the colors, and will not be informed of where focus is in the app.

[Guy]

Also, on Android, a screen reader swipe gesture can be used to move the Android Talkback screen reader between the color buttons visually, but because the elements' names are all "Button", the users are not informed of the color shown on the button. The attached image shows the Android TalkBack screen reader's caption showing the announcement when moving between color buttons: "Button Double tab to activate". Interestingly the text includes "Double tab", where if the control where a semantic button, it would say "Double-tap".

[Guy]

Also, on Android, a screen reader swipe gesture can be used to move the Android Talkback screen reader between the color buttons visually, but because the elements' names are all "Button", the users are not informed of the color shown on the button. The attached image shows the Android TalkBack screen reader's caption showing the announcement when moving between color buttons: "Button Double tab to activate". Interestingly the text includes "Double tab", where if the control where a semantic button, it would say "Double-tap".

[Guy]

Also, on Android, a screen reader swipe gesture can be used to move the Android Talkback screen reader between the color buttons visually, but because the elements' names are all "Button", the users are not informed of the color shown on the button. The attached image shows the Android TalkBack screen reader's caption showing the announcement when moving between color buttons: "Button Double tab to activate". Interestingly the text includes "Double tab", where if the control where a semantic button, it would say "Double-tap".

[Guy]

Also, on Android, a screen reader swipe gesture can be used to move the Android Talkback screen reader between the color buttons visually, but because the elements' names are all "Button", the users are not informed of the color shown on the button. The attached image shows the Android TalkBack screen reader's caption showing the announcement when moving between color buttons: "Button Double tab to activate". Interestingly the text includes "Double tab", where if the control where a semantic button, it would say "Double-tap".

[Vidyalakshmi Mani]

Hi Guy,

Thank you for reaching out to us.

We’ve identified and fixed the issue where Android TalkBack announces, “Double tab” instead of “Double tap.” This fix will be included in our upcoming weekly NuGet release scheduled for May 5, 2026. We’ll keep you informed once the release is available.

Regarding the remaining accessibility concerns you reported, we’re currently reviewing them in our source and will share an update soon. We appreciate your patience in the meantime.

Regards,

Vidyalakshmi M.

[Guy]

Hi Vidyalakshmi, thank you for following up.

Typically an app should never have to supply the text relating to the "double tap" announcement. If the control used is a match for the semantics of the UI (for example a Button control), then a screen reader will automatically announce whatever it feels is helpful to the user. This will also account for whatever screen reader settings the user currently has selected relating to having more or less information announced. I'd strongly recommend the custom control used for the button-like control shown in the UI is replaced with a semantic Button control. This will ensure that "double tap" is announced when users want it to be, and other things such the screen reader announcements made when tabbing through the controls on a Windows device work as expected.

[Vidyalakshmi Mani]

Hi Guy,

For the issue “Android TalkBack screen reader's caption showing the announcement when moving between color buttons: "Button Double tab to activate".”

We have addressed the reported issue and included the fix in our latest weekly NuGet release, version 33.2.5, which is now available for download from nuget.org

Root Cause: The accessibility text used for the screen reader/TalkBack announcement was not correct, and it has now been updated.

Release Notes: Essential Studio® for MAUI Release Notes - v33.2.5

Regarding query “Any user who uses a screen reader, cannot learn what color is shown visually, such as "red" or "blue".”

At present, announcing the actual color names through the screen reader is not supported in the MAUI SfImageEditor. We have considered this requirement as a feature request; however, we do not have any immediate plans for implementation.

You can track the status using the feedback link below.

Feedback link: Enable screen reader announcement of selected color in SfImageEditor color palette toolbar in .NET MAUI | Feedback Portal

Any updates regarding this feature will be shared through the above link.

For the issue “So a screen reader will not be informed of where focus is in the app on windows”

We have checked, and we can replicate the reported issue. We have logged an issue report for this, we will fix this issue and include the issue fix in our weekly NuGet release update which is expected to be available by June 2, 2026. We appreciate your patience until then.

You can track the status of this report through the following feedback link: Screen reader does not announce focused toolbar items in MAUI SfImageEditor on Windows in .NET MAUI | Feedback Portal

Note: The feedback link provided is private, and you need to log in to view this feedback.

Disclaimer: Inclusion of this solution in the weekly release may change due to other factors including but not limited to QA checks and works reprioritization.

With respect to your recent comment about not supplying text for "double tap" announcements:

In the SfImageEditor, localization is supported, so all custom strings are converted to localized values based on the selected language. Because of this, the text used for screen reader / TalkBack announcements is set manually.

Regards,

Vidyalakshmi M.

[Vishal Omprasad]

Hi Guy,

We have fixed the reported scenario “Screen reader does not announce focused toolbar items in SfImageEditor on Windows” from our end and included the issue fix in our latest weekly NuGet release update version 33.2.10, which is available for download at nuget.org.

Root-cause: Screen reader announcement was not properly implemented for toolbar items when they receive focus.

We thank you for your support and appreciate your patience in waiting for this release. Please get in touch with us if you require any further assistance.

Regards,
Vishal O.