Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve accessibility SfTextInputLayout #66

Open
jfversluis opened this issue Jan 7, 2025 · 1 comment
Open

Improve accessibility SfTextInputLayout #66

jfversluis opened this issue Jan 7, 2025 · 1 comment
Assignees
Labels
bug Something isn't working
Milestone

Comments

@jfversluis
Copy link

Description

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)

  1. Turn on Talkback and Install and open ".NET 9 template" app.
  2. "Home Screen" will open.
  3. Tab till Hamburger menu and press enter, Projects options will screen will open.
  4. Tab till New button and press enter, New project screen will appear, Verify all the elements in Project screen are accessible and MAS Compliant.
  5. Choose a category from the list of category.
  6. Choose a tag from the list of tags.
  7. We can select the task from the existing task list.
  8. 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

@jfversluis
Copy link
Author

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 :)

<sf:SfTextInputLayout 
                    Hint="Name" AutomationProperties.IsInAccessibleTree="True">
    <Entry Text="{Binding Name}" />
</sf:SfTextInputLayout>

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Development

No branches or pull requests

3 participants