You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As reported on the .NET MAUI repository here, the accessibility of the enclosed Entrys in a SfTextInputLayout is reduced as screen readers do not see the Entry control and skip over them.
I have selected Android and macOS right now as affected platforms, but I assume that this is something that is applicable to all platforms.
Steps to Reproduce
(Taken from the issue reported on the .NET MAUI issue linked above)
Turn on Talkback and Install and open ".NET 9 template" app.
"Home Screen" will open.
Tab till Hamburger menu and press enter, Projects options will screen will open.
Tab till New button and press enter, New project screen will appear, Verify all the elements in Project screen are accessible and MAS Compliant.
Choose a category from the list of category.
Choose a tag from the list of tags.
We can select the task from the existing task list.
Observe that In New project screen Name, category and description sections are not accessible with talkback
Version with bug
1.0.2
Is this a regression from previous behavior?
No, this is a new issue
Last Known Working Version
1.0.2
Affected platforms
Android, macOS
Affected Platform Versions
No response
Have you found a workaround?
No response
Relevant log output
No response
The text was updated successfully, but these errors were encountered:
I just discovered the AutomationProperties.IsInAccessibleTree property. That at least allows us to see it with the screen reader without any changes on your side. However, I do still think its not ideal. If I press on it, it reveals the Entry but I can't start typing. Also the macOS Accessibility Inspector doesn't then recognize it as a textbox yet.
Just adding this for extra information. Maybe it will help you resolve it :)
Description
As reported on the .NET MAUI repository here, the accessibility of the enclosed
Entry
s in aSfTextInputLayout
is reduced as screen readers do not see theEntry
control and skip over them.I have selected Android and macOS right now as affected platforms, but I assume that this is something that is applicable to all platforms.
Steps to Reproduce
(Taken from the issue reported on the .NET MAUI issue linked above)
Version with bug
1.0.2
Is this a regression from previous behavior?
No, this is a new issue
Last Known Working Version
1.0.2
Affected platforms
Android, macOS
Affected Platform Versions
No response
Have you found a workaround?
No response
Relevant log output
No response
The text was updated successfully, but these errors were encountered: